Billing Schedules in SaaS Metric Reporting
Billing Schedules help define how and when customers are billed for SaaS products across various sales activities such as new contracts, renewals, upsells, and more. In the context of SaaS Metric Reporting, billing schedules are critical for recurring revenue tracking and reporting of key metrics.
How Billing Schedules Define Terms
|
Attribute or Condition |
Value or Calculation |
Notes |
|---|---|---|
|
Term Definition |
Start and end dates on the transaction header define the term. |
— |
|
Billing Schedule Present |
Term is defined even if start and end dates have no inherent value. |
Billing schedule drives the term logic. |
|
Transaction Date |
Set as start date. |
— |
|
End Date Calculation |
If In Arrears = True: Transaction Date + (Recurrence Frequency × Repeat Every) – 1 day |
Used for in-arrears billing cycles. |
|
If In Arrears = False: Transaction Date + (Recurrence Frequency × Repeat Every) + 1 month – 1 day |
Used for standard and advanced billing cycles. |
|
|
Recurrence Frequency: Daily |
Calculated by exact number of days. |
— |
|
Recurrence Frequency: Custom |
Calculated using exact dates entered by the customer. |
Allows flexible configuration. |
Related Transaction Types
Sales Orders may be created at the header or line level.
Impact Categories for Transactions
|
Impact Category |
Impact Subcategory |
Scenario/Example |
Notes |
|---|---|---|---|
|
New |
New Contract |
New contract or item |
New transaction or item is added. |
|
Upsell |
Price Increase |
Increase in price (same item, renewal) |
Upsell is recognized. |
|
Upsell |
Quantity Increase |
Increase in quantity (same item, renewal, co-term) |
Upsell is recognized. |
|
Upsell |
Add-on |
New add-on item or line (renewal, co-term) |
Different sales order with same customer and end date may qualify as add-on. |
|
Upsell |
Quantity Increase |
Price and quantity increase at same time |
— |
|
— |
— |
Standalone transaction (no revision history), increase only |
Monthly impact updated, not categorized as upsell. |
|
Downsell |
Quantity Decrease |
Partial quantity returned, credited, and refunded (linked) |
— |
|
Downsell |
Quantity Decrease |
Reduced quantity (same item, renewal) |
— |
|
Downsell |
Price Decrease |
Reduced amount (same item, renewal) |
— |
|
Downsell |
Item Removal |
Item removal (renewal or return, credit, refund) |
— |
|
— |
— |
Standalone transaction (no revision history), decrease only |
Monthly impact updated, not categorized as downsell. |
|
Churn |
Contract Churn |
No renewal transaction (contract ends) |
— |
|
No Impact |
Renewal |
Renewal transaction is created and linked |
Analytical impact record linked to renewal. |
Renewal Processing Rules
Analytical impact is assigned automatically if:
-
The renewal has the same record type, item, customer, and subsidiary.
-
The renewal start date is one day after the original transaction end date.
If not all requirements are met, use the Renewal From list to assign the analytical impact manually. In this list:
-
Only analytical impact records with matching attributes and a renewal start date within 31 days after the original impact’s end date will be listed.
-
Records where the end date is before the renewal's start date will be filtered out.
-
You can adjust the Renewal From field as needed.