How do I track subcontractor pay applications in my AP system?
Vergo automates subcontractor pay application tracking by coding each G702/G703 with inference from your own accounting structure and syncing directly to your ERP. Traditional workflows require logging each pay app against its subcontract, validating line items against the approved schedule of values, calculating retainage, collecting lien waivers, routing for field approval, and posting to job cost codes.
Key takeaways
- Subcontractor pay applications require matching to approved schedules of values, prior billing history, and retainage terms — workflows standard AP systems don't support.
- Each pay app should be logged with a unique number tied to the subcontract, validated against cumulative billings, and posted at the cost code level in your ERP.
- Retainage must be calculated at the line level and tracked in a separate liability account to avoid reconciliation problems at project close-out.
- Lien waiver collection — conditional for the current period, unconditional for the prior — should be a hard gate before payment release.
- Field approval by the project manager confirms percentage complete against observed work before the pay app enters your accounting system.
- Vergo automates this workflow with inference-based coding and direct ERP sync, so subcontractor pay applications are matched to the correct job, phase, and cost code on first sight with no rule library to build.
Why pay application tracking breaks down in construction AP
Most AP systems are built for commodity invoices: a vendor sends a bill, you match it to a PO, you pay it. Subcontractor pay applications don't fit this model because a G702/G703 is a progress billing document tied to a schedule of values, a subcontract, prior payment history, and retainage terms. Standard AP workflows lack the structure to account for these elements, so AP teams often track pay applications in spreadsheets alongside their ERP, creating a dual-entry problem that leads to errors, delays, and disputes at project close-out. Pay apps entered as flat invoices make overbilling hard to catch, retainage gets calculated manually or inconsistently, and prior billings go unvalidated because cumulative-to-date figures aren't cross-referenced against historical records.
The recommended workflow for tracking subcontractor pay applications
Start by assigning each incoming G702/G703 a unique pay app number tied to the subcontract ID in your system and logging the submission date, which starts the clock on review and payment windows. The AP manager or project accountant then validates the billing period, subcontract value, and confirms that no line item exceeds the approved schedule of values amount for that trade, flagging any line where billed-to-date percentage exceeds work-in-place percentage. Pull the cumulative payment history for that subcontract and confirm that the current application's prior billings column matches your records exactly. Calculate retainage based on the contractual rate and confirm it's been applied correctly at the line level. Before routing for approval, collect required compliance documents: conditional lien waiver for the current period, unconditional lien waiver for the prior period, and any insurance certificates or certified payroll required by the prime contract.
Field approval and ERP posting
Send the validated pay app to the project manager or superintendent for field verification. They confirm percentage complete per cost code against the current schedule and site observations, providing a dated, documented approval. Once approved, post the amount to the correct job, phase, and cost code in your accounting system. Enter retainage held as a separate line item to a retainage payable account — do not combine multiple pay apps into a single invoice entry. Vergo handles this by coding AP invoices by inference from your own accounting structure and history, so subcontractor pay applications are matched to the correct job, phase, and cost code on first sight with no rule library to build, and every coding shows why it was chosen so a reviewer confirms in seconds instead of re-coding by hand. After the check run or ACH is processed, mark the pay app as paid, record the payment date and check number, and update the cumulative billed-to-date total on the subcontract record. This line-level posting discipline ensures accurate job costing and clean reconciliation at project close-out.
Best practices for construction AP teams
Maintain a pay app log by subcontract showing submission date, approved amount, retainage withheld, payment date, and cumulative totals — this prevents disputes and gives project managers on-demand status visibility. Never pay without a lien waiver exchange: conditional waivers for the current period and unconditional waivers for the prior period should be a hard gate, not a best practice. Set up retainage payable as a separate liability account per job, because commingling retainage with standard AP balances creates reconciliation problems at project close-out and makes retainage release tracking unreliable. Require schedule of values line-item detail on every submission — a pay app submitted as a lump sum gives you no basis for reviewing percentage complete by trade or cost code, so require the G703 continuation sheet every time.
How Vergo handles this
Vergo codes AP invoices by inference from your own accounting structure and history, so subcontractor pay applications are matched to the correct job, phase, and cost code on first sight with no rule library to build. 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 once they clear, they sync into your accounting or ERP software. Card spend, employee reimbursements, and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use. Vergo integrates with every ERP and accounting software. See how it works at getvergo.com/products/ap-invoices.
Related questions
Frequently Asked Questions
What is the difference between a subcontractor pay application and a standard AP invoice?
A standard invoice documents a completed transaction. A subcontractor pay application is a progress billing request tied to a schedule of values, showing work completed to date, prior billings, retainage withheld, and the net amount due. It requires validation against a subcontract, not just a purchase order, before any payment is authorized.
How should retainage be tracked in the AP system for subcontractor pay apps?
Retainage should be posted to a dedicated retainage payable liability account, broken out by job and subcontract. Never net retainage against the invoice amount and post only the payment. Keeping retainage as a separate payable ensures accurate job cost reporting and makes retainage release auditable at project close-out.
What should happen if a subcontractor's pay app amounts don't match the prior billing history?
Reject or hold the pay application immediately and request a corrected submission. Discrepancies in cumulative billed-to-date figures are a leading indicator of overbilling. Document the discrepancy in your pay app log, notify the PM, and do not route the application for approval until the subcontractor reconciles the variance in writing.
How often should subcontractor pay applications be processed in a typical construction billing cycle?
Most construction projects run monthly pay application cycles tied to a contractual billing cutoff date, often the 25th or last day of the month. GCs then have a defined review window — typically 7 to 14 days — before payment is due under the subcontract. Consistent cycle dates reduce administrative backlog and improve cash flow predictability for both parties.
Can Vergo handle pay applications that include stored materials or equipment not yet installed?
Yes. Vergo supports stored materials line items on G703 submissions, allowing AP teams to track materials billed but not yet incorporated into the work. These line items are flagged for PM verification and can be configured to require supporting documentation — such as a bill of lading or stored materials listing — before approval is permitted.
What compliance documents should be required before approving a subcontractor pay application?
At minimum, require a conditional lien waiver for the current billing period and an unconditional lien waiver for the prior paid period. Depending on project type, you may also need certified payroll, proof of insurance, and OCIP enrollment confirmation. Treating these as hard approval gates — not optional — protects the owner and GC from downstream lien exposure.