What ASC 606 Actually Changed for SaaS Revenue Recognition

Most of the confusion around ASC 606 isn’t about the standard itself — it’s about the fact that a lot of SaaS companies were never doing revenue recognition correctly under the old rules either, and the new standard just made the gap visible.

The core change for SaaS is the shift from a rules-based model to a five-step framework built around performance obligations: identify the contract, identify the performance obligations, determine the transaction price, allocate that price across obligations, and recognize revenue as each obligation is satisfied. For a simple monthly subscription, this changes little. For anything with implementation fees, multi-year contracts, usage-based components, or bundled professional services, it changes almost everything about when revenue actually hits the income statement.

The most common error we still see: a company bundling a one-time implementation fee into month-one revenue instead of recognizing it ratably across the contract term, because that’s how the invoice was structured and nobody separated the accounting treatment from the billing treatment. Those are two different questions, and conflating them is the single most common finding in SaaS audits we perform.