Payment applications AIA-style G702/G703 SOV + retainage

Construction Payment Applications: Contractor Guide

Quick answer:

A construction payment application is a formal request for payment that shows what’s complete, what you’re billing this period, retainage withheld, and what’s left — usually driven by a Schedule of Values (SOV). Many teams submit in an AIA-style format (G702 summary + G703 continuation sheet).

PayAppPro outputs are AIA-style only and are not licensed AIA documents. AIA®, G702® and G703® are registered trademarks of the American Institute of Architects.

“Payment application” is just the formal way of saying: here’s what we’ve built so far, and here’s what we should get paid for this period. The problem is the details — SOV, stored materials, retainage, change orders, and the classic kickback: “your totals don’t tie.”

If you’re working in QuickBooks Online

Start here: Does QuickBooks do AIA billing (G702/G703)? Then see: Progress billing in QBO and Retainage in QBO.

What Is a Construction Payment Application?

A construction payment application (often shortened to pay app) is a structured billing package that shows exactly what you’ve earned so far and what you’re requesting for this billing period. Compared to a normal invoice, it’s built for review: the GC/owner can validate progress, retainage, and prior totals quickly.

On many commercial jobs, this is done using AIA-style documents — most commonly the G702-style summary and the G703-style continuation sheet. On other projects, the owner/GC may have a custom form or portal — but the core logic is the same.

Why Payment Applications Exist (Instead of Simple Invoices)

Owners, GCs, architects, and lenders want to approve payment based on a consistent financial story. A pay app format helps them answer four questions fast:

  • What’s the contract value right now? (original + approved change orders)
  • What’s complete to date? (by line item)
  • What’s being billed this period?
  • What’s the payment due after retainage?
Reality check: reviewers rarely “fix” your pay app. If the math or backup is unclear, it gets kicked back and your payment waits.

What to Include in a Construction Payment Application

Regardless of whether you’re using AIA-style billing, a GC template, or software, most pay applications include the same building blocks.

1) Project and contract information

  • Project name/address
  • Owner/GC entity names (match the contract)
  • Your company legal name (match W-9)
  • Original contract sum
  • Approved change orders to date

2) Schedule of Values (SOV)

Your Schedule of Values (SOV) is the backbone. It breaks the contract into line items with assigned dollar values. Each billing period, you update the same line items instead of “starting over.”

Need a starting point? Grab the free SOV template (Excel/PDF).

3) Work completed: previous, this period, and to-date totals

This is where progress billing becomes a rollforward problem. Reviewers expect last month’s “to date” to become this month’s “previous.” If it drifts, you’ll hear about it.

For the plain-English rollforward overview: Construction progress billing.

4) Stored materials (if allowed)

Stored materials can help cash flow, but it’s also where reviewers ask for backup: invoices/receipts, photos, storage location, and sometimes insurance. Track it by SOV line and reduce stored amounts as materials are installed.

See: How to bill stored materials on AIA-style G702/G703.

5) Retainage

Retainage is usually 5–10% and must be applied consistently. Some projects treat retainage differently for stored materials vs work in place — your pay app needs to reflect the contract rule.

6) Change orders

Approved change orders affect the contract sum and the SOV. If your CO log and your pay app disagree, your review slows down. Update the SOV as soon as changes are approved so the pay app stays reconcilable.

7) Lien waivers and backup documents

Many pay apps aren’t “complete” until the waiver packet and backups are attached. Common items:

  • Lien waivers (conditional/unconditional)
  • Stored materials backup
  • Change order approvals
  • Any owner/GC required forms

How AIA-Style G702 & G703 Fit In

In an AIA-style workflow:

  • G703-style continuation sheet = the SOV + line-item math
  • G702-style summary = totals, retainage, prior payments, and amount due
  • Backups (COs, waivers, stored material docs) ride along as the submission packet
Want a read-only reference? View a completed AIA-style G702/G703 example (educational sample; no login).

Common Reasons Pay Applications Get Rejected

  • G702 summary doesn’t match the G703/SOV totals
  • SOV total doesn’t match the current contract sum (including approved COs)
  • Line items exceed scheduled values
  • Stored materials billed without backup (or never reduced when installed)
  • Retainage handled inconsistently across periods
  • Lien waiver amounts don’t match the application/payment history

Full checklist: Common G702/G703 errors (and how to avoid them).

How QuickBooks Online Fits (without pretending it’s a pay app tool)

QBO is great for accounting and AR — but it doesn’t natively generate an AIA-style pay application package. The simplest workflow most teams end up with is:

  1. Build the pay app package using an SOV-driven workflow
  2. Get it approved
  3. Mirror the approved totals into QBO (invoice/update) so AR stays accurate

Start here: Does QuickBooks do AIA billing (G702/G703)?


How PayAppPro Simplifies Payment Applications

You can run pay apps in spreadsheets — but month-to-month consistency is where spreadsheets quietly fail. PayAppPro is built to reduce the number of ways a pay app can drift:

  • Build your SOV once and reuse it every billing period
  • Keep G702 totals tied to G703/SOV math automatically
  • Track stored materials and retainage consistently
  • Organize backup docs per application (instead of scattered emails)
  • Generate AIA-style PDFs quickly (clean, reviewer-friendly)

FAQ: Construction Payment Applications

A construction payment application is a formal request for payment that shows completed work to date, what’s being billed this period, retainage withheld, and the remaining balance—often using an SOV and an AIA-style format.

Common attachments include lien waivers, change order approvals, stored material invoices/backup, and any project-specific forms required by the GC/owner.

Not always. Many projects accept AIA-style pay applications that follow the same structure, but you should confirm what your contract or GC/owner requires.

Most rejections happen when totals don’t tie out (G702 summary vs G703/SOV), retainage is inconsistent, change orders aren’t reflected, stored materials lack backup, or lien waivers don’t match the application amounts.

QuickBooks Online is strong for accounting and AR, but it doesn’t natively generate an AIA-style pay app package. Many teams use a pay app workflow for G702/G703-style presentation and mirror the approved totals into QBO.

Related Guides

Create Your Next Construction Payment Application

Build AIA-style pay apps, track stored materials and retainage, and keep totals tied out across billing periods.