Valuing and Reconciling Long-Term Contract Balances at Year-End

At each reporting date, a construction company holds a position on every active contract. That position has multiple moving parts: revenue recognised under POC, valuations issued to the customer, customer certifications, payments received, retentions withheld, applications for variations, and provisions for known issues. The year-end reconciliation pulls all of these together onto a single contract-by-contract schedule and confirms that the figures going into the accounts are internally consistent. Auditors test this schedule heavily.

The contract reconciliation in seven moving parts

For each material contract at year-end, the reconciliation captures:

1. 1Total contract value (original plus agreed variations).
2. 2Cumulative revenue recognised to date under POC (using the cost-input or output method).
3. 3Cumulative valuations or applications issued to the customer.
4. 4Cumulative customer certifications (the amount the customer has formally accepted).
5. 5Cumulative payments received from the customer.
6. 6Cumulative retentions withheld by the customer.
7. 7Outstanding applications (issued but not yet certified) and unsettled claims.

How the figures relate to each other

Several relationships should hold across the reconciliation. Discrepancies are not necessarily errors but they require explanation:

• Cumulative revenue recognised (POC) versus cumulative valuations issued: the difference appears as either "amounts due from customers" (POC ahead of valuations) or "amounts due to customers" (valuations ahead of POC). This is where the balance-sheet contract debtor or creditor sits.
• Cumulative valuations issued versus cumulative customer certifications: difference reflects pending certification or disputes.
• Cumulative customer certifications versus cumulative payments received: difference reflects unpaid invoices and retentions withheld.
• Cumulative retentions withheld: should reconcile to the retention balance disclosed under trade receivables.

Worked reconciliation example

For a single contract at year-end:

Reading the implications:

• POC revenue (£1,890,000) exceeds valuations issued (£1,800,000) by £90,000 → balance-sheet position: amounts due from customers (asset) of £90,000.
• Valuations issued (£1,800,000) exceed certifications (£1,720,000) by £80,000 → outstanding applications matching the £80,000 not yet certified.
• Certifications (£1,720,000) less retentions withheld (£86,000) = £1,634,000 paid → reconciles cleanly to payments received.
• Retention balance (£86,000) sits in trade receivables.

A reconciliation that does not tie out across these relationships indicates either a control breakdown (lost paperwork, miscoded transactions) or a disclosure issue (unrecorded variations, unrecognised claim revenue). Both warrant investigation before the accounts are finalised.

When the reconciliation reveals problems

Common patterns when something is wrong:

• POC revenue materially exceeds valuations. May indicate over-recognition of revenue (cost forecast too low) or genuine catch-up valuations not yet issued. Investigate the cost forecast.
• Certifications materially below valuations. Customer is rejecting valuations. Investigate which heads are disputed and whether claim revenue should be deferred or recognised at a lower amount.
• Payments materially below certifications. Customer is paying late or has stopped paying. Trigger credit-control review and consider whether contract receivable is impaired.
• Retention balances drifting upwards over time. Retentions not being released on schedule. Investigate whether projects have crossed practical completion or end of defects liability period.

Common questions

Who should sign off the reconciliation?

For internal control purposes: the contract commercial manager prepares; the senior commercial leadership reviews; the finance director signs off. For audit purposes: the same chain of evidence with documented dates and challenge points. A reconciliation prepared by finance alone, without commercial input, is materially weaker.

How material is "material" for separate reconciliation?

Convention: every contract above 1% of total revenue, plus any contract subject to specific concerns regardless of size. For a contractor with £20m of revenue, contracts above £200,000 each get individual reconciliation. Smaller contracts can be grouped as long as no single contract within the group has known issues.

What documentation does the auditor expect?

The reconciliation schedule itself. Supporting CVRs for each contract. Customer certification documents and payment remittances. Communication trail on outstanding applications and disputes. Independent surveyor reports where used. Sign-off audit trail.