The Procure-to-Pay (P2P) Process, Explained Step by Step

Procure-to-pay (P2P, sometimes called purchase-to-pay) is the end-to-end process that takes a business need from request all the way to a paid supplier invoice. Done well, it's invisible: the right thing is bought from an approved vendor at an agreed price, received, checked, and paid — with an audit trail at every step. Done badly, it's where money leaks through maverick spend, duplicate payments, and approvals that take a week of email.

This guide walks through the eight stages of the procure-to-pay cycle, who owns each one, and the controls that keep it clean. It's the operational backbone behind every reverse auction and RFQ you run.

The eight stages of procure-to-pay

1. Identify the need — a department realises it needs goods or services.
2. Raise a purchase requisition — the need is formalised and routed for approval.
3. Approval — the requisition clears the approval workflow.
4. Source the supplier — RFQ, RFP, or reverse auction to select a vendor and price.
5. Issue a purchase order — the approved, sourced requirement becomes a binding PO.
6. Receive the goods/services — delivery is logged against a goods receipt note.
7. Match the invoice — three-way match of PO, GRN, and invoice.
8. Pay the supplier — the matched invoice is scheduled and paid.

Stage 1–2: Need and requisition

Everything starts with a need — a line falls short on raw material, a laptop dies, a contractor is required. The requester captures it as a purchase requisition: what, how much, when, and (ideally) a cost-centre and budget line. The requisition is an *internal* document — a request for permission to spend — not yet a commitment to any supplier.

Stage 3: Approval

The requisition flows through an approval workflow — often multi-step and amount-based. A ₹5,000 stationery order might need one manager; a ₹15 lakh capex item routes through the cost-centre owner, finance, and the CFO. Good workflows enforce separation of duties (the requester can't approve their own request) and keep a timestamped record of every decision.

This is the single biggest source of delay in most Indian buying teams, and the easiest to fix: route by amount, escalate on timeout, and let approvers act from their phone instead of a forwarded PDF.

Stage 4: Sourcing

With approval in hand, sourcing finds the right supplier at the right price. The instrument depends on the buy: a quick RFQ for a defined, priced item; an RFP for a solution where approach matters; or a live reverse auction when you have a competitive field and a clear spec. For repeat categories, you may already have a rate contract and can skip straight to a PO.

Stage 5: Purchase order

The winning quote becomes a purchase order: a numbered, dated document stating items, quantities, unit prices, taxes, delivery, and payment terms. Once the supplier accepts, it's a contract. In India the PO must carry the right GST treatment and HSN/SAC codes so the downstream invoice and input tax credit reconcile. A consistent purchase order format avoids disputes later.

Stage 6: Goods receipt

When the delivery arrives, the receiving team logs a goods receipt note (GRN) recording what actually showed up — quantity, condition, batch, and any shortfall or damage. The GRN is the independent evidence that you received what you ordered; without it, you're paying on the supplier's word alone.

Stage 7: Invoice and three-way match

The supplier's invoice is checked against two other documents in a three-way match: the PO (what you agreed to buy), the GRN (what you received), and the invoice (what you're being billed). Only when all three agree on quantity and price does the invoice clear for payment. This single control blocks the most common leakages — overbilling, billing for undelivered goods, and duplicate invoices.

Stage 8: Payment

A matched, approved invoice is scheduled for payment per the agreed terms — net 30, net 45, or against milestones. Smart AP teams track early-payment discounts and ensure TDS is deducted correctly where applicable. Payment closes the loop, and the supplier's on-time, in-full performance feeds their supplier scorecard for next time.

Where P2P breaks — and the controls that fix it

• Slow approvals → route by amount, escalate on timeout, approve from mobile.
• Maverick spend → require a PO before any commitment; block off-catalogue buys.
• Overbilling → enforce a strict three-way match before any payment.
• Duplicate payments → unique invoice numbers and PO references, validated automatically.
• No visibility → a single system of record so spend under management is measurable.

P2P is also where procurement either earns or loses trust with finance. A clean, auditable cycle — requisition to payment, with three-way matching and GST handled correctly — is what lets a buying team scale spend under management without scaling headcount.

Procupy runs the full procure-to-pay cycle in one place — requisitions, amount-based approvals, RFQs and reverse auctions, POs, GRNs, three-way matched invoices, and payments — so nothing falls between email and spreadsheet. Compare it against tools like Procurify or SAP Ariba.