How does VIM route invoices for approval?

VIM routes invoices based on configurable rules that reflect your AP structure. PO invoices that pass automated matching and fall within tolerance can post without any approval step. Invoices that trigger exceptions or exceed thresholds route to specific approvers based on amount, vendor, cost center, department, or geography, with rule-based approval chains and automatic escalation when an approver does not act.

Non-PO invoices always require manual approval because there is no purchase order to match against; these typically route to the relevant department head. The routing logic can be layered, so an invoice might go to a cost center manager under $10,000 and escalate to a director above it. Because VIM uses SAP Business Workflow underneath, existing organizational models and substitution rules carry over instead of being rebuilt. Approvers can act from mobile devices or SAP Fiori, which removes the delays caused by travel and remote work. Routing also benefits from periodic redesign: in PetSmart's reimplementation, we removed redundant approval steps that had accumulated over years, because the configured workflow no longer matched how the AP team actually operated. Approval paths drift out of date as organizations change, and the workflow should follow.