Key points
Revenue recognition is the set of rules that decides in which period revenue is reported, and in what amount.
US GAAP uses ASC 606 and IFRS uses IFRS 15; both apply the same five-step model to contracts with customers.
Each pricing model has its own pattern: subscriptions ratably, usage as consumed, prepaid credits as used plus breakage.
Hybrid plans mix patterns in one contract, so one customer can create deferred revenue and unbilled revenue at once.
Startups usually need ASC 606 revenue once they face an audit, raise a priced round or prepare for diligence.
Revenue recognition in one paragraph
Revenue recognition decides when revenue appears on the income statement and how much. The answer is not when cash arrives or when an invoice goes out. Under the revenue recognition principle, you report revenue as control of goods or services transfers to the customer, at the amount you expect to be entitled to.
In the US the rules are in ASC 606, Revenue from Contracts with Customers. Outside the US, IFRS 15 applies, effective for annual periods beginning on or after 1 January 2018. Both use the same five-step model.
How it works by pricing model
Most questions finance teams have are not about the standard in general. They are about how their own pricing turns into monthly revenue. This table is the short version.
Pricing model | Usual recognition pattern | Balance sheet account it creates |
|---|---|---|
Annual subscription billed upfront | Ratably over the term | |
Usage billed monthly in arrears | As consumed, often via the right-to-invoice expedient | |
Prepaid credit packs | As credits are consumed, plus breakage on expiry | Deferred revenue |
Platform fee plus usage overage | Platform ratably, overage as consumed | Both, per contract |
Free months or ramped pricing | Evenly over the term, ahead of billing | Contract asset |
Implementation or onboarding | As performed if distinct, otherwise over the access term | Depends on billing timing |
Worked example: one hybrid customer, one month
Illustrative only. Fieldnote AI is a fictional Series B company with usage-based pricing. One customer has a $120,000 annual platform fee paid upfront, a prepaid credit pack, and overage billed in arrears. In March the customer uses $4,000 of prepaid credits and $3,000 of overage that will be invoiced in April.
Component | March revenue | Source of the number |
|---|---|---|
Platform fee | $10,000 | $120,000 ÷ 12 |
Prepaid credits consumed | $4,000 | Usage database at contract credit rate |
Overage consumed | $3,000 | Usage database at overage rate |
Total | $17,000 |
March 31, month-end entry. No cash moves in March, yet revenue is $17,000.
Account | Debit | Credit |
|---|---|---|
Deferred revenue | $14,000 | |
Unbilled receivables | $3,000 | |
Subscription revenue | $10,000 | |
Usage revenue | $7,000 |
Why it matters for startups
Early on, many startups report revenue from Stripe payouts or invoices. That works until the first audit, a priced round with diligence, or a board that compares revenue to billings. Rebuilding two years of contracts under ASC 606 at that point takes weeks.
Usage and AI pricing raise the stakes. Revenue depends on consumption data, and cost of revenue depends on the same data through inference and cloud bills. If revenue is recognized in the wrong month, gross margin is wrong in two months.
Common mistakes
Revenue equals invoices. Fine for simple monthly billing, wrong for annual prepayments, arrears billing and credits.
One method for every plan. A hybrid plan needs ratable and consumption patterns side by side.
No written policy. Auditors start by asking for your revenue policy memo. Without one, each judgment gets reopened.
Ignoring expired credits. Unused credits left on the balance sheet indefinitely overstate liabilities and understate revenue.
How to set up revenue recognition
List every pricing model you sell, including legacy and custom deals.
For each model, document the performance obligations and the recognition pattern in a short policy memo.
Connect contract terms, billing data and usage data so each month’s revenue can be recomputed.
Book revenue through journal entries to deferred revenue, unbilled receivables and contract assets, not straight from invoices.
Reconcile each balance monthly with a roll-forward.
Review the policy whenever pricing changes.
How Quanta handles it
Quanta is an accounting-first platform with an in-house accounting team that keeps the ledger. It is built around how a company charges, with integrations into the customer’s usage database, Stripe and cloud bills. Revenue and the cost lines behind it are current, and every number traces back to journal entries.
Quanta perspective
Revenue recognition for usage and AI pricing is a data problem first and an accounting problem second. When revenue and COGS come from the same consumption data, gross margin by customer becomes visible, and in usage pricing that matters more than ARR.
Frequently asked questions
What are the five steps of revenue recognition?
Identify the contract, identify the performance obligations, determine the transaction price, allocate the price to the obligations, and recognize revenue when or as each obligation is satisfied.
Do private companies have to follow ASC 606?
Private companies that issue US GAAP financial statements must apply ASC 606. A company that only prepares cash-basis or tax-basis statements does not, but lenders, auditors and investors often require GAAP.
How is usage-based revenue recognized?
Usually as the customer consumes the service. For a fixed price per unit, the right-to-invoice practical expedient often lets revenue equal metered usage times price.
Is revenue recognized when cash is received?
Not under accrual accounting. Revenue is recognized when control of the goods or services transfers, which can be before or after payment.
What is the difference between ASC 606 and IFRS 15?
They share the same core model and five steps. Differences are in details, such as some disclosure relief for private companies under US GAAP and a few practical expedients.