How to Avoid Pay Application Rejections

The easiest pay application to fix is the one that never gets rejected. Use this contractor checklist to catch the issues that get G702/G703-style pay apps kicked back: mismatched totals, SOV drift, retainage mistakes, stored materials confusion, and missing docs.

PayAppPro generates AIA-style pay application outputs and does not provide official AIA Contract Documents. AIA®, G702® and G703® are registered trademarks of the American Institute of Architects. Official AIA Contract Documents are offered by ACD Operations, LLC.

Short on time?

Start with the printable checklist, then use the “fix rejected pay app” guide if you already got kicked back.

Reality check: “Resubmit and hope” is not a strategy. Reviewers will reject the same issue again if you didn’t fix the root cause.

1) Start With the Contract (Not the Form)

Most pay app problems begin before billing even starts. Confirm what the contract (or GC billing packet) requires:

  • Whether they expect G702/G703-style billing or a different template
  • An approved Schedule of Values (SOV) format
  • Retainage percentage and any special retainage rules
  • Stored materials rules and documentation expectations
  • Monthly backup docs (waivers, invoices, certified payroll, etc.)
Pro tip: If you don’t know what format they want, ask: “Do you want an AIA G702/G703-style package with a Schedule of Values, or a standard progress invoice?” (This alone prevents a lot of avoidable kickbacks.)

2) Lock the Schedule of Values Early

Once the SOV is approved, treat it as your “source of truth”:

  • No new line items without approval
  • No shifting values between categories to “make it work”
  • Descriptions should mirror the contract scope
  • Line numbers should stay stable month-to-month

If you need help structuring it, see: How to create a Schedule of Values template.

3) Make the G702 Summary Tie Exactly to the G703 Totals

This is the #1 rejection driver. Before you submit, confirm:

Tie-out checks

  • G702 totals match the G703/SOV totals exactly
  • Previous period values didn’t change
  • Contract sum to date includes approved change orders
  • Balance-to-finish math is consistent

If you’re in spreadsheets…

  • Watch for broken ranges after inserts/deletes
  • Watch for “copied” formulas that reference the wrong row
  • Don’t retype prior period numbers (carry them forward)

4) Retainage Has to Be Consistent

Retainage mistakes are sneaky because the numbers can “look close” while still being wrong. Make sure:

  • The retainage percentage matches the contract
  • Retainage is applied consistently to the same base (completed/stored) every period
  • You’re not accidentally retaining twice (line retainage + summary retainage)

Need a refresher? What is retainage in construction?

5) Stored Materials: Document It and Make It Move

Stored materials are a common rejection trigger because reviewers worry about double-counting. To avoid that:

  • Keep stored materials separate from installed work
  • Attach invoices/receipts and any required proof of storage/insurance
  • As materials are installed, stored amounts should decrease while work-in-place increases

More detail here: How to bill stored materials

6) Change Orders: Only Bill Approved Ones

If you bill unapproved change orders, you’re basically volunteering for a rejection. Keep it clean:

  • Only include signed/approved change orders in the contract sum to date
  • Reference CO numbers clearly (and match the signed values)
  • Update the SOV if the GC requires COs as separate line items

7) Attach the “Always Missing” Docs

Many pay apps are “right” but still rejected because the package is incomplete. Before you send:

  • Lien waivers (correct type + correct amount)
  • Supplier invoices (especially for stored materials)
  • Approved change orders and backup
  • Certified payroll (if required)
  • Any GC/owner/lender-specific forms for that month
If you want a tighter “before you submit” version of this page, use: AIA G702/G703 rejection checklist.

FAQ

Quick answers for common “why did they reject this?” moments.

Most rejections come from a few repeat problems: G702 totals not matching the G703/SOV, previous amounts changing, retainage math being inconsistent, missing change order updates, and missing backup documents like lien waivers or stored-material invoices.

Treat the approved Schedule of Values as your source of truth, keep previous-period numbers locked, and confirm the G702 summary ties exactly to the G703 totals before you submit.

It depends on your contract. Many projects accept an AIA-style format as long as the structure and math match what the reviewer expects. PayAppPro produces AIA-style pay application outputs and does not provide official AIA Contract Documents.

Stored materials should be clearly documented and should move (reduce) as materials are installed. If stored amounts never change while work-in-place increases, reviewers often flag it as double-counting risk.

The usual culprits are lien waivers (correct type and amount), supplier invoices for stored materials, change order approvals, certified payroll on public jobs, and any project-specific forms required by the GC/owner/lender.
Create a Pay App That Gets Approved
Want the full “rejection-proof” flow? See AIA billing software.

Related Guides

Want fewer “please revise and resubmit” emails?

Build the SOV once, carry forward automatically, and export a clean AIA-style package each billing period.