Procurement Workflow for Organisations — PR, PO, GRN Explained
Published: April 4, 2026
Most organisations buy things. Fewer have a structured process for it. The result is predictable — purchases happen without proper approvals, invoices don't match what was ordered, and when the auditor arrives, there's no trail from "someone needed this" to "we paid for it and received it."
This article explains the three core documents in a procurement workflow — Purchase Requisition (PR), Purchase Order (PO), and Goods Receipt Note (GRN) — and how they connect to create an auditable, governed process.
1. The Three Documents
| Document | Who Creates It | Purpose |
|---|---|---|
| Purchase Requisition (PR) | Any employee | Formal request to procure something — specifies what, why, how many, and estimated cost |
| Purchase Order (PO) | Procurement team / manager | Instruction to a vendor — specifies agreed price, quantity, delivery terms, and payment terms |
| Goods Receipt Note (GRN) | Stores / receiving team | Confirmation that goods were physically received — specifies what arrived, in what quantity, and in what condition |
The flow is sequential: PR → PO → GRN. Each document requires approval before the next can be created. This is the governance chain — it ensures no purchase happens without authorization and no payment happens without confirmed receipt.
2. Purchase Requisition — The Starting Point
A purchase requisition is where the process begins. An employee identifies a need — equipment for a lab, stationery for a department, maintenance supplies — and raises a formal request.
A well-structured PR captures:
- What is being requested (item description, classification, specifications)
- How many units and estimated unit cost
- Which department and budget it falls under
- Why it's needed (justification)
Approval Governance
The PR then goes through an approval chain. Who approves depends on the organisation's rules — typically based on the department, the type of purchase, and the amount. A stationery request for Rs 5,000 might need only a department head's approval. A capital equipment purchase for Rs 50 lakhs might need the CFO and a procurement committee.
This is where an approval matrix becomes valuable. Instead of ad-hoc approvals via email or verbal nods, the system routes each PR to the right approvers based on configurable rules.
The approval matrix is the foundation of procurement governance. Without it, you have a process. With it, you have a governed process.
3. Purchase Order — The Commitment
Once a PR is approved, it becomes eligible for a Purchase Order. The PO is the organisation's formal commitment to a vendor — "we will buy these items at this price, and you will deliver by this date."
A PO typically includes:
- Vendor details (name, GSTIN, address)
- Line items inherited from the approved PR (description, quantity, agreed unit price)
- GST treatment (CGST/SGST for intra-state, IGST for inter-state)
- TDS applicability (Section 194C for contracts, 194Q for goods above threshold)
- Delivery terms, payment terms, and any special conditions
The PO itself goes through its own approval chain — because the actual vendor and price may differ from what was estimated in the PR. A PR might estimate Rs 10,000 per unit, but after vendor negotiation, the PO might be at Rs 9,500 or Rs 11,000. The PO approval ensures someone has reviewed the actual commercial terms.
4. Goods Receipt Note — The Confirmation
When goods arrive, the receiving team creates a GRN. This is the physical confirmation that what was ordered has actually arrived.
A GRN records:
- What was received (matched against PO line items)
- How many units arrived vs how many were ordered
- Condition on receipt (acceptable, damaged, wrong item)
- Gate entry details (if the organisation has a security/stores check)
Three-Way Matching
This is where invoice matching comes in. When the vendor sends an invoice, it's matched against three documents:
- PO: Did we order this at this price?
- GRN: Did we receive this quantity?
- Invoice: Is the vendor billing correctly?
Mismatches — quantity differences, price discrepancies, GST calculation errors — are flagged for resolution before payment. This prevents overpayment, duplicate payment, and payment for goods not received.
5. What Happens After GRN?
For capital items (fixed assets), the GRN triggers asset capitalisation — the item enters the fixed asset register with its cost, classification, location, and depreciation schedule. For consumables and inventory, it updates stock records.
If the organisation uses Tally for accounting, the GRN posting generates the corresponding accounting voucher — crediting the vendor, debiting the asset or expense account, and handling GST input credit.
6. Why This Structure Matters
Without this workflow, procurement typically happens through emails, verbal approvals, and retroactive documentation. The problems are predictable:
- Unauthorised purchases: No one approved it, but the goods arrived and the vendor expects payment.
- No price governance: Different departments buy the same item from different vendors at different prices. Nobody notices until an audit.
- Payment without receipt: Invoices are paid without confirming that goods were actually received and inspected.
- Audit findings: The auditor asks "show me the approval for this Rs 15 lakh purchase" and the answer is "the director told us verbally." This becomes a qualification in the audit report.
- Tax leakage: GST input credit is claimed on invoices that don't match the PO, or TDS isn't deducted where required.
7. Getting Started
Implementing a PR → PO → GRN workflow doesn't require replacing your entire ERP. The practical steps are:
- Map your current process: Who buys what? Who approves? How do goods get received today?
- Define your approval matrix: Which roles approve which types and amounts of purchases?
- Start with one department: Run the governed workflow for one department first. Expand after it's stable.
- Connect to accounting: Once the workflow is producing clean data, generate Tally vouchers from it instead of manual entry.
ProcureTrail supports this complete workflow — from PR creation and multi-level approval, through PO approval with GST/TDS handling, to GRN with gate entry and three-way matching. Vendor debit notes handle the mismatches. Tally integration handles the accounting.
8. Frequently Asked Questions
What is the PR, PO, GRN process in procurement?
PR (purchase requisition) is an internal request to buy something — it triggers an approval workflow. PO (purchase order) is the approved commitment sent to the vendor. GRN (goods receipt note) records what actually arrived. Together, the three documents create an auditable chain from request to delivery to payment.
How do purchase requisition, purchase order, and goods receipt note connect?
A purchase requisition is approved, then converted to a purchase order sent to the vendor. When goods arrive, a goods receipt note is raised against the PO to record what was received. Three-way matching compares PO, GRN, and vendor invoice before payment is authorised.
Why do Indian organisations need a PR → PO → GRN workflow?
Companies Act 2013 and CARO 2020 require documented internal financial controls over procurement. A structured PR → PO → GRN workflow produces the audit trail that proves who approved what, what was ordered, and what was received — evidence the statutory auditor asks for under Section 143(3)(i).
What is the difference between a purchase requisition and a purchase order?
A purchase requisition is an internal document requesting authorisation to buy something; it does not commit the organisation to any vendor. A purchase order is the approved external document sent to the vendor as a legal commitment. The requisition must be approved before the order can be issued.