How to Use a Purchase Order in Xero Without the Headaches
You've chased down the supplier invoice, the bank line's sitting there waiting, and the order in Xero is either missing details or never got raised in the first place. That's where a purchase order in Xero stops being admin fluff and starts saving real time, because it gives you a clear commitment before the bill lands. If you want a broader view of how this fits into UK bookkeeping, Receipt Router's Xero accounting software guide is a useful companion read, and SteadStack's purchase order guide is worth a look if you're comparing different purchasing workflows.
Why a Purchase Order in Xero Is Worth the Extra Click
A lot of freelancers only feel the pain when the invoice turns up a week later. The designer has approved a new software subscription, the printer's already shipped the stationery, or the contractor has said “yes, go ahead” in email, and now you're trying to remember what was agreed, what was delivered, and what should hit the books. A purchase order in Xero fixes that by turning the commitment into a formal record before the bill arrives, and Xero treats that order as a binding contract once the supplier accepts it. Xero also says the purchase order number is a unique identifier that suppliers can reference on invoices and shipping documents, which helps reduce matching errors and speeds reconciliation. See Xero's own guide on what a purchase order is in Xero.
PO, bill and invoice are not the same thing
In day-to-day bookkeeping, the difference matters. A PO is the promise to buy. A bill is the supplier's request to be paid. An invoice is what you send out when you're charging a client, including when Xero lets you turn a purchase order into an invoice to recoup costs on someone else's behalf, as its purchasing workflow explains. Xero's purchase order software also connects purchase orders, bills and invoices in one workflow, which is exactly why the document hierarchy matters instead of everything living in one vague “notes” field. Xero's purchase order software overview sets out that flow plainly.
Practical rule: if a supplier accepts the PO, treat it like a real commitment, not a placeholder.
For UK freelancers, the point isn't formality for its own sake. It's a clean trail from order to bill, especially when VAT-sensitive purchases need the right coding and the right record of what was agreed. That's where a PO gives you something an email thread never will. It keeps committed spend traceable, which is exactly what you want when a month-end reconciliation has to stand up to review later.
Building Your First Purchase Order in Xero
Open Business, then Purchase orders, then start a new PO from there. The screen is simple enough, but the fields you choose at draft stage decide whether the later bill is easy or annoying. A realistic example is an annual SaaS licence or a batch of branded stationery, because both tend to involve a clear supplier, a known tax treatment, and a delivery date you care about.
The fields that make or break the workflow
Start with the supplier contact. If the contact doesn't already exist, create it properly rather than improvising a near-duplicate name, because Xero auto-saves contacts and a sloppy setup tends to follow you into the bill. Then set the date and expected delivery date with care. Those dates matter because they tell you when the commitment was made and when you expect the goods or services to arrive.
The line items need equal attention. Use an item code if the product already exists in inventory, or an account code if you're coding directly to expenses. Xero's own training material makes clear that draft POs can be saved and completed later, and the workflow includes a real approval stage before the order is sent. Xero's purchase order training video shows that status flow in practice.
Get the coding right before you send it
The biggest practical issue is entry quality. Xero's guidance notes that the PO needs the correct supplier/contact, delivery date, tax treatment, and either an item code or account code on each line, because bad coding is hard to undo cleanly after approval. That's the point most small businesses miss. Once the PO is accepted and later turned into a bill, you're relying on the original structure to save time rather than create extra work. Xero's own explanation of data quality and auto-populated items backs that up in its purchase order workflow material.
Check the tax treatment at draft stage, not after approval. If the line is coded wrongly now, you're just moving the problem into the bill later.
For UK VAT work, that means slowing down long enough to confirm the right tax rate on each line before you hit submit. Get that right, and the bill matching process becomes routine instead of forensic. For a cleaner walk-through of the broader software pattern, the image of a PO sitting in a control workflow matters more than the click path itself.
Setting Up Approvals That Actually Help a Small Team
A purchase order approval doesn't need to feel like corporate red tape. For a one-person business, it can be a deliberate pause before spend gets committed. For a two-person shop, it becomes a real separation between the person who wants to buy something and the person who signs it off.
Keep the approval step lightweight
Xero's native purchase order workflow includes a draft stage and an approval stage before the order is sent. Users can also submit a PO for further approval before it goes out, so the control is built into the document flow rather than bolted on afterwards. That matters because the status change is visible, and the record shows whether a PO is still being checked or has been authorised. Xero's own materials describe the common status sequence as draft, awaiting approval, approved and billed in community and training content.
A useful habit is to attach the quote or statement of work to the PO record. Independent advice on Xero approval workflows leans on that for context, and it's good practice because approvers can see the commercial basis for the commitment. If you're using tracking categories, add the project or client context at the same time so the approval trail doesn't live in someone's memory. If you want a broader AP workflow, this accounts payable automation guide is a good reference point.
Use approval as evidence, not theatre
The point of approval is not to create a ceremonial click. It's to show who checked the spend, what they checked against, and why the PO was allowed through. That's especially useful for sole traders who need a paper trail without building a heavy process, and for small teams that need an actual control around supplier commitments.
Approval works best when the approver can see the quote, the line coding and the project context in one place.
A practical rule for small teams is simple. If the PO can't stand on its own with the quote attached and the lines correctly coded, it isn't ready to approve. Xero's approval flow is enough for that use case when the business is small and the process is kept disciplined. For more structured buying environments, the record should still stay readable when you come back to it later.
Converting a Purchase Order to a Bill and Handling the Awkward Bits
The easy part is the happy path. The supplier sends everything, you open the approved PO, and you copy it into a bill so the coding and descriptions carry through. Xero says you can turn purchase orders into bills for payment or into invoices to recoup costs, and its workflow is built to keep the order, the bill and the invoice connected without re-keying the same data. That makes matching much cleaner than typing a bill from scratch.
The bit most guides skip is partial fulfilment
The mess starts when only part of the order arrives. A stationery supplier might deliver half the order on Tuesday and the rest next week. Xero's own materials show the core workflow, but user discussions still revolve around partial fulfilment and how to handle only part of a PO without marking the whole order as fully billed. That tells you something important. The edge case is common enough that practitioners still search for workarounds.
The practical pattern is blunt but effective. Bill what has been received, then leave a clear trail for the remainder. In some cases that means updating quantities and closing the PO in stages. In others, it's cleaner to raise a follow-up PO for the balance so the original record stays honest. If you need a concrete comparison of matching logic, this invoice matching guide helps explain why consistency matters.
Converting to an invoice is different
If you're buying on behalf of a client and recharging the cost, Xero also allows a purchase order to become an invoice. That's useful in contractor and consultancy work where the original spend isn't yours in the commercial sense, even if you paid the supplier first. The key is to keep the reason clear in the record so the PO supports the client billing trail rather than muddying it.
Don't force one PO to pretend it was fully delivered if it wasn't. The cleaner move is to bill what arrived and keep the remainder visible.
For real-world stationery or software buys, the best practice is to keep the PO aligned with what was supplied. That protects your month-end reports and stops committed spend disappearing into a half-closed order.
Multi-Currency, VAT and Tracking Categories on Purchase Orders
A PO in Xero becomes more than a formal slip of paper. For UK businesses buying from overseas suppliers, the order needs to carry the right currency and the right tax treatment from the start. If it doesn't, the later bill and reconciliation work can get noisy fast, especially when the supplier's invoice arrives in a different currency from your base books.
Currency at order time matters
Xero's purchase order workflow supports multi-currency, and the exchange rate at order time is part of the practical control picture. That's important because the amount you commit to when you raise the PO may not match the amount you eventually see on the bill if the currency has moved. You want that reality visible in the record rather than buried in a later reconciliation surprise.
For UK freelancers and small businesses, that's especially useful when ordering services or software from overseas suppliers. The order tells you what you expected to spend in the supplier's currency, and the bill tells you what came through later. If you're handling a mix of domestic and international purchases, this multi-currency accounting guide is a useful companion because it frames the bookkeeping consequences without overcomplicating the process.
VAT treatment needs to be set line by line
VAT is where a lot of lightweight processes fall apart. The PO should reflect the correct tax treatment for goods versus services, and if you're dealing with imports or reverse charge situations, the line coding needs to match the transaction rather than the supplier's wording. Xero's guidance and workflow materials make the broader point clear, the PO is a structured accounting object, not a memo field. That means the tax choice on the line is part of the control, not an afterthought.
Tracking categories matter for the same reason. If you code the PO by project, department, or client, you can report on committed spend in the way the business works. Xero's reporting discussions also note that purchase-order data can be grouped and summarised by contact, item code and other dimensions, which is exactly what you want when you're trying to see where money is already spoken for.
A good PO records the commercial reality once, then lets the later bill inherit that structure.
That's the gain here. When the PO is coded well, the bill has less room to drift off course, and the month-end report has a better chance of reflecting what the business committed to spend.
Common Errors That Trip Up UK Freelancers Using Purchase Orders in Xero
The mistakes tend to be boring, which is why they keep happening. Someone sends a PO from the wrong contact, uses the wrong tax code, or leaves the order sitting in draft after the goods have already arrived. None of those are dramatic on their own, but each one makes reconciliation harder than it needs to be.
The same few mistakes cause most of the pain
A duplicate supplier contact is a classic trap. Xero will happily hold both versions if you let it, and then the invoice lands against the wrong record later. The fix is simple. Clean up the contact list and make sure the PO is raised from the correct supplier profile from the outset.
Another common issue is approving a PO with the wrong quote attached. That sounds minor until a supplier disputes the scope and you have to explain which version was authorised. If the attachment doesn't match the commitment, the approval record is weak. Keep the quote or SOW aligned to the exact order being sent.
There's also a reporting error people make by treating the PO like a bill. A PO is a commitment, not a creditor balance. If you post it mentally, or in a process, as though it were already a bill, you can end up double-counting or losing sight of committed spend. Xero's status-based workflow is there to stop that.
Use the status view instead of hunting through emails
The simple fix is to work from Xero's purchase order list by status. Xero materials describe operational stages like draft, awaiting approval, approved and billed, and that list view lets you see what's still open instead of relying on inbox memory. It's a small habit, but it stops orders being forgotten after they've been sent or approved.
If a PO's status doesn't match what happened in real life, fix the record before month-end, not after.
The same logic applies to supplier spend that's already been committed but not yet billed. Keep the ordered-versus-billed view tidy, and the surprise level at reconciliation drops sharply. That's the win, not pretty paperwork.
Tying Purchase Orders Into a Smoother Month-End Routine
A good PO habit should make the end of the month quieter, not busier. If the receipt or invoice lands in the right place and the PO has already been coded, approved and matched, you're not rebuilding the story from scratch later. That's the main reason I push small businesses to treat purchase orders as part of the month-end routine instead of a separate admin chore.
Pair the PO with receipt capture and clean filing
When a supplier bill comes in by email, the worst-case scenario is that nobody can tell whether it relates to an approved order, a one-off buy, or something that was already received last week. A disciplined PO flow avoids that. The order gives you the commitment record, then the receipt or invoice can be filed against the same job or supplier so the paper trail stays intact.
That matters even more when you're handling international purchases or mixed VAT treatments, because the source documents need to be easy to find again. Receipt capture tools help here because they keep the supporting document close to the transaction instead of scattered across inboxes and downloads folders. If you've ever spent a Friday evening digging through old supplier emails, you already know why that matters.
A simple weekly routine keeps the books cleaner
One practical rhythm is to review outstanding POs once a week, clear out stale drafts, and match new bills back to the approved orders. Xero's reporting and status structure support that kind of review, and it's far easier than doing a giant tidy-up at year end. That's also the point where you catch orders that were approved but never billed, or bills that arrived without the PO being updated.
Weekly habit: check what's still open, close what's complete, and question anything that sits in draft too long.
A few small rules make the whole process hum:
- Review open POs weekly: Keep an eye on anything still awaiting delivery or billing so committed spend doesn't drift.
- Attach support at the start: Add quotes, SOWs or project notes to the PO record before approval.
- Convert from the PO, not the inbox: Use the order as the source of truth when creating the bill.
- Close stale drafts: If the order won't proceed, tidy it up instead of leaving it hanging.
Used properly, a purchase order in Xero isn't extra admin. It's the bit that stops month-end from becoming a detective job.
If you want fewer lost receipts, cleaner supplier records and less faffing at reconciliation time, Receipt Router is built for exactly that kind of housekeeping. It helps UK freelancers and small businesses keep supporting documents organised so your Xero records line up with the paperwork, not a crowded inbox.