Key Takeaways
- A purchase order (PO) is the buyer's official, numbered offer to buy specific goods or services at agreed quantities and prices. When the supplier accepts it, it becomes a binding contract.
- The PO is the first of the three documents — PO, goods receipt, invoice — that accounts payable matches before paying.
- A PO is not a requisition (internal request) and not an invoice (supplier's bill). It sits between them.
- The standard PO process runs in six steps: requisition, approval, PO creation, supplier acknowledgment, receipt, and matching to invoice.
- Clean, complete PO data is the single biggest driver of touchless invoice matching — AI cannot fix a PO that was wrong to begin with.
Purchase Order: The Definition
A purchase order is a buyer-issued document that formally requests goods or services from a supplier at agreed quantities, prices, and delivery terms. It carries a unique PO number that follows the order all the way to payment. Legally, a PO is an offer: the moment the supplier accepts it — by acknowledging it or by shipping against it — it becomes a binding contract on the terms the PO states.
That dual nature is why POs matter so much in procurement. They are simultaneously a control (nothing is bought without an approved, numbered order), a contract (the terms are enforceable), and a data record (the reference that ties together everything that follows). The PO is also the anchor for the entire downstream procure-to-pay flow and a core building block of the wider source-to-pay cycle.
What a Purchase Order Contains
POs vary by organization and system, but a complete one carries a predictable set of fields. The PO number is the most important: it is the key that links the order to its receipt and its invoice.
| Field | What it is | Why it matters |
|---|---|---|
| PO number | Unique reference for the order | Links PO, receipt, and invoice for matching |
| Buyer & supplier details | Legal entities transacting | Establishes the parties to the contract |
| Line items | Description, quantity, unit price | Defines exactly what is being bought |
| Total amount | Sum of line items plus tax/freight | The committed spend value |
| Delivery date & address | When and where goods are due | Drives receipt timing and follow-up |
| Payment terms | e.g. Net 30, early-pay discount | Sets when and how the supplier is paid |
| Terms & conditions | Referenced legal terms | The binding contractual terms |
When any of these fields is missing or wrong — a blank quantity, an outdated price, a missing PO number on the eventual invoice — the order falls out of automated matching and lands in a human's exception queue. That is the link between PO quality and AP efficiency.
The Purchase Order Process, Step by Step
Here is the standard lifecycle. Think of it as a numbered flow rather than a diagram.
- Requisition. A requester identifies a need and raises a purchase requisition — an internal request to buy. Nothing has left the building yet.
- Approval. The requisition routes through approval based on amount, category, and budget. Approval workflows are where policy is enforced.
- PO creation. The approved requisition is converted into a purchase order with a unique PO number and issued to the supplier.
- Supplier acknowledgment. The supplier reviews and accepts the PO. Acceptance is what turns the offer into a contract.
- Goods receipt. When the order arrives, receipt is recorded against the PO — the second document in the matching trio. The mechanics are covered in our note on the goods receipt note.
- Invoice matching and payment. The supplier invoices, and the invoice is matched against the PO and the receipt before payment. Our guide to AI three-way matching explains this control in depth.
The deeper mechanics — approval thresholds, exception routing, partial receipts — are unpacked in our dedicated purchase order process walkthrough. If you need a starting document, the purchase order template gives you a field-by-field structure to copy.
Automate PO creation and matching
See how AI-powered PO and invoice tools score on integration, accuracy, and ease of use in our independent directory.
Types of Purchase Order
Not every PO is a one-off. Four types cover most situations, and choosing the right one reduces administrative overhead.
- Standard PO. A one-time order for known items, quantities, and prices. The default for most discrete purchases.
- Planned PO. Items and prices are known, but delivery dates are estimated and confirmed via releases over time.
- Blanket PO. An agreement to buy up to a value or quantity over a period, drawn down by multiple releases. Useful for recurring, predictable spend.
- Contract PO. References an underlying contract for terms and pricing; individual orders are issued against it.
Blanket and contract POs are where the connection to sourcing shows up most clearly: a well-negotiated contract is worthless if buyers raise standard POs at list price instead of drawing down the blanket. This is the same compliance gap that strategic sourcing teams work to close.
PO vs Requisition vs Invoice
These three documents are constantly confused. The distinction is about who issues the document and when in the timeline.
| Document | Created by | When | Purpose |
|---|---|---|---|
| Requisition | Internal requester | Before approval | Ask permission to buy (internal) |
| Purchase order | Buyer | After approval | Offer to buy, sent to supplier |
| Invoice | Supplier | After delivery | Request payment for what was supplied |
In a sentence: the requisition asks, the PO commits, and the invoice bills. The PO is the pivot — it is the only one of the three that is both internal-facing (it acts on an approved requisition) and external-facing (it is a contract with the supplier).
Why Purchase Orders Matter
It is tempting to see POs as bureaucracy. They are actually the control that makes spend governable. Without POs, every purchase is an unstructured event with no pre-approval, no committed budget, and no document to match an invoice against — which is exactly how duplicate payments, overbilling, and maverick spend creep in.
"A purchase order is cheap insurance: a few minutes of structure up front in exchange for a clean audit trail, enforceable terms, and an invoice you can actually verify before you pay it."
POs also create the commitment data that finance needs. The moment an approved PO is issued, the organization has a known future liability — visibility that is impossible if buying happens through unstructured emails and corporate cards.
How AI Is Changing the Purchase Order
AI is not reinventing the PO, but it is removing friction around it. The most dependable applications today are narrow and verifiable: extracting line items from a supplier quote to pre-fill a PO, suggesting the right GL code or category, flagging a requisition that should draw down a blanket PO instead of creating a new standard one, and — most maturely — matching the eventual invoice back to the PO automatically.
The honest caveat is that AI inherits the quality of the PO data it is given. A platform such as Vic.ai or Stampli can lift touchless matching rates substantially, but only when the underlying POs are complete and the supplier puts the PO number on the invoice. Garbage POs produce exceptions no matter how good the model is. For where this fits the bigger picture, our source-to-pay AI market analysis looks at how PO and AP automation are consolidating into suites.
Frequently Asked Questions
What is a purchase order?
A purchase order (PO) is a buyer's official document that requests goods or services from a supplier at agreed quantities and prices. Once the supplier accepts it, the PO becomes a legally binding contract. It is the buyer's formal offer to buy, identified by a unique PO number used to track the order through to payment.
What is the difference between a purchase order and an invoice?
A purchase order is created by the buyer before a transaction to request goods or services; an invoice is created by the supplier after delivery to request payment. The PO states what the buyer wants to buy and at what price; the invoice states what the supplier is billing for. Matching the two — plus the goods receipt — is how accounts payable verifies a payment.
What is the difference between a purchase order and a purchase requisition?
A purchase requisition is an internal request asking for approval to buy something; it never leaves the organization. A purchase order is the external document sent to the supplier after the requisition is approved. The requisition starts the process; the PO acts on it.
What does a purchase order contain?
A standard PO includes a unique PO number, buyer and supplier details, line items with descriptions, quantities and unit prices, the total amount, delivery date and address, payment terms, and any terms and conditions. The PO number is the reference that links the order to its receipt and invoice.
Is a purchase order legally binding?
A purchase order becomes a legally binding contract once the supplier accepts it, either explicitly or by fulfilling the order. Before acceptance it is an offer. The binding terms are those stated on the PO and any referenced terms and conditions, which is why accurate PO data matters.
For the surrounding process, continue with our source-to-pay pillar and the full procurement blog, which connects the PO to sourcing, receiving, and payment.