3 Way Match: The Fields, Tolerances, and Exceptions Explained

A pallet shows up eighteen units short. The invoice bills for all of them anyway. Nobody notices, because it gets paid before anyone puts the delivery note next to the invoice, and the shortfall turns up three weeks later as a line item nobody can explain.

3 way match is the accounts payable control built to catch exactly that. It compares three documents before anything gets paid: the purchase order, showing what was agreed; the goods receipt, showing what actually arrived; and the invoice, showing what the vendor wants for it. When the three agree, the invoice pays. When they don't, someone reviews the gap first.

This goes deep on the mechanics: what each document actually contributes, the exact fields worth comparing, how to set a tolerance instead of chasing every cent, the mismatches that show up most often and what to do about each, and an honest read on when three-way matching is more control than your business needs.

What each document brings to a 3 way match

The purchase order (PO) is where the match starts. It's the record of what your business agreed to buy, at what price, and in what quantity, issued before any money moves. Everything downstream gets checked against it, because it's the only one of the three documents that reflects what you actually authorized.

The goods receipt is the physical reality check. Someone counted what came off the truck and logged it, separate from anyone touching the invoice. It exists to answer one question: did what you ordered actually show up, in the quantity you're about to be billed for?

The invoice is the vendor's claim on your money, and it's the only one of the three the vendor controls. That's exactly why it doesn't get paid on its own. A three-way match works because the PO and goods receipt are both generated inside your business, independent of what the vendor decides to bill.

The fields a 3 way match actually compares

Invoice matching isn't a document-level check, it's line by line, field by field. The table below shows what each document is expected to say, and which fields the match is actually built to catch a disagreement on.

Price and quantity carry most of the match. Unit of measure is the field people forget, and it's the one that quietly multiplies an error: if the PO says cases and the invoice bills individual units, every other field can agree and the total will still be wrong by the pack size.

What a matching tolerance is, and how to set one

A tolerance is the small, defined difference a match allows without flagging an exception. Without one, a match run at face value throws an exception on every currency rounding difference and every case that ships half a unit light, which turns a control meant to save time into the thing eating it.

A worked 3 way match example

Say a distributor orders two things on the same purchase order: 1,000 corrugated shipping boxes at $0.85 each, and 200 rolls of pallet stretch wrap at $12.00 each. The truck arrives, the warehouse counts what's on it, and logs a goods receipt before the invoice even lands.

The boxes show up in full. The stretch wrap doesn't: 185 rolls arrive instead of 200, but the invoice bills for the full 200 anyway, at the agreed price. Here's the match, line by line.

The variance is exactly the 15 rolls that never arrived: 15 × $12.00 = $180.00. A 3 way match catches this because the goods receipt, not the invoice, is the source of truth for quantity. Pay the $3,070.00 the receipt supports, hold the $180.00 open, and let the vendor either ship the rest or issue a credit.

How to resolve a 3-way match exception, step by step

Not every exception means the same thing, and treating them all as "call the vendor" wastes the one advantage a three-way match gives you: it tells you exactly which figure disagrees. Here's what each common mismatch means and what to do about it.

1. Price variance. The invoice charges more per unit than the PO agreed. Hold the payment at the PO price and ask the vendor to either match it or send a credit for the difference before paying the balance.
2. Quantity variance. The invoice bills for more than the goods receipt shows arrived. Pay against the received quantity, not the invoiced quantity, and leave the gap open until the vendor ships the rest or credits it.
3. Partial delivery. The goods receipt shows the order split across two or more shipments. Match and pay each shipment against its own portion of the PO as it arrives, rather than waiting for the whole order to land.
4. Freight and handling charges. The invoice adds a shipping or handling line that never appeared on the PO. Check it against the agreed shipping terms separately, since freight usually isn't a line the match itself is built to catch.
5. Duplicate invoice. The same invoice number, amount, and vendor show up twice, sometimes weeks apart. Reject the second one outright rather than matching it again, since a duplicate will pass every check and pay in full a second time.

Where exceptions land varies by business, but the shape is fairly consistent. Quantity variances are usually the most common, price variances close behind, and duplicates are rare but the one type worth catching every single time. Here's a typical, illustrative split, not a figure from any one client.

When two-way match is enough, and what changes when it runs itself

Three-way matching earns its cost when goods receipts actually exist and someone checks against them. If your business doesn't carry physical inventory, a services firm, an agency, most SaaS spend, there's nothing for the goods receipt to compare against, and the control quietly becomes a two-document match wearing a three-document label.

Two-way match, invoice against PO, catches the same overbilling with one fewer document to chase on every invoice, forever. For fixed recurring bills, rent, software subscriptions, utilities, even a formal match is often more process than the risk justifies. Approve those on a schedule instead. For the wider process this control sits inside, see the accounts payable process.

The manual version of this doesn't scale past a handful of invoices a week: three documents, however many line items, checked by a person who also has other things due today. That's the part that's actually mechanical, comparing numbers across three sources, which is exactly what the agents we build do for document intake: read the PO, the receipt, and the invoice, flag only the lines that fall outside tolerance, and leave the judgment call, is this variance real, to a person.

It's the same capability behind SmallERP, which reads receipts and invoices and keeps them coded and matched without someone re-typing every line by hand. The match logic doesn't change; what changes is who's running it, and how few exceptions a person actually has to look at. The automation ROI calculator will tell you whether closing that gap is worth building against at your invoice volume.

Frequently asked questions

The bottom line

A 3 way match is only as useful as the documents behind it. If a goods receipt exists and someone's logging it accurately, the match catches real overbilling before it goes out the door. If it doesn't, the match is theater, and an honest two-way match against the PO is the better control.

Set a tolerance so rounding doesn't eat a day's work, know the five ways a match actually fails, and decide, on purpose, whether your invoice volume justifies checking it by hand or automating the comparison and keeping a person on the exceptions.