Construction payment audit checklist for owners: trace each dollar

Define the payment population before opening invoices

Start with one contract family and one cutoff date. Obtain the original agreement, amendments, change register, payment applications, certificates, accounts-payable ledger, credits and disbursement records. Record which currency and tax basis each file uses. Ask the owner to identify the contractual reviewer and the person authorized to decide a correction.

The first control is completeness. Reconcile the number and value of applications in the review register to the source-system export. List missing attachments and excluded contracts explicitly. An audit that starts with the easiest PDF folder can miss payments that never reached that folder. Save a dated export so a later ledger change does not silently rewrite the starting population.

Run six checks against the actual agreement

Confirm the current authorized contract amount, then compare cumulative requested work with the underlying schedule lines. Review the evidence for quantities and stored materials. Recalculate relevant markups using the agreement's eligible bases and sequence. Compare prior certificates with the prior amounts deducted in this application.

Next, inspect approval authority and the exact version approved. Finally, trace the resulting payable amount to credits, withholding and cash settlement. A payment can be accurately calculated but miscoded, approved by the wrong person or paid twice. Treat these as different exceptions because they require different decisions and produce different financial outcomes.

Worked example: distinguish a correction from a recovery

Consider a fictional owner contract of $900,000 plus $60,000 of authorized changes. The current contract basis is $960,000. Supported cumulative work is $480,000. Under this example's assumed flat 5% retainage, the cumulative amount after retention is $456,000. With $380,000 previously certified, the current amount before other adjustments is $76,000.

Suppose the draft asks for $88,000 because it deducts only $368,000 of prior certificates. The $12,000 difference is a proposed application correction. If the draft has not been paid, it is not recovered cash. If the owner already paid the excess, an agreed credit or refund needs its own reference before the result becomes confirmed. The percentages and values are teaching assumptions, not recommended contract terms.

Use audit findings to choose tests, not predict savings

Toronto's Auditor General reviewed 105 change orders and reported incorrect or unknown markups in 48%, with at least C$50,000 in overcharges. That finding supports checking markup evidence. It does not establish the error rate or recoverable amount on another owner's portfolio.

Use separate statuses for missing support, disputed interpretation, confirmed calculation error, approved adjustment and settled result. Ask the authorized reviewer to accept or reject the proposed adjustment with a reason. Preserve the response even when the original flag was wrong. A useful audit leaves a reproducible decision record, including clean transactions.

Sources: Toronto Auditor General: oversight of change orders in capital projects (2026)

Turn the checklist into a monthly control

Assign a preparer to reconcile the population before the next payment cycle and a separate reviewer to decide exceptions. Set deadlines around actual billing cutoffs. Escalate only the unresolved issue, amount and source required for the decision, rather than circulating an entire confidential packet.

Keep Procore, Oracle or the existing accounting system as the authoritative destination. Ask Buildalytic to demonstrate collection and follow-up for one missing payment record, then define any additional reconciliation work in a written scope. Judge the workflow by verified decisions and reviewer time. An annual portfolio assurance engagement should follow a successful diagnostic and agreed recurring coverage, rather than a promise that software replaces project certification.

Sources: Buildalytic: current custom-workflow scope