ASC 606 Revenue Recognition for Engineering Firms: Practical Risks, Controls, and Common Pitfalls
Engineering firms often operate with long-duration contracts, evolving scopes, fixed-fee or time-and-material arrangements, reimbursable costs, subcontractor involvement, retainage provisions, and change orders. These features make revenue recognition one of the most judgmental areas in the financial statements and one of the most important areas for management, controllers, and auditors to monitor.
This article summarizes the ASC 606 considerations most relevant to engineering firms and translates them into practical risk-and-control actions. It is intended to support consistent project accounting, stronger work-in-process oversight, and better documentation of revenue judgments.
Why Revenue Recognition Is a High-Risk Area for Engineering Firms
Revenue recognition risk is elevated when project economics depend on estimates that change over the contract life. Common risk drivers include:
- Long-term projects with revenue recognized before final billing or collection.
- Fixed-fee contracts where margin depends on current estimates of total labor hours, subcontractor costs, and other project costs.
- Time-and-material arrangements where rates, reimbursable costs, caps, or not-to-exceed provisions must be monitored.
- Change orders and scope modifications that may be approved, pending, disputed, or partially priced.
- Claims and customer-caused delays where collectability and enforceable rights require careful evaluation.
- Retainage provisions that affect classification as a contract asset or receivable.
- Subcontractor or consultant costs that may require principal-versus-agent (gross vs net) analysis.
- Decentralized project management where project managers may update estimates inconsistently across offices or service lines.
The practical objective is not simply to calculate revenue mechanically. Management must determine what was promised, when control transfers, how progress is measured, what consideration is expected, and whether recognized revenue is constrained by uncertainty.
Start With the ASC 606 Framework
ASC 606 applies a five-step model:
- Identify the contract with the customer.
- Identify the performance obligations.
- Determine the transaction price.
- Allocate the transaction price to the performance obligations.
- Recognize revenue when, or as, performance obligations are satisfied.
For engineering firms, the most judgmental steps are typically identifying performance obligations, determining whether revenue is recognized over time or at a point in time, measuring progress, estimating variable consideration, and accounting for contract modifications.
Identifying Performance Obligations
Engineering contracts may include design, consulting, project management, inspection, environmental studies, construction administration, procurement support, and other services. The first practical question is whether the contract contains one performance obligation or multiple performance obligations.
A contract may contain a single combined performance obligation when the firm provides a significant integration service, for example, integrated engineering design services that produce one combined project deliverable. In other cases, promises may be distinct and accounted for separately if the customer can benefit from each service on its own or with readily available resources and the promises are separately identifiable.
Practical examples include:
Integrated design package for a single facility: Often one combined performance obligation if the services are highly interdependent.
Separate feasibility study followed by optional detailed design services: May be separate performance obligations or separate contracts, depending on enforceable rights and obligations.
Engineering services plus procurement of third-party equipment: Requires assessment of whether the firm controls the specified goods or services before transfer and whether it is principal or agent.
Stand-alone inspection services billed hourly: May qualify for over-time recognition and, in some cases, the invoice practical expedient (ASC 606-10-55-18)
Control focus: Contract review should document the promised goods and services, whether promises are distinct, and whether project accounting has been set up consistently with that conclusion.
Over-Time Revenue Recognition Is Not Automatic
Many engineering arrangements qualify for revenue recognition over time, but over-time recognition is appropriate only when at least one ASC 606 criteria is met. A performance obligation is satisfied over time when one of the following applies:
- The customer simultaneously receives and consumes the benefits as the entity performs.
- The customer controls the asset as it is created or enhanced.
- The asset has no alternative use to the entity, and the entity has an enforceable right to payment for performance completed to date.
If none of those criteria is met, revenue is recognized at the point in time when control transfers to the customer. Indicators of control transfer include the customer’s obligation to pay, transfer of legal title, physical possession, transfer of significant risks and rewards, and customer acceptance.
For many engineering service contracts, the “simultaneously receives and consumes” criterion may be met because another firm would not need to substantially reperform work completed to date. For customized deliverables, the “no alternative use and enforceable right to payment” criterion may be relevant. However, the conclusion should be documented and should not be assumed solely because the project is long-term or billed periodically.
Control focus: Revenue files should include a concise conclusion explaining which over-time criterion is met. If no criteria is met, the file should identify the point-in-time control transfer event.
Measuring Progress: Use a Method That Faithfully Depicts Performance
For performance obligations satisfied over time, ASC 606 requires a method that faithfully depicts progress toward complete satisfaction of the performance obligation. Output methods may include surveys of performance completed, appraisals, milestones, time elapsed, or units delivered. Input methods may include labor hours, costs incurred, resources consumed, time elapsed, or machine hours.
Engineering firms commonly use:
- Labor-hour input methods, especially when labor effort is the primary driver of performance.
- Cost-to-cost methods, particularly for broader engineering and construction-related arrangements.
- Milestone or deliverable-based methods, when milestones faithfully depict value transferred.
- Straight-line methods, only when effort or service transfer is even over the performance period.
The selected method should be applied consistently to similar performance obligations in similar circumstances. Progress should be updated at each reporting date. Cost-based methods should exclude inputs that do not depict transfer of control, such as significant inefficiencies or wasted resources not reflected in the contract price.
Billing Status Is Not a Stand-Alone Revenue Recognition Method
A common error is to use billing status as a proxy for revenue. Billing may differ from performance because of retainage, milestone billing, advance payments, delayed invoicing, or negotiated billing schedules. Therefore, billing status alone is not an acceptable revenue recognition method.
There is a limited exception: if the firm has a right to invoice the customer in an amount that corresponds directly with the value of performance completed to date, such as a fixed hourly rate contract for services provided, the firm may recognize revenue in the amount it has a right to invoice under the ASC 606 invoice practical expedient.
Control focus: Project accounting policies should distinguish between billing, earned revenue, contract assets, and contract liabilities. Any use of the invoice practical expedient should be documented by contract type.
Estimate Updates and WIP Oversight
Because many engineering contracts are recognized over time, revenue often depends on current estimates of total effort or cost. Outdated estimates can cause revenue and margin to be materially misstated.
Common issues include:
- Project managers do not update estimated hours to complete.
- Cost-to-complete estimates exclude known subcontractor or consultant cost overruns.
- Project budgets are revised operationally but not reflected in accounting records.
- Change orders are included in project forecasts without accounting review.
- Loss projects are not identified timely.
- WIP schedules do not reconcile to the general ledger.
Recommended controls include:
- Monthly project review meetings for significant contracts.
- Required estimate-to-complete updates by project managers.
- Accounting review of revenue and margin changes above defined thresholds.
- Reconciliation of project subledger, WIP reports, contract assets/liabilities, and the general ledger.
- Documentation of significant judgments, including progress measures, modifications, variable consideration, and loss indicators.
Change Orders and Contract Modifications
Change orders are common in engineering projects and may affect scope, price, schedule, or all three. ASC 606 requires specific analysis of contract modifications.
A contract modification may exist even when the parties dispute scope or price, or when scope has been approved but final pricing has not yet been determined. If the change creates or changes enforceable rights and obligations, the firm must evaluate the modification and estimate any related change in transaction price using the variable consideration guidance and constraint.
The accounting depends on the nature of the modification:
Adds distinct goods or services at a price that reflects stand-alone selling price: Account for as a separate contract.
Adds or changes goods/services that are distinct from those already transferred, but not at stand-alone selling price: Generally account for prospectively as a termination of the existing contract and creation of a new contract.
Adds or changes goods/services that are not distinct and are part of a single performance obligation: Generally account for through a cumulative catch-up adjustment.
ASC 606 provides specific guidance for modifications that are not accounted for as separate contracts, including prospective treatment when remaining goods or services are distinct and cumulative catch-up treatment when they are not distinct.
Control focus: Material change orders should not be recorded solely based on project manager expectations. Files should include evidence of approved scope, enforceable rights, estimated pricing, collectability, and the revenue recognition treatment.
Variable Consideration, Unapproved Pricing, and the Constraint
Engineering contracts may include variable consideration such as:
- Unpriced or partially priced change orders.
- Performance bonuses or incentives.
- Liquidated damages or penalties.
- Claims for customer-caused delays or design changes.
- Reimbursable costs subject to approval.
- Not-to-exceed limits or shared savings provisions.
ASC 606 requires variable consideration to be estimated using either the expected value method or the most likely amount method, depending on which method better predicts the amount of consideration to which the entity expects to be entitled.
However, estimated variable consideration is included in the transaction price only to the extent it is probable that a significant reversal of cumulative revenue recognized will not occur when the uncertainty is resolved. This is commonly referred to as the variable consideration constraint. For engineering firms, the constraint is especially important for unapproved change orders, disputed pricing, claims, and incentives with uncertain outcomes.
Practical Documentation for Variable Consideration
For significant variable consideration, the revenue file should document:
- The nature of the variable amount.
- The basis for enforceable entitlement.
- The estimation method used.
- Evidence supporting the estimate.
- Factors affecting the constraint, including history with the customer, negotiation status, contract terms, and susceptibility to factors outside the firm’s influence.
- Updates to the estimate each reporting period.
Control focus: Establish approval thresholds requiring accounting leadership review before recognizing material unapproved change orders, claims, or incentive fees.
Claims Require Enforceability and Constraint Analysis
Claims are amounts above the agreed contract price that a firm seeks to collect from a customer or another party. They may arise from customer-caused delays, errors in specifications, design changes, disputed or unapproved change orders, contract terminations, or other unanticipated costs.
Claims should be evaluated to determine whether they create enforceable rights and obligations. If enforceable, they are accounted for under the variable consideration guidance, including estimation and constraint.
Evidence that may support recognition includes written customer approval of scope, contract language supporting entitlement, separately documented costs, and favorable experience resolving similar claims.
Control focus: Claims should be reviewed by accounting and legal or contract administration personnel before revenue is recognized.
Principal-Versus-Agent Considerations
Engineering firms often engage subconsultants, specialty engineers, surveyors, laboratories, or other third parties. The presence of a subcontractor does not automatically mean the firm is an agent. The firm must determine whether it controls the specified good or service before it is transferred to the customer.
If the firm is the principal, it recognizes revenue gross for the consideration to which it expects to be entitled. If the firm is an agent, it recognizes revenue net, generally for its fee or commission. ASC 606 requires this assessment at the level of each specified good or service; an entity may be principal for some goods or services and agent for others in the same contract.
Indicators that the firm may be principal include responsibility for fulfillment, discretion in selecting and directing subcontractors, integration of subcontractor services into the combined deliverable, inventory or cost risk, and pricing discretion. Indicators that the firm may be an agent include arranging for another party to provide services without controlling those services before transfer.
Control focus: Contracts with significant subcontractor or reimbursable cost components should include a documented gross-versus-net conclusion.
Contract Costs Under ASC 340-40
Engineering firms often incur proposal, mobilization, design setup, and contract acquisition costs. ASC 340-40 provides guidance on which costs may be capitalized.
Costs to Obtain a Contract
Incremental costs of obtaining a contract should be capitalized if the costs are expected to be recovered. Incremental costs are costs the firm would not have incurred if the contract had not been obtained, such as certain sales commissions. Costs that would have been incurred regardless of whether the contract was obtained, such as many proposal salaries, are generally expensed unless they are explicitly chargeable to the customer. A practical expedient allows entities to expense incremental costs when the amortization period would be one year or less.
Costs to Fulfill a Contract
Certain fulfillment costs may be capitalized if they relate directly to a specific contract or anticipated contract, generate or enhance resources that will be used to satisfy performance obligations, and are expected to be recovered. Capitalized contract costs are amortized on a systematic basis consistent with the transfer of the related goods or services and are tested for impairment.
Control focus: Policies should distinguish between bid and proposal costs, recoverable mobilization costs, commissions, fulfillment costs, and ordinary project expenses.
Retainage, Contract Assets, and Receivables
Retainage provisions are common in engineering and construction-related contracts. Classification depends on whether the firm’s right to consideration is conditional.
A receivable exists when the right to consideration is unconditional and only the passage of time is required before payment is due.
A contract asset exists when the firm has transferred goods or services but the right to consideration is conditional on something other than the passage of time.
Retainage subject to completion, milestones, customer acceptance, fulfillment guarantees, or other future performance conditions is generally a contract asset until the condition is satisfied. Retainage that is unconditional except for the passage of time is generally a receivable. Retainage should be assessed at the contract level; some retainage balances may be receivables while others are contract assets.
Control focus: WIP and accounts receivable reports should clearly distinguish billed receivables, contract assets, contract liabilities, and retainage.
Uninstalled Materials and Significant Procured Items
Some engineering or engineering-procurement contracts involve significant materials or equipment procured before installation or integration. If a cost-to-cost method is used, including large uninstalled materials in the progress measure may accelerate revenue in a way that does not faithfully depict performance.
ASC 606 guidance for uninstalled materials is especially relevant when the customer obtains control of goods before the firm performs the related integration services. In those circumstances, the firm may need to adjust the cost-to-cost measure to avoid recognizing profit before installation or integration.
Control focus: Project reviews should identify large equipment, materials, or pass-through procurement items and evaluate whether cost-to-cost revenue requires adjustment.
Disclosures Under ASC 606
ASC 606 disclosures are intended to help financial statement users understand the nature, amount, timing, and uncertainty of revenue and cash flows from customer contracts. Required disclosures may include information about disaggregated revenue, contract balances, performance obligations, remaining performance obligations, significant judgments, and assets recognized from costs to obtain or fulfill contracts.
For nonpublic entities, some disclosure requirements are reduced or optional, but disclosures still generally need to address:
- Revenue disaggregation sufficient to explain how economic factors affect revenue.
- Opening and closing balances of receivables, contract assets, and contract liabilities.
- The nature of goods and services promised.
- Significant payment terms.
- When performance obligations are typically satisfied.
- Revenue recognized from performance obligations satisfied or partially satisfied in prior periods.
- Significant judgments used in applying ASC 606.
Control focus: Disclosure preparation should be integrated with the revenue close process so contract balances, significant judgments, and revenue rollforwards are complete and consistent with the general ledger.
Practical Risk-and-Control Checklist
Performance obligations: Contracts may be set up as a single project without first evaluating whether the agreement includes multiple distinct promises. A stronger control is to require a documented performance-obligation assessment during setup for every significant new contract.
Over-time recognition: Revenue may be recognized over time without documenting which ASC 606-10-25-27 criterion supports that treatment. A stronger control is to add the applicable over-time criterion and supporting rationale to the contract review template.
Billing versus revenue: Invoices or billing milestones may be treated as earned revenue even when billing does not reflect the value transferred to date. A stronger control is to reconcile billed amounts to earned revenue and use the invoice practical expedient only when ASC 606-10-55-18 applies.
Progress estimates: Percent-complete calculations may rely on outdated labor, cost, or effort estimates. A stronger control is to require project managers to update estimates to complete monthly, with documented review and approval.
Cost-to-cost inputs: Inefficiencies, wasted costs, or significant uninstalled materials may distort the measure of progress and accelerate revenue. A stronger control is to review unusual costs and major procured items before each revenue close and adjust the progress measure when necessary.
Change orders: Unapproved changes may be included in revenue before enforceability, pricing, and collectability are adequately supported. A stronger control is to require accounting review of enforceable rights, the pricing estimate, and the variable consideration constraint before recognition.
Claims: Claims may be recorded based on an expectation of recovery rather than evidence of an enforceable right to payment. A stronger control is to require legal or contract-administration review, support for entitlement, and documented constraint analysis before recognizing revenue.
Variable consideration: Bonuses, incentives, penalties, and other variable amounts may not be reassessed as project conditions change. A stronger control is to update the estimate and evaluate the constraint at every reporting period, retaining evidence that supports the conclusion.
Subcontractors: Revenue may be reported gross without determining whether the firm controls the third-party service before it is transferred to the customer. A stronger control is to document the principal-versus-agent assessment for significant subcontractor and other third-party services.
Contract costs: Bid, proposal, or other contract-related costs may be capitalized even when they do not meet ASC 340-40 criteria. A stronger control is to maintain a clear policy for costs to obtain and fulfill contracts, and review capitalized balances at least quarterly.
Retainage: Retainage may be classified entirely as a receivable without evaluating whether the right to payment remains conditional. A stronger control is to assess each retainage balance at the contract level and classify it as a receivable or contract asset based on the underlying payment conditions.
Disclosures: Contract balances, revenue rollforwards, and significant judgments may be incomplete or inconsistent with underlying accounting records. A stronger control is to tie disclosure support to WIP, accounts receivable, contract asset and liability, and revenue reports as part of the close process.
Closing Thoughts
For engineering firms, ASC 606 compliance depends on disciplined project accounting and timely communication between project managers, accounting, contract administration, and executive leadership. The most effective revenue controls are not limited to the year-end audit. They operate throughout the project lifecycle, from contract review and project setup to monthly WIP updates, change order evaluation, billing, close, and disclosure preparation.
A strong ASC 606 process should answer four practical questions for every significant project:
- What did we promise the customer?
- When does control transfer?
- How do we measure progress and update estimates?
- What uncertainties could cause revenue to reverse?
When those questions are answered consistently and supported by documentation, engineering firms are better positioned to produce reliable financial statements, identify margin issues early, and withstand audit scrutiny.