If you have ever waited on a vendor to deliver the right quantity at the agreed price, only to find a mismatch at the receiving dock or in the final bill, you already know why purchase orders exist. For an Indian SME buying raw material, packaging, or components from multiple suppliers, an informal “please send 500 units” phone call or WhatsApp message rarely holds up when there’s a price dispute or a tax reconciliation to do later.
This article explains what a purchase order is, the main types businesses use, what an Indian PO format typically includes, and how GST-related information such as GSTIN and HSN/SAC fits into that format — while keeping the PO clearly distinct from the vendor’s GST tax invoice. It also covers whether a PO is mandatory, and how it connects to GRN and invoicing in the wider procurement process.
A purchase order (PO) is a formal document a buyer sends to a vendor to order specific goods or services at an agreed price, quantity, and delivery schedule. It documents the purchase and becomes an important reference for receiving goods, matching invoices, and tracking procurement. A PO is not a GST tax invoice — that is a separate document the vendor issues under GST law.
- A purchase order is a buyer-issued document that formally requests goods or services from a vendor at agreed terms.
- Businesses use POs to control spending, give vendors clear instructions, and create a reference point for receiving and invoice matching.
- The four common PO types are standard, blanket, planned, and contract purchase orders, each suited to different buying patterns.
- A PO connects to the wider procurement flow: requisition → approval → PO → GRN → invoice → payment.
- Indian POs commonly reference GSTIN and HSN/SAC for planning purposes, but the prescribed GST particulars apply to the tax invoice, not the purchase order.
- What Is a Purchase Order?
- Why Do Businesses Use Purchase Orders?
- What Are the Different Types of Purchase Orders?
- What Should a Purchase Order Include?
- What GST Considerations Apply to a Purchase Order in India?
- Is a Purchase Order Mandatory in India?
- How Does a Purchase Order Fit Into the Procurement Process?
- Purchase Order vs Invoice vs GRN
- When Should a Business Start Using Formal Purchase Orders?
- When Manual Purchase Orders Start Becoming Difficult
- FAQ
- Conclusion
What Is a Purchase Order?
A purchase order is a document a buyer creates and sends to a vendor to formally order goods or services. It states what is being bought, how much, at what price, and by when it should be delivered.
The buyer is the business placing the order — for example, a manufacturing SME that needs raw material. The vendor (or supplier) is the business fulfilling that order. Once a vendor accepts a PO, that acceptance may form part of the commercial agreement between the parties, depending on the terms agreed and applicable contract law — the exact legal effect can vary by situation, so businesses with specific contractual questions should check with a qualified professional.
Example scenario: Consider a hypothetical Indian manufacturing SME — call it a small components manufacturer in Pune — that needs 500 kg of a specific grade of steel sheet from a regular vendor. Instead of relying on a phone call, the purchase manager issues a purchase order specifying the item, quantity, agreed rate, delivery location, and expected delivery date. This becomes the reference document for everyone involved: the vendor, the receiving team, and accounts.
A typical PO establishes:
- Buyer — the business placing the order
- Vendor/supplier — the business fulfilling it
- Product or service — what is being purchased
- Quantity — how much is being ordered
- Agreed price — the rate per unit and total value
- Delivery terms — where and when goods should arrive
- Payment terms — when and how the vendor will be paid
Why Do Businesses Use Purchase Orders?
Purchase orders solve a practical problem: without a written record, procurement relies on memory, verbal agreements, or scattered emails. This creates room for price disagreements, wrong quantities, and confusion during payment.
A PO gives a business several concrete benefits:
- Purchase authorization. It shows that someone with the right authority approved the spend, rather than an ad-hoc order.
- Clear vendor instructions. The vendor knows exactly what to supply, at what price, and by when — reducing back-and-forth.
- Documented quantity and price. Both sides agree to the same numbers before goods move, which limits disputes later.
- Procurement control. Finance and purchase teams can track what has been ordered but not yet received (open POs).
- Receiving reference. The warehouse or stores team checks incoming goods against the PO quantity and item details.
- Invoice reconciliation. Accounts can compare the vendor’s bill against what was actually ordered and received.
- Audit trail. A dated, numbered PO record supports internal audits and helps explain historical purchasing decisions.
This is about the value of the document itself, not a particular software tool. Even a business using spreadsheets or a simple template gets these benefits once POs become a consistent practice.
What Are the Different Types of Purchase Orders?
Not every purchase follows the same pattern. Businesses typically use one of four common PO types, depending on how predictable and repetitive the purchase is.
Standard Purchase Order
This is a one-time order for a specific quantity of goods or services, at a fixed price, for a defined delivery date. It’s the most common type and suits occasional or non-repeating purchases.
Example: The Pune manufacturing SME orders 500 kg of steel sheet as a single, defined purchase.
Blanket Purchase Order
A blanket PO covers multiple deliveries of the same item over a period, under pre-agreed pricing and terms, without creating a new PO for every delivery. It suits vendors supplying the same item repeatedly.
Example: The same SME agrees with its steel vendor to draw up to 5,000 kg over the quarter, releasing smaller quantities as needed, without renegotiating price each time.
Planned Purchase Order
A planned PO specifies expected quantities and tentative delivery schedules in advance, but the exact release dates or amounts may still be confirmed closer to the actual need. It helps with forecasting while retaining some flexibility.
Example: The SME plans monthly steel deliveries for the next two quarters based on projected production, with exact release dates confirmed each month.
Contract Purchase Order
A contract PO is tied to a broader agreement — often covering pricing, terms, and conditions negotiated over a longer period — and is used to formalize individual purchases under that contract.
Example: The SME signs an annual supply agreement with its steel vendor covering rates and quality terms, then issues contract POs against it for specific batches.
PO Type Comparison Table
| PO Type | What It Means | Best Use | Example |
|---|---|---|---|
| Standard PO | One-time order with fixed quantity, price, and delivery date | Occasional or non-repeating purchases | Ordering 500 kg of steel sheet as a single order |
| Blanket PO | Covers multiple deliveries of the same item at pre-agreed terms | Repeat purchases from the same vendor | Drawing steel in smaller lots over a quarter |
| Planned PO | Forecasted quantities and tentative schedule, confirmed closer to need | Businesses forecasting demand but needing flexibility | Planning monthly deliveries based on projected production |
| Contract PO | Individual order issued under a broader negotiated agreement | Long-term vendor relationships with negotiated terms | Issuing batch-wise POs under an annual supply agreement |
What Should a Purchase Order Include?
A well-structured PO reduces confusion for both the vendor and the buyer’s own teams. While exact formats vary by business and industry, most Indian purchase orders group information into a few clear sections.
Buyer information
The buyer’s legal or trade name, address, and contact details, so the vendor knows exactly who is ordering.
Supplier information
The vendor’s name, address, and contact details, confirming who is expected to fulfil the order.
PO identification
A unique PO number and PO date. The number lets both sides reference the order in emails, GRNs, and invoices without ambiguity.
Product/service information
A clear description of what is being ordered — including specifications, model, or grade where relevant — so the vendor supplies the correct item.
Quantity and pricing
The quantity ordered, unit price, and total order value. This is the figure both sides will later check the invoice against.
Delivery information
Where the goods should be delivered and the expected delivery date. This helps the receiving team plan and gives the vendor a clear deadline.
Payment terms
When payment will be made — for example, a fixed number of days after delivery or invoice — set out so there’s no ambiguity at settlement time.
Tax-related information (optional, business practice)
Businesses may choose to reference GSTIN, HSN/SAC, and indicative CGST, SGST, or IGST information on their PO as part of their procurement and reconciliation process. This is a business practice rather than a legal requirement for the PO itself — the particulars actually prescribed for GST purposes apply to the vendor’s tax invoice under GST rules, not to the purchase order. Including this information on the PO simply helps both sides align on expected tax treatment before the vendor bills the transaction.
Approval/authorization information
Many businesses include an approver name or signature line on the PO, reflecting internal purchase authorization — this is a business control, not a government requirement.
It’s worth being clear that none of the fields above are mandated by GST law for a purchase order. Indian GST rules do not prescribe a fixed format for POs; they prescribe the particulars for the tax invoice instead (covered in the next section). What’s listed here reflects common, sensible business practice for a document that needs to be clear, traceable, and useful for later reconciliation.
The visual above shows a single-page PO for the Pune-based manufacturing SME example, purchasing steel sheet from a regular vendor, with numbered callouts marking:
- Buyer details (company name, address, GSTIN)
- PO number and PO date
- Vendor details (company name, address, GSTIN)
- Delivery address and expected delivery date
- Item description, HSN code, quantity, and pricing
- Indicative CGST/SGST or IGST reference
- Payment terms
- Authorized signatory
- A clarifying note that the PO is not a GST tax invoice
This layout mirrors what a finance or procurement executive at an Indian SME would typically see or need to create, grouping commercial details, delivery details, and tax-reference details into clearly separated sections rather than one dense block of text.
What GST Considerations Apply to a Purchase Order in India?
This is one of the most misunderstood areas of Indian procurement documentation, so it’s worth being precise about what each document is and isn’t.
Three separate documents, three separate roles:
Purchase order
the buyer’s commercial ordering document, created before the supply happens
GRN (Goods Receipt Note)
the buyer’s internal record of what was actually received
Tax invoice
the vendor’s legal GST billing document, governed by GST law
A purchase order is not the same document as a GST tax invoice.
Under Section 31 of the CGST Act, a registered supplier must issue a tax invoice in the circumstances specified by the Act, and Rule 46 sets out the prescribed particulars of a tax invoice, including supplier details, GSTIN, invoice number and date, HSN/SAC-related information, description, quantity where applicable, value, tax rate, tax amount and other prescribed information.
These provisions govern the tax invoice; they do not prescribe a universal purchase-order format.
A business may choose to include GST-related reference information such as GSTIN, HSN/SAC and indicative tax information on its PO to communicate expected commercial treatment and support reconciliation. However, including this information does not make the PO a GST tax invoice or replace the prescribed tax documentation.
The applicable GST treatment depends on the nature and circumstances of the supply and the relevant GST provisions. Businesses should verify current requirements against official GST sources or a qualified tax professional when making a compliance decision.
Is a Purchase Order Mandatory in India?
There is no GST or company-law provision that requires every Indian business to issue a purchase order for every purchase. In that narrow legal sense, a PO is generally not mandatory the way a GST tax invoice is for a registered supplier. Whether a business needs one in practice depends on a different set of factors — legal, contractual, and internal:
- Legal requirement: Generally, no general law compels a PO for a standard commercial purchase. (Specific industries, government procurement, or particular contracts may have their own rules — check the applicable regulation if relevant to your situation.)
- Contractual requirement: Many vendors, especially larger ones or those supplying under a formal agreement, will refuse to process an order — or delay invoicing — without a PO reference, because it’s built into their own billing workflow. Here, the PO becomes necessary by agreement, not by statute.
- Internal procurement control: Businesses that want spending approved before it happens, rather than discovered after the invoice arrives, use POs as an internal control, independent of any external legal requirement.
- Business practice: In many industries, especially manufacturing, trading, and distribution, issuing a PO is simply standard commercial practice, expected by both buyers and vendors.
In short: a PO is rarely a strict legal requirement on its own, but it is often a practical, contractual, or internal-control necessity. This is general information, not legal advice — businesses with specific compliance questions should consult a qualified professional.
How Does a Purchase Order Fit Into the Procurement Process?
A purchase order is one step within a broader procurement flow. Here’s how it typically connects to the steps before and after it:
- Purchase Requisition: An internal request — for example, from a production or stores team — flagging that an item needs to be bought.
- Approval: The requisition is reviewed and approved by whoever holds purchasing authority, before any commitment is made to a vendor.
- Purchase Order: Once approved, the PO is created and sent to the chosen vendor, formalizing the order.
- Goods Receipt / GRN: When goods arrive, the receiving team records what was actually delivered against the PO.
- Supplier Invoice: The vendor bills the buyer, referencing the PO and/or GRN.
- Reconciliation / Payment: Accounts checks the PO, GRN, and invoice against each other before releasing payment.)
Purchase Order vs Invoice vs GRN
These three documents are often confused, but each serves a distinct role in the same transaction.
| Document | Created By | Main Purpose | When Used |
|---|---|---|---|
| Purchase Order | Buyer | States what is being ordered, at what price and terms | Before goods are supplied |
| GRN (Goods Receipt Note) | Buyer | Records what was actually received | When goods physically arrive |
| Invoice | Vendor/Supplier | Bills the buyer for goods or services supplied, under GST rules | At or after delivery |
In short: the PO records what was ordered, the GRN records what was actually received, and the invoice records what the supplier is billing for. Comparing all three — often called three-way matching — helps catch mismatches in quantity, price, or tax details before payment is released.
This article only covers the essentials of that relationship.
When Should a Business Start Using Formal Purchase Orders?
Many small businesses start out managing purchases informally, and that can work fine at low volumes. Certain signs typically indicate it’s time to formalize the process.
| Sign You’re Seeing | Why It Points to Formal POs |
|---|---|
| Purchase volume is increasing month over month | Harder to track spend and commitments from memory alone |
| Multiple vendors supply similar items | A written order avoids confusion about who agreed to what |
| The same items are reordered repeatedly | A blanket or planned PO can reduce repetitive paperwork |
| Price disputes with vendors are becoming frequent | A documented, agreed price prevents after-the-fact disagreements |
| Quantity discrepancies show up on delivery | A PO gives the receiving team a clear quantity to check against |
| Approvals happen after spending, not before | A PO built on an approved requisition enforces authorization upfront |
| The business now operates across multiple locations | A consistent PO format keeps purchasing comparable across sites |
| It’s hard to track which orders are still open | A numbered PO record makes open orders visible and searchable |
| Invoice amounts don’t match what was received | A PO-GRN-invoice check catches mismatches before payment |
None of these signs mean a business must adopt any specific tool. They simply indicate that a documented PO process — even a simple one — would likely reduce errors and disputes compared to informal ordering.
When Manual Purchase Orders Start Becoming Difficult
Once a business does move to formal POs, many run this process manually at first — using spreadsheets, email chains, and printed forms. This works, but it tends to strain as volume grows:
- Spreadsheet-based PO logs become hard to keep updated and version-controlled
- Email approvals are slow to track and easy to lose in busy inboxes
- Duplicate POs get created when there’s no single shared record
- Records go missing across different people’s inboxes and folders
- Purchase managers and finance heads lack real-time visibility into open orders
- Reconciling POs, GRNs, and invoices by hand takes significant manual effort each month
These are common friction points as purchasing scales, not universal problems every business will face. For SMEs with a handful of vendors and low order volume, spreadsheets may remain entirely workable for some time.
For businesses that have outgrown manual tracking, the next step is usually procurement software that connects purchasing, approvals, receiving, and reporting in one place.
Practical ERP Implementation Note
Businesses moving from manual to system-based PO management commonly run into a few recurring setup issues — incomplete or outdated vendor master data, inconsistent product/item naming across teams, unclear or undefined approval hierarchies, a backlog of old “open” POs that were never formally closed, and GRN quantities that don’t match PO quantities due to partial deliveries. These are common implementation issues to plan for, not guaranteed outcomes, and addressing them early tends to make the transition to a formal PO system smoother.
Original Information Asset / Framework
How a Purchase Order Connects to Other Procurement Data
A purchase order rarely stands alone — it links to several categories of information that together make up a business’s procurement record:
- Core commercial details: buyer, vendor, product/service, quantity, price, delivery terms, payment terms
- Tax-related reference (business practice, not a PO legal requirement): GSTIN, HSN/SAC, CGST, SGST, IGST — included for planning and reconciliation, with the actual GST particulars governed by the vendor’s tax invoice under Rule 46
- Process linkage: purchase requisition → approval → PO → GRN → invoice → payment
- Business purpose: purchase control, vendor communication, budget control, receiving reference, and reconciliation
Some procurement systems document this same lifecycle end to end. Shivaizer’s Purchase Management module, for example, documents the flow as Purchase Requisition (PR) → RFQ → Purchase Order (PO) → Goods Receipt Note (GRN) → Vendor Bill → Payment Voucher → Vendor Adjustment. Within that flow, its documented capabilities include:
- PR-linked PO creation, where item details, quantity, and a suggested vendor are pulled from an approved requisition
- Manual/direct PO creation for ad-hoc purchases that don’t originate from a requisition
- Configurable PO approval workflows, with a documented status flow of Submitted → Pending Approval → Approved → Sent to Vendor
- GRN recorded against an approved PO, supporting both partial and complete delivery
- Vendor bill booking against the PO, the GRN, or directly
- An audit trail across procurement and vendor-financial transactions
This is a description of one product’s documented capability, not a claim about what every business needs — smaller operations may not require this level of system support at all, and none of these capabilities should be read as a GST or legal compliance certification.
FAQ
What is a purchase order?
A purchase order is a document a buyer sends to a vendor to formally request specific goods or services, stating the quantity, price, delivery terms, and payment terms agreed for that order.
What is a purchase order used for?
It’s used to authorize spending, give the vendor clear instructions, create a reference for receiving goods, and support invoice reconciliation and audit tracking later in the process.
Is a purchase order mandatory in India?
There’s no general GST or legal requirement to issue a PO for every purchase. However, many vendors require one contractually, and most businesses use POs as an internal purchasing control regardless of legal obligation.
Is GST applicable to a purchase order?
GST is legally charged and documented through the vendor’s tax invoice under Section 31 of the CGST Act, not the purchase order. A PO may reference GSTIN, HSN/SAC, and an indicative CGST/SGST/IGST breakup for planning, but it remains a commercial ordering document rather than a tax invoice.
What information should an Indian purchase order contain?
Typically buyer and vendor details, a PO number and date, item description, quantity and price, delivery and payment terms, and — as a matter of business practice — GSTIN, HSN/SAC, and tax reference details for the items ordered.
What is the difference between a purchase order and an invoice?
A purchase order is created by the buyer to state what is being ordered, before supply happens. An invoice is created by the vendor to bill the buyer, at or after delivery, and is the document that carries the legally prescribed GST particulars.
Conclusion
A purchase order is the buyer’s formal record of what was ordered, from whom, at what price, and on what terms. Businesses use it to control spending, give vendors clear instructions, and create a reliable reference point for receiving goods and checking invoices. Depending on buying patterns, that might mean a standard, blanket, planned, or contract PO — and a well-structured Indian PO format commonly includes GSTIN, HSN/SAC, and tax reference details as a matter of practice, even though the prescribed GST particulars themselves belong to the vendor’s tax invoice. As purchase volume and vendor count grow, moving from informal ordering to a consistent, documented PO process becomes genuinely useful for avoiding disputes and keeping reconciliation manageable.
Call to Action
If you are still managing purchase orders manually, the next step depends on your business stage. Smaller teams can start with a structured PO template, while growing procurement teams may benefit from software that connects purchasing, approvals, receiving, and reporting.