A Guide to the 4 Main Types of Purchase Orders

Many finance teams discover PO discipline the hard way, a vendor invoice arrives with no matching PO, no one remembers approving the purchase, and three people spend a week reconstructing what happened.

That’s the real cost of treating POs as a formality. A payment dispute, a budget overrun, an audit finding — all of them trace back to a moment when a verbal commitment was made and no document was raised.

A purchase order prevents that. This guide explains the four types and how to match the right one to each scenario.

What Is a Purchase Order?

A purchase order (PO) is a legally binding commercial document issued by a buyer to a vendor, specifying:

• The goods or services to be purchased
• The agreed price and quantity
• Delivery terms and expected date
• Payment conditions

Once accepted by the vendor, it constitutes a binding contract. For finance teams, it’s also the foundation of 3-way matching in accounts payable — the PO is matched against the goods receipt note (GRN) and the vendor invoice before payment is released. This control prevents unauthorised purchases, overpayments, and fraud.

The 4 Main Types of Purchase Orders

1. Standard Purchase Order (SPO)

A Standard PO is a one time order for a specific quantity of goods or services at a defined price, for a specific delivery date. The most straightforward type, used when you know exactly what you need, when you need it, and at what price.

Best for:

• One time equipment or asset purchases
• Event specific or project based services
• First time vendor orders
• Emergency purchases (formalise retroactively if needed)

Example: PO for 50 office chairs at ₹8,500 each, delivered to Bengaluru office by 15 March, with 30 day payment terms.

2. Blanket Purchase Order (BPO)

A Blanket PO establishes a long term agreement with a vendor for repeated purchases over a period, typically 12 months without specifying exact delivery dates or quantities upfront. The PO sets the price, terms, and maximum total commitment. Individual release orders are issued as actual purchases are needed.

Best for:

• Recurring consumables — stationery, cleaning supplies, packaging
• Cloud or SaaS services with variable monthly usage
• Staffing agencies for contract workers
• Any vendor you buy from more than twice a year

Key advantage: Locks in pricing in advance, eliminates the admin overhead of raising a new PO for every order, and gives finance real time visibility into committed spend against a ceiling.

Example: BPO with stationery supplier, up to ₹3L total over 12 months at agreed rates. Individual orders placed as needed without a new PO each time.

3. Contract Purchase Order (CPO)

A Contract PO defines the general terms and conditions of a supplier relationship — pricing frameworks, service levels, payment terms, liability clauses — without specifying quantities or delivery schedules. Individual orders are placed separately, typically via Standard POs that reference the CPO.

Best for:

• Large framework agreements with preferred suppliers
• Multi year service contracts where specific deliverables vary
• Enterprise software licensing
• Legal retainers and managed service arrangements

How it differs from a Blanket PO:

• A Blanket PO controls spend on a known, repeating category — same goods or services, variable timing
• A Contract PO governs a relationship where what you buy varies — it sets the rules, not the quantities

Example: Master CPO with a cloud infrastructure provider establishing rates, SLAs, and terms. Monthly orders reference the CPO without renegotiating each time.

4. Planned Purchase Order (PPO)

A Planned PO is issued in advance based on a production plan or forecast, specifying quantities and tentative delivery dates. Unlike a Standard PO, delivery dates can be adjusted as plans evolve. Unlike a Blanket PO, quantities per delivery are specified upfront. The vendor uses the PPO to plan production or capacity in advance.

Primarily relevant for: manufacturing companies, retailers planning seasonal inventory, and any business that needs to signal demand to vendors well in advance to secure materials or production capacity. Most Indian SMBs outside these categories will not need this PO type.

Best for:

• Manufacturing with known production schedules
• Seasonal inventory planning in retail or D2C
• Custom order goods requiring vendor capacity planning

Example: PPO for 10,000 units of custom branded merchandise, 3,000 units in April, 4,000 in June, 3,000 in September. Delivery dates firm only 30 days out, but quantities committed upfront so the vendor can plan production.

Choosing the Right PO Type: Quick Reference

Scenario	Recommended PO Type
One time purchase, specific quantity and date	Standard PO
Regular purchases from same vendor, variable timing	Blanket PO
Long term vendor relationship, varying deliverables	Contract PO
Advance commitment with flexible delivery scheduling	Planned PO
Emergency or urgent purchase	Standard PO (retroactive)
Recurring SaaS or services, fixed monthly fee	Blanket PO
Preferred supplier with negotiated rates across categories	Contract PO

Core Fields Every PO Must Include

These fields apply regardless of PO type. Missing any of them creates downstream problems in AP — either the invoice can’t be matched, or the payment creates a compliance gap.

1. Unique PO number: for invoice matching and audit trail
2. Vendor name, address, and GSTIN: mandatory for ITC claims
3. Vendor MSME status: determines whether the 45-day payment deadline under the MSME Development Act applies
4. Buyer entity name and billing GSTIN
5. Item description, HSN/SAC code, quantity, and unit price
6. GST breakdown: CGST/SGST for intra state, IGST for inter state
7. TDS section applicable: 194C for contractors, 194J for professional services, etc.
8. Payment terms and due date formula
9. Delivery address and expected delivery date or schedule
10. Authorised signatory and approval date
11. Terms and conditions reference

PO Management Best Practices

1. No PO, no pay. Implement this as policy with defined exceptions (utilities, rent, statutory payments). Without this rule, PO discipline degrades quickly as teams find it easier to skip the step.
2. Raise the PO before the verbal commitment. The moment a team member tells a vendor “we’ll take it,” the spend is real. The PO needs to exist before that conversation, not after the invoice arrives.
3. Set value based approval thresholds.
   • Below ₹5,000: no formal PO required
   • ₹5,000–₹50,000: single approver
   • Above ₹50,000: dual approval required Adjust thresholds to your business size, but document them clearly.
4. Review open POs monthly. POs raised but not yet received create uncommitted balance sheet liabilities. Regular review keeps your payables picture accurate and prevents phantom commitments accumulating at year end.
5. Flag MSME vendors at PO creation. If a vendor is MSME registered, the 45 day payment clock starts from invoice receipt. Your AP system should flag this automatically but it can only do so if the PO captures MSME status at the source.
6. Use Blanket POs for repeat vendors. The most common PO discipline gap in Indian SMBs is raising a fresh Standard PO every time an order is placed with the same vendor. A Blanket PO eliminates that overhead and gives finance better visibility into committed spend over the year.

How open.money Manages Purchase Orders

Open’s procurement module is built around the reality that PO discipline breaks down when the process is manual.

• All four PO types supported with configurable approval workflows
• Budget checks at PO creation: commits are visible to finance before cash leaves the account, not after
• Automatic 3-way matching: vendor invoices matched against open POs and GRNs without manual intervention
• MSME flag and payment SLA tracking: 45 day deadlines flagged automatically at the PO level
• Vendor digital PO delivery: vendors receive POs digitally and reference them in invoice submissions, enabling straight through processing
• Real time committed spend visibility: open PO balances visible across all vendors and categories, not just what’s been invoiced

Finance teams using Open’s PO module report a measurable reduction in invoice exceptions, because the matching data exists from the moment the PO is raised, not from when the invoice arrives.

Frequently Asked Questions

1. Is a purchase order legally binding in India?

Yes — once a vendor accepts a PO (either explicitly or by fulfilling the order), it constitutes a binding contract under the Indian Contract Act, 1872. This means both parties have enforceable obligations: the vendor to deliver as specified, and the buyer to pay as agreed. This is why PO terms matter they define what you are legally committed to.

2. What is the difference between a PO and an invoice?

A PO is issued by the buyer before the purchase — it’s a commitment to buy. An invoice is issued by the vendor after delivery — it’s a request for payment. In a well controlled AP process, every invoice should reference a PO. If an invoice arrives with no matching PO, that’s a control failure, not just an admin gap.

3. Do I need a PO for every purchase?

Not necessarily. Most businesses set a minimum threshold below which POs are not required, typically ₹5,000 for Indian SMBs. Recurring fixed costs like rent, utilities, and statutory payments are usually excluded. Everything above the threshold and outside the exclusion list should have a PO. The policy matters less than having one and enforcing it consistently.

4. What happens if we pay an MSME vendor late?

Under the MSME Development Act, 2006, payments to MSME registered vendors must be made within 45 days of invoice acceptance (or 15 days if no agreement exists). Late payment attracts compound interest at three times the RBI bank rate, currently around 15–18% per annum. Unpaid amounts must also be disclosed in your annual financial statements, which creates reputational and audit risk.

5. Can a purchase order be cancelled after the vendor accepts it?

It depends on the PO terms. Most POs include a cancellation clause specifying notice periods and any cancellation fees. Without such a clause, cancelling an accepted PO may constitute a breach of contract, exposing the buyer to a claim for damages. Always include a cancellation clause — especially on Blanket and Planned POs where the commitment extends over time.