Deferred revenue and unearned revenue are the same thing. Both labels describe money a customer has paid before the company has delivered the promised goods or services, and both sit on the balance sheet as a liability until the company performs. Under the current revenue standard, ASC 606, the formal name is “contract liability,” but the older terms remain in everyday use on ledgers, in software, and in conversation.
Why Two Names for the Same Account
Neither term is wrong, and the accounting profession has used both for decades. “Unearned revenue” leans on the company’s perspective: the money is in hand, but it hasn’t been earned yet. “Deferred revenue” leans on timing: recognition of the revenue is being postponed to a later period. Companies pick one based on internal habit or whatever their accounting software puts in the chart of accounts by default.
The Financial Accounting Standards Board added a third label when it issued ASC 606. The standard defines a contract liability as an entity’s obligation to transfer goods or services to a customer for which the entity has received consideration from the customer.1FASB. Accounting Standards Update 2014-09 Revenue From Contracts With Customers Topic 606 Most companies keep “deferred revenue” or “unearned revenue” on their internal books and map to the ASC 606 term in public filings. All three point to the same economic fact: a customer paid, and the company still owes something.
How the Liability Sits on the Balance Sheet
When cash arrives before delivery, it cannot be booked as revenue. The payment represents a promise the company still has to keep, and a promise owed to a customer is a liability. Recording it as income at collection would overstate earnings and mislead anyone reading the financial statements.
The entry is simple. Debit Cash for the amount received. Credit Deferred Revenue (or Unearned Revenue) for the same amount. ASC 606 requires that when a customer pays before the company performs, the arrangement appears as a contract liability on the balance sheet.1FASB. Accounting Standards Update 2014-09 Revenue From Contracts With Customers Topic 606
Where that liability lives depends on when the company expects to deliver. Amounts the company will satisfy within 12 months belong in current liabilities. Anything stretching beyond a year gets split, with the portion due after 12 months moved into non-current liabilities. A 24-month prepaid support contract, for instance, would show 12 months as current and 12 months as non-current. Lenders and analysts read current liabilities to gauge short-term cash needs, so getting the split right matters.
When It Becomes Revenue
ASC 606 replaced a patchwork of industry-specific rules with a single framework. The core idea: revenue counts only when the company actually delivers what it promised. Each time a promise is satisfied, the company debits the deferred revenue liability and credits revenue for the amount earned. That entry is what moves the balance off the balance sheet and onto the income statement.
Whether that happens all at once or gradually depends on the type of promise. A shipped product is a point-in-time obligation: the customer takes control, and the entire deferred revenue balance tied to that product clears in one entry. Over-time recognition applies when one of three conditions is met—the customer simultaneously receives and consumes the benefit as the company performs, the company’s work creates or improves an asset the customer controls as it’s built, or the company’s work has no alternative use to the company and it has an enforceable right to payment for progress to date.1FASB. Accounting Standards Update 2014-09 Revenue From Contracts With Customers Topic 606 If none of the three applies, the obligation is satisfied at a point in time.
For most subscription and maintenance work, the first condition applies: the customer receives access or coverage continuously. The deferred revenue balance is reduced ratably across the service period. A $1,200 annual subscription produces $100 of recognized revenue each month until the liability reaches zero.
Common Examples
SaaS Subscriptions
A customer pays $600 upfront for a year of cloud software access. The provider records $600 in cash and $600 in deferred revenue. Each month, $50 shifts from the liability into revenue as the customer uses the platform. The service is consumed as it’s delivered, so over-time recognition applies.
Gift Cards
Retailers collect cash when a gift card is sold, but the store owes the cardholder merchandise until the card is redeemed. Revenue is recognized only as the balance is spent. ASC 606 also addresses breakage, the portion of cards that go unredeemed: if the company can reasonably estimate breakage, it recognizes that expected breakage as revenue proportionally, in step with actual redemptions.1FASB. Accounting Standards Update 2014-09 Revenue From Contracts With Customers Topic 606 If it can’t be estimated reliably, the company waits until redemption becomes remote.
Prepaid Maintenance
Equipment sellers often bundle a multi-year service plan with the hardware. The customer pays at signing, and coverage runs across the contract’s full term. Cash creates a deferred revenue liability, and revenue is recognized ratably as the coverage period elapses. Contracts longer than a year get split between current and non-current portions on each balance sheet date.
Tax Treatment Does Not Follow the Book Treatment
One point catches business owners off guard: the tax rules for advance payments don’t line up with the book rules. Under 26 U.S.C. § 451(c), an accrual-method taxpayer that receives an advance payment must generally include the entire amount in gross income in the year received.2Office of the Law Revision Counsel. 26 USC 451 General Rule for Taxable Year of Inclusion That’s more aggressive than GAAP, which spreads recognition across the service period.
The code offers a limited deferral election. A taxpayer can defer the portion of an advance payment that isn’t recognized on the applicable financial statement in the year of receipt. The relief lasts one year only: any amount not included in the year of receipt must be included in the very next tax year, no matter how long the service period runs under GAAP.2Office of the Law Revision Counsel. 26 USC 451 General Rule for Taxable Year of Inclusion
Consider a $24,000 payment collected in December 2025 for a two-year service contract. GAAP recognizes $1,000 per month across 24 months. For tax purposes, even with the deferral election, $1,000 is included in 2025 income and the remaining $23,000 is included in 2026. Tax accelerates well ahead of the earnings shown on the income statement, and businesses collecting large advance payments should plan for that cash-flow gap. Some categories, including rent, insurance premiums, and payments tied to financial instruments, don’t qualify for the deferral at all; the full amount is taxable in the year received.
Why the Classification Matters
Misclassifying deferred revenue produces a misstatement on two financial statements at the same time. Recognizing revenue too early inflates income while understating liabilities. For public companies, that combination has long been one of the most common triggers for financial restatements and SEC scrutiny. Auditors treat revenue overstatement as a leading fraud risk.
Private companies feel it too. Overstated revenue can breach loan covenants tied to earnings, distort due diligence for a sale, or create tax mismatches when book income drifts from what was reported to the IRS. The remedy is straightforward. Set clear policies for when each type of advance payment moves out of the liability account and into revenue, and revisit those policies whenever contract structures change. The label on the account—deferred revenue, unearned revenue, or contract liability—doesn’t change the substance. The timing of the release does.