The short answer
Procure-to-pay (P2P) is the cycle that runs from requesting a purchase to paying the supplier: requisition, approval, purchase order, goods receipt, invoice capture, three-way match, exception handling, payment run and supplier reconciliation. Most of it is rule-based and transfers well to an outsourced team or automation. The steps that genuinely need judgment are approving spend, resolving disputed exceptions, and releasing payment.
Key takeaways
- P2P covers requisition through payment and supplier statement reconciliation, not just invoice entry.
- The three-way match — purchase order, goods receipt, invoice — is the control that makes the rest of the cycle safe.
- Only three steps really need judgment: approving the spend, resolving genuine exceptions, and releasing payment.
- First-pass match rate is the single most useful health metric; a low rate means the problem is upstream, not in AP.
- Keep payment release with your own approvers. A provider can prepare a run to the last mile without holding authority.
What are the steps in the procure-to-pay cycle?
P2P is usually drawn as nine steps. The first three are procurement, the middle four are accounts payable, and the last two close the loop.
- Requisition. Someone requests a purchase, with a cost centre and a business reason.
- Approval. The request is approved against a delegation of authority.
- Purchase order. A PO is raised and sent to the supplier, creating the commitment.
- Goods or services receipt. Someone confirms what actually arrived.
- Invoice capture. The supplier invoice is received and its data extracted.
- Three-way match. Invoice, PO and receipt are compared on quantity, price and terms.
- Exception handling. Anything that does not match is investigated and resolved.
- Payment run. Approved invoices are scheduled and paid to terms.
- Supplier reconciliation. Supplier statements are reconciled and disputes cleared.
Teams that describe P2P as 'accounts payable' usually mean steps five to eight. The cycle breaks most often at steps three and four, and the damage shows up at step six.
What is a three-way match and why does it matter?
A three-way match compares the purchase order (what you agreed to buy), the goods receipt (what arrived) and the invoice (what you are being asked to pay). If all three agree within tolerance, the invoice can be paid without further review.
It matters because it is the control that lets everything else be routine. Without it, every invoice is a judgment call and someone senior has to look at all of them. With it, the majority pass untouched and human attention goes only to the exceptions.
| Document | Answers | Owned by |
|---|---|---|
| Purchase order | What did we agree to buy, at what price? | Procurement or the requester |
| Goods receipt | What actually arrived, and when? | The receiving team or requester |
| Supplier invoice | What are we being asked to pay? | The supplier |
Some organisations run a two-way match for services, comparing only PO and invoice. That is a deliberate trade of control for speed, and it should be a documented policy rather than an accident.
Which parts of P2P need human judgment?
Fewer than most teams assume. Three, specifically.
- Approving the spend. Whether to buy something is a business decision, governed by your delegation of authority. This never leaves your organisation.
- Resolving genuine exceptions. A price variance may be a supplier error, a renegotiated rate nobody recorded, or a partial delivery. Working out which needs a person who can ask.
- Releasing payment. The final authorisation to move money should sit with your approvers.
Everything else — capture, coding, matching, scheduling, statement reconciliation — is rule-following. That is why P2P is the most commonly outsourced and most commonly automated cycle in accounting.
Which P2P metrics should you actually track?
| Metric | What it tells you | What a poor result usually means |
|---|---|---|
| First-pass match rate | Share of invoices matching with no human touch | Bad PO discipline or missing goods receipts upstream |
| Invoice cycle time | Receipt to approved-for-payment | Approval bottlenecks, not AP capacity |
| Cost per invoice | Total processing cost divided by volume | Too much manual handling per document |
| Exception rate | Share needing investigation | Tolerance settings too tight, or supplier data issues |
| On-time payment rate | Paid to agreed terms | Scheduling problems, or approvals arriving late |
| Duplicate payment rate | Paid twice | Weak duplicate detection at capture |
First-pass match rate is the one to watch. It is the clearest signal of whether your problem is in accounts payable at all — a low rate almost always means POs are not being raised or receipts are not being entered, which is a procurement problem showing up in the AP queue.
How do you outsource procure-to-pay without losing control?
Control comes from where the approvals sit, not from where the people sit. A well-structured engagement keeps three things with you.
- Your delegation of authority stays yours. The team works inside your approval matrix, not around it.
- Payment release stays with your approvers. The team prepares the run to the last mile; you approve and release.
- System access is scoped and logged, with the team working inside your ERP rather than exporting data to somewhere you cannot see.
What the team takes on is throughput: capture, coding, matching, chasing exceptions, preparing the run, reconciling statements. See how the handover works in practice.
Stabilise before you automate. Taking over a process exactly as it runs today, getting it predictable, and only then rebuilding the mechanical steps is slower to start and far more reliable than automating on day one. Automating a broken process just produces errors faster.
What can be automated in procure-to-pay?
The judgment-free majority. In practice that means extraction and coding of invoice data, duplicate detection, matching against PO and receipt, routing exceptions to the right owner, assembling the payment file, and reconciling supplier statements.
What stays manual is the exception that genuinely needs a conversation and the approval itself. We cover the mechanics of this in how to automate accounts payable without replacing your ERP.
Frequently asked questions
What does procure-to-pay mean?
Procure-to-pay, or P2P, is the end-to-end cycle from requesting a purchase to paying the supplier and reconciling their statement. It covers requisition, approval, purchase order, goods receipt, invoice capture, three-way match, exception handling, payment and supplier reconciliation.
Is procure-to-pay the same as accounts payable?
No. Accounts payable is the second half — invoice capture through payment. Procure-to-pay includes the procurement steps before it: requisition, approval and purchase order. Many AP problems are actually caused upstream in those procurement steps.
What is the difference between a two-way and three-way match?
A three-way match compares purchase order, goods receipt and invoice. A two-way match compares only the purchase order and invoice, and is often used for services where there is nothing physical to receive. Two-way is faster but gives up a control.
Which parts of procure-to-pay should stay in house?
Approving spend under your delegation of authority, resolving genuinely disputed exceptions, and releasing payment. Capture, coding, matching, exception chasing, payment preparation and statement reconciliation transfer well to an outsourced team.
What is a good first-pass match rate?
Rather than chasing a published benchmark, measure your own rate first and set an improvement target in your agreement. A persistently low rate is usually a symptom of missing purchase orders or unentered goods receipts, so the fix is upstream in procurement rather than in accounts payable.