Why this always takes longer than it should
Every project accountant who has done this once knows the feeling: it should take twenty minutes, and it takes an afternoon. The arithmetic on a single pay application is trivial — completed value minus retainage minus prior payments should equal the amount due. What eats the time is checking that every line's percent complete actually moved forward, that retainage was withheld at the correct current rate, and that nothing on the schedule of values quietly shifted since the last pay application.
This guide is that checking process, made repeatable. Not a trick to make it instant, but a method that turns a guessing exercise into a short list of genuine judgment calls, done the same way every time.
Two decisions before you start
Two choices, made once, save re-litigating them every single billing cycle.
What counts as a confident check
Decide, once, how much agreement between percent complete, retainage rate and running total you need before treating a line as confirmed versus needing a second look.
Who resolves flagged lines
Decide who has the contract knowledge to tell a flagged line apart from a genuine discrepancy, so a review item doesn't sit unresolved because no one owns the decision.
Neither decision needs to be perfect on the first try. Most firms set an initial standard, run a cycle or two, and adjust — too strict and every line gets flagged, defeating the purpose; too loose and a genuine overbilling slips through unnoticed. What matters is making the decision explicitly rather than letting it drift cycle to cycle based on whoever happens to be reviewing that month.
The seven steps
Gather the pay application, schedule of values and contract terms
Pull the current G702/G703, the prior period's pay application, and the contract's stated retainage terms — including any step-down clause. Missing even one of the three means checking the current period in isolation, which catches arithmetic errors but misses everything that depends on comparing periods.
Read every line on the schedule of values
Scheduled value, percent complete, retainage withheld and amount due for every line — not just the ones that look unusual at a glance. A line that seems routine is exactly where a small, easy-to-miss error tends to hide, because it's the one nobody double-checks.
Check each line against the prior period
Percent complete should move forward, retainage should apply the currently correct rate, and the running total should stay within the contract sum including approved change orders. A line that fails any one of these deserves a closer look before certification, not an assumption that it will sort itself out.
Review flagged and inconsistent lines
Confirm every ambiguous check with whoever prepared the pay application, and investigate anything the current and prior periods genuinely don't agree on. Most flagged lines resolve quickly once someone with the project context looks at them directly.
Account for change orders separately
Confirm any new or revised schedule-of-values line traces back to an actually executed change order, not just an entry that appeared on the schedule of values without documentation behind it. An undocumented increase in contract sum is one of the more consequential things to catch early.
Update the running retainage balance
Carry the cumulative retainage total forward, per project and per line, so the balance due at final release is already known well before substantial completion — not a reconstruction project that starts only once the job is finished.
Log the period and set the next date
Save the checked record with the flagged items and their resolutions, and put the next pay application's review on the calendar before the current one is even fully closed out. The habit breaks most often in the gap between cycles, not during the review itself.
A pay application, worked start to finish
A $2.4M contract, month eight, pay application #8 against a 22-line schedule of values with a 10%-to-5% retainage step-down triggered at 50% complete.
| Check | Result |
|---|---|
| Lines with percent complete moving only forward | 21 of 22 |
| Retainage rate matching contract terms | Confirmed at 5%, step-down verified at period 6 |
| Running total within contract sum plus change orders | Confirmed |
| Lines flagged for review | 1 — interior framing, jumped 40% to 90% |
The flagged line stood out because a jump that size in one period was well beyond what site progress actually supported. Confirmed with the project manager and corrected to 65% before certification — a genuine overbilling caught before it reached the owner, and exactly the kind of thing a line-by-line check exists to find.
Common mistakes
Trusting the pay application's stated total without checking the lines
A total can be internally consistent and still wrong relative to the schedule of values — the total is the output of the check, not a substitute for it.
Treating a retainage step-down as an error
A rate that drops mid-project usually reflects a legitimate contractual trigger, not a mistake — check the contract before flagging it.
Letting the schedule of values drift out of sync with the contract
An unrecorded change order eventually shows up as a schedule-of-values line with no documentation behind it, discovered far later than it should have been.
Reconciling monthly totals without checking individual lines
A total that looks right can still hide one line moving backward and another overcompensating — check the lines, not just the sum.
When the contract's retainage rate steps down
Many contracts, and many state prompt-payment statutes independently of contract language, reduce retainage once a project reaches a stated completion threshold — commonly 50%. The step-down is legitimate, but it needs to be confirmed against the contract once, not re-litigated as a suspected error every period after it takes effect.
Read the trigger condition from the contract before the period it's expected to take effect, confirm the project's actual progress meets it, and apply the new rate from that period forward — a rate that was correct once and gets checked against the wrong baseline afterward is one of the more common sources of a false discrepancy in this whole process.
Doing this across several projects
A firm running several active jobs at once faces this exact problem multiplied — each project has its own contract, schedule of values and retainage terms, and no single view naturally shows all of them side by side without deliberate effort to build one.
Check each project against its own contract terms individually, and roll the results up into one portfolio-level view afterward — a running total of retainage held across every job, alongside the detail for any single project when it's needed, without collapsing distinct contracts into one undifferentiated number.
The very first review
The first pay application checked on a new project takes longer than every one after it, because there's no prior period to compare against yet — the schedule of values itself needs to be confirmed against the signed contract, retainage terms need to be read carefully rather than assumed, and any pre-existing change orders need to be reconciled before the baseline is trustworthy.
That upfront cost pays off on every subsequent period, where the check is mostly a comparison against an already-confirmed baseline rather than a from-scratch verification.
Choosing a cadence that actually sticks
Matching your review cadence to the project's billing cycle is the simplest rule that works — monthly for the standard AIA cycle most contracts follow. Reviewing less often than pay applications are submitted means several periods of billing pile up before anyone checks any of them against the contract, and an error compounds across every period it goes unnoticed in.
For a firm running multiple projects on staggered schedules, batching the review on a fixed monthly rhythm — rather than chasing each project's individual submission date — is usually the more sustainable habit, even if it means reviewing some projects a few days later than their own cycle would strictly allow.
What to do with a genuine discrepancy
A flagged line that turns out to be a real overbilling — not a step-down, not an unrecorded change order, but an actual error — needs a direct conversation with whoever prepared the pay application before certification, not a silent correction and not a certification that quietly ignores it.
Most genuine discrepancies resolve in that single conversation. The ones that don't are usually a sign the schedule of values itself needs a broader review, not just the one flagged line — worth treating as a signal, not an isolated incident.
What you actually need
A spreadsheet for the schedule of values and the running retainage total, and a reliable way to read every line of a pay application against it without transcribing by hand. The spreadsheet part rarely needs replacing — the reading and checking part is where automation earns its keep, because that's the part that scales badly with project count and schedule-of-values length. The mechanics behind that running total are covered in more depth in retainage tracking.
Handing this off to a new project accountant
The schedule of values history, the running retainage balance, and the method itself should transfer with the role — not live only in the outgoing accountant's memory of which lines have been contentious or which projects have unusual retainage terms.
A short handoff document — active projects, their retainage terms, any open flagged items — costs little to maintain and saves the incoming accountant from rediscovering context that already existed, often at the worst possible time, mid-billing-cycle.
Three ways to do this, compared
| Method | Best for |
|---|---|
| Fully manual | A single small project, simple flat retainage, no change orders |
| Spreadsheet-assisted | A handful of projects with a maintained schedule of values |
| Automated checking | Any project count, especially with step-downs or frequent change orders |
Most firms don't pick one method permanently — they start manual, move to a spreadsheet once the manual version becomes unwieldy, and adopt automated checking once project count or schedule-of-values complexity makes the spreadsheet version too slow to trust.
The tracking log, column by column
| Column | What it captures |
|---|---|
| Pay application # | Sequential identifier tying every check back to a specific submission |
| Period covered | The billing window the pay application actually covers |
| Retainage rate applied | The rate this period, and whether it reflects a step-down |
| Running total to date | Cumulative completed value and cumulative retainage held |
| Flagged lines | Any line requiring review, with resolution noted |
How to tell it's working
The clearest sign is a shrinking gap between when a discrepancy occurs and when it's caught. Early on, a step-down applied incorrectly might not surface until final retainage release, months later. A working process catches it the period it happens, when it's a quick correction instead of a reconstruction project.
A secondary sign is the review queue's stability over time — not shrinking to zero, which would suggest the check has stopped actually looking closely, but staying proportional to how much genuine complexity — change orders, step-downs, multiple contract tiers — the project actually has.
A realistic billing cycle, laid out
| When | What happens |
|---|---|
| Day 25–28 of the month | Project manager prepares the G702/G703 for the period |
| Day 1–2 of the next month | Pay application submitted and checked against the schedule of values |
| Day 2–3 | Flagged lines confirmed with the project manager |
| Day 3–5 | Pay application certified and payment processed |
When to fold in a change order
A change order should update the schedule of values the period it's actually executed, not the period it's billed. Waiting to add it until the pay application that first bills against it means the check has no baseline to compare that line to, and a legitimate new scope item looks like an unexplained addition to the contract sum.
Building the habit of updating the schedule of values the moment a change order is signed — before any billing against it happens — keeps every subsequent check clean, and avoids a scramble to reconcile paperwork after the fact.
Statutory retainage rules to check before you start
Many jurisdictions layer statutory retainage rules on top of whatever a contract independently specifies — a maximum retainage percentage the contract can't legally exceed, a mandated step-down at a defined completion percentage, or a required timeline for releasing retainage after substantial completion is certified. These rules apply regardless of what the contract itself says, and a check built only around contract language will miss them entirely.
Before checking the first pay application on a new project, confirm which statutory rules — if any — apply to that project's jurisdiction and project type, and note them alongside the contract terms you're already tracking. Public projects are the most likely to carry these rules, but some states extend similar protections to private commercial work as well, so it's worth confirming rather than assuming based on project type alone.
A firm working across multiple states benefits from keeping a short reference table of each jurisdiction's retainage rules alongside its contract templates — a document that rarely changes, but that's far cheaper to maintain once than to research fresh on every new project.
When a project sits idle mid-construction
A project can pause for months — a permitting delay, a design change, a financing gap — with pay applications stopping entirely during the idle period and resuming later, sometimes with a different project manager, sometimes with schedule-of-values lines that need updating to reflect a scope that changed while the project sat dormant.
Treating the first pay application after a long pause as a routine continuation of the last one, without re-confirming the schedule of values and retainage terms still match the current contract, risks carrying forward assumptions that quietly became stale during the gap. A short re-baseline step — confirming the contract hasn't been amended, the schedule of values still reflects current scope, and the retainage rate hasn't changed — costs little and prevents a resumed project from billing against an outdated baseline.
Coordinating with a bonding company's requirements
A surety backing a contractor's bonds often has its own reporting expectations around work in progress — how current billing tracks against actual completion, how much retainage is held across active projects, whether any project shows signs of overbilling. These expectations aren't always identical to what a contract itself requires, and treating them as an afterthought at renewal time creates unnecessary friction.
Building the review method around the same running balances and confirmed pay applications this guide describes means a bonding company's questions can usually be answered from records that already exist, rather than requiring a separate reporting exercise built specifically for the surety relationship each time it's asked for.
A closeout checklist
| Item | Confirm before final release |
|---|---|
| Running retainage balance | Matches a fresh calculation against the full contract sum and rate history |
| Punch list | Closed, or a documented reason for any retainage held past substantial completion |
| Change orders | All executed change orders reflected in the final schedule of values |
| Subcontractor retainage | Each sub's own retainage reconciled before their final release |
A project checked consistently through every billing cycle arrives at this list with every item already confirmed — closeout becomes a formality rather than the point where months of unchecked billing finally gets reconciled all at once, under the added time pressure of a project everyone wants finished.
When a project manager disagrees with a flagged line
A project manager who prepared a pay application doesn't always agree that a flagged line is actually wrong — a percent complete that looks aggressive on paper might reflect real site progress the schedule of values simply doesn't capture well, or a change order the project manager considers verbally approved even though it hasn't been formally executed yet.
Treating every flag as automatically correct undermines the project manager's legitimate site knowledge; treating every project manager objection as automatically valid defeats the point of checking in the first place. The useful middle ground is a quick, specific conversation — what evidence supports the higher percent complete, where's the change order documentation — that resolves most flagged lines within minutes once both sides are looking at the same specific discrepancy rather than a vague sense that something might be off.
A flag that survives that conversation and still looks wrong is worth escalating before certification, not after — a pay application is far easier to correct before it's submitted to the owner than after, when correcting it means either an awkward conversation about a previous overbilling or a complicated adjustment on a future pay application to compensate.
Documentation habits that make every future check easier
A handful of small habits, adopted consistently, make every subsequent pay application check faster than the one before it. Keeping change orders logged the day they're executed, not the day they're first billed. Keeping a single, authoritative copy of the current schedule of values rather than several slightly different versions circulating between the field and the office. Noting the reason for any unusual figure directly on the pay application itself, rather than relying on someone remembering the explanation months later.
None of these habits require new software or a process overhaul — they're small disciplines that compound. A project with clean documentation habits from month one reconciles noticeably faster by month twelve than one where each pay application review starts by reconstructing context that should have been recorded the first time.
The clearest sign these habits have taken hold is how quickly a new person can pick up the project accounting for an unfamiliar job — if a colleague can review last month's pay application and understand every flagged line's resolution just from what's documented, without asking anyone a single follow-up question, the habits are working exactly as intended — and that same documentation is what makes an eventual staff transition, an audit, or a bonding review go smoothly instead of becoming its own separate research project.