What is three-way matching and why does it matter for construction invoices?

Key takeaways

• Three-way matching compares the purchase order, delivery receipt, and vendor invoice to verify quantities, prices, and totals before approving payment.
• In construction, matching must account for partial deliveries, multiple jobsites, and job cost dimensions like job number, cost code, and phase.
• Vergo codes invoices by inference from your own accounting structure and history, so transactions are ready to code the moment they happen — no waiting for clearing — and every coding shows why it was chosen.
• Without matching, contractors risk duplicate payments, vendor fraud, and unreliable job cost data that distorts WIP reports and future estimates.
• Mismatches often occur when invoices charge the wrong job or cost code, even if quantities and prices align.

What three-way matching means in construction accounting

Three-way matching is an accounts payable control that requires three documents to agree before an invoice is paid: the original purchase order, the delivery receipt or proof of goods received, and the vendor's invoice. If all three align on quantities, unit prices, and totals, the invoice is approved. If any document conflicts, the discrepancy is flagged for review. In general accounting, three-way matching is straightforward because purchases typically arrive at a single warehouse with standardized receiving procedures. Construction is different. Materials ship to multiple jobsites, deliveries happen at unpredictable times, and partial shipments are common. A single PO for rebar might result in three separate deliveries across two weeks, each with its own packing slip. Because construction projects use job cost accounting, three-way matching must also verify that the invoice charges the correct job number, cost code, and phase code.

Why this matters in construction

The core pain point is simple: invoices get paid without verifying that materials were actually received or that a valid PO exists. When this happens, contractors overpay, duplicate payments slip through, and job costs become unreliable. The downstream effects compound quickly. For a project controller, unmatched invoices distort work-in-progress reports and make cost-to-complete estimates unreliable. For an AP clerk, processing invoices without matching means relying on tribal knowledge — calling the superintendent to ask whether materials were actually received. Vergo eliminates this manual back-and-forth by coding transactions by inference from your own accounting structure and history, so a reviewer confirms in seconds instead of re-coding by hand. For a CFO, weak matching controls create audit findings and increase the risk of vendor fraud. For a project manager, budget overruns caused by duplicate or erroneous payments reduce the funds available for actual construction work. For the estimating team, inaccurate historical job costs lead to mispriced future bids.

A practical example: when matching catches costly errors

Scenario 1: Duplicate invoice without matching. A mechanical subcontractor's supplier sends Invoice #4410 for copper fittings on Job 1987, Phase 3, cost code 22-400. Two weeks later, the same supplier resubmits the invoice with a slightly different format as Invoice #4410-R. Without matching against the original PO and receiving records, AP pays both. The $11,200 duplicate goes unnoticed until the quarterly job cost review. Scenario 2: Partial delivery matched correctly. An electrical contractor orders 2,000 feet of copper wire on PO-6650 for a hospital project. The distributor ships 1,200 feet in week one; the field team logs receipt of 1,200 feet. When the invoice arrives for 2,000 feet, the three-way match catches the 800-foot discrepancy. AP holds payment and contacts the vendor, and only after the remaining 800 feet ships is the full invoice released.

Cost code and job number verification

A match on price and quantity means nothing if the cost hits the wrong project. Consider a general contractor that purchases form lumber for Job 3301, cost code 03-100 (concrete formwork). The vendor invoice lists the charge against Job 3301, cost code 06-100 (rough carpentry). The three-way match flags the cost code conflict. The AP team corrects the coding before posting, keeping the WIP schedule accurate and preserving the integrity of the concrete budget line. Without this verification step, the concrete formwork budget appears under-spent while the rough carpentry budget shows a cost overrun, distorting both the current project forecast and historical cost data used to estimate future work. Mid-size general contractors running 15 active projects can see these errors multiply across hundreds of monthly invoices, creating significant financial leakage.

How Vergo handles this

Vergo is an AI-native, card-agnostic expense management platform that codes transactions by inference from your own accounting structure and history. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into your accounting or ERP software. Card spend, employee reimbursements, and AP invoices run through one coding model, so you get the same coding, the same review, and one reconciliation. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. Vergo integrates with every ERP and accounting software, and connecting your existing cards involves no card applications, no re-issuing, and no banking change.

Related questions

• How do general contractors manage hundreds of vendor invoices per month?
• What is the cost of processing a single invoice manually in construction?
• How do I reduce the risk of vendor fraud in construction accounts payable?
• What is the best AP automation software for defense contractors using Unanet?