---
title: "Three-Way Match: Steps, Tolerances, and Exceptions"
description: "Three-way match checks a vendor invoice against the PO and the receipt before payment. The steps, tolerances, exceptions, and how to automate it."
url: https://flowrunner.ai/blog/three-way-match
date_published: 2026-11-12
date_modified: 2026-11-13T14:04:35-08:00
---

Articles November 12, 2026 Updated November 13, 2026 6 min read

# Three-Way Match: Steps, Tolerances, Exceptions, and Automation

Three-way match checks a vendor invoice against the PO and the receipt before payment. The steps, tolerances, exceptions, and how to automate it.

![Ochre card headed Three-way match with the statement PO. Receipt. Invoice., the line Exceptions go to whoever can settle them., and a tally of 3 documents, 2 exceptions, and 1 bill.](https://flowrunner.ai/images/blog/three-way-match-hero.webp)

Three-way match is the accounts payable check that compares each vendor invoice with the purchase order and the receiving record before the bill is paid. When quantity and price agree within your tolerances, the bill is approved. When they don’t, the invoice is held as an exception until someone settles the difference.

Checking a clean invoice takes seconds. The time goes to the exceptions, because AP has to ask the buyer about a price or ask receiving about a missing box and then wait for the answer. A FlowRunner flow runs the match from your AP inbox and sends each question straight to the person who can answer it.

1.  1 **Invoice arrives** A PDF in your AP inbox
2.  2 **Agent reads it** Vendor, PO number, every line
3.  3 **Checked in your ERP** Against the PO and the receipts
4.  4 **The right person decides** Price to the buyer, quantity to receiving
5.  5 **Bill posted** With who approved what

## One invoice, start to finish

Here is a sample invoice from Midland Fastener Supply. The flow read the PDF and checked it against the PO and the receipts in SAP Business One. Line 1 matches. Lines 2 and 3 don’t.

**Midland Fastener Supply** Invoice 58817, Nov 3, 2026, PO 4500-2231

| Item | Qty | Unit price | Amount |
| --- | --- | --- | --- |
| Hex cap screw 3/8" x 2", box of 100 | 40 | $18.40 | $736.00 |
| Flange nut 3/8", case | 30 | $52.10 | $1,563.00 |
| The PO price is $49.75. That is 4.7% over, and your tolerance is 2%. |
| Flat washer 3/8", box of 100 | 60 | $9.20 | $552.00 |
| Receiving posted 48 boxes. 12 are billed but not received. |
| Freight |  |  | $185.00 |
| Total |  |  | $3,036.00 |

The flow asks the buyer about the price and receiving about the quantity, both at once. Here is what the buyer gets in Slack:

Slack, direct message to the buyer

F

FlowRunner 10:04 AM

**Price check: Midland Fastener Supply, invoice 58817**

Line 2, flange nut 3/8", 30 cases. PO price $49.75, invoice $52.10. That is 4.7% over your 2% tolerance, $70.50 on the line.

Approve new price Hold bill Ask vendor for credit

DR

Dana Ruiz 10:09 AM

Was there a price notice with this invoice?

F

FlowRunner 10:09 AM

No. The invoice is the only attachment, and PO 4500-2231 still shows $49.75 a case.

Dana knows the November increase was agreed and the PO was never updated, and clicks Approve new price. Receiving answers the same way: the last 12 boxes came on a second truck, and they post the receipt. The flow checks again, posts the bill, and writes the decisions onto it:

**Comment on the bill** A/P invoice 58817, SAP Business One

Matched to PO 4500-2231 and the receipts of Oct 30 and Nov 4. Line 2 price of $52.10 approved by Dana Ruiz in Slack, Nov 4, 10:12 AM. Line 3 matched after receiving posted the second delivery.

An invoice that matches skips all of this and posts on its own. Every run also keeps a step-by-step record of what the flow read, what it checked, and who answered. That record is the evidence an auditor asks for.

The same flow runs on [SAP Business One](https://flowrunner.ai/integrations/sap-business-one), [NetSuite](https://flowrunner.ai/integrations/netsuite), [Acumatica](https://flowrunner.ai/integrations/acumatica), [Microsoft Dynamics 365 Business Central](https://flowrunner.ai/integrations/microsoft-d365-bc), and [Sage Intacct](https://flowrunner.ai/integrations/sage-intacct). Invoices come in through [Gmail](https://flowrunner.ai/integrations/gmail-service) or [Outlook](https://flowrunner.ai/integrations/outlook), and the questions go out in [Slack](https://flowrunner.ai/integrations/slack) or by email.

## How three-way match works

| Document | Created by | What it proves |
| --- | --- | --- |
| Purchase order | The buyer | What you agreed to buy, how many, and at what price |
| Receiving record | Receiving or the warehouse | What arrived and was accepted, line by line |
| Vendor invoice | The vendor | What the vendor is billing you for |

NetSuite calls the receiving record an item receipt, and SAP Business One calls it a goods receipt PO. Match line by line. Two lines can be wrong in opposite directions and still add up to the right total.

## Two-way vs. three-way vs. four-way match

| Match | Compares | Use it for |
| --- | --- | --- |
| Two-way | PO and invoice | Services and subscriptions, which have no receipt |
| Three-way | PO, receipt, and invoice | Inventory purchases, which is most of what a distributor buys |
| Four-way | PO, receipt, inspection, and invoice | Items that must pass a quality check before you pay |

[AccountingTools](https://www.accountingtools.com/articles/what-is-three-way-matching.html) describes two-way matching as faster because nobody has to find the receiving report, and four-way as adding an inspection or quality approval.

## The three-way match process, step by step

1.  Capture the invoice header and every line.
2.  Check it isn’t a duplicate: the same vendor and number, or the same amount and date under a new number.
3.  Find the PO and confirm it is open and belongs to this vendor.
4.  Find every receipt against that PO, and what on each line is received but not yet billed.
5.  Compare price and quantity on each line, within your tolerances.
6.  Approve the bill, or hold it and send the exception to the person who can settle it.
7.  Keep the result with the bill, including who approved any difference.

## Tolerances: how close counts as a match

A tolerance is the difference you accept without review. It is either a percent or a fixed amount, and NetSuite’s Approvals Workflow SuiteApp [sets the two separately](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4168980481.html). Each one alone has a gap. A 2% tolerance on a $40,000 line lets $800 through, and a $25 tolerance on a $30 line accepts almost double the price. Use whichever is smaller.

| What’s compared | Example tolerance |
| --- | --- |
| Unit price, invoice vs. PO | 2% or $0.50 per unit, whichever is smaller |
| Quantity billed vs. received | Exact for counted items, 1% for items sold by weight or length |
| Freight not on the PO | Up to $250 on prepay-and-add terms |
| Invoice total vs. lines | $1.00, for rounding |

Set your own from three months of your exceptions. Look at what you would have disputed and set the tolerance just under it.

## Exceptions and who settles them

| Exception | What it looks like | Who settles it |
| --- | --- | --- |
| Partial receipt | Invoice bills 60, receiving posted 48 | Receiving |
| Invoice before receipt | Goods billed while still on the truck | Receiving |
| Price change | Invoice price above the PO | Buyer |
| Unit of measure | PO in cases, invoice in eaches | Buyer |
| Freight and fees | A fuel surcharge or small-order fee not on the PO | Buyer |
| No PO number | Missing, or a number that doesn’t exist | AP, then the requester |
| Duplicate invoice | The same bill resent, sometimes under a new number | AP |
| Substituted item | The vendor shipped and billed a different SKU | Buyer and receiving |

## Three-way match as a control

The match works as a control because three different people stand behind the three documents:

-   The buyer commits the money on the PO.
-   Receiving confirms the goods arrived.
-   AP pays only when both agree with the invoice.

If one person can post a receipt and also approve the bill, the match proves nothing. The approval before the PO goes out is its own control, covered in [PO approval workflow](https://flowrunner.ai/blog/po-approval-workflow), and both sit inside the program in our [SOX compliance checklist](https://flowrunner.ai/blog/sox-compliance-checklist).

## Matching inside your ERP

ERPs match too. NetSuite’s Approvals Workflow SuiteApp checks bills against the tolerances you set, and Sage Intacct’s [2026 Release 2](https://www.intacct.com/ia/docs/en_US/releasenotes/2026/2026_Release_2/Purchasing/2026-R2-intelligent-3-way-matching-automation.htm) added line-level matching against POs and receivers. Both show the exception on a screen inside the ERP. A flow takes the same exception to the buyer and receiving where they already work and writes their answers back. For the rest of AP, see [how to automate accounts payable](https://flowrunner.ai/blog/how-to-automate-accounts-payable) and [automate invoice processing](https://flowrunner.ai/blog/automate-invoice-processing).

## Need a custom three-way match automation? Our team can build it for you.

Tell us the process. Our implementation team at Midnight Flow builds it around how you work, tests it on your real data, and keeps it running, in your own FlowRunner workspace.

[Have us build it](https://midnightflow.ai/packages/custom?utm_source=flowrunner.ai&utm_medium=referral&utm_campaign=general&utm_content=blog.aside&utm_term=three-way-match)

## Frequently asked questions

### What are the three documents in a three-way match?

The purchase order, the receiving record (also called a goods receipt or item receipt), and the vendor invoice. Matching them confirms the vendor is billing only for goods you ordered and received, at the price on the PO.

### What is the difference between 2-way and 3-way match?

A two-way match compares the invoice with the purchase order, so it confirms the price and the quantity ordered. A three-way match adds the receiving record, so it also confirms the goods arrived. Use two-way for services that have no receipt and three-way for inventory purchases.

### What happens when a three-way match fails?

The invoice is held as an exception until someone settles the difference. Price differences go to the buyer and quantity differences go to receiving. Until one of them answers, the bill stays unpaid.

By [Mark Piller](https://flowrunner.ai/about), Founder of FlowRunner [Editorial policy](https://flowrunner.ai/editorial-policy)

---
Markdown version of https://flowrunner.ai/blog/three-way-match. Site index: https://flowrunner.ai/llms.txt
