The ASC 606 Five-Step Revenue Recognition Model

FAR coverage of contract identification, performance obligations, transaction price, allocation, and revenue recognition timing.

ASC 606 recognizes revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration the entity expects to receive. FAR questions usually test whether the candidate can apply the sequence, not merely recite it.

The five steps are sequential. If a valid contract does not exist, the remaining steps do not create revenue. If performance obligations are misidentified, transaction price allocation and revenue timing will also be wrong.

The Five-Step Sequence

Step Question Main FAR risk
1. Identify the contract with a customer Does an enforceable customer contract exist? Recognizing revenue before enforceable rights, payment terms, or probable collection exist
2. Identify performance obligations What distinct goods or services were promised? Separating promises that should be combined, or combining promises that are distinct
3. Determine transaction price How much consideration does the entity expect to receive? Ignoring variable consideration, financing, noncash consideration, or consideration payable to the customer
4. Allocate transaction price How should the price be assigned to performance obligations? Allocating based on cost or billing schedule instead of relative standalone selling price
5. Recognize revenue When does control transfer? Recognizing revenue based on cash collection instead of satisfaction of the performance obligation
    flowchart LR
	    A["1. Identify contract"] --> B["2. Identify performance obligations"]
	    B --> C["3. Determine transaction price"]
	    C --> D["4. Allocate transaction price"]
	    D --> E["5. Recognize revenue when control transfers"]

Step 1: Identify The Contract

A contract exists under ASC 606 only when enforceable rights and obligations are present. Contracts can be written, oral, or implied by customary business practice, but the arrangement must satisfy the contract criteria.

Key criteria include:

  • The parties have approved the contract and are committed to perform.
  • Each party’s rights regarding goods or services can be identified.
  • Payment terms can be identified.
  • The contract has commercial substance.
  • Collection of consideration is probable based on the customer’s ability and intent to pay.

The customer must be obtaining goods or services that are outputs of the entity’s ordinary activities. A collaboration or cost-sharing arrangement may not be a customer contract if the counterparty is not purchasing goods or services as a customer.

Contract modifications are also tested in Step 1. A modification is treated as a separate contract when it adds distinct goods or services and the price increases by an amount that reflects standalone selling price. Otherwise, the entity evaluates whether the remaining goods or services are distinct and accounts for the modification prospectively or as part of the existing contract.

Step 2: Identify Performance Obligations

A performance obligation is a promise to transfer a distinct good or service to the customer. A promised good or service is distinct only if both criteria are met:

  • The customer can benefit from the good or service on its own or together with readily available resources.
  • The promise is separately identifiable from other promises in the contract.

This step prevents mechanical separation of every contract line item. If goods or services are highly integrated, highly interdependent, or significantly modify each other, they may form one combined performance obligation.

Fact pattern Likely conclusion
Standard product plus optional support sold separately Multiple performance obligations may exist
Customized system requiring design, integration, and installation Promises may be combined into one performance obligation
Stand-ready service over a contract term A performance obligation satisfied over time
Administrative setup activity that does not transfer a good or service Not a separate performance obligation

Step 3: Determine The Transaction Price

The transaction price is the amount of consideration the entity expects to be entitled to for transferring goods or services. This amount may differ from the stated contract price.

Common adjustments include:

  • Variable consideration, such as rebates, refunds, bonuses, penalties, price concessions, and performance incentives.
  • Significant financing components when payment timing provides a financing benefit.
  • Noncash consideration measured at fair value when applicable.
  • Consideration payable to the customer, which often reduces the transaction price.

Variable consideration is estimated using either the expected value method or the most likely amount method, depending on which better predicts the consideration. The estimate is constrained. Include variable consideration only to the extent it is probable that a significant reversal of cumulative revenue will not occur when the uncertainty is resolved.

The exam trap is recognizing the highest possible bonus or incentive merely because it is contractually available. ASC 606 requires both estimation and constraint.

Step 4: Allocate The Transaction Price

When a contract has more than one performance obligation, the transaction price is allocated based on relative standalone selling prices.

[ \text{Allocated price to obligation} = \frac{\text{Standalone selling price of obligation}}{\text{Total standalone selling prices}} \times \text{Transaction price} ]

Standalone selling price is the price at which the entity would sell the good or service separately to a similar customer in similar circumstances. If directly observable prices are unavailable, the entity estimates them using methods such as adjusted market assessment, expected cost plus margin, or a residual approach when the selling price is highly variable or uncertain.

For example, assume a contract price of $1,600 includes a license with standalone selling price of $900, installation with standalone selling price of $300, and support with standalone selling price of $600. Total standalone selling prices are $1,800. The license allocation is $800, calculated as $900 divided by $1,800 multiplied by $1,600.

Obligation Standalone selling price Allocation
License $900 $800
Installation $300 $267
Support $600 $533
Total $1,800 $1,600

Step 5: Recognize Revenue When Control Transfers

Revenue is recognized when, or as, the entity satisfies each performance obligation by transferring control to the customer. Control means the customer can direct the use of the asset and obtain substantially all remaining benefits.

Revenue is recognized over time if at least one over-time criterion is met:

  • The customer receives and consumes benefits as the entity performs.
  • The entity creates or enhances an asset the customer controls as it is created or enhanced.
  • The entity creates an asset with no alternative use and has an enforceable right to payment for performance completed to date.

If none of the over-time criteria are met, revenue is recognized at a point in time. Indicators of point-in-time transfer include present right to payment, transfer of legal title, physical possession, significant risks and rewards of ownership, and customer acceptance.

Exam Traps

Trap Better FAR reasoning
Recognizing revenue when cash is received Cash receipt creates revenue only when the performance obligation is satisfied
Treating every listed deliverable as distinct Apply both distinct criteria and combine highly integrated promises
Ignoring collection probability A contract may fail Step 1 if collection is not probable
Allocating based on invoice amounts Use relative standalone selling prices unless a specific exception applies
Recognizing all variable consideration Apply the constraint to avoid significant revenue reversal
Assuming long-term contracts are always over time At least one ASC 606 over-time criterion must be met

Key Takeaways

  • ASC 606 is applied in order: contract, performance obligations, transaction price, allocation, and recognition.
  • A valid contract requires enforceable rights, payment terms, commercial substance, and probable collection.
  • Performance obligations are distinct only when the customer can benefit and the promise is separately identifiable.
  • Variable consideration is estimated and constrained.
  • Transaction price is allocated on relative standalone selling price.
  • Revenue is recognized when control transfers, either over time or at a point in time.

Five-Step Model Knowledge Check

### Which item is required to identify a contract under ASC 606? - [x] Payment terms can be identified and collection is probable - [ ] The contract must be signed only in writing - [ ] Cash must be received before any analysis begins - [ ] The goods or services must always be delivered on the same day > **Explanation:** ASC 606 requires identifiable payment terms and probable collection, among other contract criteria. ### What makes a promised good or service distinct? - [x] The customer can benefit from it and the promise is separately identifiable in the contract - [ ] It appears on a separate invoice line - [ ] It is expensive to produce - [ ] It is delivered by a third-party carrier > **Explanation:** A promise is distinct only if it is both capable of being distinct and distinct within the contract. ### Which item is an example of variable consideration? - [x] A performance bonus that depends on meeting a completion deadline - [ ] A fixed price with no refund rights - [ ] A security deposit held outside the contract price - [ ] A routine sales invoice number > **Explanation:** Bonuses, penalties, rebates, refunds, and price concessions can make consideration variable. ### How is transaction price generally allocated to multiple performance obligations? - [x] Based on relative standalone selling prices - [ ] Based on the order in which cash is received - [ ] Equally to every contract line item - [ ] Based only on the entity's cost > **Explanation:** ASC 606 generally allocates the transaction price using relative standalone selling prices. ### When is revenue recognized under ASC 606? - [x] When, or as, control of the promised good or service transfers to the customer - [ ] When the contract is first discussed - [ ] Only when all cash has been collected - [ ] Always at contract signing > **Explanation:** Revenue recognition is tied to satisfaction of performance obligations through transfer of control. ### Which fact supports over-time revenue recognition? - [x] The asset has no alternative use and the entity has an enforceable right to payment for performance completed to date - [ ] The customer pays late - [ ] The contract has a single invoice - [ ] The entity prefers smoother earnings > **Explanation:** One over-time criterion is no alternative use plus enforceable right to payment for performance completed to date.
Revised on Monday, June 15, 2026