FlowRunner
Features Pricing
Theme
Start Free

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.

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. 1Invoice arrivesA PDF in your AP inbox
  2. 2Agent reads itVendor, PO number, every line
  3. 3Checked in your ERPAgainst the PO and the receipts
  4. 4The right person decidesPrice to the buyer, quantity to receiving
  5. 5Bill postedWith 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 SupplyInvoice 58817, Nov 3, 2026, PO 4500-2231
ItemQtyUnit priceAmount
Hex cap screw 3/8" x 2", box of 10040$18.40$736.00
Flange nut 3/8", case30$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 10060$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
FlowRunner10: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 priceHold billAsk vendor for credit
DR
Dana Ruiz10:09 AM

Was there a price notice with this invoice?

F
FlowRunner10: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 billA/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, NetSuite, Acumatica, Microsoft Dynamics 365 Business Central, and Sage Intacct. Invoices come in through Gmail or Outlook, and the questions go out in Slack or by email.

How three-way match works

DocumentCreated byWhat it proves
Purchase orderThe buyerWhat you agreed to buy, how many, and at what price
Receiving recordReceiving or the warehouseWhat arrived and was accepted, line by line
Vendor invoiceThe vendorWhat 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

MatchComparesUse it for
Two-wayPO and invoiceServices and subscriptions, which have no receipt
Three-wayPO, receipt, and invoiceInventory purchases, which is most of what a distributor buys
Four-wayPO, receipt, inspection, and invoiceItems that must pass a quality check before you pay

AccountingTools 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. 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 comparedExample tolerance
Unit price, invoice vs. PO2% or $0.50 per unit, whichever is smaller
Quantity billed vs. receivedExact for counted items, 1% for items sold by weight or length
Freight not on the POUp 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

ExceptionWhat it looks likeWho settles it
Partial receiptInvoice bills 60, receiving posted 48Receiving
Invoice before receiptGoods billed while still on the truckReceiving
Price changeInvoice price above the POBuyer
Unit of measurePO in cases, invoice in eachesBuyer
Freight and feesA fuel surcharge or small-order fee not on the POBuyer
No PO numberMissing, or a number that doesn’t existAP, then the requester
Duplicate invoiceThe same bill resent, sometimes under a new numberAP
Substituted itemThe vendor shipped and billed a different SKUBuyer 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, and both sit inside the program in our 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 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 and automate invoice processing.

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.

Editorial policy

See how this would work on your stack

A 30-minute walkthrough against your actual setup, or have our team custom-build it for you.