Described, the three way match is a comparison. Run daily in a payables team, it is a queue of exceptions plus a large number of invoices that clear without anybody looking at them. How comfortable the team is has almost nothing to do with the comparison and almost everything to do with how the failures are presented, routed and aged.
What clears without attention
Invoices with an order and a receipt behind them that agree within tolerance. In a healthy process these are the majority by count and a small minority of the effort. Improving how they are handled produces little, which is why capture-focused projects sometimes underdeliver against expectations set by invoice counts.
What a good exception looks like
The reason it failed, the two numbers that disagree, the line involved, an owner who can resolve it and an age. That combination turns a stuck invoice into a short conversation with a specific person. An exception that only says the match failed is a research task, and a queue of those is exhausting.
The rhythm that keeps the queue small
Weekly, chase the oldest item in each exception category by name. Monthly, look at the distribution of reasons and act on the largest, which is nearly always upstream. Clearing the queue repeatedly is work; changing what fills it is improvement, and only the monthly look distinguishes the two.
Questions people ask about 3 way match ap
What is a normal exception rate?
It is bounded by your purchase-order and receipt coverage rather than by a benchmark. Measure that first, then judge the rate against it.
Who resolves each kind?
Price to purchasing, quantity or missing receipt to whoever takes deliveries, supplier problems to whoever maintains records, disputes to a named owner.
Should payables override small differences?
Within tolerance, yes, automatically. Outside it, only with the reason recorded, or the control becomes a formality.