Custom Plan Billing Amount Criterion – Bill the Uninvoiced and Unbilled

Introduced a new parameter called Bill the Uninvoiced and Unbilled, to the Billing Amount Criterion field in the custom plans. This feature enables the system to calculate and create new installments by determining both pending invoice amounts from previous sales and new amounts from ongoing sales for term-based plans with ABO supporting Full Term, Mid Term, and Mid Period scenarios in plan amendments and billing frequency changes.

For more information, see Switch from Regular Billing to Custom Billing and Use Case: Term Based Custom Plan for Change Operation.

Billing Rule Change Support

Support is added to change the billing rule on an existing subscription. Change in the billing rule during an ongoing contract is considered a disruption because it can have a significant impact on the flow of the revenue of the contract. Any updates to a Billing Rule are forward‑looking and apply only from the next transaction onward, ensuring that existing contracts remain unaffected unless explicitly realigned. When a change in billing rule is initiated (as a part of an ABO), the existing billing schedule records are superseded and new records are created, irrespective of any global billing setting or configuration.

For more information, see Change in Billing Rule.

Change in Billing Policy/Preference During Subscription Change Operation

Support is added for changing the Billing Preference on existing subscriptions when the new preference differs from the old preference in key billing fields, such as Billing Cycle Start, Billing Day of Month, Calendar Cycle Start, Proration Computation Method, and Prorate When Billing As One Time. Any updates to a Preference are forward‑looking and apply only from the next transaction onward, ensuring that existing contracts remain unaffected unless explicitly realigned. This update applies to non-usage products and aligns the behavior during changes leading to disruption in billing, impacting billing schedule records (BSRs) as per the latest amenments.

When a subscription is amended and key billing fields within the existing preference are updated, the system syncs/does not syncs these changes to the associated assets and subscriptions based on the value of the setting Sync Billing Info During Amendment.

For more information, see Change in Billing Policy/Preference and Use Case: Sync Preference Changes during ABO.

Invoicing APIs

Invoicing is the process of creating and sending an invoice - a legal document that lists products or services provided, along with the amount due for each item, to a customer. The invoice serves as a formal request for payment and includes details like the invoice number, customer name and address, total amount, due date, applicable taxes, discounts, and payment terms.

For More information, see Use Case: Create an Invoice Run Request.

Compliance Rules and Changes in Payment Term

Payment Term records now support compliance rules for Active and Is Default fields, ensuring only one active default term exists at any time. API support is available for creating, editing, retrieving, activating/deactivating, and defaulting Payment Term records, with all changes tracked in user details fields. Deletion of Payment Term records is not permitted from audit point of view.

Change in the payment term during an ongoing contract is considered a disruption because it can have a significant impact on the flow of the revenue of the contract. Any updates to a Payment Term are forward‑looking and apply only from the next transaction onward, ensuring that existing contracts remain unaffected unless explicitly realigned. When a change in payment term is initiated (as a part of an ABO), the existing billing schedule records are superseded and new records are created, irrespective of any global billing setting or configuration.

For more information, see Change in Payment Term and Compliance Requirement for Payment Term.