How to give your P2P transformation the best chance of success

Every organisation embarking on a Procure-to-Pay (P2P) transformation shares the same vision: better supplier outcomes, stronger compliance, faster processing, lower operating costs, improved working capital and greater visibility across the enterprise. When these outcomes are achieved, Procurement and Finance become genuine strategic partners rather than transactional functions.

Over the past 25 years I have had the privilege of leading major procurement, supply chain and business transformation programs across complex organisations. I’ve seen transformations that exceeded expectations and others that delivered the technology successfully but never realised the value promised in the business case.

The lesson has been consistent: implementing technology is only one part of the challenge. The harder task is embedding new ways of working, sustaining compliance and protecting the commercial benefits long after go-live. This paper shares the practical lessons I believe give organisations the best chance of realising the full value of their Procure-to-Pay transformation.

I have spent much of my career leading, supporting, and advising on large-scale procurement, supply chain, finance, and corporate services transformation programmes across complex enterprise environments.

These programmes begin with strong intentions, compelling business cases, clear technology roadmaps and well designed future states.

Yet in practice, the value is often harder to realise, especially in Procure-to-Pay (P2P) and Accounts Payable (AP).

P2P sits at the intersection of procurement, finance, operations, suppliers, approvals, compliance, tax, risk, working capital, and enterprise systems. It looks like a process. In reality, it is an operating model that is strategic and critical to the efficient and effective running of the business. Get it wrong and you can find yourself in a world of pain commercially, financially, regulatory, and legally.

The biggest risk to a P2P Transformation is when organisations treat it as a pure technology implementation, or it morphs into a pure technology implementation, losing the focus on change management, organisational design, business processes and the realisation of benefits.

Future‑state designs look clean—logical workflows, defined supplier journeys, embedded controls. Then they meet reality. Business units operate differently, supplier data is inconsistent, approval rules vary, legacy systems persist, and exceptions become normal. Technology may work as designed, but the organisation rarely behaves as assumed. The gap between design and reality is where value erodes.

Most P2P transformation business cases rely heavily on the promise of better upstream sourcing outcomes through strategic sourcing.

There are three key phases relating to benefits:

Identify: Through data analytics, supplier dynamics and market trends, opportunities for benefits are identified.

Capture: By focusing on long-term value, strategic sourcing captures the benefits through negotiations, supplier relationships, contracts and effective risk management.

Realise: The benefits captured are only realised when buyers utilise the contracts, catalogues, relationships and manage the risks identified at the capture phase. It is only then that the CFO sees the impact of the transformation benefits.

The logic is familiar. If more spend is visible, opportunities can be identified. If more spend is sourced, better commercial outcomes will be captured. If more buying is channelled through preferred suppliers and contracts, the organisation will realise the benefits.

The realise phase is where most captured benefits are eroded. The key to reducing this erosion is by looking beyond sourcing activity and considering the broader operational, financial, compliance, supplier, and working capital outcomes that sit across the full P2P lifecycle. The reduction in benefits erosion is as important to a successful transformation programme as the capture of the benefits itself.

The relationship between identifying opportunities, capturing negotiated value and ultimately realising those benefits shows where value typically begins to erode — when compliance, contract utilisation and P2P discipline weaken after sourcing has been completed.

Technology enables the realisation of benefits. It does not guarantee it. Reduced manual effort. Faster invoice processing. Improved compliance. Better spend visibility. Better supplier experience. Lower cost to serve. Better working capital outcomes. Fewer errors. Less leakage. Stronger controls.

These are all valid outcomes.

The problem is that they are often assumed to flow naturally from implementation.

In reality, benefits are only realised when the organisation changes the way work is actually performed.

Manual effort does not reduce if exceptions remain high. Cycle times do not improve if approvals are still delayed. Compliance does not improve if buying channels are bypassed. Supplier experience does not improve if suppliers are forced into processes that do not work for them. Working capital does not improve if payment decisions are disconnected from cash flow visibility and supplier terms.

The Benefits Capture phase is usually highly successful, but the realisation phase is more challenging. Why is this? There are multiple reasons for this.

Programmes are too system‑led. Implementation becomes about configuration and go‑live rather than how buying behaviour, supplier interaction, exception prevention, data quality, and benefit measurement will work in practice.

Change adoption is underestimated. P2P touches a wide user community. It is not limited to procurement and AP. It affects operational teams, approvers, project managers, contract owners, suppliers, finance business partners, shared services teams, risk teams, and technology teams.

A centrally efficient process may feel slow or unclear to daily users, driving workarounds—one of the biggest sources of leakage, rework, poor data, and control gaps.

Supplier reality is overlooked. If suppliers struggle to onboard, submit invoices, resolve disputes, or understand payment status, internal cost increases and benefits collapse.

Data quality is not maintained. Cleansing for go‑live is common; sustaining data discipline is not. As data deteriorates, exceptions rise, automation stalls, and trust in reporting weakens.

Controls are fragmented. Organisations often have the right controls, but not connected across systems and teams. Fragmentation pushes risk into manual checks, slowing processes and weakening accountability.

Some organisations genuinely need major transformation—new platforms, global standardisation, or operating‑model redesign. But these programmes carry high execution risk, require significant investment, and take time. CFOs, CPOs, CIOs, and boards increasingly need measurable value within current planning cycles, not multi‑year horizons.

This shifts the strategic question from: “What is the perfect future‑state platform?” to “How do we improve outcomes now, using what we already have?”

This is where the conversation needs to move. For many organisations, the next phase of P2P improvement is not another large replacement programme. It is orchestration.

Orchestration means connecting the existing components of the enterprise environment so work flows more intelligently across them.

It means linking suppliers, invoices, purchase orders, contracts, approvals, payments, controls, exceptions, and insights into a more coordinated operating model.

It does not require every system to be replaced. It requires the organisation to make better use of what is already in place, while adding intelligence, workflow, visibility, and control across the gaps.

This is materially different from traditional automation.

Automation improves a task. Orchestration improves the flow of work across the enterprise.

From experience, the organisations that realise value from P2P and AP transformation tend to do several things well.

They Start With Operational Truth

They do not rely only on process maps or future-state design.

They examine how work is actually happening today. Where purchase orders are raised and whether they contain the information needed for accurate matching. Where invoices really enter the organisation. Where approvals really slow down. Where suppliers really struggle. Where master data breaks. Where exceptions are created. Where controls depend on manual intervention.

This operational truth is essential. Without it, the transformation solves the designed problem, not the real one.

They Define Value In Measurable Terms

Successful programmes are clear about what value means.

Invoice cycle time. Touchless processing rates. Exception volumes. Duplicate payments prevented. Supplier query reduction. Working capital impact. Payment term compliance. Approval cycle time. Cost to serve. Fraud and compliance risk reduction. Audit outcomes.

The measures need to be visible, owned, and reviewed after implementation. Otherwise, transformation becomes activity rather than outcome.

They Design for Exceptions, Not Just the “Happy Path”

In P2P, the “happy path” is important, but the exceptions determine the cost.

The real value is often found in preventing, routing, resolving, and learning from exceptions.

Why did the invoice fail? Was the purchase order wrong? Was the supplier master data incomplete? Was the contract missing? Was the approval unclear? Was the buying channel bypassed? Was the payment term inconsistent?

A mature operating model does not just process exceptions faster. It reduces the causes of exceptions over time.

They Treat Supplier Experience As Part of the Control Environment

Supplier experience is not just a service issue. It is a control issue, a cost issue, and a data quality issue.

When suppliers can interact easily with the organisation, submit clean information, maintain accurate details, and understand payment status, the internal process improves.

When they cannot, the cost comes back into AP, procurement, finance, and operations.

They Use Technology to Enable the Operating Model, Not Replace It

Technology should not be expected to compensate for unclear ownership, weak governance, poor data, or low adoption.

The best outcomes occur when technology reinforces a clear operating model.

That means defined accountabilities, consistent policies, connected controls, clean data ownership, practical supplier engagement, and visible performance measures.

As an Advisory Board member of SpendConsole, I have had the opportunity to work with the team on how organisations can better protect value across the Procure-to-Pay lifecycle. The observations in this article are drawn from my broader transformation experience, while SpendConsole provides a practical example of how orchestration can address many of the challenges discussed.

SpendConsole, with AI-driven capture, validation, matching, and settlement, across all suppliers and systems has been designed for this reality

It does not require organisations to abandon the technology investments they have already made. Instead, it helps orchestrate Purchase Orders, approvals, invoices, receipting, payables, controls, cashflow across the current enterprise stack.

That matters because most large organisations already have ERPs, procurement platforms, supplier records, approval workflows, finance controls, and reporting structures in place.

The problem is that these components often do not work together well enough to deliver the outcomes the business case expects.

SpendConsole helps close that gap by orchestrating the activities that occur after purchase orders are raised in an organisation’s existing ERP or procurement platform. Rather than replacing those systems, it coordinates invoice capture, validation and matching against purchase orders, approval workflows, exception management, supplier collaboration, payment readiness, compliance, fraud prevention, working capital visibility and spend insight. In doing so, it helps protect and realise the value created upstream through sourcing, rather than simply automating invoice processing.

The value is not simply in automating more tasks. The value is in creating a more connected, governed, and intelligent flow of execution across the P2P lifecycle.

The lesson from large-scale transformation is not that organisations should stop transforming.

It is that transformation needs to be more practical, more measurable, and more connected to how the enterprise actually operates.

Large programmes can still have a place. But they should not be the only path to value.

Organisations need the ability to improve current performance while longer-term technology roadmaps continue. They need to reduce manual effort now. They need to strengthen controls now. They need better visibility now. They need to unlock working capital now. They need to improve supplier experience now.

That requires a different mindset. Not transformation as a distant future state. Transformation as continuous value delivery.

P2P and AP remain among the largest untapped opportunities in enterprise transformation.

They sit close to cash, suppliers, compliance, risk, productivity, and operational performance. Small improvements at scale can create meaningful enterprise value.

But value will not be realised through technology implementation alone.

It will come from organisations that understand the operational reality, focus on measurable outcomes, design for adoption, connect fragmented workflows, and use AI to orchestrate the systems and investments already in place.

That is the next phase of P2P transformation. Not bigger programmes for their own sake. Better execution, faster value, and more intelligent orchestration across the enterprise.

Technology does not realise value—people, processes and disciplined execution do. The organisations that continuously protect the benefits they negotiate, rather than assuming they will naturally flow from implementation, will consistently outperform those that view transformation as ending at go-live.