SAP division
The exception queue is the business process now.
We optimise OpenText Vendor Invoice Management so that invoices go through automatically more often — and so the ones that do not are routed to someone who can actually resolve them.
What usually goes wrong
The problems we get called about.
- A touchless rate that never improved.VIM was implemented to automate AP. Years later a large share of invoices still gets touched by a human.
- An exception queue nobody clears.It grows faster than it shrinks. Some items have aged into a different problem entirely.
- Approvers who have stopped approving.Invoices routed to people who do not know why they received them, sitting until somebody chases.
- Rules that misfire.Duplicate detection and tolerances set at go-live that no longer match how your suppliers actually invoice.
- Month end driven by AP backlog.Accruals built on guesswork because nobody knows what is really in the queue.
What's included
Scope, in plain terms.
- Baseline analysis.Exception volumes by type, vendor and approver, with the manual effort quantified.
- Rule and tolerance tuning.Matching, duplicate detection and tolerances reset against real invoice behaviour.
- Workflow optimisation.Routing that reaches people who can resolve the item, with escalation that works.
- Integration fixes.The SAP side: PO matching, GR handling, master data problems that surface as VIM exceptions.
- Enhancements.Controlled changes to VIM configuration and custom logic.
- Ongoing support.Day-to-day VIM incidents handled as part of a BAU arrangement.
Almost every VIM problem gets described as a system issue and turns out to be four specific exception types generating most of the manual work.
Free, no obligation
Let's look at one problem properly.
One problem area, examined by an engineer. You get a written findings note and a fixed-price proposal. No charge, no obligation.
Book a 45-minute technical review →