Quick Summary

• Single Model: ASC 606 replaced industry-specific revenue rules with one five-step model that applies to virtually all contracts with customers.
• Core Principle: Revenue is recognized when (or as) control of a promised good or service transfers to the customer, in an amount reflecting the consideration the entity expects to be entitled to.
• Performance Obligations: Contracts are broken into distinct promises, and the transaction price is allocated across them based on relative standalone selling price.
• Variable Consideration: Discounts, rebates, bonuses, and penalties are estimated and constrained so only amounts that are “probable” not to reverse are recognized.
• Converged with IFRS 15: ASC 606 and IFRS 15 share the same five-step framework, though a handful of practical differences remain.

What Is ASC 606?

ASC 606, Revenue from Contracts with Customers, is the FASB’s comprehensive revenue recognition standard, introduced through ASU 2014-09 and effective for public entities for annual reporting periods beginning after December 15, 2017 (and one year later for most private companies). It replaced dozens of industry-specific and transaction-specific rules under legacy US GAAP with a single principles-based framework built around one core idea: recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration the entity expects to receive in exchange.

The standard applies to all contracts with customers except those specifically scoped out, such as lease contracts (ASC 842), insurance contracts, financial instruments, and certain non-monetary exchanges between entities in the same line of business.

The Five-Step Model

Every revenue transaction under ASC 606 is analyzed through the same five steps:

• Step 1 — Identify the contract with a customer.
• Step 2 — Identify the performance obligations in the contract.
• Step 3 — Determine the transaction price.
• Step 4 — Allocate the transaction price to the performance obligations.
• Step 5 — Recognize revenue as (or when) each performance obligation is satisfied.

Step 1: Identify the Contract

A contract exists under ASC 606 only when all of the following are met: the parties have approved the contract and are committed to their obligations, each party’s rights regarding the goods or services can be identified, payment terms can be identified, the contract has commercial substance, and it is probable the entity will collect substantially all of the consideration it is entitled to. Two or more contracts entered into at or near the same time with the same customer are combined and accounted for as a single contract when they meet specific combination criteria (for example, they are negotiated as a package with a single commercial objective).

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 that is distinct) to the customer. A good or service is distinct when the customer can benefit from it on its own or together with other readily available resources, and the promise is separately identifiable from other promises in the contract. Goods or services that are highly interrelated — where the entity provides a significant service of integrating them into a combined output — are typically treated as a single performance obligation rather than accounted for separately.

Step 3: Determine the Transaction Price

The transaction price is the amount of consideration an entity expects to be entitled to in exchange for transferring the promised goods or services, excluding amounts collected on behalf of third parties (such as sales tax). Determining it requires consideration of variable consideration, the constraint on variable consideration, significant financing components, non-cash consideration, and consideration payable to the customer.

Step 4: Allocate the Transaction Price

When a contract has more than one performance obligation, the transaction price is allocated to each obligation in proportion to its standalone selling price — the price at which the entity would sell the good or service separately to a similar customer. When a standalone selling price isn’t directly observable, it’s estimated using an adjusted market assessment approach, an expected cost-plus-margin approach, or a residual approach (the last of which is only appropriate in limited circumstances).

Step 5: Recognize Revenue

Revenue is recognized when (point in time) or as (over time) the entity satisfies a performance obligation by transferring control of the promised good or service. A performance obligation is satisfied over time if one of three criteria is met: the customer simultaneously receives and consumes the benefits as the entity performs; the entity’s performance creates or enhances an asset the customer controls as it’s created; or the asset created has no alternative use to the entity and the entity has an enforceable right to payment for performance completed to date. If none of those criteria are met, revenue is recognized at the point in time control transfers — evaluated using indicators such as present right to payment, legal title, physical possession, risks and rewards of ownership, and customer acceptance.

Contract Costs

ASC 606 also addresses the costs of obtaining and fulfilling a contract. Incremental costs of obtaining a contract — commissions being the most common example — are capitalized if the entity expects to recover them, then amortized on a basis consistent with the transfer of the related goods or services (a practical expedient allows expensing these costs immediately if the amortization period would be one year or less). Costs to fulfill a contract are capitalized when they relate directly to an identifiable contract, generate or enhance resources used to satisfy future performance obligations, and are expected to be recovered.

Disclosure Requirements

ASC 606 significantly expanded revenue disclosures. Entities must disclose disaggregated revenue (by category — for example, geography, product line, contract duration, or timing of transfer), information about contract balances (receivables, contract assets, and contract liabilities) and how they’ve changed, remaining performance obligations and when the entity expects to recognize that revenue, and significant judgments made in applying the standard, including how the transaction price was determined and allocated.

ASC 606 vs. IFRS 15

US GAAP and IFRS converged on revenue recognition, so ASC 606 and IFRS 15 share the identical five-step model. A few practical differences remain worth knowing if you report under both frameworks:

For most straightforward contracts, the two standards produce the same accounting outcome — the differences tend to surface in edge cases like licensing arrangements, contract modifications, and collectibility assessments.

Common Pitfalls

• Under-identifying performance obligations: treating a bundle as one obligation when a promise inside it is actually distinct (or vice versa) changes both the timing and pattern of revenue recognition.
• Ignoring the variable consideration constraint: recognizing the full expected value of a bonus or rebate without testing whether a significant reversal is probable.
• Misjudging standalone selling price: defaulting to contract-stated prices instead of a defensible estimate when a good or service isn’t sold separately.
• Weak documentation: because the model relies on judgment, auditors and regulators expect a clear, contemporaneous record of how each of the five steps was applied — not just the final journal entry.