Pay Application Review
Audit an AIA G702/G703 pay application. Catches progress-billing overstatements, stored-material irregularities, retainage math errors, lien-waiver gaps, back-charge problems, and premature retention-release requests.
What it does
Pay App Review reads a current pay application (typically AIA G702 summary + G703 schedule-of-values detail) plus any previous approved applications. It applies ~10 audit checks — progress-billing validation, stored-materials verification, prompt-payment compliance, lien-waiver check, back-charge analysis, retainage parameterization (not a one-size-fits-all threshold), cost-code consistency, multi-currency, billing-period alignment, budget vs actual — and produces a recommended payment amount with flagged line items.
When to use it
- Monthly pay-app review workflow — standard audit before approving a payment.
- End-of-project final pay app — retention release + completeness checks.
- Sub-side: self-auditing your own pay app before submitting, to catch obvious issues.
What to upload
- Current pay application — G702 + G703, or equivalent format
- Previous approved certifications (optional but strongly recommended — they anchor the retainage parameters and progress baseline)
Step by step
Open the engine
Sidebar → Engines → Pay App Review.
Upload current pay app
G702/G703 in PDF or XLSX.
Upload previous approvals
Optional but changes the quality of the audit significantly — without history, the engine can't detect period-over-period irregularities.
Run
40–90 seconds.
Read the recommended payment
Top: recommended amount vs requested amount, potential savings, retainage withheld.
Review line-item statuses
Filter by status. SUPPORTED / UNSUPPORTED / DUPLICATE / OVERBILLED / PARTIAL.
Check audit sections
Each of the 10 audit areas has its own block with findings or an "all clear" note.
Understanding the results
Requested payment vs recommended payment. Delta is potential savings or withholdings.
Dollar amount currently held. Retainage % is parameterized from the contract, not assumed — engine reads the rate from the pay app/contract rather than applying a universal 10%/5% rule.
Each SOV line with current-period claim, % complete, status flag, note.
Progress billing validation, stored materials, prompt payment, lien waivers, back charges, retainage rate validation, joint checks, cost codes, multi-currency, billing period alignment, retention release.
If the pay app exceeds the model's context window — split by division or vendor and run separately.
Every control, explained
Run analysisOne run.
Try with sample dataBridgeport Pay App #1 — $2.8M request with 3 flagged issues.
Filter by statusOverbilled / Unsupported / Duplicate / Partial / Supported / All.
Expand audit sectionClick any audit heading to see full findings.
Export PDFAP-ready audit memo including recommended payment and all findings.
Export XLSXRaw SOV + flag data.
Chains
Chains into
Chained from
Exports
- PDF — audit memo with recommended payment and findings per audit section.
- XLSX — raw SOV data with flag columns.
- CSV — flat finding list.
Troubleshooting
The engine reads retainage from the documents uploaded. If the contract retainage rate isn't visible in the pay app or previous certifications, upload the contract too or use chat: "This contract is flat 5% retainage — recompute."
Stored-materials irregularities require backup documentation — if invoices/bills-of-lading aren't uploaded with the pay app, the engine conservatively flags them as unsupported. Upload the backup.
Split by sub and run separately, then sum.