Purchase Order Numbering: Formats That Scale

A well-designed PO number identifies the period, the branch or series, and the record itself in one string. It must sort numerically, resist duplicates, and be short enough to type into an invoice without error. Beauty is optional; those three functions are not.

The simplest is a plain running sequence: 0001, 0002, 0003. The most common Indian practice is a financial-year prefix: PO-25-0001, incrementing from April. A branch-stamped format adds the location: PO-BLR-25-0001.

Indian accounting and GST run on the April-to-March financial year, so a PO numbering that embeds the year makes every register sortable by period without a date column. PO-25-0001 instantly says 'the first PO of FY 2025-26'. Add the branch code when more than one location issues POs.

The two classic failures are shared spreadsheets and human memory. Give each branch its own block of numbers, or its own prefix, and never reset a sequence mid-year. If a PO is cancelled, keep the number in the register with a status mark — reusing cancelled numbers is how duplicate references silently appear.

The PO number is the key that joins the purchase record: instruct vendors to print it on invoices, record it on the goods-received note, and file the three together by PO number. A folder per PO number — PO, GRN, invoice — is the cheapest audit trail that exists.

Rekha's Delhi unit issues about twenty POs a month. Her register runs PO-25-0041 upward, and each entry stores fake-substance supplier name, amount, status and invoice reference. When GST is filed, the register subtotals the month's POs within seconds, and the open-PO column is her committed-spend forecast.

Avoid year suffixes that collide (25-0001 from last April and 26-0001 from April this year belong in different registers), leading zeros dropped by a spreadsheet, and vendor re-numbering on their own invoices. Fix all three by keeping the number in one master field and never retyping it by hand.

Without purchase software, the safest counter is a single workbook tab where the last number lives in one locked cell, and every new PO is created by a small routine that adds one. Two people opening the file at once is the risk; assign one person the numbering duty, or move the file to a drive that opens it read-only for everyone else.

A simple paper register — a ruled notebook with number, date, vendor and amount columns — remains surprisingly robust. It cannot be corrupted by a stray formula, and it is what the auditor can flip through on the spot when the accountant's laptop is not handy.

Some vendors ignore your PO number and print their own reference on the invoice. The fix is not to fight the vendor's internal system but to map it: keep a two-column cross-reference in the register — your PO number against the vendor's invoice number — and file by your own number.

When the vendor invoice carries neither number, the three-way match loses its key. Send the purchase order back with a one-line instruction: print our PO number in the reference field, or your invoice waits in the pending tray. Every procurement team learns this sentence quickly.

Moving from Excel to accounting software raises the classic question: restart the sequence or continue it? Continue it. The new system starts from your last number plus one, so the register stays continuous and no invoice ever carries a number that collides with an old one.

Tag the migration in the register itself — a note against the first system-generated PO such as 'first number under new software' — so the auditor does not spend a day explaining the break that does not exist.

A well-formed PO number gives an accounts clerk everything needed to answer most queries without opening a file: the year tells the period, the series code tells the branch or category, and the sequence tells the order within it. The habit of designing the number predictively pays off at every reconciliation.

Test your own format by reading five old POs from memory of the number alone. If any of the five needs a lookup to decode, the format is carrying too little or using codes nobody maps — simplify it before the register grows.

An alternative to per-branch prefixes is allocating each branch a fixed block of the shared sequence — Delhi 0001–1000, Mumbai 1001–2000. Blocks keep a single master sequence while giving each location its own run; the trade-off is watching for a branch finishing its block.

When a branch approaches its ceiling, allocate the next block and log it in the master register the same month. The discipline that kills this system is a branch that reuses its numbers instead of asking for more.

Beyond POs, a business often numbers multiple document types — POS, POs, and advance-payment notes. Keep each type on its own sequence, sharing the same format family so the register stays sortable: PO-25-0001 for purchase orders, POS-25-0001 for POS documents, ADV-25-0001 for advances. A shared sequence across types is how one PO and one POS hand each other duplicate references.

Numbering the forms in one family — same prefix length, same year position — is what keeps alphabetical, numerical and chronological sorting consistent across the whole purchasing archive.

The failures have fingerprint symptoms. A duplicated number shows as two vendor invoices carrying the same reference and a three-way match that keeps bouncing. A gap shows as a register that skips a number with no cancellation note. A reused cancelled number shows as a vendor invoice mapping to two POs. Each symptom points at the same root: the number was typed, not generated.

The fix is always the one control: centralise the counter so no number is ever created outside it. Everything else — the prefix, the branch code, the year — is design choice.

A seasonal business — festival supplies, harvest inputs, wedding-season goods — floods its sequence for a quarter and goes quiet the rest of the year. The quiet months are where the numbering discipline quietly decays, because the register sees so little traffic that nobody notices the dropped prefix.

Keep the sequence running in the quiet season too: issue the low-volume POs on the same counter, log the cancelled drafts, and reconcile the register once before the busy season starts. The register that survives the lull is the register that carries the rush without a duplicate.