Purchase Order vs Purchase Requisition vs Invoice: Complete Guide (2026)

A purchase requisition, a purchase order, and an invoice look similar on paper all three list items, quantities, and amounts. But they sit at three completely different stages of the buying cycle, get created by three different people, and carry three different levels of legal weight. Mixing them up is one of the most common and costly mistakes procurement and finance teams make.

If you've ever wondered why your finance team insists on a PO number before approving payment, or why an employee's request to "buy 10 laptops" isn't the same as a legally binding order, this guide breaks down exactly where each document fits, how they connect, and what happens when businesses skip one of them.

Quick Answer: What's the Difference?

• Purchase Requisition (PR): An internal request. An employee asks their organization for permission to buy something. It never leaves the company.
• Purchase Order (PO): An external document. Once the requisition is approved, the buyer sends this to the vendor to place the order. It becomes legally binding once the vendor accepts it.
• Invoice: A payment demand. The vendor sends this after delivering the goods or service, asking the buyer to pay.

In short: a requisition asks permission, a purchase order places the order, and an invoice asks for payment. One flow into the next a requisition doesn't go to a vendor, and a vendor never sees your internal approval trail, only the PO that comes out of it.

What Is a Purchase Requisition?

A purchase requisition is the starting point of any structured buying process. It's raised internally by an employee, a department head, or a project manager whenever the business needs to buy something it doesn't already have budget clearance for on a recurring basis.

Think of it as a formal version of asking your manager, "Can I buy this?" Before any vendor is contacted, before any price is finalized, the requisition exists purely to get internal sign-off.

What a Purchase Requisition Typically Includes

• Requester's name and department
• Description of the item or service needed
• Quantity and estimated cost
• Business justification (why this purchase is needed)
• Required delivery date
• Preferred or suggested vendor (if known)

Who Creates and Approves It

The requester creates it; a supervisor, department head, or budget owner approves it. Many Indian SMEs skip this step entirely for low-value purchases of office snacks, stationery but for anything crossing a spend threshold, a requisition is what stops one employee from single-handedly committing company money without oversight.

Why It Matters

Without a requisition stage, purchasing becomes a WhatsApp message and a hope that the invoice matches what was actually needed. A requisition creates the first checkpoint: it forces someone to justify the spend before a vendor is even contacted, which is the cheapest point in the entire cycle to catch an unnecessary or duplicate purchase.

What Is a Purchase Order?

Once a requisition is approved, the purchasing or procurement team converts it into a purchase order (PO) , the document that actually goes out to the vendor. This is where the internal request becomes an external commitment.

A PO specifies exactly what's being bought, at what price, in what quantity, and by when it needs to arrive. Once the vendor accepts it by signature, written confirmation, or simply by fulfilling the order it becomes a legally binding contract that both sides are expected to honor.

What a Purchase Order Typically Includes

• Unique PO number
• Issue date and expected delivery date
• Buyer and vendor contact details (in India, this includes GSTIN)
• Itemized list with SKU/HSN code, quantity, and unit price
• GST breakup (CGST/SGST/IGST) and total amount
• Payment terms (Net 30, advance, TDS applicability)
• Shipping and delivery instructions
• Authorized signatory or digital approval

Types of Purchase Orders

• Standard PO : one-time purchase with fixed quantity and price
• Blanket PO : recurring purchases from the same vendor over a period, with pricing locked in advance
• Planned PO : known items and pricing, but delivery is scheduled in stages
• Contract PO : a framework agreement setting terms for future orders without committing to specific quantities upfront

Why It Matters

A purchase order is the control point of the entire cycle. It's what finance teams reference during audits, what procurement teams track for outstanding commitments, and what accounts payable matches against the invoice before releasing payment. No PO usually means no accountability trail which is exactly where duplicate payments and disputed orders come from.

What Is an Invoice?

An invoice is issued by the vendor, not the buyer, and it comes after the goods or services have been delivered. Its only job is to request payment. Unlike a PO, an invoice by itself isn't a contract, it's a one-sided bill referencing the agreement that was already made through the PO.

What an Invoice Typically Includes

• Unique invoice number
• Reference to the original PO number
• Invoice date and payment due date
• Itemized goods/services delivered, with HSN/SAC codes
• GST breakup and total amount
• Payment terms and banking details
• TDS applicability (Section 194Q, where relevant)

Why It Matters

The invoice is where the transaction gets settled financially and it's also where mismatches surface. If the invoice quantity, price, or GST doesn't match the PO and the actual goods received, that's a red flag finance teams are trained to catch before releasing payment.

Side-by-Side Comparison: PR vs PO vs Invoice

How the Three Documents Connect: The Full Flow

These three documents aren't independent; they're sequential checkpoints in the same process, and each one exists to validate the one before it.

• Need identified : An employee or department recognizes a purchase need and raises a purchase requisition.
• Internal approval : A supervisor or budget owner reviews and approves the requisition based on budget and necessity.
• PO creation : Procurement converts the approved requisition into a purchase order, adds vendor details, pricing, and GST/HSN information, and sends it to the vendor.
• Vendor acceptance : The vendor confirms the PO, making it a binding agreement.
• Fulfillment : The vendor delivers the goods or completes the service.
• Invoice issued : The vendor sends an invoice referencing the original PO number, requesting payment.
• 3-way matching : Finance checks the invoice against the PO and the goods receipt note (GRN) before approving payment.
• Payment released : Once everything matches, payment goes out per the agreed terms.

Skip the requisition, and you lose internal oversight before money gets committed. Skip the PO, and you lose the legal and pricing safeguard before goods are even ordered. Skip matching the invoice against both, and you're paying on trust alone.

Do You Really Need All Three? A Decision Framework

Not every purchase needs the full three-document chain, forcing it everywhere just adds friction. Here's how most well-run finance teams draw the line:

Skip the formal chain when:

• The purchase is low-value and non-recurring (office snacks, a single stationery order)
• It falls under a pre-approved petty cash or discretionary spend limit
• It's an emergency purchase with no time for routing (though it should still be logged after the fact)

Use a requisition + PO, but relax on formality when:

• The vendor is a known, repeat supplier and pricing is pre-negotiated (a blanket PO can cover months of releases without a fresh requisition each time)

Enforce the full requisition → PO → invoice → 3-way match chain when:

• The purchase crosses your company's defined spend threshold
• It involves a new vendor you haven't transacted with before
• GST input tax credit is being claimed on the purchase (a PO with correct HSN/SAC codes makes GSTR reconciliation dramatically easier)
• The purchase is for capital goods, bulk raw material, or anything with audit exposure

The real question isn't "should we always use all three" it's "how much risk does this specific purchase carry, and does the paperwork match that risk." A ₹500 stationery order and a ₹5 lakh raw material order shouldn't go through the identical process.

Why This Matters More for Indian Businesses

Generic global guides on this topic rarely mention what actually trips up Indian SMEs: GST compliance.

When a purchase order is raised without HSN/SAC codes, or when the requisition-to-PO-to-invoice trail is broken, it doesn't just create an internal accounting headache it directly complicates GSTR reconciliation and can hold up input tax credit (ITC) claims. Under Section 194Q, TDS applicability on purchases above the threshold also needs to be tracked consistently from the PO stage through to the invoice, not bolted on at the end.

This is where most manual, spreadsheet-based systems fall apart: a requisition raised in one email thread, a PO drafted in Word, and an invoice that arrives with mismatched GST fields. None of these gaps show up until it's time to file returns and by then, they're expensive to fix.

The Cost of Getting This Wrong

Businesses that treat these three documents as interchangeable or skip stages entirely tend to run into the same problems repeatedly:

• Duplicate payments : without a PO to check against, the same invoice can slip through twice
• Maverick spending : purchases made without requisition approval bypass budget control entirely
• ITC mismatches : missing or incorrect HSN/GSTIN details on the PO create reconciliation errors months later
• Vendor disputes : no PO means no agreed pricing to point to when a vendor's invoice comes in higher than expected
• Audit gaps : auditors specifically look for a complete requisition-to-payment trail; a missing link anywhere raises flags

Best Practices for Managing All Three Together

1. Standardize templates across departments. A requisition form and PO format that stays identical no matter who raises it removes ambiguity when it's time to match documents.
2. Set requisition thresholds, not blanket rules. Require formal requisitions only above a defined spend limit; let low-value purchases move faster.
3. Never let a PO get created without an approved requisition for anything above your threshold; this is the control point that prevents unauthorized spend.
4. Always reference the PO number on the invoice. This single habit is what makes 3-way matching possible at all.
5. Build GST fields into the requisition and PO stage, not just the invoice. Retrofitting HSN/SAC codes after the fact is where most reconciliation errors originate.
6. Automate the matching, not just the document creation. Manually cross-checking requisition, PO, and invoice line-by-line doesn't scale past a handful of monthly purchases.

How ZYNO Expenz Brings All Three Together

Manually juggling requisition approvals in one tool, purchase orders in another, and invoice matching in a spreadsheet is exactly how gaps creep in. ZYNO Expenz, Elite Mindz's AI-powered expense and purchase management platform built for Indian SMEs, keeps requisitions, GST-ready purchase orders, and invoice matching inside a single connected workflow with configurable approval thresholds so low-value requests move fast while larger purchases get the scrutiny they need.

Instead of chasing down which requisition led to which PO led to which invoice, teams get a live trail from the first request through to final payment, with automatic 3-way matching against goods receipt notes.

Frequently Asked Questions

Q1. What is the difference between a purchase requisition and a purchase order?
A purchase requisition is an internal request for approval to buy something; it never goes to a vendor. A purchase order is the external document sent to the vendor once that request is approved, and it becomes legally binding once accepted.

Q2. What is the difference between a purchase order and an invoice?
A purchase order is issued by the buyer before delivery to place an order. An invoice is issued by the vendor after delivery to request payment. A PO authorizes a purchase; an invoice bills for it.

Q3. Which document comes first requisition, PO, or invoice?
The purchase requisition always comes first, followed by the purchase order once approved, and finally the invoice once the vendor delivers the goods or service.

Q4. Is a purchase requisition legally binding?
No. A requisition is purely an internal approval document. It creates no obligation to any vendor. Only the purchase order, once accepted by the vendor, becomes legally binding.

Q5. Can a business skip the purchase requisition step?
Yes, for low-value or routine purchases many businesses skip formal requisitions and go straight to a PO or even a direct invoice. For higher-value or first-time vendor purchases, skipping this step removes an important internal control.

Q6. What is 3-way matching?
3-way matching is the process of checking the purchase order, the goods receipt note (GRN), and the vendor's invoice against each other before releasing payment ensuring what was ordered, received, and billed all align.

Q7. Why is the PO number important on an invoice?
The PO number is what allows the buyer's finance team to trace the invoice back to the original approved order, making 3-way matching and GST reconciliation possible. An invoice without a PO reference takes significantly longer to verify and process.

Q8. Do small businesses in India need all three documents?
Even small businesses benefit once they're dealing with multiple vendors or recurring purchases. Beyond internal control, having a proper requisition-to-PO-to-invoice trail with correct HSN/SAC codes keeps GST input tax credit claims clean and audit-ready something informal WhatsApp or verbal orders simply can't provide.

Conclusion

A purchase requisition, a purchase order, and an invoice aren't three versions of the same document they're three distinct checkpoints, each catching a different kind of risk. The requisition stops unauthorized spend before it starts. The PO locks in pricing and terms before goods move. The invoice, matched properly against both, is what confirms you're paying for exactly what was ordered and received.

For Indian businesses, getting this chain right also means building GST, HSN/SAC, and TDS compliance into the process from the requisition stage onward not fixing it at reconciliation time. Whether you're running a handful of purchases a month or managing hundreds across departments, the fix is the same: standardized documents, clear thresholds for when each one is required, and a system like ZYNO Expenz that connects all three instead of tracking them separately