3 Way Matching in Accounts Payable: Process and Automation

3 way matching is the accounts payable control that compares three documents before an invoice gets paid: the purchase order, the receiving report, and the vendor invoice. If all three agree on items, quantities, and prices, the invoice is approved. If they do not, payment stops until someone figures out why.

It sounds simple, and conceptually it is. In practice, matching is where AP teams spend a huge share of their time, because doing it by hand means pulling up three documents for every invoice and comparing them line by line. This guide covers how the 3 way matching process works, a worked example, how it differs from 2 way and 4 way matching, and what changes when you automate it.

What is 3 way matching in accounts payable?

3 way matching in accounts payable is the practice of verifying a vendor invoice against the purchase order and the receiving report before authorizing payment. The match confirms three facts: the company ordered the goods, the company received them, and the vendor billed the agreed price. Only when all three documents align does the invoice move to approval.

The control exists because each document comes from a different source. The PO comes from purchasing, the receiving report from the warehouse or whoever accepted delivery, and the invoice from the vendor. Fraud or error in any one document gets caught by the other two.

The three documents in a 3 way match

Document	Created by	What it proves
Purchase order (PO)	Your purchasing team	What was ordered, at what price, on what terms
Receiving report (goods receipt)	Your receiving team	What actually arrived, in what quantity and condition
Vendor invoice	The vendor	What the vendor is billing you for

For services rather than goods, the receiving report is often replaced by a service confirmation or a manager's sign-off that the work was completed.

3 way matching process step by step

A purchase order is issued. Purchasing creates a PO with line items, quantities, unit prices, and terms, and sends it to the vendor. The PO number becomes the thread that ties everything together.
Goods are received and recorded. When the delivery arrives, the receiving team counts and inspects it, then records a receiving report against the PO. Shortages and damaged items are noted here. Receipts that sit waiting for a vendor bill show up as goods received not invoiced until the invoice arrives.
The invoice arrives and is captured. The vendor sends an invoice referencing the PO. AP enters it, or AI capture reads it automatically, including line items.
The three documents are compared. Line by line: do items, quantities, and unit prices on the invoice match the PO, and do billed quantities match what was actually received? Most companies allow a small tolerance, for example 2% or $25, so trivial variances do not block payment.
Match or exception. A clean match moves to the invoice approval workflow and then payment. A mismatch becomes an exception: AP investigates, requests a credit memo for overbilling, waits for a backordered item, or corrects a receiving error before anything gets paid.

3 way match example

Say your company orders warehouse supplies:

PO 4512: 100 storage bins at $8.00 each, total $800.00
Receiving report: 100 bins received, none damaged
Invoice INV-2209: 100 bins at $8.00, total $800.00

All three documents agree, so the invoice matches and flows straight to approval. Nobody needs to touch it.

Now the exception case. The vendor ships only 90 bins because 10 are backordered, but bills for all 100. The receiving report says 90, the invoice says 100. The match fails on quantity, and the $800.00 invoice is held. AP either asks the vendor to reissue the invoice for $720.00 or waits for the remaining 10 bins to arrive and be received. Without the match, the company would have paid $80.00 for bins it never got, and that is exactly the kind of small leak that repeats hundreds of times a year at scale.

2 way match vs 3 way match (and 4 way)

The difference between 2 way and 3 way matching is the receiving report. A 2 way match compares only the invoice and the purchase order, so it confirms the price but not delivery. A 3 way match adds the receiving report, confirming the goods actually arrived before payment. A 4 way match goes further and adds an inspection or quality acceptance document.

Match type	Documents compared	Best for
2 way match	PO + invoice	Services, subscriptions, low-risk recurring spend
3 way match	PO + receiving report + invoice	Physical goods, inventory, most PO-backed purchases
4 way match	PO + receipt + inspection + invoice	Regulated or quality-critical goods (pharma, aerospace, food)

Many companies mix levels: 3 way matching for inventory and equipment, 2 way matching for utilities and software subscriptions where there is nothing physical to receive.

Why 3 way matching matters

It blocks overpayment. Overbilled quantities, price creep above the PO, and invoices for undelivered goods all fail the match instead of getting paid.
It catches duplicate and fraudulent invoices. A fake invoice has no PO and no receiving report behind it, so it cannot pass. The match is one of the most effective controls against vendor fraud and internal collusion.
It builds the audit trail. The matched document set is precisely what auditors want to see to verify a liability is real. For US companies it supports GAAP-accurate liability recording, satisfies internal control requirements under SOX for public companies, and keeps documentation in order for IRS purposes.
It improves vendor data. Recurring mismatches surface problems with specific vendors: chronic short shipping, billing above quoted prices, or invoicing before delivery.

Where manual 3 way matching breaks down

The control is only as good as a team's capacity to run it. Manual matching means an AP clerk retrieves the PO from the purchasing system, hunts down the receiving report, and compares each line against the invoice. A few minutes per invoice becomes a full-time job somewhere in the low hundreds of invoices per month. Under volume pressure, teams start skipping the match on "trusted" vendors or rubber-stamping anything under a threshold, which is exactly when errors and fraud slip through.

Line items are the hard part. An invoice with 40 lines against a PO with 40 lines is tedious to verify by eye, and transposed digits or unit-of-measure mismatches (cases versus units) are easy to miss.

Automating 3 way matching

Dedicated invoice matching software performs the match the moment an invoice arrives. AI capture reads the invoice including every line item, the system pulls the PO and receiving data, and matching runs automatically against your tolerance rules. Clean matches flow into approval untouched. Only exceptions reach a human, with the discrepancy already highlighted.

What to look for if you are evaluating tools for this:

Line-item extraction, not just header totals. A real match happens at the line level. If the software only reads the invoice total, it cannot do a true 3 way match.
Configurable tolerances. Percentage and dollar thresholds, per vendor or per category, so freight rounding does not generate exceptions.
Exception routing. Mismatches should land in a queue with the three documents side by side, not in an email thread.
Accounting sync. Matched, approved invoices should post to QuickBooks, Xero, NetSuite, or Sage without re-keying.

AutoPayables handles this flow: upload or email an invoice, the AI reads vendor, totals, and line items, and matching plus approval routing run from there. You can test the extraction on one of your own invoices right now, and the free plan is enough to trial the workflow on real volume before paying anything.

Frequently asked questions

What is a 3 way match?

A 3 way match is a payment control that compares a vendor invoice with the purchase order and the receiving report before the invoice is approved. The invoice is only paid when all three documents agree on items, quantities, and prices within an allowed tolerance, which prevents paying for goods that were never ordered or never delivered.

What is 3 way matching in p2p?

In the procure-to-pay (P2P) cycle, 3 way matching is the verification step that links procurement to payment. It sits between goods receipt and invoice approval: the PO from the procurement stage and the goods receipt from delivery are matched against the invoice before the payment stage can begin.

Is 3 way matching required?

No US law mandates 3 way matching by name, but public companies must maintain effective internal controls over financial reporting under SOX, and 3 way matching is one of the standard controls auditors expect around disbursements. For private companies it is a best practice that auditors, lenders, and acquirers look for.

What is the difference between 2 way and 3 way matching?

A 2 way match compares the invoice against the purchase order only, verifying price and quantity ordered. A 3 way match also checks the receiving report, verifying the goods actually arrived. The extra document closes the biggest gap in 2 way matching: paying for items that were billed correctly but never delivered.

Put your matching on autopilot

If your team is still matching documents by hand, start by measuring how many invoices per month are PO-backed and how long the match takes. Then try the extraction tool at the top of this page on a real invoice. Pair it with the approval workflow guide to design the full path from invoice arrival to payment.