What Is a Purchase Order? A Plain-English Guide

What is a purchase order?

A purchase order is the buyer's official, written commitment to buy something on stated terms. It is issued before the goods arrive or the work begins, and it records what the buyer intends to pay for, in what quantity, at what price, and by when.

Two things make it more than paperwork. First, it is a control: because it is issued and approved before any money is committed, it is the point where a business decides whether a purchase should happen at all. Second, it becomes the reference everything downstream is checked against. When the goods arrive, the delivery is checked against the PO. When the invoice arrives, the invoice is checked against the PO. It is the benchmark for the whole transaction, and that is why the detail on it matters.

Purchase orders sit at the front of the procure-to-pay process, the full cycle from requesting a purchase through to paying for it.

What a purchase order contains

A complete purchase order carries enough detail that there is no ambiguity about what was ordered.

• PO number. A unique reference used to track the order through delivery, invoicing, and payment.

• Buyer and supplier details. Who is ordering, who is supplying, and the relevant addresses.

• Line items. Each product or service, described clearly, with quantity and unit price.

• Total value. The sum, including any tax and shipping treatment.

• Delivery details. Where the goods go, and by when.

• Payment terms. When payment is due, such as net 30.

• Issue date and any reference to the governing contract.

The last point is the one most often skipped and most often expensive. A PO that references the contract it sits under carries the negotiated terms with it. A PO raised from memory or from a price list does not, which is where overpayment begins.

The purchase order process, step by step

The PO process follows the same shape in most organisations.

Steps three and four are the control. Everything after them is verification

1. A need is identified. A team determines something needs to be bought.

2. A requisition is raised. An internal request captures what is needed and why.

3. The request is approved. The purchase is checked against budget and policy.

4. The PO is created and issued. A purchase order is generated and sent to the supplier.

5. The supplier accepts. On acceptance, the PO becomes a binding agreement.

6. Goods or services are delivered. The delivery is received and recorded, usually against a goods receipt.

7. The invoice is matched and paid. The supplier's invoice is checked against the PO and the receipt, then paid.

Steps three and four are where financial control actually lives. Everything after that is verification: confirming that what arrived and what was invoiced match what was approved.

Purchase order vs invoice vs sales order

These three documents describe the same transaction from different sides and at different moments, and they are routinely confused.

The clearest way to hold it: the purchase order is the request to buy, the sales order is the seller's confirmation that they will supply it, and the invoice is the request to be paid once they have. A purchase order never asks for payment, and an invoice never authorises a purchase.

Types of purchase order

Not every purchase suits the same kind of PO.

• Standard purchase order. A one-off order with all details known: items, quantities, prices, and delivery date.

• Planned purchase order. Items and prices agreed up front, with delivery dates confirmed later.

• Blanket purchase order. An agreement to buy up to a set value or quantity over a period, drawn down as needed. Common for recurring supplies.

• Contract purchase order. Agrees the terms with a supplier without committing to specific items yet, with individual orders raised against it later.

Blanket and contract POs are where control most often slips, because the commitment is made once and drawn against many times. Each drawdown needs the same checking the original received, and frequently does not get it.

Why purchase orders matter for control

A purchase order is the point at which spending becomes deliberate. Without one, a business finds out what it has committed to when the invoice arrives, which is far too late to do anything about it.

Three specific protections come from using POs properly. Budget control, because the spend is approved before it is committed rather than after. Verification, because there is a documented standard to check the delivery and the invoice against. And an audit trail, because every purchase has a record of what was approved, by whom, and on what terms, which is what an auditor asks to see.

Purchases made without a PO, often called maverick spend, bypass all three. They are difficult to budget for, impossible to verify against anything, and the first indication is usually an invoice nobody expected.

Where purchase orders go wrong

Even where POs are used consistently, the same problems recur.

• The PO does not reflect the contract. The negotiated rate sits in an agreement nobody opened, and the PO carries list price instead.

• Manual creation introduces errors. Quantities, prices, and item codes keyed by hand flow downstream into mismatched invoices.

• Blanket POs go unmonitored. Drawdowns accumulate past the agreed value without anyone noticing.

• Matching is partial or skipped. Under time pressure, invoices get paid without a proper check against the PO and receipt.

• POs are raised after the fact. A PO created to justify a purchase already made is paperwork, not control.

That first failure is the most costly and the hardest to see, precisely because nothing in the system looks wrong.

How automation handles purchase orders

Automation improves the PO process by removing manual keying and by making the matching checks happen on every invoice rather than when there is time. POs are generated from approved requisitions without re-entry, invoices are captured and matched automatically, clean transactions clear, and only genuine exceptions reach a person.

The step that matters most is what the invoice is matched against. 3-way invoice matching checks the invoice against the purchase order and the goods receipt, which is a real control. Checking it against the contract as well is what closes the gap described above, because it enforces the terms that were negotiated rather than the terms that happened to reach the PO.

Aviara Connect runs invoices and contracts on one platform for exactly this reason. Its Invoice-PO Reconciliation module uses multi-stage matching, direct field matching, fuzzy matching for partial data, and human-in-the-loop escalation when confidence is low, with credit memos generated automatically when a discrepancy is found. Because the agreements sit alongside the invoices, a negotiated rate that never reached the purchase order is still enforced at payment. In production, that approach has caught more than 100,000 dollars in overbilling that manual review had missed.

We've built AI in production at enterprise scale, including an AI search agent for NTPC, India's largest power company, serving more than 10,000 daily active users across finance, procurement, and HR, searching more than 10 GB of documents that include purchase orders and contracts. Aviara Labs is an AWS Certified Build Partner, Aviara Connect is listed on Microsoft Azure Marketplace, and we hold a 5.0 rating on Clutch and G2. For the wider buying cycle, our guide to AP automation software compares the platforms, or you can start a free trial.

Proof in production