Three-Way Matching in Accounts Payable, Explained

Every invoice your AP team pays should answer three questions. Was this ordered? Was it delivered? Does the bill match? Three-way matching is the process that cross-checks a purchase order, supplier invoice, and delivery receipt to answer all three before money leaves the account.

Simple in theory. In practice, it is the control most likely to break down under volume, because it depends on documents from different departments arriving at different times, then being compared by hand across dozens of data points. That manual comparison is where invoice errors survive longest, and where automation delivers the most measurable improvement.

What three-way matching actually involves

Three-way matching in accounts payable compares three documents before a payment is approved:

1. Purchase order (PO) — the binding agreement that authorises the purchase and lists types, quantities, and prices agreed to by buyer and supplier, with a unique number for tracking.
2. Goods receipt note (GRN) — the document your warehouse or receiving team generates when a shipment arrives, confirming the delivery date, quantity received, and condition of items.
3. Vendor invoice — the supplier's payment request, referencing the PO number and listing what they expect to be paid.

The AP team's job is to confirm that all three documents agree on what was ordered, what showed up, and what the supplier is charging. When they do, payment goes through. When they do not, the invoice gets flagged for investigation.

Two-way matching compares an invoice only to its PO. Three-way matching adds the delivery receipt, verifying that the purchased product was actually delivered. That third document is what separates a payment control from a rubber stamp.

The five steps, from PO to payment

The three-way matching process follows five sequential steps:

1. Create the purchase order. Procurement issues a PO to the supplier, locking in quantities, unit prices, and delivery terms. This is the baseline everything else is measured against.
2. Receive goods and record delivery. When the shipment arrives, the receiving team inspects it and creates a goods receipt note documenting what was delivered, in what quantity, and in what condition.
3. Receive the vendor invoice. The supplier sends their invoice, typically referencing the PO number. This lands with the AP team.
4. Match all three documents. AP compares the PO, GRN, and invoice line by line. Quantities, unit prices, item descriptions, totals. A concrete example: if a vendor invoices for 100 laptops at $1,000 each but the goods receipt shows only 80 were delivered, three-way matching catches that $20,000 discrepancy.
5. Approve or escalate exceptions. If the documents align (within tolerance), the invoice is approved for payment. If not, the mismatch is escalated for resolution. Your AP team then schedules payment and records the transaction in the accounting system, creating a full audit trail from purchase order to final payment.

Who is involved (and why that matters)

Three-way matching is not a single-department process. It pulls in multiple departments: purchasing/procurement, receiving/inventory, finance/AP, and the supplier/vendor. Each owns a different document. Procurement creates the PO. The warehouse creates the GRN. The vendor sends the invoice. AP brings all three together.

This cross-department dependency is the root cause of most matching delays. The GRN sits in a warehouse manager's inbox. The PO reference is missing from the invoice. A pricing update was agreed verbally but never recorded on the PO. Each of these requires coordination between teams that have different priorities and different systems.

Why it matters: fraud, overpayments, and the audit trail

Skip three-way matching and you are relying on trust that every invoice is legitimate, every quantity is correct, and every price is as agreed. That trust is expensive.

Invoice fraud can cost companies an estimated 5% of annual revenue, according to the ACFE. And small businesses experience billing fraud twice as often as their larger counterparts. The scale of exposure is real even at the top: Google and Facebook both issued multimillion-dollar payments for fake invoices sent by a cybercriminal in Lithuania. They recovered the money. A smaller business would be less likely to withstand the same scam.

Beyond fraud prevention, three-way matching creates an audit trail that connects every payment back to an authorised purchase and a confirmed delivery. That trail is what auditors look for, and what protects your business when a vendor disputes a payment or a regulator asks questions.

2-way vs. 3-way vs. 4-way matching: when to use which

Not every purchase needs the same level of verification.

For service purchases, you typically use 2-way matching since there is no physical delivery to confirm. Some organisations substitute a signed service completion form for the goods receipt note.

Four-way matching adds a formal inspection report to verify that goods meet quality standards before payment is released. This is common in manufacturing, pharmaceuticals, and any industry where accepting substandard goods creates downstream liability.

Most AP teams use a mix. Three-way matching for inventory and physical purchases, two-way for consulting fees and SaaS subscriptions, four-way for high-value or regulated items.

The problem with doing this manually

The logic of three-way matching is straightforward. The execution is where it falls apart.

Manual matching is prone to human error across dozens of small details. A transposed digit in a quantity field. A unit price rounded differently on the invoice than on the PO. A partial shipment recorded on one GRN but invoiced as a single line. Each mismatch creates extra work, and AP teams often need to drag warehouse and procurement managers into the resolution.

Common causes of matching failures include quantity discrepancies from partial shipments, pricing errors, missing PO numbers on invoices, and data entry mistakes when recording receipts. These are not rare edge cases. They are the daily reality of any AP team processing more than a handful of invoices.

The coordination overhead compounds with volume. Ten invoices a week is manageable by hand. A hundred is a full-time job. Five hundred, and errors start slipping through simply because there are not enough hours to check every line.

How automation changes the matching equation

Automated three-way matching replaces the manual comparison with software that extracts data from all three documents and runs the comparison instantly.

Most ERP systems including NetSuite, SAP, and QuickBooks have built-in or add-on modules that automate 3-way matching by pulling PO, receipt, and invoice data into one comparison workflow. The benefits go beyond speed.

Automating the process can save companies time and money, catch fraud, and enable AP staff to focus on higher-value projects. It also helps capture early payment discounts and avoid late fees, because invoices that used to sit in a manual queue for days now clear in minutes.

Matching tolerances, acceptable variance thresholds like a small percentage or dollar amount, let minor rounding differences pass without manual review. This prevents trivial mismatches from creating bottlenecks while still flagging genuine discrepancies.

Automation also builds institutional knowledge. When matching vendor invoices automatically, the AP team can see how many invoices have been processed from the same vendor, which can inform the vendor's rating. Patterns emerge: which suppliers consistently send clean invoices, which ones routinely overcharge or short-ship.

For teams already using AI document processing to extract invoice data, three-way matching is a natural extension. The same technology that pulls line items, amounts, and VAT from an invoice PDF can compare those fields against PO and GRN data automatically. The matching step that used to require a person toggling between three documents and a spreadsheet becomes a near-instant control that runs on every invoice, every time.

If your AP team is still handling invoice entry manually, the matching step downstream will always be a bottleneck. Automating extraction and matching together is what turns three-way matching from a compliance burden into a genuine control.

FAQ

What tolerance should I set for three-way matching?

Matching tolerances are acceptable variance thresholds, such as a small percentage or dollar amount, that allow minor discrepancies to pass without manual review. Common thresholds range from 1% to 5% or a fixed dollar amount. Set them based on your transaction size and risk tolerance. Too tight, and rounding differences flood your exception queue. Too loose, and real discrepancies slip through.

Do I need three-way matching for service invoices?

For services, you typically use 2-way matching (PO to invoice) since there is no physical delivery to confirm. Some organisations substitute a signed service completion form for the goods receipt note, effectively creating a three-way match for services where proof of delivery matters.

What causes three-way matching to fail?

Common causes include quantity discrepancies from partial shipments, pricing errors, missing PO numbers on invoices, and data entry mistakes when recording receipts. Most failures trace back to manual data handling across departments rather than genuine vendor fraud.

How does three-way matching prevent fraud?

It requires proof that goods were ordered (PO), delivered (GRN), and billed correctly (invoice) before any payment is released. A fake invoice with no corresponding PO or delivery record gets flagged immediately. Invoice fraud can cost companies an estimated 5% of annual revenue, making this control one of the most cost-effective fraud prevention measures in AP.