HomeCase studies: Ivalua procurement transformation and programme deliveryCase study: building BNP Paribas’s group source-to-pay platform on Ivalua v156
Case study: building BNP Paribas’s group source-to-pay platform on Ivalua v156
At BNP Paribas I helped build and deploy the group’s source-to-pay platform on Ivalua v156: suppliers, sourcing, CLM, catalogue, BPM and e-procurement. I worked hands-on from design to SQL, led a mixed team of 15 and supported entity rollouts in France and abroad.
- Client
- BNP Paribas
- Platform
- Ivalua v156
- Role
- Business & tech consultant
- Period
- 2020–2023 (v156 and v164)
- Status
- Delivered on budget and on schedule
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 did BNP Paribas set out to build?
BNP Paribas set out to run its procurement on one group source-to-pay platform, on Ivalua. Version 156 was the first full cycle: design the platform, configure it, connect it to the systems around it, then deploy it entity by entity. It was the first of three full-cycle implementations I have worked on for the group; the first two ran between 2020 and 2023.
Source-to-pay covers the whole chain from finding and contracting a supplier to paying the invoice. For the basics of the buying side, eProcurement Toolkit has a neutral guide to e-procurement.
Which Ivalua modules did the v156 platform cover?
The platform covered six Ivalua modules: suppliers, sourcing, CLM, catalogue, BPM and e-procurement. The table says what each module covers in Ivalua in general; how the group configured them stays with the client.
| Module | What the module covers in Ivalua |
|---|---|
| Suppliers | The supplier record and its lifecycle: registration, qualification, data kept up to date |
| Sourcing | Tenders and requests for proposals, from the request to the award |
| CLM | Contract lifecycle management: drafting, approval, signature and follow-up of contracts |
| Catalogue | The catalogues users order from |
| BPM | The approval workflows that route each request and document |
| E-procurement | Requisitions and purchase orders, the day-to-day buying |
Six modules in one platform: the full source-to-pay chain, not a single process.
The platform carried many complex specific configurations. That matters for what came next: it is the reason the group later chose a complete redesign on v164 rather than carrying the configuration forward.
What was my role on v156?
I was a business and technical Ivalua consultant on the programme, which meant working on both sides of the same feature: what procurement needed, and how to make Ivalua do it.
- Design: turning procurement requirements into an Ivalua design.
- Configuration: building that design in the platform.
- Integrations: the flows between Ivalua and the group’s other systems.
- Custom SQL: the queries behind reports, controls and data flows.
- Team: across 2020–2023 I led a mixed team of 15.
- Change management and user support on the entity rollouts, in France and internationally.
What was the outcome?
The platform was built and deployed. The two implementations I worked on for the group between 2020 and 2023, v156 and then v164, were both delivered on budget and on schedule.
No figures on entities, users, suppliers or spend are published here: they belong to the client.
What happened to the platform after v156?
The same platform went through two more full cycles. On v164 it was redesigned completely to reset and simplify the specific configurations; on v182 a new solution was built from scratch, delivered on schedule and still evolving. All four case studies are listed on the case studies page.
Already running? Check where you stand.
The health check scores your platform and your programme in three weeks.