Engine · Field · LIVE

Pay apps reconciled before you sign.

Pay App Review is the Trueleveler engine that reviews subcontractor pay applications (AIA G702/G703) against the project's schedule of values, work-completed %, and the procurement record. Flags over-billing, math errors, uninstalled material billed as installed, and retainage drift — each finding states its evidence.

Try it now

Pay App Review runs on a pay application (AIA G702/G703) and needs a free account (no card). It has no sample data yet, and the no-signup demo only levels bids.

Evidence
stated for each finding
5
finding categories
G702 / G703
native parse
$ + %
dual-tagged findings

See it run

A screen recording of Pay App Review on sample project data, with a voice-over and subtitles.

Transcript

See over-billing before you pay.

Add the pay app and schedule.

Pay App Review checks every line, to the cent.

One line is billed at sixty-two percent, only forty built.

01 · What it catches

The drift that compounds across pay periods.

Five categories cover the bulk of where pay-app review goes sideways. Each finding carries a severity tag, the dollar impact, the SOV row it ties to, and the recommended action.

CRITICAL · Over-billing

Sub bills 80% on framing. Schedule says 60%.

The pay app claims 80% completion on framing. Trueleveler pulls the master schedule's earned-value % and the daily log's framing crew counts. Both say ~60%. We flag the 20-point gap with the source data and propose a verified completion %.

CRITICAL · Uninstalled material

Steel billed as installed. Yard says delivered.

Procurement tracker shows the material was delivered May 8 but no install activity is logged. AIA allows billing for stored materials but at a separate line with proof of insurance — this is being billed as installed work. We surface the procurement record and the missing "stored materials" column.

DEVIATION · Math errors

Schedule of values doesn't sum to contract value

SOV line totals come to $1.84M; G702 contract value reads $1.86M. Retainage withheld doesn't match contract-spec retainage rate. Period addition off by $4,200 across two lines. We recompute every column and flag every cell that doesn't reconcile.

DEVIATION · Retainage drift

10% required. 7% withheld.

The subcontract calls for 10% retainage until 50% complete then 5% thereafter. This pay app withholds 7% on a 35% complete job. The vendor is asking you to release retainage you're contractually obligated to hold. Surfaced with the contract clause that controls.

NOTE · Materials on site

Stored-materials line item, no certificate

$84K of stored materials billed but no Certificate of Stored Materials attached. AIA G703 column F technically allows this with a separate proof-of-insurance docket. Flagged as "Approve with conditions: require COSM" for the PM to verify before signing.

NOTE · CO carryforward

Approved CO not reflected in SOV revision

CO-007 was approved last month for $34,200. This pay app's contract value still shows the original sum — the SOV wasn't updated. Sub may be billing against the old line structure. We surface the CO and the math correction.

02 · The review panel

Pay app submitted. Cross-checked. Annotated.

One screen. Left: the G702/G703 as the sub submitted it. Right: the findings the engine surfaced, severity-tagged with dollar impact and the evidence behind each.

Pay App Review result for Application No. 07 recommending approve-with-conditions and a $120,680 reduction, with flagged overbilling and stored-material lines, each carrying evidence and a recommended action
Pay app review · application no. 07 · sample data
Output

A reviewer's brief in PDF or Word, ready for the PM's monthly close. Approve, dispute, or route for negotiation — the audit trail captures the decision.

03 · The SOV reconcile

Schedule of values as the source of truth.

The SOV is the contract you signed expressed as line items. It's also where the most argument happens at pay-app time. The engine reconciles each billing line against the schedule of values you load with the pay app.

Initial reconcile

SOV totals = contract value

Sum of all line items equals the contract amount. CO-revised contract values flow into the running total. If the math doesn't sum, the pay app can't be paid in full — flagged before findings.

Period reconcile

This period + previous = total billed

Column G total = Column D (this period) + Column E (previous). We recompute every row.

Cross-period

Sub bills 40% → 60% → 75% → back to 70%

Completion can't go DOWN unless you're processing a back-charge. Flagged with the prior-pay-app history so the PM sees the regression and decides if it's an honest correction or a billing dispute.

04 · The procurement cross-check

Material billed. Delivery confirmed?

AIA G703 column F lets a sub bill for stored materials — material delivered to the site or to an off-site warehouse, not yet installed. The check is simple in theory: was it actually delivered? Was it stored with the right insurance? Most reviewers don't have the procurement data on hand to verify.

Pay App Review compares the pay app with the project's Procurement tracker. For each "stored materials" line on the pay app, it looks for the matching delivery in the procurement record. Mismatches get flagged — the most common: material billed as stored that was never delivered.

Match

$84K stored steel · delivered 5/8

Procurement record: 12 columns of W12×26 delivered by Walsh Steel 5/8/2026, signed by the super. COSM on file. Approved as-billed.

Partial

$42K HVAC equipment · only $28K verified

Pay app claims $42K of FCU units delivered. Procurement record shows 8 of 12 units received (~$28K). Approve $28K. Hold $14K until delivery.

Mismatch

$22K stored materials · no record

Pay app claims stored material. Procurement record has no delivery, no PO, no supplier confirmation. Dispute pending evidence.

05 · Owner reporting + audit trail

Sign-off ready. Audit-trail intact.

Every reviewed pay app lands in a single project register with the engine's findings, the PM's decision, and the dollar deltas.

Reviewer brief PDF

Hand it to the PM. Or to counsel.

Full findings list, severity-tagged, with dollar impact per finding, recommended approve/dispute totals, and one-line PM verdict per item. The document a contracting officer needs to back up a billing decision.

Pay app register

Every pay app, every sub, every period

Filterable by vendor, period, status, total approved/disputed dollars.

Approved pay apps update the project's billing-to-date roll-up.

★ · Pairs with

It works alone. It's better in a chain.

Pay App Review reads cleanly on its own. But the cross-checks need the project's procurement and schedule data.

  • Procurement — supplies the purchase orders and delivery status that the stored-materials lines are checked against.
  • Bid vs Actual — closeout reconciliation uses pay app actuals to show cost variance per cost code.
  • Schedule — the schedule's percent complete per activity is what billed completion is checked against.
06 · FAQ

Things everyone asks first.

What pay app formats are supported?

AIA G702 (Application for Payment) + G703 (Continuation Sheet) are native — we parse the AIA-issued PDF directly. Custom owner-issued pay app forms (proprietary spreadsheets, Sage Construction, Procore exports) are auto-mapped to the G702/G703 schema with reasonable accuracy. If your form is exotic, we fall back to extracting the SOV table and reconciling line-by-line.

How accurate is the completion-% check?

The engine cross-references three signals: master schedule earned-value, daily log crew counts on the relevant activity, and procurement delivery + install history. When all three agree within 5%, confidence is high. When they diverge, we surface all three for the PM to triangulate. We never claim certainty — we surface the data the PM needs to make the call.

What about pay apps that come in as a PDF screenshot of an Excel file?

Not yet. A PDF screenshot has no text layer, and this engine reads the text layer — so a screenshot comes through empty rather than wrong. Export the pay app as a native PDF or XLSX, or paste the SOV as text. We would rather refuse the file than reconstruct an SOV we cannot actually read.

Does it integrate with our accounting system?

Read-only for v1. We export approved pay apps as G702/G703 PDF + structured CSV; you push to your accounting system through whatever bridge you use today (manual entry, Sage import, Procore sync). A live QuickBooks Online sync is in development; a Sage 300 CRE connector is on the roadmap.

How does it handle owner pay applications (GMP contracts)?

Same engine, perspective flipped. The owner-facing pay app uses the GMP contract as the source of truth instead of the subcontract; stored materials check against the project-wide procurement register; retainage rules pull from the prime contract. Useful for owner-rep PMs running pay-app review on the GC's side too.

Drop a real pay app. See the findings.

Bring a G702/G703 from a live project to a 15-minute call. We'll process it on screen against your real SOV and procurement data. You keep the reviewer brief.

Try Free for 14 Days →