Invoice Matching: 2-Way, 3-Way and 4-Way Matching Explained
What invoice matching is, how 2-way, 3-way and 4-way matching differ, a worked sample with numbers, real tolerance rules, and the cases that break matching.
Quick answer
Invoice matching is the accounts payable check that a supplier invoice agrees with the purchase order, and often with the goods receipt, before it is paid. A 2-way match compares the invoice to the PO, a 3-way match adds the goods receipt, and a 4-way match adds an inspection or acceptance record. Invoices outside the agreed tolerances are held as exceptions until someone resolves them.
Why listen to us: ECIT Digital extracts line-item data from invoices, purchase orders and delivery notes, so the matching in your ERP has clean data to work with. Our people check what the AI is unsure about, and we guarantee 99.8% accuracy on the data we deliver.
Last week I ordered six avocados online. Four arrived, I was charged for six, and one of the four was, as far as I can tell, a rock [a very convincing rock, to be fair].
Without meaning to, I had just run a 4-way match on my groceries, and failed it. Invoice matching is the same idea for your AP team, with fewer avocados and more zeros. It is one step in the wider accounts payable process, and this guide goes deep on it: the three types, a worked example with numbers, tolerances, and the cases that break it [no avocados were harmed, except the rock].
2-way vs 3-way vs 4-way matching, at a glance
The short version, for the reader with an approval queue breathing down their neck [it can wait two minutes, probably].
| 2-way match | 3-way match | 4-way match | |
|---|---|---|---|
| Compares | Invoice and PO | Invoice, PO and goods receipt | Invoice, PO, goods receipt and inspection |
| Answers | Did we order this, at this price? | Did it actually arrive? | Was it accepted as good? |
| Catches | Wrong prices, items never ordered | Billing for goods not received | Paying for damaged or rejected goods |
| Typical use | Services, low-risk spend | Physical goods | Regulated, high-value or quality-critical goods |
What is invoice matching?
Invoice matching is the check AP runs before money leaves the building: does this invoice agree with what we ordered and received? If yes, it moves on to payment. If no, it waits, like a teenager outside a nightclub without ID.
The Research Foundation for SUNY sums up the rule plainly: "The invoices must meet matching tolerances or a hold is placed on the invoice and payment cannot be made until the hold is resolved or manually released". That hold is the whole point [it is also the whole frustration].
It is not a new idea, either. Back in 1995, the US GAO listed as a basic control that "payment is initiated only after receipt of goods and services and is authorized only after matching the types and quantities of goods and services received and accepted with those ordered". Government auditors were doing 3-way matching before most of us had email [some of us still miss fax].
Which documents each match compares
Each extra "way" adds one more document to the comparison. Think of it as adding one more friend to check the restaurant bill [the friend who brought a calculator].
Oracle's PeopleSoft documentation describes it the same way: "Two-way matching compares vouchers and purchase orders if the Receiving Required option for the purchase order is Do Not Receive or Optional", while 3-way adds receipts and 4-way adds inspections. Which one applies is usually set per PO or per line, not once for the whole company.
Services are the classic 2-way case, because nobody signs a goods receipt for a consultant. Rockefeller University's purchasing guide puts it simply: "A two-way match is conducted when there is no receiving report" [the consultant did not arrive in a box].
A worked invoice matching example, with numbers
Here is one fictional order, run through all three types of match, so you can see what each one catches. Spoiler: the cheap check misses the expensive mistake.
| Document | What it says |
|---|---|
| Purchase order PO-7731 | 100 boxes of printer paper at $24.00 each (total $2,400) |
| Goods receipt | 90 boxes received |
| Inspection | 5 of the 90 boxes damaged, 85 accepted |
| Supplier invoice | 100 boxes at $24.50 each (total $2,450) |
Fictional example.
| Match | What it compares | Result |
|---|---|---|
| 2-way | Invoice vs PO: 100 boxes billed, 100 ordered. Price $24.50 vs $24 on the PO, about 2% higher | Passes, if the price tolerance is 3%. The invoice would be paid in full |
| 3-way | Adds the receipt: 100 billed, 90 received | Exception. 10 boxes billed but never delivered, $245 |
| 4-way | Adds the inspection: 85 accepted | Exception. Only 85 boxes should be paid for |
Fictional example, with an illustrative 3% price tolerance.
So the 2-way match would have paid $2,450 for paper the company only partly received [the avocado rock strikes again]. The 4-way match says pay for 85 boxes, and the price difference still needs a yes from purchasing or a credit note from the supplier.
Our guide to purchase orders vs invoices has a simpler 2-way and 3-way example, if you want the gentle version first.
Matching tolerances: how close is close enough?
No invoice matches to the cent forever, so companies set tolerances, the small differences they will accept without a fuss. Too tight, and AP drowns in exceptions over a rounding error [hello, one-cent hold].
Too loose, and suppliers learn they can creep prices up. Real public policies show what this looks like in practice:
| Organization | Rule (published) |
|---|---|
| University of Connecticut | General matching tolerance of 10%/$250, and no tolerance at all for capital projects |
| Virginia Tech | Overages above $100 on a line item need written approval before payment |
Sources: UConn Accounts Payable training, 2024 and Virginia Tech procedure 20310f.
- Price tolerance: how far the invoiced unit price may sit above the PO price.
- Quantity tolerance: how many more units may be billed than were ordered or received. Many companies allow none.
- Line or invoice level: check each line, or only the total. Line level catches more, because errors can cancel out in the total.
The cases that break invoice matching
Clean, one-PO-one-delivery-one-invoice orders are the easy part. Here are the ones that make AP clerks stare out the window [usually around 4pm on a Friday].
| Case | Why it breaks | What works |
|---|---|---|
| Partial deliveries | One PO, several receipts and several invoices | Match each invoice line to what has been received so far, not the full PO |
| Split or combined invoices | One invoice covers several POs, or one PO gets many invoices | Match at line level, with the PO number on every line |
| Unit of measure | PO in cases, invoice in units (1 case of 12 vs 12 each) | Convert units in the ERP, or ask suppliers to invoice in PO units |
| Services | No goods receipt to match against | 2-way match, plus a service confirmation from the person who ordered it |
| Non-PO invoices | Nothing to match against at all | Route to the budget owner for approval and coding, and push for POs next time |
The unit of measure one is my favourite. I once ordered "1 bag" of lemons and received one lemon, in a bag [technically correct, the worst kind of correct].
What happens when an invoice does not match
A mismatch is not a failure, it is the control doing its job. The question is how fast someone fixes it.
Hold the invoice
The invoice is blocked for payment, with the reason recorded.
Find the cause
Price, quantity, receipt missing, wrong PO number or a typo in the captured data.
Send it to the right person
Purchasing for price, the receiver for quantities, the supplier for a credit note.
Fix the source
Update the PO, post the missing receipt, or get a corrected invoice.
Release and pay
Re-run the match, then release the hold.
In the US federal world this is written into the rules: FAR 32.905 says payment "will be based on receipt of a proper invoice and satisfactory contract performance". Your company may be less formal, but the logic is the same [with fewer acronyms, hopefully].
Why invoice matches fail
Exceptions are common and expensive. Ardent Partners' Andrew Bartolini called them "the bane of the modern AP department", and he has seen a lot of AP departments [and presumably a lot of rocks].
In Ardent's 2015 survey, the top cause was "a discrepancy between PO and invoice information (68%)", followed by a lack of a purchase order at 37%. Ardent's State of ePayables 2025 put the average exception rate at 18.4% of invoices, and 11.1% for best-in-class teams.
Some of those discrepancies are real: a supplier raised a price, or a delivery came up short. Others are not real at all, because the invoice data was captured wrong [a 1 read as a 7 is a very expensive typo].
Clean data in, clean matches out
Your ERP's matching engine is only as good as the numbers it is given. If the PO number, quantity or unit price is misread, you get false exceptions, or worse, false matches.
Line-item data your matching can trust
ECIT Digital extracts line-item data from invoices, purchase orders and delivery notes, in any format. Our team checks every field the AI is unsure about, and the data goes into your ERP with 99.8% accuracy guaranteed. You pay per document, with no license. See purchase order matching.
Matching is one step of many. If you are automating the whole flow, our guide to accounts payable automation best practices covers the order to do it in, and our EDI invoice guide covers the advance ship notices that make 3-way matching easier.
Fewer false exceptions
Invoice and PO data captured right, 99.8% accuracy guaranteed
Our AI reads invoices, POs and delivery notes, our team checks what the AI is unsure about, and clean line-item data lands in your ERP. You pay per document.
As for the avocados: I got a refund for two, and kept the rock as a paperweight. It now holds down a stack of invoices, all fully matched [it has finally found its purpose].
Sondre Bratlandsmo
November 5, 2026
Book free live demo
Learn how the ECIT Digital solutions can help you with the help from one of our experts.
Frequently asked questions
Invoice matching is the accounts payable check that a supplier invoice agrees with the purchase order, and often with the goods receipt, before it is paid. Invoices that do not match within the agreed tolerances are put on hold as exceptions until someone resolves them.
A 2-way match compares the supplier invoice with the purchase order, checking items, quantities and prices. It is common for services and low-risk purchases where there is no goods receipt to match against.
A 2-way match compares the invoice with the purchase order. A 3-way match also compares it with the goods receipt, so it catches invoices for goods that were ordered but never delivered.
A 4-way match compares the invoice, the purchase order, the goods receipt and an inspection or acceptance record. It is used when goods must be inspected and accepted before payment, for example in regulated or quality-critical purchasing.
A matching tolerance is the small difference between the invoice and the purchase order or receipt that a company will accept without holding the invoice, such as a percentage or a dollar amount on price. Each company sets its own tolerances.
Common reasons are price differences, billing for more than was received, a missing or wrong PO number, partial deliveries, different units of measure, and invoice data captured incorrectly. Accurate line-item capture reduces false exceptions.
Relevant articles
What Is Cash Application? How the Process Works, Step by Step
What Is an EDI Invoice? The EDI 810 Format, Explained Line by Line
