Chargebee Release Notes

When you change a subscription's pricing model from tiered to per unit or flat fee model, Chargebee now correctly clears any leftover item tier data tied to the original plan. With this fix, you'll see only the relevant pricing details across your logs and exports, making it easier to review changes and ensure data accuracy.

When you use Bill Future Renewal to generate an invoice for a future subscription, the Next Billing date now correctly displays as date(n) 00:00:00 instead of date(n-1) 23:59:59 while the subscription is in a future state. This fix applies to day-based billing scenarios and ensures consistency in how billing dates are shown both before and after subscription activation.

You can now create adjustment credit notes for prorated invoices without running into errors that previously blocked the action with a 'Credit note amount exceeds limit' message. This fix ensures that even when minor differences (like a 1-cent mismatch) occur due to tax and ratio calculations, your credit note creation will go through successfully. This helps you issue accurate refunds and adjustments without manual intervention.

You can now create one-time invoice estimates for extended service periods including multi-year durations, without encountering errors related to . This fix addresses a daylight saving time handling issue in the EDT timezone that previously disrupted interval calculations, especially for dates spanning several years. You'll no longer face errors when invoicing for long-term services.

When previewing a credit note after reducing the billing period, you'll now see accurate values in the Amount and Discount fields, without unnecessary trailing zeros. This issue was caused by a UI bug and occurred even on sites where multi-decimal pricing is not enabled. With this fix, your credit note previews will reflect clean and consistent formatting, helping you avoid confusion during billing adjustments.

Chargebee now supports proper display of "@" character in your email content. Previously, characters like "@" appeared in encoded form, making it harder to read important references such as email addresses.

Activating a subscription from trial could cause 'Sorry, something went wrong' error in some cases for subscriptions with backdated trial ending and multi-frequency billing. We've added a validation check, so your subscription activations can now proceed without interruption.

When you prepone a scheduled subscription cancellation using the Edit Scheduled Cancellation option, Chargebee now correctly calculates the credit note period. Earlier, credit was issued from the start of the cancellation day (00:00:00) instead of the end (23:59:59), resulting in an extra day of credit. This fix ensures proration is accurate and aligns with day-based billing conventions, so you issue credit only for the actual unused period, starting from the correct day.

You'll now receive an invoice_updated event whenever advance charges are removed or no longer apply, ensuring the Invoiced with advance charges filter reflects the latest invoice state. This fix helps you maintain accurate reporting and stay on top of billing changes without missing key updates.

With Multi-Frequency Billing enabled, you'll no longer encounter the "Sorry, something went wrong when trying to process the request" error when activating subscriptions through the UI or API. This issue, which caused valid activation requests to fail with a 500 internal_error, has now been fixed. You can now activate subscriptions, whether manually or programmatically without disruption to your workflows.

If your customers recently encountered the error message "The authorized amount is less than the collectable amount" during Checkout sessions for gift subscriptions, this was due to a tax calculation issue specific to those subscriptions. We've fixed the error, so you can now confidently offer gift subscriptions without disruptions at Checkout.

You can now update trial subscriptions scheduled for cancellation at the end of the billing term without running into the error 'Sorry, something went wrong while processing the request'. This fix gives you greater flexibility in managing trial subscriptions tied to contract terms, helping you avoid interruptions when adjusting subscription details.

We've fixed an issue where applying an Offer Quantity Coupon to subscriptions with Multi-Frequency Billing caused the subscription item renewal to fail. With this update, you can now confidently apply such coupons without interrupting subscription renewals, ensuring more reliable billing operations.

If you use Full-Page Checkout and customize labels through the Language Pack, you may have noticed that the '@' symbol was incorrectly displayed as '@' to your customers. We've fixed this issue so that labels now appear exactly as you intended.

Previously, under Calendar Billing, you were able to modify the Next Billing Date without restrictions due to a bug that could lead to billing inaccuracies. Now, when you attempt to change the Next Billing Date through the UI, Chargebee enforces the appropriate checks, maintaining consistent and accurate billing behavior.

We've fixed an issue where subscription Trial-End Actions were incorrectly defaulting to the site-level setting instead of respecting the plan-level configuration as intended. Now, when you define a trial_end_action at the price point level, your subscriptions will correctly follow this setting, ensuring accurate trial management and reducing any confusion in the UI.

We've fixed an issue where subscription cancellations would fail with the error 'Billing cycle cannot be lesser than 1' when managing scheduled plan changes and cancellations under millisecond-based proration. Previously, if you removed a scheduled cancellation after setting a future-dated plan change, Chargebee did not correctly update the billing cycle, causing the update to fail after renewal. With this fix, billing cycles are now properly updated when scheduled cancellations are removed, ensuring that subscriptions transition correctly without errors.