5 Steps of Revenue Recognition (ASC 606): CPA FAR Guide With Examples

Revenue Recognition Principle Explained (ASC 606 Guide 2026)

The 5 steps of revenue recognition under ASC 606 are: (1) identify the contract, (2) identify performance obligations, (3) determine the transaction price, (4) allocate the price, and (5) recognise revenue when obligations are satisfied. This five-step model applies to virtually every company reporting under US GAAP and is a high-weight topic on the CPA FAR exam.

What Are the 5 Steps of Revenue Recognition Under ASC 606?

The five steps of revenue recognition under ASC 606 (Revenue from Contracts with Customers) provide a single framework for determining when and how much revenue a company records. Issued by FASB in 2014 and effective for all entities since 2019, ASC 606 replaced dozens of industry-specific rules with one principle-based model that CPA FAR candidates must master.

Before ASC 606, a software company, a construction firm, and a retailer each followed different revenue rules. Now every entity follows the same five steps. This is why the topic carries significant weight in the CPA exam syllabus and appears in both MCQs and simulations on FAR.

The 5-Step Revenue Recognition Model Explained With Examples

Each of the five steps of revenue recognition serves a distinct purpose. Below, we break down every step with a plain-English explanation, the technical criteria from ASC 606, and a short example so you can see exactly how it works in practice. If you are preparing for FAR, pay special attention to the exam tips in each step.

Step 1 — Identify the Contract With a Customer

A contract exists when all five criteria are met: (a) both parties approve and commit, (b) each party's rights are identifiable, (c) payment terms are identifiable, (d) the contract has commercial substance, and (e) collection is probable (75-80% threshold under US GAAP).

Example: ABC Software signs a 3-year subscription deal with Client X for $36,000, payable annually. Both parties signed, the rights (software access) and payment terms ($12,000/year) are clear, it has commercial substance, and Client X has strong credit. A valid contract exists on the signing date.

Step 2 — Identify the Performance Obligations

A performance obligation is a promise to transfer a distinct good or service. A good or service is distinct if (a) the customer can benefit from it on its own or together with readily available resources, and (b) the promise is separately identifiable from other promises in the contract.

Example: In the ABC Software deal, the contract includes: (1) the software licence, (2) installation services, and (3) two years of technical support. If the customer could buy installation from a third party and the support is separately identifiable, there are three performance obligations.

Step 3 — Determine the Transaction Price

The transaction price is the amount of consideration the entity expects to receive. It can include fixed amounts, variable consideration (discounts, rebates, penalties, bonuses), the time value of money, non-cash consideration, and consideration payable to a customer.

Example: A construction company signs a $500,000 fixed-fee contract with a $50,000 performance bonus if completed early. The entity estimates an 80% probability of earning the bonus. Using the most-likely-amount method, the transaction price is $550,000 (since the bonus is probable). Under the expected-value method, it would be $500,000 + (80% x $50,000) = $540,000.

Step 4 — Allocate the Transaction Price

Allocate the total transaction price to each performance obligation based on relative standalone selling prices (SSP). If an observable SSP is not available, estimate it using the adjusted market assessment approach, expected cost plus margin approach, or residual approach.

Example: ABC Software's $36,000 deal has three obligations. Standalone prices: Software licence $24,000, Installation $6,000, Support $10,000. Total SSP = $40,000. Allocation: Software = ($24,000/$40,000) x $36,000 = $21,600. Installation = ($6,000/$40,000) x $36,000 = $5,400. Support = ($10,000/$40,000) x $36,000 = $9,000.

Step 5 — Recognise Revenue When (or As) Performance Obligations Are Satisfied

Revenue is recognised when control of the good or service transfers to the customer. This happens either over time or at a point in time. Revenue is recognised over time if any one of three criteria is met: (a) the customer simultaneously receives and consumes the benefits, (b) the entity's performance creates or enhances an asset the customer controls, or (c) the entity's performance does not create an asset with alternative use and the entity has an enforceable right to payment for work completed.

Example: ABC Builders constructs a custom home for $500,000. The customer owns the land (controls the asset as it is built), and ABC has an enforceable right to payment. Revenue is recognised over time using the cost-to-cost input method. If 40% of costs are incurred by year-end, ABC recognises $200,000 in revenue.

ASC 606 vs IFRS 15: Key Differences for CPA and DipIFR Students

ASC 606 (US GAAP) and IFRS 15 (international) are converged standards that share the same five-step model. However, several practical differences exist that matter for CPA FAR candidates and professionals studying for the ACCA Diploma in IFRS (DipIFR). The table below highlights the most exam-relevant differences.

If you work in a multinational environment and need both US GAAP and IFRS expertise, consider pairing your CPA with a DipIFR qualification. Many finance professionals find that understanding both frameworks strengthens their ability to handle cross-border reporting. Read more in our guide on DipIFR vs AICPA IFRS.

Revenue Recognition Worked Example: Step-by-Step Journal Entries

This worked example walks through all five steps of revenue recognition for a single contract, showing the journal entries at each stage. Use this as a template when practising ASC 606 task-based simulations on the CPA FAR exam.

Journal Entries:

1 January — Cash received and software delivered:

15 January — Installation completed:

31 January — First month of PCS:

How Is Revenue Recognition Tested on the CPA FAR Exam?

Revenue recognition under ASC 606 is one of the highest-weighted topics in the FAR section of the CPA exam. It appears in both multiple-choice questions (MCQs) and task-based simulations (TBSs), typically within the Select Transactions content area. Understanding the exam format helps you allocate study time efficiently. For a full breakdown, see our FAR CPA Exam guide.

Plan your exam order strategically. Many candidates tackle FAR first because it covers the broadest accounting topics. Read our best order to take CPA exams guide for data-backed recommendations. For the latest section-level data, check CPA exam pass rates.

Common Revenue Recognition Mistakes on the CPA Exam

Avoiding these pitfalls can mean the difference between passing and failing FAR. Below are the mistakes that cost candidates the most marks on ASC 606 questions, based on common exam feedback patterns.

• Recognising revenue at contract signing: Revenue is earned on delivery or performance, not when the contract is signed or cash is received.
• Ignoring variable consideration: Forgetting to constrain variable consideration (bonuses, penalties, rebates) or using the wrong estimation method (expected value vs most-likely amount).
• Failing to separate performance obligations: Treating a bundled contract as a single obligation when the goods or services are distinct.
• Using the wrong SSP allocation method: Defaulting to equal allocation instead of relative standalone selling price.
• Confusing over-time and point-in-time: Not checking the three over-time criteria before defaulting to point-in-time recognition.
• Mixing up ASC 606 and IFRS 15 collectibility thresholds: Probable means 75-80% under US GAAP but only ~50% under IFRS.

For a broader study strategy covering all FAR topics, explore our how to become a CPA guide and CPA study materials comparison.

Quick Glossary for Revenue Recognition (ASC 606)

• ASC 606 — The FASB accounting standard governing revenue from contracts with customers under US GAAP. It replaced all prior industry-specific revenue guidance.
• Performance Obligation — A promise in a contract to transfer a distinct good or service to the customer. Each obligation is a separate unit of accounting.
• Transaction Price — The total consideration an entity expects to receive in exchange for transferring goods or services to a customer.
• Variable Consideration — Components of the transaction price that can change, such as discounts, rebates, refunds, penalties, and performance bonuses.
• Standalone Selling Price (SSP) — The price at which an entity would sell a promised good or service separately to a customer. Used for allocating the transaction price in Step 4.
• Contract Modification — A change to the scope or price of an existing contract, which may be treated as a separate contract or a modification of the original.
• Over-Time Recognition — Revenue recognised progressively as the entity performs, measured using output methods (units delivered) or input methods (costs incurred). Common for services and long-term construction.
• Point-in-Time Recognition — Revenue recognised at a single moment when control transfers to the customer. Common for product sales and standard deliveries.
• IFRS 15 — The IASB equivalent of ASC 606, used internationally. Tested on the ACCA DipIFR exam.
• Deferred Revenue — A liability representing cash received before the performance obligation is satisfied. Also called unearned revenue or contract liability.

Frequently Asked Questions