Skip to main content

What is 3-way matching in accounts payable and P2P?

3-way matching compares a purchase order, a goods receipt note and a supplier invoice before you pay. It is the accounts payable control that stops overpayments and duplicate invoices.

Topic
AP Automation
Written by
Jack, Head of Product
Published
Reading time
8 minutes
In this article
  1. Where 3-way matching sits in purchase to pay
  2. Why finance teams do it
  3. Where it breaks down manually
  4. Where real invoices fail the match
  5. Tolerances and matching level: what to decide first
  6. Invoices that cannot be 3-way matched
  7. A worked example
  8. 2-way vs 3-way vs 4-way
  9. Automating the match
  10. Three-way matching FAQs

3-way matching, also written three-way matching, is the accounts payable check that compares a supplier invoice with its purchase order and goods receipt before payment. If quantity and price agree within your tolerance, the invoice is cleared; if they do not, it is held as an exception until someone resolves the gap.

The purpose is straightforward. You pay for what you ordered, at the price you agreed, and only once you have received it. The purchase order proves the order was authorised. The goods receipt note proves the goods or services turned up. The invoice is the supplier asking to be paid. The match is the moment those three views of the same transaction are reconciled.

Where 3-way matching sits in purchase to pay

Purchase to pay, or P2P, is the full cycle from a purchase requisition to the payment of the supplier. 3-way matching is the step that ties that cycle together. The purchase order is raised early in P2P, the goods receipt is posted when the delivery arrives, and the invoice comes in last. The match checks that the three stages agree before the payment run, so it is the point where purchasing and accounts payable meet. Until the invoice is matched, the value of the receipt usually sits in goods received not invoiced (GRNI). See how the whole cycle runs in purchase to pay.

Why finance teams do it

A supplier invoice on its own is a claim. It says what the supplier believes you owe. Without a check against the order and the receipt, that claim gets paid on trust, and trust is where money leaks.

Three-way matching closes the most common gaps in accounts payable:

  • Overpayment. The invoice bills 120 units at a higher unit price than the purchase order agreed. The match catches both the quantity and the price variance before the payment run.

  • Duplicate invoices. A supplier sends the same invoice twice, or a copy is keyed a second time in a busy month-end. A duplicate check on supplier, invoice number and amount is the main control here. Matching adds a second line of defence: once a purchase order line has been billed in full, a repeat claim against it has nothing left to match.

  • Paying for goods you never received. The invoice arrives, the delivery does not, or arrives short. With no goods receipt to match against, the invoice is held as an exception until the delivery is confirmed.

  • Invoice fraud. A fabricated or inflated invoice from a real or spoofed supplier has no matching authorised order behind it. The control gives every payment a paper trail an auditor can follow.

Where it breaks down manually

The logic of 3-way matching is simple. Doing it by hand at volume is not. The three documents rarely live in one place. The purchase order sits in the ERP, the goods receipt note comes from the warehouse or a site manager, and the invoice lands as a PDF in a shared inbox or on paper in the post.

So an AP clerk keys the invoice, finds the purchase order number, hunts down the receipt, and compares line by line. Quantities are checked against deliveries, prices against the order, tax against the goods. On a clean invoice this takes a couple of minutes. On a messy one, with part deliveries, a missing receipt, or a price the buyer renegotiated but never updated, it turns into a chase across three teams.

The result is a queue. Invoices wait for a receipt that has not been booked in, or for a buyer to confirm a price change. Early-payment discounts lapse. Suppliers call to ask where their money is. And because the work is dull and repetitive, tired eyes miss the variances the check exists to catch.

Where real invoices fail the match

The textbook version assumes one invoice, one order and one receipt. Many of the failures we see in implementation work come from the data around the match, so they are worth testing for before you switch anything on. These examples come from Stratas projects, with client details removed.

  • One invoice, several purchase orders. At one UK client, a five-figure invoice carried a different purchase order on each line. The whole invoice was checked against the low four-figure order shown on the first line, and the mismatch blocked it. If your suppliers put several orders on one invoice, the match has to work line by line.

  • One job, more than one order reference. At another client, the accounts team could match a haulier invoice to the wrong purchase order, because the same job may have more than one related order. Check how often this happens in your own data, since an invoice matched to the wrong order can look clean.

  • The order number in the wrong field. In one purchase order export, the field believed to hold the order number matched 5 of 152 quoted PO numbers. A different field, holding the number as displayed, matched 149. Run real invoices against your export early, because a fault like this shows up as a flood of unmatched invoices.

  • Orders from the wrong supplier. On one invoice we reviewed, six purchase orders offered for matching belonged to other suppliers. On another project, a PO number was mistaken for an unrelated internal identifier and an order for the wrong supplier was copied. The step reported success, because nothing compared the supplier it found with the one intended. Limit candidates to the invoice supplier and check the supplier on every match.

  • A receipt that has not been booked yet. Some goods receipt exceptions resolve themselves once the receipt is recorded. Re-run the match when a receipt posts, so nobody chases an invoice that is about to clear.

All of these feed the exception queue, which is where much of the cost of invoice processing sits. Good setup shortens that queue, but a supplier invoice that does not agree with your records still needs a person.

Tolerances and matching level: what to decide first

Two settings decide how many invoices reach a person: how much variance you allow, and whether you compare at line or header level. Finance should own both, because they are policy decisions. We have seen one client still to agree a purchase order tolerance, and another choose to match against the invoice total at header level.

  • Line level compares each invoice line with its order line and receipt. It catches a price or quantity variance on a single item, and it needs line-level invoice capture and tidy order data. It suits stock and multi-line orders.

  • Header level compares the invoice total with the order total. It is simpler to run, but a variance on one line can be hidden by another. It suits simple orders with few lines.

  • Tolerance can be a percentage, an amount or both. A percentage alone lets a large invoice drift by a large sum, so consider a cap in pounds as well, and decide who can approve past it.

ERPs can get granular here. Microsoft's invoice matching overview for Dynamics 365 Finance sets unit price tolerances by item, vendor, their groups or legal entity, and lets price totals matching carry a percentage or an amount limit (checked 5 November 2026). Check what your own ERP offers before you write the policy.

Invoices that cannot be 3-way matched

3-way matching needs an order and a receipt, and plenty of invoices have neither. One UK client requires utility invoices to be handled without purchase orders and read at line level. Another treats purchase orders as optional free text on the invoice description and does not validate them.

For those invoices the check moves to other data. At one property client, a PO invoice needs a matched supplier and purchase order, while a non-PO invoice needs a matched supplier, property, fund and heading. A reported "mandatory PO" problem on non-PO invoices there turned out to be an unresolved property, so the fix was matching the property. See how service charge invoices are coded for more on that route.

A worked example

Here is one supplier invoice with four lines, checked against its purchase order and the goods receipt. The business allows a 2% price tolerance, and never pays for more than has been received.

One invoice matched to its purchase order and goods receipt
LinePurchase orderGoods receivedInvoiceCheckResult
Steel bracket, M12200 × £4.20200200 × £4.20All three agreePays £840.00
Gasket set100 × £2.50100100 × £2.54Price +1.6%, inside 2% tolerancePays £254.00
Fixing bolt pack50 × £18.004050 × £18.00Billed for 10 not yet receivedHolds £180.00
Anchor plate30 × £12.503030 × £12.90Price +3.2%, outside 2% toleranceTo buyer
Illustrative figures. Tolerances are set by your own policy.

The first line agrees across all three documents. The gasket set is billed 4p a unit above the order, a 1.6% difference, so it passes within tolerance. The bolt pack bills for 50 packs when only 40 have been booked in, so £180 is held until the rest arrives or the supplier issues a credit. The anchor plate is 3.2% above the agreed price, outside tolerance, so it goes to the buyer to confirm the new price or reject it.

Whether the clean lines pay straight away or the whole invoice waits for the exceptions is a policy choice. Many teams hold the full invoice until every line is resolved, so the supplier receives one payment and one remittance.

2-way vs 3-way vs 4-way

Three-way matching is the common standard, but it is one point on a scale. How many documents you match depends on what you are buying and how much control the spend warrants.

2-way, 3-way and 4-way matching compared
MatchDocuments comparedWhat it provesTypical use
2-wayPurchase order and invoiceYou were billed for what you ordered, at the agreed priceServices, subscriptions and fees with no physical delivery
3-wayPurchase order, goods receipt and invoiceYou are paying only for what arrivedStocked and ordered goods; the usual default
4-wayPurchase order, goods receipt, inspection and invoiceWhat arrived also passed a quality checkManufacturing, construction and regulated supply chains

2-way matching

Two-way matching compares the purchase order and the invoice only. It confirms you were billed for what you ordered, at the agreed price, but it does not confirm the goods arrived. It suits services and other spend where there is no physical delivery to receipt, such as a subscription or a professional fee booked against a purchase order.

3-way matching

Three-way matching adds the goods receipt note, so the invoice is checked against both the order and the confirmed delivery. This is the standard control for physical goods, because it is the only version that proves you received what you are paying for. Most AP teams treat it as the default for stocked and ordered items.

4-way matching

Four-way matching adds an inspection or quality-acceptance step to the three documents above. The invoice is held until the goods have been received and have passed a quality check. It is used in manufacturing, construction and regulated supply chains, where accepting faulty material has a real cost and payment should wait for sign-off.

Automating the match

Matching is a set of rules applied to structured data, which makes it a natural fit for automation. Software captures the invoice, reads the line-level detail, finds the purchase order and the goods receipt in your ERP, and compares them against tolerances you set. Small, expected variances pass within tolerance. Anything outside it is flagged and routed to the right person with the mismatch shown.

That changes the shape of the work. Your team stops matching every invoice and starts reviewing only the ones that fail. The clean majority post straight through to the ERP with the purchase order, receipt and nominal codes intact. This is the core of how AP automation works, and matching is where most of the manual hours disappear.

The variable that decides how much lands cleanly is how accurately the invoice is read in the first place: a misread quantity or price fails the match just as surely as a genuine discrepancy. Once an invoice matches, its data posts into the ERP you already run, with your nominal codes and tax groups intact.

Three-way matching FAQs

What is 3-way matching in accounts payable?

It is the check that clears a supplier invoice for payment only when it agrees with the purchase order and the goods receipt on quantity and price, within your tolerance. An invoice that disagrees is held as an exception.

What is 3-way matching in P2P?

It is the same check, seen as a step in the purchase to pay cycle. The order is raised first, the receipt is posted on delivery, and the invoice arrives last, so the match is where purchasing and accounts payable meet.

What is 2-way and 3-way matching in accounts payable?

2-way matching compares the invoice with the purchase order. 3-way matching also compares it with the goods receipt, so it confirms the goods arrived. Use 2-way for services with nothing to receipt, and 3-way for physical goods.

How does 3-way invoice matching work?

The invoice is read, its purchase order and goods receipt are found, and price and quantity are compared at line or header level against your tolerance. Invoices within tolerance are cleared, and the rest go to a person with the difference shown.

What is three-way matching in AP automation?

The software runs the comparison and sends only the failures to your team. How much clears on its own depends on how accurately the invoice is read and how clean your order and receipt data is.

Written by Jack, Head of Product
Stratas
See Stratas in action

A live walkthrough with our team, built around the questions you bring.

Book a demo

Want to see this in action?

Book a demo and we'll show you how Stratas handles your specific document types.