What is source-to-pay consulting, and when do you need it?

What is source-to-pay consulting?

Source-to-pay consulting is outside help with the software that runs procurement from start to end: choosing suppliers, signing contracts, ordering and paying invoices. The consultant helps you choose the platform, set it up for your processes, connect it to your ERP, move your data, go live and keep it working through upgrades.

Gartner defines the source-to-pay suite market as “an integrated set of solutions to source, contract, request, procure, receive and pay for goods and services across an enterprise”. This is from its Magic Quadrant for Source-to-Pay Suites of January 2026, read in a copy shared by Zip, one of the vendors in the report. These suites are modular: you switch on the parts you need. Gartner also says they work with any ERP and must connect to it. So every S2P project has to connect the suite to the ERP that keeps the accounts.

For the processes themselves, eProcurement Toolkit explains procure-to-pay, strategic sourcing and procurement software from the basics, with no vendor angle. This page is about the consulting work around the software.

When do you need source-to-pay consulting?

Most organisations need S2P consulting at four moments. Each moment asks for a different kind of work, and sometimes a different kind of consultant.

Public buyers show the last moment clearly. Maryland signed its Ivalua contract in March 2019. In December 2023 the project was still only partly completed, so the State ordered a six-week outside assessment before a new contract to finish it. After go-live, buyers often sign a separate contract for the run. For example, EnBW’s run contract covers stabilisation, the interfaces with SAP, incidents, upgrades and hotfixes.

What does a source-to-pay consultant actually work on?

Most of the work happens where the platform meets your people and your other systems. On an Ivalua project, these are the pieces that take the time:

• Approval workflows. A rule such as “orders above a set amount need a second approval” becomes a workflow step. An approval rule built for one entity only still has to be retested at every upgrade.
• Supplier data. Suppliers are cleaned, checked for duplicates and loaded. You also decide which system creates a new supplier: the S2P platform or the ERP.
• ERP interfaces. Ivalua often sends approved invoices to the ERP, and the ERP sends back the payment status. Each flow must be specified, built, tested and kept working through upgrades.
• Environments and tests. Gartner notes that Ivalua gives each customer three environments by default: development, test and production. Configuration moves from one to the next, and your key users test it against written criteria.
• Reports and controls. Reports, data checks and data flows, often written in SQL, so that procurement and finance can trust the figures.
• People and rollout. Training, support for users, and the switch of each entity or country to the new platform.

How these steps fit together, phase by phase, is explained in How does an Ivalua implementation work?. What they cost, from public contracts, is in Ivalua implementation cost and timeline.

How is S2P consulting different from other procurement consulting?

Some procurement consulting is savings work. For example, Dryden Group presents its procurement advisory services as a way to cut costs, with sourcing strategy, spend assessment and benchmarking. Source-to-pay consulting is the technology side: the platform that runs the processes, whatever the savings target. It is also called procurement technology consulting. The consultant configures the tool and connects it to your ERP, not only the target process on paper.

The procurement consulting page compares the two sides and the services I offer.

How do you choose a source-to-pay consultant?

Ask questions about the work, not about the brand. These five questions help you check that the person has done this work before:

1. Has this person done a full cycle on your platform? Design, build, tests and go-live, not only one phase.
2. Are they certified for the work they will do? On Ivalua, the 2023 terms require Level 2 to configure and Level 3 for integrations.
3. Will the person you interview do the work? Ask for the names and roles in the proposal.
4. Can they write the interface specification and check the data? If ERP flows are tested end to end only at the end, every defect becomes a delay. In Forrester’s study commissioned by Ivalua, the model company also had 8 internal full-time staff during implementation, so ask what the consultant expects from your team.
5. Are they neutral, or do they implement one platform? Both are fine, but for different moments. An implementer is not the right adviser for a neutral selection.

Public cases also show what helps a project go fast. HDF Energy went live on Ivalua source-to-contract in three months. The integrator named the conditions: the standard was adopted, there was no ERP interface at the start, and the client team was available for design and tests.

What source-to-pay consulting do I offer?

I work on Ivalua only. I am certified Ivalua L1–L3 and have worked on three full-cycle implementations at BNP Paribas (v156, v164 and v182), on design, configuration, integrations and custom SQL. I do not offer neutral software selection.

• A live platform that slows down at each upgrade: the Ivalua health check, from €12,500 over 3 weeks, fixed price.
• A project that has lost its date: project rescue, starting with a 2-week diagnosis from €9,500.
• An upgrade that keeps being postponed: version migration, starting with a 1 to 2-week assessment from €7,500.
• A role to fill or more hands: a senior mission or an Ivalua team led by me, at a day rate.

To agree the scope, book a call or write to me.