SaaS Revenue Recognition Under ASC 606, Without the Jargon
The five-step model matters less than the habit: recognize subscription revenue over the term it covers, not when the cash lands. Here is how that works in practice for a Nashville SaaS company.
A customer pays you $12,000 in January for a year of software. How much revenue did you earn in January?
If your books say $12,000, they are wrong, and every metric built on them — MRR, growth rate, gross margin — is wrong with them. The right answer is $1,000, with the other $11,000 sitting on the balance sheet as deferred revenue: money you hold but have not yet earned.
That is the core of ASC 606 for a subscription business. The standard’s five-step model (identify the contract, identify the obligations, set the price, allocate it, recognize as you deliver) exists for complicated cases — usage tiers, bundled implementation, multi-year ramps. For a straightforward SaaS product, it collapses to one habit: recognize revenue over the term the payment covers, evenly, month by month.
Why founders get this wrong
Cash accounting feels honest — the money really did arrive in January. But subscription revenue is a promise to deliver service for twelve months, and eleven of them have not happened yet. Booking it all at once creates three specific problems:
- Your growth is noise. A few annual deals landing in the same month looks like a breakout quarter; their absence next month looks like collapse.
- You spend your customers’ money. Deferred revenue is close to a liability in the plainest sense: if you shut down in June, half that January payment was never yours.
- Diligence will rebuild it anyway. Any acquirer or serious investor recomputes revenue on an accrual basis first. At SaaS multiples, a rev-rec correction moves the price by multiples of the error.
What the mechanics look like
Each contract gets a simple schedule: total value, start date, term, monthly recognition amount. Cash in goes to deferred revenue; each month’s close releases one month’s slice to revenue. The whole apparatus is one spreadsheet tab or a rev-rec tool, plus one journal entry a month — but that entry has to happen every month, inside a real close. If your close is shaky, fix that first: the month-end close checklist is the foundation this sits on.
Implementation fees and setup charges deserve a mention: under 606 they are usually not a separate deliverable, and get recognized over the expected customer life rather than at kickoff. It is counterintuitive and it is also the rule.
The metrics come from the schedule
Once the deferral schedule exists, the metrics investors ask for fall out of it for free. MRR is the sum of the monthly recognition column. ARR is that times twelve. Churn and expansion come from comparing a customer’s row month over month. Companies that compute MRR from bank deposits are estimating; companies that compute it from the schedule are reporting.
One Tennessee-specific footnote while you are here: the state taxes SaaS for sales tax purposes — a separate obligation from revenue recognition, covered in Tennessee sales tax on SaaS.
For the rest of the subscription-finance stack — deferred revenue in depth, metrics, diligence prep — see SaaS Revenue & Metrics. And if you want a benchmark for what keeping this properly costs, the Cost Index breaks out SaaS specifically.
Want us to look at this in your own books?
Compass East publishes this reference and does this work for Middle Tennessee companies. Thirty minutes, free, and you keep the findings whatever you decide.