Example of a Rejected AIA-Style Pay Application
This example shows how a pay application can look reasonable at first glance but still get rejected because the billing package does not tie together.
The examples below are educational and use sample numbers only. They show common problems reviewers find in G702/G703-style billing packages: prior billing mismatches, retainage drift, pending change orders, missing stored material backup, and spreadsheet continuity errors.
Sample Rejection Summary
In this scenario, the subcontractor submitted Application #4 on a $250,000 contract. The current work is mostly valid, but several continuity problems make the package difficult for the GC to approve.
| Review Area | Submitted Value | Reviewer Issue | Likely Result |
|---|---|---|---|
| Prior billing | $84,500 | Previous approved application showed $82,000 | Returned for correction |
| Retainage | 5% on some lines, 10% on others | Contract requires 10% retainage | Retainage mismatch |
| Change orders | $12,000 added to contract | CO is pending, not approved | Contract value does not tie |
| Stored materials | $18,750 billed | No invoice, storage record, or photo backup attached | Backup requested |
Example 1: Prior Billing Continuity Error
Prior billing is one of the first things reviewers check. If last month’s approved amount was $82,000, this month’s “previously billed” value should not suddenly become $84,500 unless there is a clear explanation.
Submitted incorrectly
- Previous approved billing: $82,000
- Current application prior billing: $84,500
- No change explanation included
Corrected approach
- Use the exact prior approved total
- Explain any approved adjustment
- Keep continuation sheet history consistent
This is why billing continuity matters. A copied spreadsheet can accidentally change a previously approved value and create a rejection even when the current work is legitimate.
Example 2: Retainage Mismatch
Retainage errors can be small enough to miss but large enough to stop approval. In this example, the spreadsheet used 10% retainage on the original SOV lines but 5% on a manually added line.
Retainage should follow the contract and stay consistent across the pay application unless the contract allows a release or adjustment. Review retainage in construction before changing retained amounts manually.
Example 3: Pending Change Order Included Incorrectly
A pending change order may represent real work, but that does not mean it belongs in the approved contract value. In this example, a $12,000 pending CO was included in the current contract total before approval.
| Change Order | Status | Submitted Treatment | Reviewer Response |
|---|---|---|---|
| Added branch circuit work | Pending | Included in contract value | Rejected until approved |
See how to bill change orders on G702/G703-style pay applications for a cleaner workflow.
Example 4: Stored Materials Missing Documentation
Stored materials often require more support than a line item on the continuation sheet. Reviewers may want invoices, delivery records, photos, storage location details, insurance information, or other backup.
Weak package
- $18,750 billed as stored materials
- No invoice attached
- No storage location listed
- No photo or delivery backup
Better package
- Invoice attached
- Storage location identified
- Delivery or receiving record included
- Photos or backup organized by SOV line
For details, see how to bill stored materials on AIA-style pay applications.
How Contractors Prevent These Rejections
Most rejected pay applications are not caused by one bad number. They are caused by billing history that no longer lines up. Prior billing, retainage, stored materials, approved change orders, and current amounts all need to support each other.
PayAppPro helps contractors keep the billing record organized so each month’s pay application starts from the prior project history instead of a copied spreadsheet.