Three-Way Matching Explained

Three-way matching is the control that stops an accounts payable team from paying for things it never ordered or never received. It sounds like back-office paperwork, and it is, but it is also the single check that catches overbilling, duplicate charges, and supplier fraud before any money leaves the bank. Most finance teams know they should do it on every PO-backed invoice. The hard part is doing it fast enough that invoices still get paid on time.

This guide explains what three-way matching is, which documents it compares, how the process runs step by step, and how it differs from two-way and four-way matching. It also covers matching tolerances, why matches fail, and how teams automate the slow parts without rebuilding their accounting system.

What is three-way matching?

Three-way matching is an accounts payable check that compares three documents, the purchase order, the receiving report, and the supplier invoice, before an invoice is approved for payment. It confirms that what you ordered, what you actually received, and what you are being billed for all agree on quantity, price, and terms. Only matched invoices get paid.

The point is simple: you should pay only for goods or services you authorized and received. When all three documents line up within an acceptable range, the invoice is cleared. When they do not, it is held as an exception and reviewed before any money moves. That one gate prevents a surprising share of the costly errors that slip through when an invoice is approved on its own.

Which three documents are required for three-way matching?

Three-way matching requires the purchase order, the goods receipt (also called a receiving report or GRN), and the supplier invoice. The purchase order records what was ordered and at what price, the goods receipt records what was actually delivered, and the invoice records what the vendor is charging. The match confirms all three agree before payment.

Each document answers a different question. The purchase order says what you committed to buy. The receiving report, created by whoever accepts the delivery, says what showed up and in what condition. The invoice says what the supplier expects to be paid. A clean match means a manager authorized the spend, the warehouse confirmed delivery, and the billed amount matches both.

The middle document carries the most weight, because it is the only one written by someone inside your business who physically handled the goods. Our guide to the goods received note covers what it should contain, who is allowed to raise it, and why a supplier delivery note is not an acceptable substitute.

How does the three-way matching process work?

The three-way matching process runs in five steps: create the purchase order, receive and record the delivery, receive the supplier invoice, match all three documents on quantity and price, then approve the invoice or flag it as an exception. Matched invoices move to payment, and discrepancies are held for review before any money is released.

1. Issue the purchase order

Purchasing creates a PO that specifies the items, quantities, agreed prices, and delivery terms, then sends it to the supplier. This is the baseline every later document is checked against, so accuracy here saves work downstream.

2. Record the delivery

When the goods arrive, the receiving team inspects the shipment and creates a goods receipt noting the quantity and condition of what was delivered. This is the evidence that you actually got what you ordered, not just that you were billed for it.

3. Capture the supplier invoice

The vendor sends an invoice listing the items, quantities, unit prices, tax, and total. The AP team gets this document into the system and reads its details into structured data so they can be compared line by line against the PO and the receipt.

4. Match the three documents

AP cross-checks the invoice against the PO and the goods receipt: do the quantities agree, do the unit prices match the agreed prices, are the line items the same? A laptop order billed for 100 units when the receipt shows only 80 delivered is exactly what this step is built to catch.

5. Approve or escalate

If everything matches within tolerance, an authorized approver clears the invoice for payment. If something is off, the invoice becomes an exception: held, routed to the right person, and resolved with the vendor before payment is scheduled. Our guide to invoice exception handling covers how teams clear those holds without stalling the payment run.

What is the difference between two-way, three-way, and four-way matching?

Two-way matching compares the purchase order and the invoice. Three-way matching adds the goods receipt to confirm delivery. Four-way matching adds an inspection or quality report on top of that. Each level adds a document and a layer of assurance, so you pick the level that fits the purchase and its risk.

Most companies use two-way matching for services where there is nothing to physically receive, three-way matching for goods, and four-way matching only where a failed inspection would be expensive, such as pharmaceuticals or machined parts. You do not need the heaviest check on every purchase, just on the ones where the risk justifies it. Because three-way matching lives or dies on part numbers and quantities, the industries that lean on it hardest have their own capture patterns: see invoice extraction for manufacturing for BOM-heavy supplier bills and invoice extraction for retail for high-SKU merchandise deliveries.

What are matching tolerances in accounts payable?

Matching tolerances are the small variance thresholds, set as a percentage or a dollar amount, that let minor differences pass without manual review. A tolerance of 1% or $5, for example, stops a rounding difference or a tiny freight charge from holding up an otherwise valid invoice. Anything outside the threshold becomes an exception.

Tolerances exist because perfect matches are rare in the real world. Shipping fees, currency rounding, partial deliveries, and minor price changes create small gaps on legitimate invoices. Set tolerances too tight and your team drowns in trivial exceptions. Set them too loose and real overcharges slip through. Most teams tune the numbers by vendor and spend category over time.

What causes three-way matching failures?

Three-way matching fails when the three documents disagree: the invoice quantity exceeds what was received, the billed price differs from the PO price, a line item is missing or extra, or one document never arrived. A missing goods receipt is one of the most common causes, because the delivery was accepted but never recorded in the system.

Other frequent culprits are partial shipments billed in full, duplicate invoices from the same vendor, unit-of-measure mismatches (cases versus individual units), and tax or freight charges that were not on the original order. Each of these is a real problem worth catching. The trouble in a manual process is that finding them means comparing documents across spreadsheets, email threads, and paper files, where genuine errors hide among harmless ones.

Why is three-way matching important?

Three-way matching matters because it is the cheapest point to catch a bad payment, before the money is gone. It prevents duplicate payments, overbilling, and invoices for goods that were never delivered, and it is a frontline defense against payment fraud, which 76% of businesses reported experiencing in 2025. Recovering an overpayment after the fact is far harder than blocking it.

The savings are concrete. If a vendor bills you for 100 laptops at $1,000 each but the receiving report shows only 80 arrived, the match flags a $20,000 discrepancy before payment. Beyond fraud and error prevention, a consistent matching process gives you a clean audit trail, stronger spend control, and the documentation auditors expect. That is also why matching sits at the center of what invoice processing involves from end to end.

How do you automate three-way matching?

You automate three-way matching by letting software read each invoice into structured data and compare it against the PO and goods receipt automatically, clearing matches within tolerance and routing only exceptions to a person. OCR and AI extract the invoice fields and line items, the system runs the comparison in seconds, and your team reviews the handful that do not match.

The slow part of manual matching is not the comparison itself, it is reading each invoice and keying its details so they can be compared. Invoice data capture software removes that step by pulling the vendor, invoice number, totals, and every line into clean data, and accurate line-item extraction is what makes quantity-and-price matching possible at all. Modern extraction reaches about 99% accuracy on line-item data, which is why automated matching catches discrepancies people miss.

From there, the structured data flows into your matching engine. A broader invoice processing software setup or full accounts payable automation software can run the match against your ERP, apply tolerances, and hold only the exceptions. If your goal is also to automate the approval and payment steps after matching, that is the natural next layer to add once your invoice data is clean. Start with reliable extraction, because no matching engine can compare numbers it cannot read.

How does three-way matching fit into your ERP?

In most accounting and ERP systems, three-way matching is a built-in control on PO-backed invoices: the system stores the PO and goods receipt, then checks each incoming invoice against them before posting it as payable. NetSuite, QuickBooks Enterprise, Sage, and Microsoft Dynamics all support some form of PO matching with configurable tolerances.

The gap is usually getting invoice data into the ERP in the first place. Suppliers send PDFs and scans, not structured records, so someone has to turn each document into fields the system can match. Feeding your ERP clean, extracted invoice data is what lets its matching control actually run, instead of sitting idle while invoices pile up waiting to be keyed by hand.

Once the data is clean, the comparison itself belongs to software. Which fields it checks, what tolerances real US finance teams set, why so many invoices fail to match, and where the match actually runs (your ERP, an AP platform, or a spreadsheet) are covered on our invoice matching software page. For the invoices that arrive already structured, such as the EDI 810 files large retailers require, no capture step is needed at all.

When the match fails because a field is missing

A large share of failed matches are not disagreements about price or quantity at all. They are invoices where the PO number was never captured, the line items were summarized into a single total, or the tax was folded into the amount, so the ERP has nothing to compare. Our guide to fixing missing invoice data covers which fields go missing during manual keying and how complete capture keeps them from becoming exceptions in the first place.

When a mismatch is real rather than a data gap, the conversation moves to the supplier. Having the original line items, quantities, and totals as structured data is what makes that conversation short, and the approach is laid out in resolving vendor payment disputes with accurate invoice records.

Three-way matching is not glamorous, but it is one of the highest-return habits in accounts payable. Get the three documents to agree before you pay, set sensible tolerances, and automate the reading so your team spends its time on real exceptions rather than retyping invoices. You can extract the invoice data you need to match against your POs in seconds using the tool at the top of this page.