G702 overview G703 overview Rejection checklist

How to Fix a Rejected Pay Application

Getting a pay app rejected is annoying — but it’s almost always fixable. The trick is to fix the one underlying mismatch that triggered the rejection (instead of changing five other things and making it worse).

Quick reality check (AIA-style note)
This page explains common construction billing workflows and AIA-style concepts. PayAppPro generates AIA-style outputs and is not affiliated with or endorsed by the American Institute of Architects (AIA). AIA®, G702® and G703® are registered trademarks of the AIA. Official AIA Contract Documents are offered by ACD Operations, LLC.
Important: Don’t just “resubmit and hope.” If the root issue isn’t fixed correctly, you’ll usually get rejected again — plus your reviewer will start side-eyeing everything.

Quick Diagnosis: What kind of rejection is it?

Most rejections fall into one of these buckets. Pick the closest match and follow that path.

1) Totals don’t tie (G702 vs G703/SOV)
Most common. Usually a roll-forward or spreadsheet formula issue.
2) SOV isn’t the approved version
Line descriptions/values changed, lines re-ordered, or new lines added without approval.
3) Retainage handled inconsistently
Percent differs from contract, applied differently across lines, or changed midstream without explanation.
4) Stored materials issues
Stored billed without backup, double-counted, or never backed out as materials are installed.
5) Missing documents / compliance attachments
Lien waivers, invoices, photos, CO approvals, certified payroll, etc.
Use the Rejection Checklist

What you should ask (if feedback is vague)

Send this to the reviewer/GC:

“Can you point to the exact line item or total that failed review, and what value you expected?”

This one question avoids the “guess-and-resubmit” loop.

Step 1: Identify the exact reason for rejection

Start with the rejection note. If it says “does not tie,” you’re hunting a math mismatch. If it says “not approved SOV,” you’re hunting an alignment/versions problem. If it says “missing backup,” you’re hunting attachments.

Pro tip: Before changing anything, download/save the rejected PDF and the previous approved pay app. You’ll use them to verify what should NOT change.

Step 2: Recheck summary vs detail totals (G702 must tie to G703)

If your workflow uses a G702-style summary and a G703-style continuation sheet, the summary totals must match the detail totals exactly. If you need a refresher: G702 overview and G703 overview.

  • Total completed & stored to date on the summary must equal the sum of your SOV line totals to date.
  • Retainage must be consistent (same percent/rule and same base).
  • Prior payments / previous certificates should match the last approved pay app.

If you’re in Excel, this is where broken ranges and hand-edited formulas usually live.

Step 3: Verify the SOV is the approved version

Reviewers expect the SOV structure to stay stable across billing periods. Compare your pay app’s SOV against the approved SOV:

  • No surprise new lines unless approved
  • No shifting dollars between categories to “make it work”
  • Descriptions match what the reviewer recognizes
  • Line numbering/order remains stable

If your SOV is messy, fix the foundation first: How to create an SOV template.

Step 4: Fix Change Order Billing (Only Approved COs)

Change orders should only hit the pay app if they’re fully approved. Many rejected pay applications trace back to unapproved or incorrectly reflected CO values. Make sure:

  • Values match the signed change order exactly
  • The contract sum to date reflects approved changes
  • Your SOV total equals the updated contract sum to date
  • CO line items are clearly labeled and traceable

If you're unsure how to reflect approved changes correctly in both the summary and continuation sheet, see our guide on how to bill change orders on G702/G703 .

Step 5: Stored materials—make sure they’re supported and not double-counted

Stored materials can be a rejection magnet. Typical fixes include:

  • Add required backup (supplier invoices, photos, releases, etc.)
  • Confirm stored values aren’t counted twice (stored should back out as installed work increases)
  • Confirm retainage rules for stored materials match the contract

Need the playbook? How to bill stored materials.

Step 6: Attach missing documents (this is the quiet killer)

Many rejections are simply “we’re missing the package.” Typical attachments include:

  • Lien waivers
  • Supplier/sub invoices (especially for stored materials)
  • Certified payroll (public work)
  • Signed change orders / approvals
  • Photos or delivery tickets (when required)

Step 7: Double-check retainage (percent + base + consistency)

Retainage issues are usually one of these:

  • Wrong retainage percentage vs the contract
  • Retainage applied to different bases month-to-month (completed only vs completed+stored)
  • Some lines have retainage and others don’t (without a documented reason)

Do NOT change these unless you have a documented reason

  • Prior-period totals (previous work / previous certificates)
  • SOV line order / numbering (reviewers compare period to period)
  • Retainage rules midstream (unless contract change is approved)

Preventing repeat rejections next month

Once you fix this month’s issue, lock in the process:

  • Use a stable SOV (single source of truth)
  • Lock prior-period values so they can’t drift
  • Track stored materials as “moving” (stored → installed)
  • Apply retainage consistently across periods
  • Run a pre-submit checklist every time
Related: Before you submit your next one, run the G702/G703 Rejection Checklist.
Build Pay Apps With Fewer “Tie-Out” Surprises

Keep the SOV stable, roll totals forward automatically, and export clean AIA-style PDFs.

FAQ: Fixing Rejected Pay Applications

Short answers for the “what do I change?” panic.

Start with the rejection note, then verify (1) summary totals tie to the detail/SOV totals, (2) prior-period values weren’t changed, (3) retainage is consistent, and (4) all required attachments are included. Fix the root mismatch before resubmitting.

The most common causes are totals that don’t tie between summary and detail, SOV line items not matching the approved version, retainage handled inconsistently, stored materials billed without backup or not backed out when installed, and missing documents like lien waivers.

Usually no. Prior-period values should generally remain unchanged. If something from a prior period was truly wrong, correct it in a documented way and tell the reviewer exactly what changed and why—otherwise you’ll trigger more questions and delays.

Ask for the exact line or total that failed review and what they expected instead. A simple question like “Which line item or total needs correction?” often saves days of guessing.

Use a stable SOV, lock prior-period numbers, keep stored materials and retainage rules consistent, and use a single source of truth for roll-forward totals so the summary always ties to detail.
Generate a Clean Pay App