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.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 14, 2026Last reviewed September 14, 2026Editorial policy

Part of the revenue recognition guide.

Governing section	ASC 606-10-50, disclosure objective stated in 606-10-50-1
Disaggregation of revenue	Revenue broken into categories showing how nature, amount, timing, and uncertainty are affected by economic factors
Contract balances	Opening/closing receivables, contract assets, and contract liabilities, plus revenue recognized from prior-period liability balances
Performance obligations	What they are, when typically satisfied, and significant payment terms
Significant judgments	Methods and inputs used for transaction price, allocation, and timing of satisfaction

The objective the disclosures serve

ASC 606-10-50-1 states the disclosure objective directly: enabling financial statement users to understand the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers. Every specific disclosure requirement that follows exists to serve that one objective, which is useful for deciding how much detail a given disclosure actually needs — more than the minimum if it's genuinely material to understanding revenue uncertainty, no more than necessary otherwise.

Disaggregation of revenue

An entity has to disaggregate revenue from contracts with customers into categories that show how economic factors affect the nature, amount, timing, and uncertainty of revenue and cash flows — by geography, product line, contract duration, or another dimension that's actually meaningful for the business, not a fixed template that applies identically to every filer.

Contract balances

The standard requires disclosing opening and closing balances of receivables, contract assets, and contract liabilities from contracts with customers, plus how much revenue recognized in the period was already sitting in the opening contract-liability (deferred revenue) balance, and how much came from performance obligations satisfied in prior periods.

Performance obligations and significant judgments

Beyond the numbers, the standard requires qualitative disclosure of what an entity's performance obligations actually are, when they're typically satisfied, and significant payment terms — plus the significant judgments and changes in judgments used in applying the standard, since two entities can reach different, both-defensible conclusions from similar facts, and the disclosure is what lets a reader see which judgments drove the numbers.

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

Checklist

The four disclosure buckets ASC 606-10-50 requires

Disaggregation of revenue into meaningful categories
Contract balances — opening/closing receivables, contract assets, contract liabilities
Performance obligations — what they are, when satisfied, payment terms
Significant judgments and changes in judgments applied

Frequently Asked Questions

The core disclosure objective and most requirements apply broadly, but some nonpublic entities qualify for reduced disclosure relief on certain items (like the remaining-performance-obligations disclosure) — the specific scope of that relief is its own research question worth checking against current FASB guidance for a given entity's facts.

As granular as needed to serve the stated objective — showing how economic factors affect revenue's nature, amount, timing, and uncertainty — not a fixed number of categories. A single-product company with uniform geography and contract terms may need very little disaggregation; a diversified one needs more.

Within the contract-balances disclosure — the opening and closing contract-liability (deferred revenue) balance, plus how much of the period's recognized revenue came out of the opening balance, is exactly the roll-forward information ASC 606-10-50 requires.

Sources

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…

How-to

How do you calculate a contract's transaction price under ASC 606?

Transaction price is the consideration a company expects in exchange for goods or services. Start with the stated contract price, add variable consideration using the expected-value or most-likely-amount method, constrained to amounts unlikely to reverse, adjust for any significant financing component, then subtract noncash consideration and amounts payable to the customer.

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.

Definition

What SOX controls are typically required around revenue recognition?

The PCAOB requires auditors to treat improper revenue recognition as a presumed fraud risk unless that's documented and rebutted — which is why revenue controls sit at the center of most SOX programs. Typical controls split into preventive (segregation of duties across contract approval and billing) and detective (management review of estimates, reconciliations, flux analysis).