Introduction
A SaaS company signs a three-year, $360,000 contract and collects the full payment upfront. Recording all $360,000 as revenue the day the check clears would be a genuine accounting error — and understanding exactly why gets to the heart of what revenue recognition actually requires.
Table of Contents
- The Core Principle
- The ASC 606 Five-Step Model
- A Worked Example
- Recognized Over Time vs at a Point in Time
- Why ASC 606 Exists
- ASC 606 vs IFRS 15
- Why This Matters Beyond Compliance
- FAQ
- Conclusion
The Core Principle
Revenue recognition is the accounting principle governing exactly when a business can formally record revenue as earned. The core rule, as defined by ASC 606: revenue should be recognized to depict the transfer of promised goods or services to a customer, in an amount reflecting what the business genuinely expects to receive in exchange — and critically, this is recognized when that transfer actually happens, not necessarily when cash is collected. A business can recognize revenue before, after, or exactly when it receives payment; the timing of cash and the timing of revenue recognition are genuinely separate questions.
The ASC 606 Five-Step Model
ASC 606 (Accounting Standards Codification 606), issued by the Financial Accounting Standards Board (FASB), structures revenue recognition into a sequential, five-step process that applies to essentially every revenue transaction, regardless of industry:
- Identify the contract with a customer
- Identify the performance obligations — the distinct promises to deliver goods or services within that contract
- Determine the transaction price — the total amount the business expects to be entitled to
- Allocate the transaction price across each identified performance obligation
- Recognize revenue as (or when) each performance obligation is actually satisfied
A Worked Example
Returning to the three-year, $360,000 SaaS contract: under ASC 606, this doesn't get recognized as $360,000 in revenue upfront. Instead:
- Step 1: The contract is identified
- Step 2: The performance obligation is providing software access continuously over 36 months
- Step 3: Transaction price is $360,000
- Step 4: The full price is allocated to this single ongoing obligation
- Step 5: Revenue is recognized $10,000 per month, as the service is actually delivered over the 36-month term
The cash may have arrived in full on day one; the revenue is recognized gradually, matching when the customer actually receives the value being paid for.
Recognized Over Time vs at a Point in Time
ASC 606 distinguishes between two recognition patterns. Revenue is recognized over time if any one of these criteria is met:
- The customer simultaneously receives and consumes the benefit as the business performs (like the SaaS example above)
- The business's performance creates an asset the customer already controls
- The business has no alternative use for what it's creating, and has an enforceable right to payment for work completed to date
If none of these apply, revenue is recognized at a single point in time — typically the specific moment control of a good or service formally transfers to the customer, such as a retail sale at checkout.
Why ASC 606 Exists
Before ASC 606, revenue recognition guidance was genuinely fragmented across hundreds of industry-specific rules — software companies followed different guidance than construction companies, who followed different guidance still from retailers. ASC 606 replaced this patchwork with a single, unified, principle-based framework applicable across industries, specifically to improve consistency and comparability between companies' financial statements, regardless of what they actually sell.
ASC 606 vs IFRS 15
ASC 606 is the US GAAP standard; IFRS 15 is the equivalent standard used internationally. The two were developed jointly by FASB and the International Accounting Standards Board, and they're substantially converged — both following the same core five-step model. This was a deliberate effort to reduce the historical divergence between US and international revenue recognition practices, genuinely useful for any company operating across both frameworks.
Why This Matters Beyond Compliance
Beyond simply following the rule correctly, proper revenue recognition genuinely affects how a business's performance actually looks to anyone evaluating it — investors, lenders, or a potential acquirer. A business that recognizes revenue too aggressively (booking it before it's genuinely earned) can appear healthier than it actually is, a pattern that eventually corrects itself, often at an inconvenient moment. Consistent, correct revenue recognition is what makes a business's reported growth and performance genuinely trustworthy over time, not just compliant on paper.
FAQ
Revenue should be recognized to depict the transfer of promised goods or services to customers, in an amount reflecting what the business expects to receive in exchange — recognized when that transfer actually happens, not necessarily when cash changes hands. A business can recognize revenue before, after, or at the same time it collects payment.What is the core principle behind revenue recognition?
1) Identify the contract with a customer, 2) identify the distinct performance obligations within that contract, 3) determine the total transaction price, 4) allocate that price across each performance obligation, and 5) recognize revenue as each performance obligation is actually satisfied.What are the five steps of ASC 606?
Because the performance obligation — actually delivering the service — hasn't been satisfied yet at the moment of payment. Under ASC 606, that revenue must be recognized gradually, over the period the service is genuinely delivered, matching recognition to when the customer actually receives the value being paid for.Why can't a business recognize a full year (or multi-year) subscription as revenue immediately when it's paid?
Revenue is recognized over time if the customer simultaneously receives and consumes the benefit as the business performs, if the business's work creates an asset the customer already controls, or if the business has no alternative use for what it's creating and has an enforceable right to payment for work completed. Otherwise, revenue is recognized at a single point in time — typically when control of a good or service formally transfers to the customer.What's the difference between revenue recognized over time versus at a point in time?
ASC 606 applies broadly to any business preparing GAAP-compliant financial statements, not just public companies specifically — though the practical stakes are highest for businesses with investors, lenders, or other parties relying on accurate, standardized revenue reporting.Does ASC 606 apply to all businesses, or just public companies?
ASC 606 is the US GAAP standard; IFRS 15 is the equivalent standard used internationally. The two were developed jointly and are substantially converged, following the same core five-step model — a deliberate effort to create consistency between US and international revenue recognition practices.What's the relationship between ASC 606 and IFRS 15?
Conclusion
Revenue recognition genuinely comes down to one disciplined question, asked consistently: has the customer actually received what they're paying for, at this specific point in time? Getting this right — rather than booking revenue whenever cash happens to arrive — is what makes a business's reported growth something an investor, lender, or the business owner themselves can genuinely trust.
Need your revenue recognized correctly, especially for subscription or multi-period contracts? Our Financial Reporting service handles exactly this. Book a free consultation to talk through your specific revenue model.