When is revenue recognised over time versus at a point in time under ASC 606?

Core rule Under ASC 606, revenue is recognized over time only if the arrangement meets at least one of three specified criteria; otherwise, control of the promised good or service transfers at a single point in time and revenue is recognized then. How it works The over-time vs. point-in-time determination is made at the performance obligation level, not the contract level. This matters because a single contract can contain obligations recognized under different patterns. - Three over-time criteria (ASC 606-10-25-27): Revenue is recognized over time if (1) the customer simultaneously receives and consumes the benefits as the entity performs (e.g., routine payroll processing), (2) the entity's performance creates or enhances an asset the customer controls as it is created (e.g., construction on customer-owned land), or (3) the entity's performance does not create an asset with an alternative use to the entity and the entity has an enforceable right to payment for performance completed to date. Meeting any one criterion is sufficient. - Point-in-time default (ASC 606-10-25-30): If none of the three criteria are met, the entity recognizes revenue at the point when control transfers. Indicators of control transfer include: transfer of physical possession, transfer of legal title, transfer of ri

How does the 'no alternative use' test apply to a contract manufacturer producing semi-custom components that share 80% common parts with standard inventory?

sks and rewards, customer acceptance, and the customer having a present obligation to pay (ASC 606-10-25-30(a)–(e)). - Measuring progress for over-time obligations (ASC 606-10-25-31 through 25-37): An entity must select a single method — either an output method (e.g., milestones, units delivered) or an input method (e.g., costs incurred, labor hours) — that faithfully depicts transfer of control. The selected method must be applied consistently to similar performance obligations. - "Alternative use" and "enforceable right to payment" (ASC 606-10-25-28 through 25-29): Under criterion (3), both conditions must be met simultaneously. An asset has no alternative use if contractual or practical limitations prevent the entity from redirecting it to another customer. The right to payment must cover costs incurred plus a reasonable margin — a termination-for-convenience clause paying only costs with no profit component may fail this prong. - Contract-specific reassessment: The over-time vs. point-in-time conclusion is reassessed only when facts and circumstances indicate a significant change. It is not updated simply because time has passed (ASC 606-10-25-27, overall framework). - Disclosure requirements (ASC 606-10-50-5): Entities must disaggregate revenue in a way that depicts how economic facto

If a construction contract initially qualifies for over-time recognition but the customer later loses control of the underlying asset, when and how should the entity reassess its revenue pattern?

rs affect the nature, amount, timing, and uncertainty of revenue — commonly requiring separate disclosure of over-time vs. point-in-time revenue streams. Practical example Scenario: A software development firm signs a $500,000 fixed-price contract to build a custom application on the customer's proprietary cloud infrastructure. The contract includes an enforceable right to payment for work completed, and the asset has no alternative use (cannot be redeployed). Criterion (3) is met → revenue recognized over time using the cost-to-cost input method. At month-end, $150,000 of the estimated $400,000 total costs have been incurred → 37.5% complete → $187,500 revenue recognized ($500,000 × 37.5%). Journal entry at month-end: | Account | Dr | Cr | |---|---|---| | Accounts Receivable / Contract Asset | $187,500 | | | Revenue | | $187,500 | | Cost of Revenue | $150,000 | | | Accrued Project Costs / Cash | | $150,000 | If the same firm sold an off-the-shelf software license with no ongoing obligations, control transfers at delivery → point in time → full $X recognized on delivery date only. Common pitfalls - Misapplying criterion (1) to subscription SaaS: A multi-year SaaS arrangement may look like criterion (1) (customer uses the service simultaneously), but if the contract delivers a functional IP

Under the cost-to-cost input method, how should an entity treat uninstalled materials or wasted costs that don't reflect progress toward satisfying the performance obligation?

license rather than a service, point-in-time recognition at the license grant date may be required instead. Confusing service delivery with IP licensing is a recurring audit finding. - Assuming a right to payment equals over-time recognition: Practitioners often stop analysis at "we have a termination clause." The right to payment must cover a reasonable profit margin, not merely cost recovery. Failing to document the margin component is an SEC comment letter trigger. - Ignoring the alternative-use test for manufactured goods: Custom manufacturers frequently qualify for over-time recognition under criterion (3), but only if they can demonstrate that contractual and practical constraints prevent redirecting the WIP. Relying solely on a "custom" label without substantive analysis is an audit trap. Key paragraphs to know - ASC 606-10-25-27 — The three criteria for over-time recognition (the primary decision gate). - ASC 606-10-25-28 through 25-29 — "No alternative use" and "enforceable right to payment" definitions under criterion (3). - ASC 606-10-25-30 — Point-in-time default and the five indicators of control transfer. - ASC 606-10-25-31 through 25-37 — Selecting and applying output vs. input methods to measure progress. - ASC 606-10-50-5 — Disaggregation of revenue disclosure requirement

ASC 606 Over Time vs Point in Time

ASC 606 Over — Core Rule

Under ASC 606, revenue is recognized over time only if the arrangement meets at least one of three specified criteria; otherwise, control of the promised good or service transfers at a single point in time and revenue is recognized then.

How ASC 606 Over Works

The over-time vs. point-in-time determination is made at the performance obligation level, not the contract level. This matters because a single contract can contain obligations recognized under different patterns.