Try it now, capture a real invoice
Free plan · No credit card · Your data stays yours
The procure-to-pay process, often shortened to P2P, is the end-to-end cycle a business follows to buy goods or services and pay the supplier, running from the moment someone requests a purchase to the moment the invoice is paid and recorded. It links procurement and accounts payable into one flow: requisition, approval, purchase order, receipt, invoice, matching, and payment. When those steps connect cleanly, you get spend control, fewer errors, and faster close. When they do not, you get maverick spend, duplicate payments, and month-end chaos.
Below is each stage in order, what happens in it, who owns it, and where automation removes the manual work.
What is the procure-to-pay process?
The procure-to-pay process is the connected set of steps that turn a purchasing need into a paid, recorded transaction. It starts in procurement with a requisition and purchase order, moves through receiving when goods arrive, and finishes in accounts payable with invoice capture, three-way matching, approval, and payment. The goal is a documented trail from request to payment so every dollar spent is authorized, matched to what was ordered and received, and paid once.
The 7 steps of procure-to-pay
Most organizations run the same seven stages, whether on paper or in software. The table gives you the fast version, and the sections below add detail.
| Step | What happens | Who owns it |
|---|---|---|
| 1. Requisition | Requester submits a purchase request for approval | Requesting department |
| 2. Approval | Manager or budget owner authorizes the spend | Budget holder |
| 3. Purchase order | Approved request becomes a PO sent to the supplier | Procurement |
| 4. Receiving | Goods or services arrive and are logged against the PO | Receiving or requester |
| 5. Invoice capture | Supplier invoice arrives and data is captured | Accounts payable |
| 6. Matching and approval | Invoice is matched to PO and receipt, then approved | Accounts payable |
| 7. Payment | Approved invoice is paid and recorded in the ledger | Accounts payable |
1. Purchase requisition
An employee identifies a need and submits a requisition, an internal request to buy something. The requisition captures what is needed, quantity, estimated cost, and the budget or cost center it hits. This is the control point that catches spend before it happens rather than after the invoice lands.
2. Requisition approval
The requisition routes to the right budget owner for approval, based on amount and category. A clear approval matrix here prevents unauthorized or off-contract buying. Manual routing by email is where most delays start, which is why approval rules are usually the first thing teams automate.
3. Purchase order
Once approved, the requisition becomes a purchase order, a formal commitment sent to the supplier that states items, quantities, prices, and terms. The PO is the reference every later step matches against. Keeping structured purchase orders, rather than ad hoc emails, is what makes automated matching possible downstream. Teams that lack a system for this often adopt dedicated purchase order management software to issue and track POs consistently.
4. Goods receipt
When the goods or services arrive, the receiver records what actually showed up against the PO. This receipt is the third document in three-way matching and the proof that you got what you paid for. A missing or late goods receipt is a common reason invoices sit in exception queues, an issue we cover in goods received not invoiced.
5. Invoice capture
The supplier sends an invoice, and accounts payable captures its data: vendor, invoice number, line items, amounts, and tax. Manual keying here is slow and error-prone. AI-based invoice data capture reads the document and extracts the fields automatically, which is the foundation for touchless processing.
6. Matching and approval
AP matches the invoice to its purchase order and goods receipt, confirming price, quantity, and terms line up. This is three-way matching, and it is the strongest control against overpayment and fraud. Matches within tolerance can auto-approve; exceptions route to a human. Dedicated invoice matching software handles this at volume.
7. Payment
The approved invoice is scheduled and paid by ACH, check, card, or wire, then recorded in the general ledger. Good P2P systems time payments to capture early-payment discounts and avoid late fees. See vendor payment software for how the payment step is automated.
Procure-to-pay vs accounts payable
Procure-to-pay is the whole cycle from requisition to payment. Accounts payable is the back half: capturing invoices, matching, approving, and paying. Put simply, procurement owns the front (requisition, PO, receipt) and AP owns the back (invoice to payment). The two only work well when they share data, because AP can only auto-match an invoice if a clean purchase order and goods receipt already exist upstream. That is why P2P is treated as one connected process rather than two separate teams.
Why automate the procure-to-pay process?
Manual P2P is slow, expensive, and hard to control. Approvals stall in inboxes, invoices get keyed by hand, and matching is done on spreadsheets. Automating the cycle delivers a few concrete wins: spend is authorized before it happens, invoices are captured and matched without manual data entry, duplicate and fraudulent invoices are caught by controls rather than luck, and finance gets real-time visibility into committed and actual spend. The result is a lower cost per invoice, a faster close, and staff freed from keying to do analysis. Our guide to the best AP automation software compares the tools that handle the AP half of this cycle.
Common procure-to-pay challenges
Even with software, a few problems recur. Maverick spend happens when people buy outside the process, so requisitions never get created. Missing goods receipts leave invoices unmatched and stuck in exceptions. Poor supplier data leads to payments to the wrong account. And disconnected systems force staff to rekey the same data between procurement, AP, and the ERP. Each of these traces back to a broken link in the chain, which is the argument for running P2P as one integrated flow instead of stitched-together steps.
Frequently asked questions
What does procure-to-pay mean?
Procure-to-pay means the full business process of buying goods or services and paying for them, from the initial purchase requisition through to the supplier payment. It connects procurement activities like requisitions and purchase orders with accounts payable activities like invoice matching, approval, and payment, into one documented, controlled cycle.
What are the stages of procure-to-pay?
The core stages are requisition, approval, purchase order, goods receipt, invoice capture, matching and approval, and payment. Some models add supplier selection and contract management at the front. The essential idea is a documented path from a purchasing need to a paid, recorded transaction, with a control at each handoff.
Is procure-to-pay the same as source-to-pay?
No. Source-to-pay is broader. It adds the sourcing activities that come before procurement, such as finding suppliers, running RFPs, negotiating contracts, and managing supplier relationships. Procure-to-pay begins once you already know what you are buying and from whom, starting at the requisition and ending at payment.
How does accounts payable fit into procure-to-pay?
Accounts payable owns the back half of procure-to-pay: capturing the supplier invoice, matching it to the purchase order and goods receipt, routing it for approval, and paying it. AP depends on clean upstream data, because it can only automate matching if a valid purchase order and receipt already exist from the procurement side.