Accounting

Revenue Recognition for SaaS and Subscription Businesses

ASC 606 changed how SaaS recognizes revenue. Here's the framework, what trips up small SaaS, and how to set up books that pass diligence.

By Aparna Devalla, CPA3 min · 5 slidesUpdated May 4, 2026

1 / 5

Under ASC 606, revenue is recognized when the customer receives the promised benefit — not when cash arrives.
For SaaS: customer benefit accrues ratably over the subscription period. Annual prepaid contract = 1/12th recognized per month.
Cash collected in advance is deferred revenue (a liability), not revenue.
Critical for SaaS: getting this wrong inflates revenue, distorts margins, and breaks every metric (MRR, ARR, gross margin, customer LTV).

1. Identify the contract — written, signed, with enforceable rights.
2. Identify performance obligations — distinct deliverables the customer is paying for.
3. Determine transaction price — what the customer agreed to pay; allocate variable consideration.
4. Allocate price across obligations — if a contract includes setup + ongoing access, split the price across both.
5. Recognize revenue when each obligation is satisfied — over time for SaaS; at a point in time for one-shot deliverables.

Setup or onboarding fees: not generally distinct from the ongoing service — recognize over the customer's expected life, not upfront.
Multi-year contracts: revenue is recognized ratably across the full term, not all in year 1.
Discounts and refunds: estimate at contract inception and reduce revenue accordingly; don't wait for the actual refund.
Usage-based pricing: recognize when usage occurs, not at billing date. Estimate variable consideration carefully.
Implementation services: if material and distinct, recognize separately as services revenue (often lower margin).

Set up a deferred revenue ledger — every customer with a prepaid contract has a balance to amortize.
Monthly journal entry: debit deferred revenue, credit revenue, for the portion earned that month.
Tools: Maxio (formerly SaaSOptics), Stripe Tax + Stripe Revenue Recognition, Chargebee. For small SaaS, a spreadsheet can work for the first year.
Reconcile monthly: cash collected = revenue + change in deferred revenue.
Diligence killer: a SaaS company with no deferred revenue ledger will spend weeks reconstructing it for any serious capital event.

Investors, lenders, and acquirers expect ASC 606-compliant revenue recognition — no exceptions.
A clean deferred revenue waterfall (showing how each contract recognizes over time) is the single most useful artifact in financial diligence.
Be prepared to defend assumptions: customer churn rate driving setup-fee amortization, refund estimates, variable consideration calculations.
Get an accountant who has SaaS experience BEFORE you raise capital — fixing books retroactively under deal pressure is expensive and risky.
Note: for venture-backed SaaS, our sister practice StartupCFO.ai is purpose-built for this; for non-venture SaaS, Rubric Financial handles it directly.