How do pay applications work in construction and how do they affect AP?

Key takeaways

• A pay application is a structured billing document that requests progress payments based on completed work, typically including AIA Forms G702 and G703, a Schedule of Values, and lien waivers.
• Retainage — usually 5–10% of each billing — is withheld until project milestones are met, requiring separate tracking in your accounting system.
• Pay apps create AP complexity through retainage accounting, lien waiver verification, Schedule of Values reconciliation, and timing gaps between submission and owner approval.
• Vergo proposes coding by inference from your own accounting structure and job cost history, so each pay app transaction is ready to code the moment it happens with AI-generated explanations that let reviewers confirm in seconds.
• Proper pay app processing requires cross-referencing approved amounts against project manager verification and job cost records before releasing payment.

What is a pay application in construction?

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, meaning every pay app results in a payable amount that is less than the billed amount. Vergo integrates with every ERP and accounting software to sync approved amounts directly into your job cost structure without manual re-entry.

Why pay applications create AP complexity

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. Retainage must be coded separately from the standard payable, often to a dedicated retainage payable account per job. Lien waiver collection must be verified and matched before payment is released, and Schedule of Values alignment between the subcontract, the sub's pay app, and your job cost structure must be reconciled each billing period.

A practical example

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, and recovering it mid-project becomes a dispute. In contrast, 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. 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.

How Vergo handles this

Vergo is an AI-native, card-agnostic expense management platform that handles card spend, employee reimbursements, and AP invoices through one coding model. For construction teams, Vergo proposes coding by inference from your own accounting structure and job cost history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. Transactions are ready to code the moment they happen, and employees handle everything by text message — no app to download, no portal login. Vergo integrates with every ERP and accounting software, and connecting your existing cards involves no card applications, no re-issuing, and no banking change.

Related questions

• How do general contractors manage hundreds of vendor invoices per month?
• What is the cost of processing a single invoice manually in construction?
• How do I reduce the risk of vendor fraud in construction accounts payable?
• How do I integrate AP automation with Sage 300 for construction?