What is 3-way matching?

3-way matching is a check your finance team runs before paying a supplier. It compares three documents: the purchase order that authorised the spend, the goods receipt note that confirms what arrived, and the supplier invoice that asks for payment. When the quantities and prices agree across all three, the invoice is cleared for payment. When they disagree, it is held as an exception until someone resolves the gap.

The purpose is straightforward. You pay for what you ordered, at the price you agreed, and only once you have received it. The purchase order proves the order was authorised. The goods receipt note proves the goods or services turned up. The invoice is the supplier asking to be paid. The match is the moment those three views of the same transaction are reconciled.

Why finance teams do it

A supplier invoice on its own is a claim. It says what the supplier believes you owe. Without a check against the order and the receipt, that claim gets paid on trust, and trust is where money leaks.

Three-way matching closes the most common gaps in accounts payable:

• Overpayment. The invoice bills 120 units at a higher unit price than the purchase order agreed. The match catches both the quantity and the price variance before the payment run.

• Duplicate invoices. A supplier sends the same invoice twice, or a copy is keyed a second time in a busy month-end. A duplicate check on supplier, invoice number and amount is the main control here. Matching adds a second line of defence: once a purchase order line has been billed in full, a repeat claim against it has nothing left to match.

• Paying for goods you never received. The invoice arrives, the delivery does not, or arrives short. With no goods receipt to match against, the invoice is held as an exception until the delivery is confirmed.

• Invoice fraud. A fabricated or inflated invoice from a real or spoofed supplier has no matching authorised order behind it. The control gives every payment a paper trail an auditor can follow.

Where it breaks down manually

The logic of 3-way matching is simple. Doing it by hand at volume is not. The three documents rarely live in one place. The purchase order sits in the ERP, the goods receipt note comes from the warehouse or a site manager, and the invoice lands as a PDF in a shared inbox or on paper in the post.

So an AP clerk keys the invoice, finds the purchase order number, hunts down the receipt, and compares line by line. Quantities are checked against deliveries, prices against the order, tax against the goods. On a clean invoice this takes a couple of minutes. On a messy one, with part deliveries, a missing receipt, or a price the buyer renegotiated but never updated, it turns into a chase across three teams.

The result is a queue. Invoices wait for a receipt that has not been booked in, or for a buyer to confirm a price change. Early-payment discounts lapse. Suppliers call to ask where their money is. And because the work is dull and repetitive, tired eyes miss the variances the check exists to catch.

A worked example

Here is one supplier invoice with four lines, checked against its purchase order and the goods receipt. The business allows a 2% price tolerance, and never pays for more than has been received.

The first line agrees across all three documents. The gasket set is billed 4p a unit above the order, a 1.6% difference, so it passes within tolerance. The bolt pack bills for 50 packs when only 40 have been booked in, so £180 is held until the rest arrives or the supplier issues a credit. The anchor plate is 3.2% above the agreed price, outside tolerance, so it goes to the buyer to confirm the new price or reject it.

Whether the clean lines pay straight away or the whole invoice waits for the exceptions is a policy choice. Many teams hold the full invoice until every line is resolved, so the supplier receives one payment and one remittance.

2-way vs 3-way vs 4-way

Three-way matching is the common standard, but it is one point on a scale. How many documents you match depends on what you are buying and how much control the spend warrants.

2-way matching

Two-way matching compares the purchase order and the invoice only. It confirms you were billed for what you ordered, at the agreed price, but it does not confirm the goods arrived. It suits services and other spend where there is no physical delivery to receipt, such as a subscription or a professional fee booked against a purchase order.

3-way matching

Three-way matching adds the goods receipt note, so the invoice is checked against both the order and the confirmed delivery. This is the standard control for physical goods, because it is the only version that proves you received what you are paying for. Most AP teams treat it as the default for stocked and ordered items.

4-way matching

Four-way matching adds an inspection or quality-acceptance step to the three documents above. The invoice is held not just until goods are received, but until they have passed a quality check. It is used in manufacturing, construction and regulated supply chains, where accepting faulty material has a real cost and payment should wait for sign-off.

Automating the match

Matching is a set of rules applied to structured data, which makes it a natural fit for automation. Software captures the invoice, reads the line-level detail, finds the purchase order and the goods receipt in your ERP, and compares them against tolerances you set. Small, expected variances pass within tolerance. Anything outside it is flagged and routed to the right person with the mismatch shown.

That changes the shape of the work. Your team stops matching every invoice and starts reviewing only the ones that fail. The clean majority post straight through to the ERP with the purchase order, receipt and nominal codes intact. This is the core of how AP automation works, and matching is where most of the manual hours disappear.

The variable that decides how much lands cleanly is how accurately the invoice is read in the first place: a misread quantity or price fails the match just as surely as a genuine discrepancy. Once an invoice matches, its data posts into the ERP you already run, with your nominal codes and tax groups intact.