HomeCase studies: Ivalua procurement transformation and programme deliveryCase study: a new Ivalua v182 solution for BNP Paribas, built from scratch
Case study: a new Ivalua v182 solution for BNP Paribas, built from scratch
For the third full Ivalua cycle at BNP Paribas, a new solution was built from scratch to move the group platform from v164 to v182. Delivered on schedule and performing better, it is still evolving, in a parallel run with the old version while entities and users switch over.
- Client
- BNP Paribas
- Platform
- Ivalua v182
- Role
- Techno-functional consultant, S2P/ERP
- Period
- July 2025 – now
- Status
- Delivered, still evolving; parallel run and switch-over
Three versions, one thread
Built and deployed the group S2P platform on v156, redesigned it completely on v164, and delivered the new v182 solution built from scratch, still evolving: ERP and supplier interfaces, migration, advanced SQL.
- v156
Build and deploy
Suppliers, sourcing, CLM, catalogue, BPM, e-procurement
- v164
Complete redesign
Same group, a new design end to end
- v182
New solution, delivered and evolving
From scratch, ERP and supplier interfaces, migration
Current
What was the v182 programme?
BNP Paribas runs its group source-to-pay on Ivalua. The platform was built on v156 and redesigned completely on v164. The v182 programme is the third full cycle: a new solution built from scratch, not an in-place upgrade of v164. I joined it in July 2025 as a techno-functional Ivalua consultant, on the S2P side and on the links to the ERP.
Where does the programme stand?
As of October 2026, v182 is delivered, went live on schedule and is still evolving. The old and the new versions now run in parallel, and all entities and users are being switched over to v182 progressively rather than in one cut-over.
- Build the new v182 solution from scratch, with its interfaces.
- Migrate the data from v164, with quality controls and duplicate detection, through to sign-off.
- Go live on schedule.
- Run v164 and v182 in parallel.
- Switch entities and users over to v182 progressively, in France and internationally.
What did I do on v182?
| Workstream | My hands-on scope |
|---|---|
| Design and configuration | Functional design of the new solution and its configuration in Ivalua |
| Integrations | Supplier and ERP interfaces, catalogue, system-to-system data flows |
| Custom SQL | Advanced queries for reports, controls and data flows |
| Migration | Workstreams end to end: data quality controls, duplicate detection, flow documentation, through to sign-off |
| Change management | Entity rollouts in France and internationally |
Functional and technical in one role: the design, the interfaces, the SQL and the migration behind it.
On the migration, each flow is documented and its data checked for quality and duplicates before it is signed off.
What was the outcome?
- Delivered and still evolving: the new v182 solution is in production and continues to change.
- On schedule: the go-live date was met.
- Better performance than the version it replaces.
- Switch-over under way: entities and users are moving from v164 to v182 progressively, with both versions in parallel until then.
No figures on entities, users, suppliers, team size or spend are published here: they belong to the client.
Which systems does v182 connect?
Ivalua v182 sits between the group ERP and the supplier side. The flows I worked on are the supplier interfaces, the ERP interfaces and the catalogue, with the system-to-system data flows between them. Custom SQL carries the reports and the controls that watch those flows.
The three cycles are listed together on the case studies page.
Already running? Check where you stand.
The health check scores your platform and your programme in three weeks.