Revenue Recognition Under ASC 606: The Five-Step Model

Published: March 27, 2026

Article by Ryan O'Connell, CFA, FRM

Revenue recognition is one of the most critical topics in financial reporting. It determines when a company reports income on its financial statements — and getting it wrong can lead to SEC enforcement actions, earnings restatements, and investor losses. Under ASC 606, entities that enter into contracts with customers follow a single five-step model to recognize revenue, replacing over 100 industry-specific legacy standards with one unified framework.

What Is Revenue Recognition Under ASC 606?

Revenue recognition is the process of determining when and how much revenue a company reports on its income statement. Under ASC Topic 606 (Revenue from Contracts with Customers), revenue is recognized when — or as — an entity satisfies a performance obligation by transferring a promised good or service to a customer.

Before ASC 606, U.S. GAAP contained more than 100 revenue recognition standards spread across industry-specific guidance (software, construction, real estate, etc.). Companies in different industries applied fundamentally different rules to similar transactions, making comparisons difficult for investors and analysts. SEC enforcement cases — including Qwest Communications, Homestore.com, and Lantronix — highlighted how inconsistent standards enabled premature or improper revenue recognition.

The FASB and IASB jointly developed ASC 606 (and its international counterpart, IFRS 15) to create a single, principles-based framework applicable across all industries. While the two standards are largely converged, some differences remain — notably in the probability threshold for variable consideration. ASC 606 applies to all revenue from contracts with customers in scope; it does not govern interest income, lease payments, insurance premiums, or other non-contract-based inflows.

The Five-Step Revenue Recognition Model

ASC 606 structures revenue recognition into a sequential five-step process. Every revenue transaction — from a simple retail sale to a multi-element software arrangement — flows through these same five steps:

To illustrate how the five steps work together, consider a running example: CloudServe Inc., a SaaS company that sells a 3-year hosted cloud platform subscription (standalone selling price: $200,000), implementation services (SSP: $30,000), and premium support (SSP: $90,000) in a single contract for a bundled price of $250,000.

Step 1 — Identify the Contract with a Customer

A contract is an agreement between two or more parties that creates enforceable rights and obligations. Under ASC 606, a contract exists when all five criteria are met:

1. Approval and commitment — all parties have approved the contract (written, oral, or implied by customary business practices)
2. Identifiable rights — each party’s rights regarding the goods or services to be transferred can be identified
3. Payment terms — the payment terms for the goods or services can be identified
4. Commercial substance — the contract has commercial substance (the risk, timing, or amount of future cash flows is expected to change)
5. Collectibility — it is probable that the entity will collect the consideration to which it will be entitled

Combining contracts: Two or more contracts entered into at or near the same time with the same customer must be combined and treated as a single contract if any of the following apply: they were negotiated as a package with a single commercial objective, the consideration in one contract depends on the other, or the goods/services promised are a single performance obligation.

Contract modifications: When the parties change the scope or price of an existing contract, the accounting depends on the nature of the change:

• Separate contract — if the modification adds distinct goods/services at their standalone selling price, treat it as a new, separate contract
• Termination and new contract — if the remaining goods/services are distinct but the modification is not at standalone selling price, terminate the old contract and create a new one (reallocating any remaining consideration)
• Cumulative catch-up — if the remaining goods/services are not distinct from those already transferred, update the transaction price and measure of progress with a cumulative catch-up adjustment

Step 2 — Identify the Performance Obligations

A performance obligation is a promise to transfer a distinct good or service (or a bundle of goods or services) to the customer. A good or service is distinct if both conditions are met:

1. Capable of being distinct — the customer can benefit from the good or service on its own or together with other readily available resources
2. Distinct within the context of the contract — the promise to transfer the good or service is separately identifiable from other promises (i.e., not highly interdependent or interrelated)

Series guidance: A series of distinct goods or services that are substantially the same and have the same pattern of transfer (e.g., daily cleaning services over 12 months) is treated as a single performance obligation. This simplifies accounting for recurring service contracts.

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. Four factors can complicate the determination:

Variable Consideration

When the transaction price includes variable amounts — such as performance bonuses, penalties, rebates, or right-of-return provisions — the entity estimates the variable consideration using either the expected value method (probability-weighted) or the most likely amount method, whichever better predicts the amount.

Other Transaction Price Adjustments

• Significant financing component — if the timing of payments differs significantly from the timing of transfer, the entity evaluates whether a significant financing component exists and adjusts the transaction price for the time value of money using an appropriate discount rate. The assessment considers the difference between the promised consideration and the cash selling price, the length of time, and prevailing interest rates. A practical expedient permits entities to ignore the financing component when the period between transfer and payment is one year or less.
• Noncash consideration — measured at fair value (e.g., a customer pays with equipment instead of cash)
• Consideration payable to a customer — volume discounts, rebates, coupons, and similar payments generally reduce the transaction price. However, if the payment is for a distinct good or service the customer transfers to the entity (e.g., the customer provides advertising or shelf-space services), it is accounted for as a purchase rather than a reduction of revenue

Step 4 — Allocate the Transaction Price

When a contract contains multiple performance obligations, the transaction price must be allocated to each obligation based on its relative standalone selling price (SSP). The SSP is the price at which the entity would sell the good or service separately to a customer.

When standalone selling prices are not directly observable, entities estimate them using one of three methods:

• Adjusted market assessment approach — estimate the price customers in the market would be willing to pay (e.g., competitor pricing with adjustments for entity-specific factors)
• Expected cost plus a margin approach — forecast the costs to satisfy the obligation and add an appropriate profit margin
• Residual approach — subtract all other observable SSPs from the total transaction price (permitted only when the SSP is highly variable or uncertain)

Step 5 — Recognize Revenue When Each Obligation Is Satisfied

Revenue is recognized when (or as) the entity satisfies each performance obligation by transferring control of the promised good or service to the customer. Control means the customer has the ability to direct the use of — and obtain substantially all the remaining benefits from — the asset.

Over-Time Recognition

Revenue is recognized over time if any one of the following criteria is met:

1. The customer simultaneously receives and consumes the benefits as the entity performs (e.g., routine cleaning services)
2. The entity’s performance creates or enhances an asset that the customer controls as it is created (e.g., building on the customer’s land)
3. The entity’s performance does not create an asset with an alternative use, and the entity has an enforceable right to payment for performance completed to date (e.g., custom manufacturing to customer specs)

For over-time obligations, entities measure progress toward completion using either output methods (units delivered, milestones reached) or input methods (costs incurred relative to total estimated costs — the cost-to-cost method).

Point-in-Time Recognition

If none of the over-time criteria are met, revenue is recognized at a point in time when control transfers. Indicators that control has transferred include:

• The entity has a present right to payment for the asset
• The customer has legal title to the asset
• The entity has transferred physical possession
• The customer has the significant risks and rewards of ownership
• The customer has accepted the asset

Presentation: Contract Assets, Receivables, and Contract Liabilities

The timing difference between performance and payment creates three balance sheet items:

• Receivable — the entity’s unconditional right to consideration (only the passage of time is required before payment is due)
• Contract asset — the entity’s right to consideration in exchange for goods/services already transferred, where that right is conditioned on something other than the passage of time (e.g., the entity must satisfy another performance obligation or meet a milestone before it can bill)
• Contract liability (unearned revenue) — the customer has paid consideration before the entity has performed; reported as a liability until the performance obligation is satisfied

Contract Costs Under ASC 606

ASC 606 also provides guidance on capitalizing certain costs related to customer contracts:

• Incremental costs to obtain a contract — costs that would not have been incurred if the contract had not been obtained (e.g., sales commissions) are capitalized as an asset if the entity expects to recover them. A practical expedient allows expensing these costs immediately if the amortization period would be one year or less.
• Costs to fulfill a contract — capitalized only if they (1) relate directly to an existing or anticipated contract, (2) generate or enhance resources used to satisfy performance obligations, and (3) are expected to be recovered

Capitalized contract costs are amortized on a systematic basis consistent with the pattern of transfer and are subject to impairment testing when the carrying amount exceeds the remaining consideration expected minus direct costs to satisfy the obligations.

Special ASC 606 Revenue Recognition Issues

Several transaction types require special attention under the five-step model:

Bill-and-Hold Arrangements

In a bill-and-hold arrangement, the seller invoices the customer but retains physical possession of the goods. Revenue is recognized only when all four conditions are met:

1. There is a substantive reason for the arrangement (e.g., the customer lacks warehouse space)
2. The product has been separately identified as belonging to the customer
3. The product is currently ready for physical transfer to the customer
4. The entity cannot use the product or direct it to another customer

Even when product revenue is recognized, any custodial or storage services the seller provides may constitute a separate performance obligation with revenue recognized over the storage period.

Principal vs. Agent

When multiple parties are involved in delivering goods or services to a customer, each entity must determine whether it is a principal (controls the good or service before transfer) or an agent (arranges for another party to provide it). The core test is control: does the entity obtain control of the specified good or service before it is transferred to the customer?

• Principal — controls the good/service before transfer; recognizes gross revenue
• Agent — does not obtain control; recognizes only the net fee or commission

Supporting indicators include whether the entity has primary responsibility for fulfillment, inventory risk before or after transfer, and discretion in establishing pricing. For example, an online travel platform that does not obtain control of hotel rooms before they are provided to the traveler acts as an agent and reports only its commission as revenue.

Consignment Arrangements

In a consignment, the consignor ships goods to a consignee (typically a retailer), but the consignor retains title until the goods are sold to the end customer. The consignor does not recognize revenue upon shipment — revenue is recognized only when the consignee notifies the consignor that the goods have been sold. The consignee records only its commission as revenue, never the full sales price of the goods.

Right of Return

When a customer has the right to return a product, the entity recognizes revenue only for the consideration it expects to keep. The accounting requires:

• A refund liability for the amount expected to be returned (not contra-revenue)
• An asset for expected returns representing the right to recover products from customers (measured at the former carrying amount, less expected recovery costs)

Both estimates are updated at each reporting date based on changes in expectations.

Real-World Impact

ASC 606 vs. Legacy Revenue Standards

ASC 606 replaced a patchwork of industry-specific guidance with a single principles-based framework. Understanding what changed helps contextualize why the standard matters:

Industries most affected by the transition included software (where vendor-specific objective evidence requirements were eliminated), telecommunications (multi-element arrangements restructured), and construction (percentage-of-completion guidance incorporated into the over-time framework). Companies adopted ASC 606 using either the full retrospective method (restating prior periods) or the modified retrospective method (cumulative adjustment at adoption date).

Common Mistakes in Revenue Recognition

Even experienced accountants make errors when applying the five-step model. Here are the most frequent mistakes and how to avoid them:

Limitations and Judgment Areas Under ASC 606

While ASC 606 improved consistency, the standard still requires significant professional judgment in several areas:

1. Standalone Selling Price Estimation — When SSPs are not directly observable, management must choose among three estimation methods. Different methods can yield materially different allocations, directly affecting the timing of revenue recognition across performance obligations.

2. Variable Consideration Constraints — Determining whether including variable consideration would result in a significant revenue reversal requires judgment about future outcomes. Management may have incentives to be overly optimistic, inflating current-period revenue.

3. Over-Time vs. Point-in-Time Determination — The three over-time criteria involve subjective assessments — particularly the “no alternative use” criterion and what constitutes an “enforceable right to payment.” Different interpretations can shift large amounts of revenue between periods.

4. Industry-Specific Interpretations — Despite the goal of a single standard, industry-specific application guidance continues to evolve through FASB Technical Inquiries, SEC staff speeches, and AICPA Revenue Recognition Task Force guidance. Complete uniformity across industries has not been fully achieved.