The first purchase order you write is oddly stressful. It looks like a simple form, but it is also a commercial commitment, an accounting record and the document your finance team will match an invoice against months from now. Get a field wrong and the consequences appear late, usually as a payment that cannot be approved. This guide walks through making a purchase order field by field, with a layout you can copy, the checks to run before it leaves your outbox, and what to do once it has.
Key takeaways
- A purchase order needs eleven core elements; everything else on the page is presentation.
- Line item wording and unit of measure cause more disputes than price ever does.
- Use one sequential number series with a prefix, and never reuse or skip a number.
- An order is only binding once the supplier acknowledges it, so always ask for confirmation.
What you are actually creating
A purchase order is a document issued by a buyer to a supplier that specifies what is being bought, in what quantity, at what price and on what terms. In legal terms it is an offer. When the supplier accepts it, the two documents together form a contract, which is why the detail on the page matters more than its appearance.
That is the part first-timers usually miss. You are not filling in a form for internal record keeping, you are stating the terms you want to buy on. If your PO says nothing about delivery date or payment terms, the supplier's own terms fill the gap, and their terms are written to suit them. The standard definition of a purchase order covers the commercial mechanics if you want the background.
This article deals only with making the document. The wider question of who requests, who approves and what happens after delivery belongs to the purchase order process, which sits around the document rather than inside it.
Gather these five things first
Most half-finished purchase orders stall because a detail was missing rather than wrong. Collect the following before you open a template, and the rest takes ten minutes.
- Supplier details: full legal entity name, registered address, contact person and email, plus any account or vendor number they have given you.
- A written quotation: ideally a current quote reference with prices, lead times and validity date. Copy from this, not from memory or a phone call.
- Internal approval: confirmation from whoever holds the budget that the spend is agreed, along with the cost centre or project code it belongs to.
- Delivery information: the exact site address, a named receiver, access notes and the date you actually need the goods, not the date you would like them.
- Tax and currency position: whether the supplier charges tax, at what rate, and which currency the order is placed in if they are overseas.
If any of these are unresolved, resolve them now. Writing a PO around an assumption bakes that assumption into the accounting record.
The purchase order layout, field by field
The table below is a working layout. Reproduce it top to bottom on your template, whether that template lives in a document editor, a spreadsheet or a procurement system. Nothing here is decorative.
| Field | What goes in it | Example | Why it matters |
|---|---|---|---|
| PO number | Unique sequential reference | PO-2026-00147 | The key everything else is matched against |
| Order date | Date the order is issued | 22 July 2026 | Starts lead times and payment clocks |
| Buyer details | Your legal name, address, tax number, contact | Northgate Ltd, Leeds | Tells the supplier who is legally committing |
| Supplier details | Their legal name, address, vendor number, contact | Harlow Components Ltd | Prevents orders going to the wrong entity |
| Delivery address | Site address, named receiver, access notes | Unit 4, Bay 2, c/o M. Shah | Where goods physically go, often not the billing address |
| Required date | Date goods or services are needed | 14 August 2026 | The only date you can hold a supplier to |
| Line items | Description, part code, quantity, unit, unit price, line total | See below | Defines exactly what is being bought |
| Subtotal | Sum of line totals before tax | 4,860.00 | The figure commitment reporting uses |
| Tax | Rate and calculated amount | VAT 20% = 972.00 | Must match what the invoice will show |
| Total and currency | Gross payable, currency stated | GBP 5,832.00 | Ambiguous currency is a real and costly error |
| Payment terms | When and how you will pay | 30 days from invoice date | Sets the terms before the supplier sets them |
| Delivery terms | Shipping basis, carriage, part delivery rules | Delivered, carriage paid, no part shipments | Decides who bears cost and risk in transit |
| Authorised by | Name, role, signature or system approval | J. Okoro, Operations Manager | Evidence the spend was properly sanctioned |
Two additions earn their space on most templates. A short terms and conditions block, or a line pointing to your standard terms online, closes the gap the supplier's own paperwork would otherwise fill. And a cost centre or project code field, tucked near the header, saves finance a guessing game later.
Numbering conventions that hold up
Purchase order numbering looks trivial until you have three sites each starting at 001. Keep it simple and keep it single.
One sequence, one prefix
Use a single series across the organisation, such as PO-2026-00147. A year segment helps with archiving; anything beyond that adds noise.
Never skip, never reuse
Gaps in a sequence are how missing or fabricated orders get spotted. If a PO is cancelled, mark it cancelled and leave the number in place.
Revisions, not replacements
Changes to a live order become Rev 1, Rev 2 against the same number, so the history stays attached to one reference.
Keep data out of the number
Supplier, department and category belong in reportable fields. Encoding them in the number means renumbering every time something is restructured.
If numbering is being issued by hand from a shared spreadsheet, agree one person or one file as the source. Two people allocating numbers simultaneously is the single most common way duplicates appear.
Writing line items that cannot be misread
Line items are where accuracy pays off. A price error is obvious and gets corrected; a vague description is fulfilled literally and arrives as the wrong thing.
Write each line so a stranger in the supplier's warehouse could pick it without asking a question. That means a part or catalogue code where one exists, then a description that includes size, grade, finish, colour or model as applicable. "Steel bracket" is not a line item. "Bracket, galvanised steel, 120 x 80mm, part GB-1208" is.
Unit of measure deserves its own sentence because it causes disproportionate damage. Ordering 10 of something priced per box when you meant per unit, or per metre when you meant per roll, produces a delivery that is wrong by a factor of ten and an invoice that technically matches the order. State the unit explicitly on every line: each, box of 50, metre, litre, hour, day.
For services, replace quantity and unit price with a clear scope and a basis of charge. A line reading "Site survey, Building C, fixed fee" with a stated deliverable and date is far easier to receipt against than "consultancy, 3 days". If you cannot describe what you will receive, you are not ready to raise the order.
Extend each line to a line total, then sum to a subtotal. Do the arithmetic in the tool rather than by hand, and check that the subtotal on your PO matches the quotation you copied from. A mismatch here is the first thing a supplier will query.
Tax, totals and terms
Tax on a purchase order should mirror what you expect the supplier's invoice to show. State the rate and the calculated amount separately from the net figure, because your finance system will want both. If the supplier is not registered for tax, or the goods are zero rated or exempt, say so on the order rather than leaving a blank that looks like an omission.
Currency is a one-word field that causes outsized problems when it is missing. Always print the currency code next to the total, particularly for cross-border orders where the same symbol means several different things.
Payment terms should state the trigger and the period, for example "30 days from date of valid invoice". Anchoring to the invoice date rather than delivery avoids arguments about when the clock started. Delivery terms should cover who pays carriage, who bears risk in transit, and whether part deliveries are acceptable. For international orders, an agreed shipping basis saves a great deal of negotiation after the fact.
The checks to run before sending
Spend two minutes on this list. It catches almost everything that would otherwise surface as an invoice query.
Confirm the supplier name matches the entity you hold banking details for, not a trading name. Check the PO number has not already been used. Re-read the delivery address and required date, which are the two fields most often copied from an older order and left unchanged. Verify prices against the quotation reference and confirm the quote is still valid. Recalculate the total, including tax. Confirm the approval you hold covers the final value, not the estimate you started with. Finally, check that the authorising name on the document is a person with the authority to commit that amount.
If any figure changed during drafting, go back to the approver before sending. Getting retrospective sign-off is always harder than getting it in advance.
Sending it and getting acknowledgement
Send the order as a PDF attachment rather than an editable file, from a monitored address, with the PO number in the subject line. Copy your own procurement or finance inbox so the order is on file somewhere other than your sent items. Where the supplier has a portal, use it, and still keep a copy.
Ask explicitly for written acknowledgement confirming price, quantities and delivery date. One line in reply is enough. If it does not arrive within a couple of working days, chase it, because an unacknowledged order is just a document you sent. Where the supplier acknowledges with a change, such as a later delivery date, treat that as a counter-offer: accept it in writing or push back, but do not leave it hanging.
What happens next
Record the order against the budget straight away so committed spend reflects reality rather than only what has been invoiced. File the PO, the quotation and the acknowledgement together; when a query lands in four months, those three documents answer it.
When the goods arrive, receipt them against the PO line by line, noting shortages or damage at the point of delivery rather than later. When the invoice comes in, match it to the order and the receipt before approving payment. Once everything is delivered, invoiced and paid, close the order so it stops appearing in open commitment reports.
Doing all of this on paper works until volume rises, at which point numbering, approvals and open order visibility become the bottleneck. ProcureWave handles that side quietly: sequential numbering, approval routing based on value, acknowledgement tracking and matching against receipts, so the person raising an order fills in fewer fields and gets fewer of them wrong. If you would like to see how that maps onto the way your team already buys, take a look at the ProcureWave solution or get in touch and we will walk through it with your own order template.
Frequently asked questions
What information must a purchase order contain?
At minimum: a unique PO number, the order date, the legal name and address of both buyer and supplier, a delivery address and required date, one line per item with description, quantity, unit of measure and unit price, any tax, the total value, the currency, payment and delivery terms, and the name of the person authorising it. Anything else is useful but optional.
How do I number my purchase orders?
Use a single sequential series with a short prefix, such as PO-2026-00147. Sequential numbering makes gaps visible, which is a basic fraud control. Avoid embedding supplier codes or department names in the number itself, because both change; put those in fields where they can be reported on instead.
Can I write a purchase order by hand or in a spreadsheet?
Yes, and plenty of small firms do. A handwritten or spreadsheet PO is legally just as valid once the supplier accepts it. The practical limits show up later: numbers get reused, versions diverge, and nobody can tell what is committed but not yet delivered. Most teams move to a system somewhere between twenty and fifty orders a month, and our purchase order programs guide compares the options.
Does a supplier have to acknowledge a purchase order?
Not automatically, but you should ask for it. A purchase order is an offer until the supplier accepts it, and written acknowledgement is what turns it into a contract on your terms. Without it you have no clear evidence of agreed price or delivery date if something goes wrong.
What do I do if the details change after the PO is sent?
Issue an amended version of the same PO number with a revision marker, such as PO-2026-00147 Rev 1, and get it acknowledged again. Never edit a sent order silently. If the change is large enough to breach an approval threshold, it needs re-approval before it goes out.
Want to see this in your own numbers?
Book a tailored demo and we will show ProcureWave running on scenarios that match your business.
Get in touch
