Purchase Orders: The Complete Guide
A purchase order looks like a simple document — a few line items, a price, a date. It's also the single most important paper trail in procurement, the thing every invoice gets checked against before anyone gets paid. Here's everything worth knowing about it.
What a purchase order actually is
A purchase order is the document a buyer sends a supplier to formally place an order. It typically includes the items or services being ordered, quantities, agreed unit prices, delivery date, shipping terms, and a PO number that ties everything downstream — receiving, invoicing, payment — back to this one record. Once a supplier accepts a PO, it becomes a binding commitment on both sides: the buyer to pay the agreed amount, the supplier to deliver as specified.
Procurement teams typically issue a PO after a purchase requisition has been approved internally — the requisition is the internal ask, the PO is the external commitment that goes to the supplier.
PO vs invoice vs receipt: how they connect
These three documents get confused constantly, mostly because they show up at different points in the same transaction and look superficially similar. Here's how they actually differ:
| Document | Issued by | When | Purpose |
|---|---|---|---|
| Purchase order | Buyer | Before delivery | Formally places the order |
| Invoice | Supplier | After delivery | Requests payment |
| Receipt | Supplier | After payment | Confirms the transaction is complete |
Before payment is released, most procurement teams perform three-way matching: comparing the purchase order, the goods receipt note (confirming what actually arrived), and the invoice to make sure all three agree on quantity and price. A mismatch anywhere in that chain is exactly what this process is designed to catch, before money moves rather than after.
Blanket purchase orders
Issuing a brand-new PO for every single order from a supplier you buy from weekly is unnecessary overhead. A blanket purchase order solves this by setting a single agreement — a price, a spending cap, a time window (often a quarter or a year) — under which the buyer can place multiple individual releases without renegotiating terms each time. It's common for recurring categories like office supplies, maintenance services, or raw materials from a regular supplier.
The trade-off: a blanket PO needs active monitoring of remaining spend against the cap, or it can quietly get exceeded without anyone noticing until a release gets rejected or a supplier flags it.
How to track purchase orders
At minimum, a usable PO tracking system needs to answer three questions at a glance: which POs are open (issued but not yet fulfilled), which are overdue against their expected delivery date, and which have discrepancies waiting to be resolved at the invoice-matching stage. In a spreadsheet, this means consistent status columns and someone disciplined enough to update them after every status change — which works, until PO volume grows past what one person can keep current by hand.
That's the point most teams move to dedicated purchase order software: not because a spreadsheet is technically incapable of tracking a PO, but because it stops being reliably updated once volume and headcount grow past a certain point, and a stale PO tracker is worse than no tracker at all, since people trust numbers that are quietly wrong.
Purchase order management for small teams
A small business doesn't need an enterprise procurement suite to manage POs well. What it needs is a consistent numbering system, a single source of truth for PO status (not three people's inboxes), and a simple approval step before a PO goes out the door. Cloud-based PO tools built for smaller teams typically focus on exactly these basics — fast PO creation, clear approval routing, and visibility into what's open — rather than the deeper sourcing and contract-management features an enterprise buyer would need.
If you're weighing whether to move off a manual process, our procure-to-pay process guide covers where PO issuance fits into the fuller purchasing cycle, and what typically triggers a team to formalize it.
Common questions about purchase orders
A purchase order (PO) is a document a buyer sends to a supplier specifying the goods or services being ordered, the agreed price, quantities, delivery date, and terms. Once the supplier accepts it, it becomes a legally binding commitment to buy.
A purchase order is issued by the buyer before goods or services are delivered, stating what's being ordered. An invoice is issued by the supplier after delivery, requesting payment. The two are compared during three-way matching, along with a goods receipt note, before payment is released.
A blanket purchase order is a single agreement covering multiple deliveries or a set spending limit over a period of time, rather than issuing a brand-new PO for every individual order. It's commonly used for recurring purchases from the same supplier, reducing administrative overhead.
Many small businesses start with a numbered PO template in a spreadsheet or shared document, manually logging status and approvals. This works at low volume but tends to break down once a business is issuing more than a handful of POs per week, which is usually when teams move to dedicated purchase order software.
Editorial note
PO terminology and process detail can vary by industry and jurisdiction — some sectors add extra compliance steps to PO issuance. This guide reflects general commercial practice rather than any single regulatory standard.
Related procurement fundamentals
Purchase Requisition GuideInventory Management for ProcurementSourcing vs ProcurementThe Procurement Lifecycle