ASC 606 Five-Step Model: A Practitioner Walkthrough

The ASC 606 five-step model is the operational framework every US GAAP preparer uses to decide when and how much revenue to recognize from contracts with customers. If you already know what ASC 606 is, this guide goes further: it walks each step with the judgment calls that actually cause restatements, the interdependencies that trip up even experienced teams, and the specific areas where the SEC staff pushes back hardest.

For a grounding in the standard's background and core principle, see ASC 606 Revenue Recognition: What It Is and How It Works. This article is for finance and accounting teams who need to apply the model correctly to their own contracts.

Key takeaway: The five steps are sequential but interdependent. A wrong call in Step 2 (performance obligations) corrupts your allocation in Step 4 and your timing in Step 5. Getting the sequence right is not just good process; it is the difference between defensible revenue and an SEC comment letter.

What Are the 5 Steps Under ASC 606?

The five steps are: (1) identify the contract with a customer, (2) identify the performance obligations in the contract, (3) determine the transaction price, (4) allocate the transaction price to the performance obligations, and (5) recognize revenue when or as each performance obligation is satisfied. They come directly from FASB ASC Topic 606, issued jointly with the IASB (as IFRS 15) in May 2014 and effective for public companies for annual periods beginning after December 15, 2017.

The standard replaced more than 200 pieces of industry-specific US GAAP revenue guidance with this single principles-based framework. That consolidation created consistency, but it also shifted the burden onto preparers to exercise judgment at every step.

Step 1: Identify the Contract with a Customer

A contract is in scope only when five criteria are all met under ASC 606-10-25-1: both parties have approved and are committed; each party's rights are identifiable; payment terms are identifiable; the contract has commercial substance; and collection of substantially all consideration is probable.

Contracts can be written, oral, or implied by customary business practices. The form does not matter; enforceability does.

Where this gets hard

The collection criterion is the one that catches teams off guard. "Probable" under ASC 606 means the customer has the ability and intention to pay, not that payment is guaranteed. For healthcare entities billing insurers, or SaaS companies with high-churn customer segments, this assessment requires real evidence, not a blanket assumption.

If the five criteria are not met, revenue is recognized only when the entity has received substantially all consideration and performance is complete, or the contract is terminated. That is a materially different outcome, and it applies more often than preparers expect in early-stage or distressed customer situations.

Contract combinations also matter here. Two or more contracts entered into at or near the same time with the same customer may need to be combined if they were negotiated as a package, the consideration in one depends on the other, or the goods and services are a single performance obligation.

Step 2: Identify the Performance Obligations in the Contract

A performance obligation is a promise to transfer a distinct good or service to the customer. Under ASC 606-10-25-14, a good or service is distinct only if both criteria are met: the customer can benefit from it on its own or with other readily available resources (capable of being distinct), AND the entity's promise to transfer it is separately identifiable from other promises in the contract (distinct within the context of the contract).

Both tests must pass. Failing either means the item gets bundled with other promises until the combined bundle is distinct.

The two-question test in practice

As EY's Financial Reporting Developments guide notes, the first question (capable of being distinct) is generally easier to satisfy than the second. Entities often incorrectly conclude goods or services are not distinct simply because they are sold together. The correct analysis asks whether the nature of the entity's promise is to transfer each item individually, or to deliver a combined output to which the items are merely inputs.

Indicators that promises are NOT separately identifiable, and should be combined, include:

• The entity provides a significant integration service (e.g., constructing a building from components)
• One good or service significantly modifies or customizes another (e.g., specialized equipment requiring custom configuration)
• The goods and services are highly interdependent or interrelated (e.g., software with critical updates that alter its core functionality)

The cascade effect: why Step 2 errors are the most expensive

This is the step that competitors' guides underplay. If you bundle two obligations that should be separate, you defer revenue that should be recognized earlier. If you separate two obligations that should be combined, you may accelerate revenue that has not yet been earned. Either error flows directly into Step 4 (you are allocating to the wrong units of account) and Step 5 (you are recognizing at the wrong time). FASB's post-implementation review identified performance obligation identification as one of the top ongoing challenges under the standard.

Principal vs. agent: a Step 2 and Step 5 issue

When a third party is involved in providing goods or services, the entity must decide whether it is a principal (records gross revenue) or an agent (records net revenue, i.e., the commission or fee). The controlling question under ASU 2016-08 is whether the entity controls the specified good or service before it is transferred to the customer.

Three indicators of control:

1. The entity has primary responsibility for fulfilling the promise
2. The entity has inventory risk before or after transfer
3. The entity has discretion in setting the price

As Deloitte's On the Radar guide states: "Entities often have difficulty determining the appropriate judgments to apply in the identification of performance obligations and the assessment of whether an entity is a principal or an agent. Not surprisingly, these are two topics of the revenue standard on which entities commonly seek the SEC staff's views in prefiling submissions."

Getting this wrong has a direct P&L impact: a principal records gross revenue with a corresponding cost; an agent records only the net amount retained.

The series guidance: a practical simplification for SaaS

One gap in most five-step explainers is ASC 606-10-25-14B, the series guidance. If a series of distinct goods or services is substantially the same and has the same pattern of transfer to the customer, the entity can account for the entire series as a single performance obligation. This is commonly applied to SaaS subscriptions and managed services, simplifying allocation and recognition. But it requires careful assessment: the series criteria must actually be met, not assumed.

Industry examples

• SaaS: A vendor sells a one-year subscription plus implementation services. Are these one obligation or two? If implementation is not distinct (because it significantly customizes the SaaS platform and the customer cannot benefit from implementation alone), all revenue is deferred and recognized over the subscription period. If implementation is distinct, it may be recognized separately, often accelerating revenue.
• Construction: A general contractor builds a hospital. The design, site preparation, and construction are inputs to a single combined output. One performance obligation.
• Healthcare: A hospital provides an emergency room visit, lab work, and imaging. Each service may be a separate obligation if the patient can benefit from each independently.

Step 3: Determine the Transaction Price

The transaction price is the amount of consideration the entity expects to be entitled to in exchange for transferring goods or services to the customer, per ASC 606-10-32-2. It includes fixed amounts, variable consideration, significant financing components, non-cash consideration, and consideration payable to the customer.

Variable consideration and the constraint

Variable consideration (discounts, rebates, bonuses, royalties, refunds, penalties) must be estimated using either the expected value method (probability-weighted average) or the most likely amount method. The right method depends on which better predicts the amount the entity will be entitled to.

But estimation alone is not enough. The constraint under ASC 606-10-32-11 requires that variable consideration be included in the transaction price only to the extent it is probable that a significant reversal in cumulative revenue recognized will not occur when the uncertainty resolves.

Factors that increase the likelihood of a significant reversal, and therefore require more conservative constraint, include:

• The outcome is highly susceptible to factors outside the entity's control (weather, market prices, counterparty behavior)
• The uncertainty is not expected to resolve for a long period
• The range of possible outcomes is broad
• The entity has limited experience with similar contracts

In practice, this means a software company with a usage-based pricing component should not recognize the full estimated usage upfront. It recognizes only the amount where reversal is not probable. The constraint is one of the most frequently misapplied concepts in ASC 606 and a recurring subject in SEC comment letters.

Significant financing components

If the timing of payments provides either party with a significant benefit of financing, the transaction price must be adjusted to reflect that financing. A practical expedient exists: if the period between transfer and payment is one year or less, the entity need not adjust for financing.

Step 4: Allocate the Transaction Price to Performance Obligations

The transaction price is allocated to each performance obligation based on relative standalone selling prices (SSP), per ASC 606-10-32-31. If SSP is not directly observable, the entity must estimate it.

SSP estimation methods

The residual approach is restricted. It cannot be used simply because it is convenient or because it produces a favorable allocation. Using it without meeting the "highly variable or uncertain" threshold is a common error that auditors flag.

Why allocation errors compound

Allocation errors in Step 4 are almost always downstream consequences of Step 2 errors. If you identified the wrong performance obligations, you are allocating to the wrong units of account. The math may balance, but the revenue timing will be wrong. This is why the five steps must be treated as a system, not a checklist.

Step 5: Recognize Revenue When or As a Performance Obligation Is Satisfied

Revenue is recognized when the customer obtains control of the promised good or service, per ASC 606-10-25-27. Control is the ability to direct the use of and obtain substantially all of the remaining benefits from the asset.

Over time vs. point in time

An obligation is satisfied over time if any one of three criteria is met:

1. The customer simultaneously receives and consumes the benefits as the entity performs (e.g., a cleaning service)
2. The entity's performance creates or enhances an asset the customer controls as it is created (e.g., construction on customer-owned land)
3. The entity's performance does not create an asset with alternative use, AND the entity has an enforceable right to payment for performance completed to date

If none of these criteria are met, the obligation is satisfied at a point in time.

The third criterion is particularly nuanced for construction and long-term service contracts. As KPMG's Handbook on Revenue Recognition notes, the "no alternative use plus enforceable right to payment" test requires careful legal analysis of contract terms, not just an accounting judgment. A contract that allows the customer to cancel without compensating the entity for work performed may fail this criterion even if the asset has no alternative use.

Licenses of intellectual property

Licenses require a separate analysis that most five-step guides skip entirely. Under ASC 606-10-55-54, a license is recognized at a point in time (right to use) if the IP has significant standalone functionality and the customer can direct its use and obtain substantially all remaining benefits as the IP exists at the grant date. A license is recognized over time (right to access) if the entity's ongoing activities are expected to significantly affect the IP to which the customer has rights.

For software companies, this distinction determines whether a perpetual license is recognized on delivery or spread over the contract term. For pharma companies licensing a drug compound, it determines whether milestone payments are recognized immediately or deferred. The FASB's post-implementation review flagged this as an ongoing area of difficulty.

Measuring progress for over-time obligations

For obligations satisfied over time, the entity must select a single method of measuring progress that best depicts the transfer of control. Two broad approaches:

• Output methods: Units delivered, milestones reached, surveys of performance completed. Best when outputs can be directly measured.
• Input methods: Costs incurred relative to total expected costs (cost-to-cost), labor hours. Best when outputs are difficult to measure directly, common in construction and professional services.

The chosen method must be applied consistently to similar obligations and in similar circumstances. A change in method is a change in estimate.

Contract Modifications: Re-Running the Model

Contract modifications (change orders, amendments, renewals, scope changes) require the entity to assess whether the modification creates a new contract or changes the existing one. Under ASC 606-10-25-10, a modification is a new contract only if both conditions are met:

1. The scope increases by adding distinct goods or services
2. The price increases by an amount that reflects the SSP of the additional goods or services

If either condition fails, the modification is accounted for as part of the existing contract, either prospectively (if remaining goods or services are distinct) or using a cumulative catch-up adjustment (if remaining goods or services are not distinct from those already transferred).

Subscription businesses, construction companies, and any entity with long-term contracts face this question regularly. For a detailed walkthrough with worked journal entries, see How to Account for ASC 606 Contract Modifications: Three Worked Examples.

ASU 2021-08: The M&A Wrinkle

One amendment that most ASC 606 guides miss entirely: ASU 2021-08 requires acquirers in a business combination to apply ASC 606 to recognize and measure contract assets and contract liabilities acquired from the target. Before this amendment, acquirers often reset deferred revenue to fair value at acquisition, which was typically lower than the carrying amount, suppressing post-acquisition revenue. ASU 2021-08 was effective for public entities for fiscal years beginning after December 15, 2022. If your company is M&A-active, this amendment directly affects how you account for acquired contract liabilities.

Where the SEC Pushes Back: Common Comment Letter Themes

The SEC Division of Corporation Finance has consistently flagged ASC 606 issues in comment letters. The recurring themes:

• Insufficient disaggregation of revenue: Companies disclose one or two revenue categories when the economic factors affecting timing and uncertainty clearly warrant more. ASC 606-10-50 requires disaggregation that depicts how economic factors affect revenue; "product" and "service" is rarely enough.
• Inadequate description of performance obligations: Boilerplate language that does not explain what the entity actually promises, when it is satisfied, and what the significant payment terms are.
• Unclear over-time vs. point-in-time rationale: Disclosures that state a conclusion without explaining the criterion met or the evidence supporting it.
• Principal vs. agent conclusions without adequate support: Particularly for marketplace and platform businesses where the control analysis is genuinely complex.

For companies preparing an S-1 or navigating SEC review, see ASC 606 Disclosures for IPO: Build the S-1 Revenue Note for a detailed treatment of disclosure requirements and SEC correspondence patterns.

ASC 606 vs. IFRS 15: Key Differences

ASC 606 and IFRS 15 were issued as a converged standard and are substantially identical. The differences are narrow but matter for multinational preparers:

For most practical purposes, the five-step analysis is the same under both standards.

FAQ

Is ASC 606 still relevant in 2026? Yes. ASC 606 has been fully effective for several years, but it continues to generate SEC comment letters, restatements, and FASB post-implementation guidance. The standard is principles-based, which means judgment calls never become routine. The FASB's post-implementation review confirmed the standard is working as intended but identified ongoing challenges in performance obligation identification, variable consideration, principal vs. agent, and licenses of IP.

Does ASC 606 apply to private companies? Yes. ASC 606 applies to all entities with contracts with customers under US GAAP, public and private. Private companies had a later effective date (annual periods beginning after December 15, 2018) but are fully subject to the standard. Some sources incorrectly imply a revenue threshold for applicability; there is none under GAAP.

What is the most common mistake companies make under ASC 606? Performance obligation identification errors in Step 2 are the most consequential, because they cascade into incorrect allocation (Step 4) and incorrect timing (Step 5). Principal vs. agent misclassification is the most frequently cited in SEC prefiling submissions.

How do contract modifications affect the five-step analysis? Modifications require the entity to assess whether a new contract has been created or the existing one has been changed. The accounting treatment, prospective or cumulative catch-up, depends on whether the remaining goods or services are distinct. See How to Account for ASC 606 Contract Modifications: Three Worked Examples for worked scenarios.

What disclosures does ASC 606 require? Under ASC 606-10-50, entities must disclose disaggregated revenue, contract balances (contract assets, contract liabilities, receivables), performance obligation descriptions (including when satisfied, significant payment terms, variable consideration, and obligations for returns), and significant judgments and changes in judgments. These requirements are extensive and frequently cited as insufficient in SEC comment letters.

Can AI help with ASC 606 compliance? AI tools can assist with contract parsing, obligation tagging, and allocation calculations, but the judgment-intensive steps (performance obligation identification, variable consideration constraint, principal vs. agent) require human review. For a detailed assessment of where AI adds value and where it does not, see AI Revenue Recognition ASC 606 Automation: 2026 Practitioner Walkthrough.