Number invoices with a simple ascending sequence, starting wherever you like — 1001, 1002, 1003 — and never reuse or retrospectively change a number once the document has left your hands. A prefix and a year are optional refinements; the uniqueness is not.
The three properties that matter
Every workable scheme has these. Every problem comes from losing one of them.
- Unique. One number identifies exactly one document, forever. This is the only property that some jurisdictions turn into an explicit rule — the UK, for instance, requires a unique identification number on every invoice.
- Ordered. A higher number means a later document. It lets you and anyone reviewing your records tell at a glance whether something is missing.
- Stable. Once a document has been sent, its number is fixed. The customer has filed it under that number; their accounts system may already reference it.
Three schemes that work
| Scheme | Looks like | Suits | Watch out for |
|---|---|---|---|
| Plain sequential | 1001, 1002, 1003 | Almost everyone. The default for a reason. | Nothing, really. Starting at 1001 rather than 1 is purely cosmetic. |
| Prefixed sequential | INV-0042, EST-0007 | Anyone issuing more than one type of document, or filing a lot of PDFs. | Keep the sequences separate, or an estimate will consume an invoice number. |
| Year-prefixed | 2026-014, 2026-015 | Seasonal work, or anyone who files by year and wants the year visible. | Decide in advance whether the counter resets each January. Then never change your mind. |
Padding — 0042 rather than 42 — costs nothing and makes filenames sort correctly in every file browser you will ever use. Four digits is plenty; a scheme that runs past 9999 can simply keep counting.
The scheme to avoid: customer codes
Sooner or later someone suggests ACME-001, ACME-002, BRIGHT-001. It reads well and it falls apart quickly.
- You now maintain one counter per customer, which is where duplicates come from.
- The numbers no longer tell you what order you issued things in, so a missing document is invisible.
- Customers get renamed, acquired, or turn out to be two entities that share an office.
If you want the customer visible, put them in the filename — Invoice-1042-Acme.pdf — and leave the number itself as a plain sequence.
Why changing a number afterwards causes trouble
This is the one genuinely damaging mistake in the topic, and it usually happens with good intentions: you spot a gap, or a typo, and tidy it up.
By then the document may exist in three other places. Your customer has filed a PDF under the old number. Their finance system has it against a purchase order. Their payment reference quotes it. When their payment arrives referencing 1042 and your records only contain 1041 and 1043, someone spends an afternoon working out what happened.
Two documents sharing a number is worse still, because “invoice 1042” stops identifying anything. If you need to correct an invoice that has already gone out, issue a new document with the next number and reference the original on it. Do not rewrite history.
Estimates need their own sequence
If you quote before you work, keep the two counters apart. Estimates have a much lower conversion rate than invoices — plenty are sent and never accepted — so running them through one shared sequence produces an invoice numbering full of holes that correspond to jobs that never happened.
Two independent sequences means your invoice numbers stay tight and your estimate numbers can be as gappy as reality requires. More on the two documents in invoice vs estimate.
Starting from an existing sequence
Moving from a spreadsheet or a pad of carbonless forms? Do not restart at 1. Continue from wherever you got to, so your records read as one continuous history. If your old numbers were inconsistent, pick the highest number you ever issued, round up, and start the new scheme cleanly above it — the discontinuity is obvious, explicable, and only happens once.
The number is one of eight elements a complete invoice carries; the rest are here.
Sources
Requirements around numbering — particularly whether a sequence may contain gaps — are set by the tax authority where you trade, and differ. Check yours.
- GOV.UK — Invoicing and taking payment from customers — what invoices must includeThat UK invoices are required to carry “a unique identification number”.
- Federation of Tax Administrators — State tax agenciesWhere US readers can check whether their own state imposes any numbering or record requirements.
