How do you measure progress and update estimated total contract costs under the cost-to-cost input method when actual costs fluctuate significantly?

- Step 2: Identify performance obligations — A performance obligation is a promise to transfer a distinct good or service to the customer (ASC 606-10-25-14). A good or service is distinct if the customer can benefit from it on its own or together with other readily available resources, and the entity's promise to transfer it is separately identifiable from other promises in the contract (ASC 606-10-25-19). If two promises are highly interdependent or interrelated, they are combined into a single performance obligation. Watch for series of distinct goods or services that are substantially the same and have the same pattern of transfer — these may be treated as one performance obligation under ASC 606-10-25-14. - 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 promised goods or services (ASC 606-10-32-2). This includes fixed amounts plus any variable consideration, estimated using either the expected value method or the most likely amount method (ASC 606-10-32-6). Variable consideration is included only to the extent it is probable that a significant revenue reversal will not occur when the uncertainty resolves (ASC 606-10-32-11). Adjust for significant financing components, non-cash consideration, and consideration payable to the customer where applicable. - Step 4: Allocate the transaction price — The transaction price is allocated to each performance obligation based on relative standalone selling prices (ASC 606-10-25-4 requires that the allocation reflect what the entity would charge for each promised good or service independently). If standalone selling prices are not directly observable, they must be estimated using approaches such as adjusted market assessment, expected cost plus margin, or residual methods under limited circumstances. Discounts and variable consideration are generally allocated proportionally unless specific allocation criteria are met.

When can an entity recognize revenue over time, and what is the difference between the right-to-invoice practical expedient and recognizing revenue based on actual performance?

- Step 5: Recognize revenue — Revenue is recognized when (or as) each performance obligation is satisfied by transferring control of the promised good or service to the customer (ASC 606-10-25-20). Transfer can occur either at a point in time or over time. An entity recognizes revenue over time if one of three criteria is met — including whether the entity's performance creates or enhances an asset that the customer controls as it is created (ASC 606-10-25-27). If none of the over-time criteria are met, revenue is recognized at the point in time when control transfers. - Combining or splitting contracts incorrectly — Contracts entered into at or near the same time with the same customer may need to be combined and treated as a single arrangement under ASC 606-10-25-9. - Overlooking variable consideration — Rebates, discounts, bonuses, and penalty clauses all constitute variable consideration and must be estimated and constrained before inclusion in the transaction price (ASC 606-10-32-7). - Misidentifying distinct performance obligations — Entities frequently either over-separate bundled promises or fail to separate genuinely distinct ones, leading to incorrect timing of revenue recognition. - Applying the wrong recognition pattern — Defaulting to point-in-time recognition without evaluating whether over-time criteria are met, or vice versa, is a persistent error in practice. - Ignoring the portfolio practical expedient — ASC 606-10-10-4 permits a portfolio approach when the financial statement effect would not differ materially from a contract-by-contract analysis, but entities must apply it consistently. - ASC 606-10-25-1 — Sets out the five criteria that must be met for a contract with a customer to exist for revenue recognition purposes. - ASC 606-10-25-14 — Defines a performance obligation and introduces the concept of a series of distinct goods or services treated as a single obligation. - ASC 606-10-25-19 — Establishes the two-part test for determining whether a promised good or service is distinct (capable of being distinct and separately identifiable). - ASC 606-10-32-2 — Defines the transaction price and specifies what amounts are excluded from that measurement. - ASC 606-10-32-11 — Describes the constraint on variable consideration — inclusion only when it is probable no significant revenue reversal will occur. - ASC 606-10-25-20 — States the core recognition principle: revenue is recognized when or as a performance obligation is satisfied by transferring control to the customer.

ASC 606 Revenue Recognition — 5-Step Model

ASC 606 Revenue from Contracts — Core Rule

Revenue is recognized when (or as) an entity transfers promised goods or services to a customer in an amount that reflects the consideration to which the entity expects to be entitled (ASC 606-10-25-1(e)). This principle governs all contracts with customers unless a specific scope exclusion applies (ASC 606-10-15-2). The five-step model is the structured framework for applying this principle consistently across industries and transaction types.

How ASC 606 Revenue from Contracts Works

The five-step model applies to all contracts with customers within scope. Here is how each step functions in practice:

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

ASC 606 Revenue from Contracts — Core Rule

How ASC 606 Revenue from Contracts Works