Why Pay Applications Get Rejected

What Does It Mean When a Pay Application Is Rejected?

A rejected pay application means the reviewer (GC, owner, architect, or lender) found an issue serious enough that they won’t approve payment until it’s corrected. Sometimes this is a formal rejection. Other times it shows up as a “please revise and resubmit.”

Either way, rejections slow cash flow, create extra admin work, and often push payment into the next cycle.

The Most Common Reasons Pay Applications Get Rejected

1. Math Errors on G702 or G703

This is the #1 reason pay apps get rejected. Totals don’t tie out, retainage is calculated incorrectly, or the G702 summary doesn’t match the G703 continuation sheet.

These mistakes usually come from manual spreadsheets, copy-paste errors, or last-minute edits right before submission.

2. Schedule of Values (SOV) Doesn’t Match the Contract

If your billing lines don’t align with the approved Schedule of Values, the pay app will almost always be rejected.

• Line items added without approval
• Values shifted between categories
• Work billed under the wrong cost code

Once an SOV is approved, it becomes the rulebook for billing.

3. Change Orders Not Properly Included

Approved change orders must be reflected correctly in both the SOV and the pay application totals. Common issues include:

• Billing CO work before it’s approved
• Forgetting to add approved COs to the SOV
• Incorrect CO values or references

If you’re unsure how change orders should flow into your contract sum and line-item detail, see our guide on how to bill change orders on AIA G702/G703 .

4. Missing Backup or Required Documents

Many GCs require attachments with every pay app. Missing any of these can trigger rejection:

• Lien waivers
• Certified payroll (where applicable)
• Supplier invoices or receipts
• Change order approvals

5. Stored Materials Billed Incorrectly

Stored materials are one of the fastest ways to get rejected if they’re not documented correctly. Many contracts require:

• Proof of purchase
• Photos of materials on site or in approved storage
• Separate line items on the G703

6. Retainage Calculated Wrong

Even small retainage mistakes get flagged. Retainage must match the contract percentage and be applied consistently to both current and total billing.

A Real Rejection Example (Walked Through)

The reasons above are easier to understand with a real package in front of you. Here is a realistic scenario: a subcontractor submits Application #4 on a $250,000 contract. The current work is legitimate, but several continuity problems make the package difficult for the GC to approve.

The reviewer’s summary

Example 1: Prior billing continuity error

Prior billing is one of the first things a reviewer checks. If last month’s approved amount was $82,000, this month’s “previously billed” value should not suddenly become $84,500 without a clear explanation.

This is why billing continuity matters. A copied spreadsheet can quietly change a previously approved value and trigger a rejection even when the current period’s work is entirely legitimate.

Example 2: Retainage mismatch

Retainage errors can be small enough to miss but large enough to stop approval. Here, the spreadsheet applied 10% retainage to the original SOV lines but 5% to a manually added line.

Retainage should follow the contract and stay consistent across the whole application unless the contract allows a release or adjustment. See how to calculate retainage on G702/G703 before changing retained amounts manually.

Example 3: Pending change order included too early

A pending change order may represent real work, but that does not mean it belongs in the approved contract value yet. In this example a $12,000 pending CO was folded into the current contract total before approval.

See how to bill change orders on G702/G703 for the cleaner workflow.

Example 4: Stored materials without documentation

Stored materials usually require more support than a line item on the continuation sheet. Reviewers may want invoices, delivery records, photos, storage location details, and insurance information.

For the full backup checklist, see how to bill stored materials on G702/G703.

Why Excel Templates Cause So Many Rejections

Excel templates work—until they don’t. As projects evolve, spreadsheets become fragile:

• Formulas break
• Totals drift
• Previous billing gets overwritten

That’s why many GCs quietly distrust spreadsheet-based pay apps.

How to Avoid Pay Application Rejections

Contractors who avoid rejections usually do a few things consistently:

• Lock the SOV early and keep it consistent
• Track previous, current, and total billing accurately
• Include required documents every billing cycle
• Use tools that mirror AIA G702/G703 logic

How PayAppPro Helps Prevent Rejected Pay Apps

PayAppPro is designed specifically to reduce pay app rejections by:

• Automatically tying pay apps totals to line items
• Preventing math and retainage errors
• Keeping SOVs consistent month to month
• Generating accurate, GC-ready PDF pay applications
• Supporting lien waivers and backup attachments