How does VIM handle three-way matching?

Three-way matching in VIM compares the vendor invoice against the purchase order (PO) and the goods receipt (GR) before payment is released. When a PO invoice enters the system, VIM checks that quantities, prices, and line items align with what was ordered and what was actually received.

Invoices within the tolerance levels configured in SAP's logistics invoice verification settings post automatically. Invoices outside tolerance are blocked for payment and routed as exceptions. In practice, many matching failures are not AP problems at their root: a missing goods receipt belongs to Receiving, and a price mismatch often belongs to Procurement, so we configure routing to send each failure to the team that owns it, with the resolution action built into the screen, for example opening the goods-receipt transaction pre-filled for the right PO line instead of leaving the user to find it. Two design decisions matter most. Tolerance thresholds set too tight flood the process with exceptions, while thresholds set too loose let incorrect payments through, and setting them well requires knowing your actual variance patterns rather than accepting defaults. Goods-receipt timing needs equal care, because electronic invoices now arrive faster than physical goods, and a configured wait period on GR-related checks prevents a flood of artificial exceptions in the days before receipts are posted.