How SaaS companies set up minimum commits in billing

A minimum commit is a contractual floor: the customer agrees to spend at least a set amount over a period, usage is rated and drawn down against that amount, and if actual spend falls short, a true-up invoice bills the difference. Setting it up well means storing the commit on the contract (amount, period, ramp, true-up timing), rating usage in the same system, and reporting ARR on the committed amount while forecasting the usage on top. A quote-to-cash platform that handles commits, usage rating, ramped terms and forecasting in one place avoids rebuilding this in spreadsheets every quarter.

Commit models you will meet

Not every “commit” is billed the same way. Before configuring anything, pin down which of these the contract describes:

• Prepaid commit (drawdown). The customer pays the commit upfront or in installments. Usage draws down the prepaid balance. Once it is used up, overage applies.
• Postpaid minimum (true-up). The customer pays for usage as it happens. At the end of the commit period, if total spend is below the minimum, the system bills the shortfall.
• Minimum per period. The floor applies monthly or quarterly rather than over the whole term. Each period is trued up on its own, with or without carry-over of unused amounts.
• Ramped commit. The commit grows year over year in a multi-year deal ($100,000 in year 1, $150,000 in year 2, $200,000 in year 3), and each year has its own floor.

The first model is close to prepaid credits, covered in how to combine prepaid credits and overages on one invoice. This guide focuses on the true-up mechanics and how commits interact with ramps and forecasting.

A worked example

A made-up but representative contract, for illustration only:

• Annual minimum commit of $60,000, billed quarterly in arrears on actual usage.
• Usage priced at $0.04 per processed transaction.
• True-up at the end of the contract year if annual spend is below $60,000.
• Year 2 commit ramps to $90,000.

Year 1 usage by quarter:

Quarter	Transactions	Usage billed
Q1	250,000	$10,000
Q2	300,000	$12,000
Q3	350,000	$14,000
Q4	400,000	$16,000
Year total	1,300,000	$52,000

The customer spent $52,000 against a $60,000 floor. The Q4 invoice (or a separate true-up invoice) adds a shortfall line of $8,000. Total billed for year 1 is exactly $60,000.

For reporting, contracted ARR in year 1 is $60,000, the committed floor. The usage trend (+$2,000 per quarter) suggests year 2 usage of around $80,000 to $90,000, which is close to the new $90,000 floor. Your forecast should therefore carry two numbers for year 2: $90,000 committed ARR and an expected usage figure, with any amount above the floor shown as forecast upside, not as contracted revenue.

If instead the contract had a quarterly minimum of $15,000, Q1 ($10,000) and Q2 ($12,000) would each trigger their own true-up ($5,000 and $3,000), and Q3 and Q4 would not. Same annual total of usage, different invoices and cash timing. This is why the true-up period has to be a field on the contract, not a convention someone remembers.

Forecasting ARR with commit plus usage

Commits make usage businesses easier to forecast, but only if the two parts are kept apart in reporting:

• Committed ARR is the annualized floor. It is contractual and belongs in the ARR you report to the board.
• Usage above commit is variable. Most finance teams forecast it from trailing usage and show it separately, sometimes as “run-rate revenue.”
• Ramp steps must be scheduled, so that the committed ARR moves on the ramp date without a manual change.
• True-up risk is the gap between usage run-rate and the floor. A customer trending well below the commit is a renewal risk even though the revenue is billed.

A platform that forecasts from the contract and the usage history in the same data model gives you all four numbers without exporting to a spreadsheet.

Common pitfalls

Commit stored in the CRM only. If the minimum lives on the opportunity and not on the billing contract, the true-up depends on someone remembering to raise an invoice. It often does not happen.

Shortfall billed but not explained. A true-up line with no reference to the commit and the usage total generates disputes. The invoice should show the floor, the actual spend and the difference.

Ramp steps entered as new contracts. Re-creating the contract each year breaks ARR history and makes the year 2 increase look like expansion instead of a contracted ramp.

Carry-over left undefined. Can unused commit roll into the next period? Can overspend in Q4 offset a shortfall in Q1? These rules change the amounts billed, so they need to be in the contract terms and in the system.

Usage that arrives late. If usage for the last week of the period is ingested after the true-up runs, the customer is billed a shortfall they did not owe. Define a cut-off and a correction process.

What to ask a vendor

1. Can a contract hold an annual and a per-period minimum, with the true-up period chosen per deal?
2. Is the true-up calculated and invoiced automatically, with floor, actual and shortfall on the invoice?
3. Can the commit ramp year over year inside one contract?
4. Are carry-over rules (unused commit, overspend offset) configurable?
5. Does reporting split committed ARR from usage above commit?
6. Does the forecast use both the contract schedule and the usage trend?
7. How is the true-up re-run if late usage arrives?

Which quote-to-cash platforms document it

The table lists the platforms that document both prepaid credits (the drawdown side of a commit) and ramped, multi-year deals, in score order. 23 of the 44 platforms we score document both. On the other two capabilities this guide relies on, 42 document usage rating and 27 document forecasting.

To compare the platforms on each capability alone, see best quote-to-cash software for prepaid credits and best quote-to-cash software for ramped and multi-year deals. How each level is assigned is explained on the scoring criteria page.

FAQ

What is a true-up in SaaS billing?

A true-up is the invoice line, or separate invoice, that bills the difference between a customer’s minimum commit and their actual spend at the end of the commit period. If usage meets or exceeds the commit, there is no true-up.

Is a minimum commit counted in ARR?

The committed floor is usually counted in ARR because it is contractual. Usage above the floor is variable and is typically reported and forecast separately, so ARR does not swing with each month’s consumption.

What is the difference between a minimum commit and prepaid credits?

With prepaid credits, the customer pays upfront and draws down a balance. With a postpaid minimum commit, the customer pays for usage as it happens and only pays a shortfall if spend ends below the floor. Some contracts combine both, prepaying part of the commit.