ASC 606 Revenue Recognition: A CFO's Guide for B2B SaaS
Revenue recognition under ASC 606 gets harder as pricing gets more flexible. Here is how CFOs keep close and compliance from colliding.
Every CFO has had this month. The sales team closed a great quarter. The board deck is due tomorrow. And revenue recognition, the process of deciding when the money you have collected actually counts as earned, is still being reconciled in a spreadsheet that only one person on your team fully understands.
Revenue recognition is not glamorous, but it is the difference between a close that takes two days and one that takes two weeks. And as pricing gets more creative, ramped contracts, usage components, multi-year deals with mid-term changes, it gets exponentially harder to get right by hand.
The five steps everyone knows and nobody enjoys applying
ASC 606 gives you a clean five-step framework: identify the contract, identify the performance obligations, determine the transaction price, allocate that price across obligations, and recognize revenue as each obligation is satisfied. On a whiteboard, it is simple. In a real contract with a platform fee, three add-ons, a usage component, and a ramped discount that steps down in month seven, it is a different problem entirely.
Where it actually breaks:
most revenue recognition errors do not come from misunderstanding the standard. They come from contract terms that live in a CRM or a signed PDF, disconnected from the system that is supposed to be recognizing revenue against them.
5 steps
in the ASC 606 model, from identifying the contract to recognizing revenue as obligations are satisfied
2-10 days
the typical range in close time between finance teams running manual recognition and those with automated schedules
1-5%
of ARR that industry research estimates is lost annually to billing and revenue leakage
The audit conversation nobody wants to have twice
If you have been through a revenue recognition audit with spreadsheet-based processes, you know the drill. The auditor asks for the standalone selling price justification on a bundled deal from fourteen months ago. Someone has to reconstruct it from memory and old emails, because the calculation that produced the number was never saved anywhere durable.
"An auditor does not just want the right number. They want to see exactly how you got there, every time, the same way."
Author
Jordan Lee
Head of Revenue, Module
