Skip to main content

What is deferred revenue?

Deferred revenue is a liability an entity records when a customer pays, or the entity has an unconditional right to payment, before the goods or services have actually been delivered. Under ASC 606, the formal term is contract liability — deferred revenue and unearned revenue are the older, still commonly used names for the same balance-sheet item.

Zuny FesterBy Zuny Fester, Head of Operations and Marketing
Reviewed by Zuny Fester
Published Last reviewed Editorial policy

Part of the revenue recognition guide.

What it isA liability, not revenue — money received or billable before it's been earned
ASC 606 termContract liability, per the codification
Common alternate namesDeferred revenue, unearned revenue, refund liability (in some contexts)
When it clearsAs the entity satisfies the related performance obligation, it moves from liability to recognized revenue
Where it livesOn the balance sheet as a liability, until earned

The core idea: payment and earning aren't the same event

A customer paying for an annual software subscription up front hasn't caused the seller to earn a full year of revenue in that instant — the seller still owes twelve months of service. Deferred revenue is the accounting mechanism that keeps that distinction honest: the cash (or the unconditional right to it) is recorded, but it sits as a liability rather than revenue until the seller actually delivers what was paid for.

Why ASC 606 calls it a "contract liability" instead

A contract liability is an entity's obligation to transfer goods or services to a customer when the customer has prepaid, or when the customer's consideration is due, ahead of performance. "Contract liability" is the formal ASC 606 term; entities aren't required to use it on the face of their financial statements, and most continue using the more familiar "deferred revenue" or "unearned revenue" labels — the underlying accounting concept is identical either way.

How it clears

As the entity satisfies the performance obligation the payment relates to — delivering a month of a subscription, completing a milestone on a services contract — the corresponding portion moves off the balance sheet as a liability and onto the income statement as recognized revenue. A twelve-month subscription paid in full up front typically clears roughly one-twelfth of the deferred balance each month, though the actual pattern depends on how the underlying performance obligation is satisfied, not a fixed calendar assumption.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Worked example

A $12,000 annual contract, month by month

A customer pays $12,000 upfront for a 12-month software subscription on January 1. On that date, the seller records $12,000 in deferred revenue (a liability) and $0 in recognized revenue — nothing has been delivered yet beyond the promise. At the end of January, having provided one month of service, the seller moves $1,000 from deferred revenue to recognized revenue. By June 30, six months of service delivered, deferred revenue has shrunk to $6,000 and recognized revenue for the contract stands at $6,000. The cash arrived entirely in January; the revenue arrives at $1,000 a month as it's actually earned.

Frequently Asked Questions

No — they're opposites. A contract liability (deferred revenue) exists when payment is ahead of performance; a contract asset exists when performance is ahead of the right to payment (work delivered that hasn't yet been billed or become unconditionally due).

Tax treatment of advance payments is a separate question from GAAP revenue recognition and depends on the entity's tax method and applicable rules — this page covers the accounting-liability concept, not tax timing, which needs its own analysis.

If the performance obligation is genuinely never satisfied (a service is cancelled and unused, for instance), the liability typically resolves through a refund or a forfeiture recognition instead of clearing into revenue — it doesn't just sit indefinitely as a stale balance.

Sources

Related

Topic

Revenue Recognition

Revenue recognition determines when — not just how much — revenue hits the books. Under ASC 606 (US GAAP) and its international counterpart IFRS 15, revenue is recorded as a company satisfies its perf…

Read more

Definition

What is ASC 606 revenue recognition?

ASC 606 is the FASB standard for recognizing revenue when control of a good or service transfers to the customer, for the amount expected in exchange. It uses one five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate that price, and recognize revenue as each obligation is satisfied.

Read more

Diagnostic

Why doesn't deferred revenue match the general ledger?

Deferred revenue usually drifts from the general ledger when the billing system's revenue schedule isn't synced to GL journal entries, or when manual entries post outside that schedule. Reconcile the deferred revenue roll-forward against the GL trial balance at the contract-line level, not the invoice level, to find exactly where the two diverge each month.

Read more

Definition

What are the required ASC 606 disclosures?

ASC 606-10-50 requires disclosures that let a reader understand the nature, amount, timing, and uncertainty of revenue and cash flows — chiefly disaggregation of revenue into meaningful categories, contract-balance roll-forwards (receivables, contract assets, contract liabilities), remaining performance obligations, and the significant judgments made applying the standard.

Read more