Usage-based billing is a way of charging customers for what they actually consume in a billing period – API calls, gigabytes stored, transactions processed, minutes, seats active, units shipped – at the prices and rules set out in the contract. The invoice is not a fixed number agreed in advance. It is calculated after the period closes, from measured usage, and it is only correct if three things line up: the meter, the contract terms and the invoice.
It is also called consumption-based, metered or pay-as-you-go billing. Cloud providers are the best-known example: AWS describes its pricing as a pay-as-you-go approach in which customers pay only for the services they consume, with volume-based discounts as usage grows.
What usage-based billing means in a contract
A usage-based contract does not just say “pay per unit”. It usually combines several terms, and each one changes the invoice:
Billable unit. What exactly is counted: an API call, a GB-month of storage, a processed transaction, an active user. The definition matters. “Successful calls” and “all calls” can produce very different numbers.
Unit rates and tiers. A price per unit, often on a rate card, with lower rates at higher volumes.
Included allowance. A quantity covered by a fixed platform or subscription fee before usage charges start.
Overage rate. The price for each unit above the included allowance or above a contracted tier.
Committed minimum. A floor on spend or volume over a period, sometimes called a minimum purchase commitment. Usage draws the commitment down. If usage falls short, the contract may require a shortfall payment, similar in effect to a take-or-pay contract.
True-up. A periodic reconciliation, often annual, that settles the difference between what was billed and what the contract says was owed.
Billing in arrears. Usage is invoiced after the period ends, because the quantity is not known until then.
Price changes. Escalators or uplifts that change unit rates at renewal or on an anniversary, usually under a price escalation clause.
The mechanics are the same whether you sell the service or buy it.
Meter. A system records each billable event with a timestamp, customer or account ID, and quantity.
Aggregate. At period end, events are totalled per account and per billable unit.
Rate. The totals are priced against the contract: allowance first, then tiers and overage, then any discounts.
Apply commitments. Charges are counted against any committed minimum, and the remaining balance is updated.
Invoice. The rated charges are invoiced in arrears, usually alongside any fixed fees.
True-up. At the end of the commitment period, any shortfall against the minimum, or any agreed adjustment, is settled.
A usage invoice is a calculation; it is only correct when the meter, the contract and the invoice line up.
Large providers publish how this works for their own commitments. Microsoft’s documentation on tracking an Azure consumption commitment (MACC) shows the pattern clearly: the customer commits to a level of spend over a defined period, each invoiced event decrements the commitment and shows the remaining balance, and if the commitment is not met by the end date a shortfall charge is applied for the remaining amount. The exact rules for your own contract will differ, but the shape is common.
Why usage-based billing matters to finance teams
Usage billing moves revenue and cost from a fixed schedule to a calculation. Every calculation has inputs that can go wrong.
For the seller, revenue depends on usage being metered, matched to the right contract and rated at the right tier. Common gaps:
Usage is not metered at all for a new product, region or account.
Usage is metered but not matched to the customer’s contract, so it is priced at a default rate or not billed.
The customer moves into a higher overage tier, but the billing system still applies the included allowance or the lower rate.
A committed minimum is not reached and the shortfall is never invoiced.
An escalator is in the contract but unit rates were never updated.
Each one is a form of contract value leakage: the contract says money is owed, and the invoice does not collect it.
For the buyer, the risk runs the other way. Paying a usage invoice without checking it against the contract can mean paying for units outside the definition, tiers applied in the wrong order, rates that were renegotiated but not updated, or usage that was already covered by a prepayment. That is overbilling, and it is easy to miss because usage invoices change every month by design.
For revenue accounting, usage fees are variable consideration. Under IFRS 15, if the consideration promised in a contract includes a variable amount, the entity must estimate the amount it expects to be entitled to. How that applies to a specific contract is a question for your accountants and auditors.
A worked example of usage-based billing
All figures below are illustrative. They show how the terms interact, not typical prices.
A software company sells an API platform to a customer under this contract:
Platform fee: $5,000 per month, including 1,000,000 API calls.
Overage tier 1: calls 1,000,001 to 3,000,000 at $0.004 per call.
Overage tier 2: calls above 3,000,000 at $0.003 per call.
Tiers are graduated: each rate applies only to the calls inside its band.
Annual committed minimum: $120,000, with any shortfall invoiced at year end.
Usage billed monthly in arrears.
Month 1: correct invoice. The customer makes 3,600,000 calls.
Line
Calculation
Amount
Platform fee (includes 1,000,000 calls)
fixed
$5,000
Tier 1 overage
2,000,000 x $0.004
$8,000
Tier 2 overage
600,000 x $0.003
$1,800
Total due
$14,800
Where it goes wrong on the seller side. The meter for one region was not connected to the billing system, so 400,000 calls were missing. The invoice used 3,200,000 calls: $5,000 + $8,000 + (200,000 x $0.003 = $600) = $13,600. The customer was under-billed by $1,200 that month. Nobody noticed, because $13,600 looked like a normal month.
Where it goes wrong on the buyer side. Suppose instead the billing system was set up with volume tiers, where every overage call is priced at the rate of the highest tier reached. That would give 2,600,000 x $0.003 = $7,800 of overage, against $9,800 under graduated tiers. Which number is right depends entirely on the contract wording. If the contract says graduated, the seller under-billed by $2,000. If it says volume, a buyer seeing $9,800 was overbilled by $2,000. The only way to know is to read the clause.
Year end: the minimum. Suppose total invoiced charges for the year come to $96,000 against the $120,000 commitment. The contract says the $24,000 shortfall is invoiced at year end. If no one tracks the drawdown, that invoice is never raised. On the buyer side, the same $24,000 should be expected and accrued, not discovered in the last week of the year.
Illustrative: the same usage can produce different invoices, and only the contract wording says which is right.
Usage-based billing vs. related pricing terms
Usage-based billing vs. subscription or flat-fee billing. A subscription charges a fixed amount per period regardless of use. Usage billing charges for measured consumption. Many contracts are hybrid: a fixed platform fee with an included allowance, plus usage charges above it. The fixed part is predictable. The usage part needs metering and reconciliation every period.
Usage-based billing vs. a true-up. Usage billing is the ongoing, period-by-period charge. A true-up is the settlement event that reconciles actual usage or entitlement against what was billed or committed, often once a year. In software licensing, a software license true-up charges for extra seats or units used above the license entitlement, while a true-down reduces the count where the contract allows it.
Usage-based billing vs. a committed minimum. The minimum is the floor. Usage billing is how spend accumulates toward it. A contract can have usage billing without a minimum, but when both exist they must be tracked together.
Usage-based billing vs. annual contract value. Annual contract value is usually based on committed, recurring amounts. Usage above the commitment is variable and may or may not be counted, depending on how your company defines the metric.
How to track and reconcile usage-based billing
Usage reconciliation is a specific kind of invoice reconciliation: you compare three records instead of two.
Extract the commercial terms from the signed contract and every amendment. Billable unit definition, allowance, tier bands and rates, graduated or volume tiers, minimum and period, shortfall terms, true-up timing, escalators and effective dates. Amendments often change rates mid-term.
Get the usage data at the right grain. Per account, per billable unit, per period. Check that every product, region and account in the contract is actually being metered.
Re-rate the usage independently. Apply the contract terms to the usage totals and compare the result with the invoice line by line. Differences point to the wrong tier, a missing allowance, a stale rate or missing usage.
Track the commitment balance. Keep a running drawdown against any minimum, with the end date and any interim milestones. Flag the expected shortfall well before the period closes.
Check effective dates. Rate changes, escalators and renewals each have a date. Usage before and after that date may price differently.
Record the clause behind every finding. A variance without the clause is an argument. A variance with the clause and the calculation is a correction someone can approve.
Sellers run this to make sure everything owed is invoiced. Buyers run it before approving payment. Whether a shortfall, back-bill or credit can actually be claimed depends on the contract wording, any notice or dispute periods, and the governing law. This article is general information, not legal advice.
Where ObligaAI fits
ObligaAI’s revenue leakage product reads customer contracts for “fees, escalators, usage tiers, discounts, minimums, milestones and renewal terms” and turns them into plain-language obligations with a confidence score. It then matches contract to invoice, usage to invoice and milestone to invoice, using customer contracts, order forms, renewals, price lists, usage reports and invoices. “Usage under-billed” is one of the leak categories it looks for. Each finding comes with the clause, the invoice, the shortfall, its dollar value and a recommended action.
It is advisory first. Findings are suggestions with the clause attached, never automatic changes, and no invoice is changed until the right person signs it off. It works as an overlay beside the billing and contract systems you already run, not as a replacement.
On the buying side, ObligaAI’s use cases include monitoring software contracts, licensing terms, renewals and commercial commitments, such as seats in use against seats purchased.
You can start free with no credit card, or start a conversation about your usage contracts.
Usage-based billing FAQ
Is usage-based billing the same as pay-as-you-go?
Mostly. Pay-as-you-go usually means pure usage pricing with no commitment. Usage-based billing is broader: it also covers contracts with included allowances, tiered overage and committed minimums.
Why is usage billed in arrears?
Because the quantity is not known until the period ends. The meter has to close, usage has to be totalled, and only then can it be rated and invoiced.
What is the difference between graduated and volume tiers?
With graduated tiers, each rate applies only to the units inside its band. With volume tiers, all units are priced at the rate of the highest tier reached. The same usage can produce different invoices, so check which one your contract specifies.
What happens if a customer does not reach the committed minimum?
It depends on the contract. Many require a shortfall payment for the difference at the end of the period. Some allow rollover or credit instead. Read the shortfall clause and its timing.
How often should usage invoices be reconciled against the contract?
Every billing period for material contracts, plus a full review before any true-up or renewal. Monthly checks catch metering gaps while the usage data is still fresh.
Who owns usage billing accuracy?
On the seller side, usually billing or revenue operations with finance. On the buyer side, accounts payable together with the budget owner, IT or procurement who know what was contracted.