Money you have but haven’t earned
Deferred revenue solves a problem as old as the prepayment: what do you do, in your books, with money a customer has handed you for something you haven’t delivered yet? Take a magazine subscription — the customer pays $120 in January for twelve monthly issues. The publisher has the cash, but it hasn’t earned it; it owes the customer eleven more issues. To call that $120 “revenue” in January would be to claim a year’s performance in a single month and leave the next eleven months looking empty. Deferred revenue is the accounting that fixes this: the $120 is recorded not as revenuebut as a liability — an obligation to deliver — and it’s converted to revenue a twelfth at a time as each issue ships.
This concept has always existed wherever customers paid in advance, but it has exploded in importance with the modern economy. Subscriptions, SaaS, annual software licenses, retainers, prepaid services, gift cards, maintenance contracts — an enormous and growing share of business now involves getting paid before delivering, often for a year or more at a time. For these businesses, deferred revenue isn’t a footnote; it’s frequently one of the largest items on the balance sheetand the entire mechanism by which their revenue gets recognized correctly over time. Deferred revenue is what enforces the revenue recognition principle in practice: it’s the holding account that keeps unearned cash out of revenue until it’s actually earned.
What is deferred revenue?
Deferred revenue (also called unearned revenue, or a “contract liability” under ASC 606) is cash a business has received for goods or services it hasn’t yet delivered. It is recorded as a liability on the balance sheet — an obligation to deliver — and converted to revenue as the goods or services are provided.
When a customer pays in advance, the business gets cash but takes on an obligation: it now owes the customer the product or service. That obligation is deferred revenue — a liability, not revenue, despite the cash being in hand. As the business delivers (ships the issues, provides the months of service, completes the work), it satisfies its obligation, and the deferred revenue is released to revenue in step with that delivery, following the ASC 606 principle that revenue is recognized when earned. Mechanically, this runs on a release schedule — the total amount divided across the delivery periods, recognized incrementally until the liability reaches zero. Deferred revenue is the liability counterpart of the revenue recognition rule: where the revenue page asked when is it earned?, deferred revenue is the account that holds the money until the answer is “now.”
What does deferred revenue actually mean?
Deferred revenue means you have the cash, but you still owe the work — and accounting insists on treating it that way until the work is done. It’s one of the clearest illustrations of the gap between cash and revenue: the money is in the bank (good for cash flow), but it isn’t yours to claim as earnings yet, because you haven’t delivered what the customer paid for. So it sits as a liability — a promise on the balance sheet — and only becomes revenue as you fulfill the promise. This is why a business can be flush with cash from prepayments and still have modest recognized revenue: the cash arrived, but the earning is still ahead.
The structurally interesting thing about deferred revenue is that it’s a liability unlike most others, and understanding this is the key to it. Most liabilitiesare discharged by paying cash — you owe a supplier, you pay them, the liability goes away. Deferred revenue is discharged by delivering — you owe the customer a service, you provide it, and the liability converts not into a cash payment but into revenue. It’s a self-releasing liability that shrinks over time as you earn it, flowing off the balance sheet and onto the income statement. That makes deferred revenue the bridge between the two statements for prepaid business: cash comes in and parks as a balance-sheet liability, then releases gradually as income-statement revenue as the obligation is met. For the coffee shop selling a $200 prepaid coffee card: the $200 is deferred revenue (a liability) when sold — the shop owes $200 of coffee — and it becomes revenue cup by cup as the customer redeems it, until the card is spent and the liability is zero.
Where does deferred revenue sit in GAAP?
A contract liability under ASC 606. Deferred revenue is the balance-sheet companion to the ASC 606 revenue recognition model. Under ASC 606, when a customer pays (or has an unconditional obligation to pay) before the entity transfers the promised goods or services, the entity records a contract liability — the formal ASC 606 term for what’s long been called deferred or unearned revenue. It’s recognized as revenue only as the performance obligations are satisfied, following the five-step model. IFRS 15 treats contract liabilities identically.
The schedule and the roll-forward. Operationally, deferred revenue lives in a schedule that tracks, for every contract, how much was received, how much has been recognized, and how much remains deferred. The integrity of that schedule rests on a simple identity that must hold every period:
opening deferred revenue + new billings − revenue recognized = closing deferred revenue
If that equation doesn’t balance, something is wrong — revenue recognized that wasn’t earned, billings missed, or a schedule error. This roll-forward is the core control over deferred revenue, and a critical discipline is that the schedule must be tied to contracts, not invoices — because the contract defines the obligation and therefore the earning, while an invoice is just a billing event. The deferred-revenue schedule is, in practice, the artifact auditors scrutinize most when revenue recognition is at issue, because it’s where the timing of revenue is laid bare.
Where it sits on the balance sheet. Deferred revenue is a current liability to the extent it’ll be earned within a year, with any portion earned later shown as long-term. It therefore reduces working capital and the current ratio— though for subscription businesses a large, growing deferred-revenue balance is a healthy sign, indicating strong prepaid forward commitments. The mirror image is the contract asset (accrued or unbilled revenue): revenue earned but not yet billed — the opposite timing difference.
Where does deferred revenue matter most?
Deferred revenue dominates wherever customers pay before delivery.
| Industry / model | Why prevalent | Recognition pattern |
|---|---|---|
| SaaS / subscriptions | Annual/monthly prepayment | Released ratably over the subscription term |
| Software licenses & maintenance | Upfront license + support | Split: license at delivery, support over time |
| Media / publishing | Prepaid subscriptions | Released as issues/access delivered |
| Services & retainers | Advance payment for future work | Released as work is performed |
| Gift cards / prepaid plans | Cash now, redemption later | Released on redemption (plus breakage estimates) |
(Rows reflect practitioner framing of where deferred revenue carries the most weight, not a vendor ranking.)
How is deferred revenue handled in QuickBooks, Xero, Sage, and Zoho Books?
Recording deferred revenue is easy; releasing it correctly over time is where the work lives — and where the base platforms need help.
- QuickBooks Online, Xero, Sage, Zoho Books. When cash is received in advance, it’s recorded to a deferred revenue (liability) account rather than revenue. Releasing it then happens via recurring journal entries or scheduled entries that move a portion from the liability to revenue each period — or via a dedicated revenue-recognition module/tool (common for SaaS) that automates the schedule.
- The schedule is the real deliverable. Whether in a tool or a spreadsheet, the deferred-revenue schedule — contract by contract, showing amount received, recognized to date, and remaining deferred — is what actually controls recognition. The base accounting platforms don’t natively maintain this for complex contracts, which is why it’s often run alongside the ledger and reconciled to it.
- The reconciliation. Each period, the schedule’s roll-forward (opening + billings − recognized = closing) must tie to the deferred-revenue balance in the GL. When it doesn’t, either the schedule or the ledger is wrong — and finding which is core deferred-revenue work.
The structural lesson: the software makes parking cash as deferred revenue straightforward, but releasing it correctly requires a maintained schedule and a monthly reconciliation. The release is mechanical once the schedule is set — but setting the schedule correctly (from the contract) and reconciling it faithfully is the discipline.
How do CPA firms use deferred revenue?
For a CPA firm, deferred revenue is where it operationalizes the revenue recognition judgment. Having determined (per ASC 606) how a client’s contracts are recognized, the firm sets up the deferred-revenue schedule that executes that treatment over time: recording prepayments as liabilities, releasing them to revenue on the right pattern, and reconciling the schedule to the GL each period. In close work, releasing the period’s earned portion and reconciling the roll-forward is a standard month-end task. In review and audit, the deferred-revenue schedule is a primary focus — auditors test it hard because it’s where revenue timing is most visible and most manipulable. In advisory, the firm helps clients (especially SaaS and subscription businesses) understand and manage their deferred-revenue balance as the leading indicator it is.
The questions a firm asks about deferred revenue are timing-and-control questions: is prepaid cash correctly sitting in deferred revenue (not prematurely in revenue), is it being released on the right schedule tied to the contract, does the roll-forward reconcile to the GL, and is the balance behaving sensibly relative to billings and delivery.
How does deferred revenue work in offshore accounting?
Deferred revenue is where the hardest judgment in accounting becomes work an offshore team can do superbly — and seeing why completes the picture the revenue page opened. Revenue recognition, that page established, is the single biggest judgment in accounting, requiring onshore knowledge the offshore team lacks (the contract terms, whether delivery actually happened), and therefore a firm-and-client-owned decision the offshore team must never make. That could leave the impression that offshore teams have little role in revenue at all. Deferred revenue corrects that impression precisely: it is the account where the firm’s recognition judgment gets translated into a recognition schedule, and a schedule is mechanical, repeatable, rules-bound work — exactly what offshores well. The division is clean and it is the heart of the matter. The firm decides the recognition treatment (the judgment); the offshore team executes it through the deferred-revenue schedule (the mechanics). Revenue is where judgment lives and cannot be offshored; deferred revenue is where that judgment, once made, becomes the disciplined monthly execution that can be — and where the offshore team adds real, reliable value.
This makes deferred revenue the enforcement account for the revenue page’s central discipline. That page’s instruction was: defer by default, never recognize too early, keep unearned amounts out of revenue. Deferred revenue is where “defer by default” stops being a principle and becomes a balance — the holding account whose entire job is to keep money out of revenue until it’s genuinely earned. The offshore team’s role is therefore precise and powerful: keep the money in the deferred-revenue liability until the firm-set schedule says it’s earned, and release it only on that schedule. Every dollar the offshore team correctly holds in deferred revenue is a dollar of revenue not recognized too early — which means the offshore team, running the schedule faithfully, is the operational guardian of conservative recognition. The hardest judgment in accounting (when is revenue earned) was made once, by the firm, at the contract; the offshore team then protects that judgment every month by releasing strictly to schedule and never accelerating. This is the mechanized form of “defer by default”: the discipline lives in an account, and the offshore team’s job is to honor it.
The control that makes this checkable is the roll-forward reconciliation, and it is exactly the kind of objective, mechanical verification that offshore work depends on. The identity —
opening deferred revenue + billings − revenue recognized = closing deferred revenue
— must hold every period, and the offshore team reconciles it monthly, contract by contract, tying the schedule to the GL. This is the deferred-revenue analog of bank reconciliation: an objective equation that either balances or doesn’t, giving a reviewer a clean, verifiable artifact rather than a judgment to second-guess. And it is more than housekeeping, because the roll-forward is where premature recognition becomes visible. If revenue is recognized faster than delivery warrants — the classic too-early manipulation the revenue page flagged — the deferred-revenue balance drains faster than the remaining obligations justify, and the schedule stops tying to the contracts. The roll-forward catches it: a deferred-revenue balance that’s falling too fast relative to billings and delivery is the fingerprint of revenue being pulled forward. So the offshore team running the deferred-revenue schedule with discipline isn’t just executing mechanics — it’s operating the very control that detects the most common revenue error, which is why the deferred-revenue schedule is the artifact auditors scrutinize most, and why it should be the offshore team’s most carefully maintained deliverable.
Two disciplines complete the offshore picture, both sharpening the revenue page’s principles into mechanics. First, tie the schedule to contracts, not invoices — the direct operational form of the revenue page’s “an invoice is not revenue.” Because the offshore team can see invoices easily and contracts less easily, the temptation is to build the release schedule off billing events; but billing and earning are different, and a schedule built on invoices will recognize on the wrong rhythm. The schedule must be built from the contract’s delivery terms (which the firm provides), not from when invoices happen to be raised. Second, never accelerate the release, and escalate any pressure to do so — releasing deferred revenue faster than the schedule is the mechanical equivalent of recognizing revenue too early, and it’s a decision the offshore team is never authorized to make on its own; a request or apparent reason to release faster is a flag for the firm, not a call for the offshore team. Put together: deferred revenue is where offshore accounting handles revenue correctly — not by making the recognition judgment (which it can’t), but by executing the firm’s judgment through a disciplined, reconciled, contract-tied schedule that holds money out of revenue until earned and surfaces any attempt to pull it forward early. Revenue is the judgment the offshore team must defer to; deferred revenue is the mechanism through which it faithfully carries that judgment out, month after month — and doing that well is exactly how an offshore team earns trust on the most sensitive number on the financials.
What are the common misconceptions about deferred revenue?
- “Deferred revenue is revenue.” It’s the opposite — it’s a liability, money received for work not yet done. It only becomes revenue as the obligation is satisfied. The name confuses people; “unearned revenue” is clearer.
- “If the cash is in the bank, it’s earned.” No — cash and earning are different. Prepaid cash sits as deferred revenue (a liability) until you deliver. You can be cash-rich from prepayments with little recognized revenue yet.
- “Deferred revenue is a bad thing (a debt).” Not for subscription businesses — a large, growing deferred-revenue balance signals strong prepaid forward commitments and is generally healthy. It’s an obligation to deliver service, not borrowed money.
- “You release deferred revenue when you invoice.” No — you release it as you deliver (satisfy the obligation), per the contract. The schedule must be tied to the contract, not to billing events.
- “Deferred revenue and accrued revenue are the same.” They’re mirror opposites — deferred revenue is cash received before earning (a liability); accrued/unbilled revenue is earning before billing (an asset).
- Control reality. The schedule must reconcile every period (opening + billings − recognized = closing), and that roll-forward is where premature revenue recognition becomes visible.
What terms are commonly confused with deferred revenue?
| Confused with | The key difference |
|---|---|
| Revenue | Earned income; deferred revenue is unearned — a liability until the obligation is satisfied |
| Accrued / unbilled revenue (contract asset) | The mirror — revenue earned but not yet billed (an asset); deferred revenue is cash received but not yet earned (a liability) |
| Accounts receivable | Money owed to you for delivered goods (an asset); deferred revenue is your obligation to deliver for money already received |
| Accrued expenses | An expense incurred but unpaid (the expense-side timing difference); deferred revenue is the revenue-side one |
| Deposits / customer prepayments | Often are deferred revenue — the same concept by another name |
Common client questions about deferred revenue
Why isn't the money my customer prepaid counted as revenue yet?
Because you haven’t earned it yet. Revenue is recognized when you deliver what the customer paid for, not when the cash arrives. So when a customer pays you upfront — for a year of service, say — that cash goes onto your books as deferred revenue, which is a liability: it represents your obligation to deliver the service you’ve been paid for. As you deliver month by month, that liability converts into revenue. The cash is yours to use, but it isn’t yours to claim as earnings until you’ve done the work.
Is deferred revenue a bad thing — it's a liability, right?
It’s a liability in the accounting sense, but it’s usually a good sign, especially for subscription businesses. It means customers have paid you in advance — they’ve committed, and you’re holding their cash. A large and growing deferred-revenue balance shows strong forward bookings, which is healthy. It’s not debt you have to repay in money; it’s an obligation you discharge by delivering the service you’ve already been paid for. So don’t read “liability” as “problem” here — for many businesses it’s a sign of momentum.
When does deferred revenue become actual revenue?
As you deliver. The deferred-revenue amount is released to revenue in step with you satisfying your obligation to the customer — typically on a schedule that matches the delivery. For an annual subscription paid upfront, you’d recognize one-twelfth each month as you provide that month of service, until after twelve months the whole amount has moved from the liability to revenue and the deferred balance is zero. The key is that it follows your actual delivery, set by the contract terms — not by when you invoiced or when the cash came in.
Why do you track deferred revenue on a separate schedule?
Because it’s the only way to recognize the revenue correctly over time and to prove the numbers are right. The schedule tracks, for each contract, how much you received, how much you’ve recognized so far, and how much is still owed as future service. Each period it has to reconcile — your starting balance, plus new prepayments, minus what you’ve earned, should equal your ending balance. That reconciliation keeps your revenue honest and is exactly what an auditor or investor will examine, because it’s where the timing of your revenue is laid out. A clean schedule is one of the most important things a prepaid-revenue business can maintain.
My deferred revenue is large — what does that tell me?
For a subscription or prepaid business, a large deferred-revenue balance generally reflects strong forward commitments — customers have paid ahead for service you’ll deliver over the coming months. That’s revenue you can count on recognizing as you deliver, so it’s a kind of visibility into your near-future income. It does tie up in your obligations (it reduces working capital on paper, since it’s a current liability), but for a healthy subscription business, a growing deferred-revenue balance is one of the better signs there is — it means demand is being committed and paid for ahead of delivery.
