Deferred revenue is one of the largest balance sheet items for subscription businesses and the source of the most frequent accounting errors. This guide covers what deferred revenue actually represents, how it's tracked and released, current vs long-term classification, and common mistakes that catch auditors' attention.
Deferred revenue (also called unearned revenue) is a liability on the balance sheet representing cash received for goods or services not yet delivered. It's a promise to deliver something to the customer in the future.
When a customer pays for a 12-month SaaS subscription upfront, the company receives cash but has only delivered day 1. The remaining 364 days of obligation sits as deferred revenue until delivered.
At cash receipt (customer pays $12,000 for 12-month subscription):
End of month 1 (revenue recognition for one month delivered):
Repeated monthly until contract ends. Final month's entry moves last $1,000 from deferred to recognized; deferred revenue balance for that contract reaches zero.
Deferred revenue is often the single largest balance sheet item for a SaaS company. For a company with $20M ARR and annual prepayment terms, deferred revenue at a typical point in the year is $8M–$15M. Getting this wrong materially misstates financials.
Deferred revenue gets split between current and long-term portions based on when it will be recognized:
Deferred revenue expected to be recognized within 12 months of balance sheet date. Classified in current liabilities.
Deferred revenue expected to be recognized beyond 12 months. Classified in non-current liabilities.
3-year subscription contract worth $108k with full upfront payment. At contract date (Jan 1, 2026):
Each month, $3k moves from deferred to recognized revenue. Additionally, each month, $3k shifts from long-term to current (maintaining the 12-month current portion). Until month 25, when the contract enters its last year and all remaining deferred revenue is current.
Current/long-term split needs review at every balance sheet date, not just at contract signing. Monthly reclassification from long-term to current is a standard month-end journal entry for contracts over 1 year.
Most common error for early-stage SaaS. Books $12k as revenue when customer pays, rather than spreading over 12 months. Results in overstated revenue and understated deferred revenue liability.
Customer upgrades from $500/mo to $800/mo mid-contract. Deferred revenue schedule needs adjustment to reflect new rate going forward. Missing modifications causes deferred revenue to drift from contractual reality.
Splitting current vs long-term at contract signing but not updating monthly. Over time, long-term balance should decrease as contract ages; current should stay at 12-months-forward. Companies that don't reclassify quarterly show incorrect liquidity presentation.
Implementation fees recognized at kickoff rather than over the service delivery period. ASC 606 typically requires implementation fees to be recognized over the longer of the service period or the customer relationship period if the implementation doesn't provide standalone value.
Customer cancels mid-contract with refund. Deferred revenue should be reduced (debit deferred revenue, credit cash for refund amount). Companies that don't process cancellations properly end up with zombie deferred revenue balances.
Contract in foreign currency needs special handling: deferred revenue balance revalued at each reporting date; revenue recognized at historical rate or current rate depending on policy; FX gain/loss tracked separately.
Gift cards, customer credits, and loyalty points have deferred-revenue-like characteristics but specific accounting rules (breakage estimates, expiration treatment). Not the same as subscription deferred revenue.
Related: ASC 606 revenue recognition, startup bookkeeping, offshore controller.
Related