If your SaaS business bills customers annually but delivers the service monthly, you can't simply record the full annual payment as revenue the day it hits your bank account. That's the core idea behind ASC 606 revenue recognition, and it trips up a lot of early-stage SaaS founders.
The Basic Idea
ASC 606 requires revenue to be recognized as the service is actually delivered, not when cash is received. If a customer pays $12,000 upfront for an annual subscription, that revenue gets recognized at roughly $1,000 per month over the year — not all at once in the month they paid.
What "Deferred Revenue" Means
The portion of that payment not yet "earned" sits on your balance sheet as a liability called deferred revenue (sometimes called unearned revenue). It represents an obligation — you've been paid, but you still owe the customer months of service. As each month passes, a slice of that deferred revenue moves over to recognized revenue.
Why This Actually Matters
- Investors and boards expect it — recognizing all cash upfront overstates revenue in the month collected and understates it later, distorting growth trends.
- It affects valuation conversations — ARR and MRR calculations depend on revenue being recognized correctly over time, not lumped at collection.
- Cleanup gets expensive later — fixing years of incorrectly recognized revenue during a fundraise or audit is far more costly than setting it up correctly from the start.
Getting This Right From the Start
This becomes more complex with usage-based pricing, multi-year contracts, or bundled products and services — each has its own recognition pattern under ASC 606's broader framework. The key is setting up your accounting system to track this automatically as contracts are signed, not trying to reconstruct it later.
See how we support technology and SaaS companies with revenue recognition and investor-ready reporting.