Document Numbering: The Small Detail That Keeps Records Straight

Nobody chooses an ERP because of document numbering. It is also, reliably, one of the first things that causes trouble when it has been left informal — two invoices with the same number, a purchase order nobody can find, a challan referenced by three different labels in three departments.

It takes fifteen minutes to get right at setup and is genuinely painful to change later.

What good numbering does

A document number is not decoration. It is:

• A unique handle for referring to one specific document
• A sequence that reveals whether anything is missing
• A category marker that tells you what kind of document it is at a glance
• A compliance requirement, particularly for tax invoices

Manual numbering satisfies none of these reliably once more than one person is issuing documents.

A scheme that works

The pattern most businesses land on, and rarely regret:

SO-202608-0142
│    │      └── sequence within the period
│    └───────── year and month
└────────────── document type

Why each part earns its place:

Type prefix. SO, PO, GRN, DC, INV. Anyone reading the reference knows immediately what document it is — in an email, on a phone call, in a spreadsheet.

Period component. Year and month makes the age of a document obvious and keeps sequences a manageable length. It also resets naturally at boundaries, which matters for tax documents.

Zero-padded sequence. Four digits sorts correctly in every tool, including Excel — which matters more than it should, because your data will end up in Excel.

Rules worth following

1. Let the system generate them

Automatic generation from a defined series is the entire point. Manual numbering produces duplicates the moment two people issue documents on the same day. FlexgrewERP generates numbers from configurable document series per document type.

2. Never reuse a number

Even for a cancelled document. Cancel it, leave the number spent, and record why. A reused number destroys the audit trail exactly where you most need it.

3. Keep the sequence gapless

Gaps invite questions from auditors and hide genuine problems. If a document is voided, it should still exist as a voided record rather than vanishing.

4. Do not encode too much

It is tempting to put customer codes, branch codes and product categories into the number. Resist. Those belong in fields you can filter and report on. An over-engineered number becomes unreadable and breaks when the business changes.

5. Decide before go-live

Changing the scheme mid-year means your records split into "before" and "after" formats, and every historical reference needs explaining. Set it during implementation and leave it alone.

Special care for tax documents

Invoice numbering carries obligations beyond convenience. Sequences must be consistent, unique and traceable, and the number forms part of what is reported under GST e-invoicing. This is the single strongest argument for taking numbering out of human hands entirely.

The multi-location question

If you run several locations, decide deliberately between one continuous company-wide sequence and separate series per location.

Separate series make it obvious where a document originated and let locations operate independently. A single sequence gives you one clean chronological order company-wide. Either works — what causes problems is not deciding, and ending up with overlapping numbers issued from two places.

The payoff

Correct numbering is invisible when it works. You notice it only in the absence of a specific set of irritations: no duplicate invoices, no unfindable purchase orders, no arguments about which challan a customer means, no awkward gaps to explain during an audit.

Fifteen minutes at setup. Years of quiet.

See document series configuration alongside the rest of the settings — book a FlexgrewERP demo.