BACS via Adyen
With this release, we have added support for Chargebee JS and HPv3 Integration for BACS via Adyen.
Note: This feature is in beta. Submit a request to enable this feature.
Release Notes
Updates, changes, and improvements at Chargebee
Release Notes
Updates, changes, and improvements at Chargebee
With this release, we have added support for Chargebee JS and HPv3 Integration for BACS via Adyen.
Note: This feature is in beta. Submit a request to enable this feature.
With this release, we have added support for Chargebee JS and HPv3 Integration for BACS via Stripe.
Note: This feature is in beta. Submit a request to enable this feature.
With this release, we have added support for Chargebee JS and HPv3 Integration for BECS via Stripe.
Note: This feature is in beta. Submit a request to enable this feature.
The following issues were fixed with this release:
Scheduled changes were not working as expected with Metered Billing.
A scheduled bulk upload operation to update price for a large list of customers was not occurring as per schedule.
A 500 Error was displayed while downgrading a subscription from yearly to monthly frequency with day-based billing and proration enabled.
We found an issue wherein invoice was not being aligned correctly to the calendar billing setting.
The following issues were fixed with this release:
An incorrect contract term value was found to be applied when customer modified a subscription to cancel and create a new contract term.
The Total Contract Value (TCV) was found to be incorrect with scheduled changes.
Customers with coupons removed through UI were not seeing MRR change in the same period as the change date was not being captured correctly.
This release will reduce the page loading time, boost performance, cut redundant hits, and optimize API response time. With this release, we are focusing on improving Largest Contentful Paint (LCP) score for enhanced user experience by prioritizing critical asset loading, deferred loading, and API enhancements for faster rendering.
With this release, we have addressed a user interface inconsistency on the Customers, Invoices, and Credit Notes Index page. In Leap UI, when a company name is present, the first name and last name details will now be displayed, aligning with the behavior in the classic UI.
The following are the fixes:
We've addressed the absence of the "Override Relationship" and "Payment Terms" filters on the Subscriptions, Invoices, or Credit Notes Index page.
When the "Override Relationship" filter is set to `true` and `is present`, it displayed two different sets of records. This issue is fixed.
In this release, we have enhanced the security and stability of our system by restricting certain characters in Customer and Subscription IDs.
Improvements:
Auto-Hyphenation: To prevent issues arising from spaces in IDs, we now automatically insert hyphens - when spaces are entered during ID creation.
Tooltip Information: A tooltip has been incorporated alongside the ID field, providing clear explanations about the restricted characters.
Please review the changes below to ensure a seamless experience:
Restricted Characters:
Percentage `%` - Usage will result in API error 500.
Space - Usage will result in API error 404.
Semicolon `;` - Usage will result in API error 500.
Back Slash `/` - Usage will result in API error 400.
Forward Slash `\` - Usage will lead to a complete site break with the "The page isn't working" message.
The following issues were fixed with this release:
VAT was charged for a customer with valid VAT number. With this release, we enabled necessary site settings re-validate invalid vat numbers which were last validated more than (or equal to) 30 days ago.
We identified and fixed an invalid VAT Customer field wherein the filter in customer index page was reporting customers with no VAT number as invalid.
Taxes were not calculated and applied for an invoice with billing address in UK. We identified the root cause for this bug and fixed the same.
With manual taxes configured for Canada region, a transaction was incorrectly treated as exempt and taxes were not applied with the exempt reason updated as export in the invoice event.
A credit note tax amount was found to be rounded wrongly. This is now fixed!
The reverse charge toggle will now be displayed in a greyed out state on the UI when third-party tax is configured.
The following issues were fixed with this release:
With manual taxes configured for Canada region, a transaction was incorrectly treated as exempt and taxes were not applied with the exempt reason updated as export in the invoice event.
A credit note tax amount was found to be rounded wrongly. This is now fixed!
The reverse charge toggle will now be displayed in a greyed out state on the UI when third-party tax is configured.
We identified that incorrect tax rates were captured on invoices, invoice PDFs, and invoice events though tax rates were applied correctly. This is now fixed!
The following issues were fixed with this release:
Inability to create credit notes at times, while it works as expected mostly.
The billing cycle was found to be displayed as 0 on the Schedule Advance Invoices estimate popup due to an issue identified with backdating and calendar billing. This is now fixed!
Currently, in Contact Import, deleting contacts is only supported via email or phone. This creates an issue for cases in which multiple customers have the same email. If the email of one customer is deleted or changed at the source, the current contact import deletes contacts of all customers having the same email. With this release, we have added support for deletion by Customer ID in Contact Import.
With this release, we have added the Invoice Ageing bucket as a parameter to the Payment Risk algorithm to determine the payment risk more efficiently to reflect the tendency of payments for a customer. This addition makes the risk further tightened to reflect the near-perfect payment behaviour of customers.
With this release, we have added two new quick filters to the Customer View:
First Payment Failure - This represents customers who have had their first payment failure
Card Updated After Retries - This represents the set of customers who updated their cards after retries and require assistance in attempting their payments again.
With this feature release of our React Native SDK, we have introduced the retrieve subscription entitlements function - retrieveEntitlements(). Learn more.
We are pleased to announce the latest update to our Xero Sync Rules feature, aimed at enhancing your experience with seamless synchronization of payment data. However, we would like to bring to your attention a specific display issue that has been identified and addressed in this release.
We are excited to announce an important update in Revenue Story that improves the navigation experience for Revenue Recognition reporting. In response to valuable feedback from our users, we have made significant changes to the RevRec link located in the left navigation bar.
In this release, we are thrilled to introduce the new and enhanced [Quick View](https://www.chargebee.com/docs/revrec/revrec-reporting-new.html#what-are-the-main-differences-between-revrec-quick-view-reports-and-the-revenue-recognition-reports-in-revenuestory-and-classic-reports) reports in the RevRec section, which offers a more efficient and insightful revenue recognition analysis. As part of this improvement, we will be discontinuing the use of the existing RevRec reports in the Accounting Reports section.
The following enhancements were released with this release:
Pause Subscriptions: Introducing the Pause/Resume Subscription button on a CB Subscription page in Salesforce, allowing you to pause subscriptions. You have the flexibility to choose between Immediate pausing, End of the term, Specified date for pausing
Resume Subscriptions: With the Pause/Resume Subscription button, you can easily resume paused subscriptions. Choose to resume immediately or specify a date for resuming.
Multiple Price Books Support: For users dealing with multiple price books, now you can create entries for products in your preferred price book. Select the price book on the opportunity to ensure correct product additions.
Subscription Cancellation Enhancements: Updates to subscription cancellations for more control over termination. Schedule Chargebee subscription termination at the end of its term or on a specific date. Provide a cancellation reason code for better tracking and analysis.
Salesforce Flow Updates: Salesforce Flows have been enhanced to support cancel subscriptions and change subscription actions. Improved integration capabilities for seamless subscription management.
Contact to Account Association: A new feature enabling contacts without accounts to be associated with newly created accounts. Useful when a contact is created in Salesforce before a subscription or deal creation. When a customer returns to make a direct purchase through Chargebee, an account will be generated in Salesforce, and the contact will be linked based on a matching field. When future subscriptions are created with unbilled charges, the contract value was displayed incorrectly as per discount.
Chargebee now allows you to void an invoice with credit note created automatically. As per law in Nordic Countries(and some EU regions like Germany and France), you must void an invoice and regenerate a new one when you generate an incorrect invoice. While voiding the invoice, the original invoice must be adjusted by a separate document equivalent to a negative invoice (Cancellation invoice) and acts as an indicator that the original invoice stands canceled.
We are pleased to announce that our Android SDK now includes a new method that handles the one-time purchase against App Store Connect and creates a Charge corresponding to this one-time purchase in Chargebee. Learn more.
Apple changed the functionality of REFUND notification and now this notification type supports auto-renewable subscriptions along with one-time purchases. Chargebee also added support for the same. Learn more about V2 notifications type.
With this release, we have added support for Stripe's new bank account instant verification method called Financial Connections. This method is proprietary to Stripe and it is targetted towards simplifying the verification process. This feature is in beta, contact Chargebee Support to enable it.
The following issues were fixed with this release:
After re-bench-marking of List Invoice API with two environment properties to reduce redundant calls, we found that the app server was taking more time between execution of two SQL queries. This is now fixed!
The provincia field under Sender was found to take 'zz' as value since the correct State (County) code was not passed to Storecove. This has been fixed!
The following issues were fixed with this release:
While entering the VAT number on a Chargebee Billing TEST site, an error "the VAT number is invalid" was displayed. However, the same VAT number when entered on the LIVE site did not throw any error. This is now fixed!
The integrations page kept loading when one or more tax providers were configured. Fixed!
An error MATCHING_RESOURCE_NOT_FOUND was thrown during VAT Validation by His Majesty's Revenue & Customs(HMRC). Fixed!
Introducing cache and retry mechanism for React Native SDK purchase flow to enhance subscription processing. With this update, the SDK now allows you to validate the receipt during network failures. Learn more.
The following issues were fixed with this release:
After re-bench-marking of List Invoice API with two environment properties to reduce redundant calls, we found that the app server was taking more time between execution of two SQL queries. This is now fixed!
The provincia field under Sender was found to take 'zz' as value since the correct State (County) code was not passed to Storecove. This has been fixed!
In response to Shopify's deprecation of older API versions, we have implemented an upgrade to the new Shopify API version. This release focuses on updating the URLs of the APIs being called to ensure compatibility with the latest version. Thorough testing has been performed to ensure a smooth transition and maintain seamless functionality.