Purchase Order Number Format: How to Create PO Numbers
Jul 9, 2026
Jul 9, 2026
Convert a purchase order to Excel, CSV, or JSON
Submit your purchase orders
Drop documents here, or click to file
Up to 50 files per batch
Uploading...
A purchase order number is the unique identifier the buyer assigns to a purchase order when it is issued, and it is the reference every later document quotes back: the supplier's acknowledgment, the packing slip, the invoice, and the payment. There is no legally required format. A workable one is a short prefix plus a sequential number, such as PO-2026-00417, applied consistently and never reused.
Last updated July 2026.
The PO number only earns its keep if it survives the round trip to your supplier and back. If your orders come back to you as PDFs, upload one above and the PO number, supplier, and every line item come back as structured data in seconds, so nobody is re-typing a fourteen-character reference into a matching screen.
A purchase order number is a unique alphanumeric code the buyer creates and prints on the purchase order, used to track that order from issue through delivery to payment. It is not assigned by the supplier and it is not the invoice number. Its whole job is to be the one string that ties together every document, message, and ledger entry connected to a single purchase.
People also call it a PO number or, in shorthand on forms, "PO no." Whatever it is called, in accounts payable it is the key that makes matching possible. Quote it on the invoice and the bill can be tied to an order in seconds. Leave it off, and the invoice sits in a queue while somebody emails the vendor to ask which order it belongs to.
Most PO numbers combine a prefix, sometimes a date or entity code, and a sequential counter. Here are the formats US businesses actually use, and what each one buys you.
| Format | Example | Good for | Watch out for |
|---|---|---|---|
| Plain sequential | 00417 | Small businesses, low volume | Tells you nothing at a glance |
| Prefix plus sequence | PO-00417 | Any size; the safest default | None, this is the workhorse |
| Year plus sequence | PO-2026-00417 | Annual reporting and archiving | Decide up front whether the counter resets each year |
| Department or entity code | PO-MKT-2026-00417 | Multi-department or multi-entity groups | Reorganizations make old codes meaningless |
| Category or product line | PO-2026-ELEC-0100 | Buyers who report by spend category | Items often span categories |
| Date-stamped | PO-20260709-04 | High daily volume, easy sorting | Long, and error-prone to read aloud |
The pattern to notice is that every extra segment adds meaning and adds fragility. Encode a department into the number and you have to renumber when the org chart changes. Most teams settle on a prefix, an optional year, and a zero-padded counter, then keep the real detail in fields on the order rather than inside its identifier.
A good PO number format is short enough to read aloud over the phone, unique across the whole company, sortable, and zero-padded so it lines up in a spreadsheet. PO-2026-00417 satisfies all four. Avoid characters that get mangled in transit: no spaces, no slashes, no leading zeros stored in a spreadsheet cell that Excel will helpfully delete for you.
Three rules matter more than the exact shape you choose:
The buyer assigns it, at the moment the purchase order is created. Procurement or the person raising the order generates it, prints it on the PO, and sends the order to the supplier. The supplier does not create it, cannot change it, and is expected to quote it back on the order acknowledgment, the delivery note, and the invoice. The supplier's own sales order number is a separate reference on their side of the transaction.
Sequential numbering is the standard, and for good reason: gaps are visible. If POs run 00415, 00416, 00418, an auditor immediately asks what happened to 00417, and that question is the point. Sequences make missing or deleted orders obvious, which is a basic internal control. Random or hashed identifiers hide gaps and buy you nothing unless you have a genuine reason to obscure your order volume from suppliers.
Sequential does not have to mean guessable-from-nothing. Starting the counter at 1001 instead of 1 is a harmless convention many small businesses use so their first order does not look like their first order.
No. Within a single company, a PO number must be unique, permanently. Duplicates cause invoices to match against the wrong order, payments to be applied to the wrong commitment, and receipts to be booked against a line nobody ordered. The failure mode is quiet: nothing errors, the numbers simply stop meaning anything.
Two situations create duplicates in practice. The first is manual numbering in a spreadsheet where two people take the next number at the same time. The second is reusing numbers from canceled orders to "keep the sequence tidy." Both are worth designing out, which is what an automatic generator does.
Every real system generates the number for you, and locks it. QuickBooks auto-increments from the last purchase order and lets you set the starting value once. NetSuite and Sage use auto-numbering with a configurable prefix and counter. SAP uses number ranges assigned to a document type, so a standard PO and a stock transport order draw from different bands. Dynamics 365 Business Central uses number series with a code, a starting number, and an increment.
What they all have in common is a single point of issue, which is what guarantees uniqueness. If you are still numbering by hand in a spreadsheet, that is the first thing to change: not the format, the source. And when you issue orders that a counterparty needs to sign before work starts, it is worth having a clean way to send the document out for signature rather than chasing a scanned page back by email with the PO number half cut off.
On a well-formed supplier invoice, the PO number sits in the header block near the invoice number and date, usually labeled "PO Number," "Purchase Order," or "Your Reference." Some suppliers repeat it per line when one invoice covers several orders. Accounts payable reads it first, because it determines which purchase order and which goods receipt the invoice will be matched against in the three-way match.
If your supplier's invoices routinely omit it, that is a supplier onboarding conversation, not an AP problem. Make quoting the PO number a condition of payment in the order terms, and put it in bold on the face of the PO. It is the cheapest process fix in accounts payable.
No, and pretending otherwise creates a shadow process. Most companies set a threshold, for example any purchase over a few hundred dollars, above which a PO is required, and handle smaller spend on a corporate card or an expense claim. Recurring services under contract often run on a blanket PO covering a period rather than a new number per delivery, which we cover in blanket purchase order vs standard purchase order.
The test is whether anyone will need to match a future invoice back to a prior commitment. If yes, issue a PO and give it a number. If no, a PO number is paperwork for its own sake.
Pick a format today, write it down, and let your system issue the numbers. PO-YYYY-NNNNN with a five-digit counter that never resets covers almost every US business under a few thousand orders a year, sorts correctly in a spreadsheet, reads cleanly over the phone, and survives a system migration.
Then make sure the number survives the round trip. When a supplier returns an acknowledgment or an invoice as a PDF, the PO number has to get back into your system to be useful. Reading it off the page and typing it in is where the digits get transposed, and a transposed PO number is functionally a missing one. Extracting the document instead, whether through AI purchase order software or a direct purchase order API call, keeps the reference intact from issue to payment. If you are new to reading these documents, start with how to read a purchase order, and if you are setting one up from scratch, how to create a purchase order walks through the fields.