What a three-way match checks
It compares three documents. The purchase order says what you ordered and at what price. The receiving record says what actually arrived. The vendor invoice says what you're being billed. If all three agree, you pay. If they don't, you dispute it before paying.
| What you check | Against | What it catches |
|---|---|---|
| Unit price on each line | The purchase order or contract price | Price creep and discounts that weren't applied |
| Quantities | The receiving record | Items billed but never received, short shipments |
| Line items | The purchase order | Items nobody ordered |
| Invoice number | Invoices already entered | Duplicates, including near-matches like INV-1043 and 1043 |
| Sales tax | Your resale or exemption certificates | Tax charged on items you buy for resale |
| Vendor details | Your vendor master file | An unknown vendor, a new remit-to address, a changed bank account |
| Terms | What you agreed | Different payment terms, freight you didn't agree to, a missed early-payment discount |
Services work differently: there's no receiving record, so you match the invoice to the PO and get sign-off from whoever ordered the work. That's a two-way match.
How it's done by hand
- 01Gather the documents
The invoice arrives by email, as a PDF or on paper. The receiving record is at the dock, signed by whoever took the delivery. The PO is in your system or a spreadsheet.
- 02Find the PO and the receiving record
Many invoices don't reference the PO number, so someone searches by vendor, date and items.
- 03Compare line by line
Price and quantity on every line. Then tax, freight and the total.
- 04Check it isn't already entered
Search for the same invoice number from the same vendor, and for the same amount on the same date.
- 05Log the differences and dispute them
With the line, the agreed price and the billed price. The vendor sends a credit memo or a corrected invoice.
- 06Release it for payment
Only then does it go into the payment run.
Each invoice takes a few minutes. With hundreds a month, teams spot-check: the big ones get matched, the small ones get paid. Whatever isn't checked gets paid anyway.
Set your tolerances once
Small differences happen: rounding, a freight charge that varies, a price that moved a few cents. Decide in writing what you accept without review. For example, a price difference under 1% or $25 per invoice, whichever is smaller. Anything above that gets stopped.
Tolerances are what make automation work. Without them, every cent stops an invoice and the team goes back to checking by hand.
What you can automate
Almost all of the mechanical work. An AI agent, a program that reads documents and follows your rules, can run the full match on every invoice:
- Read the invoice however it arrives (PDF, photo or a file from the vendor) and turn it into data: vendor, number, date, lines, tax and total.
- Find its purchase order and receiving record, even when the invoice doesn't reference them.
- Compare each line: price against the PO, quantity against what was received, item against what was ordered.
- Recalculate tax and the total, and check the vendor against your vendor master.
- Look for duplicates across everything entered, not just this month.
- Prepare the dispute: the line, the agreed price, the billed price and the difference.
By handThe team checks a sample: the big invoices.
AutomatedEvery invoice gets checked the same way.
By handA discrepancy shows up after payment, if at all.
AutomatedA discrepancy stops the invoice before payment.
By handDisputes are built from memory.
AutomatedDisputes go out with the line, the agreed price and the billed price.
Example · USD · Not a real invoice
One invoice, matched line by line
| Line | Purchase order | Received | Invoice | Result |
|---|---|---|---|---|
| Bearing 6204 | 20 × $45.00 | 20 | 20 × $49.50 | Price 10% over the PO |
| Oil seal 35 × 52 | 40 × $18.00 | 30 | 40 × $18.00 | 10 billed, not received |
| V-belt A42 | — | — | 5 × $62.00 | Not on the PO |
| Grease, 1 lb | 10 × $7.00 | 10 | 10 × $7.00 | Matches |
To dispute before paying, before tax$580.00
$90.00 on price, $180.00 on quantity and $310.00 for an item nobody ordered. The grease goes through without anyone looking at it.
The rule that holds it together: what matches goes through; what doesn't gets stopped and reaches a person with the case already built.
What a person should still decide
- Tolerances. What you accept without review. Decided once, applied every time.
- Announced price increases. If the vendor gave notice, someone has to accept it and update the agreed price.
- Substitutions. A different brand or size arrived. Whoever does the buying decides if it's acceptable.
- Bank account changes. Confirm by calling a number you already have on file, even if the email looks like it came from the vendor. It's a common fraud.
- Payment. The system prepares it; a person releases the money.
Where to start
- 01Measure how it works today
How many invoices a month, from how many vendors, how long each one takes and how many actually get checked.
- 02Get the documents in order
Every purchase with a PO, every delivery with a signed receiving record, somewhere you can search. Without a PO there's nothing to match against. If they live on paper or in scattered spreadsheets, start there: business software puts them in order.
- 03Send invoices to one inbox
An address like ap@yourcompany.com, with paper invoices scanned into it.
- 04Write down the rules
Tolerances, who approves which amounts, and what happens to an exception.
- 05Start with your biggest vendors
The ones that bill you the most. That's usually where most of the money is.
- 06Run it in parallel for a month
The system flags, the team checks as usual, and you compare. When they agree, the team moves to reviewing exceptions only.
How we run it at Relevo
We train an agent on your rules, connect it to your AP inbox and your purchasing records, and run it for you: when a vendor or an invoice format changes, we adjust it. You can hire it on its own, without the Relevo platform.
How the process works: supplier invoice checks. The other processes we run: automation.