Retainage is the practice of withholding a percentage of each progress payment to a subcontractor or supplier until the work is substantially complete. The withheld amount, typically 5 to 10% of each invoice, creates a liability on the GC's balance sheet that is released only when defined completion conditions are met.
For a general contractor managing 50 subcontractors across three active projects, retainage creates three parallel AP workflows that are connected but distinct: the current-period invoice processing workflow, the retainage balance tracking workflow, and the retainage release workflow triggered by completion documentation. None of these workflows are handled well by standard AP automation without construction-specific configuration.
The financial stakes are material. A GC with $20M in active subcontract value typically carries $1M to $2M in withheld retainage at any point. Releasing retainage early because completion documentation was incorrectly accepted releases leverage before the work is done. Holding retainage after all completion conditions are met damages subcontractor relationships and, in many jurisdictions, creates prompt payment law violations.
What Retainage Creates in the AP Workflow
Split invoice processing
When a subcontractor submits a progress invoice for $100,000 on a 10% retainage contract, the AP team processes a current payment of $90,000 and withholds $10,000. In a manual process, this split requires the AP team to create two payment records from one invoice: the current payment to be processed immediately and the retainage balance to be tracked as a future obligation.
Without automation, the retainage tracking lives in a spreadsheet that is separate from the AP system. The spreadsheet is updated with each progress invoice, but its accuracy depends on the AP team maintaining it consistently and the spreadsheet being accessible to whoever needs to review retainage balances.
Retainage balance liability tracking
The cumulative retainage withheld from each subcontractor must be tracked as a liability that will eventually be paid. In a manual process, this balance is either in the AP aging report under a separate retainage payable category, or in a separate spreadsheet, or somewhere between the two with neither being authoritative.
When the GC is preparing financial statements, the retainage liability must be accurately stated. When the GC is negotiating with lenders, the retainage payable affects working capital calculations. When a subcontractor asks how much retainage is outstanding, the AP team should be able to answer immediately from the system rather than from a spreadsheet that may or may not be current.
Conditional release workflow
Retainage is released when defined completion conditions are met. Typical conditions include: substantial completion certification from the project manager, final lien waiver from the subcontractor, warranty documentation delivered, and punch list items resolved. In a manual process, the AP team receives a release request, checks whether the required documentation has been collected, and processes the release payment.
The failure mode is documentation incompleteness. Release payments are processed before all conditions are verified because the AP team does not have a reliable system for tracking which conditions have been met. Alternatively, release payments are delayed because the AP team has no visibility into when conditions are met and relies on the project manager to remember to notify them.
What AP Automation Handles Differently
Automated retainage splitting at invoice entry
When a subcontractor invoice is entered with the contract reference, the AP platform reads the retainage percentage from the contract record and automatically splits the invoice into a current payment amount and a retainage hold amount. No manual calculation required. The two amounts are created simultaneously and coded to the correct GL accounts: accounts payable for the current payment and retainage payable for the withheld amount.
Retainage balance by subcontractor and project
Every withheld amount accumulates into a live retainage balance by subcontractor and by project. The AP platform shows at any moment the total retainage outstanding to each subcontractor, broken down by project, with the original contract reference and the completion status of each project. This is the single authoritative view that replaces the spreadsheet.
Document-gated release workflow
Retainage release is triggered by a structured completion checklist in the AP platform. The project manager marks each completion condition as satisfied and attaches the required documentation. The AP platform gates the retainage release payment on all required conditions being marked complete with documentation attached. An incomplete condition prevents the release from proceeding until the project team resolves it.
This document-gated workflow eliminates the most common retainage release error: releasing payment before all conditions are met because the AP team cannot verify completion status from the AP system alone. The workflow brings the completion verification into the payment authorization chain rather than relying on communication between the project team and the AP team.
Prompt Payment Law Compliance
Many jurisdictions have prompt payment legislation that imposes timelines on retainage release after substantial completion. Non-compliance carries financial penalties and creates lien exposure. An AP platform with retainage tracking capability can flag projects where the substantial completion date has passed and the retainage has not been released, giving the finance and legal teams advance warning before a prompt payment violation occurs.
This compliance flag is only useful if the substantial completion date is recorded in the system accurately. Building the project completion date tracking into the AP workflow, rather than relying on a separate project management system that may not be integrated, is the configuration step that makes the compliance monitoring meaningful.
