Afternoon logoAfternoon

Usage-based revenue recognition: Rules and examples

Updated 2026-09-24

Usage-based revenue recognition depends on what your contract promises and when you deliver it. Metered usage can support the amount of revenue, but neither an invoice nor a usage event is enough to define the accounting policy.

For a straightforward service priced by consumption, recognizing revenue as the customer uses the service may be appropriate. Minimum commitments, credit discounts, separate services and contract changes require further analysis.

This guide concerns U.S. GAAP under ASC 606. The examples are illustrative and omit tax.

Start with the contract

Before configuring a revenue schedule, document:

  • The enforceable contract period and cancellation rights.
  • The services or other promises the customer receives.
  • Whether those promises are distinct.
  • Fixed fees, usage rates, discounts and minimum commitments.
  • When the customer receives each service.
  • Whether payment rights depend on anything other than the passage of time.

Use that assessment to select the recognition method. Do not let the billing system's default schedule determine the policy.

The FASB revenue implementation Q&A discusses the distinction between variable consideration and options to buy additional goods or services. Two contracts with similar invoices can have different accounting.

Apply the five steps

Use the ASC 606 framework to turn the contract review into a written conclusion:

StepQuestion to resolve
Identify the contractDo the agreement and collection assessment meet the contract criteria?
Identify performance obligationsWhich promised goods or services are distinct?
Determine the transaction priceWhat fixed and variable amounts can enter the calculation?
Allocate that priceHow does the amount relate to each performance obligation?
Recognize revenueWhen or over what period does the customer receive each promised service?

Allocation generally uses relative standalone selling prices, subject to the standard's exceptions. A separate invoice line does not prove that an item is a separate performance obligation. See FASB's guidance on identifying performance obligations.

Estimates and the constraint

When variable consideration needs an estimate, choose the expected-value or most-likely-amount method based on which better predicts the amount. Only include an estimate when it is probable that resolving the uncertainty will not cause a significant reversal of cumulative revenue. Reassess it at each reporting date.

The ASC 606 guidance on variable consideration sets out these methods and the constraint. Actual usage does not eliminate estimates for retrospective discounts, refunds, or other uncertain amounts.

When can revenue follow usage?

Two provisions often matter for service contracts:

ProvisionWhat to assess
Variable consideration allocationWhether the variable payment relates specifically to a distinct service or period and whether allocating it there meets the allocation objective
Right-to-invoice practical expedientWhether the amount you have a right to invoice corresponds directly to the value transferred to the customer to date

These are separate assessments. Billing monthly does not establish that either applies. A minimum, a retrospective discount or a changing unit price can affect the conclusion.

See the Deloitte discussion of variable consideration allocation, which includes the relevant ASC 606 guidance and examples.

Example: Simple usage billed after month-end

Assume a contract qualifies for recognizing revenue as usage occurs. The business delivers $600 of service in September and invoices in October.

EventDebitCredit
September service deliveryUnbilled receivable $600Revenue $600
October invoiceBilled accounts receivable $600Unbilled receivable $600
Customer paymentCash $600Billed accounts receivable $600

This example assumes the right to payment is unconditional except for the passage of time. If another condition must be met, a contract asset may be appropriate instead. The invoice date alone does not decide the classification.

The October invoice moves an amount between receivable accounts. It does not create another $600 of revenue. The accounts receivable guide covers payment matching and collections after billing.

Example: Purchased credits used over time

Assume a customer pays $1,000 for service credits, there is one service obligation, and the credits have no discount, refund, financing or breakage complication. During the period, the company delivers $250 of the service.

EventDebitCredit
Payment before serviceCash $1,000Contract liability $1,000
Service deliveredContract liability $250Revenue $250

The remaining contract liability is $750. The customer-facing credit balance and the accounting balance should reconcile, but they need not use the same unit. See AI credits vs. tokens for the difference between billing balances and usage units.

If the customer paid less than the credit's face value, do not automatically recognize the face value as revenue. Consider the transaction price and its allocation. Keep promotional credits separate from credits purchased for cash.

See accounting for AI credits for the buyer and seller records.

Minimum commitments need their own analysis

A monthly access fee, an annual spend commitment and a prepaid block of service units can create different rights.

  • A fee for a distinct stand-ready service may support recognition over the service period.
  • A commitment to buy units may relate to the units delivered rather than equal monthly amounts.
  • A package containing separate access and usage promises may require an allocation between them.
  • A discount that changes earlier unit prices can require an estimate and later adjustment.

Do not recognize every minimum evenly over the term, then add all usage on top. That can double-count the same consideration.

Write the conclusion for each contract pattern and have the reviewer approve it before using the pattern for other customers.

A minimum and overage example

Assume an illustrative monthly contract charges $5,000 for a stand-ready service that includes 100,000 transactions, then $0.06 for each extra transaction. Assume the accounting assessment supports even recognition of the monthly service and allocating the overage to that month's service.

At 150,000 transactions, the month's amount is:

  • Monthly service: $5,000.
  • Overage: 50,000 × $0.06 = $3,000.
  • Total revenue under these assumptions: $8,000.

Do not also charge or recognize the included 100,000 transactions at the overage rate. An annual commitment to buy a fixed quantity needs its own analysis; this example does not establish a monthly schedule for every minimum-spend contract.

Setup fees, discounts, and changes in the contract

An upfront setup fee may pay for an activity that transfers no separate service to the customer. In that case, receiving the fee does not itself earn revenue. If implementation is distinct, assess when the customer receives that service, which may occur over time or at a point in time.

Review renewal rights when deciding the recognition period for a nonrefundable fee. It is not always the initial term or the full expected customer relationship. FASB's implementation Q&A, question 52, addresses this distinction.

For volume discounts, establish whether a new tier changes only later units or reprices earlier ones. Repricing can require a revised estimate and adjustment. For a midterm change, keep the approved terms and effective date and assess whether the change creates a separate contract or changes the remaining accounting.

Expired credits and unused rights

Unused paid credits do not become revenue merely because a dashboard marks them expired.

Assess whether the business expects to be entitled to breakage, whether the estimate meets the applicable constraint, and whether unclaimed-property rules require payment to another party. When the required conditions are met, estimated breakage follows the pattern of rights exercised. Other cases may require waiting until the likelihood of exercise becomes remote.

Document the method and revisit the estimate as behavior changes. See ASC 606 breakage guidance and examples.

A month-end process for usage revenue

  1. Close the usage period. Define event time, timezone and the treatment of late records.
  2. Reconcile completeness. Compare accepted usage with the source system and investigate rejected or missing events.
  3. Apply the contract version. Check rates, amendments, included usage and discounts.
  4. Calculate revenue under the approved policy. Keep this calculation distinct from the amount due on the invoice.
  5. Reconcile balances. Explain changes in receivables, contract assets, contract liabilities and credits.
  6. Review exceptions. Record manual adjustments with a reason, preparer and reviewer.
  7. Retain the evidence. Save the contract, usage extract, calculation and approval together.

An automated process should still expose differences for review. It should not silently overwrite prior periods when someone changes a price or corrects an event.

What should the system export?

At minimum, keep a stable customer and contract reference, service period, product, price version, measured usage, billed amount, recognized amount and adjustment history.

A finance reviewer should be able to select a revenue entry and trace it back to the contract and delivery evidence. For the billing side, see how to turn API usage into invoices.

Use operating metrics alongside the revenue schedule

Track usage revenue as a share of total revenue, earned revenue per billable unit, and delivery cost by product or tier. Compare periods using the same units and explain rate or product-mix changes.

Review usage growth and net dollar retention by customer group. Separate more consumption from price changes or new service commitments. These measures help explain revenue and margin, but they do not replace the contract assessment or turn a usage forecast into earned revenue.

Book revenue and taxable income can differ

ASC 606 governs this financial reporting assessment. Income-tax rules for accounting methods and advance payments are separate. A deferred-revenue balance in the books does not, by itself, establish that a receipt is deferred for tax.

Review the tax method and applicable advance-payment rules with the return preparer. IRS Publication 538 explains accounting periods and methods.

Common questions

Do I recognize revenue when I invoice? Not automatically. Determine when the relevant service is delivered under the contract and approved policy.

Does consumption pricing eliminate estimates? No. Discounts, breakage, refunds and other variable amounts can still require estimates.

Can software automate recognition? It can apply an approved policy to complete data. It cannot establish that a contract qualifies for that policy merely because the invoice has a usage line.