# April 2025

Chargebee product updates released in April 2025.

Source: https://release-notes.chargebee.com/april-2025

<Update tags={["NEW FEATURE"]} topics={["Payments"]}>
  ## Introducing Reach as a Merchant of Record solution

  Chargebee now supports [Reach](https://www.chargebee.com/docs/payments/2.0/reach.html) as the Merchant of Record (MoR) solution designed to simplify global selling. With Reach, you can delegate the complexities of global payments, tax collection, and regulatory compliance. It takes care of the operational heavy lifting, so you can focus on growing your business internationally with greater confidence and less friction.

  ### **Why is this important?**

  As the MoR, Reach efficiently handles local transactions, ensures compliance with international regulations, mitigates fraud risks and chargebacks, and reduces payment failures caused by currency and banking restrictions, helping you reduce operational overhead and financial risk.

  ### **How can you use it?**

  Contact [Chargebee Support](https://www.chargebee.com/docs/billing/2.0/kb/getting-started/how-to-contact-chargebees-support-team?utm_source=docs_rn&utm_medium=content&utm_campaign=support) to enable Reach for your Chargebee site. [Learn more](https://www.chargebee.com/docs/payments/2.0/reach.html#configuring-in-chargebee) about configuring Reach with Chargebee.
</Update>

<Update tags={["NEW FEATURE"]} topics={["Usage-Based Billing"]}>
  ## Turn usage data into revenue with Usage-Based Billing

  We're excited to launch Chargebee's latest Usage-Based Billing capabilities, reimagined for the age of AI. You can now send usage data real time, track consumption, price, and bill your products based on usage, right within Chargebee Billing.

  ### **Why is this important?**

  With Usage-Based Billing, you can now ingest your raw usage data of large scale into your Chargebee Billing site and turn it into actionable insights and revenue. This gives you the flexibility to uncover monetization opportunities, test new pricing strategies, and bill your customers accurately for what they use.
  \- Chargebee's Usage-Based Billing is built on a schema-less ingestion engine and a modular architecture that allows for high-volume, flexible usage tracking. It supports rule-based filtering for greater precision and agility, so you can iterate your pricing and packaging without engineering overhead.
  \- Bring [Features](https://www.chargebee.com/docs/2.0/features-overview.html), [Entitlements](https://www.chargebee.com/docs/2.0/entitlements.html), and Usage Consumption into a unified system, so you set usage limits, track allocated vs actual usage, and monetize additional consumption without the operational hassle.
  \- And the benefits go beyond billing. Your usage data can now power downstream workflows like personalized lifecycle offers, credit triggers, and even churn prediction. [Learn more.](https://www.chargebee.com/docs/2.0/understanding-usages.html)

  ### **How can you use it?**

  The latest Usage-Based Billing capabilities are currently in early access. [Contact us](https://form.typeform.com/to/bIsKhNt5?typeform-source=www.chargebee.com) to enable this for your Chargebee Billing site.

  <Image src="/screenshots/april_2025/ubb-image.png" alt="" />
</Update>

<Update tags={["ENHANCEMENT"]} topics={["Payments"]}>
  ## Language packs now support error message overrides

  Chargebee now allows you to customize customer-facing error messages at [Chargebee Checkout](https://www.chargebee.com/docs/2.0/hosted-checkout.html) using language packs.

  ### **Why is this important?**

  You can tailor error messages based on specific error_cause_id values to align with your brand voice, reduce confusion, and provide clearer guidance to your customers. This gives you greater control over the messaging experience and helps improve conversion by minimizing ambiguity during failed checkout attempts.

  ### **How can you use it?**

  Use Chargebee's [Language Packs](https://www.chargebee.com/docs/2.0/configure-multiple-languages.html#language-pack) feature to override the default message shown for any [error_cause_id](https://apidocs.chargebee.com/docs/api/error-handling?lang=curl#error_handling:~:text=the%20param%20attribute.-,error_cause_id,-A%20Chargebee%2Ddefined). Simply update the relevant translation string in your language pack to reflect the message you want your customers to see on Checkout.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["Hosted Pages"]}>
  ## Support for new labels in Full-Page Checkout

  Chargebee's [Full-Page Checkout](https://www.chargebee.com/docs/2.0/hosted-checkout.html#ui-layout-options_full-page-layout) now lets you add additional information above the order submission button in the Order Summary section. You can tailor a message for each checkout scenario—whether your customer is starting a subscription with a trial, subscribing without a trial, or making a one-time purchase.

  ### **Why is this important?**

  Adding clear, timely information right where your customers are about to complete their purchase helps set the right expectations, answer last-minute questions, and reduce potential confusion. This small addition can improve checkout completion rates.

  ### **How can you use it?**

  To enable these messages, head to [Chargebee Billing](https://app.chargebee.com/), and in step 2 of [adding labels](https://www.chargebee.com/docs/2.0/configure-fullpage-fieldslabels.html#add-a-label), search for and enable any of the following:

  - Trial subscription info message
  - Non-trial subscription info message
  - One-time info message
</Update>

<Update tags={["ENHANCEMENT"]} topics={["Accounting Integration"]}>
  ## Automated email notifications on Xero credentials expiry

  Whenever your [Xero](https://www.chargebee.com/docs/2.0/xero-config.html) credentials expire, an automated email will be sent to all site admins and owners. Previously, you had to rely on manual communication from our support team to know when your Xero credentials expired, which could delay your response.

  ### **Why is this important?**

  Chargebee will automatically send an email notification to all site admins and owners when your Xero credentials expire. This will help you take immediate action and avoid any interruptions in your billing and accounting processes.

  ### **How can you use it?**

  This feature is enabled by default for all sites.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["RevenueStory"]}>
  ## Build accurate reports with updated data source descriptions

  We have updated the descriptions for all [data sources](https://www.chargebee.com/docs/2.0/revenuestory-datasources.html) in the [Report Builder](https://www.chargebee.com/docs/2.0/revenuestory-reportbuilder.html). This will provide clear context and help you choose the right data while creating or modifying reports.

  ### **Why is this important?**

  Understanding your data is crucial for building accurate reports. Review the descriptions to better understand what each source contains and ensure you select the most relevant data for your reporting needs.

  ### **How can you use it?**

  Go to **RevenueStory** > **Report Builder**, you'll now find updated descriptions alongside each data source.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["RevRec"]}>
  ## Get a head start on month-end reporting in RevRec

  Previously, the accounting period always ended close to the month end, leaving your finance teams with limited time to review and finalize revenue data. You can now configure your RevRec [accounting period](https://www.chargebee.com/docs/revrec/accounting-and-reporting-periods.html) to close before the end of the calendar month.

  ### **Why is this important?**

  This gives your finance teams more breathing room to finalize reports, perform reconciliations, and share accurate financial insights with senior management, without internal reporting deadlines racing against the clock at month's end.

  ### **How can you use it?**

  To enable early period closure for your RevRec site, reach out to [Chargebee Support](https://www.chargebee.com/docs/billing/2.0/kb/getting-started/how-to-contact-chargebees-support-team?utm_source=docs_rn&utm_medium=content&utm_campaign=support). You can configure the accounting period to close upto 5-6 days prior to the end. Any revenue or deferred revenue from invoices or credit notes generated during the remaining days of the current period will be automatically carried over as catch-up adjustments to the following period.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["RevRec"]}>
  ## Track deferred revenue with improved accuracy at the item level

  RevRec now lets you allocate deferred revenue balances using the same [Standalone Selling Price](https://www.chargebee.com/docs/revrec/standalone-selling-price.html) (SSP) applied for revenue allocation at the contract level.

  ### **Why is this important?**

  This ensures consistency across your revenue recognition process. By aligning deferred revenue with the SSP-based allocation at the order item level, you can accurately match invoiced amounts to their corresponding revenue schedules. This leads to cleaner financials, minimizes manual adjustments, and ensures each item's deferred balance is fully reversed over the contract term.

  ### **How can you use it?**

  This update is available by default if you're using SSP-based allocation in RevRec. The system automatically adjusts invoiced amounts at the item level, so your deferred revenue balances stay in sync with recognized revenue over time.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["RevRec"]}>
  ## Price Variant support in Reports and Product Page

  RevRec now supports Price Variants in alignment with Chargebee Billing's Variant Pricing feature. This enhancement enables users to drill down into Price Variant ID and Price Variant Name within reports, allowing for detailed analysis of revenue recognized across different price variants of a given product.

  ### **Why is this important?**

  You can now analyze revenue performance across different pricing tiers of the same product, helping you understand how each price variant contributes to overall revenue.

  ### **How can you use it?**

  You'll find the Price Variant ID and Price Variant Name available in your revenue recognition reports and directly on the Product Page in RevRec. Use these fields to filter, group, and analyze revenue data by variant.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["RevRec"]}>
  ## Add custom fields to your journal exports

  RevRec's Journal Exports now include custom fields used for journal account mapping and aggregation. This lets you exercise control over how journal entries are structured in your accounting system.

  ### **Why is this important?**

  By incorporating custom field values, you can align your exports with internal reporting standards, meet unique business requirements, and simplify reconciliation across systems.

  ### **How can you use it?**

  When setting up journal account mapping or aggregation rules, you can now use custom fields to drive how journal entries are categorized and exported. Once configured, these fields will automatically appear in the exported journal data, ready for ingestion into your accounting platform.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["RevRec"]}>
  ## Search and Filter for GL Account Mappings

  You can now search for [General Ledger(GL) account mappings](https://www.chargebee.com/docs/revrec/journal-account-mapping.html) in RevRec using account numbers directly from the Journal Account Mapping page.

  ### **Why is this important?**

  This update saves you time when managing large sets of GL accounts. Instead of manually scanning through mappings, you can quickly locate specific entries by typing in the GL account number, helping reduce errors and speed up month-end workflows.

  ### **How can you use it?**

  Head to the [Journal Account Mapping](https://www.chargebee.com/docs/revrec/journal-account-mapping.html) page in RevRec, and use the new search field to enter a GL account number. Matching results will instantly appear, making it easier to review or update the relevant mapping

  <Image src="/screenshots/april_2025/revrec-filter.png" alt="" />
</Update>

<Update tags={["ENHANCEMENT"]} topics={["RevRec"]}>
  ## Recognising discount as negative revenue over time

  RevRec now lets you recognize discounts as negative revenue over the contract term by treating them as separate line items with Ratable Revenue Recognition.

  ### **Why is this important?**

  This allows for the setup of discounts as separate line items with [ratable revenue recognition](https://www.chargebee.com/docs/revrec/ratable-revenue-recognition.html). Instead of spreading a discount across other sales order items, you can track it independently, making your revenue reports more transparent and your journal entries more precise.

  ### **How can you use it?**

  Set up discounts as distinct line items in your sales orders and apply [Ratable Revenue Recognition](https://www.chargebee.com/docs/revrec/ratable-revenue-recognition.html). RevRec will automatically track revenue and deferred revenue for the discount, and reflect the corresponding entries in your journal exports and revenue reports.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["RevRec"]}>
  ## Pause Revenue at the customer level

  You can now pause revenue for all active orders tied to a specific customer using the new **Pause Revenue** feature in RevRec.

  ### **Why is this important?**

  This gives you better control over revenue recognition when a customer's billing or service status changes, such as during disputes, contract holds, or delivery delays. Instead of handling each order individually, you can pause revenue recognition across the board and resume it when appropriate, helping ensure your revenue reporting aligns with business reality.

  ### **How can you use it?**

  Navigate to the customer record in RevRec and enable the **Pause Revenue** option. This will halt revenue recognition for all of the customer's active orders. You can resume recognition at any time as required.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["RevRec"]}>
  ## Release deferred revenue at sub cancellation

  RevRec now supports the release of deferred revenue at the item level when a bundled subscription is cancelled before all units have been delivered, specifically for products using delivery-based revenue recognition.

  ### **Why is this important?**

  This ensures that [deferred revenue](https://www.chargebee.com/docs/revrec/standard-reports.html) is released accurately for undelivered items when a subscription ends early, rather than relying on SSP-based [credit note](https://www.chargebee.com/docs/2.0/credit-notes.html) allocation. You get clearer revenue tracking at the product level and more precise handling of refunds, especially in mixed-method bundles that combine delivery-based and recurring revenue items.

  ### **How can you use it?**

  When a bundled subscription with delivery-based products is canceled, RevRec will automatically release the remaining deferred revenue on each applicable item. The refund will be calculated based on the undelivered portion, and reflected directly in your revenue and journal reports—no extra configuration needed.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["Subscriptions"]}>
  ## Accurate invoicing for backdated subscriptions with Multi-Frequency Billing

  While backdating a subscription with [Multi-Frequency Billing](https://www.chargebee.com/docs/2.0/subscriptions.html#subscription-billing-frequency_multi-frequency-billing), you can now ensure that addons are invoiced accurately for the entire backdated period, not just for the first term. This update brings the billing behavior in line with your expectations when handling [backdated subscriptions](https://www.chargebee.com/docs/2.0/subscriptions-creation-backdating.html).

  ### **Why is this important?**

  You no longer have to manually adjust charges when backdating subscriptions involving addons. This helps you maintain accurate invoices, reduces billing errors, and ensures that customers are charged fairly for the services used during the entire backdated period.

  ### **How can you use it?**

  Simply [backdate a subscription](https://www.chargebee.com/docs/2.0/subscriptions-creation-backdating.html) as you normally would. With Multi-Frequency Billing enabled, Chargebee will now automatically invoice for all applicable addon terms during the backdated period.
</Update>

<Update tags={["ENHANCEMENT"]} topics={["Subscriptions"]}>
  ## Default Manual Discount type set to forever

  The default type for [Manual Discounts](https://www.chargebee.com/docs/2.0/subscription-manual-discounts.html#manual-discount-duration) has now been updated to **Forever**. This ensures that any manual discounts you apply will automatically persist on the subscription indefinitely without the need for ongoing adjustments.

  ### **Why is this important?**

  This change reduces the need for repeated updates to discount settings, saving you time and effort. It also provides more consistency in managing your pricing and discounts.

  ### **How can you use it?**

  While [creating](https://www.chargebee.com/docs/2.0/subscriptions.html#creating-a-subscription) or [updating](https://www.chargebee.com/docs/2.0/subscriptions.html#editing-a-subscription) a subscription record, [applying manual discounts](https://www.chargebee.com/docs/2.0/subscription-manual-discounts.html#adding-manual-discounts) will now default to **Forever**, until you decide to modify or remove them, offering you greater control over your pricing strategy.
</Update>

<Update tags={["UI ENHANCEMENT"]} topics={["Invoices"]}>
  ## Discount summary updated in credit note preview

  We've updated the discount summary section in the [credit note](https://www.chargebee.com/docs/2.0/credit-notes.html) preview to improve clarity and accuracy. The line previously shown as '$xxx USD discount applied' has been changed to '$xxx USD total discount reduced' and is now displayed after the line '$xxx USD discount is reduced from the total credits issued'.

  ### **Why is this important?**

  This change provides better visibility and context when multiple discounts are involved. By reordering and rewording the discount lines, you get a more accurate and easier-to-read breakdown of how discounts impact the credit note total.

  ### **How can you use it?**

  When previewing credit notes that include multiple discounts, you'll now see a more logical sequence of discount information, helping you review and share accurate billing summaries with confidence.

  <Image src="/screenshots/april_2025/credit-note-preview.png" alt="" />
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Enhanced filtering for override relationship in subscriptions

  If you're using [account hierarchies](https://www.chargebee.com/docs/2.0/account-hierarchy.html), you can now filter subscriptions based on the override relationship setting. Previously, subscriptions where the [override_relationship](https://apidocs.chargebee.com/docs/api/subscriptions?lang=go#subscription_override_relationship) was not set didn't appear when filtering for False, even though they showed as false in the API. To fix this, we've introduced two new filters 'Is Present' and 'Is Not Present', so you can accurately segment subscriptions based on whether an override relationship exists.
</Update>

<Update tags={["BUG FIX"]} topics={["Payments"]}>
  ## Transaction Descriptors support for BACS via Stripe

  You can now display custom transaction descriptors for BACS payments made through Stripe. Previously, your customers may have seen generic or incomplete information on their bank statements due to Chargebee not passing descriptors to Stripe. With this update, Chargebee now includes the correct statement descriptors like your business name in the payment request, ensuring your customers can easily recognize their charges. This can help reduce payment disputes and build trust with your brand.
</Update>

<Update tags={["BUG FIX"]} topics={["Invoices"]}>
  ## Display fix for 0% tax on invoices

  Invoices display a 0% [tax rate](https://www.chargebee.com/docs/2.0/tax-overview.html) when applicable, ensuring compliance with regional tax regulations like GST in Singapore. Previously, when you applied a 0% tax rate, the tax percentage was omitted from the invoice, even though the amount was correctly shown as zero. With this fix, your invoices will now reflect both the amount and the applied tax rate, helping you stay audit-ready and meet reporting requirements.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Item tiers are now cleared when switching pricing models

  When you change a subscription's [pricing model](https://www.chargebee.com/docs/2.0/plans.html#pricing-models) 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.
</Update>

<Update tags={["BUG FIX"]} topics={["Invoices"]}>
  ## Accurate billing date display for future subscriptions

  When you use [Bill Future Renewal](https://www.chargebee.com/docs/2.0/advance-invoices.html#generating-an-advance-invoice) 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](https://www.chargebee.com/docs/2.0/proration.html#introduction_billing-mode) scenarios and ensures consistency in how billing dates are shown both before and after subscription activation.
</Update>

<Update tags={["BUG FIX"]} topics={["Invoices"]}>
  ## Avoid errors when creating credit notes

  You can now create [adjustment credit notes](https://www.chargebee.com/docs/2.0/credit-notes.html#types-of-credit-notes_adjustment-credit-note) 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.
</Update>

<Update tags={["BUG FIX"]} topics={["Invoices"]}>
  ## Daylight saving issue resolved in invoice estimates

  You can now create [one-time invoice](https://www.chargebee.com/docs/2.0/charges.html#adding-quick-charges_adding-quick-charge-via-ui) estimates for extended service periods including multi-year durations, without encountering errors related to `service_period_in_days`. 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.
</Update>

<Update tags={["BUG FIX"]} topics={["Invoices"]}>
  ## Accurate values now shown when previewing credit notes

  When previewing a [credit note](https://www.chargebee.com/docs/2.0/credit-notes.html) 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](https://www.chargebee.com/docs/2.0/multi-decimal-support.html) is not enabled. With this fix, your credit note previews will reflect clean and consistent formatting, helping you avoid confusion during billing adjustments.
</Update>

<Update tags={["BUG FIX"]} topics={["Notifications"]}>
  ## Special characters in email notes now display correctly

  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.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## No more errors when activating subscriptions with backdated trials

  Activating a [subscription](https://www.chargebee.com/docs/2.0/subscriptions.html) from trial could cause *'Sorry, something went wrong'* error in some cases for subscriptions with [backdated trial ending](https://www.chargebee.com/docs/2.0/subscriptions-creation-backdating.html) and [multi-frequency billing](https://www.chargebee.com/docs/2.0/subscriptions.html#subscription-billing-frequency_multi-frequency-billing). We've added a validation check, so your subscription activations can now proceed without interruption.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Edit restrictions applied for subscriptions with ramps

  With [backdating subscriptions](https://www.chargebee.com/docs/2.0/subscriptions-actions-backdating.html) and [day-based billing](https://www.chargebee.com/docs/2.0/proration.html#introduction_billing-mode) enabled, you can no longer schedule subscription changes through **Edit Subscription** with [ramps](https://www.chargebee.com/docs/2.0/ramps.html), as intended. Previously, such edits were allowed and scheduled but never took effect, ultimately causing SUB_RENEWAL jobs to fail with the message *'This sub has pending changes before renewal'*. With this fix, Chargebee now blocks incompatible edits for ramped subscriptions, helping you avoid failed renewals and ensuring billing flows stay consistent.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Day-based billing now adheres to correct cancellation timing

  When you prepone a scheduled [subscription cancellation](https://www.chargebee.com/docs/2.0/cancellations.html) 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](https://www.chargebee.com/docs/2.0/credit-notes.html) only for the actual unused period, starting from the correct day.
</Update>

<Update tags={["BUG FIX"]} topics={["Invoices"]}>
  ## Better visibility for changes to advance charges

  You'll now receive an [invoice_updated](https://apidocs.chargebee.com/docs/api/events?lang=go#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.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Error resolved for activating subscriptions via UI and API

  With [Multi-Frequency Billing](https://www.chargebee.com/docs/2.0/subscriptions.html#subscription-billing-frequency_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](https://apidocs.chargebee.com/docs/api/error-handling?lang=go#error_codes_list), has now been fixed. You can now activate subscriptions, whether manually or programmatically without disruption to your workflows.
</Update>

<Update tags={["BUG FIX"]} topics={["Hosted Pages"]}>
  ## In-App Checkout sessions for gift subscriptions fixed

  If your customers recently encountered the error message "The authorized amount is less than the collectable amount" during [Checkout](https://www.chargebee.com/docs/2.0/hosted-checkout.html) sessions for [gift subscriptions](https://www.chargebee.com/docs/2.0/gift-subscriptions.html), 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.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Manage trial subscriptions without update errors

  You can now update trial [subscriptions](https://www.chargebee.com/docs/2.0/subscriptions.html) 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](https://www.chargebee.com/docs/2.0/contract-terms.html), helping you avoid interruptions when adjusting subscription details.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Issue resolved for multi-frequency addons and coupons

  We've fixed an issue where applying an [Offer Quantity Coupon](https://www.chargebee.com/docs/2.0/coupons.html#offer-quantity-coupons) to subscriptions with [Multi-Frequency Billing](https://www.chargebee.com/docs/2.0/subscriptions.html#subscription-billing-frequency_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.
</Update>

<Update tags={["BUG FIX"]} topics={["Hosted Pages"]}>
  ## Accurate tagging for subscription payment sources

  We've fixed an issue where the Overridden tag was incorrectly appearing on [subscriptions](https://www.chargebee.com/docs/2.0/subscriptions.html#viewing-subscriptions) even when the [payment source](https://www.chargebee.com/docs/2.0/subscriptions.html#editing-a-subscription_edit-trial-end:~:text=Payment%20Methods%20%2D%20This%20section%20displays%20the%20customer%27s%20payment%20method%20that%20is%20added%20for%20the%20subscription.%20You%20can%20click%20the%20more%20icon%20to%20modify%20the%20same.) was actually inherited from the customer record. Now, you'll only see the Overridden tag when a subscription truly has a distinct payment source. This ensures greater clarity when reviewing subscription details.
</Update>

<Update tags={["BUG FIX"]} topics={["Hosted Pages"]}>
  ## Customized labels now display '@' symbols correctly in Full-Page Checkout

  If you use [Full-Page Checkout](https://www.chargebee.com/docs/2.0/hosted-checkout.html#ui-layout-options_full-page-layout) and customize labels through the [Language Pack](https://www.chargebee.com/docs/2.0/configure-multiple-languages.html), 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.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Next billing date changes now correctly restricted in Calendar Billing

  Previously, under [Calendar Billing](https://www.chargebee.com/docs/2.0/calendar-billing.html), you were able to modify the [Next Billing Date](https://www.chargebee.com/docs/2.0/next-billing-date.html) 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.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Plan-level Trial-End Actions now honoured for subscriptions

  We've fixed an issue where subscription [Trial-End Actions](https://www.chargebee.com/docs/2.0/trial_periods.html) 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.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Scheduled cancellations and plan changes now handled correctly

  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](https://www.chargebee.com/docs/2.0/proration.html#introduction_billing-mode). 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.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Accurate charge calculations for Offer Quantity Coupons

  The issue of an [Offer Quantity Coupon](https://www.chargebee.com/docs/2.0/coupons.html#offer-quantity-coupons) being incorrectly applied, leading to inaccurate charges on draft invoices, has been fixed. This bug previously affected the application of a free 1000-quantity coupon, resulting in unexpected charges. With the fix, you can now expect an accurate coupon application, ensuring that customer renewals and revenue are properly handled. [Contact Chargebee Support](https://www.chargebee.com/docs/billing/2.0/kb/getting-started/how-to-contact-chargebees-support-team?utm_source=docs_rn&utm_medium=content&utm_campaign=support) to avail this fix for your Chargebee Billing site.
</Update>

<Update tags={["BUG FIX"]} topics={["Invoices"]}>
  ## Correct modal title now displayed for consolidated invoicing settings

  The issue with the missing locale for the [consolidated invoicing](https://www.chargebee.com/docs/2.0/consolidated-invoicing.html) confirmation modal has been fixed. Previously, the confirmation modal title for the **Disable confirmation** was not appearing correctly for English (en) users. This fix ensures that the modal now loads properly with the correct title, improving the user experience when managing consolidated invoicing settings.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Accurate billing periods for extended non-renewing subscriptions

  We've fixed an issue where [invoices](https://www.chargebee.com/docs/2.0/invoice-overview.html) and [unbilled charges](https://www.chargebee.com/docs/2.0/unbilled-charges.html) displayed an incorrect prorated billing period when a non-renewing subscription's cancellation date was extended. Previously, the billing period was mistakenly ended a day earlier, leading to incorrect billing details. Now, when you extend a non-renewing subscription's cancellation date, the prorated billing period accurately reflects the correct start and end dates, helping you maintain precise billing and reporting.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Accurate unused period timing in credit note line items

  [Credit notes](https://www.chargebee.com/docs/2.0/credit-notes.html) are now generated using the subscription's term end date instead of the next billing date. Previously, this led to incorrect billing periods on credit notes when the next billing date didn't align with the actual term-end. With this fix, credit notes will accurately reflect charges up to the end of the term, helping you maintain precise billing records and avoid revenue discrepancies.
</Update>

<Update tags={["BUG FIX"]} topics={["Subscriptions"]}>
  ## Accurate Free Period removal in subscription settings

  You can now successfully remove the [Free Period](https://www.chargebee.com/docs/2.0/subscriptions.html#creating-a-subscription_free-period) for subscription in a trial. Previously, when you unchecked the **Free Period** option, the preview screen indicated it was removed, but the change wasn't applied. This fix ensures that when you remove the free period, it's properly reflected, providing more control and accuracy when managing trial periods and subscription settings.
</Update>

<Update tags={["BUG FIX"]} topics={["Invoices"]}>
  ## Adjust due amount credit note now available for all due amounts

  You can now successfully [create a credit note](https://www.chargebee.com/docs/2.0/credit-notes.html#types-of-credit-notes_adjustment-credit-note) with **Adjust due amount** option even when the due amount is $0.01. Previously, this option was unavailable when the due amount was exactly $0.01, as the system incorrectly excluded it. This issue has been fixed, and now any due amount equal to or greater than $0.01 will allow the **Adjust due amount** option to be selected.
</Update>
