Three-Way Matching in Accounts Payable: How 2-, 3- and 4-Way Matching Work

Paying a supplier invoice should be the end of a chain of evidence: someone authorized the purchase, the goods or services arrived, and the supplier billed what was agreed. Invoice matching is how accounts payable confirms that chain before money leaves the bank. It is one of the oldest and most effective controls in finance, and also one of the most common sources of delay when it is poorly run.

This guide explains two-way, three-way and four-way matching, how matching works line by line, how to set tolerances, how to handle exceptions, how to automate matching, and which measures show whether your process works. If you need the basics of purchase orders first, see purchase order vs invoice.

The three documents

Three-way matching takes its name from the three records compared:

1. Purchase order (PO): what the buyer ordered, at what price.
2. Goods receipt (goods received note, GRN, or receiving report): what actually arrived, in what quantity and condition.
3. Supplier invoice: what the supplier is billing.

Each is created by a different person or function, ideally: procurement raises the PO, the warehouse or requester records the receipt, and the supplier sends the invoice to AP. That separation is the point. Agreement between independent records is strong evidence the payment is valid.

Two-, three- and four-way matching compared

Level	Documents compared	Confirms	Typical use
Two-way	Invoice ↔ PO	Billed items and prices were ordered and agreed	Services, low-risk items, where receipt isn't recorded
Three-way	Invoice ↔ PO ↔ receipt	Billed goods were also received	Physical goods, inventory, higher-value purchases
Four-way	Invoice ↔ PO ↔ receipt ↔ inspection	Received goods passed quality inspection	Regulated, high-value or quality-critical items

Organisations typically set the matching level per category, supplier or item type in their ERP or AP system. A sensible default is three-way matching for physical goods and two-way matching with approval for services, with four-way reserved for the few categories where quality failures are costly.

How matching works, line by line

Matching happens at the line level, not only on totals. For each invoice line, the system or clerk checks:

• Item: the invoiced item corresponds to a PO line.
• Quantity: invoiced quantity ≤ quantity received (three-way) and ≤ quantity ordered and not yet invoiced.
• Unit price: invoiced price = PO price, within tolerance.
• Line amount: quantity × price.
• Tax: correct rate and treatment.
• Header details: supplier, PO number, currency, payment terms, bank details.

Worked example: a three-line invoice

PO-7780 ordered:

Line	Item	Qty ordered	Unit price
1	Safety gloves (box)	50	12.00
2	Hi-vis vests	30	8.50
3	Hard hats	20	15.00

The receiving record shows 50 boxes of gloves, 30 vests and 16 hard hats (4 on back order).

The invoice bills:

Line	Item	Qty	Unit price	Amount
1	Safety gloves (box)	50	12.00	600.00
2	Hi-vis vests	30	8.75	262.50
3	Hard hats	20	15.00	300.00

Matching results:

• Line 1 matches on quantity and price: approved, 600.00.
• Line 2 quantity matches, but price is 8.75 vs 8.50. The difference is 0.25 per unit, 7.50 in total, about 2.9%. If the price tolerance is 2%, this is an exception.
• Line 3 bills 20 but only 16 were received. Under three-way matching, only 16 × 15.00 = 240.00 can be approved; the remaining 60.00 waits for the back order or a credit.

Without line-level matching, the invoice total of 1,162.50 might have been approved. The matched amount is 600.00 + 240.00 = 840.00, with line 2 held pending a decision on the price.

Tolerances

Exact matches are not always realistic. Small differences arise from rounding, currency conversion, freight allocation or minor quantity variances on weighed or measured goods. Tolerances let small differences pass automatically.

Common tolerance types:

Tolerance	Example	Purpose
Price, percentage	±2% per line	Rounding, small price adjustments
Price, absolute	±5.00 per line	Prevents large % tolerance on large values
Quantity, percentage	±5%	Bulk goods measured by weight or volume
Total invoice amount	±10.00	Rounding across lines
Tax	Exact, or ±0.05	Rounding in tax calculations

Set tolerances carefully:

• Too tight and AP is flooded with trivial exceptions.
• Too loose and overcharges slip through. A 5% tolerance on a 200,000 invoice allows 10,000 of overbilling.
• Combine percentage and absolute limits, using whichever is lower.
• Review tolerance usage: if one supplier always bills at the top of the tolerance, that is a pattern worth discussing.

Exception handling

Exceptions are where matching earns its value and where processes stall. Typical exceptions and owners:

Exception	Likely cause	Who resolves
Price variance	Supplier price change, wrong PO price	Procurement with supplier
Quantity not received	Partial delivery, receipt not recorded	Warehouse or requester
Quantity over ordered	Over-shipment	Procurement; return or amend PO
No PO number	Supplier omitted it	AP with supplier or requester
PO closed or fully invoiced	Duplicate invoice or late extra charge	AP; investigate duplicate
Item not on PO	Substitution or extra charge (freight)	Procurement
Tax mismatch	Wrong rate, missing tax number	AP with supplier
Bank details changed	Possible fraud	AP with independent verification

Good practice:

1. Route exceptions automatically to the right owner, with the documents attached.
2. Set deadlines, such as a response within three business days.
3. Escalate overdue exceptions to managers.
4. Record the resolution (credit note requested, PO amended, variance approved) for audit.
5. Analyse causes monthly and fix root problems: outdated PO prices, late receipting, suppliers ignoring PO numbers.

Matching services and non-PO invoices

Three-way matching assumes something physical is received. For services:

• Use two-way matching plus a service acceptance or approval by the requester, sometimes recorded as a receipt in the system to enable three-way logic.
• For time-based services, compare invoiced hours with timesheets or the PO's limits.

Invoices without POs, such as utilities, rent, subscriptions and some professional fees, cannot be matched to a PO. Control them through:

• Approval workflows based on amount and cost centre.
• Contract or schedule checks: rent and lease payments against the agreement; subscriptions against the contract.
• Analytical review: comparing with prior months.

Tricky situations in matching

Partial deliveries and split invoices

A single PO often results in several deliveries and several invoices. The system must track, per PO line, how much has been ordered, received and invoiced so far. The invoiced quantity cannot exceed the received quantity, and the cumulative invoiced amount cannot exceed the PO. When suppliers invoice before the back order arrives, the unreceived portion waits until the goods come in, rather than being rejected outright.

One invoice covering several POs

Some suppliers consolidate deliveries against several POs into one invoice. Matching then happens line by line against each PO. Ask suppliers to show the PO number on each line, not just in the header, or to invoice per PO if your system struggles with multi-PO invoices.

Freight, surcharges and other additional charges

Freight, fuel surcharges, packaging and handling fees often appear on invoices without a matching PO line. Options include adding expected freight to the PO, setting a separate tolerance for freight lines, or routing additional charges to the requester for approval. Whichever you choose, apply it consistently so suppliers know what to expect.

Credit notes

Credit notes reduce previously matched invoices. They should reference the original invoice and PO, so the system can reverse the matched quantity or amount. Unmatched credit notes tend to sit forgotten on the supplier account; review them monthly and apply them to the next payment.

Price changes during the contract

When a supplier legitimately raises prices, update the PO or the price agreement before invoices arrive. Otherwise every invoice becomes a price exception, and AP teams start approving variances by habit, which defeats the control.

Foreign currency invoices

Match in the invoice currency, not after conversion, so exchange rate movements do not create false variances. The payment amount in your base currency will differ from the invoice's converted value at booking, but that is an exchange difference for the accounts, not a matching issue.

Matching in small business accounting software

Smaller businesses using QuickBooks, Xero or similar tools can apply the same principles without an ERP:

• Create purchase orders in the software for significant purchases.
• When goods arrive, check the delivery note against the PO and note any shortages.
• When the bill arrives, convert the PO into a bill, or compare the two, and adjust for shortages or price differences.
• Keep the delivery note attached to the bill as evidence of receipt.

This manual three-way match takes a few minutes per bill and catches the most common errors. For businesses with few purchases, a two-way check of bill against PO or quote, plus the owner's knowledge that goods arrived, may be enough.

Automating invoice matching

Manual matching means a clerk opening three documents and comparing them line by line. Automation changes the job to exception handling.

What automation needs

1. Structured invoice data: from e-invoices, supplier portals or extraction. See invoice data extraction.
2. Accurate POs and receipts in the system, recorded promptly.
3. Clean supplier and item master data, so invoice lines can be linked to PO lines.
4. Configured rules and tolerances.

What automation does

• Reads the invoice and identifies the PO.
• Matches lines by item code, description and quantity.
• Applies tolerances and approves clean matches.
• Creates exceptions with reasons and routes them.
• Prevents duplicate matching against the same receipt.
• Releases approved invoices for payment according to terms.

Well-configured systems can approve a large share of PO invoices with no human touch, though the rate depends on supplier behaviour, data quality and how disciplined receipting is. Measure your own first-pass match rate and improve it over time. Our guide to accounts payable automation covers the wider picture.

Matching as a fraud and error control

Matching protects against:

• Overbilling: prices higher than agreed.
• Billing for goods not received.
• Duplicate invoices, including the same invoice resubmitted with a small change to the number.
• Fictitious suppliers: invoices without valid POs stand out.
• Unauthorized purchases: no approved PO, no automatic payment.

Matching does not protect against everything. It will not catch a fraudulent change to a genuine supplier's bank details, collusion between a buyer and a supplier on inflated POs, or fake receipts recorded by someone with access. Combine matching with supplier master data controls, segregation of duties and payment verification. After payment, reconcile bank statements to the AP ledger; if you work with PDF statements, a bank statement converter gives you a list of payments to compare. See our audit procedures guide for related tests.

Who does what in a matching process

Matching works when each step has a clear owner:

Step	Owner	Common failure
Raise PO with correct items and prices	Requester and procurement	Outdated prices, vague descriptions
Record receipt accurately and promptly	Warehouse or requester	Receipts entered days late, or not at all for services
Capture invoice data	AP or automation	Misread lines, missing PO numbers
Run the match and approve clean invoices	AP or system	Tolerances misconfigured
Resolve exceptions	Procurement, requester, AP	No deadlines, no escalation
Pay according to terms	Treasury or AP	Matched invoices paid late or early
Reconcile payments and supplier statements	AP and accounting	Credit notes and duplicates missed

The most frequent bottleneck is not AP at all; it is receipting. If people who receive goods do not record receipts, every invoice fails the three-way match. Make receipting easy, for example on a mobile device at the loading dock, and track how quickly it happens.

Supplier statement reconciliation as a backstop

Even with good matching, reconcile supplier statements periodically, especially for large suppliers. The supplier's statement of account lists the invoices and credits they believe are open. Differences from your AP ledger reveal invoices you never received, credit notes you have not applied, payments the supplier has not allocated and duplicates. It is a simple check that catches what matching misses.

Key metrics

Metric	What it shows
First-pass match rate	Share of PO invoices matched without intervention
Exception rate by type	Where problems originate
Average exception resolution time	Process efficiency
Invoices paid late due to exceptions	Supplier impact
Duplicate payments detected	Effectiveness of controls
Tolerance-approved variances by supplier	Possible overbilling patterns
Receipts recorded late	Warehouse or requester discipline

Implementing three-way matching: a short plan

1. Define policy: which categories need two-, three- or four-way matching.
2. Fix master data: suppliers, items, prices.
3. Train receivers to record receipts on the day goods arrive.
4. Tell suppliers to quote PO numbers and invoice by PO line.
5. Set tolerances and exception routing.
6. Pilot with a few suppliers, measure, then expand.
7. Review monthly: exceptions, causes, fixes.

Common pitfalls

• Matching totals only, missing line-level differences.
• Late receipting, making valid invoices fail and suppliers wait.
• After-the-fact POs, created to make an invoice match.
• Loose tolerances applied to large invoices.
• No ownership of exceptions, so they sit for weeks.
• Duplicate matching, where two invoices are matched to the same receipt.
• Treating matching as a substitute for bank detail verification.

Frequently asked questions

What is three-way matching?

Three-way matching compares a supplier invoice with the purchase order and the goods receipt before payment. It confirms that the buyer ordered the items, received them and is being billed the agreed price for the quantity received.

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

Two-way matching compares the invoice with the purchase order only. Three-way matching adds the goods receipt, confirming that what is being billed was actually delivered.

When is four-way matching used?

Four-way matching adds an inspection or quality acceptance step. It is used for goods where quality must be verified before payment, such as regulated materials, components for manufacturing or high-value equipment.

What is a matching tolerance?

A tolerance is the acceptable difference between invoice and PO or receipt values, such as ±2% on price or ±5% on quantity, within which an invoice can be approved automatically. Differences beyond the tolerance become exceptions.

Why is my invoice failing three-way matching?

The most common reasons are that the goods receipt has not been recorded yet, the invoiced price differs from the PO price beyond the tolerance, the invoice is missing the PO number, or the PO has already been fully invoiced. Check the receipt status first, because it is the most frequent cause and the quickest to fix.

Does three-way matching apply to small businesses?

The principle applies to any business: check that you ordered it, received it and are being charged the agreed price. Small businesses can do this informally by comparing the bill with the order and delivery note before paying.

Can three-way matching be automated?

Yes. AP automation and ERP systems can match invoices to POs and receipts at line level, apply tolerances and route exceptions. Automation depends on accurate invoice data, timely receipts and clean master data.

Summary

Invoice matching confirms that each invoice reflects what was ordered, received and agreed before payment. Choose two-, three- or four-way matching by category, match at line level, set sensible tolerances, manage exceptions with clear owners and deadlines, and automate the clean matches. Combine matching with master data controls and bank reconciliation for a robust payables process.

To reconcile what was actually paid against your matched invoices, convert bank statements with StatementPilot into spreadsheets checked against the statement balances.