Construction retainage collection: recover the last payment by project

Why the last payment needs its own collections queue

A 2025 r/Contractor discussion about final payment describes a siding contractor whose last installment depends on a final inspection for a much larger project. The poster worries that their own scope will be finished long before that event. This is an anecdote about mismatched milestones, not evidence that the clause is enforceable or typical.

A retainage register can show how much is withheld. A collection queue must also show what makes the balance releasable and who can approve it. Otherwise, “waiting for closeout” becomes a permanent status even after the contractor has supplied the relevant evidence. This guide focuses on moving a reconciled balance through the release and receipt steps.

Sources: Reddit r/Contractor: Final payment (2025 discussion; anecdotal)

Reconcile withheld, released and paid amounts first

For each job, obtain the cumulative retained amount, authorized releases, pending release requests and cash applications. Confirm how the ledger records retainage so the collector understands whether a released amount remains in retainage AR or moves to another receivable account. Track the transfer without counting the same dollars twice.

The balance should reconcile across the subcontract, pay applications, any certificates, ledger and customer response as applicable. Investigate differences before issuing a final request. A release request for an old spreadsheet total can be wrong if an earlier partial release was already paid or if the contract basis changed.

Translate the release conditions into checkable events

Read the applicable agreement and project instructions for the relevant completion, acceptance and document requirements. Record the source for each condition and who confirms satisfaction. The actual trigger may relate to a subcontract scope, incremental acceptance, project completion or another defined event. Avoid replacing the contractual wording with a generic “job done” checkbox.

Confirm whether your team must submit a distinct retainage invoice, a final pay application or another release package. Ask who receives it, which supporting records are required and how a deficiency is communicated. Keep the answer with the job instructions so the next coordinator does not have to rediscover the process when the project manager moves on.

Use four statuses for a retainage collection queue

Give each retained amount a status that identifies the next task. “Not ready” means a documented release condition still needs attention. “Ready to request” means the responsible reviewer has confirmed the basis for submission. “Requested” means the release package has been sent through the required channel. “Approved, unpaid” means there is a payment-release or receipt question.

Attach evidence to the status rather than treating a color as approval. Keep a separate exception for an asserted deduction or unresolved entitlement. The collector should know whether to call the closeout coordinator, project reviewer or payment authorizer.

Worked example: reconcile a $27,000 retainage balance

Assume a fictional subcontract has accumulated $36,000 of withheld retainage. A prior $9,000 release has been received and applied, leaving $27,000. The authorized reviewer identifies $18,000 as eligible to request now and $9,000 as still dependent on an unresolved release condition under the example agreement.

Submit the $18,000 through the required process and keep the $9,000 with its specific condition and owner. When the payer approves the $18,000, update the collection status while keeping the ledger treatment consistent with accounting policy. Approval is not cash receipt. If only $12,000 later arrives and is applied, $6,000 remains in the approved-payment path.

The remaining retained or related receivable exposure is $15,000: the $6,000 unpaid approved portion plus $9,000 awaiting the condition. No amount has vanished. This is an invented allocation, not a suggested release percentage, customer result or rule for all projects.

Send a retainage request that identifies the decision needed

An original illustrative status request is: “Our reconciliation shows $27,000 in remaining retainage on Project North. Our release package requests $18,000 against the scope-acceptance record attached. Please confirm receipt, identify any specific deficiency and advise who approves the request and its next payment checkpoint. The remaining $9,000 is tracked separately pending the condition identified in our register.”

Tailor the wording to the actual project and the reviewer’s determination. If the recipient says “waiting for the owner,” ask what event remains and which retained amount it affects. Keep any entitlement disagreement in the authorized commercial channel. Repeating a generic final-invoice email will not resolve a missing acceptance decision.

Check whether a project-specific payment rule applies

U.S. DOT’s official Part 26 guidance discusses retainage release on DOT-assisted contracts and explains why a subcontractor’s completed scope should not simply wait for a much later whole-project completion. It also addresses satisfactory completion, documentation and incremental acceptance. These requirements are scoped to the covered program and project.

Ask the qualified reviewer to confirm the applicable regulation, recipient implementation and contract terms, including any current changes. Private projects and other public work can have different rules. Use the project-specific source to establish a deadline; a general blog cannot determine the due date from the fact that retainage exists.

Sources: U.S. DOT: Official Part 26 questions and answers, prompt payment and retainage (DOT-assisted work)

Review final releases against the payment being made

California CSLB publishes distinct conditional and unconditional progress and final release forms. It is a useful example of why a final-payment exchange should identify both the type of release and the actual payment status. Other jurisdictions have different requirements and effects, so use the forms and review process appropriate to the project.

Before signing, have the authorized person review amount, covered period, exceptions and unresolved changes or claims. Preserve the approved version and receipt evidence. Do not let a closeout administrator silently settle an unresolved deduction by uploading a final release that nobody has reviewed.

Sources: California CSLB: Conditional and unconditional waiver and release forms (California only)

Review the portfolio for balances with no next owner

At month-end, review retained balances across active, substantially complete and closed projects. Look for amounts with no release condition recorded, requests with no receipt, approved releases with no payment date and cash received with no application. Older jobs are easy to miss when project managers have moved to new work.

Buildalytic’s payment-follow-up capability can be evaluated for contacting the designated recipient and recording the missing status. Test it on one eligible release and one unresolved closeout condition. Keep legal interpretation, acceptance, waiver approval and accounting adjustments with the responsible team.

Sources: Buildalytic: Construction payment follow-up