Deferred Revenue
Deferred Revenue Definition
Deferred revenue is cash or billings a company records before it has earned the related revenue by delivering the promised product or service. It is a liability because the company still owes access, service, delivery, or sometimes a refund. The balance moves out of deferred revenue only as the company satisfies the related obligation and can recognize revenue on the income statement.
For B2B SaaS, deferred revenue often appears when customers prepay for annual subscriptions, usage credits, implementation milestones, or multi-year contracts. Under ASC 606, the same idea is usually called a contract liability: payment is made or due before goods or services transfer. Clean deferred-revenue tracking ties each invoice, contract term, recognition schedule, and journal entry together so billing, revenue, and reconciliation do not drift. Without that trail, finance can overstate revenue, understate liabilities, and spend close rebuilding the schedule by hand.
Also referred to as: unearned revenue, contract liability, deferred income, customer prepayment.
How deferred revenue works in B2B SaaS
Deferred revenue starts with a timing gap. The customer has paid, or the invoice is due, but the company has not yet delivered all of the promised service. A SaaS company might invoice $120,000 on January 1 for a 12-month subscription. Cash and billings moved on day one, but the service will be delivered over the full year.
That upfront amount should not all become revenue in January. If the subscription is a simple stand-ready service, the company typically recognizes $10,000 each month as access is provided. If the contract includes prepaid usage credits, usage overages, implementation services, or milestones, the recognition pattern may follow consumption or delivery instead of a straight-line monthly schedule. That is why deferred revenue needs contract terms, billing data, usage data, and recognition schedules to stay connected.
Deferred revenue vs. recognized revenue
Deferred revenue sits on the balance sheet. It is a liability because the company has an obligation left to fulfill. Recognized revenue sits on the income statement. It is the portion the company has earned because the customer received the promised product or service.
The two balances move in opposite directions as performance happens. When the customer prepays, deferred revenue increases. As the service is delivered, deferred revenue decreases and recognized revenue increases. Cash may not change during that monthly release because the customer already paid.
Deferred revenue under ASC 606
Under ASC 606, revenue follows performance obligations. A company identifies what it promised to deliver, determines the transaction price, allocates that price to the obligations, and recognizes revenue when or as each obligation is satisfied. When the customer pays or payment becomes due before that transfer happens, the balance is a contract liability.
For a flat SaaS subscription, the obligation is often satisfied over time as the customer has access to the service. For usage-based contracts, revenue may follow actual consumption. For contracts with setup fees, implementation services, usage credits, ramps, or mid-term amendments, finance has to decide which obligations are distinct, how the price is allocated, and when each piece is earned.
Deferred revenue journal entry example
Suppose a customer prepays $120,000 for a 12-month SaaS subscription that starts on January 1 and is recognized evenly over the term. At billing or cash collection, the company debits cash or accounts receivable for $120,000 and credits deferred revenue for $120,000.
At the end of each month, once one month of service has been provided, the company releases one-twelfth of the balance by debiting deferred revenue for $10,000 and crediting subscription revenue for $10,000. After January, deferred revenue is $110,000. By the end of December, the deferred balance tied to that contract is zero, assuming the service was delivered as planned.
Common mistakes and edge cases
The biggest mistake is recognizing revenue when the invoice goes out. Invoicing proves the customer owes money; it does not prove the company has earned the revenue. A clean process separates billing from recognition and then reconciles the two.
Other edge cases show up when the contract changes. Upgrades, downgrades, ramps, credits, refunds, implementation milestones, and usage commitments can all change the recognition schedule. A contract amendment that updates billing but not the deferred-revenue schedule creates drift that usually appears at close or during audit prep.
Why deferred revenue matters for billing and reconciliation
Deferred revenue is one of the places where messy billing becomes messy accounting. If the contract, invoice, usage data, and recognition schedule do not agree, finance has to rebuild the trail by hand: what was promised, what was billed, what was collected, what was delivered, and what should be recognized.
LedgerUp keeps that trail in the post-signature workflow. Ari reads the contract, extracts billing and recognition terms, checks the invoice, tracks usage and amendments, and keeps deferred revenue tied to the same ledger that supports billing reconciliation. When finance needs journal entries, Ari can post summarized recognized-revenue and deferred-revenue activity to the general ledger while preserving the detail behind the schedule.
When you'd use this
- Reviewing annual or multi-year customer prepayments.
- Building or checking ASC 606 revenue recognition schedules.
- Reconciling billed, collected, deferred, and recognized revenue at close.
- Explaining why cash increased before revenue was earned.
- Evaluating a revenue recognition subledger or automation workflow.
Related Guides
The five-step model that determines when deferred revenue can be recognized.
How prepaid usage credits, consumption, and deferred balances work under ASC 606.
How finance keeps invoices, usage, deferred revenue, and recognized revenue tied together.
How LedgerUp automates schedules, journal entries, and deferred-revenue reconciliation.
How Ari connects signed terms to billing, recognition, reconciliation, and journal entries.
Deferred Revenue FAQ
Is deferred revenue a liability?
Yes. Deferred revenue is a liability because the company has received payment, or has a right to payment, before it has delivered the related product or service. The liability goes down as the company satisfies the obligation and recognizes revenue.
Is deferred revenue the same as unearned revenue?
In most day-to-day accounting discussions, yes. Deferred revenue and unearned revenue both describe amounts billed or collected before the related revenue is earned. Under ASC 606, the more precise term is contract liability.
What is the deferred revenue journal entry?
When a customer prepays, the typical entry is to debit cash and credit deferred revenue. As the service is delivered, the company debits deferred revenue and credits revenue. If the invoice is due before cash is collected, accounts receivable may be debited before cash.
When is deferred revenue recognized as revenue?
Deferred revenue is recognized when or as the company satisfies the related performance obligation. For a simple subscription, that may be ratably over the contract term. For prepaid usage credits or consumption-based contracts, recognition may follow actual usage.
How is deferred revenue different from accounts receivable?
Accounts receivable is an asset: the customer owes the company money. Deferred revenue is a liability: the company owes the customer future service or delivery. They can appear together when the customer has been invoiced before the company has performed.