Construction Accounts Payable: The Complete Operations Guide

Construction accounts payable has a reputation for being messy, and the mess is usually blamed on volume. The real cause is structural: a construction invoice carries obligations that a generic AP workflow was never designed to check. This guide describes the full operating model — the lifecycle each invoice should follow, who owns each step, what goes wrong, and how to measure whether the function is working.

It is the hub for our construction AP series. For controls specifically, see the construction AP controls framework; for retention mechanics, see retainage management for AP teams; for benchmarks, see the Construction AP Benchmark Centre.

Why construction AP is a different discipline

Four things make a contractor's payables fundamentally different from a distributor's or a SaaS company's:

• Every line is a job-cost entry. An invoice is not fully processed until each line is coded to a job, phase, cost code, and cost type. Miscode it and the project's margin report is wrong — see construction job costing for how the dimensions fit together.
• Approval means field verification. Someone who saw the work — a project manager or superintendent — has to confirm the billed quantities happened on that job before the invoice is safe to pay.
• Payments have documentation gates. A subcontractor payment without a signed lien waiver of the correct type is a risk event, not a completed task.
• Part of every billing is withheld. Retention accrues on progress billings at contract terms and lives outside normal AP aging until release.

Generic AP software treats these as edge cases. In construction they are the workflow.

The construction invoice lifecycle

A well-run construction AP function moves every invoice through seven stages. The stages are the same whether the tooling is paper or fully automated — automation changes who does the work, not what must happen.

1. Receipt. All invoices land in one intake point — a dedicated AP inbox, not project managers' personal email. Invoices that arrive in the field get forwarded in, never processed from the side.
2. Capture. Header and line data are extracted: vendor, invoice number, date, amounts, and — critically — the job references the vendor wrote on the invoice.
3. Coding. Each line is assigned job, phase, cost code, and cost type. The discipline that matters is coding at entry: recoding at month-end means project reports were wrong all month. Vendor history and PO context predict most codes; the exceptions need a human who knows the job.
4. Matching. PO-backed lines are matched against the commitment — three-way matching where receiving exists, two-way against the PO or subcontract elsewhere. Within tolerance, the invoice can skip field approval entirely.
5. Approval. Unmatched or judgment-dependent invoices route to the project manager; everything routes by documented thresholds, with mobile approval and automatic reminders doing the chasing. Our approval delay calculator quantifies what this stage costs when it runs on email.
6. Compliance gate. Before payment: correct waiver signed, compliance documents current, retention withheld at contract terms. See lien-waiver controls and retention tracking.
7. Payment and posting. The coded bill posts to the accounting system (for most contractors, QuickBooks), retention posts to its own balance, and the payment run releases under dual control.

Centralised vs project-level processing

Contractors oscillate between two failure modes: fully central AP that approves work nobody verified, and per-project AP where every job office keys its own invoices, vendor records fragment, and no control is applied twice the same way.

The working pattern is central processing, distributed verification. One team owns intake, coding standards, matching, the vendor master, and payment. Project teams do exactly two things: verify work and approve within their authority. Everything the project team touches flows through the same central pipeline.

Roles and responsibilities

The most common structural mistake is letting the project manager role bleed into the others — PMs entering invoices, editing vendor records, or holding payment authority. Field verification is essential; field control of the ledger is how errors and fraud hide.

The construction exception taxonomy

Tracking why invoices stall is what turns AP problems into fixable upstream problems:

Cross-industry research puts the average exception rate at 14% of invoices (IOFM). Contractors carrying a broader taxonomy should expect the untreated number to run higher — and should measure it rather than guess.

The metrics that tell you AP is healthy

Six numbers, tracked monthly, describe the function: cost per invoice, invoice-to-posting cycle time, approval days split by role, first-pass job-cost coding accuracy, missing-waiver rate at release (target: zero), and retention outstanding by job. Definitions and formulas for the full set live in the Construction AP Benchmark Centre; the cost-per-invoice calculator and job-costing calculator compute your baseline from numbers you already know.

Measure the baseline before changing anything. The improvement case for automation should be provable from your own before/after data, not vendor claims.

Where automation belongs — and where it does not

Automation earns its keep on the deterministic steps: capture, code suggestion from vendor and PO history, matching within tolerance, approval routing and reminders, waiver chasing, retention arithmetic, and posting coded bills to the ledger. Cross-industry data shows what that is worth — the all-in industry average is $9.40 per invoice (Ardent Partners), against $1.50–$3.00 with end-to-end automation (IOFM).

The judgment calls stay human: approving work, resolving disputed billings, releasing retention, and any payment above threshold. A system that auto-posts everything is not mature AP — it is an unaudited one. The dividing line between the two is the subject of the controls framework.

If you want to see the full lifecycle running on a QuickBooks file — capture, coding, matching, field approvals, waivers, and retention in one flow — that is what Nexus Build does.