SuiteBilling: Charge Commit On Usage Preference and Commit Plus Overage Line Behavior

What changed

A new line-level checkbox, Charge Commit On Usage, is available on subscription lines in SuiteBilling. It changes when the system generates charges for minimum amounts (usage services) and commitment quantities (commit plus overage services).

Usage services

• When the box is checked, the unused portion of the minimum amount defined on the price plan header is billed at the end of the pricing period rather than on the first usage transaction.
• When the box is unchecked (default/legacy behavior), the full minimum amount is charged on the first usage record.
• At least one usage record must exist for the system to bill the minimum on that line.

Commit Plus Overage (C+O) services

• When checked and billing mode is in arrears, the commitment quantity is charged at the end of the pricing period.
• When checked and billing mode is not in arrears, usage up to the commitment quantity is invoiced according to the billing account's invoice frequency.
• Commitment credits from the C+O line can now be shared across multiple usage service lines. Overage is billed at each individual usage line's own price plan rate.
• The overage price plan and frequency fields on a usage service line are ignored when that usage line is tied to a C+O line — overage is governed by the C+O line instead.
• Breakage and overage revenue are tracked against the C+O line, not the individual usage lines.
• Commitments reset at the end of each pricing period.

Grouping

The C+O model supports subscriptions grouped by customer, currency, and subsidiary.

Technical details

Oracle's documentation does not specify the internal field ID for the new checkbox. Based on naming conventions it is likely chargecommitonusage or similar on the subscription line sublist, but this should be confirmed via the Records Browser or by inspecting the subscription record in a sandbox. The column appears in the subscription line sublist under Charge Commit On Usage.

No new SuiteScript modules or REST endpoints are mentioned. However, any SuiteScript or integration that programmatically creates or updates subscription lines, usage records, or charge records should account for this preference:

• Scripts that set line values on subscription records may need to set or read this new field.
• Saved searches or N/query workloads that report on charges, breakage, or overage revenue should verify whether the charge source is the C+O line or an individual usage line, since revenue attribution has shifted.
• Workflows or scheduled scripts that trigger on the first usage record to reconcile minimum-amount charges will behave differently when this preference is enabled — the minimum charge now appears at period end.

What to do

1. Identify the field ID. In a sandbox, navigate to a subscription record, enable the Charge Commit On Usage column, and use the Records Browser or record.getSublistFields to confirm the internal ID.
2. Audit existing scripts. Search your SuiteScript codebase for references to subscription line sublists, usage records, and charge generation. Determine whether any logic assumes the minimum amount or commitment is billed on the first usage event.
3. Review saved searches and analytics. If you report on breakage or overage revenue at the usage-line level, update queries to account for revenue now tracked on the C+O line.
4. Test in sandbox. Create a subscription with shared commitment credits across multiple usage lines. Verify that overage charges use the correct per-line rate and that the commitment resets at period boundaries.
5. Coordinate with billing teams. This preference changes invoice timing — billing and finance stakeholders should review the impact on cash-flow reporting and revenue recognition schedules.