Purchase Order Management Guide for India

If your procurement team still tracks POs in Excel, you already know the pain. Someone edits the wrong row, a PO number gets duplicated, a vendor invoice doesn't match because the GSTIN was entered wrong three months ago. The PO looks like a simple document, but in India it's doing heavy lifting: TDS tracking, GST compliance, vendor payment reconciliation, audit trails. Get it wrong and you're exposed on multiple fronts.

This guide covers how Indian finance and procurement teams should actually manage purchase orders, from structuring the PO lifecycle to building approval workflows that don't slow you down, and making sure every order holds up under GST scrutiny.

What Is Purchase Order Management and Why It Matters

Purchase order management covers the full lifecycle: creating, approving, issuing, tracking, and closing POs. A purchase order is a legally binding document once accepted by the vendor. It specifies what's being supplied, in what quantity, at what price, and on what terms.

In India, POs carry extra weight beyond the operational basics:

• GST documentation trail: The PO sets the expected tax treatment (CGST+SGST for intra-state, IGST for inter-state) and HSN/SAC codes. These must match the vendor invoice for clean ITC claims
• Budget control: POs commit spend against approved budgets before the money actually leaves. That's forward visibility your finance team needs
• Contractual protection: Under the Indian Contract Act, 1872, a PO accepted by a vendor is a valid contract. Disputes over delivery, quality, or pricing? The PO terms govern
• Audit readiness: Tax authorities and statutory auditors routinely examine PO-to-invoice trails during GST assessments and income tax scrutiny

Anatomy of an Effective Purchase Order

A PO for Indian businesses needs to satisfy both operational needs and regulatory requirements. Here's what should be on every PO:

Essential PO Fields

• PO number: Unique sequential or system-generated identifier for tracking and reference
• Date of issue: Establishes the timeline for delivery and payment terms
• Buyer details: Company name, registered address, GSTIN, and PAN
• Vendor details: Supplier name, address, GSTIN (verified as active), PAN, and bank account details
• Line items: Description, HSN/SAC code, quantity, unit of measure, unit price (exclusive of tax)
• Tax breakup: Applicable GST rate per line item, CGST/SGST or IGST split based on place of supply rules under Section 10 of the IGST Act
• Delivery details: Ship-to address, expected delivery date, shipping terms
• Payment terms: Net payment days, early payment discount if applicable, TDS applicability
• Terms and conditions: Quality standards, return/rejection policy, warranty terms, penalty clauses

Place of Supply: Get This Wrong and ITC Gets Messy

Under Sections 10-13 of the IGST Act, 2017, the place of supply determines whether you apply IGST or CGST+SGST:

• Goods: Generally where the goods are delivered for consumption
• Services: Typically the location of the recipient (your registered address)
• Imports: Location of the importer: IGST applies and can be claimed as ITC

Get the place of supply wrong on a PO and you'll apply the wrong tax type. Fixing that after the fact (through refund applications or cross-utilisation) can take months. Better to get it right upfront.

Designing a PO Approval Workflow

Approving POs via email chain? That's how things fall through the cracks. The PO approval workflow needs to enforce controls without becoming a bureaucratic bottleneck. Here's what works:

Approval Hierarchy Best Practices

1. Value-based tiers: Up to INR 25,000: auto-approved against budget. INR 25,001 to INR 2,00,000: department manager. INR 2,00,001 to INR 10,00,000: department head plus finance. Above INR 10,00,000: CFO or procurement committee
2. Category-based rules: CapEx might need a different approval chain than OpEx, even at the same value
3. Budget check first, then approval: The system should verify budget availability before routing to a human. No point having a manager approve a purchase that'll blow the budget
4. Segregation of duties: The person raising the requisition can't be the sole approver. Auditors will flag this every time
5. Escalation timers: If an approver doesn't act within 48 hours, escalate. Purchase requests shouldn't die in someone's inbox because they're on leave

"Effective PO approval workflows have three things: value-based tiers, automated budget checks before human approval, and strict escalation rules. Drop any one of those and you'll either have weak controls or a painfully slow process."

Handling Amendments and Revisions

POs change. Quantities shift, prices get renegotiated, delivery dates slip. That's normal. What's not normal is changing a PO without a trail. Your workflow should:

• Keep full revision history with timestamps and who approved what
• Route amendments through the same (or stricter) approval chain based on the revised value
• Generate supplementary POs or amendments that clearly reference the original PO number
• Notify the vendor automatically with the updated document

PO Creation: From Requisition to Issued Order

Here's what the PO creation flow should look like when it's working properly:

Step 1: Purchase Requisition

Someone in operations needs something. They raise a requisition: what they need, why, estimated cost, preferred vendor (if any), and budget code. In a good system, they're picking from item catalogues with pre-populated HSN/SAC codes and approved vendors. That alone kills most data entry errors.

Step 2: Sourcing and Vendor Selection

For new requirements or big-ticket purchases, procurement issues an RFQ to multiple vendors. The system should let you compare quotations side by side: unit price, delivery timeline, GST registration status, payment terms, vendor compliance score.

Step 3: PO Generation

Vendor selected, requisition approved: the system generates the PO automatically. It pulls from the approved requisition, vendor master (verified GSTIN and PAN), item master (HSN/SAC codes), and agreed pricing. Zero re-keying.

Step 4: PO Dispatch and Acknowledgment

The PO goes to the vendor electronically. They acknowledge receipt and acceptance. That acknowledgment is important: it confirms the contractual commitment and starts the clock on delivery timelines. A PO accepted by a vendor is legally binding under the Indian Contract Act, 1872.

Purchase Order Tracking and Lifecycle Management

Creating a PO is the easy part. Tracking it from issue to close: that's where most teams lose visibility.

PO Status Stages

1. Draft: PO created but not yet submitted for approval
2. Pending Approval: Submitted and awaiting approval at one or more levels
3. Approved: All approvals obtained; ready for dispatch to vendor
4. Issued: Sent to vendor; awaiting acknowledgment
5. Acknowledged: Vendor has confirmed receipt and acceptance
6. Partially Received: Some line items or partial quantities delivered and GRN recorded
7. Fully Received: All goods/services received and GRN completed
8. Invoiced: Vendor invoice received and matched against PO and GRN
9. Closed: Payment processed, all matching complete, no further action required
10. Cancelled: PO cancelled before fulfilment (with cancellation reason and audit trail)

Three-Way Matching: The Core AP Control

Three-way matching compares the PO, the Goods Receipt Note (GRN), and the vendor invoice. It's the standard accounts payable control for a reason: it catches problems before money goes out the door. Flag discrepancies in:

• Quantity: Did the vendor invoice for more than you received? More than you ordered?
• Price: Does the invoiced unit price match the PO-agreed price? (Allow a small tolerance, say 1-2%)
• Tax: Does the GST rate on the invoice match the PO? This directly affects your ITC
• HSN/SAC codes: Must match between PO and invoice for proper GST classification

Common PO Management Challenges in Indian Businesses

Knowing best practices is one thing. Dealing with the real-world messiness of Indian procurement is another. Here are the challenges that trip up even well-run teams:

Challenge 1: Vendor GST Compliance Gaps

You onboarded a vendor six months ago. Their GSTIN was active then. But GST registrations get suspended or cancelled, and nobody tells you. Any purchases from such a vendor won't qualify for ITC. Your PO management software needs to re-verify GSTIN status at PO creation time, not just at onboarding.

Challenge 2: Multi-Entity, Multi-Location Complexity

Indian business groups often run multiple entities across states, each with its own GSTIN. A PO from your Karnataka entity to a vendor in Maharashtra? That's IGST. Same vendor, but PO from your Maharashtra entity? CGST+SGST. Get the entity wrong and you'll apply the wrong tax type. The ITC mess that follows can take months to sort out.

Challenge 3: Blanket PO / Rate Contract Management

Blanket purchase orders (rate contracts) are pre-negotiated agreements with vendors for recurring purchases over a set period at agreed rates. The challenge? Making sure individual POs raised against these contracts actually use the agreed rates and don't exceed committed quantities or values without proper approval.

Challenge 4: Goods Return and Credit Notes

When you return goods, the vendor must issue a credit note and reduce their GST liability. You must reverse the ITC you claimed. Under Section 34 of the CGST Act, credit notes must be issued before the return filing deadline. Your PO management needs to track returns against original POs and flag when credit notes are missing.

Where OneFinOps Comes In

OneFinOps handles PO management as part of its procurement platform, but the real value is in how compliance is woven into every step rather than checked after the fact.

When you create a PO, the system verifies the vendor's GSTIN in real time (not just at onboarding). It flags MSME vendors for 45-day payment tracking automatically. It checks TDS applicability under Section 194Q against running aggregate purchase totals per vendor. When invoices arrive, three-way matching runs automatically, and only exceptions need human attention.

For multi-entity businesses, OneFinOps applies the correct GST treatment (IGST vs. CGST+SGST) based on the buying entity's GSTIN and vendor location. You don't have to remember the rules: the system enforces them.

Wrapping Up

Every PO in India's GST regime is a compliance event. Every gap in your PO process (a wrong GSTIN, a mismatched HSN code, a missed MSME deadline) is a potential ITC loss or audit finding waiting to happen.

Take an honest look at how your team manages POs today. Where are the manual steps creating delays? Where are compliance checks missing? Where do you lose visibility into PO status? Fix those gaps with a system that handles the full PO lifecycle with Indian compliance built in, not patched on after the fact.