Pay applications are formal billing documents that include a Schedule of Values, lien waivers, and retainage calculations tied to project milestones — creating AP complexity that standard invoice workflows aren't built to handle. Platforms like Vergo address this by mapping pay app line items directly to job cost codes and syncing retainage balances to construction ERPs.
A pay application is a structured billing document used in construction to request progress payments based on work completed to date. Unlike a standard vendor invoice, a pay app is not a simple request for a fixed amount — it is a snapshot of a project's financial status at a specific point in time.
The standard pay app package typically includes AIA Form G702 (the application and certificate for payment), Form G703 (the continuation sheet with a Schedule of Values broken out by cost code or work scope), a lien waiver, and sometimes certified payroll or insurance certificates. Each line on the Schedule of Values represents a portion of the original contract, and the contractor bills a percentage of completion against each line.
Retainage — typically 5–10% of each draw — is withheld by the owner and not released until substantial completion or contractual milestones are met. This means every pay app results in a payable amount that is less than the billed amount, a distinction that must be tracked separately in your accounting system.
For a controller, pay applications introduce accounting challenges that standard AP workflows are not designed to handle. Each approved pay app from a subcontractor becomes a payable, but that payable has layers: the approved billed amount, the retainage withheld, the amount previously paid, and the net due this period. Tracking all four figures accurately — across dozens of subcontractors on a single project — is where AP complexity compounds.
The timing gap between pay app submission, owner approval, and actual payment creates another challenge. Subcontractors often submit pay apps before the general contractor has received approval from the owner, meaning liability may exist in the system before funding is confirmed.
Practical implications for construction AP teams:
For a project manager, a pay app approval delay means subcontractors slow work or stop showing up. For a controller, a pay app processed without proper matching creates audit exposure and potential double-payment risk.
Scenario 1 — The problem: A concrete subcontractor on the Riverside Office Building submits Pay App #4 for $142,000. The AP team receives it, codes it to the job, and queues it for payment. No one checks that the sub billed 90% complete on formwork that the site super has marked at 70% in the daily logs. The overpayment is released. Recovering it mid-project becomes a dispute.
Scenario 2 — Proper process: On the Harbor Logistics Warehouse project, the AP team requires that each pay app be cross-referenced against the project manager's approval in the project management system before it enters the payment queue. The PM's approved percentage-complete figures feed directly into the payable amount, retainage is automatically split to the retainage payable account by job, and the lien waiver is logged as a required document before the payment batch runs.
Scenario 3 — Retainage release complexity: At project closeout on a 14-subcontractor project, the controller must identify all open retainage balances by sub, confirm final lien waivers have been received, and release payments that have been sitting in the retainage payable account for 18 months. Without job-level retainage tracking from day one, this reconciliation can take weeks.
Construction-specific AP platforms address pay app complexity by treating retainage, lien waivers, and Schedule of Values matching as native workflow steps — not manual workarounds bolted onto a generic AP process.
Vergo is a card-agnostic expense management platform built for construction. Connect any corporate or project credit card and get full visibility and control over field spending.
A standard invoice requests payment for a fixed amount due. A pay application documents cumulative work completed against a Schedule of Values, calculates the percentage billed to date, deducts retainage, and offsets prior payments. The result is a net payment due for the period — a multi-step calculation that a standard invoice does not require.
Retainage withheld from a subcontractor's pay app should be coded to a separate retainage payable account at the job level, not lumped into the standard AP balance. This keeps the retainage liability visible, ensures it is not inadvertently paid early, and allows accurate WIP and cash flow reporting until the retainage release conditions are met.
A Schedule of Values (SOV) is a line-item breakdown of a subcontract, showing the value assigned to each scope of work. When a sub submits a pay app, they bill a completion percentage against each SOV line. AP teams must verify that billed percentages are aligned with approved field progress — overbilled SOV lines create overpayment risk and distort job cost reporting.
Lien waivers are legal documents in which a subcontractor or supplier waives their right to file a mechanics lien in exchange for payment. Conditional waivers are exchanged at payment time; unconditional waivers confirm payment was received. AP teams must collect and log the correct waiver type before releasing payment to protect the owner and general contractor from downstream lien exposure.
Pay apps move through a multi-party approval chain: subcontractor submits, GC reviews, owner approves, payment is issued. Each step introduces delay. If a GC's draw to the owner is rejected or reduced, the downstream payment to subcontractors is also delayed or reduced. Controllers must track the approval status of both incoming and outgoing pay apps to forecast cash accurately.
Generic AP automation tools handle standard invoices but lack native support for retainage splits, lien waiver tracking, and Schedule of Values matching. Construction-specific platforms like Vergo are built for these workflows, automating retainage coding, enforcing lien waiver collection before payment release, and syncing approved pay apps to ERPs like Sage, Viewpoint, and Procore without manual re-entry.