BonoficiGrade your business
Menu
Guide10 min read

Three-Way Match: How 3-Way Matching Works in Accounts Payable

How three-way matching works, 2-way vs 4-way, example tolerances, why invoices fail to match, and how to automate it, with a matching rules and exception reasons sheet.

A three-way match checks a supplier invoice against two other documents before anyone pays it: the purchase order that says what you agreed to buy, and the goods receipt that says what actually arrived. If quantity, price and item agree across all three, within the tolerances you set, the invoice is approved for payment. If they don’t, it goes on hold and a named person decides what happens next.

What three-way matching is for

Accounts payable has one job that matters more than speed: pay the right supplier the right amount for something you ordered and received. Each of the three documents answers one part of that question.

  • The purchase order (PO) says what was agreed: item, quantity, unit price, delivery terms.
  • The goods receipt (or delivery note, or receiving report) says what came through the door, booked by whoever unloaded it.
  • The supplier invoice says what the supplier wants paid.

Each document comes from a different person: a buyer, someone in the warehouse, the supplier. That separation is the point. No single person can order, receive and approve payment for the same goods, which is why auditors like it and why it catches mistakes that a single approver would wave through.

Two-way, three-way and four-way match

The number refers to how many documents are compared. Most companies use more than one level, depending on what is being bought.

MatchComparesTypical use
Two-wayPO and invoiceServices, subscriptions and low-value orders where there is no physical delivery to receive
Three-wayPO, goods receipt and invoiceStock and physical goods: the default for anything that arrives on a pallet
Four-wayPO, goods receipt, inspection report and invoiceGoods that must pass a quality check before they count as received, such as raw materials or regulated parts

A sensible rule is to write down which purchase categories get which match, and stick to it. The common failure is not choosing the wrong level, it is applying three-way matching to services that never get a goods receipt, so every one of those invoices lands in the exception queue.

Tolerances: how close is close enough

Real invoices rarely agree to the penny. A tolerance is the gap you accept without asking anyone. Without tolerances, someone reviews every rounding difference. With tolerances that are too loose, you pay for things you didn’t get.

There is no standard figure. These are examples of the kind of rules companies set, not recommendations:

  • Price: for example, accept a unit price up to 2% above the PO, or up to a fixed amount per line, whichever is smaller.
  • Quantity: for example, accept an invoice for less than was received, but never for more.
  • Invoice total: for example, a small absolute amount to absorb rounding across many lines.

Set tolerances per supplier or category if you need to. A supplier who always rounds unit prices to two decimals needs a different rule from one who invoices in whole pallets. Write the reason next to each tolerance, so the next person can tell a deliberate rule from a workaround.

Why invoices fail to match

When you look at the exception queue, the same handful of causes come up again and again. Knowing which one you are looking at tells you who should fix it.

  • Partial deliveries. The supplier invoices the full order, but only part of it has been received.
  • Price changes. The supplier raised prices after the PO was raised, or the buyer agreed a new price by phone and never updated the PO.
  • Units of measure. The PO is in boxes, the delivery note in units, the invoice in kilos.
  • Extra lines. Freight, fuel surcharges, packaging or handling fees that were never on the PO.
  • Missing goods receipt. The goods arrived, but nobody booked them in the system. This is often the largest single cause, and it is a warehouse habit, not an AP problem.
  • Duplicate invoices. The same invoice sent twice, by email and by post, or re-sent with a new number after a reminder.
  • Wrong PO reference. The invoice quotes an old PO, a different branch’s PO, or none at all.

The three-way match process, step by step

  1. Raise the PO in your accounting or ERP system (QuickBooks, Xero, NetSuite, SAP or similar) with item, quantity, unit price and supplier.
  2. Book the goods receipt when the delivery arrives, against the PO, recording what actually came in. Short or damaged goods are noted here, not later.
  3. Capture the invoice. It arrives by email, PDF, portal or post. Key it in, or extract the fields automatically: supplier, invoice number, date, PO reference, lines, quantities, prices, tax and total.
  4. Check for duplicates on supplier, invoice number and amount before anything else.
  5. Match line by line: each invoice line to a PO line and a receipt line.
  6. Apply tolerances. Lines within tolerance pass; lines outside go to an exception with a reason.
  7. Approve or hold. A fully matched invoice goes to payment. An exception is put on hold and routed to whoever can resolve it.
  8. Post and pay on the agreed terms, and keep the three documents linked for audit.

Handling exceptions without losing a week

The match itself is quick. Exceptions are where the time goes, mostly in waiting: an email to a buyer who is out, a question to the warehouse that nobody answers. Three rules keep the queue moving.

  • Route by reason. A price difference goes to the buyer who raised the PO. A missing receipt goes to the warehouse. A duplicate goes back to AP. The exception reason decides the route, so record it every time.
  • Give every hold an owner and a date. “On hold” with no name is how invoices end up paid late, or paid twice after the supplier re-sends.
  • Decide what AP may resolve alone. For example, AP accepts a freight line under a set amount if the supplier’s terms include delivery charges; anything else goes to the buyer.

Write these rules down. The way exceptions are handled on a quiet Monday is often not how they are handled at month end, when someone senior approves a batch to get them out of the way. Our lesson on documenting the exceptions covers how to capture both versions.

Matching rules and exception reasons

Part 1: matching rules

CategoryMatch typePrice toleranceQuantity ruleTotal toleranceReason for this rule
Stock itemsThree-waye.g. 2% or [amount] per line, lower of the twoInvoice ≤ receivede.g. [small amount][why]
ServicesTwo-waye.g. 0%n/ae.g. [small amount][why]
Raw materialsFour-way[ ]Invoice ≤ accepted after inspection[ ][why]

Part 2: exception reasons

CodeReasonRouted toAP may resolve alone if…Respond within
PRICEUnit price outside toleranceBuyer on the PONever[x] working days
QTYInvoiced more than receivedWarehouse leadReceipt is booked late and matches[x] working days
NO-GRNo goods receipt bookedWarehouse leadNever[x] working days
UOMUnit of measure differsAP, then buyerConversion is on the supplier record[x] working days
EXTRALine not on PO (freight, surcharge)Buyer on the POUnder [amount] and allowed by terms[x] working days
DUPPossible duplicateAPAlways: reject and note the originalSame day
NO-PONo or wrong PO referenceAP, then requesterCorrect PO found on supplier record[x] working days

Owner of these rules: [role]. Last reviewed: [date]. Next review: [date].

How to automate three-way matching

Accounts payable automation works best when it does the dull part, reading and comparing, and leaves the decisions to people. A practical order to build it in:

  1. Extract the invoice fields. OCR turns a scanned or PDF invoice into text; AI invoice processing goes further and reads the layout, so it can find the PO number and the line items on a supplier format it has not seen before. Keep a confidence score per field and send low-confidence fields to a person.
  2. Match lines, not just totals. Matching on invoice total alone hides a price rise on one line offset by a short delivery on another. Match each line to the PO and receipt, using item codes where they exist and descriptions where they don’t.
  3. Apply your tolerances from the rules sheet, exactly as written.
  4. Route only the exceptions, with the reason code and the three documents attached, to the person your rules name.
  5. Keep approvals where they are. Whoever approves today still approves; the software just puts a complete case in front of them.
  6. Write back to the system of record. The match result, hold status and approval go into your accounting or ERP system, so it stays the single source of truth and your audit trail lives where your auditors expect it.

If you are deciding which part of AP to start with, our lesson on going from a process map to automation shows how to score each step before you build anything.

What not to automate

  • Changing tolerances. Who may widen a tolerance is a control decision. Keep it with a person and log every change.
  • Accepting price increases. Software can flag them; a buyer should accept them.
  • Supplier bank detail changes. This is where invoice fraud happens. Verify any change by calling a known contact on a number you already hold, never one on the invoice or in the email.
  • Booking goods receipts from the invoice. It is tempting to fill a missing receipt with what the supplier invoiced. That removes the third document and turns a three-way match back into a two-way one.

What to measure

Measure before you change anything, so you can tell whether the change helped. Pick a recent month and count:

  • First-pass match rate: invoices that matched with no human touch, divided by all invoices.
  • Time to approve: from invoice received to approved for payment, as a median, not an average, because a few stuck invoices skew it.
  • Exceptions by cause: using the reason codes above. This shows where to fix the process upstream. If most exceptions are missing receipts, the fix is in the warehouse, not in AP software.
  • Early-payment discounts missed and late-payment charges paid, if your suppliers offer or charge them.

If you want to see where your own operations could start, the free Bonofici grader reads your company’s public pages and shows where to begin. For AI tools more generally, our AI readiness assessment helps you check whether a process is ready to automate.

Start with what your team already knows.

Book a 30‑minute call.We come back with the first three tools worth building, in writing.

Not ready for a call?

See where your company stands and which jobs are worth the most, from your public pages.