.png)
Deferred Revenue Accounting: Recognition Schedules and Worked Examples
Deferred revenue is the accountant's answer to a simple problem: a customer paid you upfront for something you have not yet delivered. The cash is in the bank. The revenue belongs to a future period. Deferred revenue holds the balance until the service catches up.
Deferred revenue is a liability representing cash received from customers for goods or services that have not yet been delivered. Under accrual accounting, the cash collection does not create revenue — it creates an obligation to deliver. Revenue is recognized over time as the service is delivered, reducing the deferred revenue liability and increasing the revenue line.
Common cases include annual SaaS subscriptions paid upfront, conference sponsorships paid before the event, retainers, gift cards, and event deposits. The accounting pattern is consistent: cash in creates deferred revenue; service delivered reduces deferred revenue and recognizes revenue.
Key takeaways
- ✓ Deferred revenue is a liability — cash received for services not yet delivered.
- ✓ Recording cash receipt creates the liability; delivering the service draws it down and recognizes revenue.
- ✓ Recognition patterns include straight-line (most subscriptions), point-in-time (single-event deliveries), and milestone-based (services engagements).
- ✓ Deferred revenue balances should be reconciled to a contract waterfall every period — the schedule of remaining performance obligations across customers.
- ✓ Most deferred revenue work in QBO is mechanical and recurring, making it well-suited to automation.
- ✓ The underlying authority for revenue recognition under US GAAP is the FASB revenue framework; under IFRS, the corresponding IFRS revenue standard.
What deferred revenue is
Deferred revenue is a liability. Specifically, it is the obligation to deliver goods or services that a customer has already paid for. The cash is in the bank. The product or service has not yet been delivered. Until that delivery happens, accrual accounting treats the cash as a liability — a promise to perform — rather than revenue.
The conceptual hurdle is that "deferred revenue" sounds like it should be revenue. It is not. Revenue is recognized when goods or services are delivered. Until then, cash received in advance creates a payable to the customer in the form of future delivery. That payable is what sits on the balance sheet as deferred revenue.
Common examples
Deferred revenue shows up wherever a business collects payment before delivering:
- Annual SaaS subscriptions paid upfront. The dominant case in software businesses. A customer pays for twelve months on day one; revenue is recognized ratably across the twelve months of service.
- Conference sponsorships paid before the event. A $30,000 sponsorship paid in June for an October conference is deferred revenue from June through September, then fully recognized in October when the event occurs.
- Event deposits. A wedding venue collects a 50% deposit in January for a July event. The deposit is deferred revenue from January through June; revenue is recognized in July when the event happens.
- Retainers paid upfront. A six-month consulting retainer billed and collected at the start of the engagement; revenue recognized as work is performed.
- Gift cards and customer credits. Cash received for something the customer can redeem later; revenue recognized when redemption occurs or after a defined breakage period.
- Annual maintenance contracts. Service agreements billed annually but consumed across the year.
The pattern in every case: cash in today, delivery (and therefore revenue) spread across or occurring in some future period.
Journal entries
Two entries handle a typical deferred revenue transaction.
Entry 1: Cash collection. When the customer pays.
| Account | Debit | Credit |
|---|---|---|
| Cash | $24,000 | |
| Deferred revenue (liability) | $24,000 |
Entry 2: Monthly revenue recognition. Posted at the end of each delivery period.
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue (liability) | $2,000 | |
| Revenue | $2,000 |
That second entry is repeated each month across the period of service. After twelve recognitions, the deferred revenue liability is zero and total recognized revenue equals the original $24,000 collected.
Recognition schedules
The pattern of recognition follows the pattern of delivery, governed by the principles in ASC 606 revenue recognition guidance. Three patterns cover most cases:
Straight-line (ratable). Equal recognition each period across the term of service. Twelve-month SaaS: $2,000 per month. This is the default whenever the service is delivered continuously and roughly evenly across time.
Point-in-time. Full recognition on the date of delivery. A $30,000 conference sponsorship paid in June for an October event: zero recognition June–September, $30,000 recognition in October. Used whenever the customer derives benefit at a single point rather than over time.
Milestone-based. Recognition tied to specific deliverables. A consulting engagement priced at $100,000 with three accepted milestones — discovery ($30K), build ($50K), launch ($20K) — recognizes revenue as each milestone is accepted by the customer. Used in professional services and project-based work.
Choosing the right pattern is a question of what the customer is actually paying for. SaaS subscriptions are ratable because the customer gets continuous access. Event sponsorships are point-in-time because the customer derives benefit on the day of the event. Engineering services are usually milestone-based because the customer accepts and benefits from specific deliverables.
A worked SaaS example
For a $24,000 annual SaaS contract collected January 1:
| Month | Opening deferred | Recognition | Closing deferred | Cumulative revenue |
|---|---|---|---|---|
| Jan | $24,000 | $2,000 | $22,000 | $2,000 |
| Feb | $22,000 | $2,000 | $20,000 | $4,000 |
| Mar | $20,000 | $2,000 | $18,000 | $6,000 |
| Apr | $18,000 | $2,000 | $16,000 | $8,000 |
| May | $16,000 | $2,000 | $14,000 | $10,000 |
| Jun | $14,000 | $2,000 | $12,000 | $12,000 |
| Jul–Dec | $12,000 | $2,000 × 6 | $0 | $24,000 |
The cash event happened once on January 1. The recognition happens twelve times across the year. Throughout, the schedule tells you exactly what should be in deferred revenue on any date.
Reconciliation and reporting
The deferred revenue balance is one of the most heavily scrutinized accounts on the balance sheet, especially in SaaS or subscription businesses where it represents future contracted revenue.
Every period, three reconciliations matter:
- GL balance to contract waterfall. The total in the deferred revenue GL account should match the sum of remaining performance obligations across all customer contracts.
- Recognized revenue to delivery records. The revenue recognized each period should match the schedule of services delivered — customer-by-customer or contract-by-contract.
- Rollforward. Opening balance + new bookings (cash in for future delivery) − revenue recognized = closing balance. The rollforward is the audit-friendly summary.
For subscription businesses, deferred revenue is also a leading indicator of revenue health. A growing deferred revenue balance signals expanding contracts; a shrinking one signals churn or duration shortening.
Deferred revenue vs unbilled revenue
These two concepts are easy to confuse because both involve a timing gap between revenue and cash.
- Deferred revenue is cash received before revenue is recognized. The liability sits on the balance sheet until the service is delivered.
- Unbilled revenue (also called contract assets) is the opposite — service has been delivered and revenue recognized, but the customer has not yet been billed. The asset sits on the balance sheet until invoicing catches up.
A professional services firm working under a fixed-fee engagement often has both: deferred revenue for milestones billed in advance, unbilled revenue for work performed ahead of the next billing event.
Automating deferred revenue recognition
Deferred revenue recognition is the textbook case for accrual automation. The math is predictable, the recognition pattern is set when the contract is signed, and the entry repeats every period across the contract term. None of it requires judgment after the schedule is established.
Accruer handles deferred revenue recognition inside QBO the same way it handles prepaid amortization. You set up the contract once with the start date, end date, total amount, and recognition pattern; Accruer calculates, posts, and substantiates the monthly entry. The tool understands locked periods (it will not overwrite closed months when a new contract is added retroactively) and recalculates correctly when contracts change mid-stream — a twelve-month deal that becomes a nine-month deal, with two months already locked, gets its remaining schedule rebuilt against the new total.
Common mistakes
Recognizing revenue when cash is collected
The most common mistake on a cash-to-accrual transition. An annual contract paid upfront should create deferred revenue, not twelve months' worth of revenue in the collection month.
Off-by-one-day recognition schedules
A SaaS contract written as 01/01 to 01/01 of the following year spans twelve months and one day — the recognition engine will allocate a small slice into a thirteenth month. Standardize on either MM/DD/YYYY for prorated terms or month names for whole-month spans.
Mixing point-in-time and ratable items in one entry
A bundled deal with a SaaS subscription plus a one-time setup fee needs two recognition schedules: ratable for the subscription, point-in-time for the setup. Lumping them together produces an incorrect revenue curve.
Forgetting to true up at contract changes
When a contract is upsized, downsized, or canceled mid-term, the deferred revenue schedule has to be rebuilt against the new total. Continuing the original schedule produces wrong revenue from the change date forward.
No reconciliation between GL balance and contract waterfall
The deferred revenue GL balance should equal the sum of remaining performance obligations across all contracts. When it does not, either contracts are missing from the schedule or recognized revenue was booked incorrectly.
Automate deferred revenue recognition in QBO
Accruer handles deferred revenue waterfalls the same way it handles prepaid amortization — set the schedule once, the monthly entries post themselves. A 20-minute demo will show you exactly how it fits your close.
Book a demoFrequently asked questions
Is deferred revenue a liability or an asset?
A liability. It represents the obligation to deliver goods or services that a customer has already paid for.
What is the journal entry for deferred revenue?
On collection: debit cash, credit deferred revenue (liability). On recognition: debit deferred revenue, credit revenue. The liability is drawn down to zero across the period of service.
Is deferred revenue the same as unearned revenue?
Yes — the two terms refer to the same balance sheet account. Some companies use one term, some the other. Both mean cash received before delivery.
What is the difference between deferred revenue and accrued revenue?
Deferred revenue is cash received before delivery (liability). Accrued revenue — sometimes called unbilled revenue or contract assets — is delivery before invoicing (asset). They are opposites.
How is deferred revenue recognized?
Through a recurring journal entry each period: debit deferred revenue, credit revenue, in an amount that matches the pattern of service delivery. Ratable for subscriptions, point-in-time for single events, milestone-based for project work.
Does QuickBooks Online track deferred revenue?
Yes, as a balance sheet account. But QBO does not generate the recognition entries on its own — each monthly recognition requires a manual journal entry. Accruer adds automation.
What standard governs deferred revenue accounting?
Under US GAAP, the governing standard for revenue recognition (and therefore deferred revenue) is ASC 606 revenue recognition guidance. Under IFRS, the corresponding IFRS revenue standard. Both arrive at the same five-step model for determining when revenue is earned.
Where to go next
Read these next:
- The complete accrual accounting pillar
- Revenue recognition rules under accrual
- Automating accruals in QuickBooks Online
- Prepaid expenses (the customer-side mirror)
Related Resources
Sources & References
- FASB revenue recognition guidance — see ASC 606 on fasb.org.
- IRS guidance on accounting periods and methods — see irs.gov.
- IASB revenue recognition standard under IFRS — see ifrs.org.
- AICPA, Audit and Accounting Guide.
- FinOptimal Managed Accounting practice — implementation data across 50+ client environments, 2024–2026.
.png)
.png)
.png)