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.
Short on time?
Start with the printable checklist, then use the “fix rejected pay app” guide if you already got kicked back.
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.)
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
FAQ
Quick answers for common “why did they reject this?” moments.
Related Guides
- Why pay applications get rejected
- How to fix a rejected pay application
- AIA G702/G703 rejection checklist
- Common G702/G703 errors to avoid
- How to fill out AIA-style G702 & G703
Want fewer “please revise and resubmit” emails?
Build the SOV once, carry forward automatically, and export a clean AIA-style package each billing period.