If you have ever approved a subcontractor invoice that “looked about right,” you already understand the problem: in construction, a single wrong quantity, missing change order, or duplicate invoice can quietly turn into a margin leak. The three-way match process is a simple control designed to prevent that. Done well, it catches errors early, protects job costs, and can actually speed up approvals because fewer invoices bounce around in confusion.
At its core, three-way matching is a verification step before you pay. You confirm that what you ordered, what you received, and what you were billed all align. The concept is common in manufacturing and distribution, but contractors have their own reality: field conditions change, delivery receipts get lost, and invoices often blend labor, materials, rentals, and retainage. That is exactly why a clear matching standard matters. Three-way matching is widely recognized as a foundational accounts payable control by financial professionals and audit bodies, including the Institute of Finance and Management in its guidance on three-way mismatches and resolution.
The three documents and what each one proves
Three-way match compares:
- Purchase Order (PO): What was authorized. This is your scope, pricing, and terms at the time of approval.
- Proof of delivery, or POD, field acceptance, or another receipt record: What was actually received or completed. This could be a delivery ticket, a foreperson sign-off, a daily report, a rental log, or inspection acceptance.
- Invoice: What the vendor or subcontractor says you owe.
When those three items agree, you have a defensible basis to pay. When they do not, you have a clear reason to pause, resolve, and document the change.
Why contractors get burned when matching is informal
Contractors do not lose money only through obvious fraud. More often, it is death by a thousand paper cuts. A delivery ticket goes missing and the invoice gets approved anyway. A change order is verbally agreed to but never coded properly, so costs land in the wrong bucket. Two project managers forward the same invoice and AP pays both versions.
The result is not just extra spend. It is also unreliable job costing, painful month-end cleanups, and leadership making decisions from numbers that are not trustworthy.
Where three-way match fits in your AP workflow
Three-way match should happen before payment, and ideally before an invoice is even marked “approved.” In many contractor workflows, the fastest improvement comes from making matching a consistent gate: invoices either pass quickly or go into an exception process that is easy to manage.
The three-way match process (step-by-step) that prevents subcontractor payment errors
Here is a practical, contractor-friendly version of the three-way match process. The goal is to create a repeatable workflow that your team can follow even on busy projects, without turning AP into a bottleneck.
Step 1: Build clean POs and change-order discipline
Three-way match fails if the PO is sloppy. A PO should be more than a placeholder. It should include:
- Clear scope and line items (labor, materials, rentals, etc.)
- Agreed pricing or unit rates
- Job, phase, and cost code assignments
- Any retainage terms or billing schedule expectations
Most importantly, commit to a simple rule: if the scope changes, the paperwork changes. In the real world, changes happen daily. What kills margins is allowing those changes to stay “off the record” until the invoice arrives.
If your organization struggles with change orders, start by standardizing what counts as an approved change. For example: a signed change order, an email approval from the authorized role, or a documented field directive that gets converted into a change order within a set timeframe. The exact method matters less than consistency.
If you want a broader view of how better systems support contractors, start with how DC Tech Group approaches ERP and workflow design.
Step 2: Capture proof of delivery and field acceptance
Not every invoice needs the same matching rule. A materials invoice may require delivery documentation, while a subcontractor pay application may require progress approval, lien waiver status, and retainage review.
In construction, “receipt” is not always a warehouse scan. Your receipt might be:
- Signed delivery ticket for materials
- Completed timecard or daily report for labor
- Equipment rental log and off-rent confirmation
- Inspection acceptance, punch completion, or milestone sign-off
The key is to define the acceptable proof for each category and make it easy to capture. A common best practice is to create a simple checklist per invoice type. For example, subcontractor progress billing might require a pay app, lien waiver status, and superintendent sign-off, while a materials invoice might require delivery ticket images and a packing slip match.
This is where operational discipline protects finance. When field teams know what is required, they can capture it at the moment the work is done instead of reconstructing it two weeks later.
Step 3: Verify the invoice and resolve exceptions fast
Now compare the invoice to the PO and the receipt/acceptance. This includes:
- Quantities delivered vs billed
- Unit prices vs PO rates
- Correct job, phase, and cost code
- Retainage and tax handling
- Dates and billing periods (especially for rentals and T&M)
When everything matches, approval is straightforward. When it does not, do not rely on informal Slack messages or forwarded emails. Put the invoice into a visible exception flow with clear ownership. The best teams treat exceptions like a queue, not a mystery.
Common mismatch scenarios (and how to fix them without slowing down)
Most AP teams see the same issues repeatedly. Fixing them is less about heroics and more about building standards that eliminate repeat confusion.
Quantity and unit-price mismatches
Quantity mismatches are often caused by partial deliveries, swapped materials, or field substitutions. The fix is to document the reality: was it a partial shipment, an over-delivery, or a genuine billing error?
Unit-price mismatches frequently happen when a vendor updates pricing mid-project or when a subcontractor bills at a rate that does not match the approved schedule of values. The best response is fast and factual: confirm what was authorized, confirm what was received, and either correct the invoice or issue a change.
Wrong job/cost code and phase misallocations
Mis-coded costs are one of the fastest ways to destroy job cost visibility. The invoice may be legitimate, but if it lands in the wrong bucket, your project reporting becomes unreliable. The correction process should be standardized, and it should be easy for project teams to flag coding issues early.
Many contractor-focused systems and workflows are built specifically to reduce this kind of rework. If your firm operates in commercial construction, it can help to evaluate solutions designed for your vertical.
Duplicate invoices, partials, and retainage confusion
Duplicates are common when invoices are submitted through multiple channels. A simple control, like requiring one submission method and using invoice number plus vendor as a uniqueness check, can eliminate most issues.
Partials and retainage create confusion when the schedule of values, prior billed amounts, and current billing are not clearly tracked. That is why an ERP-backed process matters. Instead of relying on spreadsheets, use a system that can maintain history and enforce rules consistently.
How to implement three-way matching without creating more admin work
The fear with any control is that it will slow the business down. In reality, a well-designed three-way match process can reduce total effort because it cuts down on corrections, rework, and back-and-forth approvals.
Define roles, approval thresholds, and “stop-the-line” rules
Start by defining who does what. Ownership typically falls across four roles: the field acceptance owner (superintendent or foreperson), the PO owner (project manager or purchasing), the invoice verification owner (AP or project accountant), and the final approval owner (controller or project executive, based on dollar thresholds).
Then define your “stop-the-line” rules. For example: if an invoice exceeds the PO by more than a set percentage, it cannot be approved without an updated authorization. This keeps the process fair and predictable for everyone.
Standardize your exception queue and SLA
Most organizations do not struggle with routine invoices. They struggle with the messy 10 to 20 percent that do not match. The solution is to create a standard exception path: one place where exceptions live, a clear owner for each, a target response time (SLA), and a required resolution note so you can identify patterns over time.
A simple exception status structure might include Needs PM Review, Waiting on Vendor, Change Order Required, Coding Issue, and Approved to Pay. This gives everyone on the team a shared language for where an invoice stands and what action is needed.
This turns exceptions into operational insight. If the same mismatch happens every week, it is a process issue, not a people issue.
Use ERP Workflows to Automate and Standardize the Process
Manual three-way matching is possible, but it tends to collapse under volume. ERP workflows can help by:
- Requiring POs before invoices can be approved
- Automating approval routing based on dollar thresholds
- Storing attachments (delivery tickets, pay apps, approvals) with the transaction
- Preventing duplicate invoices
- Keeping job cost coding consistent and auditable
In Acumatica, contractors can use connected project, purchasing, AP, and job cost workflows to make invoice review more consistent and easier to audit.
For field service organizations, the same discipline applies. Your systems should connect work performed, materials used, and billing in a way that is visible and consistent.
Measuring success: KPIs that prove your AP controls are working
Three-way matching should create measurable improvements. If it does not, your workflow is either not consistently applied or not designed for the realities of your projects.
Error rate, rework time, and cycle time
Track the percentage of invoices that go to exception, the average time to resolve each one, and the total cycle time from receipt to payment approval.
The goal is not zero exceptions. The goal is to resolve exceptions quickly, document the reason, and reduce repeat issues over time.
Job cost accuracy and margin protection
Your job cost reporting should become more trustworthy. Over time, you should see fewer month-end corrections, fewer surprise overruns that “come out of nowhere,” and better alignment between budget, committed cost, and actual cost. That is where the real value is.
Vendor and subcontractor relationship impact
This might surprise teams: a consistent matching process can improve vendor relationships. When you can point to clear documentation, disputes become easier to resolve. Subcontractors also benefit when approvals are predictable and payments are timely.
If you are ready to tighten up AP controls and reduce payment errors, reach out to DC Tech Group to discuss a practical implementation plan and how a modern ERP workflow can support it.
