HomeServicesIvalua health check: an audit of your platform and programme in three weeks
Ivalua health check: an audit of your platform and programme in three weeks
An Ivalua health check is a fixed-price audit of a platform in production: configuration, workflows, roles, supplier data, ERP interfaces, performance, licences and upgrade position. In three weeks you get a scored diagnosis, the findings and a 90-day plan. From €12,500.
Who is an Ivalua health check for?
Procurement, procurement-systems and IT leads who run Ivalua in production and want an outside reading of where it stands. Two situations call for it: you suspect drift but cannot name it, or a new CPO or programme owner wants a baseline before deciding what comes next.
The health check looks at a platform that is live. If your project has not gone live yet and the plan no longer holds, the project rescue is the better entry. If the main question is a version upgrade, see the upgrade assessment.
What does an Ivalua health check cover?
Twelve areas, each read in your environments and documents, not only in interviews. The list follows what Ivalua’s own contract terms make costly and what a public run contract for an Ivalua platform asks for: incidents and performance in data and interfaces, upgrade sessions, hotfixes.
| Area | What I check | Why it matters |
|---|---|---|
| Configuration and custom objects | The inventory of specific configurations, custom objects and fields, and whether each one is still used | In Ivalua’s standard terms, customisations and complex configurations added after go-live incur labour charges at every upgrade |
| Workflows (BPM) | Number of circuits, steps and exceptions; rules nobody can explain end to end | Virginia’s eVA, on Ivalua, reports requisition workflows stalling with timeouts under heavy workflow logic (release notes, February 2026) |
| Roles and security | Role matrix, segregation of duties, accounts that should no longer exist | Rights decide what each user, and any assistant acting for them, can see and do |
| Supplier data | Duplicates, statuses, bank details, ownership of the supplier record | Duplicate suppliers break reporting, payments and onboarding |
| ERP interfaces | Error and rejection rates, replays, monitoring, what happens when a message fails | EnBW’s run contract for its Ivalua platform singles out incidents and performance in data management and the SAP integration |
| Catalogues and punchout | Catalogue freshness, punchout connections, what users order outside them | Off-catalogue buying is a sign users work around the platform |
| Reporting and SQL | Specific reports and queries, their cost on performance, manual fixes before each committee | Virginia’s eVA disabled one custom alert whose query caused timeouts, and rewrote another |
| Performance against the SLA | Response times and incidents compared with the SLA in your contract | Your contract defines what Ivalua commits to, and what it excludes |
| Licence usage | Actual users and volumes against the metrics you pay for | In Ivalua’s standard terms, usage beyond the ordered metrics is invoiced, at standard rates unless the order sets the price |
| Version currency | Version in production, date of the last upgrade, versions behind | Ivalua’s standard terms require an upgrade at least every two years |
| Test and release process | Non-regression scripts, environments, how a change reaches production | Upgrades require test scripts written by the customer |
| Governance | Who decides on changes, design authority, change board, link with the integrator | Without a decision path, every change request becomes a negotiation |
Twelve areas, one scored reading: the platform, its data, its interfaces and the way changes are decided.
Sources: Ivalua’s standard terms (next section); Virginia eVA release notes, February 2026; the EnBW run contract for its Ivalua platform, TED notice 750093-2023.
What do Ivalua’s standard terms say about upgrades and performance?
Ivalua’s standard terms are rarely public, but the master agreement signed in 2023 with the State of Maine, under the NASPO ValuePoint cooperative contract, publishes them. They explain why version currency, configuration debt and test scripts are part of the health check:
- Ivalua recommends at least one upgrade every 12 to 18 months and requires the customer to upgrade at least once every two years.
- After go-live, customisations or complex configurations and integrations not covered by the subscription incur labour charges for each upgrade.
- An upgrade starts only when the customer has written detailed test scripts, a project plan is signed and the target version is generally available.
- If the customer is not in compliance with the upgrade process, Ivalua is not responsible for defects, security issues or a missed SLA.
- The SLA in the same contract sets availability at 99.80% per month and a hit response time under 3 seconds for 90% of hits.
Source: Ivalua’s standard terms in a public US contract, master agreement MA 18P 23081100000000000020, effective August 2023. Ivalua may have updated its terms since; your own contract is the one that applies, and reading it is part of the health check.
What do you receive at the end?
- A scored diagnosis: each of the twelve areas scored, with the evidence behind the score.
- The findings: what is wrong, where it shows in the platform, and what it costs you today or at the next upgrade.
- A 90-day plan: the actions in order, who carries each one (your team, your integrator, Ivalua), and what can wait.
- A restitution: a session with your team and sponsors to go through the findings and the plan, and to answer questions.
The written report is yours. It is written so that your team or your integrator can act on it without me.
How do the three weeks run?
- Before week 1: we agree the scope and you grant read access to the environments and share the project documents.
- Week 1, collect: I read the configuration, workflows, roles, interfaces and reports in your environments, and hold the first interviews (six to eight in total) with procurement, IT and the integrator.
- Week 2, analyse: I check data quality, interface logs, performance and licence usage, finish the interviews and test the first findings with your team in a workshop.
- Week 3, restitution: I score each area, write the report and the 90-day plan, and present them in a second workshop.
The work is remote, plus two workshops with your team. I do the health check myself, from Cape Town (UTC+2), in French or English.
What does an Ivalua health check cost?
From €12,500 excluding VAT, at a fixed price, for three weeks. The written proposal confirms the price once we have agreed the scope: the number of modules and interfaces in production decides it.
The experience behind it: three full-cycle Ivalua implementations at BNP Paribas, on v156, v164 and v182, from design and configuration to integrations, custom SQL and migration. Certified Ivalua L1, L2 and L3.
Frequently asked questions
What access do you need?
Read access to the environments in scope, the project documents (design, specifications, interface documentation, test material) and six to eight interviews with procurement, IT and, if you have one, your integrator. I do not need write access: the health check changes nothing in your platform.
Can our integrator take part?
Yes, and it helps. The integrator knows why things were built the way they were. The interviews include them, and the findings separate what belongs to the platform, to your team and to the integrator, so the plan is usable by everyone.
Is the health check a best-practice review against Ivalua’s standard?
Partly. Distance from the standard matters because Ivalua’s own terms charge labour for complex configurations at every upgrade. But the health check scores what each choice costs you, not how far it sits from a textbook. A specific configuration that earns its keep stays in the plan.
What happens after the 90-day plan?
Your team or your integrator can carry it alone. If you want help, I can take a senior mission on part of the plan, or lead an Ivalua team for a larger scope. Nothing obliges you to continue with me.
Do you sign a confidentiality agreement?
Yes. The environments, documents and findings stay confidential, and the report belongs to you. Nothing from a health check is published or reused as a case study without your written agreement.
30 minutes. Your project, my honest read.
Tell me where the programme stands. You leave the call with a view on risk and the next step, whether or not we work together.