Key takeaways
- A procurement transformation works on six areas at once: operating model, processes, technology, data, people, and responsible sourcing. A new tool on top of old habits copies the old habits.
- The usual roadmap: assess, design the target, involve stakeholders, set priorities, deploy in waves, measure. Several public Ivalua cases start with one area, such as sourcing or supplier management, and extend it later.
- Only e-invoicing has fixed dates. In France, every company must be able to receive electronic invoices since 1 September 2026. At EU level, cross-border e-invoicing rules apply from 1 July 2030.
- Every decision ends up in the platform as a role, an approval rule, a mandatory field or an interface. Each exception to the standard costs again at every upgrade.
- My part is the platform: designing, configuring, connecting and evolving Ivalua. Category strategy and the design of a procurement organisation are other people’s work.
What is procurement transformation?
Procurement transformation is a programme that changes how a company buys, and keeps the change in place. It covers the procurement operating model, the processes from need to payment, the source-to-pay software, supplier data and the skills of the team. It runs in stages, with targets you measure. Some firms say “sourcing and procurement transformation” to make clear that strategic sourcing is part of it.
Firms describe the same scope in their own words. KPMG’s target operating model has six layers: process, people, service delivery model, technology, performance insights and governance. Ivalua’s guide lists seven steps, from assessing current processes and the technology stack to managing change. Both treat technology as one part, not the whole programme.
| Area | What changes | A typical situation | Who usually leads it |
|---|---|---|---|
| Operating model and governance | Roles, reporting lines, what is decided centrally or locally | Two regional teams buy from the same supplier on different terms | The CPO and executive management, often with a consulting firm |
| Processes | The path from need to payment, the same across entities | Each entity has its own approval chain for purchase requests | Procurement, with finance and the business |
| Technology | The source-to-pay suite, its interfaces with the ERP and with e-invoicing networks | A supplier’s e-invoice arrives through an approved e-invoicing platform, and nobody has decided where it goes next | Procurement and IT, with an integrator or certified consultants |
| Data | Supplier master data, spend classification, data quality | The same supplier exists three times, with three addresses | Procurement, accounts payable and IT |
| People and change | Training, new roles, adoption of the tool | Requesters keep emailing their needs to a buyer | Procurement, HR and the project team |
| Responsible sourcing and risk | Sustainability criteria in tenders, supplier assessment | The supplier sustainability questionnaire lives in a spreadsheet, outside the tool | Procurement, sustainability and compliance |
Six areas, worked on together. My work is on the technology row: Ivalua, and the data that goes into it.
This guide looks at the transformation from the platform side, where decisions become screens, rules and data flows. For the source-to-pay processes themselves, without a vendor angle, eProcurement Toolkit’s guides to procure-to-pay and procurement software start from the basics.
What is driving procurement transformation in 2026?
One obligation with fixed dates, e-invoicing, and pressure to do more with the same team. The table gives what each text or survey says, then what it changes in a source-to-pay platform.
| Driver | What the text or survey says | What it changes in the platform |
|---|---|---|
| E-invoicing in France | Since 1 September 2026, all companies must be able to receive electronic invoices through an approved platform. Large and mid-sized companies issue them from the same date; small companies from 1 September 2027 (French government) | The path of each invoice, from the approved platform to the source-to-pay suite and the ERP, has to be designed, built and tested |
| E-invoicing in the EU (ViDA) | Council Directive (EU) 2025/516: the e-invoicing and digital reporting rules for trade between EU countries apply from 1 July 2030. Member states can also require e-invoices at home, each with its own dates | A group present in several countries gets one invoice channel per country before it gets one EU rule |
| Due diligence (CSDDD), after Omnibus I | EU text published on 26 February 2026: the duty now covers groups with more than 5,000 employees and €1.5 billion turnover, from 26 July 2029 | Fewer companies are in scope, but they will ask their suppliers for data. That data sits on the supplier record: questionnaires, documents, expiry dates |
| AI | Hackett, 2026: 43% of organisations are actively deploying AI in procurement, 12% at scale. McKinsey, 2025: AI agents could make the function 25 to 40% more efficient (their analysis) | AI reads the data in the platform. Duplicate suppliers and free-text categories limit what it can do |
| Digital maturity | PwC, 5th Digital Procurement Survey (2024, over 1,000 companies): source-to-pay solutions are the norm for 94% of procurement departments surveyed; target of 70% digitised processes by 2027 | Most companies already have a suite. The question is less which tool, more what the tool is set up to do |
Only e-invoicing has a fixed calendar. The other drivers change what customers, auditors and management ask you to prove, and that proof is data.
McKinsey also reports that among attendees at its procurement forum, only 60% of large and 30% of small organisations have a procure-to-pay system, which it says can deliver a 2 to 5% cost reduction. These are McKinsey’s figures, from its own forum, not a market census.
What does a procurement transformation roadmap look like?
Guides use different names, but the order stays close. Ivalua’s guide gives seven steps, from assessment to change management. Here is that order, with deployment in waves added, and what each step asks of the platform.
- Assess the current state: processes, data, tools and pain points. For example: how many approval chains exist, and in which system each supplier is created.
- Design the target: the operating model, processes and platform you aim for. Decide which system owns each type of data: suppliers, contracts, cost centres.
- Involve stakeholders from the start: procurement, finance, accounts payable, controlling, requesters and approvers, IT, suppliers and executive management. Ivalua’s guide names executive buy-in as its own step.
- Set priorities: quick wins, deeper changes, data prerequisites and dependencies on IT. The business case puts a figure on each priority.
- Deploy in waves: one area, entity or country after another, on a common base, with close support after each switch.
- Measure: indicators chosen at the start, produced by the tool, not corrected by hand every month.
Public Ivalua cases show waves by area as well as by entity. Hutchinson started with supplier relationship management and spend analysis in 2014; in 2023 it added eProcurement, doubling users from 4,000 in Europe to 8,000 worldwide. Scandinavian Tobacco Group went live in 2021 with supplier management, sourcing and contracts in five months, as the first stage of a longer programme. Groupe BPCE rebuilt its Ivalua platforms in three lots, with a gap analysis before each lot.
For a global procurement transformation, waves by country are the norm. Each country brings its own legal entities, approval rules, languages and, now, its own e-invoicing dates. The common base matters more than the speed of the first country. On Ivalua, How does an Ivalua implementation work? describes the project steps themselves.
Where does the source-to-pay platform come into a procurement transformation?
Wherever a decision has to become a rule the tool applies. An operating model, a process or a sustainability policy written in a document changes nothing until someone configures it. Here is how each area arrives in a platform such as Ivalua.
| Transformation decision | What it becomes in the platform | The question to settle |
|---|---|---|
| A target operating model | Roles and rights: who creates a supplier, who approves a request, who signs a contract | Can a local buyer create a supplier, or only request one? |
| A common process | One approval chain, plus a list of exceptions granted by entity | Does this entity keep its own rule, knowing it will be tested again at every upgrade? |
| A responsible sourcing policy | A supplier questionnaire, mandatory fields, a scored criterion in tenders | Does the questionnaire block supplier creation, or only the assessment? |
| Clean supplier data | One system that creates suppliers, duplicate checks, an interface with the ERP | Is a supplier created in the source-to-pay suite or in the ERP? |
| Indicators | Reports produced by the tool, from reliable data | Who corrects wrong data, and in which system? |
Each row is a procurement decision, not the integrator’s. The platform only applies what was decided, and shows what was not.
Each exception to the standard has a cost that comes back. Ivalua’s contract terms published in 2023 require an upgrade at least every two years. An approval rule built for one entity only must be tested again at each upgrade. That is typical of Ivalua projects.
When the transformation stops at the document, three signs usually appear in the tool: each upgrade takes longer, users go around the platform, and reports need manual fixes. An Ivalua health check starts from these signs.
Sometimes the platform side means a rebuild. On BNP Paribas’s source-to-pay platform, v156 carried many complex specific configurations. v164 was a complete redesign built from scratch: it simplified those configurations and redesigned the workflows. I worked on both, then on v182, also built from scratch.
What results do companies report from a procurement transformation?
Published results exist, but most come from surveys of self-reported performance or from vendor case studies. The table says which is which.
| Source | What it reports | What kind of evidence |
|---|---|---|
| Deloitte, Global CPO Survey 2025 | Organisations “betting big in the right ways” met or beat their plan more often than followers: cost savings 96% vs 80%, internal stakeholder satisfaction 84% vs 59%, innovation 56% vs 24% | Survey of procurement leaders, self-reported |
| Piramal Glass, in Ivalua’s guide | 19% annual cost savings over four years; 75% shorter cycle time for contracts and catalogues; 40% shorter requisition-to-order cycle | Vendor case study |
| Virginia eVA, Ivalua case study | More than $5 million of annualised savings; average solicitation cycle down to 69 days from 121 | Vendor case study |
Use these figures to frame a business case, not as a promise. Your own baseline, measured before you start, is the only number that proves your result.
Who does what in a procurement transformation?
No single party covers the six areas. Consulting firms mostly work on the operating model, category strategy and the roadmap. Integrators and certified consultants do the work in the tool. The vendor provides the platform and its releases. Who to hire for which part, with what consultancies sell and what public buyers paid, is covered in procurement transformation consulting.
| Party | What they do | The question to ask them |
|---|---|---|
| Large consulting firm | Strategy, operating model, risk, sustainability, digital roadmap | Who will do the work, by name? Does the firm have an alliance with a software vendor? |
| Procurement consultancy | Spend analysis, category strategy, savings, governance, skills | Does the firm work in the platform itself, or only on the target? |
| Integrator | Configuration, interfaces, data migration, run and upgrades | How many certified people on the platform, and at which level? |
| Software vendor | The platform, support, release calendar | Which releases will be available during your rollout? |
| Independent platform consultant | Design, configuration, ERP interfaces, data migration, SQL, on a platform they know first-hand | Have they done this work themselves on a comparable project? |
For the operating model and category strategy, a procurement consultancy. To make the transformation work in Ivalua, certified people who configure it themselves.
On Ivalua, certification matters for the work itself: Ivalua’s 2023 terms require Level 2 to configure and Level 3 to build integrations. What I do not do: category strategy, the design of a procurement organisation, and neutral software selection. I implement Ivalua, so I am not neutral.
How can I help with your procurement transformation?
On the Ivalua part of your transformation, in three ways, depending on where you are.
| Your situation | What I offer | Duration | Price |
|---|---|---|---|
| The transformation runs on Ivalua and you lack a senior profile | Senior mission: techno-functional lead or programme manager in your team | Custom | Day rate, on request |
| You need several Ivalua profiles to deliver | An Ivalua team I lead, with certified consultants from my network | Custom | Day rate per consultant, on request |
| Ivalua is live and you want to know what it can carry | Ivalua health check: each area rated, with a 90-day plan | 3 weeks | From €12,500, fixed price |
A mission or a team to do the work; a fixed-price health check when you first need to know where you start.
On a mission, I do the work myself: design, configuration, supplier and ERP interfaces, data flows, advanced SQL for reports and controls, and data migration end to end. I have also supported change on entity rollouts, in France and abroad. If you are several versions behind, the Ivalua upgrade starts with an assessment from €7,500.
I am certified Ivalua L1, L2 and L3 and have worked on three full-cycle Ivalua implementations at BNP Paribas. To discover the platform, read What is Ivalua?. All my services are on the procurement consulting page. The tools and data side, from supplier data to e-invoicing dates by country, is covered in digital procurement transformation.
Frequently asked questions
Short answers to the questions people ask, each one sourced above.
What is the difference between procurement transformation and digital procurement transformation?
Digital procurement transformation is one part of procurement transformation: the platform, the data, automation and AI. Procurement transformation also covers the operating model, processes, skills and responsible sourcing. The two move together: a tool without a reviewed process copies the old approval chains.
How long does a procurement transformation take?
No standard duration is published: it runs in waves, and each wave has its own plan. The platform project is one part. Public Ivalua cases range from five months for a first sourcing and contracts scope, at Scandinavian Tobacco Group, to programmes extended over years, such as Hutchinson’s, started in 2014 and extended in 2023.
Do you need new software to transform procurement?
Not always. If your current platform covers your needs but carries too many specific configurations, a rebuild on the same software can be enough. BNP Paribas did that with v164, rebuilt from scratch on Ivalua. Start by assessing what the current tool can carry. If you do change software, eProcurement Toolkit’s procurement software guide is a neutral place to start.
What is a procurement transformation strategy?
It is the plan that links the company’s goals to the six areas: which operating model, which processes, which platform, which data, which skills, in which order. It ends in a roadmap of waves with indicators. The strategy is set by procurement leadership; the platform team turns each choice into roles, rules and interfaces.
Who does the platform work in a procurement transformation?
Integrators and certified platform consultants. They turn each choice of the transformation into roles, approval rules, ERP interfaces and data migration in the tool. Consultancies mostly work on the target, the roles and category strategy. Who to hire for which part is covered in procurement transformation consulting.
Project already started? Check where it stands.
The health check scores your platform and your programme in three weeks.
