Deferred Revenue and Unearned Revenue: Journal Entries for SaaS, Subscriptions, and Gift Cards
Deferred revenue (unearned revenue) journal entries walk through revenue recognition for subscriptions, SaaS, gift cards, and pre-payments with full worked examples.
Deferred revenue (unearned revenue) journal entries walk through revenue recognition for subscriptions, SaaS, gift cards, and pre-payments with full worked examples.
Learning Objectives
- ✓Distinguish deferred revenue (liability) from earned revenue (income statement)
- ✓Apply the 5-step ASC 606 revenue recognition model to deferred revenue
- ✓Record deferred revenue journal entries for subscriptions, SaaS, and pre-payments
- ✓Recognize gift card revenue including breakage
- ✓Handle refund scenarios and contract modifications
1. Why Deferred Revenue Is a Liability, Not Revenue
Deferred revenue (also called unearned revenue) appears on the balance sheet as a LIABILITY, not revenue on the income statement. This trips up many students. The logic: when a customer pays you before you deliver the goods or services, you now owe them something — either delivery of the product, performance of the service, or (if things go wrong) a refund. Until you have delivered what was paid for, the cash received represents an obligation to the customer, not earned income. The revenue recognition principle under ASC 606 requires that revenue be recognized when (or as) the performance obligation is satisfied — that is, when control of the good or service transfers to the customer. If a customer pays $1,200 on January 1 for a 12-month software subscription, you have not satisfied the performance obligation on January 1. You will satisfy it over 12 months as you provide access. On January 1, you record a liability (deferred revenue) of $1,200. Each month as service is delivered, you convert $100 of that liability into revenue. The balance sheet impact is important: growing deferred revenue is generally a GOOD sign for SaaS and subscription businesses because it reflects future revenue already contracted. Investors and analysts closely watch deferred revenue as a leading indicator of future recognized revenue.
Key Points
- •Deferred/unearned revenue sits on balance sheet as a liability until earned
- •Revenue is recognized as performance obligations are satisfied, not when cash is received
- •Growing deferred revenue can signal healthy future recognized revenue in subscription businesses
- •Failure to defer revenue properly violates ASC 606 and GAAP matching principle
2. The 5-Step ASC 606 Model Applied to Deferred Revenue
ASC 606 requires revenue recognition to follow a 5-step framework: 1. Identify the contract with the customer. 2. Identify the performance obligations in the contract. 3. Determine the transaction price. 4. Allocate the transaction price to the performance obligations. 5. Recognize revenue when (or as) the performance obligations are satisfied. Applied to a SaaS subscription: - Step 1: A 12-month subscription agreement signed with a customer on January 1. - Step 2: One performance obligation — providing software access for 12 months. - Step 3: Transaction price is the $1,200 annual fee paid upfront. - Step 4: $1,200 is allocated to the single performance obligation. - Step 5: Revenue is recognized ratably over 12 months as access is provided (since access is a continuous performance obligation with even delivery over time). Applied to a gift card: - Step 1: Customer purchases gift card for $100 on December 15. - Step 2: Performance obligation is providing merchandise equal to the card's face value when redeemed. - Step 3: Transaction price is $100. - Step 4: Full $100 to the single performance obligation. - Step 5: Revenue recognized upon redemption. Separately, estimated breakage (portion likely never redeemed) recognized based on historical redemption patterns proportionally. Applied to annual maintenance contracts bundled with software: - Step 1: Contract includes software license + 12 months of maintenance. - Step 2: Two performance obligations — software license (delivered upfront) and maintenance (delivered over time). - Step 3: Total transaction price. - Step 4: Allocate transaction price to the two obligations based on relative standalone selling prices. - Step 5: Software portion recognized immediately (or at delivery date); maintenance portion recognized ratably over 12 months.
Key Points
- •ASC 606 is the controlling standard for revenue recognition under US GAAP
- •All revenue recognition follows the same 5-step framework regardless of industry
- •Multi-element contracts require allocating transaction price across obligations
- •Revenue is recognized over time for services delivered continuously, at a point in time for products
3. Worked Example 1: SaaS Annual Subscription Paid Upfront
Setup: On January 1, 2026, a customer signs a 12-month SaaS subscription and pays $1,200 upfront. Software access is provided for all 12 months evenly. Step 1: Record cash receipt on January 1. Dr. Cash $1,200 Cr. Deferred Revenue $1,200 At January 1, the balance sheet shows: - Cash increased $1,200 - Deferred Revenue (liability) increased $1,200 - No revenue yet recognized on the income statement Step 2: Monthly revenue recognition. At the end of each month, recognize one-twelfth (1/12) of the total = $100 per month. January 31: Dr. Deferred Revenue $100 Cr. Subscription Revenue $100 February 28: Dr. Deferred Revenue $100 Cr. Subscription Revenue $100 And continuing through December 31. By year-end: - Deferred Revenue: $0 (fully recognized) - Subscription Revenue: $1,200 total recognized over the year Balance sheet impact over the year: Cash stays at $1,200 (or changes based on other activity), Deferred Revenue declines $100 per month from $1,200 to $0. Income statement impact: $100 of subscription revenue recognized each month, $1,200 total annual revenue from this customer. Common student error: recognizing full $1,200 revenue on January 1 when cash is received. This overstates Q1 revenue and understates Q2-Q4. It also creates a mismatch with the matching principle (revenue matched with delivery period).
Key Points
- •Upfront payment creates deferred revenue liability, not revenue
- •Revenue recognized ratably (straight-line) as service is delivered over time
- •Monthly entries reduce liability and increase revenue by equal amounts
- •Full year produces correct matching of revenue to service period
4. Worked Example 2: Multi-Year SaaS with Escalating Pricing
Setup: On January 1, 2026, customer signs a 3-year SaaS contract. Payment schedule: $10,000 on Jan 1, 2026; $12,000 on Jan 1, 2027; $14,400 on Jan 1, 2028. Service provided evenly over 36 months. Under ASC 606, the total transaction price is fixed but payment timing is different from delivery timing. Total transaction price: $10,000 + $12,000 + $14,400 = $36,400 over 36 months. Monthly revenue recognition: $36,400 / 36 = $1,011.11 per month. Year 1 journal entries: January 1, 2026 (cash received): Dr. Cash $10,000 Cr. Deferred Revenue $10,000 January 31 (and monthly thereafter): Dr. Deferred Revenue $1,011.11 Cr. Subscription Revenue $1,011.11 By December 31, 2026: - Deferred Revenue balance remaining from 2026 payment: $10,000 − (12 × $1,011.11) = $10,000 − $12,133.32 = negative balance That negative balance signals we've recognized more revenue than we've received cash for. This gives rise to a Contract Asset on the balance sheet. Specifically: - Revenue recognized in 2026: $12,133.32 (12 months × $1,011.11) - Cash received in 2026: $10,000 - Difference: $2,133.32 → becomes a Contract Asset (receivable for future billing) January 1, 2027 (cash received): Dr. Cash $12,000 Cr. Contract Asset $2,133.32 Cr. Deferred Revenue $9,866.68 This clears the contract asset built up in 2026 and creates new deferred revenue for months 13-24. Continuing the pattern through 2027 and 2028 produces: - Revenue recognition: even at $1,011.11/month throughout - Cash flow: follows payment schedule - Balance sheet: contract asset builds and clears as cash catches up This example illustrates why ASC 606 requires recognizing deferred revenue AND contract assets based on delivery pattern, not cash flow. The complexity is because payment timing doesn't match service delivery timing for multi-year escalating contracts.
Key Points
- •Multi-year contracts with escalating prices can create contract assets
- •Revenue recognition follows delivery pattern, not cash pattern
- •Total transaction price includes all fixed payments over contract term
- •Contract assets represent earned but unbilled revenue
5. Worked Example 3: Gift Cards with Breakage
Setup: On December 1, 2025, a retailer sells $10,000 in gift cards. Historical data shows 10% of gift cards are never redeemed (breakage). ASC 606 allows recognition of breakage in proportion to the pattern of rights exercised. Common approach: recognize breakage as gift cards are redeemed. Step 1: Record gift card sale (December 1, 2025): Dr. Cash $10,000 Cr. Gift Card Liability $10,000 Step 2: Record redemptions. In January 2026, customers redeem $3,000 of gift cards. Based on 10% expected breakage (90% redeemable), each $1 of redemption triggers breakage of $1/9 ≈ $0.111. Actually, there are multiple accepted methods. The simplest: proportional method — breakage recognized as a ratio to redemption. If historical redemption rate is 90% (meaning 10% breakage), the proportion method says for every $1 redeemed, recognize: - Revenue of $1 (customer bought merchandise for $1) - Breakage of $1 × (10/90) = $0.111 January 31, 2026 (assuming $3,000 redeemed): Dr. Gift Card Liability $3,000 Cr. Gift Card Revenue $3,000 Dr. Gift Card Liability $333 Cr. Breakage Revenue $333 Reasoning: customers redeemed $3,000 of their $10,000 gift card balance. Proportion method says $3,000 redeemed is 33.3% of the ultimate redemption total ($9,000 of $10,000 will ever be redeemed, the other $1,000 is breakage). 33.3% of breakage = $333 recognized. Alternative simpler method: wait-to-recognize breakage — recognize breakage only after extended period (24+ months of inactivity) suggests cards are unused. Balance sheet impact: Gift Card Liability starts at $10,000, decreases by $3,333 in January ($3,000 for revenue + $333 for breakage) to $6,667.
Key Points
- •Gift card sales create a liability, not revenue, until redeemed
- •Breakage (unredeemed portion) can be recognized based on historical patterns
- •Proportional method recognizes breakage alongside actual redemption
- •Retailers with significant gift card programs must estimate and record breakage
- •State escheat laws may require remitting unredeemed card values to the state in some jurisdictions
6. Customer Deposits and Progress Billing for Services
Setup: A service company receives a $20,000 deposit on March 1 for a 4-month consulting engagement ($5,000/month value). The remaining $0 is billed at end of engagement (deposit is full amount). March 1 (deposit received): Dr. Cash $20,000 Cr. Deferred Revenue (Customer Deposit) $20,000 At end of each month, as the service is provided: March 31: Dr. Deferred Revenue $5,000 Cr. Consulting Revenue $5,000 April 30: Dr. Deferred Revenue $5,000 Cr. Consulting Revenue $5,000 And so on. By June 30, all $20,000 is recognized as revenue; deferred revenue balance = $0. Progress billing scenario: $40,000 contract, billed as 25% at start, 50% at midpoint, 25% at completion. Services delivered evenly over 4 months. March 1: bill $10,000 (25%) Dr. Cash $10,000 Cr. Deferred Revenue $10,000 March 31 (recognize 1 month of service = $10,000 of $40,000 total): Dr. Deferred Revenue $10,000 Cr. Service Revenue $10,000 Actually by end of March, we've recognized $10,000 of revenue — but we've only billed $10,000. So deferred revenue is 0 and no contract asset yet. By end of April, we've recognized $20,000 total but only billed $10,000. Need $10,000 more revenue recognition but no additional deferred balance to draw from: Dr. Contract Asset (Unbilled A/R) $10,000 Cr. Service Revenue $10,000 May 1: bill $20,000 (50%) Dr. Cash $20,000 Cr. Contract Asset $10,000 Cr. Deferred Revenue $10,000 May 31 (recognize 1 more month = $10,000): Dr. Deferred Revenue $10,000 Cr. Service Revenue $10,000 June 1: bill $10,000 (25% final) Dr. Cash $10,000 Cr. Deferred Revenue $10,000 June 30 (final month recognition): Dr. Deferred Revenue $10,000 Cr. Service Revenue $10,000 By end of June: all $40,000 of revenue recognized, no deferred revenue balance, no contract asset. This illustrates how timing mismatches between billing and service delivery produce both deferred revenue (when billed ahead) and contract assets (when delivered ahead).
Key Points
- •Customer deposits are deferred revenue, not earned revenue
- •Progress billing can create deferred revenue or contract assets depending on timing
- •Revenue recognition follows service delivery pattern
- •Multi-stage billing requires careful reconciliation of billed vs delivered amounts
7. Refund Accounting and Contract Modifications
Refund scenario: Customer purchased a 12-month subscription for $1,200 on January 1. On July 1 (after 6 months), the customer cancels and receives a prorated refund of $600 for the remaining 6 months. Before cancellation (after 6 months of normal recognition): - Deferred Revenue balance: $600 - Revenue recognized to date: $600 At cancellation (July 1): Dr. Deferred Revenue $600 Cr. Cash (refund) $600 The deferred revenue balance is cleared against the refund. No income statement impact at cancellation because no revenue was recognized for the unused portion (the matching is already correct). Contract modification scenario: Customer upgrades mid-year. Initial 12-month subscription for $1,200 purchased January 1. On July 1 (6 months in), customer upgrades to premium tier at $150/month. They pay an additional $600 for the premium upgrade for the remaining 6 months. Analysis: the upgrade creates a new performance obligation (premium access for 6 months) at the standalone selling price. At July 1: Dr. Cash $600 Cr. Deferred Revenue $600 (for premium upgrade) Monthly from July 1 onwards: $100 base + $100 premium = $200 total revenue per month. Alternative modifications can be treated as contract termination and new contract, or as continuation with adjusted allocation. The treatment depends on whether the modification adds new goods/services at standalone selling prices (separate contract) or modifies existing obligations (cumulative catch-up or prospective allocation). Important for exams: identify whether the modification is: - Separate new contract (add new performance obligation at standalone price) - Termination of existing contract + new contract (different scope, different pricing) - Modification of existing contract with cumulative catch-up (retrospective adjustment) - Modification of existing contract with prospective recognition ASC 606 provides specific criteria for each, and the accounting treatment differs materially.
Key Points
- •Refunds reduce deferred revenue, not previously-recognized revenue
- •Prorated refunds work cleanly when revenue was recognized ratably
- •Contract modifications may be separate contracts or amendments — different accounting
- •Upgrade modifications often create new deferred revenue at the upgrade price
High-Yield Facts
- ★Deferred revenue is a current liability (or long-term if service period > 1 year)
- ★Revenue recognized when performance obligation satisfied, not when cash received
- ★ASC 606 governs all revenue recognition under US GAAP
- ★Multi-year contracts can create contract assets when delivery leads billing
- ★Gift card breakage can be recognized proportionally based on redemption
- ★Refunds reduce deferred revenue, not recognized revenue
- ★Growing deferred revenue signals committed future revenue for SaaS businesses
Practice Questions
1. A customer pays $600 on January 1 for a 6-month subscription. What journal entry on January 1 and February 28?
2. A retailer has sold $50,000 in gift cards. Historical breakage is 8%. Customers redeem $20,000. What is breakage revenue recognized?
3. On June 1, a company receives $3,600 for a 1-year maintenance contract. What is deferred revenue balance at year-end (Dec 31)?
4. SaaS company signs 2-year contract. Total $24,000 paid $10,000 upfront + $14,000 at start of year 2. Monthly revenue recognition over 24 months?
5. Why is deferred revenue called a 'liability' when you've already received the cash?
FAQs
Common questions about this topic
Deferred revenue: cash received BEFORE goods/services are delivered. Balance sheet: liability. Example: annual subscription paid upfront. Accrued revenue: goods/services DELIVERED before cash is received. Balance sheet: receivable (asset). Example: consulting work completed but not yet billed. They're mirror concepts — both involve timing mismatches but in opposite directions.
Yes — they're synonymous terms. 'Deferred revenue' is more common in modern US GAAP literature and IFRS. 'Unearned revenue' is more common in older textbooks and colloquial usage. Both refer to cash received in advance of service delivery, recorded as a liability until earned. No difference in accounting treatment.
Recognize revenue when (or as) the performance obligation is satisfied — that is, when control of the goods or services transfers to the customer. Services delivered over time (like subscriptions) recognize revenue ratably. Goods delivered at a point in time recognize revenue at delivery. If the customer has not yet received what they paid for, keep it deferred.
Yes. Any portion of deferred revenue that will be earned more than 12 months from the balance sheet date is classified as long-term deferred revenue. For example, a 3-year prepaid subscription has approximately 1/3 of its balance in current deferred revenue and 2/3 in long-term deferred revenue at the start. As months pass, more becomes current.
Refunds that occur after partial service delivery typically reduce deferred revenue (not recognized revenue) because the unused portion was held as liability. For subscription refunds: debit deferred revenue, credit cash. The customer received service for the months they used (already recognized as revenue); the refund is for the months they didn't use (which were still in deferred revenue). If you need to refund already-recognized revenue, that becomes a returns/allowance item that reduces current revenue.
Yes. Describe the scenario (subscription terms, gift card sales, multi-year contracts, contract modifications) and AccountingIQ walks through the ASC 606 analysis, identifies performance obligations, allocates transaction price, produces the journal entries step-by-step, and flags common errors. Especially useful for complex multi-period and multi-element contract problems. This content is for educational purposes only and does not constitute accounting advice.