Purchase Order: The Complete Guide

A purchase order is a document a buyer sends to a supplier that formally authorises a purchase and records exactly what has been agreed: the items, quantities, prices, and delivery terms. Once the supplier accepts it, the purchase order becomes a binding contract and the reference point for everything that follows, from delivery to payment. This guide explains what a PO is, how it differs from an invoice and a requisition, what one contains, the full PO process, and how automation removes the paperwork.

What is a purchase order?

A purchase order, or PO, is a commercial document issued by a buyer to a supplier that sets out the goods or services being purchased, the quantities, the agreed unit prices, and the terms of delivery and payment. It is the buyer's formal commitment to buy on stated terms, and it carries a unique number that ties together every later document in the transaction.

The PO exists to remove ambiguity. Before any money changes hands, both sides have a written record of precisely what was ordered and at what price, agreed in advance. That single reference prevents the most common disputes in buying: wrong quantities, unexpected prices, and deliveries that do not match what was intended. Everything downstream, the goods received note, the supplier invoice, the payment, checks back against the PO.

Because it is created by the buyer rather than the supplier, the PO puts the buyer in control of the commercial terms. It is the moment a loose intention to buy becomes a firm, documented obligation, which is why disciplined organisations insist that no significant spend happens without one. Sitting inside the wider procurement process, the PO is the pivot point where a decision to buy turns into an auditable transaction.

Purchase order vs invoice, requisition and contract

The PO is one of several documents in a purchase, and confusing them is a frequent source of error. Each is created by a different party, at a different stage, for a different purpose:

A purchase requisition is an internal request; it never leaves your organisation and simply asks for permission to buy. The PO is external and goes to the supplier. The invoice comes back from the supplier once goods are delivered, asking to be paid. A contract, by contrast, usually sits above individual orders and sets the terms for many POs over time.

The cleanest way to remember it: the requisition asks to buy, the PO agrees to buy, the invoice asks to be paid, and the contract frames the relationship in which all of that happens. Keep those roles distinct and the paperwork of purchasing suddenly makes sense.

What a purchase order contains

A good PO leaves nothing to interpretation. The exact layout varies, but a complete purchase order covers a predictable set of fields that together define the deal:

Alongside those core fields, a PO names the buyer and supplier, states any relevant terms and conditions, and increasingly carries a general ledger or cost-centre code so the spend lands in the right budget. The unique PO number is the thread that runs through the whole transaction: quote the number on the delivery note and the invoice, and matching becomes almost effortless.

Precision here pays for itself many times over. A vague line item invites the wrong product; a missing delivery date invites a late arrival; an omitted price invites a surprise on the invoice. The few minutes spent making a PO exact save hours of dispute later.

The purchase order process, requisition to payment

A PO is not a standalone document but one step in a controlled flow that runs from the first request to the final payment. The full cycle, often called procure-to-pay, moves through clear stages:

• Requisition. Someone raises an internal request to buy, which goes for approval.
• Approval. A budget holder checks the need, the price and the budget, then signs off.
• Purchase order. The approved requisition becomes a PO and is issued to the supplier.
• Acceptance. The supplier confirms the order, at which point the PO becomes binding.
• Receipt. Goods arrive and are checked against the PO; a goods received note is recorded.
• Invoice and match. The supplier invoices, the invoice is matched to the PO and receipt, and payment is released.

Each stage builds a record. By the time payment is made, you have an unbroken trail from the original need to the money leaving the account, with an approval attached to every step. That trail is what makes spending auditable and gives finance confidence that no payment happens without a documented reason.

The discipline of the cycle is its whole value. Skip the requisition and spend goes uncontrolled; skip the receipt check and you pay for goods you never got. The PO sits in the middle, converting an approved need into a formal order and setting up the match that protects the payment at the end.

Types of purchase order

Not every purchase suits the same kind of PO. Choosing the right type keeps the paperwork proportionate to the buying pattern:

• Standard PO. A one-off order where you know the item, quantity, price and delivery date. The most common type, used for defined, single purchases.
• Planned PO. A commitment to buy known items over time with estimated delivery dates that are firmed up later. Useful when you know what you need but not exactly when.
• Blanket PO. An agreement to buy up to an agreed value or quantity over a period, drawn down in releases. Ideal for repeat purchases of the same goods from one supplier.
• Contract PO. A PO that references an underlying contract governing terms, against which individual orders are then placed. It links day-to-day buying to a negotiated agreement.

The distinction matters most for recurring spend. Raising a fresh standard PO for every carton of the same consumable is wasteful; a blanket PO lets the team draw against a pre-agreed value without re-approving each time. Match the type to how you actually buy, and the PO becomes an enabler rather than a bottleneck.

Three-way matching and control

The single most important control the PO enables is three-way matching. Before an invoice is paid, three documents are compared: the purchase order (what was ordered), the goods received note (what arrived), and the supplier accounts payable invoice (what is being billed). When all three agree on quantity and price, the invoice is approved automatically. When they do not, the exception is flagged for a human to resolve.

This is where the discipline of raising a PO earns its keep. Without a PO there is nothing to match the invoice against, so accounts payable is reduced to trusting that the bill is correct. With one, every invoice is checked against an authorised order and a confirmed delivery, which blocks duplicate invoices, inflated prices and quantities that were never received. It is a quiet, systematic defence against both honest error and deliberate fraud.

Benefits of using purchase orders

Organisations that insist on POs are not adding bureaucracy for its own sake; they are buying a set of concrete advantages that loose, ad hoc purchasing cannot offer.

The first is control over spend. Because every PO is approved before it is issued, budget holders see commitments before the money is spent rather than discovering them on the invoice. That visibility turns procurement from a reactive scramble into a managed process, and it makes forecasting far more reliable because open POs show exactly what has been committed but not yet paid.

The second is protection. A PO is a written, agreed record of the deal, so disputes over price or quantity are settled by reference to a document both sides accepted, not by memory or email archaeology. Paired with three-way matching, it guards the payment at the end. The third is auditability: a complete PO trail satisfies auditors, supports clean financial reporting, and demonstrates that spending followed policy. To see how these controls fit a modern buying platform, explore the ProcureWave procurement solution.

Common purchase order mistakes

POs are simple in principle, which is exactly why they are often handled carelessly. The recurring mistakes are easy to name and easy to avoid:

• Buying without a PO. Off-system spend that is only discovered at invoice time defeats the whole point of the control and is impossible to match.
• Vague line items. A loose description invites the wrong product and a dispute the PO was meant to prevent.
• Skipping approval. A PO raised without a genuine sign-off is a rubber stamp, not a control.
• No receipt check. Paying against the invoice alone, without confirming what actually arrived, is how you pay for goods you never received.
• Losing the paper trail. POs, receipts and invoices scattered across inboxes cannot be matched or audited when it matters.

Almost every one of these traces back to treating the PO as paperwork to be rushed rather than a control to be respected. The organisations that get the most from purchase orders are the ones that make the discipline routine, so raising, approving and matching a PO is simply how buying is done.

Automating purchase orders

Running POs on paper or by email is slow and error-prone. Requisitions wait in inboxes for approval, POs are re-keyed from one system to another, and matching an invoice means hunting for the right PO and delivery note by hand. Every manual step adds delay and a chance to make a mistake, which is why e-procurement has become the norm for organisations of any size.

An automated system routes requisitions to the right approver, turns the approved request into a PO without re-typing, sends it to the supplier, and records the goods receipt against it. When the invoice arrives, the software performs the three-way match automatically and only surfaces the exceptions that need a human. What used to take days of chasing happens in minutes, and every step is logged for audit. A sourcing event, such as an RFQ, can flow straight through into a PO so the winning quote never has to be re-entered.

That is exactly what ProcureWave is built to do: connect requisition, purchase order, receipt and invoice into one auditable flow so spend is controlled and matching is automatic. If you want to see the purchase order process run end to end on your own buying, book a demo with our team.

The purchase order is one of the most important documents in buying because it is where an approved intention becomes a firm, auditable commitment. Get the PO right, make raising and matching it routine, and choose the type that fits how you actually buy, and you gain control over spend, protection against error and fraud, and a clean trail from the first request to the final payment.

Frequently asked questions

What is a purchase order?

A purchase order (PO) is a document a buyer sends to a supplier to authorise a purchase. It lists the items, quantities, agreed prices and delivery terms, and once the supplier accepts it, the PO becomes a binding contract between the two parties.

What is the difference between a purchase order and an invoice?

A buyer issues a purchase order before goods are delivered to authorise the order. A supplier issues an invoice after delivery to request payment. The PO says what was ordered; the invoice bills for what was supplied.

Is a purchase order a legally binding contract?

On its own a PO is an offer. Once the supplier accepts it, whether by confirming the order or by fulfilling it, the PO becomes a legally binding contract on the terms it states, which is why accurate wording matters.

What is three-way matching?

Three-way matching compares the purchase order, the goods received note and the supplier invoice before payment. When all three agree on quantity and price, the invoice is approved. Mismatches are flagged for review, which stops overpayment and fraud.

What are the main types of purchase order?

The four common types are standard POs for one-off orders, planned POs for known items with estimated dates, blanket POs for repeat buying against an agreed value, and contract POs that reference a wider supplier agreement.