The subscription is amended to push the contract's start and end dates out by one month. The amendment adds one month to the contract's end but doesn't truncate one month from the beginning of the contract. As a result, the contract term, TCV (Sales), or both are changed after the amendment. The billing periods after the amendment do not align with the existing periods, disrupting the billing schedule records (BSRs).

A subscription, with a quarterly billing frequency is sold for one year with a TCV (Sales) of USD 96,000.00. The contract start date is 01-July-2024 and the end date is 30-June-2025. The selling term is four (because the billing frequency is quarterly) and the net price is USD 24,000.00.

You want to move out (delay) the contract term by one month.

The subscription is amended to push the start and end dates by one month. Due to existing CPQ behavior, the start date remains 01-July-2024 (instead of 01-August-2024 ), however, the contract's end date is extended to 31-July-2025, resulting in a change in the contrac's term. Although TCV (Sales) has increased from USD 96,000.00 to USD 104,000.00, it remains unchanged because the net price for the period remains unaltered. The date range is changed so that the new periods do not overlap with the existing ones. This disrupts the existing BSRs and new BSRs are created for the amended period. It is illustrated in the following diagram:

Here, the billing application receives the payload for the amendment from an order or asset line item generated in Conga CPQ. When the application processes this line item per the request, it uses the value in the Effective Start Date field on the order line item (OLI) as the start date (null here) indicating that there is no change in the start date. As a result, the billing header fields are updated as follows:

The BSRs are:

Setting "Superseding the Schedules during Asset Management" to Always Supersede

Setting "Superseding the Schedules during Asset Management" to Minimize

BSDs are: