How does the five-step model work under ASC 606?

Core rule Under the ASC 606 Five-Step Revenue Recognition Model, an entity recognizes revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services (ASC 606-10-05-3). How it works The model requires sequential completion of five steps before revenue can be recorded: - Step 1 — Identify the contract: A contract exists when it is approved, has commercial substance, identifies rights and payment terms, and collection is probable (ASC 606-10-25-1). Contracts can be written, oral, or implied by customary business practice. - Step 2 — Identify performance obligations: Each promise to transfer a distinct good or service is a separate performance obligation (ASC 606-10-25-14). A good or service is distinct if the customer can benefit from it on its own and it is separately identifiable from other promises in the contract (ASC 606-10-25-19). Bundled arrangements frequently require disaggregation here — a common area of audit scrutiny. - Step 3 — Determine the transaction price: The transaction price is the amount of consideration an entity expects to receive, ad

How do you apply the variable consideration constraint when estimating rebates or volume discounts under ASC 606-10-32-11?

justed for variable consideration (e.g., rebates, discounts, returns), significant financing components, noncash consideration, and amounts paid to customers (ASC 606-10-32-2). Variable consideration is included only to the extent it is probable a significant revenue reversal will not occur (the constraint under ASC 606-10-32-11). - Step 4 — Allocate the transaction price: The standalone selling price (SSP) of each distinct performance obligation drives allocation (ASC 606-10-32-28). When SSPs are not directly observable, estimation methods include adjusted market assessment, expected cost plus margin, or residual approach (ASC 606-10-32-34). Discounts and variable consideration are generally allocated proportionately unless specific criteria are met (ASC 606-10-32-36 through 32-38). - Step 5 — Recognize revenue: Revenue is recognized when (or as) a performance obligation is satisfied — either over time if one of three criteria is met (ASC 606-10-25-27), or at a point in time based on indicators of control transfer such as right to payment, physical possession, legal title, and risks/rewards of ownership (ASC 606-10-25-30). Practical example Scenario: A SaaS company sells a one-year softwar

What are the specific criteria for over-time revenue recognition under ASC 606-10-25-27, and how do they apply to construction contracts?

e license ($60,000) bundled with implementation services ($15,000) for a combined contract price of $70,000. SSPs are $60,000 and $15,000, respectively (total $75,000). Step 4 allocation: - License: $70,000 × ($60,000 / $75,000) = $56,000 - Implementation: $70,000 × ($15,000 / $75,000) = $14,000 Step 5: Implementation services are recognized over time (3 months). License is recognized ratably over 12 months. At contract inception — cash received upfront: | Account | Dr | Cr | |---|---|---| | Cash | 70,000 | | | Deferred Revenue (Contract Liability) | | 70,000 | End of Month 1 — implementation complete (1/3 of services) + 1 month of license: | Account | Dr | Cr | |---|---|---| | Deferred Revenue | 9,333 | | | Revenue — Implementation Services | | 4,667 | | Revenue — Software License | | 4,667 | (Implementation: $14,000 / 3 = $4,667; License: $56,000 / 12 = $4,667) Common pitfalls - Misidentifying performance obligations in bundled arrangements: Practitioners frequently treat a bundle as a single unit of account, missing required disaggregation. This is especially acute in software, telecom, and franchise arrangements where installation, support, and licenses have distinct SSPs and transfer p

How should a company estimate standalone selling price when no observable SSP exists — and which estimation method is most defensible under audit scrutiny?

atterns. - Improper variable consideration constraint application: Recording the full expected volume rebate or milestone bonus without applying the constraint under ASC 606-10-32-11 leads to revenue overstatement and potential restatement risk — a top SEC comment letter trigger. - Over-time vs. point-in-time errors: Defaulting to over-time recognition for service contracts without confirming one of the three ASC 606-10-25-27 criteria is met (customer simultaneously receives/consumes, entity's performance creates/enhances a customer-controlled asset, or no alternative use with enforceable right to payment) is a recurring audit deficiency. Key paragraphs to know - ASC 606-10-25-1 — Contract existence and enforceability criteria (Step 1) - ASC 606-10-25-14 and 25-19 — Distinct good or service and separability criteria (Step 2) - ASC 606-10-32-11 — Variable consideration constraint (Step 3) - ASC 606-10-32-28 and 32-34 — SSP estimation methods for allocation (Step 4) - ASC 606-10-25-27 and 25-30 — Over-time vs. point-in-time recognition criteria (Step 5) - ASC 606-10-50-1 through 50-22 — Disclosure requirements for disaggregated revenue, contract balances, and remaining performance obligations

ASC 606 Five-Step Revenue Recognition Model

ASC 606 Five-Step Revenue Recognition Model — Core Rule

Under the ASC 606 Five-Step Revenue Recognition Model, an entity recognizes revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services (ASC 606-10-05-3).

How ASC 606 Five-Step Revenue Recognition Model Works

The model requires sequential completion of five steps before revenue can be recorded:

Step 1 — Identify the contract: A contract exists when it is approved, has commercial substance, identifies rights and payment terms, and collection is probable (ASC 606-10-25-1). Contracts can be written, oral, or implied by customary business practice.

Step 2 — Identify performance obligations: Each promise to transfer a distinct good or service is a separate performance obligation (ASC 606-10-25-14). A good or service is distinct if the customer can benefit from it on its own and it is separately identifiable from other promises in the contract (ASC 606-10-25-19). Bundled arrangements frequently require disaggregation here — a common area of audit scrutiny.