9 min read
Procure-to-pay, usually shortened to P2P, is the end-to-end process that runs from the moment someone in the business buys something through to the moment the supplier gets paid. It covers requisition, approval, purchase order, receipt, invoice matching, and payment, and it is where procurement policy either becomes real or quietly gets ignored.
I have watched a lot of teams treat P2P as the unglamorous end of procurement, the plumbing you install once and stop thinking about. That framing is why so many implementations disappoint. Almost everyone in an organization interacts with P2P at some point, most of them with no interest in procurement whatsoever, and it is the part of the relationship a supplier experiences most often.
This article covers the process step by step, how it differs from source-to-pay, what a real rollout looks like inside a large company, and where these programs usually come unstuck.
Key takeaways:
- P2P spans requisition to payment. Source-to-pay is broader, adding the sourcing and contracting work that happens before anyone raises a requisition.
- The "pay" half matters as much as the "procure" half. Programs run by procurement without accounts payable at the table tend to stall after go-live.
- Adoption is the hard part, not configuration. A voluntary launch rarely produces compliance on its own.
- Buying a tool your culture cannot absorb is a more common failure than buying one that lacks features.
What is procure-to-pay?
Procure-to-pay is the sequence of steps an organization follows to request, approve, order, receive, and pay for goods and services. It connects procurement and accounts payable into one workflow, so that what was agreed with a supplier is what gets ordered, what gets received, and what ultimately gets paid.
The term is used interchangeably with purchase-to-pay, and the abbreviation P2P appears in both forms. In practice they describe the same cycle. Some organizations draw the starting line slightly differently, which is where most of the definitional confusion comes from.
The procure-to-pay process, step by step
Every organization words these stages differently, but the underlying sequence is consistent.
- Need identification and intake. Someone in the business needs something. How that request reaches procurement, and how well it is captured, shapes everything downstream. This front door has become a discipline of its own, which we cover separately in why procurement needs intake management software.
- Requisition. The request becomes a formal purchase requisition, with the category, quantity, budget code, and any supporting detail attached.
- Approval. The requisition routes for approval, typically against budget and policy, sometimes through several layers.
- Purchase order. Once approved, a purchase order goes to the supplier. The PO is the commercial commitment, and it is also the control point that makes everything after it verifiable.
- Receipt. The organization records that the goods arrived or the service was delivered.
- Invoice receipt and matching. The supplier's invoice arrives and is matched against the PO and the receipt. Two-way matching compares invoice to PO; three-way matching adds the receipt.
- Approval and payment. Matched invoices are approved and paid on agreed terms. Exceptions get investigated, and in many organizations that exception handling absorbs a disproportionate share of the manual effort in the entire cycle.
- Record keeping and analysis. Every transaction leaves data behind. Done well, this is what makes spend visible enough to source against next time.
Steps one through four belong mostly to procurement. Steps six and seven belong mostly to finance. That handoff in the middle is a recurring point of failure, and it is a theme the practitioners quoted below return to from several directions.
How do you differentiate procure-to-pay from source-to-pay?
The two terms describe overlapping scopes, and the difference is simply where you start counting.
Source-to-pay (S2P) is the whole arc: understanding the category, running the sourcing event, negotiating, contracting, and then the transactional buying and payment that follows. Procure-to-pay is the downstream portion, beginning once a contract or supplier is already in place.
Put plainly, strategic sourcing decides who you buy from and on what terms. P2P is how the organization actually buys, day after day, and whether those negotiated terms survive contact with reality. A brilliant contract that nobody buys against delivers nothing.
Why P2P is harder than many other procurement technology
Teams who have deployed a sourcing tool or a contract repository often assume P2P will be a similar exercise. It usually isn't, for two reasons.
The scope is the entire company
Jennifer Ulrich, former Senior Director of Advisory at Corcentric, drew the contrast precisely on an AOP Live session:
"When we're implementing a contracting tool or a sourcing tool, your focal point is going to be a lot smaller. P2P is everyone in the organization. You buy something, you're impacted."
Jennifer Ulrich, former Senior Director of Advisory, Corcentric (Art of Procurement, Avoiding an EPIC P2P Implementation Fail)
A sourcing tool might have dozens of users, all of whom are paid to care about procurement. A P2P system can have thousands who are not, and who will judge it against the experience of buying something online in their personal life. That is a far harder audience.
Procurement often forgets the second half of the name
Her colleague Joe Payne, Senior Vice President of Source-to-Pay at Corcentric at the time, named the failure he sees most often, and it starts before any software is chosen:
"The biggest failure is one that I actually see almost every time we start a P2P implementation or a transformation of a procurement or accounts payable function. That's not really realizing what the letters stand for. It's procure-to-pay."
Joe Payne, former Senior Vice President of Source-to-Pay, Corcentric (Art of Procurement, Avoiding an EPIC P2P Implementation Fail)
Procurement designs the buying experience, finance owns the invoice and the payment, and the two halves frequently get specified by different people with different goals. Payne is also refreshingly blunt about the scale of the undertaking, describing a P2P transformation as one step down from an ERP deployment. That is a useful expectation to set with a steering committee before the business case gets written, not after.
What a real rollout looks like: Case Clorox
Abstract advice about P2P is easy to find. A named company willing to describe what actually happened is not, which is why Kathy Thrasher's account of the Clorox indirect P2P program is worth walking through. She spoke to us in 2021, partway through the rollout, which is exactly why the account is useful: nobody was presenting a finished success story.
Kathy, a Senior Manager at The Clorox Company, started from a position most procurement leaders would find alarming:
"Believe it or not, Clorox had no purchasing system at all for indirect spend, and the indirect spend accounts for half of our overall spend as a company. And we had been trying to do it for many, many years, taking a run at it, but it takes a big team, a lot of dedication, a lot of money. We didn't even know until the invoices came in what was committed."
Kathy Thrasher, Senior Manager, The Clorox Company (Art of Procurement, Episode 420, recorded 2021)
Clorox selected an implementation partner in December 2019 and kicked off as the pandemic arrived, running the entire program from design to go-live without a single in-person meeting. They deliberately took the software largely as it came rather than customizing it, and Thrasher is candid that having no legacy system made that possible: there was no existing process to protect.
They went live on 19 January 2021 with a voluntary approach, on the reasonable theory that bringing people along beats mandating. It did not work well enough. Non-PO invoices kept arriving, and by 1 May 2021 they had made purchase orders mandatory. Even then, holdouts persisted. The team ran the numbers, identified the worst offenders, required them to attend training, and told their managers. Kathy’s summary of that period is the most honest thing I have heard a practitioner say about P2P adoption:
"There's days I just shook my head. How can people not understand that they have to create a purchase order? But we're still working through that, with a smile on our face, and get on the phone and talk them through it again."
Kathy Thrasher, Senior Manager, The Clorox Company, speaking in 2021 (Art of Procurement, Episode 420)
One detail from that program deserves separate attention. Clorox set up a help desk mailbox expecting procurement questions, and found that close to 90 percent of what arrived was invoice related, which forced finance colleagues onto the desk alongside the procurement operations team. It is the clearest possible illustration of Payne's point about the second P in “procure-to-pay.”
Where P2P programs stall
Over the years, the topic of P2P failure has come up in many of my conversations with procurement executives and consultants.
Treating a program like a project
Tom Pellescki, VP of Professional Services at Corcentric, described the pattern that separates the implementations that deliver from the ones that technically went live:
"What we see a lot is people implement P2P and they get five catalogs put up and then they're done. They never achieve the full ROI of the program. The main driver there is they treat the project like it's a project when it's really a program."
Tom Pellescki, VP of Professional Services, Corcentric (Art of Procurement, Avoiding an EPIC P2P Implementation Fail)
Go-live is the start of the work, not the end of it. Catalog coverage, supplier enablement, and compliance all need an owner twelve months later, and a project team that has been disbanded cannot provide one.
Buying technology your organization cannot absorb
Mike Caldron, Senior Group Manager at WNS Denali, who supported the Clorox program, put the selection question in terms that cut through most feature comparisons:
"There are lots of bleeding edge tools that are out there that you can go with. But is the culture of your organization bleeding edge? And if not, then that's just not really a great recipe for success."
Mike Caldron, Senior Group Manager, WNS Denali, speaking in 2021 (Art of Procurement, Episode 420)
Clorox lived this out. Their IT function preferred a different tool, and the disagreement went far enough up that Thrasher describes it as arm wrestling at the top. Procurement's argument was that the tool had to be one their people would actually adopt, and that argument won. Notably, the executive steering committee refused to settle it and sent both teams away to resolve it themselves.
Designing P2P around the people who use it
The teams that get adoption tend to start from a service mindset rather than a control mindset. Magnus Bergfors, then Global Business Director at Basware and now Vice President of Procurement Research at Ardent Partners, made a point about approval workflows that most procurement leaders privately recognize:
"There are managers out there that sit and approve hundreds of requisitions and invoices. And I will bet you money that they're not taking a detailed look at any of these. They're sort of auto-approving them."
Magnus Bergfors, Then Global Business Director, Basware (Art of Procurement, Episode 399).
An approval step that nobody genuinely performs is not a control. It is a delay wearing the costume of a control. Magnus’s argument is that if a requisition can be checked automatically against policy and budget, it should be, so that human attention goes to the exceptions that actually warrant it.
The same logic applies to the buying experience itself. If the compliant path is slower than the workaround, people will find the workaround, and no amount of policy communication will fix a process that is simply worse than its alternative. The useful design question is not how to enforce the policy, but how to make following it easier than not following it.
Suppliers deserve the same consideration and rarely get it. Both the Corcentric team and Sushant Adhikari of WNS Denali, speaking on separate episodes, independently named suppliers as the stakeholder group most often forgotten during P2P design and selection. That matters, because suppliers are the ones who have to submit the invoice correctly for any of the processes to work, and they are doing it across a great many customer portals that all behave differently.
How to tell whether your P2P process is working
Be careful with benchmark numbers here. Much of the ROI data circulating on P2P originates with organizations that sell P2P software or services, and it tends to arrive without a stated denominator, timeframe, or method. Treat any headline multiple you cannot reconstruct with suspicion.
More useful is to track a small number of things you can actually observe:
- PO coverage, meaning the share of invoices arriving against a purchase order. This is the clearest single measure of whether the process is being followed.
- Touchless invoice rate, the proportion of invoices that match and pay without human intervention.
- Exception volume and reasons, which tells you where the process is breaking rather than just that it is.
- Where the questions come from. Clorox used the changing mix of their help desk traffic as a progress signal. As PO-backed invoices rose, invoice queries fell.
Cycle time and cost per invoice are worth tracking too, but only against your own baseline. Cross-company comparisons in this space are rarely like for like.
The bottom line on procure-to-pay
P2P is often where procurement's strategy either lands or evaporates. The contracts, the negotiated rates, and the preferred suppliers all depend on a transactional process that thousands of people who do not work in procurement have to use without resenting it.
That makes P2P less a technology problem than an adoption problem with a technology component. The organizations that do it well pick tools their culture can absorb, put accounts payable in the room from day one, resource the program well past go-live, and accept that they will spend a long time getting on the phone and walking people through it.
If you want to hear the full Clorox story in their own words, it is Episode 420 of the Art of Procurement podcast, recorded in 2021 while the rollout was still underway.
