The procure-to-pay process, and the six steps that keep spend under control.

The short answer. Six steps, one thread of accountability.

The procure-to-pay process, often shortened to P2P, is the full chain of steps a business runs through every time it buys something: requisition, approval, purchase order, receipt, invoice matching and payment. The point of documenting it as a single process, rather than treating "buying things" and "paying invoices" as two separate jobs handled by two separate teams, is traceability. Every payment a business makes should be able to point back to a specific approved requisition, and every requisition should be able to point forward to the invoice it eventually produced.

Founder-led businesses often run a version of this informally: someone emails a supplier, someone else eventually approves the invoice for payment, and the two events are only loosely connected in anyone's head. That works while spend is small and everyone involved is in the same room. It stops working the moment two people can independently commit the business to a supplier, because nobody can then say with confidence what has actually been agreed, ordered or owed at any given point.

The process also sits at the point where operations and finance most often disagree about what actually happened. Operations wants supplies to arrive quickly and does not want a purchasing process getting in the way of the work. Finance wants every payment traceable to an authorised commitment and the cash flow visibility that comes with knowing what is owed and when. A well-run procure-to-pay process is not a compromise between those two positions; it gives operations a fast, predictable route to get what they need approved, while giving finance the paper trail it needs without either side having to chase the other after the fact.

How it works in practice. The six-step process.

Each step exists to answer a specific question, and skipping one usually means that question goes unanswered until it becomes expensive.

1. Requisition. The person who needs something raises a request stating what it is, roughly what it will cost and why it is needed, before any conversation with a supplier begins.
2. Approval. The requisition is approved against a defined authority level, typically the requester's manager for smaller amounts and a finance or founder sign-off above a set threshold.
3. Purchase order. An approved requisition becomes a purchase order sent to the supplier, fixing price, quantity and terms in writing before any commitment is made or goods are shipped.
4. Receipt. The goods or service are received and formally logged against the purchase order, confirming what actually arrived, and in what condition or quantity, rather than assuming the order was fulfilled exactly as placed.
5. Invoice matching. The supplier's invoice is checked against both the purchase order and the receipt record, a three-way match, before it is approved. If all three agree, the invoice can be approved automatically; if they do not, it is flagged for review rather than paid on trust.
6. Payment. Payment is released on the agreed terms, and the accounting and budget records update to reflect it, closing the loop from the original requisition through to cash actually leaving the business.

The three-way match in step five is the control that does most of the work. Without it, a business is effectively paying whatever a supplier invoices, trusting that the amount, quantity and price match what was agreed and delivered. With it, discrepancies get caught before money moves rather than discovered afterwards during a reconciliation nobody enjoys doing.

The gap between running this manually and running it with automated matching is well documented and larger than most founder-led teams expect. Ardent Partners' Accounts Payable Metrics that Matter in 2025 report, drawn from 212 AP professionals, puts real numbers against the difference.

That gap is not a rounding error. A business processing a few hundred invoices a month is looking at a meaningful, recurring cost difference, quite apart from the cash flow benefit of paying on time consistently rather than fielding a late-payment call from a supplier once a quarter.

What good looks like. A worked example.

A 60-person hospitality group we worked with had been running procurement almost entirely by email: department heads ordered supplies directly from vendors, invoices arrived at finance with no consistent way to confirm what had actually been agreed or received, and duplicate or unauthorised orders were only caught when finance happened to notice two invoices from the same supplier in the same week. There was no single record connecting a request to an order to a payment.

The fix followed the six-step structure exactly, built inside the CRM and finance tools the business already used rather than a new standalone system. Every requisition over a modest threshold now routes through a single approval step before any supplier is contacted. Purchase orders are generated automatically from approved requisitions, with the price and quantity locked in before the goods are ordered. Receiving staff log what actually arrives against the purchase order number, and invoices are matched automatically against both records before finance ever sees them, with only genuine mismatches routed for manual review.

Getting department heads to adopt the new sequence took more work than building it. The rollout paired every requisition template with a one-page guide showing exactly which threshold required which approval, and finance ran the first month's requisitions alongside department heads rather than simply handing over a new form and expecting immediate compliance. That hands-on start mattered more than any feature of the system itself: a process that looks correct on paper but that nobody actually follows delivers none of the control it was designed to provide.

Within the first full quarter of running the new process, the business identified and stopped two recurring supplier arrangements nobody had formally approved, and cut the average time to clear an invoice from over two weeks to under five days, broadly in line with the gap Ardent Partners' 2025 accounts payable research found between best-in-class teams and the rest. The bigger change was cultural rather than technical: department heads got used to raising a requisition before contacting a supplier, not after, because the approval step now sat in front of the order rather than behind the invoice.

Budget coding was the other quiet win. Every requisition now carries a cost centre and budget line from the moment it is raised, rather than finance reconstructing which department a cost belonged to after the invoice had already arrived. That single change gave department heads a running view of spend against budget for the first time, instead of finding out they were over budget when the quarterly accounts closed.

For businesses mapping this out for the first time, our process mapping work usually starts by documenting the process exactly as it happens today, gaps and workarounds included, before designing the six-step version that replaces it.

Pitfalls to avoid. Where control breaks down.

The most common failure is allowing orders to go out before a purchase order exists, sometimes called maverick spend. Once a supplier has already delivered, the approval step becomes a formality rather than a genuine control, because rejecting an invoice for goods already received and in use is rarely a realistic option. The control only works if it sits before the commitment, not after it.

A second pitfall is skipping the receipt step and matching invoices only against the purchase order. Without a receipt record, a business is confirming that an order was placed correctly, not that what was billed actually arrived. This is precisely the gap that lets incorrect quantities, short deliveries and, occasionally, invoices for goods never received pass through unnoticed.

A third pitfall is routing approvals and matching entirely by email and spreadsheet once transaction volume grows past a handful of orders a week. Manual routing is exactly where Ardent Partners' research locates the gap between best-in-class and average performers: top teams achieve a 90%+ first-time match rate with a 9% exception rate, while the rest run exception rates closer to 22%, meaning roughly one in five invoices needs manual handling under a process that was never built to catch discrepancies systematically.

A fourth pitfall is setting approval thresholds once and never revisiting them as the business grows. A £500 sign-off limit that made sense at ten employees becomes an administrative bottleneck at fifty, pushing routine, low-risk purchases through the same approval chain as genuinely significant spend, and encouraging staff to quietly split orders to stay under the limit rather than wait for sign-off. Reviewing thresholds annually, alongside the rest of the process, keeps the control proportionate to the risk it is actually managing rather than to the headcount the business had when the policy was written.

For the diagramming conventions behind documenting a process like this clearly, see our guide to process map symbols, and for the broader case on when to automate a workflow rather than keep running it manually, our piece on business process automation covers the decision in full.