Release Notes
Updates, changes, and improvements at Chargebee
November 2022
November 2022
Credit Note Enhancements
Chargebee users can now configure revenue recognition rules for custom reason codes in addition to the standard reason codes. And the accounting configuration for credit notes is now available to contract term based revenue recognition, while previously it was only available for invoice as contract approach.
ACH via Checkout.com
With this release, we have added support for ACH as a new payment method for Checkout.com. This feature is a Private Beta Release. Contact Chargebee Support to enable ACH via Checkout.com for your Test and Live site.
Introducing Foreign Currency Translation Report
The new Foreign Currency Translation report shows the details behind currency translations including the specific foreign exchange rates used in revenue translation and how is the foreign currency change impact calculated, giving you more insights in your multi-currency book of business.
RevRec Improvements
We have added the following enhancements:
Support for use of Product Code, Product Family, or other product custom fields to create a linkage in SSP allocation between performance obligations, where pricing of one product is dependent on pricing of the other while using simple net percent or apportioned net percent standalone policy.
Improvements in regression API and UI testing with automated tools.
Various bug fixes and stability fixes.
Top-Stats Modifications (Landing Page and Receivables Dashboard)
With this release, we have divided the top stats into two categories - Overall Stats and Payment Stats. The Overall stats category will be selected and displayed by default, while the user has the option to select the Payment Stats to view the stats under it. This will provide better clarity in terms of the different sets of numbers being displayed.
Chargebee Dashboard Issues
The following bugs were identified and fixed with this release:
Graphs in the dashboard were identical for the various individual currencies this issue was identified and fixed.
If a user navigates to the toggle button and selects "Include Zeros in Y axis", no change in the Y axis was observed. The option to display zeros in the Y axis was fixed in all reports.
Missing data for the latest period in Home Dashboard was identified and fixed for a specific customer.
Invoices Fix
The following errors were fixed and enhancements were released with this update:
An inability to downgrade quantity for a subscription record was reported. This is now fixed!
We identified a UI bug wherein the application's left navigation section was accessible while deleting usages for a subscription record. Fixed!
The invoice line item name on the invoice PDF was found to be different from what was displayed on the UI. This issue is now resolved.
Upon refresh or closure, multiple line items and subscription items quantity was set to 0 erroneously. Fixed!
We've introduced the ability to import invoices that were written off on a past date into Chargebee via API.
While creating a credit note at the line item level, in addition to calling out that you can choose a date between the billing period, we've introduced an option to choose Now that simplifies your experience.
Skip to the Next Billing Cycle
You can now skip the next billing cycle in a subscription. For example, if a subscription's renewal date is the 30th of every month (and this is August) and the subscriber selects to skip 2 billing cycles then the resumption date of the subscription will be the 30th of November.
Contract Term Amount Logic and VAT Issues
The following issues were fixed with this release:
An issue with the contract term amount calculation logic was reported. The contract term amount for a subscription was found to be incorrect and inconsistent while applying a full discount, editing the next billing date, or adding prorated charges to the unbilled amount with a full discount.
While editing the offline payment method for a subscription record and reactivating the subscription, the invoice generated was found to have VAT applied twice.
AvaTax for Communication Integration
While using the Chargbee-AvaTax for Communications integration, if you are using Avalara's ECMS (Exemption certificate management system) for exemptions, Chargebee now passes a new field called custref id to Avalara that captures the customer id to track tax exemptions.
High-Value Currency Support
Earlier, Chargebee only supported currency value in a 32-bit integer with a maximum value of 21,474,836.47. With this release, the currency value is stored in a 64-bit integer with a long-value limit of 90,071,992,547,409.91. This will allow the merchants to add a bigger currency value to a transaction, plan, or other related entities.
Session Expiry Issue
Earlier, if the customer comes back to the instance/session after it was left idle for some time, it would try to reload but not load anything.With this release, session expiry has been introduced because of which, if the instance/session has been idle for 24 hours, the system will redirect the user to the login page.
Invoices Fix
The following errors were fixed and enhancements were released:
Consolidated invoicing was found to not work as expected when imported subscriptions were present. Fixed!
An inability to override the parent-child customer relationship on a subscription record was reported to occur due to unbilled charges, without any unbilled charges associated. This is fixed!
While so far, Chargebee relied on the invoice date of the invoice to calculate overages, there was revenue leakage identified in cases like closing pending invoices, or sometimes the generation of invoices. We've now shifted to using the invoice-generation date for a more accurate calculation of overages wherever applicable.
We've introduced the ability to record service periods at the line item level while creating credit notes in Leap UI.
We've introduced the ability to delete charge and quick charge line items (when the invoice is in a pending status) through API also.
Webhook Fired on Subscription_Entitlement Creation
To avoid making an extra API call for fetching entitlements every time a new subscription is created. We now allow you to configure and receive a webhook whose payload comprises of the subscription entitlements for the corresponding subscription Id. This will reduce the implementation time of entitlements compared to implementing the JSON metadata-based solution.