Short Dump Blog - Aktualisiert 3.5.2026 - 6 Min. Lesezeit
Why three-way match training belongs in Source to Pay
Invoice verification is not a finance-only topic; it is where procurement discipline becomes measurable.
Author: Rastislav Janak / s4hanahub team
Problem definition
Three-way match is sold as a clean comparison between PO, goods receipt and invoice. In production it is more often a team-building exercise between procurement, warehouse and finance, usually scheduled after the supplier has already asked for money.
The uncomfortable question
When an invoice is blocked, do users know whether they are looking at a price issue, a missing receipt, a tolerance design or simply a purchasing habit wearing a finance error message?
Source-to-Pay is where procurement discipline becomes measurable. The system does not care who promised what in an email; it compares what was ordered, received and claimed.
This is why three-way match belongs in business training, not only in invoice verification configuration. The blocked invoice is the headline, but the article is usually written earlier by purchasing data and receiving behavior.
Here is the project version: Three-way match is often introduced as a technical rule: compare purchase order, goods receipt, and supplier invoice. For a Source to Pay audience, that definition is not enough. The match is the visible proof that buying intent, operational receipt, and supplier claim agree. That sounds simple, which is how SAP topics lure us into underestimating them.
The SAP evidence trail is less romantic: A useful training module starts before the invoice. It explains why purchase order quantity, price, account assignment, tax code, and delivery tolerance matter. If these values are weak, invoice verification becomes a queue of avoidable exceptions. In a clean demo this takes minutes; in production it asks for ownership, variants and a little courage.
This is where the support ticket usually starts: Goods receipt is the second anchor. Warehouse and service receivers need to understand that timely and accurate receipt is a financial control, not only a logistics step. The screen is only the stage. The process is the plot.
The control angle is the part worth underlining: Finance users need the procurement story as well. A blocked invoice may point to a real supplier issue, a late receipt, a missing approval, or a master-data gap. The right response depends on understanding the upstream process. A consultant should be able to explain this without opening a thirty-slide apology deck.
For training, the useful lesson is this: Good E2E training reduces blame between teams. It gives everyone the same language for tolerance, approval, receipt, block, release, and payment timing. That is the difference between technical navigation and knowledge people can reuse.
A clean match is not magic. It is a small ceremony where procurement, logistics and finance agree that reality, intention and the supplier invoice have finally met each other.