Download PDF
Download page Advancing the Term of One-Time Products.
Advancing the Term of One-Time Products
When you request to advance the term of a one-time product to the Change endpoint, Billing modifies the fields on the activated billing header per the change request or displays an error message.
Prerequisites
- The Superseding the Schedules during Asset Management setting is set to Always Supersede or Minimize.
- The value in the Billable Amount for Current Order Line Item field is strictly USD 0.00.
The selling term remains the same as the previous sale.
Use Case: Advancing the Term
Initiating the billing for a one-time product creates a single billing schedule record (BSR) and billing schedule detail (BSD). When the contract date is advanced by a fixed period (by a quarter) the new billing period never aligns with the original schedule. For more details, refer to Billing Records for Change in Term.
Contact your admin to make this functionality available in your application so that clicking a button calls the billing services API.
When billing is initiated for a product or service subject to the advancement of the term:
- As the new period does not align with the original schedule, the application creates a new BSR and BSD for the latest period, Pending Billing status. It cancels or refunds the original BSR and BSD per their invoice status.
- The fee amount for a period is computed per the full or partial term of the BSR.
- For the periods that are not a part of the contract after the change, the application cancels the billing schedules depending on their invoice status and the setting, Superseding the Schedules during Asset Management set to Always Supersede or Minimize. For more details, refer to Effect of the Custom Setting on the Creation of Refund Schedules.
- On the billing header (BH),
- The values in the Billing Start Date, Billing End Date, and Billable Amount from the Current Order Line fields are updated to the corresponding values from the current OLI or ALI fields.
- The values in the Selling Term and TCV (Sales) fields remain unchanged.
For example, a new sale for a one-time service is initiated with a TCV (Sales) of USD 1,200.00. The billing frequency is yearly. The start date is 01-July-2024 and the end date is 30-June-2025. Initiating the billing creates a billing header and one BSR with a fee of USD 1,200.00.
New Sale
For a new sale, the billing header has the following data:
BH ID | Current OLI | Parent OLI | ALI | Billing Start Date | Billing End Date | TCV (Sales) | Billable Amount for Current OLI | Total Invoiced Amount | Pending Invoice Amount | Status |
---|---|---|---|---|---|---|---|---|---|---|
BH-1 | OLI-1 | OLI-1 | ALI-1 | 01-July-2024 | 30-June-2025 | USD 1,200.00 | USD 1,200.00 | USD 0.00 | USD 1,200.00 | Active |
Only one BSR is generated as shown below:
BSR ID | BSD ID | Record Type | Category | Period Start Date | Period End Date | Actual Fee Amount | Invoice Status |
---|---|---|---|---|---|---|---|
BSR-1 | BSD-1 | Regular | Fee | 01-July-2024 | 30-June-2025 | USD 1,200.00 | Pending Billing |
After Change
Suppose the term is advanced by a quarter. The billing start date is 01-May-2024 and the billing end date is 30-April-2025. You sent this term change to the existing billing header using a new OLI. When the OLI is activated and initiated for billing, the billing engine applies the term changes to the header and adjusts the schedules as shown below.
BH ID | Current OLI | Parent OLI | ALI | Billing Start Date | Billing End Date | TCV (Sales) | Billable Amount for Current OLI | Total Invoiced Amount | Pending Invoice Amount | Status |
---|---|---|---|---|---|---|---|---|---|---|
BH-1 | OLI-110 | OLI-1 | ALI-1 | 01-May-2024 | 30-April-2025 | USD 1,200.00 | USD 0.00 | USD 0.00 | USD 1,200.00 | Active |
Scenario 1: Setting "Superseding the Schedules during Asset Management" to Minimize.
The application creates a new BSR for the latest period in Pending Billing status with a fee of USD 1,200.00. The existing BSR, BSR-1 is canceled. Counter-BSD, BSD-1.a is created to offset the positive fee amount of BSD-1.
The BSRs are:
BSR ID | Record Type | Category | Period Start Date | Period End Date | Actual Fee Amount | Invoice Status | Remarks |
---|---|---|---|---|---|---|---|
BSR-2 | Regular | Fee | 01-May-2024 | 30-April-2025 | USD 1,200.00 | Pending Billing | New BSR introduced for the advanced period |
BSR-1 | Regular | Fee | 01-July-2024 | 30-June-2025 | USD 0.00 | Canceled | The fee is USD 0.00 due to the roll-up of the sum of BSD-1 and its counter-BSD, BSD-1.a. |
The BSDs are:
BSD ID | BSR ID | Record Type | Category | Period Start Date | Period End Date | Actual Fee Amount | Derived Invoice Status | Remarks |
---|---|---|---|---|---|---|---|---|
BSD-2 | BSR-2 | Regular | Fee | 01-May-2024 | 30-April-2025 | USD 1,200.00 | Pending | New BSD introduced for the advanced period |
BSD-1 | BSR-1 | Regular | Fee | 01-July-2024 | 30-June-2025 | USD 1,200.00 | Canceled | |
BSD-1.a | Regular | Fee | 01-July-2024 | 30-June-2025 | (USD 1,200.00) | Canceled | Counter-BSD for the canceled BSD-1, BSD-1.a can be used to offset the revenue forecast from the previous BSD-1. |
Scenario 2: Setting "Superseding the Schedules during Asset Management" to Always Supersede.
The application creates a new BSR for the latest period in Pending Billing status with a fee of USD 1,200.00. The existing BSR, BSR-1 is canceled. No counter BSD is created.
The BSRs are:
BSR ID | BSD ID | Record Type | Category | Period Start Date | Period End Date | Actual Fee Amount | Invoice Status | Remarks |
---|---|---|---|---|---|---|---|---|
BSR-2 | BSD-2 | Regular | Fee | 01-May-2024 | 30-April-2025 | USD 1,200.00 | Pending Billing | New BSR introduced for the advanced period |
BSR-1 | BSD-1 | Regular | Fee | 01-July-2024 | 30-June-2025 | USD 1,200.00 | Canceled |