GC Rejected Your G702/G703? What to Check Next
A rejected pay application is more than a paperwork nuisance. It can delay cash flow, trigger another round of project manager questions, and force your accounting team to rebuild the billing story under pressure.
Most G702/G703-style pay applications get rejected because the numbers do not tie out, retainage was handled inconsistently, the continuation sheet does not support the summary, or required backup is missing.
Before revising the package, review how general contractors review pay applications so you understand what the GC is trying to verify.
Why Rejections Hurt More Than They Should
When a GC kicks back a pay application, the official reason may be short: “doesn’t tie,” “retainage is off,” “missing backup,” or “revise and resubmit.” That does not always tell you where the problem started.
The real issue is often billing continuity. Prior work, current work, stored materials, retainage, approved change orders, and the current amount due all need to carry forward cleanly from one billing period to the next. When spreadsheets are copied, edited, or manually adjusted month after month, small mistakes can become rejection-level problems.
If you are still working through the broader construction payment application process, this page focuses specifically on what to check after a rejection and how to prevent the same issue next month.
Common Reasons G702/G703 Pay Apps Get Rejected
Most rejections fall into a few predictable categories. Start here before changing random numbers.
1. Summary and Detail Do Not Match
The G702-style summary must be supported by the G703-style line-item detail. If totals, prior payments, or current amounts do not reconcile, the reviewer may stop there.
Related: G702 vs G703 differences
2. Retainage Is Wrong
Retainage mismatches are one of the fastest ways to trigger a rejection. Reviewers compare current retainage against contract terms and prior approved billing.
Related: retainage in construction
3. Prior Billing Changed
If last month’s approved numbers do not match this month’s prior-to-date values, the reviewer has to figure out why. That usually means delays.
Related: pay app review workflow
4. Stored Materials Lack Backup
Stored materials may be allowed, but they usually need documentation. Missing invoices, photos, storage details, or approval support can cause a pay app to come back.
Related: stored materials billing
5. Pending Change Orders Were Billed as Approved
Reviewers usually separate approved change orders from pending or disputed work. If the contract sum includes unapproved work, the package may be rejected.
Related: approved vs pending change orders
6. Spreadsheet Formulas Broke
A copied spreadsheet may look fine until a hidden formula, linked cell, or manually typed value changes the billing history. Reviewers do not care why it happened. They care whether the package ties.
Related: AIA billing software
What to Check Before You Resubmit
Do not just fix the line item the GC mentioned and send the file back. Check the whole package. A reviewer who finds one issue often looks more closely at the rest of the submission.
Check the summary
- Original contract sum
- Approved change orders
- Current contract sum
- Total completed and stored to date
- Total retainage
- Previous payments
- Current amount due
Check the continuation sheet
- Line-item scheduled values
- Work completed from previous applications
- Work completed this period
- Stored materials
- Percent complete
- Balance to finish
- Line-item retainage, if applicable
How to Prevent Future Pay Application Rejections
The best way to prevent rejected pay applications is to protect the billing history. Every pay period should build from the last approved pay application, not from a freshly copied spreadsheet that may or may not carry the same formulas forward.
Keep one source of truth
The SOV, prior billing, retainage, stored materials, and approved change orders should all roll forward from the same controlled project record.
Separate approved and pending work
Do not bury pending change orders inside the contract total. Reviewers usually want clean separation until the work is officially approved.
Review retainage every period
Retainage should match the contract and prior approved history. A small retainage change can throw off the entire current amount due.
Check backup before submission
Stored materials, lien waivers, change orders, and requested backup should be attached before the package reaches the GC reviewer.
This is where structured billing software can help. PayAppPro keeps the SOV, prior billing, retainage, stored materials, approved change orders, and AIA-style output tied together so each month’s package is not rebuilt from scratch.
See how AIA billing software helps reduce continuity mistakes, or review the QuickBooks Online integration for AIA billing if your accounting workflow also needs to stay aligned.
Example: A Retainage Mismatch That Delays Payment
A subcontractor submits a $92,000 current payment request. The work completed this period is accurate, but the spreadsheet calculates retainage at 5%. The contract and prior approved applications used 10%.
The GC reviewer sees that total retainage no longer matches prior billing history. Now the current amount due is wrong, the balance to finish may be wrong, and the owner billing package cannot be finalized until the subcontractor corrects the pay app.
That is the problem with many rejections. The work may be valid, but the billing package does not prove it cleanly enough for approval.
Recommended Next Steps
If your pay application was rejected, start with the issue the GC flagged, then follow the surrounding workflow. Rejections usually point to a larger continuity problem.
Understand the GC review process
Learn what reviewers check before approving or kicking back a pay application.
How GCs review pay applicationsFix retainage problems
Review how retainage affects balances, prior billing, and current amount due.
Retainage in constructionCheck summary vs detail
Understand how G702-style summaries and G703-style continuation sheets support each other.
G702 vs G703 differencesReview stored materials
Make sure stored material billing has the right support before resubmitting.
Stored materials billingMove away from fragile spreadsheets
See how PayAppPro helps maintain billing continuity across pay periods.
Explore AIA billing softwareConnect accounting workflow
Keep pay application and invoice workflows easier to reconcile.
QuickBooks Online integrationFrequently Asked Questions
Stop Rebuilding Rejected Pay Apps From Fragile Spreadsheets
PayAppPro helps contractors prepare cleaner AIA-style pay applications with SOV, retainage, stored materials, approved change orders, and billing history tied together.
Create an AIA-Style Pay App See AIA Billing Software