ERP5 min readNetray Engineering Team

Revenue Recognition for Manufacturers Under ASC 606

ASC 606 requires manufacturers to recognize revenue when control of a good or service transfers to the customer, using a five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate that price to the obligations, and recognize revenue as each obligation is satisfied. For most standard product shipments this still means point-in-time recognition at delivery. But for custom, engineered, and long-cycle work, ASC 606 pushed a meaningful share of manufacturing revenue to over-time recognition, which changes billing, ERP configuration, and the shape of the balance sheet.

Over-Time vs Point-in-Time Recognition for Manufactured Goods

The critical test for manufacturers is in ASC 606-10-25-27. Revenue is recognized over time if the asset being created has no alternative use to the seller and the seller has an enforceable right to payment for performance completed to date, including a reasonable profit margin. Custom tooling, build-to-print defense assemblies, and configured capital equipment frequently meet both conditions, especially where the contract includes a termination-for-convenience clause that pays costs plus profit. Standard catalog products almost never do, because they can be redirected to another customer. The conclusion is contract-specific and driven by the actual legal terms, so the same physical part can be over-time revenue for one customer and point-in-time for another.

Measuring Progress With the Cost-to-Cost Method

When over-time recognition applies, progress must be measured with an input or output method applied consistently. Manufacturers overwhelmingly use the cost-to-cost input method: costs incurred to date divided by total estimated costs at completion, applied to the transaction price. This requires an estimate at completion that is genuinely maintained, because a stale EAC produces revenue that reverses later as a cumulative catch-up adjustment. Uninstalled materials receive special treatment; significant materials procured but not yet installed are generally recognized at zero margin so buying steel early does not manufacture profit.

  • Maintain estimate-at-completion by contract and update it at least monthly, not just at quarter end
  • Recognize significant uninstalled materials at zero margin rather than letting procurement drive revenue
  • Book cumulative catch-up adjustments in the period the estimate changes, and document the reason
  • Reconcile job cost detail in ERP to the costs incurred figure used in the percentage calculation

Variable Consideration, Rebates, and Contract Modifications

Transaction price is rarely the number on the purchase order. Volume rebates, early payment discounts, price concessions, liquidated damages, and performance incentives are variable consideration that must be estimated using either the expected value or the most likely amount method, then constrained so a significant revenue reversal is not probable. Manufacturers that accrue rebates only when invoiced by the customer are almost certainly non-compliant. Contract modifications need their own analysis: a change order adding distinct goods at standalone selling price is a separate contract, while a scope change on an existing obligation is typically accounted for as a cumulative catch-up on the original contract. Engineering change orders on long-cycle programs make this a recurring, not one-time, judgment.

Configuring ASC 606 in Manufacturing ERP

Standard ERP order-to-cash flows recognize revenue at shipment or invoice, so over-time recognition requires deliberate configuration. The common pattern is a project or contract structure that carries the performance obligation, an EAC maintained against it, and a periodic revenue recognition run that posts the calculated revenue along with a contract asset (unbilled receivable) or contract liability (deferred revenue) depending on whether recognition leads or lags billing. Infor LN supports this through its Project package with cost and revenue recognition methods per project. SyteLine users commonly drive it from project or job structures with a supporting schedule. The critical control is reconciling recognized revenue and the contract asset balance back to job cost detail every month.

  • Model each performance obligation as a distinct project, contract line, or job so costs accumulate separately
  • Automate the contract asset and contract liability postings rather than maintaining them in a spreadsheet
  • Reconcile unbilled receivables to the revenue recognition calculation monthly, with aging over 90 days reviewed
  • Retain the ASC 606 assessment memo per contract type so auditors see the over-time conclusion and its basis

How Netray Supports Revenue Recognition Compliance

Netray builds revenue recognition agents that read contract terms, job cost detail, and billing status directly from your ERP, then calculate percentage of completion, propose the recognition entry, and reconcile the resulting contract asset and liability balances. The agents flag contracts whose estimate at completion has not been updated in more than 45 days, detect EAC movements large enough to trigger a material cumulative catch-up before quarter close, and maintain a per-contract audit file with the inputs used. For manufacturers running dozens of long-cycle programs, this converts a multi-week quarterly scramble into a monthly review of exceptions, and gives auditors a consistent evidence package.

Frequently Asked Questions

When can a manufacturer recognize revenue over time under ASC 606?

Over-time recognition applies when the asset being produced has no alternative use to the manufacturer and there is an enforceable right to payment for work completed to date, including a reasonable profit. Custom tooling, build-to-print defense assemblies, and configured capital equipment often qualify, particularly when the contract includes termination-for-convenience terms paying cost plus profit. Standard catalog products that can be sold to another customer do not qualify and remain point-in-time at delivery.

What is the cost-to-cost method for percentage of completion?

Cost-to-cost measures progress as costs incurred to date divided by total estimated costs at completion, and applies that percentage to the contract transaction price to determine revenue recognized. It is the most common input method for manufacturers because job cost data already exists in ERP. Its accuracy depends entirely on the estimate at completion being kept current, since a stale estimate produces revenue that reverses as a cumulative catch-up adjustment later.

What is a contract asset versus unbilled receivable?

A contract asset arises when a company has recognized revenue by satisfying a performance obligation but its right to payment is still conditional on something other than the passage of time, such as completing a further milestone. An unbilled receivable exists when the right to payment is unconditional but the invoice has not yet been issued. Both appear when over-time recognition runs ahead of the billing schedule, and both should be reconciled to job cost detail monthly.

Key Takeaways

  • 1Over-Time vs Point-in-Time Recognition for Manufactured Goods: The critical test for manufacturers is in ASC 606-10-25-27. Revenue is recognized over time if the asset being created has no alternative use to the seller and the seller has an enforceable right to payment for performance completed to date, including a reasonable profit margin.
  • 2Measuring Progress With the Cost-to-Cost Method: When over-time recognition applies, progress must be measured with an input or output method applied consistently. Manufacturers overwhelmingly use the cost-to-cost input method: costs incurred to date divided by total estimated costs at completion, applied to the transaction price.
  • 3Variable Consideration, Rebates, and Contract Modifications: Transaction price is rarely the number on the purchase order. Volume rebates, early payment discounts, price concessions, liquidated damages, and performance incentives are variable consideration that must be estimated using either the expected value or the most likely amount method, then constrained so a significant revenue reversal is not probable.

Talk to Netray about automating percentage-of-completion revenue and contract asset reconciliation directly from your ERP job cost data.