Close the project account with an explicit exceptions list
Compare approaches
TL;DR — what you’ll learn
- Reconcile final quantities, approved changes, payments, advances, retention, materials and securities in connected streams.
- Keep client and subcontract accounts separate, with a clear basis for every balance.
- Put unresolved claims and conditions in an owned exceptions list instead of forcing the account to appear settled.
- Distinguish financial record closure from contractual discharge and obtain the appropriate final authority.

Illustrative EPC site office and plant readiness yard; not a client project site.
Stores has reconciled the materials and closed its project register. A variation remains disputed, retention is still held, and the final settlement document has not been reviewed. The project dashboard nevertheless says account closed because one department finished its part.
A final account needs a coordinated reconciliation and an explicit exceptions decision. Each stream should show its agreed position, evidence and unresolved items. Financial closure, operational handover and contractual discharge may require different decisions; a completed ledger task cannot make them interchangeable.
- Reviewed base value
- ₹100 lakh
- Source measurements and contract basis retained
- Approved changes
- +₹8 lakh
- Authorised additions in this example
- Agreed value
- ₹108 lakh
- 100 + 8
- Recorded payments
- ₹90 lakh
- Reconciled on the same stated basis
- Residual before further adjustments
- ₹18 lakh
- 108 − 90
- Separate disputed variation
- ₹4 lakh claimed
- Owner and next decision remain in the exceptions list
Illustrative same-basis arithmetic excludes tax, retention, advances and other adjustments. The ₹4 lakh claim is not part of the approved ₹108 lakh.
Read the visual as text
Reviewed base value: ₹100 lakh. Source measurements and contract basis retained. Approved changes: +₹8 lakh. Authorised additions in this example. Agreed value: ₹108 lakh. 100 + 8. Recorded payments: ₹90 lakh. Reconciled on the same stated basis. Residual before further adjustments: ₹18 lakh. 108 − 90. Separate disputed variation: ₹4 lakh claimed. Owner and next decision remain in the exceptions list.
Original explanatory visual: NextEdge Labs. Illustrative records, not client results.
- STEP 01Reconcile scope and changes
Owner: QS and commercial reviewers
Preserve final measurements and authorised values.
- STEP 02Reconcile ledgers and obligations
Owner: Finance, stores and security owners
Keep parties, cash, advances, retention and instruments distinct.
- STEP 03Review the exceptions
Owner: Delegated authority and contracts advisers
Identify disputed amounts and closure conditions.
- STEP 04Approve and preserve the final position
Owner: Authorised signatories
Save the decision, evidence index and remaining conditions.
Approve only the stated financial and contractual scope.
Resolve the unexplained balances or revise the proposed conditions.
Return path: Return the authorised resolution to the relevant stream and repeat the combined final review.
Read the workflow as text
1. Reconcile scope and changes (QS and commercial reviewers) → 2. Reconcile ledgers and obligations (Finance, stores and security owners) → 3. Review the exceptions (Delegated authority and contracts advisers) → 4. Approve and preserve the final position (Authorised signatories). After step 3, ask: Is the proposed closure supported with explicit exceptions? Yes: Approve only the stated financial and contractual scope. No: Resolve the unexplained balances or revise the proposed conditions. Return: Return the authorised resolution to the relevant stream and repeat the combined final review.
Workflow: NextEdge Labs. Apply the project’s actual authority and procedures.
Establish the account and its parties
Identify the contract, legal entities, currency, scope and reporting cut-off. Separate the owner's account with the contractor from the contractor's accounts with subcontractors and suppliers. Their balances may be related operationally, but one party's receivable is not automatically available to settle another party's payable.
Collect the final measurement basis, approved changes, certificates or invoices, ledger entries, bank receipts or payments, advance recovery, retention, material balances and securities. Record the current version and reviewing owner for each. A folder containing all these files still needs a common reconciliation basis.
The Department of Expenditure's Works Manual, section 7.6 discusses material, user-department and payment reconciliation within its public-works scope. It is a useful way to organise the streams. The actual contract, accounting policy and delegated authority determine your final approval and settlement process.
Work an agreed value with a separate disputed claim
In this fictional arithmetic example, the reviewed base value is ₹100 lakh and approved changes add ₹8 lakh. The agreed value is therefore ₹108 lakh. Recorded payments against that same basis total ₹90 lakh, leaving ₹18 lakh before any further adjustments. For this simplified example, there are no taxes, advances, retention or other adjustments in those figures.
A further ₹4 lakh variation remains disputed. Keep it outside the approved ₹108 lakh and show its claimed amount, source, status and owner. Do not add it to the agreed value simply because it was submitted, or remove it from the exceptions list because finance has not recognised it as an agreed balance.
The commercial and finance reviewers determine the actual treatment of the claim in their respective records. If the dispute is resolved, record the authorised outcome and update the relevant bridge. Preserve the earlier agreed and claimed positions so the final movement remains explainable.
Reconcile quantities and changes before the total
The quantity surveyor or designated measurement owner should confirm the final scope and measurement basis under the project's process. Identify duplicate, omitted, returned or superseded measurement records. Preserve the relationship between final quantities and earlier interim certificates.
For changes, separate instructed or reported work, submitted quotations, reviewed amounts and authorised approvals. A final-account spreadsheet should not promote a pending quotation into an approved change because it contains a rate and signature from the wrong authority.
Link each final value to its evidence. If the final measurement differs from the last interim position, explain the movement. A reviewer should be able to trace the difference without reopening every bill manually or relying on the estimator's memory.
Check cash, advances and retention on their own basis
Finance reconciles recorded receipts and payments to the bank and the relevant ledger entries. The client-payment reconciliation guide explains why existing cash allocation is different from creating a new bank movement. Resolve unapplied amounts and reversals before presenting a final outstanding position.
Review advances and recoveries with their original references and any reversals or replacements. Keep client advances and subcontractor advances separate. A recovered amount should not be deducted again merely because it appears in both an earlier certificate and a summary sheet.
Retention needs a counterparty-specific balance and the actual release conditions. The retention-register guide covers that distinction. Final measurement agreement does not automatically establish that every retention release condition has been met.
Keep materials and securities connected to their obligations
Stores reconciles materials, issues, returns, approved dispositions and remaining custody. Quality and engineering owners confirm the relevant acceptance evidence. Closing the material register establishes that stream's reviewed position; it does not settle a disputed variation or release a guarantee.
For client-supplied items, preserve ownership and the agreed reconciliation. The free-issue material guide explains why physical custody and financial ownership should not be collapsed. Any shortage or proposed recovery needs its actual evidence and authorised treatment.
Review guarantees, deposits and other security against their instruments and underlying obligations. Record required extensions, release decisions and bank or finance evidence separately. A project status change should not automatically terminate an instrument or make blocked funds available.
Make the exceptions list a decision record
Each exception needs an amount or scope, source evidence, current status, responsible owner, next action and decision authority. Use a meaningful category: measurement unresolved, change disputed, cash unapplied, advance difference, retention condition pending, material discrepancy or security action outstanding.
Keep claimed, reviewed and approved amounts distinguishable. Where an exception has no reliable value yet, say so and assign the valuation task. A precise-looking estimate should not be inserted merely to make the final total appear complete.
If a conditional closure is proposed, record exactly what is being approved and which matters remain open. Qualified contracts or legal reviewers should assess the wording and effect of releases, acknowledgements or settlement documents. A software checkbox called final and complete cannot determine that effect.
Test the final review across departments
Ask measurement, commercial, stores and finance reviewers to reconstruct one package from the final account. Include a disputed variation, an advance correction and a security awaiting release. Each should be able to identify their own decision and the dependencies on other streams.
A controlled reconciliation workbook can work when sources and approvals are disciplined. An ERP or project-cost platform can reduce repeated entry, but it still needs versioned evidence and an exceptions route. Compare the ability to explain the final position, not simply produce a polished closure certificate.
Export the accepted reconciliation, evidence index, approval record and remaining exceptions. Agree the retention and retrieval arrangements before project access is removed. The final account is likely to be needed after the team that assembled it has moved on.
The useful outcome is an approved position whose boundaries are clear. Where a claim remains unresolved, the record should say so plainly and preserve the next action.
- Reconcile the final scope, approved changes and financial records on a stated basis.
- Review client and subcontract streams separately, including advances, retention and materials.
- Assign every remaining exception and obtain the required settlement review.
- Save the authorised final position and explicit conditions in a retrievable closeout package.
Compare this workflow with your current setup
Share the step that takes the most manual work, the systems involved and the exceptions your team handles. That gives us a concrete starting point for comparing approaches.
References and further reading
Sources checked 15 October 2026. The worked examples and diagrams are original editorial explanations, not client results.
- Department of Expenditure — Manual for Procurement of Works, Second Edition 2025Sections 5.1.4–5.1.5, 7.3.4, 7.4.5 and 7.6 as cited; public-works scope
Indian public-works guidance within the manual’s scope.
Visual credits
Original explanatory visuals and workflow diagrams by NextEdge Labs. Labels and text equivalents are included in the page. Numerical scenarios are illustrative; diagrams preserve the project owner’s approval and exception decisions.