A purchase order, or PO, is a document a buyer sends to a supplier to confirm an order. It states exactly what is being bought: the products or services, the quantities, the agreed prices, and the delivery date. Once the supplier accepts it, the purchase order becomes a binding agreement, created before any invoice exists.
That is the short answer, and for many people it is all they ever need. But a purchase order does a lot of quiet work behind the scenes. It tells the supplier precisely what to send, it gives your finance team a reference to check the invoice against, and it leaves an audit trail so that, months later, anyone can see who ordered what, at which price, and when. This guide explains the purchase order in clear terms first: what it contains, what a PO number is, the order in which the process runs, how a PO differs from a requisition and an invoice, the main types you will meet, and three-way matching. Then we will tell a short, real-feeling story about a business whose purchasing had quietly slipped out of control, and what changed when it was fixed.
A purchase order is a structured document, not a casual email. Whether it is printed, sent as a PDF or generated by software, a well-formed PO carries the same core information every time:
The point of all this detail is precision. When the order, the goods that arrive and the invoice that follows all reference the same purchase order, mistakes have nowhere to hide.
A PO number is the unique reference assigned to a single purchase order. It is the thread that ties the whole transaction together. The buyer generates it when the order is raised, the supplier quotes it on their delivery note and invoice, and the finance team uses it to match everything up before payment.
Think of the PO number as the order's name. Without it, a supplier invoice is just a request for money with no easy way to confirm it relates to something you actually ordered. With it, anyone can trace an invoice straight back to the original order, the prices agreed and the goods received. That single reference is why purchase orders make audits and disputes far simpler to resolve.
A purchase order is not a one-off document. It moves through a defined sequence from the moment a need is identified to the moment the supplier is paid. Understanding this flow is the key to understanding what a PO is for.
Three-way matching is the heart of the process. By confirming that what was ordered, what was received and what was invoiced all line up, it stops you paying for goods that never arrived or at prices you never agreed. If you want the operational detail on running this flow at volume, our guide on how to manage purchase orders at scale covers approval workflows, supplier pricing and reconciliation in depth.
These three documents are often confused, yet each does a distinct job and they appear at different points in the buying cycle. Getting the distinction clear is essential to understanding what a purchase order actually is.
A purchase requisition is an internal request to buy something. It comes first. A member of staff who needs stock or supplies raises a requisition, which goes to a manager or the purchasing team for sign-off. It never leaves the company. It is the business asking itself for permission to spend, before any supplier is contacted.
A purchase order is the external document sent to the supplier once the requisition is approved. It is the company telling the supplier, in writing, exactly what to provide and on what terms. The PO is created by the buyer, before the goods are delivered and before any invoice exists.
An invoice is the supplier's request for payment. It comes last. The supplier issues it after the goods or services have been delivered, and it should quote the purchase order number so the buyer can match it back to the original order. The simplest way to remember the order: the requisition asks internally, the purchase order instructs the supplier, and the invoice requests payment.
Not every purchase order is the same. The type you use depends on how often you buy from a supplier and how predictable the orders are. There are four common types.
For most small and medium UK businesses, the standard purchase order covers the bulk of buying, with blanket orders handy for regular, repeated supplies.
Here is the thing most people get wrong about purchase orders.
The myth: a PO is just admin. A bit of paperwork the accounts team likes, a hoop to jump through before you can buy the thing you already know you need.
The reality: the purchase order is often the only thing standing between you and paying for goods twice, paying for goods that never arrived, or paying a price nobody actually agreed. It is not paperwork. It is a promise in writing, and a record that the promise was kept. When a supplier invoice lands, the PO is what lets you answer one simple question with confidence: did we order this, at this price, and did it turn up? Without a PO, that question becomes an afternoon of phone calls and a leap of faith. With one, it is a thirty-second check.
That gap between myth and reality is exactly where money leaks out of growing businesses, and it is the best way to understand the story that follows.
Picture a Midlands distributor we worked with. Not a giant, around twenty staff, importing and reselling to trade customers across the UK. The kind of business that had grown faster than its admin.
For years, purchasing had lived in a spreadsheet and an email inbox. When someone needed stock, they emailed the supplier directly. Sometimes they raised a numbered order in the spreadsheet, sometimes they did not. The PO number, where it existed, was whatever the last person had typed plus one. Two people occasionally ordered the same line from the same supplier in the same week, neither knowing the other had done it.
The morning that prompted the call was a familiar one. A supplier invoice landed for a pallet of goods that nobody in the office could remember ordering. No PO number on it. No matching line in the spreadsheet. The owner spent half a day on the phone trying to work out whether they genuinely owed the money or whether it was a mistake, and in the end paid it because they could not prove otherwise. It was not the first time. It was just the time that finally felt like enough.
When we looked at how they bought things, the pattern was clear. There was no single approval step, so spend left the business before anyone with a budget had seen it. There was no reliable PO number, so finance could not match invoices to orders, which meant they could not catch duplicates or wrong prices. And because the goods coming in were never formally checked against an order, short deliveries went unnoticed until a customer complained.
The fix was not dramatic. We did not reinvent how they ran the business. We gave the purchasing process the structure it had been missing and put it inside a system. Every order now starts as a request that someone has to approve before it can be sent. Every order gets a unique PO number automatically, so there is no more guessing and no more duplicates. When goods arrive, they are checked in against the order. And when a supplier invoice comes in, the system matches it against the order and the goods received, three documents lined up, before anyone approves it for payment.
We are not going to put a number on what that saved, because honest answers do not always come with a tidy figure. But the qualitative change was obvious within a few weeks. The duplicate orders stopped, because the system would not let two people raise the same order blind. Invoices that did not match a purchase order stopped being paid on trust and started being questioned. The finance person stopped chasing paper across three inboxes to reconstruct what had happened, because the trail was already there, in one place, with the PO number tying it together. And that pallet-arrives-with-no-explanation morning simply stopped happening. If you want to see the kinds of operational problems we tend to fix, our success stories walk through more of them.
The point of the story is not that this distributor was badly run. It is that informal purchasing works right up until the day it does not, and by then it has usually been quietly costing money for a while. A purchase order, used properly, is the thing that closes that gap.
That story is a single example, but the underlying reasons are general. Purchase orders exist because trust on its own does not scale. When a business places a handful of orders a year, an email might be enough. As volume grows, informal ordering starts to leak money and create confusion. Purchase orders bring that under control in several ways.
They enforce approval, so spending is authorised before it happens rather than questioned afterwards. They create a clear audit trail, so every order has a documented owner, price and date that anyone can review. They prevent overpayment, because the three-way match catches invoices that do not agree with what was ordered and received. They reduce disputes, because the supplier and buyer are working from the same agreed document. And they give finance visibility of committed spend, so the business knows what it is on the hook for before the invoices land.
In short, a purchase order turns a verbal or email arrangement into a controlled, traceable transaction. That is why auditors look for them and why growing businesses adopt them.
Raising purchase orders by hand works until it does not. Once a business is placing dozens or hundreds of orders, spreadsheets and email start to creak: numbers get duplicated, approvals get skipped, and matching invoices by hand eats hours every month. The Midlands distributor is not unusual; most businesses hit this wall at roughly the same point.
This is where the right software earns its place, and it is the part of the problem we spend our days on. At Softomate we build ERP and operations systems, usually on Odoo, that take the purchasing flow described above and run it automatically. A proper system generates purchase orders when stock hits a reorder point, assigns the PO number, routes the order for approval, records the supplier's acknowledgement, checks goods in against the order, and performs three-way matching on the invoice without anyone rekeying figures. The audit trail is built in, and finance can see committed spend in real time.
For businesses outgrowing manual processes, an Odoo ERP implementation brings purchasing, stock and accounts into one connected system, so the purchase order stops being a standalone document and becomes part of a single, accurate flow. If purchasing is tangled up with stock control specifically, our warehouse and stock management software handles reorder points, goods-in and the link back to the PO. And for the modern angle on the supplier-invoice problem that started this story, we add AI document automation: an AI-ready ERP system can read incoming supplier invoices and purchase order PDFs, extract the figures, and line them up for matching, so the pallet-with-no-explanation morning is caught by the system rather than by a human reading every line.
None of this changes what a purchase order is. It simply takes the discipline a good PO process provides and makes it automatic, so the control holds up as the business grows. If you import or hold stock, two related reads are worth your time: our guide to working out true landed cost for UK importers, and a closer look at Odoo for UK wholesale distributors.
Yes, a purchase order becomes legally binding once the supplier accepts it. At that point it forms a contract between buyer and supplier, committing the buyer to pay for the goods or services and the supplier to provide them on the stated terms. Before the supplier accepts it, a PO is an offer rather than a binding agreement.
A purchase order is created by the buyer to order goods or services, while an invoice is created by the supplier to request payment for those goods once delivered. The PO comes first and sets out what is being bought and at what price. The invoice comes last and should quote the PO number so the buyer can match it back to the original order.
A PO number is the unique reference assigned to a purchase order. It identifies that specific order and links it to the supplier's delivery note and invoice, so finance can match the three documents and confirm the invoice relates to a genuine order before approving payment.
The buyer raises a purchase order, usually through a purchasing or procurement team after an internal purchase requisition has been approved. In smaller businesses, an owner, office manager or accounts person often raises POs directly. The supplier never raises the purchase order; they receive it and respond with an acknowledgement.
No, a purchase order is not the same as a receipt. A purchase order is issued by the buyer before goods are delivered to confirm an order, whereas a receipt is issued after payment to prove that a transaction has been completed. The two sit at opposite ends of the buying cycle: the PO begins it and the receipt closes it.
We protect the real names of all clients featured in examples and case studies. Every testimonial is from a real client.
More from the blog
Work with us
Book a free 30-minute discovery call with DD and get a personalised automation roadmap.
Softomate Solutions Limited
Deen Dayal Yadav
Online
We use essential cookies to keep the site running. With your permission, we also use analytics cookies to understand how visitors use our site so we can improve it. No data is sold. Privacy Policy
