)
Learn what procure to pay means, how the five P2P stages connect, where they break in growing companies, and how to optimise each one.
What is the procure-to-pay process?
Procure to pay, or P2P, is the connected sequence a company follows from the moment someone needs to buy something to the moment the supplier is paid and the cost is booked.
The five stages are:
Purchase request
Purchase order
Goods receipt
Invoice processing
Payment
Each stage creates a record, and each record should confirm the one before it. When those records live in one workflow, finance can see what has been requested, approved, ordered, delivered, invoiced, and paid at any point in the month.
In growing companies, the sequence rarely lives in one place. Requests arrive in Slack, purchase orders sit in spreadsheets, invoices land in personal inboxes, and payments run from the bank portal.
That fragmentation, rather than any lack of effort, is what slows the process down.
Ardent Partners' State of ePayables 2025 survey of 204 AP professionals, 31% of whom were based in EMEA, found that:
49% cited invoice and payment approvals taking too long as a top challenge.
48% cited a high percentage of invoice exceptions.
Both problems start upstream, at the request and order stages, long before an invoice reaches accounts payable.
This guide is for procurement and finance operations managers who own that sequence in a company of roughly 50 to 1,500 employees.
It explains each stage, shows where the handoffs break, and sets out how to optimise the process without importing unnecessary enterprise procurement overhead.
Key takeaways
Procure-to-pay works as a chain of five records, and a gap in any one of them resurfaces later as an invoice exception.
Most approval delays and invoice exceptions begin at the request and purchase order stages rather than in accounts payable.
Capturing the cost centre, budget, and supplier details at the request stage removes the reconstruction work finance otherwise does at month-end.
Matching the invoice to the purchase order and goods received note before payment catches pricing, quantity, and duplicate discrepancies before money leaves.
The quickest route to policy compliance is making the governed purchasing path faster than the workaround.
How does the procure-to-pay cycle work?
The procure-to-pay cycle runs through five stages, and each one hands a record to the next.
Stage | Who usually owns it | Record it creates | Where it tends to break |
|---|---|---|---|
1. Purchase request | Requesting employee, budget owner | Approved request with cost centre and budget | Requests arrive by email or Slack with no cost centre or budget attached |
2. Purchase order | Procurement | Purchase order sent to supplier | Approval routing is manual, so the PO waits for a person to notice it |
3. Goods receipt | Requester or warehouse | Goods received note or service sign-off | Nobody records receipt, so finance cannot verify the invoice |
4. Invoice processing | Accounts payable | Matched, approved invoice | Invoices need re-keying and manual matching before approval |
5. Payment and recording | Finance | Payment record and accounting entry | Payment status and GL coding live in systems procurement cannot see |
Each break in the right-hand column becomes visible one or two stages later, usually as a supplier query or a correction at month-end.
1. Identifying needs and creating purchase requests
A purchase request records:
What an employee needs
Why they need it
What it will cost
Which budget will carry the cost
The request should be created before anyone contacts a supplier.
The quality of that first record determines how much work the rest of the cycle requires. A request that already carries the cost centre, expense category, expected delivery date, and supporting quote can move straight to the right approver.
A request that arrives as a chat message forces procurement to reconstruct those details later, often when the invoice is already overdue.
Guided request forms do most of the work here. When the form asks for the fields finance needs at booking, the requester supplies them once and nobody re-enters them downstream.
Budget owners can then see the request against the budget it will affect rather than approving it in isolation.
2. Purchase order creation and approval
A purchase order, or PO, turns an approved request into a document the supplier can act on.
It records:
What you are buying
From whom
At what price
On what terms
Where it should be delivered
When it should be delivered
The contractual effect of a PO depends on the wording and circumstances, so treat it first as an operational anchor.
Its number is the reference that ties the supplier's invoice back to the original approval.
Approval routing determines how quickly the PO reaches the supplier. A workflow that routes by amount, cost centre, and category can allow a £300 software renewal to pass through one approver while a £40,000 equipment order collects two.
Once approved, the PO represents committed spend: money the company has promised but not yet paid.
Tracking committed spend separately from spend already paid tells a budget owner how much of the budget is still available.
3. Goods receipt and service verification
The goods received note, or GRN, confirms that what was ordered arrived, in what quantity, and in what condition.
For services, the requester or project owner signs off that the work was delivered as agreed.
Smaller companies skip this stage more than any other. Skipping it removes the evidence finance needs to approve payment with confidence.
Partial deliveries are where the record earns its keep.
If a supplier ships 60 of 100 units but invoices for all 100, a GRN logged against the PO shows the gap immediately. Without one, the discrepancy usually surfaces only when the supplier chases a second payment.
4. Invoice processing and matching
Invoice processing turns the supplier's invoice into an approved payable by:
Capturing the invoice
Extracting its data
Matching it to the PO and GRN
Routing it for approval
Three-way matching compares the invoice against both the purchase order and the goods received note.
Two-way matching compares the invoice against the PO alone. This is suitable for services and subscriptions where nothing physical arrives.
In both cases, the check happens before payment, which is where it needs to happen to be useful.
Matching rarely works first time everywhere. APQC's Open Standards Benchmarking, with a median across 4,438 organisations published on 27 January 2026, puts the share of invoice line items matched first time at 75%.
One line in four needs a person to review it, whether because of:
A price change
A quantity difference
A missing PO number
Another exception
Capture quality therefore matters as much as the match itself.
A shared invoice inbox and optical character recognition, or OCR, turn data entry into a review task. The team's time can then go to the 25% that needs judgement.
Within Spendesk's accounts payable module, an incoming invoice can be linked automatically to its purchase order and delivery record. The platform raises an alert where the three documents disagree.
Invoices that match an already approved PO can be configured to skip the budget-owner approval stage and route directly to Review, so the same budget decision is not taken twice. Whether this suits your control requirements depends on your configuration.
5. Payment execution and recording
Payment closes the cycle when finance pays the approved invoice on the agreed terms and books the cost to the correct general ledger code with the right VAT treatment.
Two decisions sit at this stage:
When to pay: early to capture a discount, or on terms to protect cash
How to record it: so month-end does not require a second pass over the same invoice
Recording is where the upstream work pays off.
If the request already carried the cost centre and category, the bookkeeping entry is largely prepared before the invoice is validated.
Payment status should also flow back to the same record. A procurement manager answering a supplier's question about payment status should be able to see the answer without asking finance.
What are the benefits of an optimised procure-to-pay process?
An optimised procure-to-pay process reduces the number of times a person touches each transaction. Every touch removed reduces cost, delay, and error together.
The four benefits below all trace back to that mechanism.
1. Efficiency and cost savings
The saving comes from removing re-keying and reconstruction.
In a fragmented process, the same purchase may be typed into:
A request thread
A PO spreadsheet
The invoice system
The accounting package
Someone then reconciles the four versions at month-end.
That aggregate time cost, sometimes called the spend management tax, grows with headcount and supplier count even when nothing goes wrong.
Time recovered from transactional follow-up is time procurement can spend on strategic procurement, including:
Consolidating suppliers
Renegotiating terms
Reviewing the tail of small vendors
2. Improved supplier relationships
Suppliers experience your procure-to-pay process as the time between sending an invoice and receiving payment.
The UK government's Large Businesses' Payment Practices and Performance Statistics 2025, drawn from 11,178 statutory reports and published on 14 July 2026, found that:
15% of invoices were paid late by number.
The median time to pay was 32 days.
Late payments rarely reflect a cash shortage. More often, the invoice sat in an approval queue or waited for a PO nobody could find.
When invoices match POs automatically and route to the right approver on arrival, fewer invoices go late.
Predictable payment also puts you in a stronger position when negotiating terms, because suppliers price reliability into what they charge.
3. Greater visibility and control
A connected process separates three numbers that a spreadsheet blurs:
Budget approved
Budget committed
Budget used
An approved PO commits spend before any invoice exists. A validated invoice converts committed spend into used spend.
Budget owners who can see all three at the moment of approval make better decisions than budget owners who see only last month's actuals.
The same records support reporting by:
Supplier
Category
Cost centre
Entity
Purchase order
This can happen without a separate export.
If budget owners currently approve without that context, see how Spendesk shows the financial impact behind a request before they approve it.
4. Compliance and risk management
A connected procure-to-pay process produces an audit trail as a by-product of doing the work:
Request
Approval
Purchase order
Goods received note
Invoice
Payment
Each record is timestamped and attributed to a person.
Reconstructing that trail after the fact is slower and less reliable, whether the person asking is an auditor or a colleague investigating a duplicate payment.
Fraud risk sits at the same handoffs.
UK Finance's Annual Fraud Report 2026 records £41.3 million lost to invoice and mandate fraud across 2,305 cases in 2025.
Of those losses, 68%, or £28 million, occurred on business accounts.
Many schemes rely on:
A changed bank detail
A plausible invoice with no PO behind it
A supplier record that has not been independently verified
Requiring a PO number on incoming invoices and verifying any bank-detail change through a second channel are controls you can manage inside the workflow rather than after payment.
What are the most common procure-to-pay challenges?
The three challenges below share a root cause: the process was built for a smaller company, and growth added tools and people faster than the workflow adapted.
Each has a practical fix.
1. System fragmentation
Fragmentation means the request, PO, delivery confirmation, invoice, and payment each live in a different system. A person becomes the integration between them.
The symptoms are familiar:
Approval queues nobody can monitor
Supplier records duplicated between procurement and AP
Invoices matched by searching an inbox for the original quote
Payment status unavailable to procurement
Budget information unavailable to requesters
The fix is one record that every stage writes to.
Spendesk is an all-in-one spend management platform consolidating:
Company cards
Expense management
Accounts payable
Procurement
Budgeting
For a procure-to-pay process, this means the purchase request, the PO it becomes, the invoice that arrives against it, and the payment that settles it sit in the same workflow as the cards and expense claims finance already manages.
Suppliers created for procurement sync to accounts payable, so the same vendor does not need to be set up twice.
2. Policy non-compliance
Maverick spend happens when the governed route is slower than the workaround.
If raising a request takes three days and using a personal card takes three minutes, employees will choose the card. No amount of policy wording changes that arithmetic.
The practical answer is to make the compliant path the faster path:
Set a PO threshold so low-value purchases do not need a full request.
Route routine categories to a single approver.
Give employees virtual cards with limits for small recurring spend.
Communicate why the process exists.
Hold budget owners accountable for approvals.
Our guide to procurement management covers how to set those thresholds.
If controls currently act after payment, see how Spendesk applies approval workflows and spend rules before money moves.
3. Poor spend visibility
Visibility fails when committed spend is invisible until the invoice arrives.
Efficio's 2025 report, The Illusion of Control in Indirect Spend, based on 300 senior finance and procurement leaders in Europe, found that:
Only 19% had full visibility of their organisation's indirect spend.
85% said more than a quarter of indirect spend had no financial oversight.
93% identified maverick spend as a major problem.
These figures describe one condition: leaders know money is being committed but cannot see it until it is spent.
The solution is to report on approved POs as committed spend from the day they are approved, and to hold every supplier invoice against a PO or a documented exception.
Once that is true, spend by supplier and category becomes a live view rather than a quarterly reconstruction.
What are the best practices for procure-to-pay optimisation?
The five practices below are ordered roughly by how quickly a team can act on them. The first two need no new software.
Improve supplier relationships
Give each supplier one record and one channel.
A single supplier master, shared between procurement and AP, prevents duplicated vendor entries that can cause:
Misdirected payments
Duplicate onboarding
Inconsistent supplier data
Payment delays
A dedicated invoice-forwarding address and a requirement that invoices quote the PO number give suppliers a predictable route and provide clean matching data.
Consolidating suppliers where several provide the same category reduces the number of relationships to manage and gives the remaining suppliers more volume to price against.
Paying on terms, consistently, is the cheapest relationship investment available.
Look beyond the list price
The price on the quote is one part of what a purchase costs.
The RS 2026 Indirect Procurement Report, produced with the Chartered Institute of Procurement & Supply from 448 UK and Ireland respondents, puts the average business cost of processing an order at £77.
For a £50 purchase, the process costs more than the item itself.
That arithmetic argues for:
Consolidating small orders
Moving low-value recurring spend onto controlled cards
Treating payment terms as part of the negotiated price
Treating early-payment discounts as part of the negotiated price
Considering processing costs when setting PO thresholds
Standardise processes
Write down the approval matrix and PO threshold, then build the workflow to match.
An approval matrix states who approves what by:
Amount
Category
Cost centre
A PO threshold states the value above which a purchase order is mandatory.
Both remove the case-by-case judgement that slows approvals and invites exceptions.
Segregation of duties belongs in the same document.
Ideally:
The person who sets up a supplier is not the person who approves its invoices.
The person who approves invoices is not the person who releases payment.
Bank-detail changes are independently verified.
If the team is too small to separate every duty, a documented independent review of new suppliers and bank-detail changes provides an additional check.
Automate the repetitive steps
Automate the steps that do not need judgement:
Reading invoice data
Detecting duplicates
Matching invoices to POs
Routing for approval
Preparing the accounting entry
Each is a task a person may perform identically hundreds of times a month. Each is also a point where re-keying errors enter.
In Spendesk, OCR reads each incoming invoice and pre-fills the supplier, amount, and VAT fields finance needs. Bookkeeping rules and machine-learning-based suggestions prepare the GL code for review.
Finance confirms prepared fields instead of entering each one from scratch, and duplicate detection flags a repeat invoice before payment rather than during reconciliation.
If the AP queue is your main bottleneck, see how Spendesk connects invoice capture, approval, matching, payment, and tracking.
Monitor and measure performance
Measure a small set of indicators monthly, because the process degrades quietly when nobody watches it.
Indicator | What it tells you | Reference point |
|---|---|---|
Invoice exception rate | Share of invoices needing manual intervention | 18.4% market average; 11.1% best-in-class, Ardent Partners 2025 |
Straight-through processing rate | Share of invoices processed without a human touch | 35.4% average; 51.0% best-in-class, Ardent Partners 2025 |
Invoice cycle time | Days from receipt to approval | 8.2 days average; 2.9 days best-in-class, Ardent Partners 2025 |
First-time match rate | Share of invoice lines matched to PO and GRN without correction | 75% median, APQC, January 2026 |
PO coverage | Share of invoices linked to a purchase order | Track your own trend; higher coverage reduces exceptions |
On-time payment rate | Share of invoices paid within agreed terms | Track against your agreed terms |
The Ardent Partners figures come from the State of ePayables 2025 survey cited earlier, and the APQC figure comes from its Open Standards Benchmarking.
Both samples skew North American, so treat them as directional for a UK or European team rather than as fixed targets.
The more useful comparison is your own trend:
A falling exception rate shows that upstream fixes are working.
A rising PO coverage rate shows that employees are using the governed route.
A shorter invoice cycle time shows that approval bottlenecks are improving.
A higher first-time match rate shows that purchase and receiving data is becoming more reliable.
What does the future of procure-to-pay look like?
The near-term future of procure-to-pay is machine-learning-based automation applied to better upstream data.
Generative and agentic tools remain largely at pilot stage in procurement, while blockchain has limited operational relevance for a mid-sized company in the next few years.
Artificial intelligence and machine learning
The machine learning already in production handles repetitive reading and matching, including:
OCR on invoices
Categorisation
GL code suggestions
Duplicate detection
Anomaly detection
These capabilities deliver value today because their inputs are structured documents and their outputs can be reviewed by a person.
Generative AI is a different story.
In July 2025, Gartner placed generative AI for procurement in the Trough of Disillusionment on its Hype Cycle. Gartner identified fragmented and low-quality data as one of the main obstacles to adoption.
The implication for a finance team is direct: any AI, current or future, will be only as good as the procure-to-pay records it reads.
Connected requests, POs, and invoices are the precondition. Teams that fix those records first will get the most from whatever arrives next.
Advanced analytics
Analytics in procure-to-pay is moving from month-end dashboards to live questions:
How much of this quarter's marketing budget is committed but unpaid?
Which suppliers received more than 20% of a category's spend?
Which POs have been open for more than 60 days?
Which invoices are repeatedly failing to match?
Which cost centres are creating the most exceptions?
These questions can be answered continuously when every stage writes to one record.
Conversational access is the next step.
Spendesk AI Connect uses the Model Context Protocol, or MCP, to let compatible AI assistants query Spendesk data for search, analysis, and reporting. Access is read-only and follows the permissions of the person asking.
It does not:
Approve requests
Change suppliers
Create payments
It answers questions.
If disconnected data is limiting how your team uses AI, see how AI Connect works in an existing assistant.
Blockchain integration
Blockchain in procurement remains aspirational, and the evidence from the last four years points in the opposite direction.
All four major blockchain trade-finance networks that existed in 2019 closed in their original form between 2022 and 2023.
As Ledger Insights put it after Contour shut down in November 2023:
In 2019, there were four major blockchain trade finance networks. Komgo is the only one left standing.
Current distributed-ledger activity sits in wholesale settlement pilots run by banks and central banks, not in purchase orders or invoice matching.
The audit-trail benefits often attributed to blockchain, such as an immutable and timestamped record of who approved what, can be achieved today through a connected procure-to-pay system with role-based permissions.
Transform your P2P process with Spendesk
The approval delays and invoice exceptions that AP teams name as their biggest problems are symptoms of records created in the wrong place, at the wrong time, or by the wrong process.
Fixing them means:
Capturing the cost centre at the request stage
Committing the budget at the PO stage
Matching the invoice before payment
Connecting procurement, budget owners, and finance in one system
Spendesk's procure-to-pay module connects:
Guided purchase requests
Configurable approval workflows
Purchase order creation
Supplier invoice capture
Payments
Budgets
Committed-spend visibility
Card and expense payment workflows
It is a complementary module rather than a replacement for a strategic sourcing suite. It is strongest where the priority is connecting purchasing to payment and accounting without introducing a separate procurement system.
Local accounting connections, including DATEV, Xero, and NetSuite, and country-specific finance workflows mean a European team does not need to rebuild the same process market by market.
Implementation typically takes two to six weeks, depending on scope.
If you are weighing whether a connected process would remove the exceptions your team handles today, book a demo to see the request-to-payment flow configured for your organisation, or get a free tour of the platform first.
Frequently asked questions about the procure-to-pay process
What is the difference between procure-to-pay and source-to-pay?
Procure-to-pay starts once you know what you need. It covers:
Request
Approval
Purchase order
Receipt
Invoice
Payment
Source-to-pay adds the stages before that, including:
Identifying suppliers
Running tenders or quotes
Negotiating
Contracting
Most companies with 50 to 1,500 employees need a strong procure-to-pay process first. Sourcing tools become more important once spend volume in a category justifies formal competition between suppliers.
What is the difference between procure-to-pay and accounts payable?
Accounts payable is the fourth and fifth stage of procure-to-pay:
Receiving invoices
Approving invoices
Paying suppliers
Recording the transaction
Procure-to-pay also includes the request, approval, and ordering stages that happen before an invoice exists.
An AP team that inherits invoices with no PO behind them is dealing with a procure-to-pay problem, not just an AP problem.
What happens when an order is only partially delivered or partially invoiced?
The goods received note records what arrived. The invoice is matched at line level, and finance pays for the quantity received while the purchase order remains open for the balance.
When the remaining goods arrive, a second receipt and invoice close the order.
Without a receipt record, the usual result is either:
Paying for goods that have not arrived
Delaying payment for goods that have arrived
Who should own the procure-to-pay process, procurement or finance?
Ownership is usually shared by stage:
Procurement owns the request and purchase order stages.
Requesters or operations own receipt.
Finance owns invoice approval, payment, and recording.
What matters more than the organisation chart is that all three teams work from the same record. A question about any purchase should have one answer, regardless of who asks.
Do you need a purchase order for every purchase?
Most companies set a value threshold below which a controlled company card or a simple approved request is sufficient, and above which a purchase order is mandatory.
The threshold should reflect the processing cost of an order against the value of the control it provides. A PO on a £30 subscription may cost more to raise than the control it protects.
Curious how Spendesk works?
Try an interactive demo to see spend control and approvals end-to-end.
Get a free tour)
Chris Dunne
Chris Dunne is our Senior Content Marketing Manager. Based in Derry, he brings over 15 years of marketing experience to our content strategy. Outside of work, Chris loves spending time with his two young children, playing football, and exploring Ireland.
)
)
)
)
)