What Is a 3-Way Match in Accounts Payable?

A 3-way match is an accounts payable control that compares three documents before a supplier invoice is paid: the purchase order, the goods receipt, and the supplier invoice. When the vendor, quantities, and prices agree across all three, the invoice is approved for payment. When they do not, it is flagged for review. The goal is simple: pay only for what you ordered, actually received, and agreed to pay.

Last updated July 2026.

If your team still lines these documents up by hand, the slowest part is usually reading the purchase order itself: typing the PO number, vendor, and every line item off a PDF or a scan so it can be checked against the invoice. That is the step this tool removes. Upload the PO above and you get the PO number, vendor, ship-to, line items, and totals as clean Excel, CSV, or JSON in seconds, ready to match.

The three documents in a 3-way match

Each document answers a different question, and matching them together is what makes the control work.

• Purchase order (PO): what you ordered. It lists the vendor, the agreed quantities, the unit prices, and the terms. The PO is the authorization that a purchase was approved before it happened.
• Goods receipt (delivery receipt): what you received. Created when the shipment arrives, it confirms the items and quantities that actually showed up at the dock.
• Supplier invoice: what you are being billed. The vendor's formal request for payment, listing items, amounts, and payment terms.

A 2-way match skips the goods receipt and compares only the PO and the invoice. That is common for services or non-inventory spend where there is nothing to receive. A 3-way match adds the receipt, which is why it is the standard for physical goods. On services work the order itself is often scoped by a statement of work rather than a line-item list, and purchase order vs statement of work covers how the two documents divide the job.

How the 3-way match process works, step by step

The mechanics are the same whether you do it manually or in an ERP:

1. Purchase order is issued. Procurement raises a PO with the vendor, line items, quantities, and prices, and sends it to the supplier.
2. Goods are received and logged. When the order arrives, the receiving team records the quantities received against the PO.
3. Invoice arrives. The supplier sends an invoice referencing the PO number.
4. The three are compared. AP checks that the vendor, item quantities, and prices on the invoice agree with the PO and the receipt, within a set tolerance.
5. Approve or flag. A clean match is approved for payment. A mismatch (a price above the PO, a quantity billed but not received, a duplicate) is held and routed for investigation.

Why accounts payable teams use 3-way matching

The control exists to stop money leaving for the wrong reasons. Comparing the three documents catches overcharges where the invoice price is higher than the agreed PO price, quantities billed for goods that never arrived, duplicate invoices submitted twice, and fraudulent invoices for orders that were never placed. It also creates a clean audit trail: every payment is tied back to an approved order and a confirmed delivery, which is exactly what auditors look for. For a deeper look at how a PO differs from the invoice it is matched against, see our guide to the purchase order vs invoice.

Where the manual version slows down

In theory the match is a quick comparison. In practice the bottleneck is data capture. Someone has to read the purchase order and the invoice and get the numbers into a system that can compare them. POs arrive as PDFs, email attachments, scans, and photos, with a different layout from every supplier. Line items wrap across rows, tables split across pages, and a faded scan has no text to copy at all. Typing all of that by hand is slow and it introduces the exact transcription errors that then look like a mismatch.

That is the part worth automating first. Turning the PO into structured fields, one row per line item, means the comparison itself becomes trivial. See how we handle the hardest part of that in purchase order line item extraction, and the broader case for cutting hand entry in reducing purchase order processing costs.

How automated PO data extraction supports the match

To be clear about scope: this tool does not perform the 3-way match itself, and it does not route approvals. What it does is the data-capture step that feeds the match. You upload a purchase order and the AI returns the PO number, vendor, ship-to and bill-to, every line item with SKU, quantity and unit price, dates, terms, and totals, exported to Excel, CSV, Google Sheets, JSON, or an API. Your ERP or AP system then runs the comparison against the receipt and invoice. For teams that want to automate the full payable workflow, including approvals and matching logic, a dedicated accounts payable automation platform handles that side, while the invoice half of the match can be captured the same way with an invoice data extraction tool. We focus on getting clean, match-ready purchase order data out of the document fast. For AP-specific workflows, see purchase order extraction for accounts payable.

3-way match vs 2-way match vs 4-way match

The difference is how many documents you compare. A 2-way match compares the PO and invoice only. A 3-way match adds the goods receipt. A 4-way match adds an inspection or quality-acceptance document on top, common in manufacturing where received goods must pass QA before the invoice is cleared. More documents mean tighter control and more handling, so most companies use 3-way for physical goods and 2-way for services. For a full breakdown of when each fits, including tolerances and the reasons matches fail, see 2-way match vs 3-way match, and for how the allowed variance is configured, purchase order tolerance.

The accounting control behind a 3-way match

The match is more than a payment check; it is an internal control that keeps your books accurate under accrual accounting. When goods are received, the liability is recorded at that moment, not when the invoice arrives. The goods receipt drives that entry, usually through a goods-receipt or invoice-receipt clearing account that is credited at receipt and cleared when the matching invoice posts. If the invoice equals the received value, the account nets to zero; any leftover balance flags a discrepancy for someone to investigate. That mechanism is what keeps period-end payables and inventory correct.

The match also supports segregation of duties, a core control auditors look for. Purchasing raises the purchase order, the receiving team logs the goods receipt note, the vendor issues the invoice, and accounts payable approves the payment. Because no single person controls all three documents, it is far harder for an error or a fraudulent invoice to slip through unnoticed. Accounting systems handle the match differently: NetSuite and SAP support native three-way matching with configurable tolerances, while QuickBooks and Xero offer limited native matching (getting the order in cleanly first is what a purchase order to Xero import does) and often rely on an add-on.

What are 3-way match tolerances?

A 3-way match tolerance is the small difference a company will accept between the invoice, the purchase order, and the receipt before it holds the invoice as an exception. Most US finance teams set both a dollar limit and a percentage, for example accept a variance up to $25 or 2 percent of the line, whichever is lower. Anything inside the band posts automatically; anything outside it goes to a person.

Tolerances exist because a strict match creates more work than it prevents. Rounded freight, a cent of tax rounding, or a supplier shipping 101 units against an order of 100 will all fail an exact comparison, and none of them are worth an email. Set the band too wide, though, and price creep walks straight through the control. Reviewing the exception log every quarter tells you whether your thresholds are set where the real errors are.

The match is one stage inside a longer chain. To see where it sits between the order and the payment, read the full purchase order to invoice process.

What is 3-way matching in procurement?

In procurement, 3-way matching is the check that protects the terms the buyer negotiated. Procurement issues the purchase order at an agreed unit price and quantity, and the match is what confirms the supplier actually invoiced those terms rather than a higher price or a larger quantity. Without it, a negotiated contract rate is an intention, not an outcome. When goods arrive but the invoice has not posted yet, the open value sits in the goods received not invoiced accrual until the match clears.

This is why the line-level data on the PO matters so much. Matching on header totals alone hides a supplier who overcharged on one line and undercharged on another. Capturing the item table properly, through purchase order line item extraction, is what makes line-level price verification possible at all.

Common 3-way match exceptions and how to clear them

An exception is any invoice that does not agree with the purchase order and the goods receipt inside your tolerance, so it is held instead of paid. Most fall into a handful of repeat patterns, and knowing them tells you which document to check first.

• Quantity mismatch. The invoice bills for more units than the goods receipt confirms. Usually a partial delivery that was invoiced in full, or a receipt that was never posted. Check the receiving record before you touch the invoice.
• Price mismatch. The invoiced unit price is higher than the price on the purchase order. This is the exception that protects a negotiated rate, and it is only catchable when you match at the line level, not on header totals.
• Missing goods receipt. The invoice arrives before receiving logs the delivery, so there is nothing to match against. The value sits in the goods received not invoiced accrual until the receipt posts.
• Duplicate invoice. The same invoice is submitted twice, often once by email and once by mail. A clean match against a single PO and receipt is what stops the second payment.
• Unit-of-measure mismatch. The PO is in cases and the invoice is in each, so the quantities look wrong even though the delivery was correct. A conversion, not a real discrepancy.
• Freight or tax not on the PO. Charges the buyer expected but did not put on the order. Teams handle these with a tolerance or a non-PO charge rule rather than a hard hold.

The volume of exceptions is what makes manual matching expensive, because each one is a person opening three documents and reconciling them by hand. Feeding clean, line-level PO data into your matching step is the difference between an exception queue you clear in an afternoon and one that never empties. That is the whole premise behind invoice matching automation: capture the documents as structured data first, then let the system compare them.

Frequently asked questions

What is a 3-way match in simple terms?

A 3-way match means checking three documents against each other before paying a bill: the purchase order (what you ordered), the goods receipt (what you got), and the supplier invoice (what you are billed). If the vendor, quantities, and prices agree across all three, the invoice is approved. If not, it is held for review. It exists to make sure you only pay for goods you ordered and received.

What are the three documents in a three-way match?

The three documents are the purchase order, the goods receipt (also called a delivery or receiving report), and the supplier invoice. The purchase order shows the approved order and agreed prices, the goods receipt confirms what physically arrived, and the invoice is the vendor's request for payment. Matching the vendor, quantities, and amounts across all three confirms the payment is legitimate.

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

A 2-way match compares only the purchase order and the invoice, which suits services or spend with nothing physical to receive. A 3-way match adds the goods receipt, so you also confirm the items actually arrived before paying. The 3-way match is the standard for physical goods because it catches invoices for undelivered or short-shipped items.

Why is 3-way matching important?

3-way matching protects cash by catching overcharges, duplicate invoices, billing for goods never received, and fraudulent invoices before payment goes out. It also builds an audit trail that ties every payment back to an approved order and a confirmed delivery. For finance and audit teams, that documented control is often a requirement, not just a nice-to-have.

Does this tool perform the 3-way match?

No. This tool extracts purchase order data into clean, structured Excel, CSV, or JSON so the match is fast and accurate. The comparison against the goods receipt and invoice, plus approval routing, happens in your ERP or AP automation system. We remove the slow data-entry step that feeds the match rather than replacing your matching engine.

How do you automate a 3-way match?

Automation has two parts: capturing the document data and running the comparison. Tools that read purchase orders and invoices turn each document into structured fields, then your ERP or AP platform compares vendor, quantity, and price within set tolerances and flags exceptions for a human. Automating the data-capture step first removes the transcription errors that cause most false mismatches.

Ready to skip the typing? Extract your purchase order data with AI and get match-ready line items in seconds.

What is a 3-way match tolerance?

A tolerance is the acceptable variance between invoice, purchase order, and receipt before an invoice is held for review. Teams typically set a dollar cap and a percentage, such as $25 or 2 percent per line, whichever is lower. Differences inside the band post automatically, which keeps small rounding and freight variances from consuming AP time.

What is three-way matching in accounts payable?

In accounts payable, three-way matching is the verification step before payment: the invoice is compared against the purchase order and the goods receipt to confirm the price was agreed, the goods arrived, and the quantities line up. Matched invoices are approved for payment; mismatched ones are held as exceptions until the discrepancy is resolved. For the full AP workflow, tolerances, and common exceptions, see three-way matching in accounts payable.

Some accounts payable teams skip the invoice entirely with evaluated receipt settlement, which pays a supplier from the purchase order and goods receipt alone, turning the three-way check into an automated two-way one.