Three-way matching, explained for the people who approve it

Three-way matching is one of those controls everyone in finance nods along to and few outside AP could explain on the spot. It is also where a huge share of payables effort goes. Worth understanding plainly, because it is the single best target for automation in AP.

The three documents

A purchase order says what you agreed to buy and for how much. A receipt says what actually arrived. An invoice says what the supplier wants to be paid. Three-way matching confirms those three agree before money moves. When they do, the bill is safe to pay. When they do not, something needs investigating.

Why exceptions pile up

• Quantities differ: you ordered ten, received nine, were billed for ten.
• Prices drift: the invoice reflects a rate the PO did not capture.
• Timing splits: a partial shipment invoices before the rest arrives.
• References are messy: PO numbers are mistyped or missing entirely.

Each of these is a legitimate reason to pause, but most are small and resolvable. The problem is that a manual process treats every mismatch the same — as a ticket for a human — so analysts spend their days on tolerable variances instead of real ones.

What agents change

An agent matches every invoice against its PO and receipt, clears the ones that agree within your tolerance with no human touch, and routes only true exceptions to a person — already labeled with what differs and a suggested resolution. The approver stops seeing the clean 70% and starts spending their judgment on the 30% that earns it.

The control does not weaken. It gets sharper, because the people running it are finally looking only at the cases that need a human.