By Katari Technologies Ltd · Published
What it is
A three-way match is a payables control. Before an invoice is paid, you compare three documents: the purchase order (what you asked for), the receipt (what arrived) and the invoice (what the supplier is charging). If they agree, the invoice can move forward. If they do not, the difference is looked at first.
A simple example: you order ten boxes of filters at an agreed price. Eight arrive. The invoice charges for ten. Without a match, the invoice looks fine on its own and gets paid. With a match, the gap between the receipt and the invoice is visible before any money moves, and someone asks the supplier about the missing two.
What it catches
Because each document is produced by a different person or party, a match is a cheap and effective check.
- Invoices for goods or services that never arrived
- Quantities or prices that differ from the order
- The same invoice entered twice
- Invoices with no order behind them
Making it practical
Matching only works if the order and the receipt are recorded. Raise purchase orders for what you buy, record receipts when goods arrive and capture invoices in the same system so differences are shown automatically. Keep supplier bank details approved and changed only by people with that permission.
Approvals then follow your rules: the right people approve, payments go out in batches and the record shows who did what.
Common mistakes to avoid
Three-way matching is simple to describe and easy to undermine. Most failures come from the same few habits.
- Paying from the invoice alone because the goods “obviously” arrived
- Letting one person raise the order, record the receipt and approve the payment
- Accepting partial deliveries without recording what was actually received
- Treating a small difference as noise, so tolerances quietly grow over time
In Kinetic VOC
Kinetic VOC keeps suppliers in one register, compares order, receipt and invoice, flags duplicates and applies approval workflows before payment, with ageing and spend reports afterwards.