Invoicing and Getting Paid

Invoice Numbering: Rules, Formats and Common Mistakes

Why invoice numbers must be unique and sequential, which formats work for one company or a group, how to handle voids and credit notes, and how to change systems without breaking the run.

Illustrative example with fictional data.

An invoice number looks like admin. It's actually the thread that ties an invoice to its payment, its VAT entry, its receipt and its audit trail. Get the numbering right and every one of those links is easy to follow. Get it wrong, with duplicates, gaps nobody can explain, or two companies sharing a sequence, and every later question takes longer to answer.

The three rules

1. Every number is unique. No two invoices from the same business share a number, ever, including invoices that were later voided.

2. Numbers run in sequence. Each new invoice gets the next number. Commentary on the 2025 tax reforms says VAT invoices are expected to carry sequential numbering and the supplier's business registration number, and the move to NRS e-invoicing makes a unique invoice number a basic field of every invoice record (Invoice Data Extraction). Treat this as the floor, and confirm the current requirements with your adviser as the NRS rules settle.

3. Gaps are explained, not hidden. If INV-2026-0412 was raised in error, it isn't deleted and reused. It's voided, and the void is recorded. A tax officer or auditor can live with a voided number. A missing one invites questions about what else is missing.

Formats that work

A good format is short, readable over the phone, and sorts correctly. Here are four common ones:

Format Example Good for Watch out for
Plain sequence 000418 Single, simple businesses Says nothing about year or company
Prefix + year + sequence INV-2026-0418 Most businesses Decide whether the sequence restarts each year
Company code + year + sequence ACL-2026-0418 Groups with several companies Each company needs its own run
Prefix + month + sequence INV-2611-031 High volume with monthly close Long numbers, more typing mistakes

Two practical tips:

  • Pad the sequence (0418, not 418) so invoices sort properly in spreadsheets and email searches.
  • Keep it free of meaning that might change. A format like INV-LAGOS-… breaks the day you open in Abuja.

Does the sequence restart each year?

Either choice is fine if you're consistent. INV-2026-0001 on 1 January is common and readable. A never-ending sequence (INV-004127) avoids any question of whether INV-2027-0418 and INV-2026-0418 might be confused. Pick one, write it down, and don't change it mid-year.

Several companies, several runs

If you run a group (say Adebayo & Co. Logistics in Ikeja, Adebayo Haulage in Trans-Amadi and AB Foods in Garki), each legal entity needs its own sequence. They're separate taxpayers with separate TINs, separate VAT returns and separate books.

Company TIN Next invoice
Adebayo & Co. Logistics Ltd 23456789-0001 ACL-2026-0419
Adebayo Haulage Ltd 23456790-0001 AHL-2026-0087
AB Foods Ltd 23456791-0001 ABF-2026-0233

Sharing one sequence across companies feels tidy, but it leaves every company with gaps it can't explain, because "the missing numbers belong to our sister company" is not something you want to defend in an audit. See our guide to multi-entity software for the wider picture.

Voids, credit notes and corrections

Situation What to do Don't
Invoice raised in error, not sent Void it; keep the number on record Delete it and reuse the number
Invoice sent, then the amount was wrong Issue a credit note referencing the original, then a correct new invoice Edit the sent invoice silently
Customer cancelled part of the order Credit note for the cancelled part Reissue the whole invoice under the same number

Credit notes usually get their own sequence (CN-2026-0012) and always reference the invoice they correct. That way the original invoice, the credit and the replacement can all be traced.

Changing systems without breaking the run

The riskiest moment for numbering is moving from spreadsheets or an old system to a new one. Avoid the two classic mistakes: restarting at 0001 and colliding with old numbers, or jumping to a new format mid-year without a note.

  1. Find the last number issued in the old system, and confirm nothing was raised after it.
  2. Decide: continue or change format. Continuing the old run is simplest. If you change format, change at a clean break, such as the start of a month, and note it.
  3. Set the new system's next number before anyone raises a live invoice.
  4. Stop raising invoices in the old system. Two systems issuing numbers in parallel is how duplicates happen.
  5. Write it down: "From 1 December 2026, invoices are raised in the new system, continuing from INV-2026-0418." One line in your records saves an hour of explanation later.

Our implementation checklist covers the rest of the switch.

Keep the records

The Nigeria Tax Administration Act 2025 puts weight on proper record-keeping and registration for taxable persons (KPMG; Mondaq). Keep every invoice, void and credit note, in number order, for the retention period your adviser confirms. An unbroken, explained sequence is the easiest evidence you have that your sales records are complete.

How Flux helps

Each organisation in Flux keeps its own numbering, so a group's companies never share a run. You can number by sequence or continue your existing legacy format, which makes switching systems a matter of setting the next number. An invoice raised in error can be voided, and the audit log records who did what to each invoice. See Invoicing & Billing.

This article is general information about Nigerian tax and employment rules as we understand them on 02 November 2026. It isn’t legal, tax or financial advice. Rules and rates change, and your situation may differ, so confirm with a qualified adviser or the relevant authority before you act.

Sources

  1. The Nigeria Tax Administration Act (NTAA) 2025 · KPMG Nigeria · accessed 02 November 2026
  2. The Nigeria Tax Administration Act (NTAA) 2025 · Mondaq · accessed 02 November 2026
  3. Nigeria VAT invoice requirements · Invoice Data Extraction · accessed 02 November 2026

From the blog