3 Way Match Accounting: What It Is and Why It Matters

A 3 way match in accounting is the control that compares three documents before an invoice gets paid: the purchase order, the receiving report, and the supplier invoice. If the quantities, prices, and line items agree across all three, the invoice is approved for payment. If any one of them disagrees, the invoice becomes an exception and a person investigates before money leaves the business.

Last updated July 2026.

It is a simple idea that survives because it works. You said you would buy it, someone confirmed it actually arrived, and the supplier is billing you for it. Three independent records, created by three different people at three different moments, all agreeing. That is much harder to fake and much harder to get wrong by accident than a single invoice sitting in an inbox with an approval attached.

What are the three documents in a 3 way match?

Each of the three documents answers a different question, and the control only works because they come from different sources. If the same person creates all three, you have paperwork rather than a control.

The match itself is two comparisons. Quantity billed against quantity received, and price billed against price ordered. A clean match means you are paying the agreed price for the quantity that actually showed up. Nothing else in accounts payable gives you both of those facts at once.

What is the difference between 2 way match and 3 way match?

A 2 way match compares the invoice to the purchase order only. It confirms that you were billed what you agreed to pay, but it proves nothing about whether the goods arrived. A 3 way match adds the receiving report, so it also confirms delivery. A 4 way match adds an inspection or quality acceptance record, which matters when receiving the item is not the same as accepting it.

Most organizations run more than one of these rather than picking a single policy. Goods get a 3 way match. A monthly software subscription gets a 2 way match, because there is no receiving report to produce and inventing one adds work without adding assurance. Matching every spend category the same way is the most common reason an AP team ends up drowning in exceptions that mean nothing.

Why is 3 way matching important?

It catches the two things that quietly cost real money. The first is overpayment: being billed for twelve units when ten arrived, or at $54 a unit when the agreed price was $48. These are usually honest errors, they are individually small, and without a match nobody ever notices them, because an invoice that looks reasonable gets approved.

The second is fraud, and this is where the control earns its reputation. Fictitious vendor schemes work by getting an invoice into the payment run for something that was never ordered and never delivered. A 3 way match blocks that by construction, because a fabricated invoice has no purchase order behind it and no receiving report confirming an arrival. The separation of duties is doing the work: the person who orders, the person who receives, and the person who pays are three different people, and collusion between all three is much rarer than a single bad actor.

It also produces the evidence trail auditors ask for. When an auditor tests your purchasing cycle, they select invoices and ask you to show the authorization and the proof of receipt. A team running 3 way matching answers that in minutes. A team that approves invoices on judgment spends a week reconstructing it.

What is a tolerance in 3 way matching?

A tolerance is the acceptable variance that lets an invoice pass without manual review, set as a small percentage or dollar amount. It exists because a strict match fails on trivia: a $0.03 rounding difference, a freight charge, a partial delivery where 98 of 100 units arrived. Without tolerances, your exception queue fills with items nobody needs to see.

Setting them is an empirical exercise, not a policy decision made once. Look at the exceptions you resolved last quarter. If most of them were investigated and then approved with no change, your tolerances are too tight and you are paying people to rubber-stamp noise. If meaningful variances cleared without review, they are too loose. Many teams set a percentage tolerance for price and a unit tolerance for quantity, then review the settings twice a year. Keep the dollar cap separate from the percentage: 5% of a $200 order is noise, and 5% of a $200,000 order is not.

What happens when a 3 way match fails?

The invoice goes on hold as an exception and does not enter the payment run until someone resolves it. The exception itself tells you which comparison broke, and there are only a handful of causes worth knowing.

Two of those five are not accounts payable problems at all. Missing purchase orders and missing goods receipts come from upstream behavior, and no amount of AP effort fixes them. The single biggest driver of matching exceptions is invoices arriving without a valid PO, which is why the enforcement point has to be the requisition, not the invoice. Teams that make it easy to raise and track a purchase order before the spend happens see their exception volume fall without changing anything in AP itself. Late receipting is the same shape of problem: if goods receipts get posted within a day of delivery rather than at week end, an entire exception category disappears.

How do you automate 3 way matching?

Automation captures the invoice data, compares it against the PO and the receipt automatically, releases anything inside tolerance, and routes only genuine exceptions to a human. The AP team stops matching and starts resolving, which is a much better use of the same headcount. The three documents still have to exist and still have to be created by different people, because the control is the separation of duties and software does not replace that.

Where the matching itself runs depends on your stack. A mid-market ERP already does it natively: Business Central and Sage Intacct both carry PO, receipt, and invoice records with tolerances you configure, so the gap is rarely the match and almost always the exception queue nobody owns.

Be realistic about what changes. Automated matching removes the mechanical comparison work and it makes the exception queue visible, which is often uncomfortable at first because the exceptions were always there and nobody was counting them. What it does not do is fix a purchasing process where half the spend never sees a PO. If that is your situation, the software will simply show you the problem faster and more precisely.

How 3 way matching relates to reconciliation

Three way matching is a control on money going out before it is paid. Reconciliation is the check that what actually left the bank agrees with what your ledger says. They are different jobs at different points in the cycle, and each one catches things the other cannot.

A 3 way match will not catch a payment that was approved correctly and then processed twice, or a bank fee nobody booked, or a supplier payment that cleared for a different amount than the one approved. Those only surface when you tie the bank statement back to the ledger. This is where a duplicate payment gets caught: it clears the match on the way out because the underlying invoice was legitimate, and then shows up as two ledger entries competing for one bank line during the tie-out. Our guide to common causes of reconciliation discrepancies covers that pattern and the others in detail.

If AP volume is the reason your close runs long, both halves are worth automating. Reconciler handles the second half: it connects your bank feeds, corporate cards, payment processors, and your QuickBooks, Xero, NetSuite, Sage Intacct, or Business Central ledger read-only, matches both sides automatically, and explains every match in plain English. It never moves money and never posts an entry on its own, so a person still approves every correction. The bank reconciliation software page covers how the matching and the exception list work, discrepancy detection covers what gets flagged, and audit trail covers the evidence side that auditors ask about alongside your matching controls.

If you are tightening controls generally, the month end close checklist puts both the payables review and the reconciliations in the order most teams find works, and reconciliation for controllers covers the review and sign-off layer above them.

Is 3 way matching required?

No accounting standard names it as a requirement. GAAP governs how you recognize and report transactions, not which internal controls you use to authorize them. What does create pressure is everything built on top: SOX requires public companies to maintain and test effective internal control over financial reporting, and matching is one of the standard controls tested in the purchasing cycle. Auditors, lenders, and acquirers all expect to see something serving this purpose.

For a private company below that threshold, treat it as a decision about risk and volume. If you place a handful of purchase orders a month and the owner sees every invoice, formal 3 way matching adds process for little gain. Once purchasing is spread across several people, or spend runs through dozens of vendors a month, the control pays for itself the first time it catches a duplicate invoice or a price that quietly went up.