Scope

ASC 606 establishes a single comprehensive model for revenue recognition for contracts with customers across all industries. It replaced the legacy industry-specific revenue guidance (real estate, software, construction, multiple-element arrangements, etc.) with one unified framework. Effective for public business entities for annual reporting periods beginning after December 15, 2017, and for all other entities one year later. The standard was developed jointly with the IASB; IFRS 15 is the converged international counterpart.

The scope covers contracts with customers — defined as parties contracting with the entity to obtain goods or services that are an output of the entity's ordinary activities. It excludes lease contracts (ASC 842), insurance contracts (ASC 944), financial instruments (ASC 815, 825, 860), guarantees (ASC 460), and certain non-monetary exchanges.

The five-step model

The framework hinges on five sequential steps, codified in ASC 606-10-05-4:

Step 1 — Identify the contract with a customer (ASC 606-10-25-1 through 25-13). A contract exists when it has approval from the parties, identifiable rights and payment terms, commercial substance, and probable collection of the consideration the entity is entitled to. Note that "probable" here means "likely to occur" — a higher threshold than IFRS 15's "probable" which uses the lower IASB definition.

Step 2 — Identify the performance obligations (ASC 606-10-25-14 through 25-22). A performance obligation is a promise to transfer a good or service (or bundle) that is distinct. Distinct means: (a) the customer can benefit from it on its own or with readily available resources, and (b) the promise is separately identifiable from other promises in the contract. The separately-identifiable analysis (often the harder of the two) considers integration, modification, and dependency between goods or services.

Step 3 — Determine the transaction price (ASC 606-10-32-2 through 32-27). The amount of consideration the entity expects to be entitled to in exchange for transferring goods or services, considering variable consideration, significant financing components, noncash consideration, and consideration payable to the customer.

Step 4 — Allocate the transaction price (ASC 606-10-32-28 through 32-41). Allocate to each performance obligation based on relative standalone selling prices. Where standalone selling prices aren't observable, estimate using adjusted market assessment, expected cost plus margin, or a residual approach (only allowed when the standalone selling price is highly variable or uncertain).

Step 5 — Recognize revenue when (or as) the entity satisfies a performance obligation (ASC 606-10-25-23 through 25-37). Recognition timing depends on whether control transfers at a point in time or over time. Over-time recognition requires meeting one of three criteria: customer receives and consumes benefits simultaneously, the entity's performance creates or enhances an asset the customer controls, or the entity's performance creates an asset with no alternative use and the entity has an enforceable right to payment for performance completed to date.

Variable consideration

Variable consideration includes discounts, rebates, refunds, credits, performance bonuses, penalties, and any other amount that varies based on outcomes. The entity must estimate the amount using either:

Expected value — sum of probability-weighted amounts across a range of possible outcomes. Better for contracts with a large number of similar arrangements.
Most likely amount — the single most likely amount in a range. Better for contracts with binary or limited outcomes.

Critically, variable consideration is subject to the constraint in ASC 606-10-32-11: include only to the extent it is "probable that a significant reversal in the amount of cumulative revenue recognized will not occur when the uncertainty associated with the variable consideration is subsequently resolved."

The constraint is where most variable consideration estimates go wrong in practice. Companies default to expected value because it sounds more rigorous, but for binary outcomes (a milestone payment will or won't be earned) the most likely amount is more defensible. The constraint then ensures aggressive estimates don't drive premature recognition.

Principal vs. agent

ASC 606-10-55-36 through 55-40 govern whether the entity is the principal (records revenue gross) or agent (records revenue net of amounts owed to the supplier). The principal controls the specified good or service before it transfers to the customer. Three indicators of control:

Primary responsibility for fulfilling the promise
Inventory risk before transfer to the customer
Discretion in establishing prices

The principal-agent analysis matters enormously for platform businesses, marketplaces, and resellers — the gross-versus-net question drives reported revenue magnitude even though net income is identical.

Licensing of intellectual property

ASC 606-10-55-54 through 55-65 establish a special framework for IP licensing. Distinguish between:

Right to use (point-in-time license) — IP that exists at a point in time and the customer can use it as-is.
Right to access (over-time license) — IP that the licensor continues to develop, support, or enhance, and the customer has rights to the benefits of those changes.

The distinction drives whether license fees are recognized upfront or over the license term. The factors at ASC 606-10-55-60 (whether the entity has ongoing activities that significantly affect the IP, whether those activities expose the customer to positive or negative effects, whether the activities transfer goods or services as they occur) are the governing analysis.

For software, the analysis is complicated further by whether the license is a functional license (software code) or a symbolic license (brand, trade name, logo). Functional licenses are presumed right-to-use; symbolic licenses are presumed right-to-access.

Contract modifications

ASC 606-10-25-10 through 25-13 govern modifications. Three possible accounting outcomes depending on the facts:

Separate contract — modification adds distinct goods or services and the price reflects standalone selling price.
Termination of existing contract and creation of new — modification adds distinct goods or services but at a price that doesn't reflect standalone selling price.
Continuation of existing contract — modification doesn't add distinct goods or services; the cumulative-catchup approach is applied.

Disclosure requirements (ASC 606-10-50)

The disclosure regime is the most expanded part of the new standard. Required:

Disaggregation of revenue
Contract balances (receivables, contract assets, contract liabilities)
Performance obligations descriptions
Significant judgments (timing of recognition, transaction price determination and allocation)
Assets recognized from costs to obtain or fulfill contracts

The disaggregation disclosure is where investors and analysts focus. Disaggregation should depict how the nature, amount, timing, and uncertainty of revenue and cash flows are affected by economic factors — typically by product line, geography, customer type, contract duration, or sales channel.

Common pitfalls

Defaulting to expected value for variable consideration. Expected value sounds rigorous but is wrong for binary outcomes. A milestone that either will or won't be hit is most-likely-amount territory, not expected value.
Underweighting the constraint. The "significant reversal not probable" test is restrictive. Aggressive variable consideration estimates that pass step 3 still need to clear the constraint. Many implementation errors live here.
Missing performance obligations within services contracts. A SaaS contract with implementation services often has two distinct performance obligations — implementation (point-in-time when complete) and subscription (over-time during the term). Treating it as one bundled obligation defers revenue inappropriately.
Principal-agent miscategorization. Marketplace and platform companies routinely get this wrong, especially during periods of business model change. Re-examine principal-agent each time the company's role in the transaction changes materially.
License classification drift. Functional vs. symbolic licensing is judgmental. Companies that classify legacy IP arrangements as functional (point-in-time) without reassessing for ongoing development support are at risk.
Disaggregation that doesn't disaggregate. A single-line "Product Revenue" with no further breakdown often fails the disaggregation objective. Look at what the entity discloses in earnings calls and management presentations — the disaggregation in the financial statements should be at least that granular.

Operator note

I lived through two ASC 606 implementations as a finance leader, both with materially different mechanics. At Spincast AI, where I was CFO, we built revenue recognition from a blank page on a B2B payments thesis — the principal-agent analysis for processing fees, the timing of subscription versus transaction revenue, and the disaggregation between platform revenue and embedded financing were the high-judgment areas. At NBCU Parks & Resorts, the issues were different — admission revenue versus separately-priced experiences, third-party merchant arrangements within the park, season pass deferral and refund mechanics, multiple-element bundles with accommodations.

The pattern across both: the implementation is not the hard part. The hard part is the ongoing maintenance of the judgments. Variable consideration estimates need to be revisited each period; principal-agent analyses need to be revisited whenever the contract structure changes; license classifications need to be defended at audit. Build a "606 file" per material contract or contract type that captures the judgments in writing, with the citations, and refresh it each year. Auditors are testing those judgments specifically.

For B2B SaaS and marketplace clients I work with through the consulting practice, the most common 606 finding is performance obligation under-identification. Implementation, customization, training, and ongoing subscription are often bundled into "annual contract value" with single-line recognition. The audit fix is straightforward but disruptive — revenue gets re-cut, prior-period comparatives get adjusted, and the auditor wants the controller to defend the revised allocation. Get this right at the start of a contract redesign rather than fixing it under audit pressure.

Related references

IFRS 15 — the converged international standard
ASC 340-40 — Costs to Obtain or Fulfill a Contract with a Customer
ASC 326 — Credit losses on receivables and contract assets
SEC SAB 101 / SAB 104 — legacy SEC revenue guidance (largely superseded but still relevant for transition)