An invoice should not pass only because it resembles a purchase order. Three-way matching compares what was approved, what arrived and what was billed before payment is released.
Short answer
Use a shared line identifier, normalize units and currency, then compare price, quantity and charges. Differences within an approved tolerance continue to review; differences outside it become owned exceptions. Missing receipt evidence must never become automatic acceptance.
| Comparison | Pass condition | Exception owner |
|---|---|---|
| PO × invoice | item and price fit tolerance | buyer |
| Receipt × invoice | previously matched plus current quantity does not exceed available receipts after returns and cancellations | operations; hold payment until reconciled |
| Charges and discounts | approved rule explains variance | finance |
| Duplicate invoice | tax key and content are not repeated | investigation queue |
approved purchase order → recorded receipt → received invoice
→ normalize lines → compare price + quantity + charges
→ approve, request correction or investigate
→ release payment only after decision
Dynamics 365 defines three-way matching as comparing invoice price to the purchase order and invoice quantity to corresponding product receipts. A tolerance is not permission to ignore a mismatch; define it by category, risk and materiality.
Pilot with synthetic documents: partial delivery, unexpected freight, mismatched unit, duplicate invoice and missing receipt. Pass only when every hold is explainable, no exception is paid and the decision trail can be reconstructed.
Connect this control to purchase approval and e-invoice automation. Approving, receiving and paying are separate decisions.