On this page
- What procure to pay means
- The nine steps
- Who owns what
- A worked example
- Where the process breaks
- Why companies invest in fixing P2P
- Controls that matter most
- Building a P2P process from scratch
- Procure to pay across different kinds of spend
- Terms to know in P2P
- Where to go from here
- Manual, partly automated and fully automated P2P
- How to measure P2P
- Procure to pay software
- Frequently asked questions
Key takeaways
- Procure to pay is the full chain from request to payment, joining procurement and accounts payable.
- The nine steps are request, approve, source, order, receive, invoice, match, pay and record.
- The three-way match of order, receipt and invoice is the control that stops overpayment and fraud.
- Most delays happen at approval and at invoice exceptions, not in the buying itself.
- Measure it with cycle time, touchless invoice rate and the share of spend covered by a purchase order.
A purchase that takes four minutes to decide can take four weeks to finish. The delay is rarely in the decision. It sits in an approval waiting for someone on leave, a receipt nobody recorded, and an invoice that does not match the order by eleven dollars.
Procure to pay is the name for the chain those problems live in. Understanding the chain is the first step to shortening it.
What procure to pay means
Procure to pay, written P2P or sometimes purchase to pay, is the end to end process that begins when someone in the business asks to buy something and ends when the supplier is paid and the transaction is recorded in the books. It joins two worlds that often sit in different departments: procurement, which buys, and accounts payable, which pays.
Procure to pay is the connected process of requesting, approving, ordering, receiving, invoicing and paying for goods and services, with matching controls between each step.
Its mirror image on the sales side is order to cash. If you know one, the logic of the other is familiar.
The nine steps
1. Requisition
An employee raises a request describing what they need, how much and why. The request should carry a budget code. Without one, finance cannot tell what the money was for until the end of the quarter. See the purchase requisition guide.
2. Approval
The request goes to someone with authority over that budget. Approval rules usually depend on amount and category. A 200 dollar item needs one signature. A 50,000 dollar contract needs several.
3. Sourcing and supplier selection
The buyer picks a supplier from an approved list, or runs a quote or tender for bigger purchases. For one-off services outside the list, this is where new suppliers are set up.
4. Purchase order
The buyer issues a purchase order to the chosen supplier. It sets quantity, price and delivery terms, and becomes the document everything later is matched against.
5. Receiving
The goods arrive or the service is completed, and someone records it. For physical goods this is a goods receipt note. For services it is usually a sign-off from the requester.
6. Invoice receipt
The supplier sends an invoice. It may arrive by email, paper, a supplier portal or electronic exchange. Capturing the data accurately is its own task, and the point where many teams still type numbers by hand.
7. Three-way match
Accounts payable compares three documents: the purchase order, the goods receipt and the invoice. Quantities, prices and totals should agree within a set tolerance. Differences become exceptions that someone must resolve. The invoice approval and GRN guide explains this in depth.
8. Payment
Matched invoices are scheduled and paid according to the agreed terms. Paying early without a discount wastes cash. Paying late damages the relationship, and sometimes triggers interest.
9. Record and reconcile
The transaction is posted to the general ledger and the documents are archived. Auditors will ask for them later.
Who owns what
| Step | Usually owned by | What goes wrong when it is weak |
|---|---|---|
| Requisition and approval | Requesters and budget holders | Spend starts before anyone has agreed to it |
| Sourcing and PO | Procurement or purchasing | Off-contract prices and duplicate suppliers |
| Receiving | Operations or the requester | Payment for things that never arrived |
| Invoice, match and payment | Accounts payable | Duplicate payments, late payments, fraud risk |
A worked example
A facilities manager requests 40 office chairs at 120 dollars each, a total of 4,800 dollars. Her director approves. Procurement orders from the approved furniture supplier under purchase order PO-1042 for 40 units at 120 dollars.
The supplier delivers 38 chairs because two are back-ordered. The warehouse records a receipt of 38. The invoice arrives for 40 chairs at 4,800 dollars.
The three-way match fails on quantity. Accounts payable holds the invoice, asks the supplier for a corrected invoice for 38 chairs at 4,560 dollars, and pays that amount. The remaining 2 chairs are invoiced when they arrive. Without the match, the company would have paid 240 dollars for chairs it did not have.
Where the process breaks
Three failure points account for most of the pain, and each has a plain cause.
Approvals stall. Requests wait in inboxes because the approver does not know they are waiting. The fix is routing rules, reminders and a named backup for every approver.
Buying skips the PO. People order first and ask for a PO afterwards, which means the order was never controlled. Sometimes this is a sign that raising a PO is too slow. Fix the speed before you blame the people.
Invoices fall out of the match. Price differences, partial deliveries and missing receipts create exceptions. Each one takes a person time. Cleaner purchase orders and prompt receiving prevent most of them.
Why companies invest in fixing P2P
The benefits are practical rather than glamorous, and finance leaders tend to notice them first.
- Fewer duplicate and incorrect payments. The match catches mistakes before cash leaves.
- Better cash planning. When every approved order is visible, you know what you owe weeks before invoices arrive.
- Faster closing of the books. Accruals get easier when orders and receipts are recorded as they happen.
- Stronger supplier relationships. Suppliers who are paid accurately and on time stop padding their quotes and start prioritizing your work.
- An audit trail that builds itself. Each step leaves a record with a name and a date on it.
Get the next guide in your inbox
We publish plain-language guides for people who buy and run procurement software. Leave your email and we send you new ones as they go live.
Controls that matter most
Good P2P is as much about separating duties as about speed. The person who requests should not also approve their own request. The person who creates a supplier should not also pay that supplier. The person who receives goods should not also approve the invoice for them. These separations make fraud hard and honest mistakes visible.
- Supplier changes, especially bank detail changes, get verified by a call to a known number, not by replying to the email that asked for the change.
- Payments above a set amount need a second approver.
- Duplicate invoice checks run on supplier, invoice number and amount.
- A regular report lists invoices paid without a purchase order, so the exceptions are seen, not buried.
Building a P2P process from scratch
- Map what happens today by following one real purchase from request to payment. Write down every handoff.
- Mark where time is lost and where mistakes appear. Those two lists are your priorities.
- Set approval limits and the rule for when a purchase order is required.
- Standardize the request form so every request carries the same information.
- Agree the tolerance for the three-way match, for example price within 2 percent and quantity exact.
- Name an owner for exceptions and publish a target resolution time.
- Pick three measures, record today's baseline and review monthly.
Procure to pay across different kinds of spend
The nine steps stay the same, but the emphasis moves with what you buy.
| Spend type | What matters most | Typical twist |
|---|---|---|
| Physical goods | Receiving and the three-way match | Partial deliveries and damaged goods |
| Services and consulting | Approval before work, and sign-off on completion | No physical receipt, so someone must confirm the work was done |
| Software subscriptions | Renewal control and user counts | Invoices can arrive from the vendor with no PO at all |
| Recurring utilities and rent | Accurate recurring payments | Often exempt from POs under policy |
| Capital items | Budget approval and asset records | Longer approval chain, link to fixed asset register |
Terms to know in P2P
- Accrual. An expense recorded before the invoice arrives, usually because goods were received but not yet billed.
- GRN. Goods receipt note, the record of what arrived.
- Net 30. Payment due 30 days after the invoice date. Net 60 is 60 days.
- Early payment discount. A reduction for paying sooner, often written as 2/10 net 30, meaning 2 percent off if paid within 10 days.
- Tolerance. The allowed difference between invoice and order before a match fails.
- Touchless processing. An invoice that moves from receipt to payment without a human step.
Where to go from here
Two pages go deeper on the pieces that cause most trouble: purchase requisitions at the front and the invoice approval and GRN guide at the back. For a view of the full buying cycle that includes planning and supplier review, read the procurement lifecycle guide.
Manual, partly automated and fully automated P2P
Teams run procure to pay in very different ways. The differences are in how much the work depends on human memory.
- Manual. Email requests, paper or spreadsheet POs, invoices keyed in by hand. Works at low volume, breaks when volume or headcount changes.
- Partly automated. Approvals and POs run in a system, but invoices still arrive as PDFs that someone retypes.
- Automated. Requests, approvals, POs, invoice capture and matching run in connected software. People handle exceptions only.
The jump from manual to automated is not all-or-nothing. Many teams get most of the benefit by fixing approvals and PO creation first. See procurement automation for how to sequence it.
How to measure P2P
- Requisition to PO cycle time. How many days from request to order?
- Invoice processing cost and time. How long and how much per invoice?
- Touchless invoice rate. The share of invoices that match and pay without a human touching them.
- PO coverage. The share of spend that has a purchase order. Low coverage means buying outside the process.
- Exception rate. The share of invoices that fail the match.
The full set of ideas is in our procurement KPIs guide.
Procure to pay software
Dedicated P2P tools connect requisition, PO, receipt and invoice in one flow, usually with approval routing and a link to your accounting system. Before you shop, write down your current steps and mark where time is lost. That map tells you which features you need. Our procure to pay software category page lists what to compare.
- Every request has a budget code and an approver.
- Every approver has a named backup.
- Purchase orders are issued before the supplier starts work.
- Receipts are recorded within a few days of delivery.
- Invoice exceptions have a named owner and a target resolution time.
- You can find any order, receipt and invoice together in under a minute.
Frequently asked questions
What is the procure to pay process?
It is the chain of steps from requesting a purchase through approval, ordering, receiving, invoicing and payment, ending with the transaction recorded in the books.
What is the difference between procure to pay and purchase to pay?
They are the same process. Procure to pay is the more common name, and P2P is the usual abbreviation for both.
What is a three-way match?
It is a check that compares the purchase order, the goods receipt and the supplier invoice. If quantities and prices agree within tolerance, the invoice is approved for payment.
Who is responsible for procure to pay?
Procurement owns the buying steps and accounts payable owns the paying steps. Requesters and budget holders own the first two steps. A single process owner helps connect them.
Do small businesses need a P2P process?
Yes, in a lighter form. Even five people spending company money benefit from approval rules, purchase orders for larger items and a check that goods arrived before paying.