What is a three-way match in accounts payable?
Short answer
A three-way match checks a supplier invoice against the purchase order and the goods receipt, line by line, and releases payment only when all three agree within set tolerances.
Key takeaways
- A three-way match compares three documents before payment: the purchase order (what was ordered, at what price), the goods receipt (what arrived) and the invoice (what the supplier bills).
- The usual rule: the invoice price is checked against the order price, and the invoice quantity against the quantity received.
- Tolerances let small differences through without review. They are set as a percentage, an amount or both, and an invoice outside them is put on hold or blocked for payment.
- A two-way match leaves out the receipt and suits services or purchases with nothing to receive; a four-way match adds an inspection or acceptance step.
- Most exceptions come from a missing or late goods receipt, an outdated price on the order or a different unit of measure, not from supplier fraud.
What is a three-way match?
A three-way match is an accounts payable check that compares a supplier invoice with the purchase order and the goods receipt before the invoice is paid. If price and quantity agree, within set tolerances, the invoice is approved for payment. If they do not, the invoice is held until someone resolves the difference.
- The [purchase order](/procure-to-pay/purchase-order) says what the buyer ordered: items, quantities, unit prices and terms.
- The goods receipt says what arrived. A warehouse clerk or the requester records it in the system when the delivery is checked. For a service, it is the confirmation that the work was done.
- The invoice says what the supplier asks to be paid for.
A simple case: a school orders 100 boxes of paper at €20 a box. The delivery note says 100, but the caretaker counts 90 boxes and records a receipt for 90. The invoice asks for 100 boxes at €20. The match finds that the price agrees but the quantity does not: the school pays for 90 boxes, and the supplier either delivers the last 10 or sends a credit note.
The three-way match is one step of invoice processing, which also covers how invoices arrive, how their data is captured and how they are approved and paid. It sits near the end of the procure-to-pay cycle, after ordering and receiving and before payment. Some people call it 3-way matching or PO matching; invoice matching is the wider term that covers all levels.
Public buyers apply the same logic. US federal rules base payment on a proper invoice and on satisfactory contract performance; payment documentation includes a receiving report that shows the quantities accepted, and a proper invoice must carry the contract or order number and the line item number.
Disclosure: the author works as an Ivalua consultant. The ERP products named on this page are cited from their public documentation only, to show how matching is set up; this is not a comparison.
What does a three-way match compare?
The match works line by line. Each invoice line is linked to a purchase order line and to the receipts recorded against it. The table shows which document supplies each value and what the check is.
| Value | Purchase order | Goods receipt | Invoice | Check |
|---|---|---|---|---|
| Supplier | Supplier ordered from | Supplier who delivered | Supplier who bills | Same supplier record on all three |
| Order reference | PO number and line | PO number and line | PO number and line quoted | The invoice points to an open order line |
| Item | Item or service ordered | Item received | Item billed | Same item and same unit of measure |
| Quantity | Quantity ordered | Quantity received | Quantity billed | Billed is not more than received |
| Unit price | Agreed price | Not recorded, or copied from the PO | Price billed | Billed price within tolerance of the PO price |
| Extra charges | Freight or fees agreed on the PO, if any | Not recorded | Freight, fees, surcharges billed | No charge that the PO does not allow |
| Tax | Tax code or taxable flag | Not recorded | Tax billed | Tax consistent with the order |
Price comes from the order and quantity comes from the receipt. The invoice must agree with both: that is the whole idea of the three-way match.
ERP documentation describes the same rule. Microsoft’s documentation for Dynamics 365 Finance defines three-way matching as matching the invoice price to the purchase order price and the invoice quantity to the quantity on the product receipts selected for the invoice. Oracle’s Fusion Cloud documentation describes tolerances on both sides: the billed quantity is checked against the ordered quantity and against the received quantity.
How does the three-way match process work?
- Capture the invoice. The invoice is registered with its supplier, number, date, lines, amounts and the purchase order number.
- Find the order and the receipts. The system uses the PO number to find the order lines and the goods receipts posted against them.
- Compare. For each line, it compares the invoice price with the order price and the invoice quantity with the quantity received but not yet invoiced.
- Apply the tolerances. Differences within tolerance are accepted. Differences above tolerance put the invoice on hold or block it for payment.
- Resolve the exceptions. The person who owns the cause fixes it: the requester posts the missing receipt, the buyer corrects the order, or the supplier sends a credit note or a corrected invoice.
- Match again and release. Once the documents agree, the hold is released and the invoice moves to payment.
- Post and pay. The invoice is posted to the ledger and paid on its due date under the payment terms.
In most ERP and procure-to-pay systems the match runs automatically when the invoice is entered, and only the exceptions reach a person. That is what three-way match automation means in practice: the software matches the clean invoices, and people work on the rest. How much automation the wider process can take is discussed in procurement automation software.
What are matching tolerances, and how are they set?
A tolerance is the difference that the match accepts without review. Without tolerances, an invoice for €100.02 against an order for €100.00 would stop, and someone would spend more on reviewing it than the two cents are worth. Tolerances are set as a percentage, as an amount, or both.
Microsoft’s documentation gives a simple example: an order for 1,000 batteries at 1.00 each, a receipt for 1,000, and an invoice at 1.10 each. With a 5% price tolerance, a price of 1.05 would be accepted, but 1.10 is not: the invoice can be saved, but it waits until the difference is resolved. When a percentage and an amount are both set, a line that breaks either one is a discrepancy. SAP’s training for S/4HANA adds two details: an invoice above the upper limit can be posted but is automatically blocked for payment, and the whole invoice is blocked even if only one line has a variance.
| Line | Order | Received | Invoiced | Difference | Result |
|---|---|---|---|---|---|
| 1. Printer toner | 40 at €62.00 | 40 | 40 at €62.90 | +1.5%, +€36 | Passes: within 2% and under €50 |
| 2. Copy paper | 300 boxes at €21.00 | 300 | 300 at €21.40 | +1.9%, +€120 | Fails: under 2% but over €50 |
| 3. Desk chairs | 12 at €180.00 | 10 | 12 at €180.00 | 2 chairs not received | Fails: quantity billed above quantity received |
| 4. Delivery charge | Not on the order | — | €45.00 | Charge not allowed on the PO | Fails: charge not on the order |
One invoice, four lines, three exceptions with three different owners: the buyer for the paper price, the requester or the supplier for the missing chairs, and the buyer again for the freight. The amount cap stops a small percentage on a large line from passing unseen.
- Set tolerances in writing, approved by finance, with both a percentage and an amount cap. A 2% tolerance alone lets €20,000 through on a €1 million order.
- Vary them by category when needed: fuel or metals with daily prices may need a wider price tolerance than office supplies.
- Treat quantity differently from price. Paying for more than was received is rarely acceptable, so many organisations set no quantity tolerance for goods.
- Review the tolerances once a year, with the list of invoices that passed within them, to check that they are not hiding a supplier habit.
Two-way vs three-way vs four-way match: which one applies?
The number of “ways” is the number of documents compared. Most organisations use more than one level and choose by category, by supplier or by order line.
| Level | Documents compared | Typical use | What it does not catch |
|---|---|---|---|
| Two-way match | Invoice and purchase order | Services with no delivery to count, subscriptions, low-risk purchases | Billing for something that never arrived |
| Three-way match | Invoice, purchase order and goods receipt | Physical goods and services with a clear confirmation of work done | Goods that arrived but fail a quality check |
| Four-way match | Invoice, purchase order, goods receipt and inspection or acceptance | Items that must pass inspection: laboratory supplies, medical devices, parts for production | Little, at the cost of an extra step before payment |
| No invoice to match (evaluated receipt settlement) | Purchase order and goods receipt; the buyer creates the invoice | Stable, high-volume supply with agreed prices | Errors in the order price, which pass straight to payment |
Choose the lowest level that still protects the payment. Three-way is the common default for goods; two-way fits work that cannot be counted at delivery; four-way fits goods that must be accepted after inspection.
In most ERPs the level is a setting, not a separate process. In Oracle Fusion Cloud, for example, Payables enforces two-, three- or four-way matching according to the match approval level set for the supplier site, and its invoice tolerances decide when a difference with the order or the receipt puts the invoice on matching hold. The hold blocks payment until it is released.
Evaluated receipt settlement goes the other way: the supplier agrees not to send an invoice, and the buyer’s system creates it from the order and the receipt. SAP describes it as a way to settle goods receipts automatically that removes invoice variances, to be used only when buyer and supplier have a clear agreement on prices and orders are kept up to date. Oracle offers a similar process, called pay on receipt.
Invoices without a purchase order cannot be matched at all. They go to an approval route instead, which is slower and gives weaker control. How those invoices are handled is explained in invoice processing.
What happens when an invoice does not match?
An invoice that fails the match is not rejected straight away. It is put on hold, or blocked for payment, and sent to an exception queue. The cause decides who fixes it.
| Situation | Usual cause | Who acts | What happens next |
|---|---|---|---|
| The invoice arrives before the goods receipt | Goods delivered but not yet recorded, or not yet delivered | Requester or warehouse | The receipt is posted and the invoice matches again; if nothing arrived, the invoice waits |
| Price higher than the order | Supplier applied a new price list or forgot a discount | Buyer | If the contract allows the new price, the order is corrected; if not, the supplier sends a credit note |
| Quantity billed above quantity received | Partial delivery, or goods returned | Requester and supplier | The buyer pays for what arrived; the rest is paid after the next receipt or credited |
| Different unit of measure | Order in boxes, invoice in single units | Buyer | Units are aligned on the order or the supplier corrects the invoice |
| Charge not on the order | Freight, express delivery or a small-order fee | Buyer | Accepted if the contract allows it, otherwise removed by credit note |
| No PO number on the invoice | Supplier did not quote it, or no order was raised | Accounts payable | AP finds the order or returns the invoice to the supplier; a missing order goes to the non-PO approval route |
| Same invoice received twice | Sent by email and by post, or resent as a reminder | Accounts payable | The duplicate is rejected before payment |
Most exceptions are process gaps inside the buying organisation, such as late receipts and outdated order prices. Fixing those causes reduces the queue more than any rule change in accounts payable.
Time matters. A held invoice keeps running against its payment terms. In US federal contracts, a billing office must return an improper invoice within 7 days of receipt, with shorter periods for some perishable foods, and pays late-payment interest automatically when a proper invoice is paid after its due date. Private contracts and national late-payment laws set their own deadlines, so exception queues need an owner and a target time for each case.
Two habits weaken the match and are worth stopping. The first is creating a purchase order after the invoice has arrived, so that the invoice has something to match: the control then checks a document written to agree with it. The second is posting a goods receipt simply to release an invoice, without checking what was delivered.
How does the three-way match work in accounting?
In accounting, the goods receipt and the invoice are two separate postings, and the match connects them. In SAP, for example, the goods receipt debits stock or expense at the order price and credits a goods received / invoice received (GR/IR) clearing account. When the matched invoice is posted, that clearing account is cleared and the amount owed to the supplier is credited to accounts payable.
Items left open on the GR/IR account show where the three documents disagree: goods received but not yet invoiced, or invoices posted for goods not yet received. Finance teams review this account at month end. A large or old open balance is often the first sign that receipts are entered late or that matching exceptions are not being resolved.
What are the best practices for three-way matching?
- Record receipts on the day of delivery. A late receipt is the most common reason a correct invoice fails the match.
- Keep order prices current. Load contract prices and catalogue prices into the order, so that the invoice is compared with the price actually agreed.
- Use the same units of measure on the item record, the order and the supplier’s invoice, or agree a conversion.
- Ask suppliers to quote the PO number and line on every invoice, and say so in the purchase order terms.
- Separate duties. The person who orders, the person who records the receipt and the person who approves payment should not be the same person for the same purchase.
- Give each exception an owner and a deadline, and report the queue by cause, not just by number.
- Measure the first-time match rate: the share of invoices that match with no human action. It shows whether the problem sits in purchasing, receiving or with suppliers.
A three-way match reduces the risk of paying for goods that were never ordered or never delivered, or of paying more than the agreed price. It does not prove that the price was a good one or that the supplier is genuine; those checks belong to sourcing and to supplier onboarding.
Questions
Which documents are involved in a three-way match?
Three documents: the purchase order, which shows what was ordered and at what price; the goods receipt, which shows what was delivered; and the supplier invoice, which shows what is billed. The invoice price is checked against the order and the invoice quantity against the receipt.
Is a three-way match required by law?
Generally no. It is an internal control that organisations choose, often because auditors expect it. Some public bodies have payment rules with the same effect: US federal agencies, for example, pay on a proper invoice backed by a receiving report showing the quantities accepted.
Can services be three-way matched?
Yes, when someone confirms that the work was done. The confirmation, recorded in the system, takes the place of the goods receipt. For services billed monthly at a fixed fee, or where there is nothing to count, many organisations use a two-way match instead and rely on the budget holder’s approval.
What is the difference between a two-way and a three-way match?
A two-way match compares the invoice with the purchase order only, so it checks the price and the quantity ordered. A three-way match adds the goods receipt, so the organisation pays only for what actually arrived. A four-way match adds an inspection or acceptance record.
Does three-way matching prevent invoice fraud?
It blocks some kinds: billing for goods never delivered, billing above the agreed price, or billing an order that does not exist. It does not stop a fake supplier set up with a real order, or a changed bank account. Those risks need supplier onboarding checks, bank detail verification and separation of duties.
New guides on the procure‑to‑pay line
One short email when a guide on this line is added or revised. Nothing else.
Coming soon: sign-up opens with the first email.