{"id":430,"date":"2026-08-25T12:13:19","date_gmt":"2026-08-25T12:13:19","guid":{"rendered":"https:\/\/shivit.com\/blog\/?p=430"},"modified":"2026-08-25T12:15:23","modified_gmt":"2026-08-25T12:15:23","slug":"what-is-purchase-order-types-format-gst-india","status":"publish","type":"post","link":"https:\/\/shivit.com\/blog\/index.php\/2026\/08\/25\/what-is-purchase-order-types-format-gst-india\/","title":{"rendered":"What Is a Purchase Order? Types, Format &amp; GST Considerations in India"},"content":{"rendered":"\n<style>\n  .shivit-blog-byline {\n    display: flex;\n    align-items: center;\n    flex-wrap: wrap;\n    gap: 10px 18px;\n    margin: 18px 0 34px;\n    padding: 14px 18px;\n    border: 1px solid #dfe6ef;\n    border-radius: 10px;\n    background: #f7faff;\n    color: #667085;\n    font-family: Inter, -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto, Arial, sans-serif;\n    font-size: 14px;\n    line-height: 1.5;\n  }\n\n  .shivit-blog-byline-item {\n    display: inline-flex;\n    align-items: center;\n    gap: 7px;\n  }\n\n  .shivit-blog-byline-label {\n    color: #172033;\n    font-weight: 650;\n  }\n\n  .shivit-blog-byline-divider {\n    width: 1px;\n    height: 18px;\n    background: #dfe6ef;\n  }\n\n  @media (max-width: 600px) {\n    .shivit-blog-byline {\n      align-items: flex-start;\n      flex-direction: column;\n      gap: 7px;\n      margin: 16px 0 28px;\n      padding: 14px 16px;\n    }\n\n    .shivit-blog-byline-divider {\n      display: none;\n    }\n  }\n<\/style>\n\n<div class=\"shivit-blog-byline\">\n  <span class=\"shivit-blog-byline-item\">\n    <span class=\"shivit-blog-byline-label\">Researched and reviewed by<\/span>\n    <span>Shivit Technologies Editorial Team<\/span>\n  <\/span>\n\n  <span class=\"shivit-blog-byline-divider\" aria-hidden=\"true\"><\/span>\n\n  <span class=\"shivit-blog-byline-item\">\n    <span class=\"shivit-blog-byline-label\">Last updated:<\/span>\n    <span>August 25, 2026<\/span>\n  <\/span>\n<\/div>\n\n\n\n<style>\n  .shivit-blog-section {\n    --shivit-blog-blue: #1769e0;\n    --shivit-blog-blue-dark: #0f3f8c;\n    --shivit-blog-navy: #172033;\n    --shivit-blog-text: #3f4a5a;\n    --shivit-blog-muted: #667085;\n    --shivit-blog-border: #dfe6ef;\n    --shivit-blog-surface: #f7faff;\n    --shivit-blog-white: #ffffff;\n    --shivit-blog-radius: 14px;\n    --shivit-blog-shadow: 0 8px 28px rgba(20, 48, 87, 0.06);\n\n    max-width: 1160px;\n    margin: 0 auto;\n    padding: 12px 20px 56px;\n    color: var(--shivit-blog-text);\n    font-family: Inter, -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto, Arial, sans-serif;\n    font-size: 17px;\n    line-height: 1.75;\n    box-sizing: border-box;\n  }\n\n  .shivit-blog-section *,\n  .shivit-blog-section *::before,\n  .shivit-blog-section *::after {\n    box-sizing: border-box;\n  }\n\n  .shivit-blog-section h2,\n  .shivit-blog-section h3,\n  .shivit-blog-section p,\n  .shivit-blog-section ul,\n  .shivit-blog-section table {\n    margin-top: 0;\n  }\n\n  .shivit-blog-section h2 {\n    margin: 64px 0 24px;\n    color: var(--shivit-blog-navy);\n    font-size: clamp(28px, 3vw, 38px);\n    line-height: 1.2;\n    letter-spacing: -0.025em;\n    font-weight: 750;\n  }\n\n  .shivit-blog-section h3 {\n    margin: 42px 0 14px;\n    color: var(--shivit-blog-navy);\n    font-size: clamp(21px, 2vw, 26px);\n    line-height: 1.3;\n    letter-spacing: -0.015em;\n    font-weight: 700;\n  }\n\n  .shivit-blog-section p {\n    margin-bottom: 22px;\n  }\n\n  .shivit-blog-section ul {\n    margin: 0 0 30px;\n    padding: 0;\n    list-style: none;\n  }\n\n  .shivit-blog-section li {\n    position: relative;\n    margin: 0 0 13px;\n    padding-left: 26px;\n  }\n\n  .shivit-blog-section li::before {\n    content: \"\";\n    position: absolute;\n    left: 3px;\n    top: 0.82em;\n    width: 7px;\n    height: 7px;\n    border-radius: 50%;\n    background: var(--shivit-blog-blue);\n    transform: translateY(-50%);\n  }\n\n  .shivit-blog-intro {\n    margin-bottom: 52px;\n  }\n\n  .shivit-blog-quick-answer {\n    margin: 34px 0 42px;\n    padding: 28px 30px;\n    border: 1px solid #cfe0f7;\n    border-left: 4px solid var(--shivit-blog-blue);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-surface);\n  }\n\n  .shivit-blog-label {\n    display: inline-block;\n    margin-bottom: 14px;\n    color: var(--shivit-blog-blue-dark);\n    font-size: 13px;\n    line-height: 1.4;\n    font-weight: 750;\n    letter-spacing: 0.08em;\n    text-transform: uppercase;\n  }\n\n  .shivit-blog-quick-answer p {\n    margin-bottom: 0;\n  }\n\n  .shivit-blog-takeaways,\n  .shivit-blog-toc {\n    margin: 42px 0;\n    padding: 28px 30px;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-white);\n    box-shadow: var(--shivit-blog-shadow);\n  }\n\n  .shivit-blog-takeaways ul,\n  .shivit-blog-toc ul {\n    margin-bottom: 0;\n  }\n\n  .shivit-blog-toc li {\n    margin-bottom: 10px;\n  }\n\n  .shivit-blog-toc li::before {\n    width: 5px;\n    height: 5px;\n    background: #91a6c2;\n  }\n\n  .shivit-blog-section-divider {\n    width: 100%;\n    height: 1px;\n    margin: 58px 0 8px;\n    background: var(--shivit-blog-border);\n  }\n\n  .shivit-blog-article-heading {\n    margin-top: 58px !important;\n    padding-top: 4px;\n  }\n\n  .shivit-blog-info-card {\n    margin: 28px 0 34px;\n    padding: 25px 28px;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: #fbfcfe;\n  }\n\n  .shivit-blog-info-card p:last-child {\n    margin-bottom: 0;\n  }\n\n  .shivit-blog-type-grid {\n    display: grid;\n    grid-template-columns: repeat(2, minmax(0, 1fr));\n    gap: 18px;\n    margin: 30px 0 42px;\n  }\n\n  .shivit-blog-type-card {\n    padding: 24px 25px;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-white);\n    box-shadow: var(--shivit-blog-shadow);\n  }\n\n  .shivit-blog-type-card h3 {\n    margin: 0 0 13px;\n    color: var(--shivit-blog-blue-dark);\n    font-size: 22px;\n  }\n\n  .shivit-blog-type-card p {\n    margin-bottom: 18px;\n  }\n\n  .shivit-blog-type-card p:last-child {\n    margin-bottom: 0;\n  }\n\n  .shivit-blog-table-wrap {\n    width: 100%;\n    margin: 30px 0 48px;\n    overflow-x: auto;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-white);\n    box-shadow: var(--shivit-blog-shadow);\n    -webkit-overflow-scrolling: touch;\n  }\n\n  .shivit-blog-table {\n    width: 100%;\n    min-width: 820px;\n    border-collapse: separate;\n    border-spacing: 0;\n    color: var(--shivit-blog-text);\n    font-size: 15px;\n    line-height: 1.55;\n  }\n\n  .shivit-blog-table th {\n    padding: 17px 18px;\n    color: var(--shivit-blog-white);\n    background: var(--shivit-blog-blue-dark);\n    text-align: left;\n    vertical-align: top;\n    font-size: 14px;\n    line-height: 1.4;\n    font-weight: 700;\n    border-right: 1px solid rgba(255,255,255,0.16);\n  }\n\n  .shivit-blog-table th:last-child {\n    border-right: 0;\n  }\n\n  .shivit-blog-table td {\n    padding: 18px;\n    vertical-align: top;\n    border-top: 1px solid var(--shivit-blog-border);\n    border-right: 1px solid var(--shivit-blog-border);\n    background: var(--shivit-blog-white);\n  }\n\n  .shivit-blog-table td:last-child {\n    border-right: 0;\n  }\n\n  .shivit-blog-table tbody tr:nth-child(even) td {\n    background: #f8faff;\n  }\n\n  .shivit-blog-table tbody tr:first-child td {\n    border-top: 0;\n  }\n\n  .shivit-blog-table td:first-child {\n    color: var(--shivit-blog-navy);\n    font-weight: 700;\n  }\n\n  .shivit-blog-section .shivit-blog-main-copy {\n    margin-bottom: 26px;\n  }\n\n  @media (max-width: 760px) {\n    .shivit-blog-section {\n      padding: 8px 17px 42px;\n      font-size: 16px;\n      line-height: 1.7;\n    }\n\n    .shivit-blog-section h2 {\n      margin-top: 44px;\n      margin-bottom: 20px;\n      font-size: 29px;\n    }\n\n    .shivit-blog-section h3 {\n      margin-top: 34px;\n      font-size: 22px;\n    }\n\n    .shivit-blog-quick-answer,\n    .shivit-blog-takeaways,\n    .shivit-blog-toc,\n    .shivit-blog-info-card {\n      padding: 22px 20px;\n    }\n\n    .shivit-blog-type-grid {\n      grid-template-columns: 1fr;\n      gap: 15px;\n      margin-top: 24px;\n    }\n\n    .shivit-blog-type-card {\n      padding: 21px 20px;\n    }\n\n    .shivit-blog-table-wrap {\n      margin-top: 24px;\n      border-radius: 11px;\n    }\n\n    .shivit-blog-table {\n      min-width: 760px;\n      font-size: 14px;\n    }\n\n    .shivit-blog-table th,\n    .shivit-blog-table td {\n      padding: 14px;\n    }\n\n    .shivit-blog-section-divider {\n      margin: 44px 0 4px;\n    }\n  }\n\n  @media (max-width: 420px) {\n    .shivit-blog-section {\n      padding-left: 16px;\n      padding-right: 16px;\n    }\n\n    .shivit-blog-section h2 {\n      font-size: 27px;\n    }\n\n    .shivit-blog-quick-answer,\n    .shivit-blog-takeaways,\n    .shivit-blog-toc,\n    .shivit-blog-info-card {\n      padding: 20px 17px;\n    }\n  }\n<\/style>\n\n<section class=\"shivit-blog-section\">\n\n  <div class=\"shivit-blog-intro\">\n    <p>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 \u201cplease send 500 units\u201d phone call or WhatsApp message rarely holds up when there&#8217;s a price dispute or a tax reconciliation to do later.<\/p>\n\n    <p>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 \u2014 while keeping the PO clearly distinct from the vendor&#8217;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.<\/p>\n  <\/div>\n\n  <div class=\"shivit-blog-quick-answer\">\n    <span class=\"shivit-blog-label\">Quick Answer<\/span>\n    <p>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 \u2014 that is a separate document the vendor issues under GST law.<\/p>\n  <\/div>\n\n  <div class=\"shivit-blog-takeaways\">\n    <span class=\"shivit-blog-label\">Key Takeaways<\/span>\n\n    <ul>\n      <li>A purchase order is a buyer-issued document that formally requests goods or services from a vendor at agreed terms.<\/li>\n      <li>Businesses use POs to control spending, give vendors clear instructions, and create a reference point for receiving and invoice matching.<\/li>\n      <li>The four common PO types are standard, blanket, planned, and contract purchase orders, each suited to different buying patterns.<\/li>\n      <li>A PO connects to the wider procurement flow: requisition \u2192 approval \u2192 PO \u2192 GRN \u2192 invoice \u2192 payment.<\/li>\n      <li>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.<\/li>\n    <\/ul>\n  <\/div>\n\n  <div class=\"shivit-blog-toc\">\n    <span class=\"shivit-blog-label\">Table of Contents<\/span>\n\n    <ul>\n      <li>What Is a Purchase Order?<\/li>\n      <li>Why Do Businesses Use Purchase Orders?<\/li>\n      <li>What Are the Different Types of Purchase Orders?<\/li>\n      <li>What Should a Purchase Order Include?<\/li>\n      <li>What GST Considerations Apply to a Purchase Order in India?<\/li>\n      <li>Is a Purchase Order Mandatory in India?<\/li>\n      <li>How Does a Purchase Order Fit Into the Procurement Process?<\/li>\n      <li>Purchase Order vs Invoice vs GRN<\/li>\n      <li>When Should a Business Start Using Formal Purchase Orders?<\/li>\n      <li>When Manual Purchase Orders Start Becoming Difficult<\/li>\n      <li>FAQ<\/li>\n      <li>Conclusion<\/li>\n    <\/ul>\n  <\/div>\n\n  <div class=\"shivit-blog-section-divider\"><\/div>\n\n \n\n  <h2>What Is a Purchase Order?<\/h2>\n\n  <p>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.<\/p>\n\n  <p>The buyer is the business placing the order \u2014 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 \u2014 the exact legal effect can vary by situation, so businesses with specific contractual questions should check with a qualified professional.<\/p>\n\n  <div class=\"shivit-blog-info-card\">\n    <p>Example scenario: Consider a hypothetical Indian manufacturing SME \u2014 call it a small components manufacturer in Pune \u2014 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.<\/p>\n  <\/div>\n\n  <p>A typical PO establishes:<\/p>\n\n  <ul>\n    <li>Buyer \u2014 the business placing the order<\/li>\n    <li>Vendor\/supplier \u2014 the business fulfilling it<\/li>\n    <li>Product or service \u2014 what is being purchased<\/li>\n    <li>Quantity \u2014 how much is being ordered<\/li>\n    <li>Agreed price \u2014 the rate per unit and total value<\/li>\n    <li>Delivery terms \u2014 where and when goods should arrive<\/li>\n    <li>Payment terms \u2014 when and how the vendor will be paid<\/li>\n  <\/ul>\n\n  <h2>Why Do Businesses Use Purchase Orders?<\/h2>\n\n  <p>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.<\/p>\n\n  <p>A PO gives a business several concrete benefits:<\/p>\n\n  <ul>\n    <li>Purchase authorization. It shows that someone with the right authority approved the spend, rather than an ad-hoc order.<\/li>\n    <li>Clear vendor instructions. The vendor knows exactly what to supply, at what price, and by when \u2014 reducing back-and-forth.<\/li>\n    <li>Documented quantity and price. Both sides agree to the same numbers before goods move, which limits disputes later.<\/li>\n    <li>Procurement control. Finance and purchase teams can track what has been ordered but not yet received (open POs).<\/li>\n    <li>Receiving reference. The warehouse or stores team checks incoming goods against the PO quantity and item details.<\/li>\n    <li>Invoice reconciliation. Accounts can compare the vendor&#8217;s bill against what was actually ordered and received.<\/li>\n    <li>Audit trail. A dated, numbered PO record supports internal audits and helps explain historical purchasing decisions.<\/li>\n  <\/ul>\n\n  <p>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.<\/p>\n\n  <h2>What Are the Different Types of Purchase Orders?<\/h2>\n\n  <p>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.<\/p>\n\n  <div class=\"shivit-blog-type-grid\">\n\n    <article class=\"shivit-blog-type-card\">\n      <h3>Standard Purchase Order<\/h3>\n      <p>This is a one-time order for a specific quantity of goods or services, at a fixed price, for a defined delivery date. It&#8217;s the most common type and suits occasional or non-repeating purchases.<\/p>\n      <p>Example: The Pune manufacturing SME orders 500 kg of steel sheet as a single, defined purchase.<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-type-card\">\n      <h3>Blanket Purchase Order<\/h3>\n      <p>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.<\/p>\n      <p>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.<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-type-card\">\n      <h3>Planned Purchase Order<\/h3>\n      <p>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.<\/p>\n      <p>Example: The SME plans monthly steel deliveries for the next two quarters based on projected production, with exact release dates confirmed each month.<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-type-card\">\n      <h3>Contract Purchase Order<\/h3>\n      <p>A contract PO is tied to a broader agreement \u2014 often covering pricing, terms, and conditions negotiated over a longer period \u2014 and is used to formalize individual purchases under that contract.<\/p>\n      <p>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.<\/p>\n    <\/article>\n\n  <\/div>\n\n  <h3>PO Type Comparison Table<\/h3>\n\n  <div class=\"shivit-blog-table-wrap\">\n    <table class=\"shivit-blog-table\">\n      <thead>\n        <tr>\n          <th scope=\"col\">PO Type<\/th>\n          <th scope=\"col\">What It Means<\/th>\n          <th scope=\"col\">Best Use<\/th>\n          <th scope=\"col\">Example<\/th>\n        <\/tr>\n      <\/thead>\n      <tbody>\n        <tr>\n          <td>Standard PO<\/td>\n          <td>One-time order with fixed quantity, price, and delivery date<\/td>\n          <td>Occasional or non-repeating purchases<\/td>\n          <td>Ordering 500 kg of steel sheet as a single order<\/td>\n        <\/tr>\n        <tr>\n          <td>Blanket PO<\/td>\n          <td>Covers multiple deliveries of the same item at pre-agreed terms<\/td>\n          <td>Repeat purchases from the same vendor<\/td>\n          <td>Drawing steel in smaller lots over a quarter<\/td>\n        <\/tr>\n        <tr>\n          <td>Planned PO<\/td>\n          <td>Forecasted quantities and tentative schedule, confirmed closer to need<\/td>\n          <td>Businesses forecasting demand but needing flexibility<\/td>\n          <td>Planning monthly deliveries based on projected production<\/td>\n        <\/tr>\n        <tr>\n          <td>Contract PO<\/td>\n          <td>Individual order issued under a broader negotiated agreement<\/td>\n          <td>Long-term vendor relationships with negotiated terms<\/td>\n          <td>Issuing batch-wise POs under an annual supply agreement<\/td>\n        <\/tr>\n      <\/tbody>\n    <\/table>\n  <\/div>\n\n  <h2>What Should a Purchase Order Include?<\/h2>\n\n  <p>A well-structured PO reduces confusion for both the vendor and the buyer&#8217;s own teams. While exact formats vary by business and industry, most Indian purchase orders group information into a few clear sections.<\/p>\n\n  <h3>Buyer information<\/h3>\n\n  <p>The buyer&#8217;s legal or trade name, address, and contact details, so the vendor knows exactly who is ordering.<\/p>\n\n  <h3>Supplier information<\/h3>\n\n  <p>The vendor&#8217;s name, address, and contact details, confirming who is expected to fulfil the order.<\/p>\n\n  <h3>PO identification<\/h3>\n\n  <p>A unique PO number and PO date. The number lets both sides reference the order in emails, GRNs, and invoices without ambiguity.<\/p>\n\n  <h3>Product\/service information<\/h3>\n\n  <p>A clear description of what is being ordered \u2014 including specifications, model, or grade where relevant \u2014 so the vendor supplies the correct item.<\/p>\n\n  <h3>Quantity and pricing<\/h3>\n\n  <p>The quantity ordered, unit price, and total order value. This is the figure both sides will later check the invoice against.<\/p>\n\n  <h3>Delivery information<\/h3>\n\n  <p>Where the goods should be delivered and the expected delivery date. This helps the receiving team plan and gives the vendor a clear deadline.<\/p>\n\n  <h3>Payment terms<\/h3>\n\n  <p>When payment will be made \u2014 for example, a fixed number of days after delivery or invoice \u2014 set out so there&#8217;s no ambiguity at settlement time.<\/p>\n\n  <h3>Tax-related information (optional, business practice)<\/h3>\n\n  <p>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 \u2014 the particulars actually prescribed for GST purposes apply to the vendor&#8217;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.<\/p>\n\n  <h3>Approval\/authorization information<\/h3>\n\n  <p>Many businesses include an approver name or signature line on the PO, reflecting internal purchase authorization \u2014 this is a business control, not a government requirement.<\/p>\n\n  <p>It&#8217;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&#8217;s listed here reflects common, sensible business practice for a document that needs to be clear, traceable, and useful for later reconciliation.<\/p>\n\n<\/section>\n\n\n\n<figure class=\"gb-block-image gb-block-image-fee1017a\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1536\" height=\"1024\" class=\"gb-image gb-image-fee1017a\" src=\"https:\/\/shivit.com\/blog\/wp-content\/uploads\/2026\/08\/annotated-purchase-order-format-india-example.png\" alt=\"Annotated purchase order format showing PO number, buyer, supplier, item quantity, pricing, delivery terms and GST-related reference information\" title=\"Annotated Purchase Order Format Example for an Indian SME\"\/><\/figure>\n\n\n\n<style>\n  .shivit-blog-section {\n    --shivit-blog-blue: #1769e0;\n    --shivit-blog-blue-dark: #0f3f8c;\n    --shivit-blog-navy: #172033;\n    --shivit-blog-text: #3f4a5a;\n    --shivit-blog-muted: #667085;\n    --shivit-blog-border: #dfe6ef;\n    --shivit-blog-surface: #f7faff;\n    --shivit-blog-white: #ffffff;\n    --shivit-blog-radius: 14px;\n    --shivit-blog-shadow: 0 8px 28px rgba(20, 48, 87, 0.06);\n\n    max-width: 1160px;\n    margin: 0 auto;\n    padding: 12px 20px 56px;\n    color: var(--shivit-blog-text);\n    font-family: Inter, -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto, Arial, sans-serif;\n    font-size: 17px;\n    line-height: 1.75;\n    box-sizing: border-box;\n  }\n\n  .shivit-blog-section *,\n  .shivit-blog-section *::before,\n  .shivit-blog-section *::after {\n    box-sizing: border-box;\n  }\n\n  .shivit-blog-section h2,\n  .shivit-blog-section h3,\n  .shivit-blog-section p,\n  .shivit-blog-section ul {\n    margin-top: 0;\n  }\n\n  .shivit-blog-section h2 {\n    margin: 64px 0 24px;\n    color: var(--shivit-blog-navy);\n    font-size: clamp(28px, 3vw, 38px);\n    line-height: 1.2;\n    letter-spacing: -0.025em;\n    font-weight: 750;\n  }\n\n  .shivit-blog-section h3 {\n    margin: 38px 0 14px;\n    color: var(--shivit-blog-navy);\n    font-size: clamp(21px, 2vw, 26px);\n    line-height: 1.3;\n    letter-spacing: -0.015em;\n    font-weight: 700;\n  }\n\n  .shivit-blog-section p {\n    margin-bottom: 22px;\n  }\n\n  .shivit-blog-section ul {\n    margin: 0 0 30px;\n    padding: 0;\n    list-style: none;\n  }\n\n  .shivit-blog-section li {\n    position: relative;\n    margin: 0 0 13px;\n    padding-left: 30px;\n  }\n\n  .shivit-blog-section li::before {\n    content: \"\";\n    position: absolute;\n    left: 3px;\n    top: 0.82em;\n    width: 7px;\n    height: 7px;\n    border-radius: 50%;\n    background: var(--shivit-blog-blue);\n    transform: translateY(-50%);\n  }\n\n  .shivit-blog-visual-note {\n    margin: 0 0 52px;\n    padding: 28px 30px;\n    border: 1px solid #cfe0f7;\n    border-left: 4px solid var(--shivit-blog-blue);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-surface);\n  }\n\n  .shivit-blog-visual-note ul {\n    margin-bottom: 24px;\n  }\n\n  .shivit-blog-visual-note li {\n    padding-left: 34px;\n  }\n\n  .shivit-blog-visual-note li::before {\n    content: attr(data-number);\n    left: 0;\n    top: 0.05em;\n    width: 24px;\n    height: 24px;\n    background: var(--shivit-blog-blue);\n    color: var(--shivit-blog-white);\n    font-size: 12px;\n    line-height: 24px;\n    text-align: center;\n    font-weight: 700;\n    transform: none;\n  }\n\n  .shivit-blog-section-divider {\n    width: 100%;\n    height: 1px;\n    margin: 58px 0 8px;\n    background: var(--shivit-blog-border);\n  }\n\n  .shivit-blog-doc-grid {\n    display: grid;\n    grid-template-columns: repeat(3, minmax(0, 1fr));\n    gap: 18px;\n    margin: 30px 0 36px;\n  }\n\n  .shivit-blog-doc-card {\n    padding: 24px 24px 22px;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-white);\n    box-shadow: var(--shivit-blog-shadow);\n  }\n\n  .shivit-blog-doc-card h3 {\n    margin: 0 0 12px;\n    color: var(--shivit-blog-blue-dark);\n    font-size: 20px;\n  }\n\n  .shivit-blog-doc-card p {\n    margin: 0;\n    font-size: 15.5px;\n    line-height: 1.65;\n  }\n\n  .shivit-blog-process {\n    margin: 30px 0 38px;\n    padding: 24px;\n    overflow-x: auto;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-surface);\n    -webkit-overflow-scrolling: touch;\n  }\n\n  .shivit-blog-process-flow {\n    display: flex;\n    align-items: center;\n    justify-content: center;\n    min-width: 920px;\n    gap: 10px;\n  }\n\n  .shivit-blog-process-step {\n    flex: 1 1 0;\n    min-width: 125px;\n    padding: 16px 14px;\n    border: 1px solid #cbd8e8;\n    border-radius: 10px;\n    background: var(--shivit-blog-white);\n    color: var(--shivit-blog-navy);\n    text-align: center;\n    font-size: 14px;\n    line-height: 1.45;\n    font-weight: 700;\n  }\n\n  .shivit-blog-process-arrow {\n    flex: 0 0 auto;\n    color: var(--shivit-blog-blue);\n    font-size: 20px;\n    font-weight: 700;\n  }\n\n  .shivit-blog-process-list {\n    margin-top: 34px;\n  }\n\n  @media (max-width: 820px) {\n    .shivit-blog-doc-grid {\n      grid-template-columns: 1fr;\n    }\n\n    .shivit-blog-doc-card {\n      padding: 21px 20px;\n    }\n  }\n\n  @media (max-width: 760px) {\n    .shivit-blog-section {\n      padding: 8px 17px 42px;\n      font-size: 16px;\n      line-height: 1.7;\n    }\n\n    .shivit-blog-section h2 {\n      margin-top: 44px;\n      margin-bottom: 20px;\n      font-size: 29px;\n    }\n\n    .shivit-blog-section h3 {\n      margin-top: 32px;\n      font-size: 22px;\n    }\n\n    .shivit-blog-visual-note {\n      padding: 22px 20px;\n    }\n\n    .shivit-blog-process {\n      padding: 18px;\n      margin-top: 24px;\n    }\n\n    .shivit-blog-process-flow {\n      justify-content: flex-start;\n    }\n\n    .shivit-blog-process-step {\n      min-width: 135px;\n    }\n\n    .shivit-blog-section-divider {\n      margin: 44px 0 4px;\n    }\n  }\n\n  @media (max-width: 420px) {\n    .shivit-blog-section {\n      padding-left: 16px;\n      padding-right: 16px;\n    }\n\n    .shivit-blog-section h2 {\n      font-size: 27px;\n    }\n\n    .shivit-blog-visual-note {\n      padding: 20px 17px;\n    }\n  }\n<\/style>\n\n<section class=\"shivit-blog-section\">\n\n  <div class=\"shivit-blog-visual-note\">\n    <p>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:<\/p>\n\n    <ul>\n      <li data-number=\"1\">Buyer details (company name, address, GSTIN)<\/li>\n      <li data-number=\"2\">PO number and PO date<\/li>\n      <li data-number=\"3\">Vendor details (company name, address, GSTIN)<\/li>\n      <li data-number=\"4\">Delivery address and expected delivery date<\/li>\n      <li data-number=\"5\">Item description, HSN code, quantity, and pricing<\/li>\n      <li data-number=\"6\">Indicative CGST\/SGST or IGST reference<\/li>\n      <li data-number=\"7\">Payment terms<\/li>\n      <li data-number=\"8\">Authorized signatory<\/li>\n      <li data-number=\"9\">A clarifying note that the PO is not a GST tax invoice<\/li>\n    <\/ul>\n\n    <p>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.<\/p>\n  <\/div>\n\n  <div class=\"shivit-blog-section-divider\"><\/div>\n\n  <h2>What GST Considerations Apply to a Purchase Order in India?<\/h2>\n\n  <p>This is one of the most misunderstood areas of Indian procurement documentation, so it&#8217;s worth being precise about what each document is and isn&#8217;t.<\/p>\n\n  <p>Three separate documents, three separate roles:<\/p>\n\n  <div class=\"shivit-blog-doc-grid\">\n\n    <article class=\"shivit-blog-doc-card\">\n      <h3>Purchase order<\/h3>\n      <p>the buyer&#8217;s commercial ordering document, created before the supply happens<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-doc-card\">\n      <h3>GRN (Goods Receipt Note)<\/h3>\n      <p>the buyer&#8217;s internal record of what was actually received<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-doc-card\">\n      <h3>Tax invoice<\/h3>\n      <p>the vendor&#8217;s legal GST billing document, governed by GST law<\/p>\n    <\/article>\n\n  <\/div>\n\n  <p>A purchase order is not the same document as a GST tax invoice.<\/p>\n\n  <p>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.<\/p>\n\n  <p>These provisions govern the tax invoice; they do not prescribe a universal purchase-order format.<\/p>\n\n  <p>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.<\/p>\n\n  <p>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.<\/p>\n\n  <h2>Is a Purchase Order Mandatory in India?<\/h2>\n\n  <p>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 \u2014 legal, contractual, and internal:<\/p>\n\n  <ul>\n    <li>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 \u2014 check the applicable regulation if relevant to your situation.)<\/li>\n\n    <li>Contractual requirement: Many vendors, especially larger ones or those supplying under a formal agreement, will refuse to process an order \u2014 or delay invoicing \u2014 without a PO reference, because it&#8217;s built into their own billing workflow. Here, the PO becomes necessary by agreement, not by statute.<\/li>\n\n    <li>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.<\/li>\n\n    <li>Business practice: In many industries, especially manufacturing, trading, and distribution, issuing a PO is simply standard commercial practice, expected by both buyers and vendors.<\/li>\n  <\/ul>\n\n  <p>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 \u2014 businesses with specific compliance questions should consult a qualified professional.<\/p>\n\n  <h2>How Does a Purchase Order Fit Into the Procurement Process?<\/h2>\n\n  <p>A purchase order is one step within a broader procurement flow. Here&#8217;s how it typically connects to the steps before and after it:<\/p>\n\n  <div class=\"shivit-blog-process\">\n    <div class=\"shivit-blog-process-flow\">\n      <div class=\"shivit-blog-process-step\">Purchase Requisition<\/div>\n      <div class=\"shivit-blog-process-arrow\" aria-hidden=\"true\">\u2192<\/div>\n      <div class=\"shivit-blog-process-step\">Approval<\/div>\n      <div class=\"shivit-blog-process-arrow\" aria-hidden=\"true\">\u2192<\/div>\n      <div class=\"shivit-blog-process-step\">Purchase Order<\/div>\n      <div class=\"shivit-blog-process-arrow\" aria-hidden=\"true\">\u2192<\/div>\n      <div class=\"shivit-blog-process-step\">Goods Receipt \/ GRN<\/div>\n      <div class=\"shivit-blog-process-arrow\" aria-hidden=\"true\">\u2192<\/div>\n      <div class=\"shivit-blog-process-step\">Supplier Invoice<\/div>\n      <div class=\"shivit-blog-process-arrow\" aria-hidden=\"true\">\u2192<\/div>\n      <div class=\"shivit-blog-process-step\">Reconciliation \/ Payment<\/div>\n    <\/div>\n  <\/div>\n\n  <ul class=\"shivit-blog-process-list\">\n    <li>Purchase Requisition: An internal request \u2014 for example, from a production or stores team \u2014 flagging that an item needs to be bought.<\/li>\n\n    <li>Approval: The requisition is reviewed and approved by whoever holds purchasing authority, before any commitment is made to a vendor.<\/li>\n\n    <li>Purchase Order: Once approved, the PO is created and sent to the chosen vendor, formalizing the order.<\/li>\n\n    <li>Goods Receipt \/ GRN: When goods arrive, the receiving team records what was actually delivered against the PO.<\/li>\n\n    <li>Supplier Invoice: The vendor bills the buyer, referencing the PO and\/or GRN.<\/li>\n\n    <li>Reconciliation \/ Payment: Accounts checks the PO, GRN, and invoice against each other before releasing payment.)<\/li>\n  <\/ul>\n\n<\/section>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"1536\" height=\"1024\" src=\"https:\/\/shivit.com\/blog\/wp-content\/uploads\/2026\/08\/purchase-order-grn-invoice-procurement-workflow.png\" alt=\"Purchase order to GRN to supplier invoice workflow showing what was ordered, what was received and what was billed\" class=\"wp-image-432\"\/><figcaption class=\"wp-element-caption\">Typical purchase-to-pay workflow showing how the purchase order, goods receipt note and supplier invoice connect during procurement.<\/figcaption><\/figure>\n\n\n\n<style>\n  .shivit-blog-section {\n    --shivit-blog-blue: #1769e0;\n    --shivit-blog-blue-dark: #0f3f8c;\n    --shivit-blog-navy: #172033;\n    --shivit-blog-text: #3f4a5a;\n    --shivit-blog-muted: #667085;\n    --shivit-blog-border: #dfe6ef;\n    --shivit-blog-surface: #f7faff;\n    --shivit-blog-white: #ffffff;\n    --shivit-blog-radius: 14px;\n    --shivit-blog-shadow: 0 8px 28px rgba(20, 48, 87, 0.06);\n\n    max-width: 1160px;\n    margin: 0 auto;\n    padding: 12px 20px 56px;\n    color: var(--shivit-blog-text);\n    font-family: Inter, -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto, Arial, sans-serif;\n    font-size: 17px;\n    line-height: 1.75;\n    box-sizing: border-box;\n  }\n\n  .shivit-blog-section *,\n  .shivit-blog-section *::before,\n  .shivit-blog-section *::after {\n    box-sizing: border-box;\n  }\n\n  .shivit-blog-section h2,\n  .shivit-blog-section h3,\n  .shivit-blog-section p,\n  .shivit-blog-section ul {\n    margin-top: 0;\n  }\n\n  .shivit-blog-section h2 {\n    margin: 64px 0 24px;\n    color: var(--shivit-blog-navy);\n    font-size: clamp(28px, 3vw, 38px);\n    line-height: 1.2;\n    letter-spacing: -0.025em;\n    font-weight: 750;\n  }\n\n  .shivit-blog-section h3 {\n    margin: 38px 0 14px;\n    color: var(--shivit-blog-navy);\n    font-size: clamp(21px, 2vw, 26px);\n    line-height: 1.3;\n    letter-spacing: -0.015em;\n    font-weight: 700;\n  }\n\n  .shivit-blog-section p {\n    margin-bottom: 22px;\n  }\n\n  .shivit-blog-section ul {\n    margin: 0 0 30px;\n    padding: 0;\n    list-style: none;\n  }\n\n  .shivit-blog-section li {\n    position: relative;\n    margin: 0 0 13px;\n    padding-left: 28px;\n  }\n\n  .shivit-blog-section li::before {\n    content: \"\";\n    position: absolute;\n    left: 3px;\n    top: 0.82em;\n    width: 7px;\n    height: 7px;\n    border-radius: 50%;\n    background: var(--shivit-blog-blue);\n    transform: translateY(-50%);\n  }\n\n  .shivit-blog-section-divider {\n    width: 100%;\n    height: 1px;\n    margin: 58px 0 8px;\n    background: var(--shivit-blog-border);\n  }\n\n  .shivit-blog-table-wrap {\n    width: 100%;\n    margin: 30px 0 40px;\n    overflow-x: auto;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-white);\n    box-shadow: var(--shivit-blog-shadow);\n    -webkit-overflow-scrolling: touch;\n  }\n\n  .shivit-blog-table {\n    width: 100%;\n    min-width: 820px;\n    border-collapse: separate;\n    border-spacing: 0;\n    color: var(--shivit-blog-text);\n    font-size: 15px;\n    line-height: 1.55;\n  }\n\n  .shivit-blog-table th {\n    padding: 17px 18px;\n    color: var(--shivit-blog-white);\n    background: var(--shivit-blog-blue-dark);\n    text-align: left;\n    vertical-align: top;\n    font-size: 14px;\n    line-height: 1.4;\n    font-weight: 700;\n    border-right: 1px solid rgba(255,255,255,0.16);\n  }\n\n  .shivit-blog-table th:last-child {\n    border-right: 0;\n  }\n\n  .shivit-blog-table td {\n    padding: 18px;\n    vertical-align: top;\n    border-top: 1px solid var(--shivit-blog-border);\n    border-right: 1px solid var(--shivit-blog-border);\n    background: var(--shivit-blog-white);\n  }\n\n  .shivit-blog-table td:last-child {\n    border-right: 0;\n  }\n\n  .shivit-blog-table tbody tr:nth-child(even) td {\n    background: #f8faff;\n  }\n\n  .shivit-blog-table tbody tr:first-child td {\n    border-top: 0;\n  }\n\n  .shivit-blog-table td:first-child {\n    color: var(--shivit-blog-navy);\n    font-weight: 700;\n  }\n\n  .shivit-blog-callout {\n    margin: 30px 0 36px;\n    padding: 26px 28px;\n    border: 1px solid #cfe0f7;\n    border-left: 4px solid var(--shivit-blog-blue);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-surface);\n  }\n\n  .shivit-blog-callout p:last-child {\n    margin-bottom: 0;\n  }\n\n  .shivit-blog-link-panel {\n    display: flex;\n    align-items: center;\n    justify-content: space-between;\n    gap: 22px;\n    margin: 34px 0 48px;\n    padding: 22px 25px;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-white);\n    box-shadow: var(--shivit-blog-shadow);\n  }\n\n  .shivit-blog-link-panel span {\n    color: var(--shivit-blog-blue-dark);\n    font-weight: 700;\n  }\n\n  .shivit-blog-link-arrow {\n    flex: 0 0 auto;\n    color: var(--shivit-blog-blue);\n    font-size: 20px;\n    font-weight: 700;\n  }\n\n  .shivit-blog-sign-grid {\n    display: grid;\n    grid-template-columns: 1fr 1.35fr;\n    gap: 0;\n    margin: 30px 0 40px;\n    overflow: hidden;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-white);\n    box-shadow: var(--shivit-blog-shadow);\n  }\n\n  .shivit-blog-sign-grid > div {\n    padding: 16px 18px;\n    border-top: 1px solid var(--shivit-blog-border);\n  }\n\n  .shivit-blog-sign-grid > div:nth-child(1),\n  .shivit-blog-sign-grid > div:nth-child(2) {\n    border-top: 0;\n    background: var(--shivit-blog-blue-dark);\n    color: var(--shivit-blog-white);\n    font-weight: 700;\n  }\n\n  .shivit-blog-sign-grid > div:nth-child(odd) {\n    color: var(--shivit-blog-navy);\n    font-weight: 700;\n    border-right: 1px solid var(--shivit-blog-border);\n  }\n\n  .shivit-blog-sign-grid > div:nth-child(2n+4),\n  .shivit-blog-sign-grid > div:nth-child(2n+3) {\n    background: var(--shivit-blog-white);\n  }\n\n  .shivit-blog-sign-grid > div:nth-child(4n+3),\n  .shivit-blog-sign-grid > div:nth-child(4n+4) {\n    background: #f8faff;\n  }\n\n  .shivit-blog-sign-grid > div:nth-child(2) {\n    border-right: 0;\n  }\n\n  .shivit-blog-process-panel {\n    margin: 32px 0 40px;\n    padding: 27px 28px;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: #fbfcfe;\n  }\n\n  .shivit-blog-process-panel ul {\n    margin-bottom: 0;\n  }\n\n  .shivit-blog-product-flow {\n    margin: 30px 0 34px;\n    padding: 25px 27px;\n    border: 1px solid #cfe0f7;\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-surface);\n  }\n\n  .shivit-blog-product-flow p:last-child {\n    margin-bottom: 0;\n  }\n\n  .shivit-blog-faq {\n    display: grid;\n    gap: 16px;\n    margin: 30px 0 52px;\n  }\n\n  .shivit-blog-faq-item {\n    padding: 23px 25px;\n    border: 1px solid var(--shivit-blog-border);\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-white);\n    box-shadow: var(--shivit-blog-shadow);\n  }\n\n  .shivit-blog-faq-item h3 {\n    margin: 0 0 11px;\n    color: var(--shivit-blog-blue-dark);\n    font-size: 20px;\n  }\n\n  .shivit-blog-faq-item p {\n    margin-bottom: 0;\n  }\n\n  .shivit-blog-cta {\n    display: grid;\n    grid-template-columns: repeat(2, minmax(0, 1fr));\n    gap: 18px;\n    margin-top: 30px;\n  }\n\n  .shivit-blog-cta-item {\n    display: block;\n    padding: 24px 25px;\n    border: 1px solid #cfe0f7;\n    border-radius: var(--shivit-blog-radius);\n    background: var(--shivit-blog-surface);\n    color: var(--shivit-blog-blue-dark);\n    font-weight: 700;\n    text-decoration: none;\n  }\n\n  .shivit-blog-cta-item:hover {\n    border-color: var(--shivit-blog-blue);\n  }\n\n  @media (max-width: 820px) {\n    .shivit-blog-cta {\n      grid-template-columns: 1fr;\n    }\n\n    .shivit-blog-link-panel {\n      align-items: flex-start;\n    }\n  }\n\n  @media (max-width: 760px) {\n    .shivit-blog-section {\n      padding: 8px 17px 42px;\n      font-size: 16px;\n      line-height: 1.7;\n    }\n\n    .shivit-blog-section h2 {\n      margin-top: 44px;\n      margin-bottom: 20px;\n      font-size: 29px;\n    }\n\n    .shivit-blog-section h3 {\n      margin-top: 32px;\n      font-size: 22px;\n    }\n\n    .shivit-blog-table-wrap {\n      margin-top: 24px;\n      border-radius: 11px;\n    }\n\n    .shivit-blog-table {\n      min-width: 780px;\n      font-size: 14px;\n    }\n\n    .shivit-blog-table th,\n    .shivit-blog-table td {\n      padding: 14px;\n    }\n\n    .shivit-blog-callout,\n    .shivit-blog-process-panel,\n    .shivit-blog-product-flow {\n      padding: 22px 20px;\n    }\n\n    .shivit-blog-sign-grid {\n      grid-template-columns: 1fr;\n      border-radius: 11px;\n    }\n\n    .shivit-blog-sign-grid > div {\n      border-right: 0 !important;\n    }\n\n    .shivit-blog-sign-grid > div:nth-child(2) {\n      border-top: 0;\n    }\n\n    .shivit-blog-link-panel {\n      flex-direction: column;\n      gap: 8px;\n      padding: 21px 20px;\n    }\n\n    .shivit-blog-faq-item {\n      padding: 21px 20px;\n    }\n\n    .shivit-blog-section-divider {\n      margin: 44px 0 4px;\n    }\n  }\n\n  @media (max-width: 420px) {\n    .shivit-blog-section {\n      padding-left: 16px;\n      padding-right: 16px;\n    }\n\n    .shivit-blog-section h2 {\n      font-size: 27px;\n    }\n\n    .shivit-blog-cta-item {\n      padding: 21px 20px;\n    }\n  }\n<\/style>\n\n<section class=\"shivit-blog-section\">\n\n  <div class=\"shivit-blog-section-divider\"><\/div>\n\n  <h2>Purchase Order vs Invoice vs GRN<\/h2>\n\n  <p>These three documents are often confused, but each serves a distinct role in the same transaction.<\/p>\n\n  <div class=\"shivit-blog-table-wrap\">\n    <table class=\"shivit-blog-table\">\n      <thead>\n        <tr>\n          <th scope=\"col\">Document<\/th>\n          <th scope=\"col\">Created By<\/th>\n          <th scope=\"col\">Main Purpose<\/th>\n          <th scope=\"col\">When Used<\/th>\n        <\/tr>\n      <\/thead>\n      <tbody>\n        <tr>\n          <td>Purchase Order<\/td>\n          <td>Buyer<\/td>\n          <td>States what is being ordered, at what price and terms<\/td>\n          <td>Before goods are supplied<\/td>\n        <\/tr>\n        <tr>\n          <td>GRN (Goods Receipt Note)<\/td>\n          <td>Buyer<\/td>\n          <td>Records what was actually received<\/td>\n          <td>When goods physically arrive<\/td>\n        <\/tr>\n        <tr>\n          <td>Invoice<\/td>\n          <td>Vendor\/Supplier<\/td>\n          <td>Bills the buyer for goods or services supplied, under GST rules<\/td>\n          <td>At or after delivery<\/td>\n        <\/tr>\n      <\/tbody>\n    <\/table>\n  <\/div>\n\n  <div class=\"shivit-blog-callout\">\n    <p>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 \u2014 often called three-way matching \u2014 helps catch mismatches in quantity, price, or tax details before payment is released.<\/p>\n\n    <p>This article only covers the essentials of that relationship.<\/p>\n  <\/div>\n\n  <div class=\"shivit-blog-link-panel\">\n    <span>[ see the full breakdown of POs, invoices and GRNs ]<\/span>\n   \n  <\/div>\n\n  <h2>When Should a Business Start Using Formal Purchase Orders?<\/h2>\n\n  <p>Many small businesses start out managing purchases informally, and that can work fine at low volumes. Certain signs typically indicate it&#8217;s time to formalize the process.<\/p>\n\n  <div class=\"shivit-blog-table-wrap\">\n    <table class=\"shivit-blog-table\">\n      <thead>\n        <tr>\n          <th scope=\"col\">Sign You&#8217;re Seeing<\/th>\n          <th scope=\"col\">Why It Points to Formal POs<\/th>\n        <\/tr>\n      <\/thead>\n      <tbody>\n        <tr>\n          <td>Purchase volume is increasing month over month<\/td>\n          <td>Harder to track spend and commitments from memory alone<\/td>\n        <\/tr>\n        <tr>\n          <td>Multiple vendors supply similar items<\/td>\n          <td>A written order avoids confusion about who agreed to what<\/td>\n        <\/tr>\n        <tr>\n          <td>The same items are reordered repeatedly<\/td>\n          <td>A blanket or planned PO can reduce repetitive paperwork<\/td>\n        <\/tr>\n        <tr>\n          <td>Price disputes with vendors are becoming frequent<\/td>\n          <td>A documented, agreed price prevents after-the-fact disagreements<\/td>\n        <\/tr>\n        <tr>\n          <td>Quantity discrepancies show up on delivery<\/td>\n          <td>A PO gives the receiving team a clear quantity to check against<\/td>\n        <\/tr>\n        <tr>\n          <td>Approvals happen after spending, not before<\/td>\n          <td>A PO built on an approved requisition enforces authorization upfront<\/td>\n        <\/tr>\n        <tr>\n          <td>The business now operates across multiple locations<\/td>\n          <td>A consistent PO format keeps purchasing comparable across sites<\/td>\n        <\/tr>\n        <tr>\n          <td>It&#8217;s hard to track which orders are still open<\/td>\n          <td>A numbered PO record makes open orders visible and searchable<\/td>\n        <\/tr>\n        <tr>\n          <td>Invoice amounts don&#8217;t match what was received<\/td>\n          <td>A PO-GRN-invoice check catches mismatches before payment<\/td>\n        <\/tr>\n      <\/tbody>\n    <\/table>\n  <\/div>\n\n  <p>None of these signs mean a business must adopt any specific tool. They simply indicate that a documented PO process \u2014 even a simple one \u2014 would likely reduce errors and disputes compared to informal ordering.<\/p>\n\n  <h2>When Manual Purchase Orders Start Becoming Difficult<\/h2>\n\n  <p>Once a business does move to formal POs, many run this process manually at first \u2014 using spreadsheets, email chains, and printed forms. This works, but it tends to strain as volume grows:<\/p>\n\n  <ul>\n    <li>Spreadsheet-based PO logs become hard to keep updated and version-controlled<\/li>\n    <li>Email approvals are slow to track and easy to lose in busy inboxes<\/li>\n    <li>Duplicate POs get created when there&#8217;s no single shared record<\/li>\n    <li>Records go missing across different people&#8217;s inboxes and folders<\/li>\n    <li>Purchase managers and finance heads lack real-time visibility into open orders<\/li>\n    <li>Reconciling POs, GRNs, and invoices by hand takes significant manual effort each month<\/li>\n  <\/ul>\n\n  <p>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.<\/p>\n\n  <p>For businesses that have outgrown manual tracking, the next step is usually procurement software that connects purchasing, approvals, receiving, and reporting in one place.<\/p>\n\n  <div class=\"shivit-blog-link-panel\">\n  <a class=\"shivit-blog-cta-item\" href=\"https:\/\/shivit.com\/blog\/index.php\/2025\/03\/18\/10-best-purchase-orders-software-to-consider-in-2026\/\">\n    [ compare purchase order software options in India ]\n  <\/a>\n<\/div>\n    \n  \n\n  <h2>Practical ERP Implementation Note<\/h2>\n\n  <div class=\"shivit-blog-process-panel\">\n    <p>Businesses moving from manual to system-based PO management commonly run into a few recurring setup issues \u2014 incomplete or outdated vendor master data, inconsistent product\/item naming across teams, unclear or undefined approval hierarchies, a backlog of old \u201copen\u201d POs that were never formally closed, and GRN quantities that don&#8217;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.<\/p>\n  <\/div>\n\n  <h2>Original Information Asset \/ Framework<\/h2>\n\n  <h3>How a Purchase Order Connects to Other Procurement Data<\/h3>\n\n  <p>A purchase order rarely stands alone \u2014 it links to several categories of information that together make up a business&#8217;s procurement record:<\/p>\n\n  <ul>\n    <li>Core commercial details: buyer, vendor, product\/service, quantity, price, delivery terms, payment terms<\/li>\n\n    <li>Tax-related reference (business practice, not a PO legal requirement): GSTIN, HSN\/SAC, CGST, SGST, IGST \u2014 included for planning and reconciliation, with the actual GST particulars governed by the vendor&#8217;s tax invoice under Rule 46<\/li>\n\n    <li>Process linkage: purchase requisition \u2192 approval \u2192 PO \u2192 GRN \u2192 invoice \u2192 payment<\/li>\n\n    <li>Business purpose: purchase control, vendor communication, budget control, receiving reference, and reconciliation<\/li>\n  <\/ul>\n\n  <div class=\"shivit-blog-product-flow\">\n    <p>Some procurement systems document this same lifecycle end to end. Shivaizer&#8217;s Purchase Management module, for example, documents the flow as Purchase Requisition (PR) \u2192 RFQ \u2192 Purchase Order (PO) \u2192 Goods Receipt Note (GRN) \u2192 Vendor Bill \u2192 Payment Voucher \u2192 Vendor Adjustment. Within that flow, its documented capabilities include:<\/p>\n\n    <ul>\n      <li>PR-linked PO creation, where item details, quantity, and a suggested vendor are pulled from an approved requisition<\/li>\n\n      <li>Manual\/direct PO creation for ad-hoc purchases that don&#8217;t originate from a requisition<\/li>\n\n      <li>Configurable PO approval workflows, with a documented status flow of Submitted \u2192 Pending Approval \u2192 Approved \u2192 Sent to Vendor<\/li>\n\n      <li>GRN recorded against an approved PO, supporting both partial and complete delivery<\/li>\n\n      <li>Vendor bill booking against the PO, the GRN, or directly<\/li>\n\n      <li>An audit trail across procurement and vendor-financial transactions<\/li>\n    <\/ul>\n\n    <p>This is a description of one product&#8217;s documented capability, not a claim about what every business needs \u2014 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.<\/p>\n  <\/div>\n\n  <h2>FAQ<\/h2>\n\n  <div class=\"shivit-blog-faq\">\n\n    <article class=\"shivit-blog-faq-item\">\n      <h3>What is a purchase order?<\/h3>\n      <p>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.<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-faq-item\">\n      <h3>What is a purchase order used for?<\/h3>\n      <p>It&#8217;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.<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-faq-item\">\n      <h3>Is a purchase order mandatory in India?<\/h3>\n      <p>There&#8217;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.<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-faq-item\">\n      <h3>Is GST applicable to a purchase order?<\/h3>\n      <p>GST is legally charged and documented through the vendor&#8217;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.<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-faq-item\">\n      <h3>What information should an Indian purchase order contain?<\/h3>\n      <p>Typically buyer and vendor details, a PO number and date, item description, quantity and price, delivery and payment terms, and \u2014 as a matter of business practice \u2014 GSTIN, HSN\/SAC, and tax reference details for the items ordered.<\/p>\n    <\/article>\n\n    <article class=\"shivit-blog-faq-item\">\n      <h3>What is the difference between a purchase order and an invoice?<\/h3>\n      <p>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.<\/p>\n    <\/article>\n\n  <\/div>\n\n  <h2>Conclusion<\/h2>\n\n  <p>A purchase order is the buyer&#8217;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 \u2014 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&#8217;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.<\/p>\n\n  <h2>Call to Action<\/h2>\n\n  <p>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.<\/p>\n\n <div class=\"shivit-blog-cta\">\n  <a class=\"shivit-blog-cta-item\" href=\"https:\/\/shivit.com\/blog\/index.php\/2025\/03\/18\/10-best-purchase-orders-software-to-consider-in-2026\/\">\n    [ Compare purchase order software options in India ]\n  <\/a>\n\n  <a class=\"shivit-blog-cta-item\" href=\"https:\/\/shivit.com\/purchase-order-management-software.html\">\n    [ Download a ready-to-use purchase order template ]\n  <\/a>\n<\/div>\n\n<\/section>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Researched and reviewed by Shivit Technologies Editorial Team Last updated: August 25, 2026 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 &#8230; <a title=\"What Is a Purchase Order? Types, Format &amp; GST Considerations in India\" class=\"read-more\" href=\"https:\/\/shivit.com\/blog\/index.php\/2026\/08\/25\/what-is-purchase-order-types-format-gst-india\/\" aria-label=\"Read more about What Is a Purchase Order? Types, Format &amp; GST Considerations in India\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[96],"tags":[102,111,105,109,113,108,112,118,104,115,100,110,106,107,98,117,116,114,103,99,101,97],"class_list":["post-430","post","type-post","status-publish","format-standard","hentry","category-best-purchase-order-management-software","tag-blanket-purchase-order","tag-cgst","tag-contract-purchase-order","tag-gst-on-purchase-order","tag-gst-purchase-order-format","tag-gstin-in-purchase-order","tag-hsn-sac-in-purchase-order","tag-igst","tag-planned-purchase-order","tag-po-format-india","tag-purchase-order-definition","tag-purchase-order-example","tag-purchase-order-format","tag-purchase-order-gst","tag-purchase-order-meaning","tag-purchase-order-vs-grn","tag-purchase-order-vs-invoice","tag-sgst","tag-standard-purchase-order","tag-types-of-purchase-orders","tag-what-is-a-po","tag-what-is-a-purchase-order"],"_links":{"self":[{"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/430","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=430"}],"version-history":[{"count":2,"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/430\/revisions"}],"predecessor-version":[{"id":435,"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/430\/revisions\/435"}],"wp:attachment":[{"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=430"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=430"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/shivit.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=430"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}