Track retention release conditions across client and subcontract accounts

For each account, identify the counterparty, contract, currency, retention basis, applicable limits and release provisions. Link the executed clause and amendments. Have the authorised commercial and finance owners validate how those terms are represented.

Do not hard-code a universal retention percentage or release period across all packages. Terms may vary by contract, stage, security arrangement or amendment. The register should show the actual reviewed basis, including any uncertainty that still requires interpretation.

Separate retention from other deductions, disputed amounts and securities. They may all reduce a payment, but their reasons and release conditions differ. Combining them into one “held amount” makes later reconciliation and follow-up harder.

The retained balance is the cumulative amount withheld under the applicable records, adjusted for releases and corrections. Eligibility indicates that specified conditions appear satisfied and the amount can enter the required request or review process. Approval is the authorised decision to release. Settlement records the actual payment or receipt.

Autodesk's payment application documentation provides an example of structured payment-application records. Project retention controls must still preserve the contract-specific conditions and the distinction between a certified amount and settled cash.

Keep dates and evidence for each stage. A requested release may remain unapproved. An approved release may remain unpaid. Reporting both as “released” obscures the action needed: commercial follow-up in one case, collection or payment processing in the other.

Consider a synthetic project with ₹8 lakh retained by the client and ₹3 lakh retained from a subcontractor. Assume the client contract permits a ₹4 lakh release request after the relevant completion evidence, which is available. The subcontract's next release requires documents that are still outstanding.

The example uses fictional terms. It does not recommend withholding a particular amount or establish a right to link the two accounts. The project must follow each agreement and applicable review.

If the client later pays ₹4 lakh, the client retained balance falls to ₹4 lakh, assuming no other movements. The subcontractor balance remains ₹3 lakh until its own release is authorised and recorded. Showing a net ₹1 lakh figure would hide both the remaining client receivable position and the separate subcontract obligation.

A release condition should identify the evidence needed and the person who verifies it. “Project complete” may be too broad if the agreement refers to a specific certificate, stage or defined completion event. Record the actual contractual reference and the reviewed interpretation.

For defect-related stages, link the applicable defect period or closure evidence without inventing a standard duration. For document conditions, list the required deliverables and acceptance status. For a security substitution, preserve the approved instrument, validity and release decision under the relevant process.

A checklist should help the reviewer make the decision, not replace contractual judgement. If a condition is disputed or its evidence is incomplete, show that status and the owner of the next action. Avoid moving it to eligible merely because a planned date has passed.

Link each retention movement to the relevant bill, certificate, payment application, credit or adjustment. Record gross retention assessed, changes and releases in a way that can be reconstructed by account and period.

Finance should confirm the ledger mapping and treatment. The register may be a management subledger or supporting schedule, but its closing balance must reconcile to the defined accounting population. Explain timing differences and corrections rather than using an unsupported balancing entry.

Cancelled or revised certificates need corresponding updates. Preserve the original movement and reversal where the system requires it. A revised bill should not leave both the old and new retention deduction in the cumulative balance.

Forecast expected release dates using current evidence and the reviewed contractual conditions. Label dates as expected until the necessary decisions occur. A forecast receipt is not cash available today.

Assign follow-up owners for missing evidence, release requests, approvals and settlement. The project team may own completion documents, commercial teams may own the request, and finance may own payment reconciliation. The register should show the handoff between them.

Review old balances individually. Some may be awaiting a routine document; others may be disputed or tied to a longer-term condition. Age alone does not explain recoverability or payment obligation. Finance and commercial owners should assess material uncertainties under the relevant policies.

Use a sample account with two release stages. Confirm that the first release reduces the retained balance but does not close the second stage. Test a release approved but unpaid, a cancelled certificate and a replacement security where the contract permits it.

Check that a client receipt does not automatically trigger a subcontract release unless an expressly reviewed rule requires that relationship. Even then, preserve the distinct accounts and evidence. A shared project code is not a sufficient basis for automatic offsetting.

Measure unreconciled balances, eligible amounts awaiting request and approved amounts awaiting settlement separately. Each metric points to a different improvement opportunity.

A reliable retention register tells the project what is held, why it is held and what must happen next. It supports collection and payment decisions without merging separate contractual obligations.

1. Validate retention terms and release conditions for each account.
2. Separate balance, eligibility, approval and settlement statuses.
3. Link every movement to its source bill or authorised adjustment.
4. Assign missing evidence and release follow-up to named owners.
5. Reconcile client and subcontract balances independently at each close.