Retainage Management for AP Teams: Calculation, Tracking, and Release

Retainage is the most misunderstood balance in contractor accounting: money you owe (or are owed) that is deliberately not paid yet, accruing invoice by invoice, governed by contract terms, and released only when documentation says so. Handled loosely, it distorts AP aging, leaks out in accidental full payments, and gives up leverage at exactly the moment leverage matters. This guide covers the mechanics AP teams need: calculation, ledger treatment, the release workflow, and the register that holds it together.

For the wider workflow this sits in, see the complete construction AP guide and the controls framework. For the concept itself, see the retention/retainage glossary entry.

Why retainage exists

Retention aligns incentives across a long project: by withholding 5–10% of each progress billing, the paying party keeps enough value on the table that finishing — punch lists, closeout documents, warranty items — is worth the sub's while. It appears on both sides of a contractor's balance sheet: retention payable (held on your subcontractors) and retention receivable (held on you by owners and GCs). AP owns the payable side; both sides need the same discipline.

The calculation, including the reduction milestone

The base case is simple: billing × retainage rate. Real contracts add a wrinkle — the rate often reduces at a completion milestone, commonly 50%:

Worked example. $850,000 subcontract, 10% retainage reducing to 5% after 50% completion. At 60% complete, billings to date are $510,000. Retention accrued: the first $425,000 of billings (up to the 50% point) withheld at 10% = $42,500, plus the next $85,000 withheld at 5% = $4,250 — $46,750 held. Billings from here to completion accrue at 5%, so projected total retention at 100% is $63,750, not the $85,000 a flat 10% would suggest.

Numbers on an AIA G702/G703 application follow the same logic: retainage is computed on completed work and stored materials and deducted before the payment due. The retainage calculator runs this structure — base rate, milestone, reduced rate, partial releases — for any contract.

Two calculation rules prevent most disputes:

• Approved change orders change the base. Retention applies to the current contract value including approved changes — recalculate when change orders land, do not keep withholding against the original value.
• The invoice states it, the contract governs it. Subs sometimes bill with the wrong retention rate, especially after a milestone. The match is against contract terms, and the discrepancy goes back to the sub — it is one of the standard construction exception types.

Ledger treatment: keep it out of AP aging

The invoice posts in full; the withheld portion posts to a retention payable account by job and vendor; the balance goes to regular AP. Done this way, AP aging shows what is actually due and payable, and retention shows as its own balance with its own expected release dates.

The common failure is posting the full invoice to AP and "remembering" the withholding at payment time. That inflates aging, invites accidental full payment, and makes the retention balance unknowable without re-deriving it from history. QuickBooks will not do the split for you natively — which is why contractors either run the posting discipline manually with a register, or use construction AP software that posts the split and tracks the balance per job automatically.

The release workflow

Treat release as a controlled event with gates, in sequence:

1. Trigger — substantial completion, final acceptance, or a contractual early-release milestone.
2. Completion verified — punch list closed, confirmed by the project team in writing.
3. Final documentation collected — final unconditional lien waivers from the sub and known sub-tier suppliers, plus any required closeout documents (as-builts, warranties, O&M manuals per contract).
4. Balance confirmed against the register — the release amount ties to the independently maintained retention balance, net of prior partial releases.
5. Approved under the authority matrix — retention releases are payment events at the top of the approval framework, not routine invoices.
6. Posted against retention payable — clearing the balance, never entered as a fresh invoice (the classic route to double payment).

The person approving the release should not be the person maintaining the register — that pairing is what makes the balance trustworthy.

The retention register

One row per subcontract, maintained as a control document:

Tie the register to the retention payable balance at month-end — it is one line on the month-end AP checklist and one of the core metrics in the Construction AP Benchmark Centre.

Common failure modes

• Retention buried in AP aging — aging overstates due amounts and someone eventually pays the full invoice.
• Rate never steps down — the milestone passes and billings keep being withheld at the base rate; the sub notices before you do.
• Release without final waivers — the remaining leverage on closeout documentation is given away with the payment.
• Release entered as a new invoice — the payable balance never clears and the amount is now payable twice.
• Nobody owns the receivable side — retention held on you goes unbilled at completion because no one tracks the trigger.

Every one of these is a process gap, not a math problem — which is why the fix is the register, the posting discipline, and the gated release rather than more spreadsheet effort. Nexus Build automates exactly that set: withholding at contract terms on each billing, a per-job retention balance synced to QuickBooks, and releases blocked until the final waivers are signed.

Retainage rules — caps, timing, escrow requirements — vary by state and project type. This guide covers operational practice, not legal advice; put state-specific questions to qualified construction counsel.