Chargebee Release Notes

We're excited to announce that Chargebee now supports the Azerbaijani Manat (AZN), expanding our supported currency options. With this update, you can seamlessly process payments and manage subscriptions in AZN, enabling you to cater to customers in Azerbaijan without the hassle of currency conversion.

We're happy to share that we've fixed a bug in our Checkout.com integration related to ACH payments. Previously, invoices were wrongly marked as paid even when payments failed. Now, we've made sure to listen for the payments_returned webhook event to accurately check the final payment status. This means your invoices will show the correct payment status, giving you confidence in your financial records.

We have tackled a UI glitch that caused confusion around future renewals in Chargebee Billing. Previously, even after billing future renewals for remaining billing cycles by adding them as unbilled charges and invoicing, the next subscription billing date would persistently show up. With this fix, we have revamped the system to accurately check and assign the next billing date in such scenarios, ensuring a seamless and clear billing experience for you. Say goodbye to discrepancies and hello to smoother invoice management!

Get ready for hassle-free billing with our latest enhancement! We've tackled an issue where non-recurring add-ons combined with one-time coupons weren't correctly tallied in consolidated invoices. By directly accessing subscription IDs from the subscription coupon map data, we ensure precise coupon exhaustion.

The following issues were fixed with this release:

Loss aversion card layouts on mobile, resolved issue with display order of loss aversion cards on mobile when 3 or more loss aversion cards are configured.

Billing interval value in Customers report, resolved issue where incorrect value is displayed in the billing interval column of the Customers report.

Enrichment using custom fields, resolved issue where custom field value did not appear in Retention due to failed validation in Chargebee Retention.JS.

We have enhanced your experience in handling subscriptions with metered add-ons. Previously, when you created a flat fee plan and added a metered add-on, then adjusted the price and scheduled these changes for renewal, the invoice would incorrectly display double line items for the metered charge. Now, we have fixed this issue to ensure that your invoice calculations are accurate and reflect only the correct charges at renewal. Plus, any changes you make to add-ons or plans are now flawlessly processed, ensuring that future renewals show the right amounts without any discrepancies.

We have enhanced the Leap UI experience by fixing an issue that previously occurred when setting the Next Billing Date with today's date by selecting the Now option in the timestamp. You no longer face the error 'The date should not be prior to today'. This problem wasn't present in the Classic UI but appeared in the Leap UI. We have fixed the issue.

>We have enhanced the Update subscription for items API in Chargebee to improve your experience significantly. Previously, you might have encountered a error. These improvements ensure that is never set before and that cannot precede . This update addresses a critical issue where setting incorrect dates could lead to a . This enhancement prevents errors caused by incorrect date settings, allowing you to manage subscription terms more effectively and with greater confidence.

We have resolved an issue where configuring non-digital products for a secondary profile without setting up taxes for the primary profile led to errors. With this fix, you can effortlessly manage your billing profiles, ensuring accurate taxation and smoother operations for your business.

We have fixed a pesky bug that was causing language pack upload and download failures due to a new BE id column in Tax Validation Options. With this fix, you can seamlessly upload and download language packs without any hiccups, ensuring smooth operations.

Previously, when cancellation reason codes were mandatory, they did not appear on the user interface, which could hinder your workflow. With this update, these reason codes now display correctly, ensuring you can complete cancellations efficiently and in compliance with your company's policies.

If you've experienced issues with the Next Billing Amount not updating due to API errors, we've addressed and resolved these problems. This fix ensures that your billing information is accurate and up-to-date, allowing you to manage your financial forecasts and billing cycles more effectively.

When utilizing multiple price books, you may have encountered an issue where the Manage CB Product button erased any previously added products. We've successfully resolved this issue, ensuring that your product entries remain intact.

We have enhanced the field mapping capabilities to support more than 100 custom fields. Previously, visibility was limited, restricting your ability to fully customize data synchronization between Salesforce and Chargebee. With this update, you can now access and map an extended range of custom fields, ensuring comprehensive data alignment and improved functionality in your workflows

If you've transitioned subscriptions from indefinite to finite billing cycles, you might have noticed that renewal opportunities were not being automatically generated. We've addressed this issue to ensure that renewal opportunities are now created seamlessly for all applicable subscriptions.

Previously, when you added a discount amount or percentage to a plan line item, these changes were not properly reflected in the CB Quote object's discount field. We've fixed this issue to ensure that any discounts you apply are accurately synced and displayed, making it easier for you to manage financial adjustments and provide clear, precise quotes to your customers.

Previously, when custom fields shared the same API name across different items (plans, addons, and charges), importing your CSV file for bulk creation resulted in errors due to duplicate names or missing mandatory fields. Our new solution simplifies this process: now, when you include a custom field with the same name in your CSV, Chargebee intelligently assigns it based on the item type specified. This means no more duplicate errors or missing mandatory fields.

Previously, when you deleted data from a custom field in a coupon and saved the changes, the old data persisted in the coupon details page, despite the system confirming a successful update. This issue has now been fixed!