How-to Playbook

How to automate 3-way match

Matching the purchase order, the goods receipt, and the vendor bill by hand does not scale past a handful of vendors. Here is how to automate it safely.

Why manual matching fails

3-way match exists to catch the bill that does not match what was ordered or what actually arrived: wrong quantity, wrong price, or a bill for goods never received. Done by eye across spreadsheets and email PDFs, it scales linearly with purchase volume, and every added vendor makes the manual check slower and less reliable.

Where teams get it wrong

  • Matching only two of the three documents: usually skipping the receipt and comparing bill to PO alone.
  • No tolerance threshold, so every rounding difference becomes a manual dispute.
  • Partial shipments and partial billing are not tracked, so the same receipt gets matched twice.
  • Mismatches get paid anyway "to keep the vendor happy," defeating the purpose of the control.
  • No vendor scorecard, so a vendor that repeatedly over-bills never gets flagged as a pattern.

The 3-Way Match Framework

  1. 1.Issue the purchase order: quantity, unit price, and vendor terms as the baseline of record.
  2. 2.Record the goods receipt: what actually arrived, on what date, against which PO line.
  3. 3.Capture the vendor bill: amount, quantity billed, and invoice number.
  4. 4.Match all three: compare PO, receipt, and bill line by line within a defined tolerance.
  5. 5.Flag exceptions: anything outside tolerance routes to a named approver, not to payment.
  6. 6.Pay only matched or approved lines: clean matches flow to payment automatically.

How Fintra automates the match

StepWhat Fintra does
Purchase orderProcurement issues and tracks POs as the system of record for what was ordered.
Goods receiptGoods receipt captures quantity and date received against each PO line.
Vendor billBill pay ingests the vendor bill and links it to the originating PO automatically.
Match3-way match compares PO, receipt, and bill within your configured tolerance.
Flag exceptionsMismatches route to a named approver instead of the payment queue.
PayMatched lines flow to bill pay over a real ACH rail; vendor scorecards track repeat mismatch patterns.
Framework step to Fintra module

The exception, not the match, is where a human looks: clean matches pay on schedule, and every override is recorded in the audit trail.

Your 3-way match checklist

Set these up before automating payment

  • Require a PO for every purchase above a defined dollar threshold.
  • Record goods receipt against the PO line, not just "received: yes/no."
  • Link every vendor bill to its originating PO number.
  • Set a tolerance band for price and quantity variance.
  • Route anything outside tolerance to a named approver, never to auto-pay.
  • Track mismatch patterns per vendor with a scorecard.
  • Review the tolerance band quarterly as vendor mix changes.

Questions people ask

What is 3-way matching in accounts payable?

It is the process of comparing three documents before paying a vendor bill: the purchase order (what was ordered), the goods receipt (what arrived), and the vendor bill (what is being charged). Discrepancies among the three (wrong quantity, wrong price, billing for undelivered goods) get flagged before payment instead of after.

Can 3-way match be fully automated?

The matching comparison itself can run automatically once POs, receipts, and bills are structured data. What should stay human is the exception: anything outside your tolerance band routes to an approver rather than paying automatically. Clean matches, the majority of purchases, can flow straight to payment.

What tolerance should I set for matching?

There is no universal number; many SMBs start around 2-5% variance or a small fixed dollar amount, whichever is larger, to absorb rounding and freight charges without masking real discrepancies. Tighten the tolerance for high-dollar vendors and loosen it for low-risk, low-dollar recurring purchases.

Do I need 3-way match if I only have a few vendors?

Two-way match (bill to PO) is a reasonable starting point for a very small vendor list, but adding the goods receipt step is what actually catches short shipments and undelivered goods. As purchase volume grows, the receipt step is usually where automation pays off fastest, because it is the one manual reviewers skip first.

Keep reading

One finance briefing a week

New guides, checklists and benchmarks, by email. Unsubscribe from any issue.

 

Match every bill automatically

Fintra compares PO, receipt, and bill and only sends you the exceptions. Talk to us: we will map it to your stack.