This article is written for U.S. finance leaders, controllers, technical accountants, and accounting teams applying ASC 606 across service, construction, manufacturing, software, and professional-services contracts.
Getting this timing wrong isn't a minor technicality. It affects financial statements, deferred revenue balances, audit support, management reporting, and compliance. Many teams default to recognizing revenue when they invoice or collect cash. That's rarely the right answer under ASC 606.
This article covers the three criteria for over-time recognition, how to measure progress once you qualify, where the model typically applies, and when point-in-time recognition is the correct conclusion instead.
Key Takeaways
- Over-time recognition applies when at least one of three ASC 606 criteria is met; otherwise, revenue is recognized at a point in time
- Evaluate each performance obligation on its own, not based on invoice dates or billing schedules
- Output methods measure value delivered; input methods measure resources consumed
- Your chosen progress method must faithfully depict performance and rest on reliable evidence
- Document every judgment call, estimate, and contract modification to withstand audit scrutiny
What Are Performance Obligations and Why Does Over-Time Recognition Matter?
A performance obligation is a promise to transfer a distinct good or service to a customer, or a series of substantially similar goods or services transferred in the same pattern. Before you can decide when to recognize revenue, you need to know what you've actually promised.
The "Distinct" Test
ASC 606 requires two conditions for a promise to count as distinct:
- Capable of being distinct – the customer can benefit from the good or service on its own, or with other resources readily available to them
- Separately identifiable – the promise is distinguishable from other promises in the contract, not so bundled together that it loses its own identity
Both conditions must be satisfied. A good or service that's theoretically useful on its own but heavily integrated with other contract elements still gets combined into a single obligation.
Revenue Follows Control, Not Cash
This is where many teams go wrong. An invoice, a deposit, or a cash receipt tells you nothing about whether control has transferred. A customer can prepay for a year of service and you still recognize revenue as you perform, not when the check clears.
Over-time recognition sits at Step 5 of the ASC 606 five-step model. By that point you have already identified the contract and obligations, determined the transaction price, and allocated it. Get any earlier step wrong, and your timing conclusion will be wrong too, no matter how carefully you measure progress.
Why this matters for your books:
- Misclassifying obligations distorts deferred revenue and contract asset/liability balances
- Auditors will test your conclusion against contract language, not your billing system
- Period-over-period comparisons become unreliable if the pattern shifts without a real change in facts
Point-in-time recognition, by contrast, records revenue at a single event such as delivery, acceptance, or title transfer. That treatment applies when control does not transfer continuously as work progresses.
How Does Over-Time Revenue Recognition Work Under ASC 606?
A performance obligation qualifies for over-time recognition when any one of three criteria is met. You don't need all three.
Criterion A: Simultaneous receipt and consumption. The customer receives and consumes the benefit as you perform. Recurring services are the classic example: monthly IT support or managed services.
The test here: would another provider need to substantially redo the work completed so far to finish the job? If not, this criterion is likely satisfied.
Criterion B: Customer controls the asset as it's built. Your performance creates or enhances an asset the customer controls throughout, not just at completion. This shows up often in construction on a customer's land or work performed on an asset the customer already controls legally or practically.
Criterion C: No alternative use, plus enforceable payment right. This one has two parts, and both must be true:
- The asset you're creating has no alternative use to you - contractual or practical restrictions prevent redirecting it to another customer
- You have an enforceable right to payment for performance completed to date, not just cost reimbursement or a cancellation penalty
A Practical Decision Flow
Work through each obligation using this sequence:
- Identify the promised good or service, including implied promises from customary practices
- Test the three criteria against the contract terms and facts
- Document your conclusion, including which criterion applies and why
- Select a progress measure if over-time recognition applies
- Reassess whenever facts or contract terms change materially
That enforceable-right-to-payment analysis under Criterion C deserves extra scrutiny. Compensation must reflect the selling price of work completed, typically cost plus a reasonable margin. A clause that only reimburses costs, without margin, generally fails this test.
Key Factors, Measurement Methods, and Applications
Once an obligation qualifies for over-time recognition, you need a method that depicts how control transfers. FASB's ASC 606 guidance requires using one method per obligation, applied consistently to similar obligations in similar circumstances, and remeasured every reporting period.
Output Methods
Output methods measure value directly transferred to the customer:
- Units produced or delivered
- Milestones reached
- Surveys of work completed
- Appraisals of results achieved
- Time elapsed, when that genuinely reflects value transfer
These work well when you have reliable, objective evidence. The catch: a units-delivered measure can understate progress if it ignores controlled work-in-process the customer hasn't technically received yet.
Input Methods
Input methods measure resources consumed relative to total expected inputs: labor hours, machine hours, costs incurred, or materials used.
Watch for these complications, as outlined in PwC's measures of progress guide:
- Wasted materials or abnormal inefficiencies that don't reflect contract pricing generally need to be excluded from the calculation
- Uninstalled materials may require different treatment. Revenue equal to cost (not accelerated margin) fits only when all four conditions hold:
- The good isn't distinct
- The customer controls it well before related services
- Its cost is significant relative to total obligation costs
- You procured it from a third party without substantial design involvement
Where This Shows Up
Over-time recognition commonly applies to:
- Recurring and managed services
- Long-term construction and engineering contracts
- Customer-specific manufacturing
- Research and development services
- Professional-services engagements
Industry labels don't decide the accounting conclusion. A "subscription" or a "construction contract" still has to pass the three-criteria test on its own facts.
Fluor's 10-K disclosure illustrates one real-world application: the engineering and construction firm uses cost-to-cost measurement because it "best depicts how control transfers to our clients."
Its ratio is costs incurred to date divided by total estimated contract cost. Estimate revisions flow through as cumulative catch-up adjustments, sometimes reversing prior revenue. This is one company's method, not a universal rule.
Documentation Checklist
Keep a record covering:
- Contract and performance-obligation analysis
- The qualifying over-time criterion and supporting facts
- Alternative-use and payment-right conclusions
- Progress method selected and key estimates used
- Approvals and periodic reassessment dates
Your job-cost systems, timekeeping, acceptance criteria, and close controls all need to actually support the method you've chosen. A spreadsheet conclusion that doesn't match your operational data won't survive an audit.
Common Issues and When Over-Time Recognition May Not Apply
A long contract term doesn't make it an over-time arrangement. Neither does a subscription model, installment billing, or an upfront deposit. None of these are criteria under ASC 606. The only question is whether one of the three control-based tests is met.
Frequent judgment traps:
- Treating a cancellation fee as an enforceable right to payment, when it may only cover costs or a penalty, not performance value
- Overlooking practical restrictions on redirecting an asset, even without a contractual non-compete clause
- Using cost incurred as the progress measure without checking whether costs actually depict performance
- Switching methods between periods to accelerate revenue recognition without a genuine change in facts
When Point-in-Time Recognition Is Correct
Point-in-time recognition applies when none of the three over-time criteria is met. Common examples:
- Delivery of a standard, off-the-shelf product where the customer obtains control at the delivery or acceptance event
- Arrangements where the asset could realistically be redirected to another customer
- One-time services completed and accepted on a single delivery date, with no continuous transfer of control
Contract modifications add another layer of judgment. Scope changes, revised cost estimates, customer acceptance clauses, and variable consideration such as rebates, bonuses, or milestone payments can all force a reassessment.
Whether a modification gets prospective treatment or cumulative catch-up depends on whether the remaining performance is distinct from what has already been delivered.
When the arrangement involves significant judgment, material estimates, unusual payment terms, customer-specific assets, or inconsistent contract practices, it's worth escalating to technical accounting advisers, your audit committee, or your auditors before you lock in a conclusion.
Judgment-heavy arrangements benefit from an outside review before the conclusion is locked in. Stratum Advisory Partners works alongside finance teams on technical accounting questions like these, analyzing complex revenue arrangements and building supportable documentation.
For companies without an interim CAO or controller to own the work day to day, that support can also take the form of hands-on interim leadership.
Conclusion
Over-time revenue recognition comes down to how and when control transfers, not contract length, billing frequency, or cash collection timing. Test each obligation against the three criteria, pick a progress method that faithfully reflects performance, and back it with evidence your systems can actually produce.
Document your judgments as you go. Monitor contract modifications and estimate changes closely, since both can shift your conclusion mid-contract. And when the arrangement gets complex or material, bring in technical accounting support before the auditors ask the hard questions.
Frequently Asked Questions
What is a performance obligation in revenue recognition?
A performance obligation is a promise to transfer a distinct good or service to a customer. Under ASC 606, revenue is recognized when, or as, that obligation is satisfied.
How do you identify performance obligations?
Review the contract and related communications for explicit and implicit promises, then apply the distinctness test. Combine promises that are highly integrated or interdependent rather than treating them as separate obligations.
What are the three criteria for recognizing revenue over time?
Revenue is recognized over time when any one of these is met:
- The customer simultaneously receives and consumes benefits as you perform
- Your work creates or enhances an asset the customer controls as it is built
- Your work creates an asset with no alternative use and an enforceable right to payment for work completed
How is progress measured for performance obligations satisfied over time?
Output methods measure value transferred directly, like milestones or units delivered. Input methods measure resources consumed, such as labor hours or costs incurred, relative to total expected inputs.
When should revenue be recognized at a point in time instead of over time?
When none of the three over-time criteria is met and control transfers at a single, identifiable event, such as delivery of a standard product the customer could use immediately.
