Zum Inhalt springen

Chargebee Release Notes

1.904 Einträge aus 1 Quelle. Zuletzt aktualisiert:

Folge Chargebee, um die Release Notes in deinen Feed zu holen.

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Produktkatalog aufräumen mit dem Catalog Organizer

Der neue, standardmäßig aktivierte Catalog Organizer ermöglicht es, Artikelpreise zwischen Artikeln zu verschieben oder zusammenzuführen, auch per Massenvorgang, mit Vorschau der Änderungen und Wiederholung fehlgeschlagener Verschiebungen.

Introducing Catalog Organizer in Chargebee Billing to restructure your product catalog by moving and consolidating item prices across items without re-creating them.

Why is this important?

The product catalog can get cluttered during migration or when you maintain multiple prices across regions, currencies, and billing frequencies. With Organizer enabled by default, your sites can immediately streamline and consolidate item prices as needed. You can now quickly:

  • Merge item prices from one item to another without recreating them.
  • Move multiple item prices in a single bulk operation.
  • Preview changes before confirming, and retry failed moves.
  • Clone an item to use as a destination, and maintain a clear catalog structure.

How can you use it?

Go to Product Catalog > Catalog Organizer in your Chargebee Billing site and move your items as required. Learn more.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Eigene Developer-Rolle für Integrationen

Eine neue Developer-Rolle gibt Zugriff auf Integrationseinstellungen wie API Keys, Webhooks, Event Streams, Custom Fields und AI Settings, ohne Admin-Rechte zu vergeben, und ist nur auf Testsites verfügbar.

You can now assign a dedicated Developer role in Chargebee that gives your team access to integration settings such as API Keys, Webhooks, Event Streams, Custom Fields, and AI Settings, without granting Admin role permissions. This role is available only on test sites and is designed specifically for developers who need to build and validate integrations.

Why is this important?

Previously, developers required Admin access to configure integrations, exposing sensitive areas such as user management, billing, and site-wide settings. This created unnecessary security risks and went against the principle of least privilege. With the Developer role, you can limit access to only what is required, reducing risk while maintaining productivity. It also helps you identify developer users across sites, enabling more relevant updates and alerts tailored to their needs.

How can you use it? …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Überzahlungen aus NetSuite mit Chargebee synchronisieren

Mit der Einstellung „Sync Excess Payments“ werden nicht zugeordnete Beträge einer NetSuite-Zahlung in Chargebee Billing als Überzahlung erfasst und mit der ursprünglichen NetSuite-Transaktion verknüpft.

You can now sync excess payments from NetSuite to Chargebee Billing using the Sync Excess Payments setting. When enabled, any unapplied amount on a NetSuite payment is recorded as an excess payment in Chargebee Billing and linked to the original NetSuite transaction.

Why is this important?

Previously, unapplied amounts in NetSuite were not reflected in Chargebee Billing, causing reconciliation gaps. This update provides a complete view of customer balances and helps avoid duplicate payment records during sync.

How can you use it?

  1. Sign in to Chargebee Billing site.
  2. Navigate to Apps > NetSuite > Advanced Sync Rules > Sync Excess Payments.
  3. Turn on the Sync Excess Payments toggle. Record the offline payment in only one system and follow a consistent process to avoid reconciliation issues.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Rückdatierte Abrechnung ohne Calendar-Billing-Proration

Abo-Änderungen können nun über die aktuelle Laufzeit hinaus rückdatiert werden, auch wenn die Calendar-Billing-Proration deaktiviert ist, wobei bestehende Rechnungen gutgeschrieben und eine neue Rechnung mit dem vollen Betrag der ersten Periode erstellt wird.

You can now backdate subscription changes beyond the current term with calendar billing proration disabled. When you make such corrections, Chargebee Billing reverts existing invoices as credits and applies them to a newly generated invoice that reflects the correct full amount for the period, without prorating the first term.

Why is this important?

In scenarios where billing dates change or pricing corrections are applied retrospectively, proration can lead to inaccurate charges for the initial period. This enhancement ensures that the first billing period reflects the full intended amount, helping you avoid undercharging and maintain consistency in fixed monthly pricing models.

How can you use it?

When you need to correct subscription pricing from an earlier date, backdate the change beyond the current term with calendar billing proration disabled. Chargebee Billing will automatically credit previous invoices and generate a revised invoice with the correct full-period charge, ensuring accurate billing without partial calculations.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Anwendbare Addons in Abos mit mehreren Plänen verwalten

Beim Erstellen und Aktualisieren von Abonnements mit mehreren Plänen berücksichtigt Chargebee Billing nun automatisch auf Planebene konfigurierte verpflichtende Addons für jeden Plan.

You can now apply applicable addons and charges across [subscriptions with multiple plans](https://www.chargebee.com/docs/billing/2.0/subscriptions/multi-plans-subscriptions) during creation and updates.

Why is this important?

In multi-plan subscriptions, ensuring that mandatory addons are always included can be challenging, especially during updates. This enhancement helps you maintain pricing accuracy and avoid missed charges by automatically enforcing addon requirements, reducing the risk of incomplete billing.

How can you use it?

Configure mandatory addons at the plan level as needed. When creating or updating a [multi-plan subscription](https://www.chargebee.com/docs/billing/2.0/subscriptions/multi-plans-subscriptions#creating-a-multi-plan-subscription), Chargebee Billing will automatically include the required addons for each plan.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Kundendaten als Merge Tags in Rechnungs-PDFs

Im Invoice Template Builder lassen sich jetzt kundenbezogene Merge Tags wie Vorname, Nachname, E-Mail-Adresse und Firmenname in Rechnungs-PDFs einfügen.

You can now use customer-related merge tags such as first name, last name, email address, and company name directly within the invoice template builder. These fields are available in the merge tag library and can be added to your invoice PDFs wherever needed, alongside the existing subscription and customer ID fields.

Why is this important?

When working with account hierarchies, relying only on IDs can make invoices harder to interpret. With access to customer attributes, you can present clearer and more meaningful information on invoices, making it easier to identify the associated customer at a glance and improving overall readability.

How can you use it?

Navigate to the template builder and select the required customer fields from the merge tag library under the subscription customer section. Insert these tags into your invoice template wherever needed, such as headers or billing sections, to display relevant customer details in the generated PDF.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Renewal-Erinnerungen berücksichtigen künftige Ramps

Erinnerungs-E-Mails zur Vertragsverlängerung zeigen nun eine korrekte Subscription-Zusammenfassung, wenn am Verlängerungsdatum eine Ramp geplant ist, ohne dass eine zusätzliche Einrichtung nötig ist.

You can now view an accurate subscription summary in contract renewal reminder emails for the upcoming contract term cycle. Earlier, renewal emails did not account for ramp actions applied on the renewal date, which led to discrepancies in TCV values, amounts, and subscription summaries.

Why accurate renewal visibility matters?

Without ramp support, renewal reminders could present outdated billing information, making it difficult to anticipate revenue changes and communicate expectations accurately. With this enhancement, you now get a clear and reliable view of upcoming contract values, helping you plan renewals and forecast revenue with confidence.

How can you use it?

No additional setup is required. If you have already enabled Send contract renewal reminders in the email notification settings of your Chargebee site, the emails will now display an accurate subscription summary when a ramp is scheduled on the contract renewal date.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Revenue-Recovery-Reports ziehen in die Checkout-Einstellungen um

Die Revenue-Recovery-Reports für Abandoned und Recovered Carts liegen jetzt im Reports-Tab der Checkout-Einstellungen statt auf der Classic-Reports-Seite, bei unveränderten Daten und unverändertem Verhalten.

In Chargebee Billing, revenue recovery reports have now moved from the Classic Reports index page to the Reports tab under Checkout settings. The report data and behavior remain unchanged.

Why is this important?

This keeps revenue recovery (abandoned and recovered cart) insights available from a more relevant location in your Chargebee Billing site.

How can you use it?

To access the reports:

  1. Log in to Chargebee Billing.
  2. Navigate to Settings > Configure Chargebee > Checkout & Self-Serve Portal.
  3. Under the Advanced Settings section, enable the Track abandoned carts toggle.
  4. Select the Reports tab that now appears.
  5. Select the Abandoned Carts or Recovered Carts reports to view them.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Zugriffskontrolle und mehr Zeichen für Quote Notes in Chargebee CPQ

In Version 1.76 lassen sich für das Feld Quote Notes in Chargebee CPQ Lese- oder Schreibrechte für Benutzergruppen vergeben, und das Feld unterstützt nun bis zu 10.000 Zeichen bei allen Quote-Typen.

You can now control access to the Quote Notes field in Chargebee CPQ by assigning read or write permissions to specific user groups, and the field now supports up to 10,000 characters across all quote types.

Why is this important?

Quote Notes often carry legal terms or standardized content that not every user should be able to edit. With access control, you can prevent unauthorized edits and reduce compliance risk.

How can you use it?

  1. In Salesforce, navigate to Chargebee Settings > Advanced Actions > Access Control.
  2. In the Access Control UI, locate the Quote Notes field.
  3. Assign Read-Only or Write access to the relevant user groups.
  4. Optionally, if users have Write access, use Prefill Field Values to pre-populate Quote Notes from an Opportunity field, allowing those users to modify the pre-populated content.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Steuer im Next Billing Amount konfigurierbar (Version 1.76)

Über den neuen Schalter Exclude Tax From Next Billing Estimate in den Subscription Sync Rules können Sie festlegen, dass der nach Salesforce synchronisierte Next Billing Amount ohne Steuer übertragen wird.

You can now control whether the Next Billing Amount synced from Chargebee Billing to Salesforce includes tax. By default, the Exclude Tax From Next Billing Estimate toggle is disabled, so the synced amount includes tax. Enable this toggle in Subscription Sync Rules to sync a tax-exclusive amount when it better fits your workflow.

Why is this important?

When tax is included in the Next Billing Amount, Chargebee calls your tax provider, such as Avalara, during every subscription sync to calculate the tax component. For high-volume sites, this can push you toward API rate limits and increase your tax provider costs. Excluding tax from the synced estimate removes those calls, reduces sync overhead, and keeps your billing data current in Salesforce without the added API usage.

How can you use it?

  1. In Salesforce, navigate to Chargebee Settings > Sync Rules > Subscriptions.
  2. Locate the Exclude Tax From Next Billing Estimate toggle.
  3. Enable it to sync tax-exclusive amounts, or leave it off to continue syncing tax-inclusive estimates.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Vollständige Ramp-Synchronisierung nach Salesforce (Version 1.76)

Mit dem neuen Feld Enable Ramp Sync From CB to SF werden Ramps eigenständig und vollständig inklusive Line Items, Coupons und Discounts von Chargebee Billing nach Salesforce synchronisiert, unterstützt für Flat Fee und Per Unit; zudem wurden die Contract-Type-Bezeichnungen in Salesforce überarbeitet.

You can now enable full subscription ramp sync from Chargebee Billing to Salesforce using the new Enable Ramp Sync From CB to SF field on the CB Site and CB Business Entity objects. When enabled, ramps sync independently and deliver the complete ramp state at execution, including all line items, coupons, and discounts. This is supported for Flat Fee and Per Unit pricing models. Contract Type labels in Salesforce have also been updated for clearer terminology.

Why is this important?

Partial ramp syncs leave data gaps between Chargebee and Salesforce, making reporting unreliable and renewals harder to plan. With full ramp sync, your Salesforce records reflect the complete subscription state at each ramp execution, giving RevOps and Finance teams an accurate view of upcoming changes. Independent ramp sync also reduces the risk of sync failures, and a dedicated entry in Sync Health makes it easier to track and troubleshoot ramp sync events.

How can you use it?

  • In Salesforce, navigate to Chargebee Settings and run the Picklist Migrations action. This is a required prerequisite before enabling ramp sync.
  • Open the CB Site or CB Business Entity object. If either object isn't visible, create a tab for it in Salesforce first.
  • Enable the Enable Ramp Sync From CB to SF field. …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Fix: E-Mail-Vorlage und Absender in CPQ-Quotes

Quote-E-Mails in Chargebee CPQ übernehmen nun die konfigurierten Betreffzeilen und Absenderadressen statt generischer Betreffs und der Standard-Billing-Adresse.

We've fixed an issue in Chargebee CPQ quotes where quote emails did not reflect configured subject lines and sender addresses. This resulted in generic subjects and emails being sent from the default billing address instead of the actual sender, with limited "From" options available. With this fix, quote emails now reflect your configured subject and sender settings for improved quote communication

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Fix: Statusfehler bei One-Time-Quotes in CPQ

Der Statuswechsel eines One-Time-Quotes in Chargebee CPQ von Declined auf Proposed führt nicht mehr zu einem Fehler.

Fixed an issue where updating a one-time quote status in Chargebee CPQ from Declined to Proposed resulted in an error. This occurred because a validation intended to check for multiple open quotes on a subscription was also triggered for one-time quotes, which do not have an associated subscription. You can now update one-time quote statuses without encountering this error.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Fix: Amendment Quotes für zukünftige Subscriptions

Amendment Quotes in Chargebee CPQ lassen sich auch für bestimmte zukünftige Subscriptions wieder erstellen, ohne den Fehler „No recurring items are present in the quote.“

Fixed an issue in Chargebee CPQ where creating an amendment quote could fail with the error, "No recurring items are present in the quote." This occurred for certain future subscriptions created through a CPQ quote-to-subscription conversion, with a later start date change and a renewal before the amendment. You can now create amendment quotes for these subscriptions as expected, helping you manage subscription changes without manual workarounds.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Fix: Zero-Payable-Fehler bei Amendment Quotes

Beim Wechsel von einem Trial-Plan auf einen bezahlten Plan lassen sich Amendment Quotes nun auch bei aktivierter Hide-Zero-Dollar-Einstellung ohne Zero-Payable-Fehler erstellen.

You can now create amendment quotes when updating from a trial plan to a paid plan without encountering a zero payable amount error. Earlier, when the hide zero dollar setting was enabled, the system incorrectly treated the total as zero and blocked quote creation. This fix ensures the payable amount reflects the updated plan, so you can complete quote creation without interruption.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Zuverlässigere Plan-Beschreibungen bei Multi-Plan-Subscriptions

Beim Erzeugen von Plan-Beschreibungen im Multi-Plan-Subscriptions-Flow treten keine Fehler mehr auf, da die Subscription-Daten nun vor dem Zugriff validiert werden.

You will no longer encounter errors in the multi-plan subscriptions flow when generating plan descriptions. With this fix, the system handles multi-plan subscription flow reliably by validating subscription data before accessing it.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Fix: Subscriptions nach Bulk-Import öffnen

Subscriptions, deren importierte IDs Sonderzeichen enthalten, lassen sich nach einem Bulk-Import wieder ohne Fehler öffnen.

After performing bulk subscription imports, where imported subscription IDs contained special characters, opening the subscription sometimes displayed an error instead of the subscription details page. This issue has been fixed.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Klarere Behandlung von Upgrades kurz vor der Verlängerung

Upgrades kurz vor dem Renewal berücksichtigen nun die Verlängerungsgrenze und die Pause-Planung, sodass Upgrade-Rechnungen nicht mehr gleichzeitig Proration und Renewal-Gebühren enthalten.

Previously, upgrades performed shortly before renewal could trigger both proration and renewal charges in the same invoice, as the system started the new billing term immediately. With this update, the system respects the renewal boundary and pause scheduling, ensuring that upgrade invoices reflect only the intended charges.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Zuverlässigere Übertragung von Migration zu Live-Site

Null-Werte in der Rechnungsnummerierung werden bei der Übertragung zur Live-Site korrekt behandelt, sodass Validierungsfehler, interne Serverfehler und hängende Transfer-Jobs vermieden werden.

Previously, null values in invoice numbering were incorrectly processed, leading to validation failures, internal server errors, and stuck transfer jobs. With this fix, null values are handled correctly, and validation checks are more robust, preventing unexpected failures during the transfer process.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Fix: Amendment- und Renewal-Flows in Chargebee CPQ (Version 1.76)

Behoben wurden das Nichtladen der Amendment- und Renewal-Flows nach dem Upgrade auf Version 1.75.4 sowie fehlgeschlagene Ramp-Syncs von Salesforce zu Chargebee Billing bei Subscription-IDs mit Sonderzeichen.

After upgrading to version 1.75.4 of the Chargebee CPQ package for Salesforce, amendment and renewal flows were not loading due to a UI component issue. Separately, ramp syncs from Salesforce to Chargebee Billing failed when subscription IDs contained special characters. Both issues are now resolved.

Originalquelle(öffnet in neuem Tab)Problem melden