---
title: "Three-Way Match: How to Do It, Step by Step"
url: "https://goremy.ai/blog/articles/three-way-match-explained-po-receipt-and-invoice"
author: Luis Chavez-Mattos
editor: Luis Chavez-Mattos
editor_title: Director, Product
published: "2026-11-20T08:00:17.449Z"
updated: "2026-11-20T08:00:17.449Z"
topic: Accounting and Month-End Close
description: Three-way match checks the PO, goods receipt, and invoice before you pay. Get the steps, tolerance rules, a worked example, and an AI prompt.
---

# Three-Way Match: How to Do It, Step by Step

> Three-way match checks the PO, goods receipt, and invoice before you pay. Get the steps, tolerance rules, a worked example, and an AI prompt.

Edited by Luis Chavez-Mattos, Director, Product · Published 2026-11-20

## What is three-way match?

Three-way match is an accounts payable control that compares three documents before a supplier invoice is paid: the purchase order (PO), the goods receipt (or receiving report), and the supplier's invoice. If the supplier, items, quantities, and prices agree across all three, the invoice is approved for payment. If they don't agree, the invoice is held until someone explains the difference. The point is simple: you pay only for what you ordered, at the price you agreed to, and what actually arrived.

## TL;DR

- **Three documents, one question:** did we order it (PO), did we get it (receipt), and are we being billed correctly for it (invoice)?
- The match runs on **vendor, item, quantity, unit price, and total**, and most mismatches come from quantity or price.
- Most companies set a **tolerance** (a small allowed variance, by percentage or dollar amount) so tiny differences don't stall payment.
- **Purchasing owns the PO, the warehouse or requester owns the receipt, and AP owns the invoice**, so every exception needs a named person who resolves it.
- AI is good at **comparing documents and drafting the exception email**. It should not approve payment, and you should recheck any arithmetic it reports.
- Services, subscriptions, and freight often have no physical receipt, so you need a **fallback rule** such as two-way match or approval by the budget owner.

## Why do companies use three-way match?

Without it, the only proof behind a payment is the supplier's own invoice. That leaves a company open to several problems:

- Paying for goods that were never delivered or were delivered short.
- Paying a price that differs from the one negotiated on the PO.
- Paying the same invoice twice, or paying an invoice for an order nobody approved.
- Paying an invoice that was sent by someone pretending to be a real supplier.

Each document comes from a different source. Purchasing creates the PO, the receiving dock or requester confirms delivery, and the supplier sends the invoice. Because the three come from different hands, an error or a fraudulent entry in one tends to show up as a mismatch with the others. That separation of duties is the real control. The matching itself is mechanical.

## What are the three documents, and who owns each one?

| Document | What it says | Who creates it | What AP uses it for |
|---|---|---|---|
| Purchase order (PO) | What we agreed to buy: items, quantity, unit price, terms, delivery date | Purchasing or the requester, approved by budget owner | The authorized price and quantity |
| Goods receipt (receiving report, GRN) | What physically arrived and when | Warehouse, receiving dock, or the requester | The quantity actually received |
| Supplier invoice | What the supplier is billing: items, quantity, price, tax, freight, total | The supplier | The amount being requested |

A PO number is the thread that ties them together. The supplier should print it on the invoice, and the receipt should reference it. When a PO number is missing or wrong on an invoice, that is the most common reason matching fails before it even starts.

## What exactly gets compared?

At each line item, the match checks:

1. **Vendor.** The invoice is from the same supplier named on the PO.
2. **Item.** The product or description matches (by item number where possible).
3. **Quantity.** The quantity invoiced is no more than the quantity received, and the quantity received is no more than the quantity ordered (unless over-receipt is allowed).
4. **Unit price.** The invoiced price equals the PO price, within tolerance.
5. **Extended amount.** Quantity times price equals the line total.
6. **Header charges.** Tax, freight, and other charges are on the PO or otherwise authorized.
7. **Terms and dates.** Payment terms match the PO, and the invoice is not a duplicate.

The comparison that matters most is quantity invoiced against quantity received. It is the check that stops you from paying for goods that haven't shown up.

## How do you do a three-way match, step by step?

This is the manual process. Your ERP or AP automation tool may do most of it for you, but the logic is the same, and you need it to resolve exceptions.

1. **Confirm the PO exists and is approved.** Find the PO number on the invoice and open the PO. If there is no PO, stop. The invoice goes to the non-PO route (see below).
2. **Check the vendor and invoice basics.** Same supplier, valid invoice number, no duplicate of an invoice already entered, correct legal entity and currency.
3. **Pull the goods receipt for that PO.** Look up what was received, in what quantity, and on what date. Partial deliveries mean several receipts against one PO.
4. **Match line by line.** For each line, compare PO quantity, received quantity, and invoiced quantity, then PO price against invoice price.
5. **Apply your tolerance.** If a difference falls inside the allowed variance, approve it. If not, flag it as an exception.
6. **Check the extras.** Freight, tax, handling fees, and discounts. These are often where the invoice differs from the PO without anyone noticing.
7. **Route exceptions to the right owner.** Quantity problems go to receiving or the requester. Price problems go to purchasing. Missing PO problems go to the budget owner.
8. **Resolve and document.** Get a corrected invoice, a credit memo, a PO amendment, or a corrected receipt, and note what was done and by whom.
9. **Approve for payment.** Once matched, the invoice moves into the payment run according to the terms.
10. **Keep the evidence together.** Store the PO, receipt, invoice, and any exception notes so an auditor can see the full chain.

## What does a worked example look like?

Say you order printer paper.

**PO 4471:** 100 cartons at $12.50 each. Total $1,250.00.
**Goods receipt:** 90 cartons received on March 3. The other 10 are back-ordered.
**Invoice INV-8823:** 100 cartons at $12.80 each. Total $1,280.00.

Run the match:

| Check | PO | Receipt | Invoice | Result |
|---|---|---|---|---|
| Quantity | 100 | 90 | 100 | Billed for 10 more than received. Exception. |
| Unit price | $12.50 | n/a | $12.80 | Price is $0.30 higher. About 2.4% over. Exception unless tolerance allows it. |
| Total | $1,250.00 | n/a | $1,280.00 | $30.00 over PO total |

There are two separate problems here. The quantity problem is the more serious one: you were billed for 10 cartons that haven't arrived. The right action is not to reject the whole invoice. Ask the supplier for a corrected invoice for 90 cartons at the PO price (or a credit memo), and have purchasing confirm whether the $12.80 price was ever agreed. If the price change was approved, purchasing amends the PO. If not, the supplier corrects the invoice.

Some teams pay the matched portion and hold the rest. Others hold the entire invoice. Which you do should be written in your AP policy, not decided case by case.

## What is a tolerance, and how should you set one?

A tolerance is the variance you will accept without a human review. Without one, a $0.02 rounding difference stops a payment just as a $2,000 difference does. Typical setups are:

- **A percentage** (for example, allow invoices up to 2% over the PO line price).
- **A dollar amount** (for example, allow up to $25 over per invoice).
- **A combination**, where the difference must be inside both limits, or inside whichever is smaller.
- **Different limits by direction.** Underbilling is usually safe to accept. Overbilling needs tighter limits.

The numbers above are illustrations, not recommendations. Your finance leadership or controller should set the actual thresholds based on your spend, your risk, and how many exceptions your team can handle. A tolerance too tight floods AP with trivial holds. A tolerance too loose lets small overcharges accumulate across thousands of invoices.

## What are the most common mismatches and how do you fix them?

| Mismatch | Likely cause | Who fixes it | Typical resolution |
|---|---|---|---|
| Invoiced quantity higher than received | Short shipment, back order, or receipt not entered yet | Receiving or requester | Enter the receipt, or ask for a corrected invoice |
| Invoice price higher than PO | Price increase, wrong contract price, or PO out of date | Purchasing | Amend the PO or get a corrected invoice |
| No PO on invoice | Order placed outside the process, or supplier left it off | Requester and purchasing | Get the PO number, or treat as a non-PO invoice with approval |
| Receipt exists, no invoice | Supplier hasn't billed yet | AP | Accrue the liability at period end |
| Freight or tax not on PO | Extra charges added by the supplier | Purchasing or budget owner | Approve the charge or dispute it |
| Duplicate invoice | Supplier resent it, or it was keyed twice | AP | Block the duplicate |
| Over-delivery | Supplier shipped more than ordered | Receiving and purchasing | Accept and amend the PO, or return the excess |

Most delays are not caused by fraud. They are caused by a receipt that was never entered or a PO that was never updated after a price negotiation. If your exception queue keeps filling with the same causes, fix the process upstream.

## How is three-way match different from two-way and four-way match?

- **Two-way match** compares the PO and the invoice only. It is used for services, subscriptions, and low-value purchases where there is nothing physical to receive, or where the cost of a receipt isn't worth it.
- **Three-way match** adds the goods receipt. It is the standard for physical goods and higher-value purchases.
- **Four-way match** adds a fourth check, usually an inspection or quality acceptance report, confirming the goods meet specification. It appears in industries where quality matters, such as manufacturing, pharma, or construction.

Many companies use all three, depending on the category and the amount. A common policy: three-way for inventory and equipment, two-way for recurring services, and a documented approval route for everything else.

## What do you do when there is no goods receipt?

Services, software subscriptions, consulting, and utilities don't arrive on a dock. Options include:

- **Service entry or acceptance.** The requester confirms in your system that the work was performed. This works like a receipt.
- **Two-way match with budget owner approval.** The PO and invoice agree, and the person who owns the budget signs off.
- **Milestone or percentage-of-completion confirmation** for projects billed in stages.

Whatever you pick, someone other than the person who entered the invoice should confirm the work was done. That keeps the separation of duties intact.

## How can AI help with three-way match?

If your ERP already does automatic matching, AI is most useful on the messy part: the exceptions. It also helps when invoices come as PDFs or emails and you are matching by hand in a spreadsheet. AI can compare three documents, spot the differences, and draft the message to the supplier or the requester.

Use only an AI tool your company has approved for financial documents. Supplier invoices and pricing are confidential, and you should not paste them into a personal account.

Paste this prompt, then add the text of the three documents (or the key lines from each):

```
You are helping an accounts payable analyst perform a three-way match.

Below are three documents: a purchase order, a goods receipt, and a supplier invoice. Compare them line by line.

1. Make a table with one row per line item and these columns: item, PO quantity, received quantity, invoiced quantity, PO unit price, invoiced unit price, quantity difference, price difference, status (Match / Exception).
2. List any header-level differences: vendor name, PO number, currency, payment terms, tax, freight, other charges, invoice total vs PO total.
3. Flag anything that looks unusual, such as a missing PO number, a duplicate-looking invoice number, or charges not on the PO.
4. Do not decide whether to pay. List the exceptions and say who should resolve each one (purchasing, receiving, requester, or supplier).
5. Draft a short, polite email to the supplier requesting a corrected invoice or credit memo for the exceptions.
6. If any information is missing or unreadable, say so instead of guessing.

Tolerance rule: [for example, accept price differences up to 2% per line].

PURCHASE ORDER:
[paste]

GOODS RECEIPT:
[paste]

INVOICE:
[paste]
```

### What should you check in the AI's answer?

- **Recompute the math yourself.** Language models can make arithmetic mistakes, especially across many lines. Check quantity times price and the totals.
- **Check every number against the source.** Confirm the quantities and prices in the table match the documents, particularly if the invoice was a scanned PDF where text can be misread.
- **Look for what it left out.** Ask whether any line items on any document were missing from the table.
- **Read the draft email before sending it.** Make sure it states the right invoice number, PO number, and amounts.

### Where should you not trust AI?

- **Approving or releasing payment.** A person with authority should do this, following your policy.
- **Deciding the tolerance.** That is a finance policy decision.
- **Judging fraud risk.** AI can flag oddities, but a changed bank account or an unfamiliar vendor should go through your normal vendor verification process, by calling a known number, not one on the invoice.
- **Reading poor scans.** If the OCR is bad, the comparison will be wrong without telling you.

## Who is responsible for what?

Three-way match works only when each team does its part on time.

- **Purchasing and requesters:** create accurate POs, include the PO number in what they send to suppliers, and amend POs when prices or quantities change.
- **Receiving and operations:** enter receipts promptly and accurately, including partial deliveries and damaged goods.
- **Accounts payable:** run the match, hold exceptions, chase resolutions, and keep the audit trail.
- **Managers and budget owners:** respond quickly when asked to confirm a receipt or approve a variance. A pile of invoices waiting on a manager's reply is a common reason for late payments and lost early-payment discounts.

A useful habit: agree on a response time for exceptions, such as two business days, and report how many are overdue by owner.

## Can you build your own exception tracker?

Many teams track exceptions in a shared spreadsheet or an email thread, and things slip. A small internal app can hold one record per held invoice with the PO number, the type of mismatch, the owner, the due date, and a status, plus a view that shows what is overdue by person. With [Remy](https://goremy.ai), you describe that tool in plain English and it builds and deploys a full-stack app with a database and sign-in, so purchasing, receiving, and AP can all work from the same list. You own the code, and it is a way to add a lightweight tracker around your existing ERP without buying another subscription.

## Frequently Asked Questions

### Is three-way match required by law?

No law requires it in general. It is an internal control that companies adopt to reduce overpayment and fraud, and auditors often expect to see it or an equivalent control for material purchasing. Your own policy and your auditors' expectations determine how strictly you apply it.

### What happens if the invoice arrives before the goods?

The invoice cannot fully match because there is no receipt yet. Most systems hold it until the receipt is entered. If the payment terms will run out first, ask the requester or receiving to confirm delivery status, and give AP a way to note the delay so nobody pays late by accident.

### Does three-way match work for partial deliveries?

Yes. Each delivery gets its own receipt against the same PO. The invoice should bill only for the quantity received so far, or the system matches the cumulative received quantity against the cumulative invoiced quantity. Back-ordered items stay open on the PO.

### Can three-way match be automated?

Yes. Most ERP and AP automation systems can match PO, receipt, and invoice automatically and pass clean matches straight to payment, leaving people to handle only exceptions. Automation depends on clean data: accurate POs, timely receipts, and invoices that carry the right PO number.

### What is the difference between a goods receipt and a packing slip?

A packing slip comes from the supplier and lists what they say they shipped. A goods receipt is your own record of what actually arrived. Matching should rely on your receipt, because the packing slip is the supplier's claim, not your confirmation.
