Revenue recognition for engineered-to-order equipment with milestone billing

Treating milestone invoices as a proxy for revenue recognition, when the over-time criteria are not actually met, can materially accelerate or defer revenue relative to the true pattern of control transfer - a direct misstatement risk in an area auditors scrutinize closely for large individual contracts. Because engineered-to-order contracts are often large relative to total revenue, getting the over-time versus point-in-time call wrong (or missing a contract asset) can materially swing reported revenue, margin and working capital in a single period, with knock-on effects on debt covenants and bid/tender track-record metrics.

Does the equipment being engineered and built have no alternative use to the manufacturer because it is customized to the specific customer's requirements? Does the manufacturer have an enforceable right to payment for performance completed to date, including a reasonable profit margin, if the customer terminates for convenience - verified as a legal as well as accounting judgment? Does milestone billing actually coincide with progress on the build, or does it precede or lag the true percentage of completion used for revenue recognition?

1. Read the contract to determine whether the equipment being engineered and built is customized to the specific customer's requirements such that it has no alternative use to the manufacturer (i.e., it cannot readily be redirected to another customer without significant rework or loss).
2. If there is no alternative use, assess whether the manufacturer has an enforceable right to payment for performance completed to date (including a reasonable profit margin) if the customer were to terminate the contract for convenience - this is a legal as well as accounting judgment.
3. If both conditions are met (or another over-time criterion, such as the customer controlling the asset as it is created, applies), recognize revenue over time using an appropriate measure of progress (e.g., cost-to-cost input method); if neither is met, revenue is recognized at the single point in time when control transfers (typically delivery, installation or customer acceptance), regardless of the billing schedule.
4. Treat the milestone billing schedule purely as an invoicing and cash-collection mechanism - do NOT default to recognizing revenue as milestones are billed; instead compare cumulative revenue recognized (per the progress assessment) to cumulative amounts billed.
5. Where cumulative revenue recognized exceeds cumulative billings, recognize a contract asset (unbilled revenue); where cumulative billings exceed cumulative revenue recognized, recognize a contract liability (billing in advance of performance).
6. Reassess the over-time versus point-in-time conclusion, and the progress measure, at each reporting date as facts change (e.g., late-added customization clauses, contract modifications, or a renegotiated cancellation/payment clause).

Measurement basis: if over-time criteria are met, revenue equals the transaction price multiplied by the progress measure (e.g., costs incurred to date divided by total estimated costs), reassessed each period for changes in estimated total cost and scope; if point-in-time, revenue is the full transaction price recognized only on transfer of control. Included: costs directly related to contract performance in the progress calculation (materials, labor, allocated overhead actually consumed on the specific contract); variable consideration such as scope-change orders once they meet the recognition/constraint criteria. Excluded from progress-to-date costs: costs of abnormal waste, uninstalled materials not yet incorporated into the asset (measured separately if the output method would be distorted), and general/unallocated overhead. Re-measurement triggers: any change in the total estimated contract cost or the total transaction price (contract modifications, change orders, scope adjustments); reassessment of the over-time versus point-in-time conclusion if contract terms are amended (e.g., cancellation clause renegotiated); and each reporting date's true-up of cumulative billings against cumulative revenue to update the contract asset/liability balance.

Disclosure of the method used to measure progress toward completion (e.g., cost-to-cost input method) and why it faithfully depicts transfer of control; contract assets and contract liabilities presented separately (or clearly labeled) on the balance sheet, with a reconciliation of opening to closing balances; disaggregation of revenue between over-time and point-in-time recognized contracts if both exist within engineered-to-order operations; significant judgments made in concluding whether the over-time criteria (no alternative use plus enforceable right to payment) are met; remaining performance obligations / backlog information for significant long-term engineered-to-order contracts, where required.

• Recognizing revenue simply as milestones are invoiced (a '
• percentage of billing'
• shortcut) rather than separately assessing the over-time/point-in-time criteria and an independent progress measure
• failing to recognize a contract asset when costs incurred and margin earned exceed amounts billed to date, understating both revenue and assets
• assuming all customized equipment automatically qualifies for over-time recognition without testing '
• no alternative use'
• or enforceability of the payment right, particularly under local contract law where cancellation clauses may be silent or unenforceable
• applying cost-to-cost progress using budgeted costs that are not regularly updated for known overruns, overstating percentage complete and revenue
• conflating advance/mobilization payments (a financing or deposit item, i.e., a contract liability) with revenue earned, recognizing revenue on cash receipt rather than on performance.