Procure-to-pay (P2P) is the business process connecting a purchase request to supplier payment. It covers authorization, ordering, receiving or service acceptance, invoice review and payment. The steps may span purchasing software, an ERP, accounts payable and a bank; one application does not have to perform them all.
For a small-business owner or purchasing lead, the useful question is who owns each handoff and what evidence the next person receives. A well-kept PO helps, but it does not prove that the invoice is correct or the payment is authorized.
The procure-to-pay cycle
Different organizations group the steps differently. SAP's P2P overview groups the process into selection, compliance and ordering, receipt and reconciliation, and invoicing and payment. The seven-step version below makes the responsibilities easier to assign in a small team.
| Step | Decision or record | Owner to identify |
|---|---|---|
| Request | What is needed, where, when and why; stock already available | Requester |
| Authorize | Whether the purchase is permitted under the relevant policy | Eligible approver |
| Order | Supplier, items, units, price, delivery requirement and terms | Buyer |
| Receive | What arrived and what was accepted, rejected or remains due | Receiver or service owner |
| Capture invoice | Supplier invoice, reference, charges, coding and duplicates | Accounts payable |
| Reconcile and approve | Relevant order, receipt, invoice and exception evidence | Authorized reviewer |
| Pay and record | Agreed due date, approved amount, verified payee and payment record | Finance/payment owner |
These are responsibilities, not a rule that seven different people must participate. A small team can combine roles while retaining the review and authorization controls its risk requires.
The sequence also has exceptions. An agreed deposit may be invoiced before delivery. A service needs acceptance evidence appropriate to the work. A partial shipment may support a partial invoice. Record the actual agreement instead of forcing every purchase through a fictional full-delivery sequence.
A worked example: a partial delivery
Assume a fictional shop orders 20 cases at $25 per case, with no freight or tax in this example. The supplier confirms the $500 order but delivers 12 cases first. Eight remain due.
- The PO records the 20-case commitment and agreed price.
- Receiving records 12 accepted cases, worth $300 at the agreed price.
- An invoice for 12 cases at $25 is consistent with that receipt, subject to the remaining finance checks.
- An invoice for all 20 cases leaves $200 beyond the accepted receipt to investigate under the billing agreement.
If the second delivery arrives, record it against the remaining eight cases. Do not receive the original 20 again. If the supplier cancels the balance, preserve that decision and assess whether another purchase is needed.
Three-way matching helps compare the invoice with the order and relevant receipts. A match can support approval; it does not verify bank details, establish tax treatment, or authorize payment by itself. Choose tolerances deliberately rather than copying a universal percentage.
P2P, procurement, source-to-pay and order-to-cash
Procurement is the broader discipline of obtaining what the business needs, including supplier strategy and performance review. P2P focuses on the operational and financial path from need to payment. Source-to-pay includes upstream sourcing and contracting in that connected scope. Order-to-cash describes the seller's order, fulfillment, billing and collection process.
Closed-loop procurement describes how purchasing results inform the next buying decision. It overlaps with P2P but is not a synonym for payment execution. Receiving an order and sending its context to accounting can close an operational handoff while invoice approval and payment still remain with finance.
Where small teams can improve first
Start with one recurring problem: requests without a need-by date, unreviewed supplier changes, missing receipt evidence, duplicate invoices or overdue approvals. Trace an actual order through the people and records involved.
Keep the original request, supplier proposal and buyer-approved change distinguishable. An updated PO reduces avoidable questions, but the invoice can still contain a new error. Track accepted receipts and prior invoices so the same goods are not billed or paid twice.
Useful measures include time awaiting approval, supplier-confirmation coverage, overdue outstanding quantities and unresolved invoice exceptions. Define each measure's starting event, denominator and time period. Shorter payment time is not automatically better: pay according to agreed terms and the business's cash decision.
Choosing software for the missing handoff
If supplier replies, partial deliveries and purchasing context are the main gaps, evaluate LineNow's procurement workflow. LineNow connects requisitions, orders, supplier communication, receiving and accounting handoff. Supported supplier replies become reviewable changes on a living purchase order.
LineNow keeps requisitions separate from supplier purchase orders. Requests go directly to the owner or Procurement for item review, sourcing, and ordering. Business-unit access determines who can handle the request.
Keep finance's review responsibilities explicit.
Bring the 20-case example to a demonstration, including the partial invoice and final delivery. Ask the buyer, receiver and finance reviewer to find their evidence independently. Book a purchasing workflow review around the handoff that is causing work today.