The procure-to-pay process, step by step

Every supplier payment starts long before the bill arrives. Someone needs something, someone approves the spend, an order goes out, goods arrive, and only then does a bill turn into a payment and an entry in the books. When those steps live in different tools, each handoff is a chance to lose an approval, pay the wrong price or rebuild the story at month-end.

This guide explains the procure-to-pay process step by step, follows one illustrative purchase from request to close, and shows which parts to automate and which decisions should stay with people.

What is the procure-to-pay process?

Procure-to-pay, often shortened to P2P and also called purchase-to-pay, is the end-to-end process a business follows to buy goods and services and pay for them: from the first request, through approval, ordering, receiving and matching the supplier's bill, to paying the supplier and recording the payment in the books. It joins two jobs that are often run separately: procurement, which decides what to buy and from whom, and accounts payable, which checks and pays the bills.

The procure-to-pay process in seven steps

1. 1Request. Someone records what they need, why, roughly what it will cost and which budget it comes from.
2. 2Approve. The budget owner approves the request, with the amount checked against what's left in the budget.
3. 3Order. A purchase order goes to the supplier with the agreed items, prices, currency and terms.
4. 4Receive. Whoever receives the goods or the service records what actually arrived.
5. 5Match. The supplier's bill is compared with the order and the receipt. Bills that agree move on; bills that don't are held.
6. 6Pay. The bill is approved for payment and paid by its due date, with the exchange rate and fees confirmed before money moves.
7. 7Record. The payment is posted with its rate and fee, matched to the bank line, and the supplier's balance goes to zero.

The match in step five is three-way matching, and steps five to seven are the core of the accounts payable process. Procure-to-pay adds the steps before the bill, where spend is decided.

A worked example: one purchase, request to close

The picture above follows the illustrative purchase used across this site: 6 laptops from Alder Tech GmbH at €1,500 each, €9,000 in total.

1. 1Request and approve. The IT lead requests 6 laptops. The budget owner approves, and the IT budget shows $21,440 left of $41,000 once this purchase is counted.
2. 2Order. Purchase order PO-2087 goes to Alder Tech GmbH for €9,000.
3. 3Receive. All 6 laptops arrive and the receipt is recorded against PO-2087.
4. 4Match. Bill #A-311 arrives for 6 laptops at €1,500. It agrees with the order and the receipt, so it's booked at 1 EUR = 1.0800 USD as $9,720 in JE-5520.
5. 5Pay. The bill is over $5,000, so two approvers sign off. By the payment date the rate is 1.0850, so the supplier receives €9,000 and $9,780 leaves the bank, including a $15 fee.
6. 6Record. JE-5521 clears $9,720 from accounts payable and records a $45 exchange loss and the $15 fee. The supplier's balance is $0 and the bank line matches to the dollar.

Seven steps, four decisions made by people and three checks or postings that ran on their own. Nothing was typed in twice, and the $60 difference between bill and bank was explained the moment the payment was made, not at month-end.

Procure-to-pay vs source-to-pay vs accounts payable

• Accounts payable starts when the bill arrives: capturing, checking, approving, paying and recording it.
• Procure-to-pay starts earlier, at the request, so spend is approved and ordered before any bill exists.
• Source-to-pay starts earlier still, with choosing suppliers and agreeing contracts, then runs through procure-to-pay.
• Order-to-cash is the mirror image on the customer side: from a customer's order to the cash you collect.

What to automate, and what to keep for people

Procure-to-pay automation works best when it takes over the checks and the handoffs, and leaves the decisions with the people accountable for them. Good candidates to automate:

• Routing each request to the right approver, based on amount, budget and supplier.
• Checking the budget at the moment of approval, including orders already committed.
• Turning an approved request into a purchase order, so nothing is typed in again.
• Matching each bill to its order and receipt as it arrives, and holding only the ones that differ.
• Checking for duplicate bills and changed supplier bank details before anything is paid.
• Posting the payment with its exchange rate and fee, and matching it to the bank line.

Keep these with people:

• Whether to buy, and from whom.
• Approving spend, with a second approver for larger amounts.
• Resolving a held bill: asking for a credit, accepting a difference with a reason, or amending the order.
• Releasing payments, and deciding when to pay based on cash and terms.

Common procure-to-pay problems

• Purchases made without an order, so the first sign of the spend is the bill.
• Approvals given in email or chat that never reach the record that pays the bill.
• Budgets checked in a spreadsheet that's out of date by the time the order goes out.
• Receipts never recorded, so bills are matched to the order alone.
• The same purchase entered separately in purchasing, payables, the bank and the books.
• Foreign payments made from a bank portal, with the rate and fee worked out later.

Procure-to-pay metrics worth tracking

• Purchase order coverage: the share of spend that had an approved order before the bill arrived.
• First-time match rate: the share of bills that agree with their order and receipt without being held.
• Cycle time: the days from an approved request to the supplier being paid.
• Exception rate: the share of bills held for a price, quantity or duplicate problem, and how long they take to resolve.
• On-time payment rate: the share of bills paid by their due date.

Why it matters to a CFO

• Spend is approved before it's committed, not discovered when the bill arrives.
• Budgets show what's already ordered, so they're current when decisions are made.
• You pay only for what was ordered and received, at the agreed price.
• Cash forecasts include orders that haven't been billed yet.
• Every payment traces back to its request, approvals, receipt and bill, ready for audit.

What to look for in procure-to-pay software

• Requests, orders, receipts, bills and payments on one record, so each purchase is entered once.
• Approval rules you set by amount, budget and supplier, that can't be skipped by paying from somewhere else.
• Budget checks that include committed orders, not just bills already paid.
• Matching that shows exactly which line is off, and by how much.
• Payments in the currencies your suppliers use, with the rate and fee recorded on the payment.
• Journal entries posted from the transaction itself, with every approval kept alongside it.

What changes on one system

Separate tools usually join these steps by syncing records between purchasing, payables, the bank and the books. On one system there's nothing to sync: the request becomes the order, the order is matched to the receipt and the bill, and the payment posts to the books with its rate and fee attached. See how it works on the Procurement and Accounts Payable pages.