The five-step model
ASC 606 reduces revenue recognition to five steps: identify the contract, identify the performance obligations, determine the transaction price, allocate the price across obligations, and recognize revenue as each obligation is satisfied. Most of the complexity comes from step two - figuring out what counts as a distinct performance obligation.
For a typical SaaS contract with a subscription plus onboarding plus support, you often have two or three separate obligations. The subscription is recognized ratably over the term. Onboarding might be recognized as delivered, or over the subscription term depending on whether it is a distinct service. Support is typically recognized ratably alongside the subscription.
The key question in step two: is each component something the customer could buy separately and use independently? If yes, it is a distinct obligation. If no, it is bundled with another. Getting this wrong is the most common ASC 606 issue in SaaS audits.
Common scenarios and how to handle them
Annual prepaid subscriptions are the simplest case. Customer pays $12K upfront for one year. You recognize $1K per month for 12 months. The unrecognized portion sits as deferred revenue on the balance sheet. Cash is fully collected day one, but revenue trickles in over the year.
Multi-year deals with upfront payment are trickier. A three-year $60K prepaid deal recognizes $1,667 per month for 36 months. This is different from simply recognizing $20K per year - you need the monthly granularity for financial reporting. Deferred revenue on the balance sheet will be meaningful for the first two years.
Implementation fees are where many founders make mistakes. If implementation is required for the customer to use the service, it is typically not a distinct obligation and gets recognized ratably over the subscription term, not upfront. Booking it all upfront overstates early revenue and understates later revenue.
What auditors look for
Auditors reviewing ASC 606 compliance focus on three things: consistency of your policy application across customers, documentation of the performance obligation analysis for each contract type, and reconciliation of your deferred revenue balance to the outstanding contract obligations.
The documentation requirement is real. "We recognize revenue ratably over the subscription term" is not enough. You need to document how you identified performance obligations, how you allocated transaction price to each, and how you determined the recognition pattern. This documentation should exist for each contract type, not each customer.
Contract modifications are another audit focus. When a customer upgrades mid-term, adds seats, or renegotiates pricing, the revenue recognition needs to reflect the change. The specific treatment depends on whether the modification is prospective or retrospective, which requires judgment. Document the reasoning.
Tools and automation
For companies under $5M ARR with straightforward contracts, spreadsheet-based recognition can work. Track each contract on a tab with start date, end date, amount, and monthly recognition. Tie the monthly totals back to your general ledger. Reconcile deferred revenue balance quarterly.
Past $5M ARR or with contract variations, dedicated revenue recognition software becomes necessary. Maxio, Chargebee, RightRev, and others handle the mechanics. Integration with your CRM and billing system automates most of the work. Expect to spend $1-3K per month on the tool plus implementation effort.
Whatever approach you use, monthly close should include revenue recognition as a distinct step, with reconciliation of deferred revenue and a review of new contracts for proper classification. Skipping this step once leads to compounding errors that surface later during audit or diligence.