Procure to Pay Process: The P2P Cycle in 8 Steps

People search for this when they have just been asked to 'explain P2P', when an ERP consultant has drawn eight boxes on a whiteboard, or when accounts and procurement are arguing about whose job a stuck invoice is. The cycle is the same in a SAP plant, a Tally-plus-Excel factory, and a buying team that still works from WhatsApp. What changes is which document is missing, and what that missing document costs you.

The procure to pay cycle at a glance

Read the cycle left to right. Each step creates a document the next step is checked against. If a step is skipped, the match at the end has nothing honest to match to.

1. 1

   Identify the need

   A person or a reorder rule says something must be bought.

2. 2

   Purchase requisition

   The need is written down, with quantity, date and a suggested vendor.

3. 3

   Approval

   The right person accepts the spend before anyone promises a supplier.

4. 4

   Sourcing

   Quotes, a rate contract or an auction set the price.

5. 5

   Purchase order

   The buyer sends a numbered order the vendor can accept.

6. 6

   Goods receipt

   Stores record what actually arrived.

7. 7

   Invoice and match

   Accounts compare the invoice with the order and the receipt.

8. 8

   Payment

   The vendor is paid, and the order is closed.

The SAP transaction codes are only labels for the same documents. A company that does not run SAP still has a requisition, an order, a receipt and an invoice. If one of those four is missing, you do not have a procure to pay process. You have a habit of paying bills.

8 steps of the procure to pay process

1. Identify the need

Someone notices stock is low, a machine needs a spare, or a project needs a service. In a plant this is often a storekeeper or a maintenance engineer. In an office it is whoever is about to buy something on a card. The failure here is buying before anyone has said what 'done' looks like: quantity, specification, need-by date, and where it must be delivered.

2. Purchase requisition

The need becomes a purchase requisition. It is internal. No vendor has been promised anything. A useful PR states the item, quantity, unit, required date, delivery location, a suggested vendor if there is one, and the cost centre. The document created is the PR, with its own PR number. The common failure is a one-line indent ('MS sheet, urgent') that forces the buyer to guess the grade, the thickness and the plant.

A blank you can copy is the purchase requisition form.

3. Approval

The requisition waits until someone who may spend that money says yes. Approval is not a courtesy. It is the moment the company accepts the spend. Route it by amount and by category: a storekeeper can pass a small repeat buy, a plant head passes a larger one, finance passes anything that hits a capital budget. The document is the approval record (who, when, and any condition). The failure is an approver who is always travelling, so people stop raising PRs and the invoice arrives first.

4. Sourcing

If a rate contract or a catalogue already fixes the price, sourcing is 'pick that rate and move on'. If it does not, the buyer sends an RFQ, collects quotations, and lines them up on a comparative statement. For a clear specification and three or more suppliers, a reverse auction does the same job in one sitting. The documents are the RFQ, the quotations, and the comparison. The failure is comparing unit prices that do not include freight, GST treatment, or payment terms, then calling the cheapest line the winner.

5. Purchase order

The buyer issues a purchase order: items, quantity, price, delivery place, delivery date, and payment terms, under a PO number. Once the vendor accepts it, that is the commercial commitment. Use a purchase order format that has room for GSTIN, HSN and the tax rate, so the invoice is not the first time anyone writes those down. The failure is a PO raised after the goods have already arrived, which means the price was never really agreed.

6. Goods receipt

The vehicle arrives with a delivery challan or a tax invoice. Stores count and inspect, and write a goods receipt note for what they actually accept. Short shipments, damage and the wrong grade are recorded here, not in an email a week later. The failure is a GRN that copies the PO quantity instead of the counted quantity. The match then passes, and you pay for goods you do not have.

7. Invoice and three-way match

The vendor's tax invoice should quote the PO number. Accounts compare three things: the PO (what was ordered), the GRN (what was received), and the invoice (what is being billed). That is three-way matching. Quantity, price and tax have to agree within the tolerance you have set. A mismatch is a query, not a payment. The failure is 'we always release MSME invoices so we do not miss 45 days', which trains vendors to send invoices that nobody has checked.

8. Payment

Treasury pays the matched, approved invoice and sends a payment advice that lists the invoices and PO numbers it covers. The PO is closed, or left partly open if more is still to come. The failure is a payment that cannot be tied back to a PO, so the next dispute starts from a bank statement instead of a document.

Documents in the P2P cycle

You do not need every document on every buy. A rate-contract release can skip a fresh RFQ. You do need to know which document you skipped, and why the match can still be done.

• Purchase requisition. Internal request. Not a promise to a vendor.
• RFQ and quotation. The ask, and each vendor's priced reply.
• Comparative statement. The sheet that shows why one quote won.
• Purchase order. The external commitment, with a PO number.
• Delivery challan. What the vendor says is on the truck when there is no sale yet, or alongside the invoice.
• Goods receipt note. What stores accepted.
• Tax invoice. What the vendor is billing, with GST.
• Payment advice. Which invoices this bank transfer covers.

Procure to pay example

A fabrication shop in Pune needs 500 kg of mild-steel sheet for a job starting in three weeks. The storekeeper raises a purchase requisition: 500 kg, IS 2062 grade, 2 mm, deliver to the Chakan plant, need-by date filled in. The plant head approves it the same day because it is inside the monthly steel budget.

There is no rate contract for this thickness. The buyer sends the same specification to three mills and stockists. One quotes ₹74 per kg ex-works Pune, one quotes ₹72 per kg delivered, one quotes ₹70 per kg but wants 100% advance and is not sure of the grade certificate. Compared on cost at the gate, the ₹72 delivered quote is the one they can actually use. The buyer issues PO-2026-1184 for 500 kg at ₹72, which is ₹36,000, plus GST at 18% (₹6,480), total ₹42,480, payment 30 days from GRN. Confirm the HSN rate for the exact sheet before you copy 18% onto a live PO.

The truck comes with a delivery challan for 500 kg. Stores weigh it, accept 480 kg, and record 20 kg of wet, rusted sheet as rejected on the GRN. The vendor's tax invoice still says 500 kg. Three-way match holds the invoice. The vendor sends a credit for 20 kg, the invoice is corrected to ₹34,560 plus GST of ₹6,220.80, and accounts release payment. The ₹6,220.80 is input tax credit only if the usual GST conditions are met: you have the tax invoice, you have received the goods, and the supplier has reported the supply. This is a buying example, not tax advice.

The vendor is a micro enterprise and the PO says 30 days, which is inside the 45 days the MSMED Act allows when there is a written agreement. If the match had dragged past that window, the interest and the income-tax disallowance under section 43B(h) would sit with the buyer, not with the vendor. The 45-day payment rule is the constraint. The match is how you pay the right amount without missing it.

Procure to pay in India: GST, e-invoicing, TDS and MSME

The cycle is global. Four Indian rules change how the documents have to be filled.

• GST on the PO. Intra-state supply is CGST plus SGST. Inter-state supply is IGST. Write the rate and the HSN or SAC on the PO so the invoice is not a surprise. Input tax credit is not automatic: blocked credits under section 17(5), a supplier who does not report the invoice, and goods you have not received are the usual reasons a 'cheap' quote is not cheap. The buyer's longer note is the GST and input tax credit guide.
• E-invoicing. Suppliers above the notified aggregate-turnover threshold have to raise an IRN on the Invoice Registration Portal. The threshold has been ₹5 crore since 1 August 2023. Check the latest CBIC notification before you reject a vendor for not having an IRN, and before you assume a smaller vendor must have one.
• TDS. Some payments need tax deducted at source, for example under section 194C for works contracts or section 194Q for purchases of goods once the buyer's and the transaction's thresholds are crossed. The PO should say whether the price is subject to TDS, so the vendor's receivable matches what you pay.
• MSME 45 days. Section 15 of the MSMED Act gives 15 days to pay if there is no written agreement, and at most 45 days if there is one. Section 43B(h) can disallow the expense for the year if you pay a micro or small supplier late. Medium enterprises are not in 43B(h). Get the Udyam category on the vendor record before you promise a term you cannot legally keep.

P2P vs S2P vs O2C

These three names get used as if they were the same project. They are not.

Source to pay is P2P plus the work before the requisition: what you spend, who you should buy from, and the contract you put in place. Procure to pay versus order to cash is the same deal seen from both companies. Your purchase order is your supplier's sales order. This page stays on the buyer's cycle.

P2P KPIs to track

Pick a few and define them once. A borrowed target from another company is useless if they count 'managed' differently from you.

• PO cycle time. Clock from an approved requisition to the PO the vendor receives. Split catalogue buys from buys that needed quotes. One blended number hides both.
• Cost per PO. Procurement and accounts-payable cost in a month, divided by POs issued. It tells you whether a tiny PO is worth the handling.
• First-pass match rate. Share of invoices that match the PO and the GRN without a hold. A low rate is usually a bad PO or a copied GRN, not a 'vendor problem'.
• Spend on PO. Value of invoices that had a PO before the invoice, divided by supplier spend. This is the practical cousin of spend under management.
• Days payable outstanding. How long you take to pay. Watch it next to the MSME clock, not only next to a cash-flow target.
• Maverick spend. Spend with no PO, or off the contract you already signed, as a share of spend procurement can influence. See maverick spend.

Common P2P problems and controls

• Invoice before PO. Do not start the match. Raise the PO only if you would have approved the buy anyway, and mark it as after-the-fact so it stays visible.
• GRN copied from the PO. Stores should enter a counted quantity. A GRN that always equals the PO is not a control.
• One-line requisitions. Send them back. The buyer cannot source a specification that was never written.
• Approvers who do not open the tool. A limit that matches how the company actually decides is better than a perfect matrix nobody uses.
• WhatsApp as the system of record. A message can start a need. The PR, PO and GRN still have to exist, or the payment has no file.
• Paying to protect the 45-day clock. Pay what matched. Chase the rest. A bad invoice paid on time is still a bad invoice.

Manual vs automated procure to pay

On paper the eight steps are the same either way. Manually, each step is a different file: a form in stores, a sheet of quotes, a PO in the ERP, a GRN in a register, an invoice in a mailbox. Someone retypes the lines between them, and the retyping is where the quantity changes. Automation means the PO is created from the approved requisition, the GRN is booked against that PO, and the invoice is held when it does not match. It does not remove the need for a person to count the goods or to decide which quote is acceptable.

In an ERP the names are familiar: purchase requisition, purchase order, goods receipt, invoice verification, payment run. A tool in front of the ERP is doing the same cycle if a buyer can see one record from the request to the payment. If they have to export to Excel to know whether the GRN happened, the cycle is still manual.

Who should be able to see the open cycle

A procure to pay process that only the buyer can see will stall at the handoff. Stores needs the open PO before the truck arrives, or the GRN is written from the delivery challan and corrected later. Accounts needs the GRN before the invoice is due, or they either hold a correct bill or pay a wrong one. The requester needs to know the PO number, or they raise a second requisition for the same steel. None of that requires a new system. It requires that the PO number, the open quantity and the match exception are visible to those three people without an export.

If you are drawing the cycle for a new plant, start with those four documents — requisition, order, receipt, invoice — and name the person who creates each one. Add sourcing, approval and payment around them. A flowchart with twelve boxes and no names is a poster. A flowchart with four documents and an owner on each box is a process you can audit on Friday.

How Procupy handles this

Procupy keeps the procure to pay documents on one record. A person raises the requisition, the approval route runs on amount and role, and the purchase order goes to the vendor with the lines and the tax that were approved. Stores book the goods receipt against that PO. Accounts match the invoice to the order and the receipt before anyone is paid. A vendor can join a sourcing event from a link with a name and a phone number, and the price they win is the price on the PO. When a quantity is short or a payment is late, you are looking at that record, not at three inboxes.