Revenue recognition for usage-based SaaS pricing models

Short answer: Under ASC 606 and IFRS 15, usage-based SaaS revenue is generally recognized in the period the customer uses the service, because the fee is variable consideration that relates to that period. Committed minimums are recognized over the commitment period, prepaid credits sit in deferred revenue until they are consumed, and usage that has been delivered but not yet invoiced at month end is recorded as accrued revenue.

This matters for any finance team that bills on consumption, API calls, seats measured monthly, transactions or data volume. The invoice often arrives a month after the usage, so revenue and billing drift apart at every close unless the accounting is set up for it.

Why usage-based pricing is variable consideration

Usage fees are variable consideration because the amount the company will receive depends on what the customer does after signing. The IFRS Foundation summary of IFRS 15 notes that when the promised consideration includes a variable amount, the company must estimate the amount it expects to be entitled to. ASC 606 sets out the same requirement, together with a constraint: variable consideration is included only to the extent that a significant reversal of revenue is not expected when the uncertainty is resolved.

For pure pay-as-you-go pricing, estimating a full year of usage upfront would be impractical and of little use. The standards provide a more direct route, covered in the next section, which is why most SaaS companies recognize usage revenue month by month as it occurs.

The allocation exception that lets usage follow the period

Most SaaS platforms are a series of distinct service periods: the company stands ready to provide access each day or each month. When a variable fee relates specifically to the service in one of those periods, and allocating it there is consistent with the allocation objective, the fee can be allocated entirely to that period instead of being spread across the contract.

In practice, this means January usage is January revenue. The company does not need to forecast February usage to recognize January correctly. Many companies also rely on the "right to invoice" practical expedient in both standards, which allows revenue to be recognized at the amount the company has a right to invoice when that amount corresponds directly with the value delivered to the customer to date. Whichever route applies, the documentation should state which one the company uses and why the facts support it.

Two situations need more analysis: tiered pricing where the per-unit rate falls as annual volume rises, and fees that depend on usage across the whole contract. In both, the rate charged in one month may not reflect the value delivered that month, so the simple period-by-period approach may not hold.

Minimum commitments with overage

A minimum commitment is a fixed amount the customer pays whether or not it uses the full allowance, with overage charged for usage above it. The fixed portion is recognized over the commitment period, usually ratably, because the company is standing ready to deliver throughout. Overage is recognized in the period the excess usage occurs.

Illustrative example: a customer signs in January 2026 for a monthly minimum of $10,000, which includes 100,000 API calls, with overage at $0.08 per additional call. The minimum resets each month, and overage is invoiced in arrears at the start of the following month. The table below shows revenue for the first quarter.

Source: illustrative figures, not customer data.

January usage falls below the allowance, so revenue is the $10,000 minimum. March overage of $4,800 is earned in March but invoiced in April, so at the March 31 close it is recorded as accrued revenue. If the minimum were annual rather than monthly, with unused allowance carrying forward, the analysis changes: the company would need to consider how much of the commitment is likely to go unused, and overage might not arise until later in the year.

Prepaid credits and drawdown models

With prepaid credits, the customer pays upfront for a block of usage and draws it down over time. The cash received is a contract liability, recorded as deferred revenue, and revenue is recognized as the credits are consumed.

Credits that the customer is not expected to use, known as breakage, need a policy. If the company expects to be entitled to a breakage amount, it recognizes that amount in proportion to the pattern of credits the customer actually uses. If it does not expect to be entitled to breakage, it recognizes the unused balance when the likelihood of the customer using it becomes remote, which is often at expiry. Estimating breakage needs reliable history, so newer usage products often wait until expiry.

• Rollover terms. Credits that roll into the next term extend the liability and push breakage later.
• Bonus credits. Free credits granted on a large purchase may be a material right and need part of the price allocated to them.
• Refund rights. If unused credits are refundable, the expected refund is a liability, not breakage.

Recording unbilled usage at month end

Usage billed in arrears creates a timing gap: the service is delivered in one month and invoiced in the next. At each close, the delivered but uninvoiced amount is recognized as revenue and recorded as accrued revenue, with the entry reversed when the invoice is raised.

The balance sheet line depends on the company's right to payment. If the only thing standing between the company and payment is the passage of time, the amount is an unbilled receivable. If payment still depends on something other than time, such as delivering further service, it is a contract asset. For most usage billed in arrears at an agreed rate, the right to the March overage is unconditional once March ends, so it is usually presented as an unbilled receivable. Our guide to deferred revenue vs accrued revenue covers the difference between the two balances.

The practical difficulty is data. Usage records live in the product, invoices in Xero or QuickBooks, and contract terms in the CRM. Finance teams that reconcile usage to invoices each month catch missed overage and duplicate billing before they reach the ledger.

Controls for a usage-based revenue process

• One agreed usage source. Revenue is calculated from a single, locked usage report for the month, not from a live dashboard that keeps changing.
• Cut-off. Usage up to 11:59 pm on the last day of the month belongs to that month, in an agreed time zone.
• Accrual reversal. Each month's accrued usage is reversed when the invoice posts, so revenue is not counted twice.
• Contract terms in one place. Allowances, rates, tiers and rollover rules are recorded per contract, so the calculation matches what was signed.
• Review before posting. The usage accrual and credit drawdown journals are reviewed and approved like any other estimate.

How ScaleXP supports usage-based revenue accounting

The fixed side of a usage contract, such as a committed minimum or a prepaid block, follows a schedule, and the invoiced side lands in your ledger. ScaleXP builds revenue schedules from your invoice data in Xero or QuickBooks, with contract details from HubSpot, Salesforce or Pipedrive, and prepares the revenue journals. The journals are posted once finance approves them, so usage estimates and accruals stay under the finance team's review.

In the ScaleXP demo company below, two usage lines on one invoice are listed with the amount still to recognize, where finance enters the amount or percentage to recognize in each month.

For amounts earned but not yet invoiced at month end, see accrued income automation in Xero and QuickBooks. For the wider process, see revenue recognition automation for Xero and QuickBooks.

Conclusion

Usage-based pricing does not need a full-year forecast for each customer. When the fee relates to the service delivered in a period, recognize it in that period; recognize committed minimums over the commitment; hold prepaid credits in deferred revenue until they are used; and accrue usage that has been delivered but not invoiced. Document which route the company uses, agree one usage source, and review the accrual every month.

Frequently asked questions

Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers.