Skip to content
VALUEWRIGHT CONSULTING — home

ERP & SAP

Why ERP implementations need business-led procurement leadership

System integrators configure software. Someone still has to decide how the business will buy, approve, receive and pay. Why that role matters, and what it involves.

By Tom Dawson3 min read · 738 words

ERP implementations are often described as technology projects. In practice, they are business change projects that happen to involve technology. Nowhere is this clearer than in procurement and procure-to-pay, where the system has to reflect how an organisation buys, approves, receives and pays — and where small design decisions have large consequences for day-to-day work.

This article explains why procurement workstreams benefit from business-led leadership, and what that role involves alongside the IT team and system integrator.

What system integrators do — and what they need from you

A system integrator or ERP partner brings product knowledge, configuration expertise and implementation methodology. Their role is to build and deliver a working system. To do that well, they need clear answers to business questions:

  • What approval hierarchy should apply to purchase requisitions, and at what thresholds?
  • How should catalogue, contract and free-text purchasing work?
  • When does a goods receipt need to happen, and who does it on a remote site?
  • How should price and quantity tolerances work for invoice matching?
  • Which supplier and material data is migrated, cleansed or retired?

These are not technical questions. They are business decisions, and they need someone with procurement expertise and the authority to make or coordinate them. When nobody fills that role, decisions default to the integrator's standard design or are made inconsistently in individual workshops.

The cost of unclear business leadership

When the business side of a procurement workstream is under-resourced, common symptoms appear:

  • Requirements arrive late or change repeatedly, compressing build and testing time.
  • Processes are designed around the old system, carrying existing workarounds into the new one.
  • Data is not ready, so migration cycles uncover duplicate suppliers, inconsistent units of measure or missing contract pricing.
  • Testing focuses on whether the system works, not whether the business can operate with it.
  • Users are trained on transactions rather than on the new way of working, so adoption suffers after go-live.

None of these are failures of the software. They are gaps in business preparation, ownership and coordination.

What business-led procurement leadership involves

A business-led procurement lead sits between the organisation and the delivery team. The role typically spans four stages.

Define

Map current and future processes, document requirements and design decisions, assess data readiness, and agree governance and decision rights. The output is a clear, shared view of what the system must do for the business — and who decides when trade-offs arise.

Deliver

Coordinate milestones, risks and dependencies with the technical team. Translate business requirements into configuration requirements, support data migration and validation, and lead user acceptance testing from a business perspective. Prepare for cutover.

Adopt

Develop role-based training and practical guides, establish super-users, confirm business readiness and support go-live. Training should explain why processes have changed, not only which buttons to press.

Sustain

Provide an agreed period of hypercare: triaging issues, reviewing adoption and compliance, refining processes and controls, and handing over to business-as-usual ownership.

Working alongside IT and technical partners

Business-led does not mean business-only. The procurement lead works alongside the internal IT team, the ERP provider and any specialist configuration or development partners. Clear role definition helps:

  • The business lead owns requirements, process design, data readiness, business testing, training and adoption.
  • Technical partners own configuration, development, integrations, environments and platform support.

When those roles are explicit, decisions move faster and accountability is clearer for everyone.

A system can be configured correctly and still fail the business. The difference is usually in the decisions made before configuration began.

Questions to ask before your implementation

If an ERP or SAP implementation is planned or underway, these questions help test whether the procurement workstream is well positioned:

  • Who in the business has authority to make procurement and procure-to-pay design decisions?
  • Are future-state processes documented and agreed, or will they be designed in configuration workshops?
  • Has supplier, material and pricing data been assessed for quality and completeness?
  • Will user acceptance testing be led by people who understand how procurement actually operates?
  • What support will be in place in the weeks after go-live, and who decides when hypercare ends?

If several of these are unclear, the procurement workstream is likely to benefit from dedicated business leadership.


Valuewright provides business-led procurement and procure-to-pay implementation leadership, working alongside internal IT teams, ERP providers and technical partners. Learn more about ERP & SAP implementation.

Let’s talk about what’s possible

Let’s build astronger business.

Tell us where you are today and what needs to change. We’ll help define the opportunity, the practical next steps and an engagement that fits.