Consumption pricing aligns what customers pay with the value they use, but it moves revenue recognition and forecasting from straightforward to judgment-heavy. The structures below cover most usage-based SaaS contracts.
Common structures
| Structure | How it is recognized |
|---|---|
| Pure pay-as-you-go, billed in arrears | Recognize as usage occurs; bill and recognize in the same month |
| Committed minimum with overage | Recognize the commitment over the term (ratably, or as used if usage is the measure of progress); overages as incurred |
| Prepaid credits drawn down | Defer the prepayment; recognize as credits are consumed |
| Annual commitment with true-up | Recognize usage as it occurs; assess the expected shortfall payment as variable consideration |
Variable consideration
Usage fees are variable consideration under ASC 606. In many SaaS contracts, the variable-consideration allocation exception lets you allocate usage fees to the period the usage occurs, which keeps recognition close to billing. Where it does not apply, estimate the variable amount and constrain it so that a significant reversal is not probable.
Breakage on prepaid credits
If customers routinely let credits expire, the unused portion is breakage. When you can reliably estimate it, recognize breakage in proportion to the pattern of usage; otherwise recognize it when the likelihood of use becomes remote, usually at expiry.
Forecasting usage revenue
- Forecast by customer cohort and usage driver (API calls, seats active, transactions), not by last month's total.
- Separate committed revenue from expected overage in the model.
- Track consumption against commitments monthly so true-ups and expansions are visible before renewal.
Metrics adjustments
- Report committed ARR and usage revenue separately.
- Calculate NRR on committed ARR, and show usage expansion as its own line.
- Watch gross margin closely: usage revenue often carries usage-linked infrastructure cost.
Systems
Usage data usually lives outside the billing system (a product database or metering tool). The close needs a monthly extract that ties metered usage to billed amounts and to recognized revenue. We build that tie-out and the schedules, in whatever billing and accounting systems you run.
A worked example
A customer signs a one-year contract with a $120,000 annual commitment billed quarterly in advance, covering up to 10 million API calls, with overage at a set price per thousand calls.
- Each quarter, bill $30,000 to deferred revenue and recognize $10,000 a month as the platform is available (if access, not consumption, is the obligation) or as calls are consumed (if consumption is the measure of progress), according to your policy.
- In a month with overage, bill and recognize the overage in that month.
- At year end, if usage fell short, there is no refund; the commitment was already recognized under your policy.
The policy choice (ratable versus consumption-based recognition of the commitment) depends on the nature of the promise and should be documented once.
Contract terms that change the answer
- Rollover of unused commitments to the next term can create a material right.
- Tiered pricing that drops the unit price as volume grows may require estimating the average price over the term.
- No-charge usage allowances offered as a promotion are part of the transaction price analysis.
Board reporting
Show three lines: committed revenue, usage revenue and total. Directors can then see how much of growth is contracted and how much depends on customer activity in the quarter, which is the first question in any discussion of forecast risk.
Sources
Questions founders ask
When are prepaid usage credits recognized?
As the credits are consumed. Unused credits that are expected to expire unused (breakage) can be recognized in proportion to usage if you can estimate them reliably; otherwise when the chance of use becomes remote.
Is usage revenue part of ARR?
Committed minimums usually are. Usage above commitments is often reported separately because it varies month to month.
