Folge Chargebee, um die Release Notes in deinen Feed zu holen.
Zur Ressource Unbilled Charges wurde ein Feld für die Business Entity ID ergänzt, damit Kunden in Berichten nicht mehr unter falschen Entities aufgelistet werden.
We have added to the resource to address and resolve the issue where customers were being listed under incorrect entities in reports. This update ensures accurate association of customers with their respective business entities, improving the reliability of reporting data.
Beim Erstellen eines Quotes für einen Jahresplan mit 15 Billing Cycles tritt kein Fehler mehr auf.
Previously, an error occurred when creating a quote for a yearly plan with 15 billing cycles. Our latest update resolves this issue, ensuring an error-free experience when setting up longer-term subscriptions.
Geplante Ramps werden nun erfolgreich ausgeführt, auch wenn beteiligte Item Prices zuvor archiviert wurden; die Funktion Subscription Ramps befindet sich im Early Access.
Previously, if an item price was archived before a scheduled ramp could execute, the ramp would fail. With our latest update, ramps will now successfully execute as planned, even if the involved item prices are archived beforehand. This enhancement guarantees that your pricing strategies are implemented without disruption.
Note: Subscriptions Ramps is in early access. Submit a request to enable this feature.
Tax-Provider-Felder werden nun auch für anteilig berechnete (prorated) Add-ons übergeben, was eine korrekte Besteuerung sicherstellen soll.
We have fine-tuned our system to ensure that tax provider fields are seamlessly passed for prorated add-ons, guaranteeing accurate taxation in every billing cycle.
Das Ändern eines Trial-Abonnements mit Contract Terms nach der Aktivierung führt bei aktiviertem Calendar Billing nicht mehr zu einem Fehler.
Previously, if you had calendar billing enabled and tried to modify a trial subscription with contract terms after activation, you might have encountered an error. Now, we've fixed this issue, ensuring a smoother and more reliable process when editing subscriptions.
Charges, die über die Aktion Add Charge oder die Create-Invoice-API hinzugefügt werden, werden nun im Total Contract Value (TCV) berücksichtigt.
Previously, when you added a charge through the add charge action or used the create invoice API, it did not update the Total Contract Value (TCV) as expected. With this update, the TCV will now accurately reflect all your charges, ensuring that your financial data remains consistent and reliable.
Ein Fehler in der List Customers API, der das System unnötig belastete, wurde behoben, sodass der Abruf von Kundendaten flüssiger und mit geringerer Latenz läuft.
We have squashed a bug affecting the List Customers API that was causing unnecessary strain on our system. With this fix, you can expect smoother performance and reduced latency when retrieving customer data.
Mit Variant Pricing (Early Access) lassen sich im Product Catalog unterschiedliche Preise für Varianten eines Produkts, etwa nach Region, Partner oder Version, in einem einzigen Item (plan/addon/charge) verwalten.
We are thrilled to introduce the Variant Pricing feature in Chargebee Billing. This powerful feature empowers businesses to effortlessly manage different prices for multiple variations of a single product or service, accommodating factors such as geography, partners, versions, and more, directly within the Product Catalog. By consolidating these variations into a unified item (plan/addon/charge), Variant Pricing streamlines your product catalog, fostering a more organized, scalable, and growth-oriented approach.
Note: Variant Pricing feature is in early access*. Submit a request to enable this feature.
In der Option Redirect to URL der Pricing Table können Plan- und Price-IDs jetzt über Variablen dynamisch in die Redirect-URLs eingefügt werden.
You can now dynamically add plan and price IDs to your pricing page redirect URLs using variables in the Redirect to URL option. Create more relevant experiences, guiding customers to targeted offers or product details without additional steps.
Die Move a subscription API (Early Access) ermöglicht es, bestimmte Subscriptions von einem Kunden auf einen anderen zu verschieben, was bisher manuell erfolgen musste.
You can now effortlessly move specified subscriptions from one customer to another. This innovative feature responds to the need for flexibility in handling subscriptions due to organizational changes on your customer's end. Until now, moving subscriptions between customer accounts required manual intervention, a process both time-consuming and prone to errors. This update not only simplifies subscription management but also empowers your customer support team to provide faster, more efficient service.
Note: Move a subscription API is in early access*. Submit a request to enable this feature.
Der Revenue backlog report ist jetzt in den kontinuierlichen Exporten und den Monatsend-Exporten enthalten und zeigt den gesamten ausstehenden Umsatz auf Sales-Order-Ebene.
The revenue backlog report is now included in both continuous and month-end exports, providing valuable insights on total outstanding revenue at the sales order level.
In der Product-Catalog-Oberfläche werden nun zusätzliche Events wie Erstellen, Ändern und Löschen von zugehörigen Items sowie von differential prices direkt bei Plan, Addon und Charge angezeigt.
We've identified a critical enhancement needed to bolster your monitoring and verification processes: the visibility of key events directly within the product catalog interface. Previously, you faced challenges in confirming if events had triggered correctly due to some missing event types. Our latest update has added crucial Product Catalog events, such as creations, updates, and deletions of attached items(plan/addon/charge) and differential prices, right on the Plan/Addon/[Charge](https://www.chargebee.com/docs/2.0/charges.html#defining-price-points-for-a-charge "https://www.chargebe…
In Chargebee Retention erscheinen jetzt Hinweise beim Verlassen von Seiten, damit Änderungen am Field Mapping nicht ungespeichert verloren gehen.
In our latest update, we're excited to introduce enhancements to field mapping notifications within Chargebee Retention. Now, users will receive notifications when navigating away from pages within their retention application, ensuring that any changes made to their field mapping are saved. With clearer notifications, managing your data has never been easier.
Slack- und E-Mail-Benachrichtigungen zeigen jetzt die für Endkunden sichtbaren Kündigungsgründe statt der internen an.
Introducing an upgrade to our notification system for Slack and email: now featuring end subscriber-facing cancellation reasons instead of internal ones. This enhancement brings clarity and transparency to the churn process, allowing customers to gain deeper insights into why subscribers are leaving. Not only does this empower users to understand churn better, but it also fosters organizational alignment, enabling teams to tackle churn more effectively.
Lieferungen lassen sich nun über eindeutige Product Codes statt Sales-Order-Item-IDs erfassen, wobei RevRec bei mehreren Items per FIFO zuordnet, und eine neue Einstellung Unit Rollover steuert, ob Einheiten über das Service-Ende hinaus verbraucht werden dürfen.
RevRec unterstützt Custom Fields für Apple- und Google-Mobile-Subscriptions und kann bei Google-Subscriptions Umsatz in der Käuferwährung erfassen und Steuern je nach Transaktionstyp automatisch abziehen.
Custom Fields: RevRec now supports custom fields for both Apple and Google mobile subscriptions, allowing you to capture additional data at the customer, product, and subscription (sales order) levels. This empowers more granular reporting and analytics.
Google Subscriptions: RevRec offers enhanced capabilities for Google mobile subscriptions. It now allows configuration to recognize revenue in the buyer's currency and automatically deducts tax based on the transaction type, ensuring accurate revenue reporting aligned with international sales.
RevRec unterstützt nun den Wechsel der Kunden-Entity bei Multi-Entity-Händlern, wobei bisheriger Umsatz bei der ursprünglichen Entity bleibt und Kunden mit laufenden Verträgen die Entity nur zur Vertragsverlängerung wechseln können.
RevRec now facilitates customer entity changes under multi-entity Chargebee merchants. This simplifies customer management within complex organizational structures. Importantly, revenue associated with the customer's original entity remains attached to that entity after the change. The new entity will only recognize revenue for new sales orders initiated after the switch. It's important to note that customers with ongoing subscriptions (governed by contract terms) can only change entities at the time of contract renewal, not during the active subscription period.
Wer eine Ramp einfügt, die vor einer bestehenden Ramp den Abrechnungszeitraum einer Subscription ändert, erhält nun eine Fehlermeldung und muss nachfolgende Ramps entfernen und die Änderungen erneut anwenden.
If you attempt to insert a ramp that modifies the billing period of a subscription before an existing ramp, Chargebee will now proactively alert you with an error message. For an effortless adjustment, remove any subsequent ramps and reapply your changes.
Note: Subscription Ramps is in early access*. Submit a request to enable this feature.
Händler mit Anrok-Integration können Tax Calculations in Chargebee jetzt für jede unterstützte Region konfigurieren.
We are excited to announce that with this release, merchants who have integrated with Anrok can now configure Tax Calculations for any supported region in Chargebee.
Ein Fehler wurde behoben, bei dem ein Checkbox-Custom-Field beim Bearbeiten eines Coupons und Festlegen der Pläne von 'True' auf 'False' sprang.
We've addressed and resolved a subtle yet significant bug affecting custom fields within coupons. Previously, when editing a coupon and specifying applicable plans, a checkbox custom field would unexpectedly switch from 'True' to 'False'. This required you to revisit the coupon edit page to reset the checkbox to its correct value. This issue is now resolved.