Introduction
SaaS accounting breaks a assumption that works fine for most businesses: cash collected equals revenue earned. For a subscription business, that assumption is wrong often enough — and wrong in a specific, predictable way — that getting it right is the difference between financial statements a real investor trusts and ones that quietly erode credibility during due diligence. This guide covers how ASC 606, deferred revenue, and the MRR/ARR metrics actually fit together.
Note: This is educational information, not accounting advice for your specific contracts. Revenue recognition under ASC 606 gets genuinely complex with bundled services, usage-based pricing, and contract modifications — have your specific arrangements reviewed by a qualified accountant.
Table of Contents
- The Core Idea: Cash Collected vs. Revenue Earned
- Deferred Revenue, Explained
- ASC 606: The Five-Step Model
- MRR, ARR, and GAAP Revenue — Three Different Numbers
- Why ARR and GAAP Revenue Drift Apart
- The Rule of 40
- Why This Matters for Fundraising
- When Spreadsheets Stop Working
- FAQ
- Conclusion
The Core Idea: Cash Collected vs. Revenue Earned
This is the single concept that unlocks the rest of SaaS accounting: cash collected is not the same as revenue earned. A $120,000 annual subscription, billed and collected in full in January, does not produce $120,000 of January (or Q1) revenue. Under ASC 606, it produces $10,000 of recognized revenue per month for 12 months — because the service is being delivered continuously over the year, not all at once at the moment of payment.
This single distinction is where most SaaS accounting confusion — and most SaaS accounting mistakes — actually originates.
Deferred Revenue, Explained
Deferred revenue (also called unearned revenue) is the accounting mechanism that makes the above work correctly. When that $120,000 payment arrives in January:
- Cash increases by $120,000
- Deferred revenue (a liability on the balance sheet) increases by $120,000
- Revenue on the income statement stays at $0 for that transaction, initially
Each month, as the subscription is delivered, $10,000 moves from deferred revenue into recognized revenue. Deferred revenue is classified as a liability for a specific reason: if the company failed to deliver the service, it would owe that money back to the customer — it isn't truly the company's earned income until the obligation is fulfilled.
Unbilled revenue is the mirror-image concept: revenue that's been earned but not yet invoiced, common with usage-based billing where the exact amount owed isn't known until the billing period closes. It sits on the balance sheet as a receivable (an asset), not a liability.
ASC 606: The Five-Step Model
ASC 606 is the US accounting standard governing how companies recognize revenue from contracts with customers, structured around five steps:
- Identify the contract — typically your Terms of Service or a signed enterprise agreement
- Identify performance obligations — what you're actually promising to deliver (software access, implementation, support)
- Determine the transaction price — the total amount you expect to be entitled to
- Allocate the price across performance obligations, based on standalone selling price (SSP) if there are multiple
- Recognize revenue as each obligation is satisfied
For a straightforward SaaS business — monthly billing, single product, no bundled implementation services — applying this is genuinely simple: recognize revenue in the month the service is delivered, with no deferred revenue entry needed if billing and delivery happen in the same period.
Complexity increases significantly with annual or multi-year contracts, bundled offerings combining software with professional services, usage-based pricing, and variable consideration like tiered discounts or volume rebates.
MRR, ARR, and GAAP Revenue — Three Different Numbers
These three metrics measure genuinely different things, and using them interchangeably is a common, confusing mistake:
| Metric | What It Measures | Best Used For |
|---|---|---|
| MRR | Recurring revenue converted to a monthly figure | Operational dashboards, month-over-month trend tracking |
| ARR | MRR × 12, a forward-looking annual run-rate | Annual planning, board decks, investor communication |
| GAAP Revenue | Actual recognized revenue under ASC 606 | Financial statements, tax filings, anything touching an auditor |
Why ARR and GAAP Revenue Drift Apart
This is worth understanding specifically so it doesn't look like an error when it shows up: ARR and GAAP revenue are not meant to reconcile to the penny, and the gap between them tends to widen over time for two structural reasons:
- Contract modifications — upgrades, downgrades, and add-ons each trigger a recalculation under ASC 606's five-step model, reallocating the transaction price across performance obligations in ways that have no direct ARR equivalent
- Discount allocation — a classic example: selling a $100,000 implementation package plus a $100,000 annual subscription, but discounting implementation to $0 as a sales incentive. Management might count $100,000 in ARR for the subscription; under ASC 606, that discount gets allocated across both performance obligations, meaning recognized subscription revenue could be meaningfully lower than the ARR figure suggests — with neither number being "wrong."
The two numbers should stay in the same general order of magnitude and draw from the same underlying data — but forcing them to match exactly wastes time better spent elsewhere.
The Rule of 40
A widely used efficiency benchmark in SaaS: revenue growth rate plus profit margin should equal or exceed 40%. A company growing 30% with a 10% margin passes; one growing 15% with a -10% margin does not. Investors use this as a quick sanity check on whether growth is happening responsibly — clean, ASC 606-compliant revenue recognition is what makes this metric trustworthy in the first place, rather than an artifact of inconsistent recognition timing.
Why This Matters for Fundraising
Revenue recognition practices get specifically scrutinized during investor due diligence. Improperly recognized revenue — even if genuinely unintentional — erodes credibility with investors and their accountants, and can meaningfully delay or derail a fundraising round. Since MRR and ARR are supposed to be based on recognized recurring revenue (not raw cash collected), conflating the two produces metrics that don't hold up under real scrutiny, leading to decisions built on numbers that don't actually reflect the business.
When Spreadsheets Stop Working
A consistent pattern across SaaS companies: manual revenue recognition tends to break down around $3-5 million in ARR. At that point, deferred revenue schedules across hundreds of customers, mid-contract modifications, multi-entity consolidation, and usage-based billing components become too complex and error-prone for spreadsheets or general-purpose platforms like QuickBooks to track reliably — pushing companies toward SaaS-specific billing and revenue recognition tools that automate ASC 606 compliance directly.
FAQ
Deferred revenue (also called unearned revenue) is cash collected for a subscription that hasn't been delivered yet. It sits on the balance sheet as a liability, not revenue, because the company still owes the customer the service — if the company failed to deliver, it would owe that money back. As the subscription period elapses, deferred revenue converts into recognized revenue on the income statement.What is deferred revenue in SaaS accounting?
MRR (Monthly Recurring Revenue) and ARR (Annual Recurring Revenue, generally MRR times 12) are forward-looking run-rate metrics used for operational tracking and investor communication. GAAP revenue is what's actually recognized on the income statement under ASC 606, based on performance obligations delivered. These numbers are not meant to reconcile to the penny — a widening gap between ARR and GAAP revenue is often just contract modifications and discount allocation, not an error.What's the difference between MRR, ARR, and GAAP revenue?
ASC 606 is the US accounting standard governing how companies recognize revenue from customer contracts, using a five-step model. For a straightforward SaaS business — monthly billing, single product, no bundled services — applying it is genuinely simple: recognize revenue in the month the service is provided. Complexity increases significantly with annual contracts, bundled implementation services, usage-based pricing, and tiered discounts.What is ASC 606 and does every SaaS company need to worry about it?
Contract modifications — upgrades, downgrades, add-ons — force recalculations under ASC 606's five-step model each time they happen, while ARR is typically a simpler forward-looking snapshot. Discount allocation is a common source of mismatch too: a discount applied to one part of a bundled deal gets reallocated across all performance obligations under ASC 606, which can make recognized revenue look meaningfully different from the headline ARR number for the same deal.Why do ARR and GAAP revenue often not match?
The Rule of 40 states that a healthy SaaS company's revenue growth rate plus profit margin should equal or exceed 40% — for example, 30% growth plus 10% margin. Investors use it as a quick efficiency check on whether a SaaS business is scaling responsibly rather than just growing fast while burning unsustainable amounts of cash.What is the Rule of 40 in SaaS?
A consistent pattern shows up around $3-5 million in ARR: manual deferred revenue schedules, mid-contract modifications, and multi-entity or usage-based billing become too complex and error-prone to track reliably in spreadsheets or general-purpose accounting software, pushing companies toward SaaS-specific billing and revenue recognition platforms.When does a SaaS company typically outgrow spreadsheets or QuickBooks for revenue recognition?
For the broader entity-structure question that comes up right around the same funding stage, see our LLC vs. S-Corp vs. C-Corp comparison.
Conclusion
The founders who get SaaS accounting right aren't the ones with the most sophisticated tooling from day one — they're the ones who internalize early that cash, MRR/ARR, and GAAP revenue are three genuinely different numbers answering three different questions, and who build a deferred revenue habit before the first annual contract makes skipping it expensive. Get that foundation right, and the rest — clean audits, credible investor conversations, metrics that actually hold up — follows from it.
If you'd like help setting up ASC 606-compliant revenue recognition and deferred revenue tracking for your SaaS business, get in touch for a free consultation.