Do I need to fix the G703 if the G702 was rejected?

Often yes. If the G702 summary totals do not match the G703 continuation sheet, both documents need to be corrected together before resubmission.

Can a rejected G702 delay payment?

Yes. A rejected G702 commonly delays payment because the billing package usually cannot move forward until the corrected pay application is reviewed and accepted.

What should I check first after a pay app rejection?

Check the rejection note, compare the current pay app to the last approved billing, verify G702 and G703 totals, confirm retainage, review change order status, and make sure all required attachments are included.

Rejected Pay App G702 / G703 payment delay risk

GC Rejected My G702 — Now What?

Q: Why would a GC reject a G702?

A GC usually rejects a G702 because the math does not match the G703, retainage is wrong, prior billing changed, unapproved change orders were included, or required backup such as lien waivers is missing.

If a GC rejected your G702, do not assume the whole pay app is ruined. In most cases, the issue is fixable. The real problem is time: a rejected G702 can stall approval, delay payment, and create a messy billing trail if you revise the wrong numbers. This guide shows you what a rejection usually means, what to check first, how to fix it, and how to avoid the same problem next month.

Reality check: A rejected G702 usually delays payment because the billing package often cannot move forward until the corrected numbers, forms, and attachments are reviewed again. The faster you isolate the problem, the better your odds of keeping the delay short.

Quick links: Rejection Checklist · Common G702/G703 Errors · G702 Line-by-Line Explanation · G703 Instructions

What a Rejected G702 Usually Means

A rejected G702 does not automatically mean you were trying to overbill or that the entire project billing setup is broken. Most rejections happen because something in the pay app package does not line up cleanly enough for the GC, owner, architect, or lender to approve.

In practical terms, a rejection usually means one of three things:

The math on the G702 does not match the G703.
The billing package does not match the contract, approved change orders, or prior billing history.
Required backup documents are missing, incomplete, or inconsistent with the numbers shown.

That is why the smartest move is not to blindly “fix the form.” It is to figure out exactly which part of the billing package triggered the rejection.

Most Common Reasons a GC Rejects a G702

These are the issues that get flagged over and over on commercial pay applications:

1. G702 Totals Do Not Match the G703

This is probably the most common problem. If the continuation sheet totals do not roll up cleanly into the summary, the GC will often reject the package immediately.

2. Retainage Is Wrong

The retainage rate may not match the contract, the project phase, or the line-item math. Even small retainage errors can trigger a rejection because they affect payment due.

3. Prior Billing Changed

If previous billed amounts suddenly shift from what was approved last month, reviewers will want an explanation. Quietly changing history is a fast way to get kicked back.

4. Unapproved Change Orders Were Included

Billing pending change orders as if they are approved is one of the easiest ways to get flagged. If the change is not approved, it usually should not be in the official pay app totals.

5. SOV Does Not Match the Contract

If your Schedule of Values line items do not match the contract structure the GC expects, approval gets harder and rejection gets more likely.

6. Missing Backup Documents

Missing lien waivers, stored materials support, CO backup, or compliance documents can hold up the entire billing package even if the math is fine.

What to Check Immediately After the Rejection

Before you touch a single number, do this in order:

Read the rejection note carefully. Sometimes the reviewer tells you exactly what is wrong. Do not skip this and start guessing.
Pull the last approved pay app. Compare the current G702 and G703 to the previous approved billing. This is the fastest way to spot changes that should not have happened.
Reconcile G702 to G703. Make sure the continuation sheet totals roll up correctly into the summary page.
Verify retainage. Check the contract rate, any partial retainage release terms, and how retainage is being applied.
Review change order status. Confirm that only approved change orders are affecting official contract totals.
Confirm attachments. Make sure required waivers, supplier backup, and supporting docs are actually included.

Best practice: treat a rejection like a reconciliation exercise, not a rewriting exercise. Your goal is to identify the mismatch, not to “clean up” the whole billing package in ways that create new problems.

Step-by-Step: How to Fix a Rejected G702

Once you know where the issue is likely coming from, use a clean process:

1. Isolate Whether the Problem Is on the G702, G703, or Both

Sometimes the summary page is wrong. Sometimes the continuation sheet is wrong. Very often, both are off because one pulls from the other. Fixing the G702 alone without reconciling the G703 usually does not solve much.

2. Confirm Contract Totals

Recheck the Original Contract Sum, Net Change by Change Orders, and Contract Sum to Date. If any of those are wrong, the rest of the pay app can fall apart.

3. Recheck Previous Billing

Prior approved billing history should usually stay locked. If previous billed amounts changed, confirm exactly why. If there is no valid reason, restore the approved values.

4. Recheck Current Period Work and Stored Materials

Review work completed this period, any stored materials, and percentage-complete assumptions. Make sure what you are billing aligns with actual progress and available backup.

5. Recalculate Retainage

Retainage errors are common because different projects handle it differently. Some use a flat rate, some reduce retainage after a milestone, and some treat stored materials differently. Check the actual contract language before revising.

6. Rebuild the Final Payment Due

Once contract totals, prior billing, current billing, and retainage are all confirmed, recheck the final payment due. If that number is wrong, the reviewer will likely reject again.

7. Resubmit With a Short, Clear Explanation

Do not just send a revised PDF with no context. A short note helps the reviewer see that you fixed the issue intentionally. Something as simple as:

“We revised the pay app to correct the retainage calculation and updated the continuation totals so the G703 matches the G702 summary. Updated lien waiver and backup are attached.”

What Not to Change When Revising a Rejected G702

When contractors are under pressure, the temptation is to “clean everything up” while revising. That often makes things worse.

Do not casually change prior approved billing.
Do not rebalance the SOV unless there is a valid, documented reason.
Do not include pending change orders as if they are approved.
Do not guess at retainage treatment.
Do not resubmit the same bad package hoping a different reviewer will accept it.

On construction billing, stability matters. Reviewers are looking for clean math and consistent history. Unexplained changes from one billing period to the next make trust worse, not better.

G702 Rejected, G703 Wrong, or Both?

A lot of contractors say “my G702 got rejected” when the real issue is somewhere else in the package.

Problem	What It Usually Means
G702 payment due looks wrong	Check contract totals, prior billing, retainage, and current period math
G702 does not match G703	Continuation sheet totals or line-item math likely need correction
Reviewer says retainage is off	Contract rate, billing phase, or stored materials treatment may be wrong
Reviewer flags unsupported billing	Missing waivers, missing CO support, or weak stored materials documentation
Reviewer says prior billing changed	Historical billing values may have shifted between periods

That is why it helps to think in terms of the entire pay application package, not just the one-page summary.

Will a Rejected G702 Delay Payment?

Usually, yes. The exact delay depends on the project workflow, the billing calendar, and how fast the issue gets corrected. On some projects, a quick correction keeps things moving. On others, missing the approval window can push payment to the next cycle.

The bigger risk is not just the rejection itself. It is losing time while trying to figure out what changed, resubmitting the wrong version, or sending incomplete backup again.

Translation: a one-hour fix can become a two-week delay if you revise the wrong numbers or miss the project’s internal review cutoff.

How to Avoid the Same Rejection Next Month

Keep your billing history stable once a pay app is approved.
Use a consistent Schedule of Values structure each month.
Track approved and pending change orders separately.
Check retainage rules against the actual contract before billing.
Collect waivers and backup documents before submission day.
Use a workflow or software that reduces manual calculation mistakes.
Submit early enough that you still have time to correct issues before cutoff.

How PayAppPro Helps Reduce G702 Rejections

A lot of rejected pay apps happen because contractors are piecing together billing in spreadsheets, editing old PDFs, or manually carrying forward numbers from prior periods. That is exactly where avoidable inconsistencies creep in.

PayAppPro is built to make AIA-style billing cleaner and easier to review. It helps contractors:

Keep prior billing history consistent from one pay app to the next
Track line-item billing through a structured SOV workflow
Handle retainage and progress billing with less manual recalculation
Generate clean G702-style and G703-style outputs
Attach supporting documents such as lien waivers and backup

Bottom line: the cleaner your billing workflow, the fewer surprises you have at review time.

Frequently Asked Questions

Why would a GC reject a G702?

Usually because the numbers do not reconcile, retainage is off, prior billing changed, unsupported change orders were included, or required documents are missing.

Do I need to fix the G703 too?

Often yes. If the G703 totals do not support the G702 summary, both need to be corrected together.

Should I resubmit the same form again?

No. If the reviewer marked it rejected, sending the same version back usually just creates another rejection. Revise the actual issue first.

Can retainage alone cause a rejection?

Absolutely. Retainage affects payment due, so even a small retainage mismatch can be enough to kick the pay app back.

What if I am not sure what changed?

Start by comparing the rejected pay app to the last approved one. That usually reveals where the history drifted or where a total no longer matches.

Related Guides

Create Cleaner AIA-Style Pay Apps

Reduce math mistakes, keep billing history consistent, and avoid preventable rejections.

PayAppPro generates AIA-style billing outputs and is not affiliated with or endorsed by the AIA. AIA®, G702®, and G703® are registered trademarks of the American Institute of Architects.