A 3 way match in accounts payable works perfectly on the invoices that were always going to be fine. The value of understanding it properly is in the ones that fail, because that is where the time goes and where the control actually earns its keep. In practice four failures account for most exceptions, they have different causes, and they want different responses. Treating all four as one queue called exceptions is why matching feels like an administrative burden in some teams and a quiet control in others. This page is the four, what each one usually means, and who should be resolving it.
The price changed since the order
The commonest and the least interesting: a supplier increased a price between order and invoice. It needs a decision about whether to accept, which belongs to the person who committed the spend, not to payables. A recurring pattern from one supplier is a procurement conversation, not a payables one.
The delivery was partial
The receipt shows less than the invoice claims. Usually genuine, occasionally not, and almost always resolvable by the person who received the goods rather than by finance. The risk here is paying in full for a part delivery and never reconciling the rest.
There is no order, or a quantity was typed wrong
A missing purchase order is a purchasing control failure surfacing in payables, and the fix is upstream. A mistyped quantity on any of the three documents is a data error, quick to fix and worth counting, because a high rate usually means somebody is re-keying something that could be captured instead.
Questions people ask about 3 way match accounts payable
Who should clear matching exceptions?
Whoever can actually answer the question. Price changes and partial deliveries belong to the budget holder and the receiver; data errors belong to whoever entered them. Routing everything to finance is what turns exceptions into a backlog.
How many exceptions are too many?
Enough that the queue never empties. On the worked example on this site a 12% exception rate is already 14.4 hours a month, and each point above that is roughly another hour.
Should exceptions block payment?
Yes, otherwise the match is advisory. What should not happen is an exception blocking payment silently while the supplier waits and nobody is accountable for clearing it.