How to Create a Purchase Order: A Practical Guide for 2026
2026-05-12
An invoice arrives for goods nobody remembers approving. The supplier says the order was agreed by email. The department head says it was urgent. Accounts payable can’t match it to anything in the ledger, and finance is left deciding whether to pay, dispute, or delay.
That’s where many teams are when they start looking up how to create a purchase order. They don’t really need a prettier template. They need a controlled way to buy, receive, match, and pay without guessing what was agreed.
A good purchase order does that job. It records the commercial agreement before money leaves the business. It gives operations clarity, gives finance an audit trail, and gives accounts payable the data needed to pay the right supplier the right amount through the right workflow.
Table of Contents
- Why a Purchase Order Is More Than Just Paperwork
- The Anatomy of a Perfect Purchase Order
- From Request to Approval The PO Workflow
- Common PO Pitfalls and How to Avoid Them
- Connecting POs to Accounting and SEPA Payments
- Automating Your Procure-to-Pay Process
Why a Purchase Order Is More Than Just Paperwork
It usually starts the same way. A manager needs something quickly, sends an email to a supplier, the supplier ships, and the invoice lands in accounts payable with no PO number, no approved budget code, and no clear owner. Finance then has to decide whether to block payment, chase approvals after the fact, or pay first and clean up the records later.
A purchase order, or PO, prevents that mess. It records what the business has agreed to buy, from which supplier, at what price, on what terms, and with whose approval. Once accepted, it becomes the reference point for receiving, invoice checking, coding, and payment.
The PO sits at the point where intention turns into commitment. If the handoff into a PO is loose, every downstream step gets harder. Goods can still arrive. Invoices can still be paid. But control weakens, matching slows down, and the accounting trail gets patched together after the event instead of built properly from the start.
### Why finance teams care about POs
Finance cares about POs because they set the structure for the rest of procure-to-pay.
Without a PO, buyers can commit spend before anyone checks budget, supplier terms, or approval limits. Accounts payable receives invoices with little context. Payment runs then depend on manual checks, email trails, and educated guesswork. That is how duplicate payments, coding errors, and supplier disputes creep in.
With a proper PO, finance gets a clear audit trail from request to approval to receipt to invoice. According to a 2021 CIPS survey, organisations using e-procurement tools are more likely to enforce internal approvals before a request becomes a PO, which helps reduce maverick spend, as discussed in this CIPS-focused review of e-procurement controls. In practice, the bigger benefit for SMEs is not just spend control. It is cleaner data. A well-built PO gives the invoice a matching reference, gives the ledger consistent coding, and gives the payment file the information it needs before month-end pressure starts.
Practical rule: If an invoice can arrive before a PO exists, the business is controlling cash after the purchase, not controlling the purchase itself.
### Why operations teams should care too
Operations teams feel weak PO discipline in different ways. Deliveries go to the wrong site. Partial shipments create confusion. Service work gets billed against vague descriptions that nobody can verify. If freight terms are unclear, the argument starts after the goods are already moving. That is one reason buyers handling cross-border or shipped goods benefit from understanding Incoterms 2025 before they raise the order.
For smaller businesses, this is often the point where informal buying either matures or starts causing repeat problems. The PO gives suppliers one agreed instruction and gives internal teams a shared record to work from. It also connects purchasing to the wider cash cycle. If you want a broader view of how purchasing, invoicing, and collections affect liquidity, this guide to accounts payable and accounts receivable for UK SMEs is a useful companion.
A good PO is not only a purchasing document. It is the data source that supports matching in the ledger and prepares the transaction for payment. For SMEs trying to automate accounting entries or generate accurate SEPA payment runs, that structure matters early. If the PO data is weak at the start, the fixes show up later in AP workload, payment exceptions, and month-end reconciliations.
## The Anatomy of a Perfect Purchase Order
A weak PO usually looks fine at first glance. It has a supplier name, a date, maybe a total. Then the trouble starts. The item description is vague, the delivery location is missing, and nobody can tell whether VAT, freight, or handling were included.
The best way to learn how to create a purchase order is to treat every field as a control point, not a box to fill.
### What must appear on the document
HM Revenue & Customs and Companies House guidance emphasise maintaining clear commercial records. A 2020 benchmark report found that this drives the inclusion of standard elements such as unique PO numbers, detailed line-item descriptions, and agreed payment terms in over 90% of UK purchase orders, as noted in this UK purchase order record-keeping summary.
At minimum, your PO should capture three groups of information:
-
Buyer and supplier details
Legal business names, addresses, contact names, and relevant reference details. If the supplier has multiple branches or trading entities, this needs to be exact. -
Order details
The PO number, date, item lines, quantities, units, prices, and any tax treatment. This is the core commercial instruction. -
Terms and fulfilment details
Delivery address, expected delivery date, payment terms, shipping terms, and any agreed conditions for partial deliveries or substitutions.
### Essential Fields for a Compliant Purchase Order
| Field Category | Essential Information | Purpose |
|---|---|---|
| Buyer information | Company name, address, contact name, email or phone | Shows who is placing the order and where queries should go |
| Supplier information | Supplier legal name, address, contact, account reference | Prevents orders being sent to the wrong entity or branch |
| PO reference | Unique PO number, issue date | Supports tracking, matching, and audit trail |
| Line items | Clear description of each item or service | Reduces delivery errors and invoice disputes |
| Quantity and unit | Number ordered and unit of measure | Avoids confusion between packs, units, hours, or licences |
| Pricing | Unit price, currency, subtotal, VAT treatment where relevant | Makes later invoice checking possible |
| Delivery details | Ship-to address, requested date, receiving contact | Ensures goods go to the correct location |
| Payment terms | Agreed terms such as net payment days and method | Sets expectations before the invoice is raised |
| Commercial notes | Any contract reference, service period, or special instructions | Captures context that may affect fulfilment or approval |
| Authorisation | Approver name, system approval, or status | Confirms the business has committed to the spend properly |
### Small details that prevent large disputes
The line description is where many teams go wrong. “Office supplies” is not a usable PO line. “A4 copier paper, white, five reams per box” is. The same applies to services. “Consulting support” isn’t enough. State the service period, scope, rate basis, and any milestone references.
If goods are moving across borders or the supplier is handling freight, delivery terms should also be explicit. Teams that buy internationally benefit from understanding who carries cost and risk at each stage. This explanation of understanding Incoterms 2025 is useful when you need the PO to reflect the correct shipping obligation.
A PO should be specific enough that a colleague could receive the goods, check the invoice, and approve payment without asking what the buyer meant.
## From Request to Approval The PO Workflow
At 4:45 p.m. on month end, a supplier invoice lands in accounts payable for goods the business already received. The buyer approved the spend in Slack, the manager agreed it was urgent, and the supplier delivered on time. Finance still cannot pay it cleanly because there is no approved PO, no budget coding, and no reliable way to match the invoice to what was ordered.
That is why the workflow matters. A PO process controls spend before commitment, and it creates the structured data that later feeds invoice matching, accounting entries, and payment runs.
### How the workflow should actually run
The process starts with a purchase requisition. That is the internal request to buy, raised before anyone places the order with the supplier. It should state what is needed, why the purchase is required, which budget will absorb the cost, when delivery is needed, and any supplier or contract context already known.
Then the request is reviewed by the right people in the right order. The line manager checks business need and budget. Procurement or finance checks whether the supplier is already approved, whether pricing or contract terms already exist, and whether the request should be grouped with other demand rather than bought ad hoc. After those checks, the PO is created, approved, and issued to the supplier.
That sequence prevents a common SME failure. Teams often treat the PO as something to produce after the fact, when the invoice arrives. By then, finance has lost its control point. It also loses the clean supplier name, coding, tax treatment, delivery reference, and payment terms that accounting systems and SEPA payment files rely on later.
This workflow is easier to grasp visually:
Approval levels should reflect financial risk and operational risk.
A low-value repeat purchase from an approved supplier may only need department approval. A first-time supplier, a service with unclear scope, a capital purchase, or any order with unusual payment terms deserves finance review before the PO goes out. In practice, good approvers are checking four things: do we need this, is the spend in budget, are the commercial terms acceptable, and will the downstream records be clean enough to process without manual fixes?
The Chartered Institute of Procurement and Supply has reported that internal approval steps are a standard part of controlled purchasing in organisations using e-procurement. That matters because approval is not just sign-off. It is the point where the business confirms the spend is authorised and the data is complete enough to move through receiving, invoice matching, accounting, and payment without rework.
A useful training aid for new team members is to walk through the process from request to issue. This short video does that well:
### What a disciplined workflow changes downstream
A good workflow reduces invoice exceptions because the supplier receives a clear PO before fulfilment. It reduces posting errors because the account code, VAT treatment, and approval trail are already in place. It also shortens payment preparation, especially where businesses are exporting supplier data into accounting software and then building SEPA payment batches from approved invoices.
That connection is often missed. If the requisition is weak, the PO will be weak. If the PO is weak, invoice matching becomes manual. If matching becomes manual, payment runs slow down and supplier queries rise.
For stock-driven businesses, purchasing discipline also depends on how replenishment is managed. Companies that want fewer stockouts with VMI often reduce the urgent, off-process buying that leads to missing approvals and poor PO records.
Good PO approvals protect cash twice. They stop unnecessary spend at the front end, and they give finance clean data for accurate posting and timely payment later.
## Common PO Pitfalls and How to Avoid Them
Organizations often don’t struggle because they lack a PO form. They struggle because the form is used inconsistently, approved too late, or treated as an administrative afterthought.
The result is avoidable friction across receiving, invoicing, and payment.
### The mistakes that cause most of the pain
The first hidden risk is the vague line item. If the PO says “materials”, the supplier may interpret that differently from the buyer. Receiving won’t know what to check, and accounts payable won’t know whether the invoice matches the order.
Another common problem is the duplicate or fragmented PO. Two people raise separate orders for the same need, or one request turns into several versions emailed around the business. When PO numbering isn’t centralised, finance loses visibility fast.
Then there’s the price that was never locked down. Teams assume the supplier will invoice what was discussed informally. If the PO doesn’t state the commercial agreement clearly, the invoice becomes the first clean record of price. By then, the advantage is lost.
The biggest accounting failure is weak matching. UK businesses using automated PO systems achieve a 92% on-time supplier acceptance rate compared with 67% for manual processes, and 34% of UK SMEs miss VAT recovery because POs are not matched to invoices correctly, based on this UK benchmark on PO process performance.
### How to tighten the process quickly
You don’t need a complex transformation project to improve PO quality. Start with these controls:
- Make descriptions auditable: Every line should tell receiving and accounts payable exactly what was ordered.
- Use one numbering logic: The PO number must be unique and generated from one controlled source.
- State commercial terms on the PO: Don’t rely on memory, inbox searches, or verbal agreements.
- Require the supplier to quote the PO number on the invoice: This is simple and removes a lot of matching friction.
- Stop retrospective POs: If goods are already delivered before the PO exists, the process has already failed.
One exception rule: If a purchase is urgent enough to bypass normal steps, document who approved the exception and why. Unrecorded urgency becomes a permanent loophole.
Manual processes can still work for low volume businesses, but they depend on discipline. Once transaction count rises, inconsistency spreads faster than people realise.
## Connecting POs to Accounting and SEPA Payments
A PO is only useful if its data survives the rest of the process intact. That’s where many SMEs run into trouble. Procurement raises the PO. Receiving confirms delivery. The supplier sends an invoice. Then someone in finance manually rekeys the details into the accounting system and banking file.
Each hand-off is a chance to introduce errors.
### Where procurement usually breaks down
The biggest gap isn’t usually drafting the PO itself. It’s the transition from approved purchase to payable invoice to bank-ready payment instruction.
A 2023 UK Finance report found that 42% of SMEs cite payment reconciliation issues as a top procurement pain point, and 28% experience SEPA format errors that cause bank rejections, as summarised in this analysis of purchase orders and payment reconciliation gaps. That’s a practical warning. If PO data isn’t structured properly from the start, later payment automation becomes fragile.
### Why three way matching matters
The control finance teams should aim for is three-way matching:
- The purchase order says what was authorised.
- The goods receipt note or service confirmation says what was received.
- The invoice says what the supplier is charging.
If those three records align, payment can move with confidence. If they don’t, the business should pause and resolve the discrepancy before releasing funds.
Many PO templates fall short. They’re written as ordering documents only, not as the first record in a payable transaction chain. Good PO data should carry through to ledger coding, invoice matching, and payment reference handling.
### What payment ready PO data looks like
For a PO to support SEPA payment preparation later, it should be clean enough that finance doesn’t have to reconstruct missing details. In practice, that means:
- Consistent supplier identity: The supplier name on the PO should match the accounting record.
- Clear amounts and tax treatment: Finance shouldn’t have to guess what the supplier will invoice.
- Usable references: The PO number and invoice reference need to map cleanly into payment and reconciliation workflows.
- Stable bank prep data: Payment teams often export approved items into batch processes. Dirty source data creates dirty payment files.
If your team is handling supplier runs in batches, it helps to understand how a SEPA batch payment file generator fits between approved payable data and the XML files banks expect.
A payment error rarely starts in the bank file. It usually starts much earlier, when the PO was too vague to support clean matching.
## Automating Your Procure-to-Pay Process
Manual purchasing doesn’t fail all at once. It fails one retyped supplier name, one missing PO reference, and one duplicate line at a time. The damage shows up later in invoice disputes, delayed approvals, duplicate payments, and month-end clean-up.
That’s why automation matters. Not because every SME needs a large ERP rollout, but because the hand-offs between requisition, PO, invoice, ledger, and payment need consistency.
Start with the points where staff re-enter data that already exists elsewhere. That usually means:
- PO creation from approved requests
- Invoice matching against PO data
- Export of approved payables into payment-ready files
- Validation of bank and reference fields before submission
With the 2026 MTD Phase 2 rollout, digital compliance becomes more important, and a BDO UK report from 2023 found that manual data entry had a 42% error rate, leading to significant duplicate payments, as cited in this overview of PO automation and digital compliance. That’s why connecting PO data to SEPA XML audit trails matters. It cuts down the places where people have to type the same information twice.
### A practical setup for SMEs
Not every business needs to replace spreadsheets tomorrow. Plenty of finance teams still work from Excel or CSV exports, especially when purchasing volumes are manageable and systems are mixed.
What works better is a staged setup:
First, keep the PO format standard. Second, make sure invoice approval retains the original PO reference. Third, export approved payment data in a controlled file structure. Then convert that data into the payment format your bank requires without manual rewriting.
Cloud finance stacks make this easier because they preserve data between systems more reliably. If you’re reviewing your wider setup, this explanation of the benefits of cloud bookkeeping for SMEs is a useful way to think about why connected records matter for daily finance operations, not just year-end reporting.
### What works better than manual rekeying
For many SMEs, the best short-term improvement isn’t a full ERP. It’s automating the bridge between approved finance data and the bank submission format.
That means using a process where Excel or CSV data can be mapped cleanly into SEPA XML, with validation before submission. Technical teams may take that further with APIs so the export, transformation, and payment file generation happen with minimal intervention.
A broader view of that model is laid out in this guide to procurement to pay, which is useful when you’re trying to connect operational purchasing discipline with actual cash movement.
Clean automation starts with clean source data. If the PO is inconsistent, the rest of the workflow only automates the inconsistency faster.
If your team prepares supplier payments from Excel, CSV, JSON, or older AEB banking files, ConversorSEPA is worth a look. It converts those files into valid SEPA XML for transfers and direct debits, supports API-based automation for technical teams, validates IBAN and bank data before submission, and helps finance departments reduce the manual rekeying that often breaks the procure-to-pay chain.
Frequently Asked Questions
- What is a purchase order and why does finance care?
- A purchase order records what the business agreed to buy, from whom, at what price, and with whose approval before goods or services are fully invoiced. It gives accounts payable a matching anchor for invoices and payments and reduces maverick spend, duplicate payments, and vague audit trails.
- What fields must a strong PO include?
- At minimum capture buyer and supplier identities, a unique PO number and date, clear line descriptions with quantities and units, pricing and tax treatment, delivery or service fulfilment details, payment terms, and evidence of authorisation. Vague lines like "office supplies" break receiving and invoice matching later.
- What is three-way matching?
- It aligns the purchase order, the goods receipt or service confirmation, and the supplier invoice before payment. When all three agree, payment can proceed with confidence. When they do not, finance should pause and resolve discrepancies rather than forcing a manual workaround at month end.
- How does PO quality affect SEPA payment files?
- Payment batches inherit weaknesses from upstream data. Inconsistent supplier names, missing references, or unclear totals force rekeying and export errors. Clean PO and invoice data flows more reliably into approved payable exports and validated SEPA XML, reducing bank rejections and reconciliation delays.
