01 / 22

Five-Step
Revenue Recognition

Master the ASC 606 framework for recognizing revenue: from identifying the contract to allocating and recognizing the transaction price.

CPA FAR

What Is Revenue Recognition?

Revenue recognition answers a deceptively simple question: when and how much revenue should a company record on its income statement? Under ASC 606 (and IFRS 15), the answer follows a single, unified five-step model that applies to virtually all contracts with customers.

Why Does ASC 606 Matter?

Comparability
One model replaces dozens of industry-specific rules, making financial statements comparable across sectors.
CPA Exam
Revenue recognition is one of the most heavily tested FAR topics. Expect multi-step calculations and journal entries.
Fraud Prevention
Premature or inflated revenue is the most common form of financial statement fraud. ASC 606 adds rigor and transparency.

Key Definitions to Know

1
Contract: An agreement between two or more parties that creates enforceable rights and obligations.
2
Performance Obligation: A promise to transfer a distinct good or service (or a bundle) to the customer.
3
Transaction Price: The amount of consideration an entity expects to receive in exchange for transferring goods or services.
4
Standalone Selling Price (SSP): The price at which an entity would sell a promised good or service separately to a customer.

The Five-Step Model

Step 1 Identify the Contract Step 2 Identify Perf. Obligations Step 3 Determine Transaction Price Step 4 Allocate Price to Obligations Step 5 Recognize Revenue Revenue on Income Statement When (or as) performance obligations are satisfied

Step 1: Identify the Contract

A contract exists when all five criteria are met. If any criterion fails, no revenue can be recognized until it is satisfied.

1
Approval: All parties have approved the contract and are committed to their obligations.
2
Rights: Each party's rights regarding goods or services can be identified.
3
Payment terms: The payment terms for goods or services can be identified.
4
Commercial substance: The contract has commercial substance (future cash flows change).
5
Collectibility: It is probable the entity will collect the consideration.

Step 2: Identify Performance Obligations

A performance obligation is each distinct promise. A good or service is distinct if it meets both criteria below.

Capable of Being Distinct
The customer can benefit from the good or service on its own or together with other readily available resources.
Distinct Within the Contract
The promise is separately identifiable from other promises in the contract (not highly interrelated or interdependent).

Step 3: Determine the Transaction Price

The transaction price is the consideration the entity expects to be entitled to. Several factors can complicate it:

Variable Consideration
Discounts, rebates, refunds, bonuses, penalties. Use the expected value or most likely amount method.
Significant Financing
Adjust for the time value of money if the contract has a significant financing component (> 1 year gap).
Non-Cash Consideration
Measure at fair value. If fair value cannot be reasonably estimated, use the SSP of the promised goods/services.

Step 4: Allocate the Transaction Price

When a contract has multiple performance obligations, allocate the total transaction price to each obligation based on its relative standalone selling price (SSP).

If an observable SSP does not exist, estimate it using one of three approaches:

1
Adjusted market assessment: Estimate the price customers in the market would pay.
2
Expected cost plus a margin: Forecast costs and add an appropriate profit margin.
3
Residual approach: Total transaction price minus observable SSPs of other obligations.

Step 5: Recognize Revenue

Revenue is recognized when (or as) a performance obligation is satisfied by transferring control of the promised good or service to the customer.

Point in Time
Control transfers at a specific moment: delivery, title transfer, or customer acceptance. Example: selling a car.
Over Time
Control transfers continuously. Must meet at least one of three criteria: simultaneous receipt and consumption, entity creates/enhances asset customer controls, or no alternative use + right to payment.

Point in Time vs. Over Time

Point in Time Over Time
When recognized Single moment of transfer Progressively as work is performed
Indicators Right to payment, legal title, physical possession, risk/reward transfer, acceptance Customer simultaneously receives/consumes, entity's work enhances customer asset, no alternative use
Example Retail product sale Construction contract, SaaS subscription
Measurement Full amount at transfer Output or input method

How to Apply the Model

1
Read the contract facts carefully. Verify all five contract criteria are met. If not, stop: no revenue yet.
2
List every promise. Identify each distinct good or service. Apply the "capable + separately identifiable" test.
3
Calculate the transaction price. Include fixed amounts, estimate variable consideration, and apply the constraint.
4
Allocate using relative SSP. Compute each obligation's share: \(\text{SSP}_i \div \sum \text{SSP}\).
5
Determine timing. Is it "over time" (3 criteria)? If not, use "point in time." Recognize accordingly.

Example 1: Simple Product Sale

1
Contract: Purchase agreement is approved, rights/terms are clear, commercial substance exists, collection is probable. ✓
2
Performance obligation: One: deliver the laptop.
3
Transaction price: \(\$1{,}200\) (fixed, no variable consideration).
4
Allocate: Only one obligation, so full \(\$1{,}200\) is allocated to it.
5
Recognize: At point in time (March 15, upon delivery). Debit Accounts Receivable, Credit Revenue for \(\$1{,}200\).

Example 2: Multiple Obligations

Step 4 Allocation:

License
\(\$10{,}000 \times \frac{\$8{,}000}{\$12{,}000} = \$6{,}667\)
Support
\(\$10{,}000 \times \frac{\$4{,}000}{\$12{,}000} = \$3{,}333\)

Example 3: Variable Consideration

1
Transaction price (most likely amount): Since 70% > 50%, the most likely outcome includes the bonus: \(\$500{,}000 + \$50{,}000 = \$550{,}000\).
2
Apply the constraint: Is it probable a significant reversal will NOT occur? If yes, include the full \(\$550{,}000\). If uncertain, constrain and include only \(\$500{,}000\) until more certain.
3
Recognize over time: Construction satisfies over-time criteria (no alternative use + right to payment). Use input method: costs incurred to date \(\div\) total estimated costs.

Common Mistakes

✕ Recognizing Too Early
Recording revenue when the contract is signed rather than when performance obligations are satisfied. Revenue requires transfer of control, not just a signature.
✕ Ignoring the Constraint
Including all variable consideration without checking whether a significant revenue reversal is probable. Always apply the constraint test.
✕ Lumping Obligations
Treating a bundle as one obligation when the goods/services are actually distinct. Each distinct promise needs its own SSP allocation.

Five-Step Summary

Step Question Answered Key Action
1. Identify Contract Is there a valid contract? Check 5 criteria
2. Perf. Obligations What are we promising? Distinct good/service test
3. Transaction Price How much will we receive? Variable consideration + constraint
4. Allocate Price How much per obligation? Relative SSP allocation
5. Recognize Revenue When do we record it? Point in time or over time

Question 1 of 5

Which of the following is NOT one of the five criteria required to identify a contract under ASC 606?

Question 2 of 5

A company sells a phone (\(\text{SSP} = \$600\)) and a 2-year warranty (\(\text{SSP} = \$200\)) for a bundled price of \$700. How much revenue is allocated to the phone?

Question 3 of 5

A construction company builds a custom building on the customer's land. The customer controls the work in progress. Revenue should be recognized:

Question 4 of 5

When estimating variable consideration, the constraint requires that an entity:

Question 5 of 5

If the standalone selling price (SSP) of a performance obligation is not directly observable, which of the following is NOT an acceptable estimation approach under ASC 606?