Get a personalized demo of Stuut and see how it can help with AR automation.
Completed AIA forms don't collect cash. Retainage sits in owner accounts for months after substantial completion, change order invoices age past 60 days while waiting for follow-up, and lien waiver exchanges stall because AR teams are already preparing the next pay application. Standardized billing forms solve the documentation problem. They don't solve the execution problem: Getting payments collected, matched, and posted across a portfolio of complex, parallel projects.
This article breaks down the mechanics of construction progress billing and retainage, then explains how adding autonomous AR execution to your existing ERP reduces DSO and unlocks trapped working capital.
Progress billing is the standard payment method on most construction contracts. Contractors bill incrementally as work completes rather than invoicing the full contract value at the end, which creates significant administrative complexity for AR teams managing multiple jobs simultaneously.
The AIA G702 and G703 forms are the industry standard for submitting and certifying progress payments. The G702 cover page summarizes the contract value, total work completed to date, retainage withheld, previous payments received, and the current amount requested. The G703 provides the line-by-line detail tied directly to the Schedule of Values, showing work completed this period, cumulative totals, materials stored on-site, and the remaining contract balance. Architects review and certify these forms before owners release payment, and any discrepancy between the G703 and actual site progress sends the entire application back for correction.
A Schedule of Values (SOV) breaks the total contract amount into individual line items, each with a specific dollar value. Think of it as a recipe for the project: Instead of one lump sum, the SOV divides the contract into distinct, measurable components (foundation, framing, mechanical, electrical) so each billing period reflects precisely how much of each component is complete. Procore describes the SOV as progress billing's backbone because every pay application draws from it to justify requested amounts.
AR teams measure billable work using the percentage-of-completion formula:
Percentage of Completion = Costs Incurred to Date / Total Estimated Costs
For example, if a contractor has spent $600,000 on a $1,000,000 project, the project is 60% complete and the contractor can bill 60% of the total contract value.
The pay application moves from subcontractor to general contractor to architect for certification, then to the owner for payment approval. Any rejection at the architect or owner stage restarts the cycle and delays cash by 30 days or more.
Expert insight: AR teams that track which applications are waiting at the architect certification stage and follow up proactively surface disputes before the owner review, when corrections are faster and less costly than resubmitting a full application.
Retainage is the percentage owners withhold from each progress payment until substantial or final completion, as a financial guarantee against incomplete or defective work. The industry standard is 5% to 10%, with 10% common on private projects. Federal contracts governed by FAR 52.232-5 cap retainage at 10% and allow the contracting officer to reduce retainage when the contractor demonstrates satisfactory progress, with no fixed completion percentage threshold in the regulation, though many state and local jurisdictions cap public project retainage at 5%.
The AIA defines substantial completion as the stage where the work is sufficiently complete that the owner can use the project for its intended purpose. At this milestone, warranty periods begin, occupancy permits may be granted, and partial retainage releases are initiated. Final completion triggers the release of all remaining retained funds. AR teams that track these milestone dates systematically and trigger collection workflows automatically shorten the time between project close and cash receipt.
Cash flow impact (as an illustration): On a project with 10% retainage withheld, expenses are 100% immediate but only 90% of each billed amount is collectable until final completion. On a project with a 5% net profit margin and 10% retainage, a contractor operates with negative cash flow relative to profit until the final retainage check clears. Across a portfolio of active projects, that trapped cash can represent months of operating expenses sitting in an owner's account instead of the contractor's.
Proper change order documentation requires written notice to the owner and architect as soon as the change is identified, because most contracts include strict deadlines for submitting change order requests:
Once a change order is approved, the AR team adds it as a new line item in the SOV before submitting the next pay application. Billing for change order work without an updated SOV can create documentation mismatches during the approval process, restarting the 30-day payment cycle.
AR teams that isolate change order billing from base contract billing in their systems can track the aging of each change order independently. This matters because change orders frequently carry a different approval timeline and payer contact than the base contract.
The distinction between lien waiver types determines whether a contractor retains lien rights if payment doesn't arrive:
A contractor who signs an unconditional waiver before the check clears surrenders lien rights with no recourse if the payment is reversed.
Payment processing on lender-funded and bonded projects often requires the contractor to submit a signed waiver before the owner releases funds. The administrative back-and-forth of exchanging waiver drafts, waiting for counter-signatures, and confirming receipt adds time to every payment cycle.
A payment bond guarantees that subcontractors and material suppliers incorporated into a construction contract will be paid, even if the prime contractor defaults. On public projects, the Miller Act (40 U.S.C. § 3131) requires payment bonds for federal construction contracts exceeding $150,000. The AR team's obligation is to document all work performed and materials supplied accurately, because bond sureties evaluate claims against this documentation.
Notice deadlines on bonded projects are strict. Filing deadlines vary by jurisdiction and contract type. Under the Miller Act (40 U.S.C. § 3133), claimants without a direct contract with the prime contractor must file within 90 days of last work performed on federal projects. State little Miller Acts set their own deadlines, which may extend further. AR teams that handle bonded projects in the same manual workflow as private jobs risk missing these windows and losing bond coverage on legitimate unpaid claims.
Expert insight: The most damaging errors in bonded project billing cluster around three areas: (1) Missing notice filing windows because no one tracked the clock from the last work date, (2) Submitting pay applications with incomplete project identifiers that create documentation gaps sureties use to delay claims, and (3) Billing change order work before the SOV is updated, which stalls the entire application. AR teams that enforce documentation standards at submission prevent these gaps before they reach the dispute stage.
Standard construction billing software handles the front half of the workflow: Capturing site data, generating compliant pay applications, and routing them for approval. The gap is in the back half: Following up on submitted applications, collecting approved amounts, matching partial payments to specific SOV line items, and following up on aging retainage receivables as they become collectible. That execution gap is where AR teams spend the most manual hours.
Construction ERPs are strong systems of record. They hold the GL, store the job cost structure, and generate compliant pay applications. They don't contact customers, follow up on aging receivables, match complex partial payments, or escalate at-risk accounts autonomously. AR automation handles that work directly.
Stuut connects to major ERPs including SAP, Oracle, NetSuite, and Dynamics via API without requiring an IT project, process redesign, or rip-and-replace. Standard environments go live in 3 to 4 days. Heavily customized environments may take up to 10 days for configuration and testing.
Once connected, Stuut reads invoice data from your ERP and writes cash application entries back in real time. Every progress payment received posts to the AR subledger automatically, without a batch process or manual match. The DSO improvement process that finance teams use to benchmark progress depends directly on this kind of real-time visibility.
Stuut's autonomous collections capability monitors invoice aging and contacts customers across email, SMS, and voice before invoices go overdue. Construction AR teams using this approach stop waiting for payments to appear and start proactively accelerating collection timelines. Across Stuut customers, the average outcome is a 37% DSO reduction and a 40% cash flow increase, though results depend on portfolio mix and existing AR process maturity.
ERPs generate and store progress bills accurately. They maintain the SOV, hold historical job cost data, and post GL entries for the Controller. If your only requirement is accurate invoicing and compliant financial records, a well-configured Sage 300 CRE or Oracle instance handles that without additional software.
You've likely outgrown your ERP's AR capabilities if you recognize any of these situations:
Stuut's cash application engine handles exact matches, partial payments, short-pays, and bulk deposits at a 95%+ automated match rate. A single ACH deposit covering three progress payment installments and a retainage release from one customer gets broken into sub-payments and matched to the correct open invoices automatically, with no collector involved.
Construction AR teams managing multiple active projects use Stuut to autonomously follow up on aging retainage receivables, match partial payments, and collect on change order invoices. Book a demo to see the execution layer in action on a construction portfolio.
AR automation platforms sync with your ERP to maintain a retainage aging report by project, showing withheld amounts, then autonomously follow up on aging retainage balances as invoices become past due. This replaces the manual calendar-and-spreadsheet approach most construction AR teams rely on today.
Retainage releases in two stages: A partial release at substantial completion and a final release when all punch list items close. Exact timing and amounts depend on contract terms and applicable state law. The applicable cap depends on funding source: Federal contracts governed by FAR 52.232-5 cap retainage at 10%, while many state and local jurisdictions set a lower cap of 5% for publicly funded projects. If your contract is state or locally funded, check the applicable jurisdiction's prompt payment or public works statute for the specific limit.
Yes. AR platforms that include lien management can track state-specific waiver form requirements and store signed documents tied to specific pay applications. This reduces the manual exchange that delays cash application on lender-funded and bonded projects.
Accurate change order billing requires documenting the change in writing before starting work, obtaining all required signatures before billing, and updating the SOV to add the change order as a separate line item before the next pay application is submitted. Billing for work without a signed change order and an updated SOV creates a mismatch that stalls the entire pay application.
Schedule of Values (SOV): A document that breaks the total construction contract into individual line items, each with a specific dollar value, used as the basis for every progress billing period. It establishes at contract execution and updates only when approved change orders modify scope.
AIA G702/G703: The American Institute of Architects standard forms for construction payment applications. The G702 summarizes the payment request and the G703 provides the line-by-line SOV detail supporting it.
Subledger: The AR subledger is the detailed record of all open invoices, payments, and balances by customer that feeds into the general ledger. In construction, the subledger must separately reflect progress payments, retainage withheld, and retainage released for accurate financial reporting.
Retainage: The percentage (typically 5% to 10%) owners withhold from each progress payment until substantial or final completion, as a financial guarantee against incomplete or defective work.
Days Sales Outstanding (DSO): The average number of days a company takes to collect payment after a sale has been made. In construction, DSO is a primary measure of AR efficiency because retainage, slow pay application cycles, and change order disputes all extend collection timelines.
