Revenue Recognition (ASC 606)
When you can count the revenue, not when you bill it - the standard that spreads an annual SaaS deal across the year you deliver.
- Term
- Revenue Recognition (ASC 606 / IFRS 15)
- Governs
- When revenue can be recognized
- Rule
- As the obligation is satisfied, not when billed
- Matters for
- SaaS, subscriptions, multi-element deals
Forms & parts of speech
Definition in plain terms
ASC 606 (and its international twin, IFRS 15) is the accounting standard that governs when and how a company can recognize revenue.
Its core principle is that revenue is recognized as the company satisfies its performance obligation - that is, as it delivers the good or service the customer paid for - not when the cash is collected or the invoice is sent.
It uses a five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate the price to the obligations, and recognize revenue as each obligation is satisfied.
It standardized revenue recognition across industries and is especially consequential for subscription and multi-element businesses.
Why it matters enormously for SaaS
ASC 606 is why SaaS revenue and SaaS billing are different numbers, which every SaaS operator must understand.
When a customer pays $1,200 upfront for an annual subscription, the company cannot recognize $1,200 of revenue immediately - under ASC 606 it must recognize the revenue as it delivers the service, roughly $100 per month over the year, with the rest sitting as deferred revenue until earned.
This is why a SaaS company's recognized revenue, bookings (contracts signed), billings (invoiced amounts), and cash collected are four distinct figures that rarely match in a period.
For multi-element deals (software plus services plus support), ASC 606's allocation rules determine how the price is split and recognized. The literacy is knowing that recognized revenue follows delivery, not billing - and that bookings, billings, revenue, and cash tell different parts of the story.
The standard requires revenue to be recognized as the performance obligation is satisfied - as the service is actually delivered
so the $1,200 annual contract becomes roughly $100 of recognized revenue per month across the year, with the remaining cash sitting as deferred revenue (a liability) until it is earned.
The team sees that the company now has four distinct numbers that rarely match in a period: bookings (the contract value signed), billings (what was invoiced), recognized revenue (what ASC 606 lets them count as earned), and cash collected (what actually arrived).
For its multi-element deals - software plus onboarding plus support - ASC 606's five-step model determines how the single price is allocated across those obligations and recognized as each is delivered.
The team builds its reporting and its board narrative on this literacy: recognized revenue follows delivery, not billing, and bookings, billings, revenue, and cash each tell a different part of the same story
the distinction that separates a SaaS operator who understands their numbers from one who conflates a signed contract with earned revenue.
and misallocating price across multi-element deals.
Formula
Benchmarks
ASC 606 is a recognition standard, not a metric; the literacy is distinguishing bookings, billings, revenue, and cash.
Ranges are illustrative; every published figure is cited from a named public source or labelled “RGM analysis.”
Synonyms & antonyms
Synonyms
Antonyms
Origin & history
ASC 606 (and IFRS 15) took effect in 2018, replacing fragmented industry-specific rules with a single five-step revenue-recognition model based on satisfying performance obligations; it is especially consequential for SaaS and subscription businesses, formalizing why recognized revenue, bookings, billings, and cash are distinct figures.
Etymology: source.
Usage trends
Search interest for this term over the last five years:
Common questions
- What is ASC 606?
- The accounting standard governing when and how revenue is recognized — requiring it to be recognized as the performance obligation is satisfied (the service delivered), not when cash is collected.
- Why does ASC 606 matter for SaaS?
- Because it requires an annual subscription's revenue to be recognized over the year as the service is delivered (not upfront), making recognized revenue, bookings, billings, and cash four distinct numbers.
- What is the five-step model?
- Identify the contract, identify the performance obligations, determine the transaction price, allocate it to the obligations, and recognize revenue as each obligation is satisfied.
Related tools & calculators
Resources & people to follow
- referenceWikipedia — IFRS 15 / ASC 606 revenue recognition
- referenceSaaS-finance and revenue-recognition practice
- referenceRGM analysis — recognized revenue follows delivery, not billing; bookings, billings, revenue, and cash differ
Curated, non-competitor resources verified per term.
Related training
Disciplines
Areas of marketing where revenue recognition (asc 606) is a core concern: