What are procurement implementation services?
Procurement implementation services are the work that makes a source-to-pay or e-procurement platform run in your company, once you have chosen it. Someone plans the project, designs your processes in the tool, configures it, connects it to your ERP, loads your suppliers and users, tests everything with your key users, trains people, goes live and hands the platform over to support.
You buy two different things. The licence gives you the right to use the software. The implementation services are people and days of work. Public tenders show the split clearly. In 2025, Southern Water, a UK water company, ran one source-to-pay tender in two lots. Lot 1, the software, went to Coupa for four years. Lot 2, a “Software Implementation Partner”, went to Parade Consulting. The tender asked for a partner accredited or certified by the software provider.
This page looks at what you buy and from whom, written by an Ivalua implementer. For what source-to-pay software does, step by step and with no vendor angle, eProcurement Toolkit’s source-to-pay guide starts from the basics.
What do procurement implementation services include?
Vendors and integrators give the phases different names, but the work is the same. SAP suggests its SAP Activate method for SAP Ariba, in six phases from Discover to Run. JAGGAER publishes five phases: Initiate, Plan, Execute, Validate and Enable. Zycus calls its framework SCALE. An integrator such as hz.group describes four steps, from assessment to rollout and close support after go-live. Each workstream below appears in at least two of these sources.
| Workstream | What the provider delivers | What your team must give |
|---|---|---|
| Scope, governance and plan | Kick-off, project plan, steering committee, list of risks | A sponsor who decides, and key users with time set aside |
| Process design | Workshops and a written design: who requests, who approves, which documents are mandatory | Decisions on approval levels per amount and per entity |
| Configuration | The platform set up to the design: forms, workflows, roles, templates | Quick answers when the design meets a real case |
| ERP interfaces | An interface plan, then flows built and tested: suppliers, orders, invoices, payment status | Your ERP team, with time in its own plan for the same flows |
| Data | Templates and loads for suppliers, users, approvers, contracts and catalogues | Clean source data, and a decision on which system owns each type of data |
| Tests and acceptance | Test plan, test cases, defect fixing | Key users who run the tests and sign them off |
| Change and training | Training material, sessions, user guides | Managers who explain to their teams why the change matters |
| Go-live, close support, handover | Switch to production, close support in the first weeks, handover to the support team | A support team ready to take over |
The right-hand column is often the real critical path. A provider cannot configure what nobody has decided, or test an interface the ERP team has not built.
Who delivers procurement implementation services: the vendor, an integrator or certified consultants?
Three models exist, and vendors describe them themselves. Coupa offers three programmes: Direct Delivery by Coupa, Expert Services, and Co-Delivery, where Coupa and its certified partners “operate as a unified team”. On Ivalua, the people matter as much as the firm: Ivalua’s contract terms published in 2023 require Level 2 certification to configure the platform and Level 3 to build integrations.
| Who | What you get | When it fits | What to ask |
|---|---|---|---|
| The vendor’s services team | People who know the product and its standard well | A standard scope, when you want one contract with the vendor | Who will work on your project, and for how long? |
| A certified integrator | A full team: project manager, consultants, developers, testers | A large programme across many countries and modules | How many people certified on this platform, and at which level, will work on your project? |
| Certified independent consultants, or a small team | Senior people who do the work themselves | One workstream, a mid-sized scope, or senior people next to an integrator | Have they done a full cycle on this platform themselves? |
The model matters less than the names. Ask for the people who will do the work, and check their certification on your platform.
Whoever you choose, the decisions stay with you. The provider configures; your procurement, finance and IT teams decide the approval levels, who owns which data and which exceptions to allow. For Ivalua, Ivalua implementation partner compares integrators and independents in detail.
How long does a procurement implementation take?
None of the vendor pages I read gives a typical duration, and neutral figures are rare. Public cases give an idea:
- Southern Water (UK): the implementation partner contract runs from 4 December 2025 to 30 November 2026, about 12 months, for procure-to-pay, source-to-contract and a supplier portal.
- Kansas State University (US): about 12 months on a mid-market platform, Unimarket, from preparation in March 2026 to a go-live for the whole university planned for February 2027, with a pilot go-live first.
- Scandinavian Tobacco Group: a first scope of supplier risk and performance, sourcing and contracts went live on Ivalua after a five-month project in 2021, according to Ivalua.
- CKS Consulting, a French Ivalua integrator, gives 8 to 10 months for a procurement system project.
Read these as single cases, not as a market average. A first scope limited to sourcing and contracts is shorter than a full source-to-pay suite connected to several ERPs. Ivalua figures taken from public contracts are in Ivalua implementation cost and timeline.
What if your ERP is changing at the same time?
Then the order of the two projects matters. The Hackett Group, a benchmarking and advisory firm, published a simple rule in January 2025, based on when the ERP project starts.
| The ERP project starts in | Hackett’s advice |
|---|---|
| Less than 12 months | Run the source-to-pay and ERP projects in parallel |
| 12 to 24 months | Implement source-to-pay first |
| More than 24 months | Move ahead with source-to-pay now |
If the ERP changes after the source-to-pay go-live, every interface must be specified and tested again. Agree the order with the ERP programme early.
For the flows themselves on Ivalua (orders, invoices, payment status, supplier records), see Ivalua ERP integration.
What makes a procurement implementation run late or over budget?
Three causes come back in the sources I read: scope that grows, data and interfaces, and adoption.
- Scope that grows. Ivalua ran its own survey of 31 integrators and does not publish the method. In it, scope expansion was the cause of budget overruns cited most often, by 65.2% of respondents.
- Data and ERP interfaces. In the same survey, data migration and integration were cited by 41.3% as an implementation challenge. A supplier that exists three times in the ERP will exist three times in the new platform, unless someone cleans the data first.
- Adoption. Stakeholder alignment and change management was the challenge cited most in Ivalua’s survey, at 58.7%. Gartner’s peer lessons on source-to-pay suite projects, as summarised by the vendor Raindrop, say the same: success depends on adoption, and preparation of data, processes and people matters more than the platform.
The same Gartner summary and Ivalua both advise starting with a narrow scope and extending later. Ivalua suggests an early win, such as sourcing and contracts, first. When the go-live date has already moved and the steering committee no longer trusts the plan, a project rescue starts with a two-week diagnosis.
How do I deliver procurement implementation services on Ivalua?
I am a certified Ivalua consultant (L1, L2 and L3), and my implementation services are on Ivalua only. I have worked on three full-cycle Ivalua implementations at BNP Paribas. On v156, we built and deployed the group’s source-to-pay platform. v164 was a complete redesign, built from scratch. Both were delivered on budget and on schedule. I led a mixed team of 15 on v156 and v164. v182, also built from scratch, is delivered and still evolving; its go-live was on schedule.
On these projects I did the work myself: design, configuration, supplier and ERP interfaces, data flows between systems, advanced SQL for reports and controls, and change management when entities moved to the platform, in France and abroad. On v182 I also ran data migration workstreams, from quality checks to sign-off.
| Your situation | Service | Duration | Price |
|---|---|---|---|
| You need several certified Ivalua people to deliver a scope | An Ivalua team I lead, from about ten certified techno-functional consultants in my network | Custom | Day rate per consultant, on request |
| Your integrator or internal team needs a senior lead | Senior mission: techno-functional lead or programme manager inside your team | Custom | Day rate, on request |
| The project is late and nobody trusts the plan | Project rescue: a fixed-price diagnosis, then I lead the project | 2-week diagnosis, then custom | From €9,500 for the diagnosis |
A team when one person is not enough, a senior lead when your team needs one, a rescue when the plan has failed.
A team I lead fits a few senior profiles, not a programme that needs dozens of people at once; for that, a large integrator is the better choice. For the steps of an Ivalua project, read How does an Ivalua implementation work?. To discuss your scope, book a call or write to me.
Frequently asked questions
Short answers to the questions people ask, each one sourced above.
What is included in procurement implementation services?
Usually eight workstreams: scope and plan, process design, configuration, ERP interfaces, data loads, tests and acceptance, training and change, then go-live with close support and handover to the support team. The provider does the work in the tool. Your team takes the decisions and runs the acceptance tests.
Is the implementation included in the software licence?
Usually not. The licence is the right to use the software. The implementation is days of work, bought from the vendor, an integrator or consultants. Some public tenders buy them in separate lots: Southern Water gave the software to Coupa and the implementation to a separate partner, Parade Consulting, for about 12 months.
How long do procurement implementation services last?
No vendor publishes a typical duration. Public cases give an idea: about 12 months for Southern Water’s implementation partner contract and for Kansas State University’s planned rollout, and five months for a first sourcing and contracts scope at Scandinavian Tobacco Group. Modules, countries, ERP interfaces and data quality decide the rest.
Should we hire an integrator or independent consultants?
It depends on size. An integrator fits a large programme that needs many people at once, across countries and modules. Certified independent consultants fit one workstream, a mid-sized scope, or senior people next to your integrator. In both cases, ask who will do the work and check their certification on your platform.
Do you implement platforms other than Ivalua?
No. My certifications (L1 to L3) and my three full-cycle implementations are on Ivalua. If you run Coupa, SAP Ariba or JAGGAER, look for people certified on that platform. If you are still choosing a platform, a neutral adviser is a better fit than an implementer like me.
Project already started? Check where it stands.
The health check scores your platform and your programme in three weeks.
Seb Troz
Certified Ivalua consultant (L1–L3). Three full-cycle implementations at BNP Paribas (v156, v164, v182), programme manager at Vallourec. Led a team of 13 on Rapsody at Société Générale. Engineer, ENSIMAG. About Seb