Procure-to-pay (P2P)
The full process from identifying a need to buy something, through ordering and receiving it, to paying the supplier's invoice.
In short
- It joins procurement and accounts payable into one flow.
- Typical steps: requisition, approval, purchase order, receipt, invoice, match, payment.
- Gaps between steps are where delays, errors and fraud tend to occur.
Procure-to-pay, or P2P, describes the end-to-end cycle of buying goods and services. It links the purchasing side, which decides what to buy and from whom, with the accounts payable side, which checks and pays the invoices.
The steps
- Need and requisition: an employee requests a purchase.
- Approval: the budget owner approves it.
- Sourcing: a supplier is chosen, from a contract or by quotation.
- Purchase order: the order is sent to the supplier.
- Receipt: goods or services are received and recorded.
- Invoice: the supplier invoices.
- Matching: the invoice is checked against the order and receipt.
- Payment: the invoice is paid on its terms and recorded in the ledger.
Why view it as one process
When purchasing and AP work in separate systems with separate goals, problems fall between them. Purchase orders aren't raised, so invoices arrive with nothing to match. Prices on orders are out of date. Every invoice becomes an exception. Receipts aren't recorded. Invoices wait. Treating P2P as one flow, with shared data from requisition to payment, reduces those handoffs and gives a clear view of committed and actual spend.
Not every purchase needs every step. Small, low-risk purchases are often handled by card instead.
Worked example
Measuring the cycle
A manufacturer measures its P2P cycle: 2 days from requisition to approved PO, 9 days to delivery, then 11 days from invoice to payment, of which 6 are spent resolving mismatches caused by outdated PO prices. Updating supplier prices in the purchasing system cuts invoice-to-payment time to 5 days.