Yes. Deferred revenue and contract liability describe the same obligation under ASC 606: money a business has collected (or has a right to collect) before it has delivered the promised goods or services. The Financial Accounting Standards Board formally named this balance a “contract liability” when it issued ASC 606, but companies are not required to use that exact wording on their financial statements. Presenting the line as “deferred revenue” or “unearned revenue” remains acceptable, provided the underlying recognition and measurement follow the standard.
What ASC 606 Actually Says
Under ASC 606-10-45-2, a contract liability is an entity’s obligation to transfer goods or services to a customer for which the entity has already received consideration, or for which consideration is already due. Plain version: you have the customer’s money, you haven’t done the work, and the balance sheet has to show that you still owe something. The liability shrinks only as you deliver.
Before ASC 606 took effect, most companies used “deferred revenue” or “unearned revenue” for this balance. The FASB introduced “contract liability” to tie the obligation directly to a specific contract rather than treat it as a generic pool of unearned cash. The conceptual link matters, but the label on the face of the statements does not have to change. ASC 606-10-45-5 permits alternative descriptions.
ASC 606 was developed jointly with the International Accounting Standards Board, and IFRS 15 is its international counterpart. The point of the joint project was to replace industry-specific revenue rules with a single framework that applies across sectors.1Financial Accounting Standards Board. Revenue Recognition
Does the Label on Your Balance Sheet Have to Change?
No. If your financial statements currently show “deferred revenue,” you can keep that presentation. ASC 606-10-45-5 explicitly permits alternative descriptions for contract liabilities and contract assets. What the standard requires is that the amount reflect the ASC 606 model, not that you rename the line item. Many public and private companies still present the balance as deferred revenue, and auditors accept it.
The label question is separate from the substance question. Even if you keep the old term, you still have to identify performance obligations, determine the transaction price, allocate that price across obligations, and recognize revenue as each obligation is satisfied. Those steps drive the number on the line, whatever you call the line.
When a Contract Liability Arises
A contract liability is created the moment a business receives payment, or has a right to payment, before fulfilling its obligations. Common triggers include upfront deposits, prepaid annual subscriptions, milestone billing that runs ahead of delivery, and gift cards or stored-value instruments. In each case, the company is holding cash it hasn’t earned, and the balance sheet has to reflect that.
A concrete example: a company sells a two-year support plan for $24,000, paid in full at signing. On day one, the entire $24,000 sits as a contract liability. Each month, as support is provided, $1,000 shifts from the liability to revenue. The performance obligation is the monthly delivery of support, and the liability shrinks in proportion to the work completed.2Financial Accounting Standards Board. Accounting Standards Update No. 2016-10 – Revenue from Contracts with Customers (Topic 606)
How the Balance Converts to Revenue
The mechanics are simple. When a performance obligation is satisfied, you debit the contract liability and credit revenue. The income statement gains earned revenue while the balance sheet loses an equivalent amount of liability. For obligations satisfied over time, this happens in increments. For obligations satisfied at a point in time, the allocated amount shifts all at once.
A $1,200 annual membership serviced monthly shows the pattern: $100 moves from contract liability to revenue each month. By year-end the liability is zero and the income statement reflects $1,200 in earned revenue. The timing of cash collection is irrelevant to when revenue appears; what matters is when the work gets done.2Financial Accounting Standards Board. Accounting Standards Update No. 2016-10 – Revenue from Contracts with Customers (Topic 606)
Breakage on Gift Cards and Prepaid Credits
Gift cards, prepaid credits, and similar instruments often go partially or fully unused. ASC 606 calls the unused portion “breakage” and offers two paths. If the company expects to be entitled to the breakage amount, based on historical redemption data, it recognizes that revenue proportionally as customers exercise their rights. A retailer that sells $50,000 in gift cards and expects 10% to go unused doesn’t wait for expiration; each redemption pulls a proportional slice of expected breakage into revenue alongside the redeemed amount. If the company does not expect to keep the breakage, perhaps because state unclaimed-property laws require remittance, revenue is recognized only when the likelihood of the customer exercising remaining rights becomes remote. In escheatment states, the unused balance becomes a liability to the government rather than revenue.
What a Contract Liability Is Not
Because the terms overlap in casual use, three related items are worth separating out. Getting these wrong distorts both the liability side of the balance sheet and the revenue line.
Refund Liabilities
A contract liability represents a promise to deliver goods or services. A refund liability represents a customer’s right to get money back. If a contract lets the customer cancel without penalty, the prepayment may not qualify as a contract liability at all for the cancellable period, because a cancellable arrangement may not meet ASC 606’s definition of a contract. The cash received should be recorded as a refund liability and presented separately. Return provisions in sales contracts work similarly: the expected returns portion is a refund liability, not part of the contract liability balance.
Consideration Payable to Customers
Coupons, rebates, and vouchers a company expects to issue reduce the transaction price rather than sitting as a separate liability. If you have a history of price concessions, those concessions are treated as variable consideration and folded into the transaction price at contract inception. The result is a smaller contract liability from the start, not a parallel entry. This applies even when the concession hasn’t been formally communicated to the customer.
Contract Assets
A contract asset is the mirror image of a contract liability. It arises when the company has delivered before it has an unconditional right to bill. The dividing line under ASC 606 is whether the right to payment is conditional or unconditional. A contract asset represents a conditional right; once only the passage of time separates the company from payment, the balance moves from contract asset to receivable. Within a single contract, a company might have both positions on different performance obligations. ASC 606 requires netting at the individual contract level, so each contract shows on the balance sheet as either a net contract asset or a net contract liability, never split.
Current vs. Non-Current, and the SEC 5% Rule
Contract liabilities split between current and non-current based on when the related performance obligations will be satisfied. Amounts tied to work you expect to complete within twelve months are current. Obligations that extend beyond a year, such as multi-year service agreements or long-term construction contracts, are non-current.
This split has real consequences. Lenders use current liabilities to calculate the current ratio and quick ratio. Misclassifying a long-term obligation as current inflates short-term liabilities and can make the company look less solvent than it is, which can trigger loan covenant issues.
SEC registrants face an additional rule. Under Regulation S-X, any individual liability that exceeds 5% of total current liabilities must be broken out as a separate line item on the balance sheet or disclosed in the notes.3eCFR. 17 CFR 210.5-02 – Balance Sheets SaaS, construction, and subscription companies frequently cross that threshold and need a dedicated line rather than a spot inside “other current liabilities.”
Disclosures Tied to Contract Liabilities
ASC 606 requires both qualitative and quantitative disclosures. For contract liabilities specifically, companies must disclose opening and closing balances for each reporting period and explain significant changes, including how much of the beginning contract liability balance was recognized as revenue during the period.
Companies also have to describe the significant judgments applied: how performance obligations were identified, how the transaction price was determined (especially when variable consideration is involved), and how the price was allocated across obligations. Use of practical expedients, such as the financing-component shortcut for contracts of one year or less, must be disclosed.4Financial Accounting Standards Board. Revenue from Contracts with Customers (Topic 606) – ASC 606-10-50
SEC registrants layer on more. Regulation S-X requires tabular disclosure of contractual obligations broken into time buckets: less than one year, one to three years, three to five years, and beyond five years.5U.S. Securities and Exchange Commission. Disclosure in Management’s Discussion and Analysis About Off-Balance Sheet Arrangements and Aggregate Contractual Obligations Material interim changes to those obligations must be discussed even when the full table isn’t required.
Where Book and Tax Diverge
The book treatment under ASC 606 and the tax treatment of the same advance payment often don’t line up, and that mismatch is one of the most common deferred tax items on corporate balance sheets. For federal income tax purposes, IRC Section 451(c) governs advance payments received by accrual-method taxpayers. The default rule: include the advance payment in gross income in the year received.6Office of the Law Revision Counsel. 26 USC 451 – General Rule for Taxable Year of Inclusion
Section 451(c)(1)(B) offers an alternative. Taxpayers can elect to defer a portion of the advance payment to the following taxable year, tracking the amount recognized as revenue on the applicable financial statement (typically the audited GAAP financials). Whatever isn’t recognized as revenue in the year of receipt can be pushed to the next year, and no further. That one-year cap means tax recognition is always faster than book recognition for multi-year contracts.7Internal Revenue Service. Notice 2018-35 – Section 451(c) Advance Payments
An illustration: a company collects $60,000 upfront for a three-year service contract and recognizes $20,000 in GAAP revenue the first year. It can defer $40,000 for tax, but only until year two. In year two, the remaining $40,000 becomes taxable regardless of how much revenue the books recognize. Companies without audited financial statements can use a straight-line or statistical method to determine the earned portion, following the approach in Rev. Proc. 2004-34.8Internal Revenue Service. Rev. Proc. 2004-34 – Changes in Accounting Periods and in Methods of Accounting
Getting the timing wrong is expensive. An accuracy-related penalty of 20% of the underpayment applies, plus interest that compounds daily from the original due date.9Internal Revenue Service. Accuracy-Related Penalty So while the answer to the terminology question is a clean yes, treating deferred revenue and contract liability as identical for tax purposes is where companies get into trouble. On the balance sheet they are the same obligation. On the tax return they are not on the same schedule.