How to Read a Pay Application (and Spot Errors Before You Sign)

A pay application is a monthly snapshot of how much a subcontractor believes they have earned on a project, how much has been paid to date, and how much should be paid this cycle. In the best case, every number reconciles cleanly against the schedule of values, the prior pay app, and the underlying receipts. In the real world, pay apps routinely contain errors — some of them honest, some of them not — that add up to real dollars across a project's life.

The problem is that pay-app review is almost always under time pressure. The sub submits on the 25th, the GC wants to cut the check on the 1st, and the AP analyst has a queue of twelve other pay apps to process in the same week. Under that pressure, most reviews reduce to 'does the requested amount look reasonable' — which catches almost nothing.

A disciplined ten-minute review, done consistently, catches the large majority of real errors. Here is the review process, in the order that pays off fastest.

Step 1: Reconcile the G702 Summary to the G703 Detail

The first check is mechanical arithmetic. The G702 cover sheet summarizes totals that are supposed to match the G703 continuation sheet exactly. Run three reconciliations: column G on the G703 (total completed and stored to date, summed across all lines) should equal line 4 on the G702 (total completed and stored to date). Column J on the G703 (retainage, summed) should equal line 5 on the G702. And the balance to finish on G702 should equal the contract sum less line 4.

Discrepancies here are almost always either honest mistakes (a line item updated on the G703 but not flowed through to the G702 summary) or indicators that the sub is filling out the form by hand with different data in each section. Either way, kick it back — the document is internally inconsistent and should not be approved.

Step 2: Reconcile This Period to Previous Periods

The previous pay app's 'total completed and stored to date' should equal this pay app's 'work completed from previous application' on the G703 (column D). This is where most line-item drift shows up. If the sub rebalanced scope between lines between periods — moving $20K from the 'demolition' line to the 'framing' line — column D will not match column G from the previous period, and you need to understand why.

Line-item drift is not always fraud; sometimes it reflects legitimate scope re-allocation. But it should always be acknowledged in writing (a change-order memo or SOV revision), not quietly slipped into the next pay app. If the drift is unexplained, kick it back and ask for the baseline change documented.

Step 3: Review Stored Materials (Column F)

Column F on the G703 is where stored-but-not-installed materials are billed. Three checks:

The most common stored-materials error is the one where the sub bills $50,000 of stored material in month four, installs it in month five, and the installation shows up in column E of month five while column F never decreases. That's a $50,000 double-bill that's trivial to miss on quick review and trivial to catch on a period-over-period check.

Step 4: Check Retainage Math

Retainage should be a clean percentage of column G on each line. Verify the percentage matches the contract — some contracts specify 10% for the first 50% of the project and 5% thereafter, and subs will occasionally switch the percentage at the wrong point.

Line items that are contractually retainage-exempt (typically bonds, insurance, permits, and mobilization) should show zero in column J. If they show retainage, the sub is either under-billing themselves (rare) or the SOV has the wrong baseline retainage setting — either way, flag and correct.

Step 5: Reconcile Change Orders

Change orders should appear as separate lines at the bottom of the G703, each with their own scheduled value that matches the approved change-order document. Two checks:

Change orders are the most common source of closeout disputes specifically because this reconciliation is easy to skip during the project and impossible to untangle after. Every change order should be a clean, traceable line on the G703 from the period it was approved through project closeout.

Step 6: Check Percent Complete Against Schedule

Column H on the G703 shows each line's percent complete (column G / column C). Compare a handful of lines against the project schedule: does the percent complete on the 'framing' line actually reflect observable framing progress on site? If the schedule says the framing is 40% complete and the pay app says 70%, that's either a pull-ahead the sub needs to justify or an overbilling.

In practice, the AP analyst won't usually do the site verification — that's the project manager's job. But the AP analyst should be cross-referencing the pay app's percent-complete claims against the project manager's most recent progress report. When those two disagree, that's a real red flag.

Step 7: Compliance Check

Before the pay app can be approved, the sub's compliance status needs to be current. A typical compliance gate includes:

Any compliance gap should block approval, not simply generate a note-to-self. The follow-up rarely happens on time once payment has cleared.

Red Flags That Should Always Trigger Extended Review

The Ten-Minute Review in Practice

Done manually, this review takes 10-20 minutes per pay app for a well-structured SOV and significantly longer for a messy one. Across a mid-sized GC processing 30-80 pay apps per month, that's 10-20 hours of AP analyst time monthly — time that is rarely budgeted and therefore rarely spent.

The highest-leverage move for most construction AP teams is to automate the first five steps (arithmetic reconciliation, period-over-period check, stored materials logic, retainage math, change-order reconciliation) so that the human analyst spends their time only on the two steps that require judgment (progress verification and compliance review). That's the specific shape of AP automation that actually works for construction, as opposed to generic invoice-processing automation built for commercial AR-AP flows.

Bottom Line

Reading a pay application is a skill that takes months to build and minutes to execute once you have it. The seven-step review above is the exact sequence that experienced construction AP teams run on every draw. It catches the errors that matter, and it catches them before money has left the account — which is the only catch that actually helps.