Purchase Order Numbers: Formats, Numbering Rules and Examples
How to number purchase orders: what a PO number is for, common formats, the rules that keep a sequence clean, and examples for small and growing businesses.
A purchase order number looks like an administrative detail until it goes wrong: two orders with the same number, a supplier quoting a number nobody can find, an auditor asking why the sequence jumps from 1041 to 1047. A good numbering scheme takes ten minutes to design and saves those conversations for years.
What a purchase order number is for
A purchase order number is the unique reference the buyer assigns to each purchase order. It does three jobs:
- It links the documents. The supplier quotes it on the delivery note and the invoice, which is what lets accounts payable match the invoice to the order and the goods receipt in a three-way match, and clear the GRNI accrual line by line.
- It makes every order findable. When a supplier calls about "our order from last Tuesday", the PO number ends the search.
- It proves completeness. An unbroken sequence shows that no order was created and quietly removed. That is why auditors look at it.
The anatomy of a PO number
Most formats combine a fixed prefix, an optional context segment and a running counter:
Only the counter has to be unique. The prefix and context segments are there to make the number readable.
Common formats
| Format | Example | Good for | Watch out for |
|---|
| Plain sequence | 1048 | Very small volumes, one entity | Easily confused with invoice and quote numbers |
| Prefix + sequence | PO-01048 | Most small businesses | Choose enough digits up front |
| Prefix + year + sequence | PO-2026-0417 | Businesses that like a yearly reset | The counter must reset only together with the year |
| Prefix + year + month + sequence | PO-2610-031 | High volumes, monthly reporting | Longer numbers that suppliers mistype |
| Entity or site + sequence | LDN-PO-0217 | Several companies or sites | One counter per entity, never shared |
| Project + sequence | RIVER-0012 | Project-based businesses (construction, events) | Projects get renamed; the number should not change with them |
Rules that keep a sequence clean
Unique, always
Two purchase orders must never share a number, including across years if the year is not part of the format. If your counter resets every January, the year has to be in the number, otherwise PO-0001 of this year collides with PO-0001 of last year.
Generated by the system, not typed by people
Manual numbering from a spreadsheet works until two people raise an order at the same time. Let the system assign the next number when the order is saved. If you must allow manual numbers (for example while migrating from an old system), make the system reject a number that already exists.
No meaning that can change
Prefixes for document type, entity and year are stable. Department codes, buyer initials and supplier names are not: people move, departments merge and suppliers get acquired, but a number once issued can never change. Keep changeable information in the order's fields, where it can be filtered and reported on, rather than in its number.
Fixed length, zero-padded
PO-0417 sorts correctly next to PO-1048; PO-417 does not. Choose a counter length that will not run out: four digits covers 9,999 orders per reset period, five covers 99,999.
Distinct from every other document
Use a different prefix for purchase orders, requisitions, goods receipts and credit notes. A supplier who quotes "1048" on an invoice should not leave anyone wondering which document they mean. If you also use purchase requisitions, give them their own series.
Readable aloud
Avoid letters that look like digits (O and 0, I and 1) in the variable part, and keep the whole number short enough to read over the phone.
Gaps in the sequence
Auditors ask about gaps because a missing number can mean a deleted order. The cleanest answer is a system that never deletes an issued number: an order that is not needed is cancelled, not removed, so the number stays in the history with its reason.
Some gaps are harmless, for example a number reserved by an order whose save failed. They are easier to explain if the system only draws a number at the moment the order is actually created, after every validation has passed. If gaps cannot be avoided entirely, keep a short log of the known ones.
Changing your numbering scheme
Changing format is fine; reusing numbers is not. Start the new series at a clear boundary such as a new financial year, make sure the new format cannot produce a number that already exists in the old one (a new prefix guarantees it), and leave historic orders under their original numbers.
How Foxpedite handles it
In Foxpedite a company admin sets the format under Settings, Numbering. Numbers can be automatic or manual. An automatic format is built from segments (fixed text, the order date, the supplier code, the project, a custom field and a zero-padded counter) with a live preview of the next number, a start value and a counter that never resets or resets every year or month. A reset is only accepted when the format contains the matching date segment, which is the uniqueness rule above enforced by the software. The number is assigned when the order is saved, and in manual mode a number already used in the company is refused.
Common questions
Who creates the purchase order number, the buyer or the supplier?
The buyer. The purchase order is the buyer's document, so the buyer numbers it. The supplier quotes that number on its order confirmation, delivery note and invoice, and uses its own numbers for its own documents.
Is a purchase order number the same as an invoice number?
No. The purchase order number is assigned by the buyer when ordering; the invoice number is assigned by the supplier when billing. A well-formed supplier invoice carries both, which is what makes matching possible.
Should the purchase order number reset every year?
It can, as long as the year is part of the number. A yearly reset keeps numbers short and makes the year visible at a glance. A continuous sequence is simpler and avoids the question altogether. Either works; mixing them does not.
How many digits should a PO number have?
Enough that the counter will not run out within its reset period, with room to spare. Estimate your yearly order volume, multiply by ten for growth and use that many digits: most small businesses land on four or five.
The short version
Use a short prefix, an optional year or entity segment and a zero-padded counter. Let the system assign numbers, keep them unique for ever, keep changeable information out of them, cancel orders rather than deleting them, and give every other document type its own series.