Experience
Work we have delivered
Below is a Source-to-Pay programme that both our founding partners worked on in previous roles at a global banking and financial services firm, and couple of engagements delivered by Elevion itself. Client names are withheld under confidentiality.
Previous roles, both founding partners
Source-to-Pay transformation with Ivalua: the scale
The figures below describe the Ivalua Source-to-Pay platform at a global banking and financial services firm where both our founding partners worked. Raja Ramasamy led the implementation and ran Ivalua operations support. Durganand Jha led the procurement teams that were the platform’s largest users. The figures show the scale we are used to working at.
US$5 Bn
Total spend
85+
Legal entities
40,000+
End users
125 K
Total contracts
70+
Hosted catalogues
100 K
Annual requisitions
Results achieved
Business impacts achieved
80%+
Adoption rate
40%
Reduction in procure-to-pay cycle time
8–10%
Cost savings
Real time
Visibility and compliance
Data driven
Decision making
Delivered by Elevion
Independent Ivalua assessment and recovery roadmap
Manufacturing group · Independent review of a live Ivalua Source-to-Pay platform and its SAP integration · Delivered by Elevion Partners in 2026
The situation
The client had been live on Ivalua for some time but was still firefighting. Advance shipping notices failed often, leaving lorries backed up at receiving and production at risk. Supplier records created in Ivalua produced errors and duplicates in SAP. Purchase order workflows created duplicates, suppliers could not trace their orders, and audit trails were incomplete. Support was slow, tickets were closed without the client agreeing, and fixes went live without proper testing or sign-off.
What we did
Two senior partners, each with more than nine years of Ivalua experience, spent two days on site with senior stakeholders and watched the problems happen. Two further weeks of interviews and a full configuration review followed, with an Ivalua Level 3 certified expert from our team alongside. Every major issue was examined through a people, process and technology lens, and nothing was concluded from a single source.
What the client got
- The real causes named: Ivalua configuration and the Ivalua to SAP integration, made worse by gaps in support response.
- A governance routine: monthly reviews with the client, Ivalua and the support provider until the platform is stable, then quarterly reviews against agreed measures.
- Proper support structures: tiered support with service levels, refreshed test environments, and a release process with client sign-off and post-release checks.
- Two costed routes: a three to four month fix of configuration and integrations for quick relief, or a six to eight month rebuild to reset the platform.
- A prioritised roadmap and an informed choice, rather than a list of problems.
Delivered by Elevion
Invoice processing productivity review
Global enterprise · Review of a multi-region accounts payable operation running on SAP · Delivered by Elevion Partners in 2025
The situation
The client’s invoice processing teams handled work for Asia-Pacific, North America, Europe and Latin America. Productivity had stalled at around 35 invoices per associate per day, even though the invoice tools were connected to SAP. Each business unit used its own capture and workflow tools, invoice formats and approval routes. Management wanted to know why the figure was low, and how to raise it without weakening accuracy, controls or turnaround time.
What we did
Over three months we worked alongside operations leaders and subject-matter experts across three operating groups, and walked through the work as it is actually done: receipt, scanning and indexing, PO and non-PO invoices, two-way and three-way matching, price, quantity and goods-receipt exceptions, work allocation, payment runs and vendor queries. We asked the question someone who has run these teams would ask: where does an associate’s day really go?
What we found
- The headline figure hid much of the work. Manual indexing took about an hour per associate per day for each company code, and none of it was counted.
- Invoices reached people before they were ready. Missing or wrong PO details, no goods receipt, blocked PO lines or missing approvals meant associates checked and parked invoices that could not be posted.
- Invoice capture was unreliable, so associates corrected and re-keyed data before real processing could start.
- Work was allocated by hand, by company code, not by readiness, complexity or live workload.
- 80 to 90% of vendor queries were simply asking about invoice or payment status.
- The data for a reliable baseline was missing: time per stage, the outcome of each touch, and why postings failed.
What the client got
- A clear explanation of the low figure, including the hidden effort it left out.
- Practical fixes first: readiness checks before invoices reach the queue, allocation by readiness, complexity and skill, exceptions routed to named owners, and proactive status updates to suppliers.
- Automation where it pays: better invoice capture, automated indexing and rule-based matching for standard invoices, with exceptions sent to people. Our early estimates pointed to about 12% from automated indexing and 15% from better allocation, to be confirmed by a pilot against a measured baseline.
- A five-phase roadmap: set the baseline, deliver quick wins, pilot automation, strengthen performance management, then scale what works.
- A way to prove the benefits, rather than assume them.
Facing something similar?
Tell us what is happening with your platform. You will speak to a founding partner, and you will get an honest view of whether we can help. If you are already live on Ivalua, a no-cost health check is a good place to start.