ASC 606
The GAAP revenue recognition standard requiring a five-step model to determine when and how to recognize revenue from customer contracts.
ASC 606 (Accounting Standards Codification Topic 606, 'Revenue from Contracts with Customers') is the authoritative US GAAP standard governing revenue recognition, jointly developed by FASB and IASB and substantially converged with IFRS 15. It replaced a fragmented collection of industry-specific guidance with a single, principle-based five-step framework.
The five steps are: (1) Identify the contract — must have commercial substance, enforceable rights, and probable collection; (2) Identify performance obligations — distinct goods or services promised in the contract; (3) Determine transaction price — including variable consideration, non-cash consideration, and financing components; (4) Allocate transaction price — based on relative standalone selling prices (SSP) of each performance obligation; (5) Recognize revenue — as each performance obligation is satisfied, either at a point in time or over time.
The 'over time' vs. 'point in time' distinction is critical. Revenue is recognized over time if the customer simultaneously receives and consumes the benefit (e.g., SaaS subscriptions), the performance creates or enhances an asset the customer controls (e.g., custom software), or there is no alternative use and the company has right to payment for performance to date (e.g., professional services).
ASC 606 introduced new disclosure requirements including disaggregated revenue, remaining performance obligations (RPO), contract assets, and contract liabilities — providing investors more transparency into revenue quality and visibility.
For complex arrangements, SSP determination is the most challenging aspect. Companies must document their SSP methodology for each product and service, update it regularly, and ensure pricing consistency to defend their revenue recognition positions during audit.
FAQs
What is a Remaining Performance Obligation (RPO) under ASC 606?
RPO is the total amount of contracted revenue not yet recognized — essentially a legally committed revenue backlog. It includes both deferred revenue (cash already collected) and non-cancellable future billings. Public SaaS companies disclose RPO as a leading indicator of future revenue, often growing faster than recognized revenue during expansion.
How does variable pricing (usage-based) work under ASC 606?
Variable consideration must be estimated and included in the transaction price, but only to the extent it is 'probable that a significant reversal' of recognized revenue will not occur. This requires applying the expected value or most likely amount methods, with regular reassessment as actual usage becomes known.
What is standalone selling price (SSP) and why does it matter?
SSP is the price at which a company would sell a promised good or service separately. Under ASC 606, when multiple performance obligations are bundled in one contract, the total price must be allocated based on relative SSPs. Getting SSP wrong leads to incorrect revenue timing — a common audit focus area.
