Deferred Revenue Schedule: Rollforward, Waterfall, Worked Example and Audit Tests Under ASC 606

Deferred revenue is cash, or a right to cash, that a company has received before it has done the work. Until the company transfers the goods or services, it owes the customer performance, so the amount is a liability. Software subscriptions, annual maintenance, tuition, memberships, prepaid service contracts and gift cards all create it.

A deferred revenue schedule is the working paper that supports the balance. It lets the preparer show the balance is complete, lets the auditor recalculate revenue, and supplies the numbers for the ASC 606 disclosures. This guide builds the two standard layouts, a rollforward and a waterfall, from a worked example, then covers the audit tests. A layout to start from is in the deferred revenue rollforward template. For the concept, see deferred revenue and contract assets and contract liabilities.

What deferred revenue is under ASC 606

ASC 606 uses the term contract liability: an entity's obligation to transfer goods or services to a customer for which the entity has received consideration, or for which the amount is due, from the customer. Deferred revenue, unearned revenue and customer deposits are common names for it.

The amount stays a liability until the performance obligation is satisfied. Revenue is then recognized, either at a point in time or over time. For a subscription or maintenance contract, the obligation is usually satisfied over time, and revenue is recognized as the service is provided, often evenly across the term. See ASC 606 revenue recognition and the five-step model.

Two points on recognition and presentation: the entity recognizes a contract liability when the customer pays or when payment is due, whichever is earlier; and the liability is classified as current if the service will be provided within the operating cycle or twelve months, and noncurrent otherwise.

Two layouts and what each shows

Rollforward. Opening balance, plus amounts added during the period (billings or cash received), less revenue recognized, equals the closing balance. This agrees to the general ledger and supports the disclosure of opening and closing balances.

Waterfall. For each contract or cohort, the amount of the closing balance that will be recognized in each future period. This supports the current versus noncurrent split and the remaining performance obligation disclosure.

Worked example

Illustrative numbers. A software company has a December 31, 2026 year-end. Customers pay annual fees in advance. The company recognizes revenue evenly by month over the contract year.

Opening balance, January 1, 2026. Contract D was billed in July 2025 and six months ($7,200) were recognized in 2025, so the opening deferred balance is $14,400 - $7,200 = $7,200.

Rollforward for 2026

Revenue recognized in 2026 by contract

• D: January to June, 6 months x $1,200 = $7,200
• A: March to December, 10 months x $1,000 = $10,000
• B: October to December, 3 months x $500 = $1,500
• C: July to December, 6 months x $800 = $4,800
• Total: $7,200 + $10,000 + $1,500 + $4,800 = $23,500

Closing balance by contract (a check)

• A: 2 months remaining x $1,000 = $2,000
• B: 9 months x $500 = $4,500
• C: 6 months x $800 = $4,800
• Total: $2,000 + $4,500 + $4,800 = $11,300, which agrees to the rollforward.

Waterfall: when the closing balance will be recognized

All of the closing balance is current. The company would recognize $11,300 in 2027 from the existing contracts, before any new billings.

Disclosures that come from the schedule

ASC 606 requires disclosure of the opening and closing balances of contract liabilities when they are not otherwise presented, and of revenue recognized in the period that was included in the contract liability balance at the beginning of the period. It also requires information about remaining performance obligations, with practical expedients that allow an entity to omit the disclosure for contracts with an original expected duration of one year or less. In the example, revenue recognized in 2026 that was in the opening balance is $7,200, the amount from contract D.

Tax may differ. A taxpayer may be able to defer advance payments for tax, within limits tied to the treatment in its financial statements, under IRC section 451(c). Treat the book schedule and the tax treatment as separate workpapers. See book-tax differences.

How auditors test the balance

• Completeness: compare billings in the schedule to invoices and cash receipts, and look for customer payments in the bank statements that have no corresponding schedule entry. See search for unrecorded liabilities.
• Cutoff: test invoices around year-end. An invoice for a service period that began in December belongs in the year-end schedule with the December portion recognized, and a payment received in December for a service that starts in January is deferred in full. See cutoff testing.
• Recalculation: pick a sample of contracts, agree the term and fee to the signed contract, and recompute revenue and the deferred balance. See recalculation.
• Total agreement: agree the schedule total to the general ledger, and test the report generating it for completeness and accuracy. See information produced by the entity.
• Revenue recognition risk: revenue recognition is a presumed fraud risk under AU-C 240, so early recognition of deferred amounts is a procedure to design for. See revenue recognition audit procedures and revenue recognition fraud presumption.
• Analytics: compare the balance to billings and to prior periods. A balance that falls while billings rise needs an explanation.
• Multiple performance obligations: where a contract includes setup, hardware and support, review the allocation of the transaction price to each obligation. See performance obligation.

Common mistakes

• Recognizing the full invoice when billed, which overstates revenue in the period.
• Using the invoice date, not the service start date, to begin recognition.
• Mid-month conventions applied inconsistently across contracts.
• Contract modifications, refunds or cancellations not reflected in the schedule.
• Omitting multi-year prepayments from the noncurrent split.
• A schedule that does not agree to the general ledger because credits and write-offs were booked outside it.
• Treating refundable deposits as revenue, when they may be refund liabilities.

Frequently asked questions

Is deferred revenue an asset or a liability?

A liability. The company has received payment and still owes the customer performance.

What is the difference between deferred revenue and unearned revenue?

Nothing in substance. ASC 606 calls it a contract liability.

How do you calculate deferred revenue?

For each contract, take the amount billed or received and subtract the revenue recognized so far, which for an evenly delivered service is the fee divided by the term, times the months elapsed.

What is a deferred revenue waterfall?

A schedule showing how the closing balance will turn into revenue in each future period.

Does deferred revenue appear on the cash flow statement?

Yes, as a change in operating liabilities in the indirect method. See statement of cash flows under ASC 230.

Sources

• FASB, ASC 606-10-45 (contract liabilities) and 606-10-50 (disclosures), asc.fasb.org
• AICPA, AU-C Section 240 (presumed fraud risk in revenue recognition)
• IRC section 451(c) and Treasury Regulation section 1.451-8, ecfr.gov

AU-C references are to AICPA Professional Standards, paraphrased here; read the standard itself before relying on a requirement. This page is guidance, not professional advice. Report an error