In this guide 6 sections
Extracted invoices fail three way matching usually because the invoice, the purchase order and the goods receipt disagree, not because the reader erred. Common causes are part deliveries, unit of measure differences, rounding, price changes after the PO and a late goods receipt. Route each to a named person, never to auto-post.
Most failures are real disagreements
Teams blame the extraction. Sometimes the reader did misread a digit. More often the invoice says one thing, the PO says another, and the warehouse recorded a third quantity entirely, so the disagreement is real.
Three way matching compares the invoice, the PO and the goods receipt, line by line, before any payment is released to the supplier. The PO states what you ordered and at what price, the goods receipt states what arrived, and the invoice states what the supplier wants paid. A mismatch means the control works.
Sort failures by cause first. Better extraction cannot post a missing receipt.
Part deliveries and late receipts
A supplier ships 400 of 1,000 bolts and invoices the full order, or ships in two lots and sends one invoice covering both. The receipt says 400. The invoice says 1,000. The match fails by design.
Late receipts look the same at the finance desk. Goods arrived on Monday, the storekeeper posted the receipt on Thursday, and the invoice landed on Tuesday and failed although the delivery itself was perfectly fine.
Route both to stores and ask one question: has every line on this invoice physically arrived at the dock and been counted against the delivery note? Finance should never guess. A short note from the storekeeper, kept with the invoice and the delivery note, settles most of these within minutes and leaves an audit trail.
- Invoice quantity above receipt quantity
- Receipt posted after the invoice date
- One invoice covering two shipments
- Partial lot closed early on the PO
Units, rounding and price drift
Unit of measure differences cause quiet failures. The PO is in metres while the invoice is in rolls, or the PO lists one carton of twelve while the invoice lists twelve singles. The extracted numbers are right. They still disagree.
Rounding is smaller but constant, because a unit price carried to four decimals and multiplied by a large quantity lands a hair away from the supplier’s line total. Set a written tolerance and route anything outside it to the buyer, who can accept the difference or query the supplier before the payment run.
Price changes after the PO are the touchiest. A supplier raises a rate between order and dispatch, and a buyer must accept it, dispute it or amend the PO. Finance only pays what was agreed.
Route each cause to a person
Give every mismatch type a fixed owner and a short reason code, such as QTY, UOM or PRICE, so the queue sorts itself by owner. Quantity gaps go to stores. Unit conversions go to whoever owns the item master, price variances go to the buyer and category head, and a missing PO goes to purchasing.
The invoice stays parked with its extracted fields and all three documents side by side, so the owner sees the exact line that failed instead of a vague error. They fix the cause. The match runs again.
Never post a failed invoice automatically. Not even a small one. A silent post is how overpayments begin.
- Quantity gap: storekeeper
- Unit conversion: item master owner
- Price variance: buyer and category head
- No PO found: purchasing
- Tolerance breach: accounts payable lead
Fix the repeat offenders
Tally one month’s failures by supplier. A handful of suppliers usually produce most of them, because one always bills in a different unit and another invoices before the truck even leaves.
Fix those at the source. Add a unit conversion to the item master, ask suppliers to quote the PO number on every line, and agree that receipts are posted the same day. Each habit removes a whole class of failures from next month’s queue, so small changes at the dock and the item master pay back quickly.
This week, export last month’s failed matches from the payables ledger and tag each with one cause code and one named supplier. The tally shows where to act first. It also shows which supplier to call.
Mismatch triage sheet
A single sheet, one line per failed invoice. Columns: invoice number, supplier, PO number, line, cause code, quantity on invoice, quantity received, price difference, named owner, date routed and date cleared. A footer tallies causes by supplier. It shows the repeat offenders at a glance and gives the buyer a ranked list to take into the next supplier review meeting.
Open a blank worksheet to printQuestions owners ask
What is three way matching?
It compares the supplier invoice with the purchase order and the goods receipt, line by line, so nobody pays for goods that never arrived. Quantity, price and item code must all agree within a written tolerance, otherwise the invoice waits in a queue for its owner.
Should a small mismatch post automatically?
Only inside a written tolerance that a named person approved, for example a rounding difference on a long list of cheap lines. Anything outside the tolerance should park and route to its owner with the documents attached, so nobody hunts through email for the PO copy.
Is the OCR to blame when matching fails?
Sometimes, for blurred scans, skewed photos or unusual layouts, but most failures are real differences between the documents, not misread digits. Check the cause before changing the extraction by opening the three documents side by side and finding the line that disagrees.
How do we cut repeat failures?
Tally causes by supplier each month. Then fix the source. Add unit conversions to the item master, put PO numbers on every invoice line, and post receipts in the warehouse on the day goods arrive.