ASC 606
The GAAP revenue recognition standard requiring a five-step model to determine when and how to recognize revenue from customer contracts.
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.