How to Number Invoices

An invoice number does one job: it lets two people looking at two different pieces of paper agree on which document they mean. Every choice about scheme, prefix and padding is in service of that job, and most of the ways numbering goes wrong are ways that job quietly stops being done.

Why the number matters

When a payment lands in your account with the reference “inv 214”, the number is what turns a bank line into a settled invoice. When a client's accounts department queries a charge six weeks later, the number is the first thing they quote, and if two of your documents answer to it, the conversation gets expensive. If you ever have to show a third party what you billed and when, the numbers are the index into that record.

There is also a compliance reason. Many tax authorities expect invoice numbers to run in a sequence with no gaps, precisely so the completeness of the set can be checked — an inspector who can see 101 through 140 with nothing missing knows the numbered series is complete. How strictly this is required, whether a voided number may simply be dropped, and how long you must retain the record all vary by country and sometimes by state. This page is general explanation, not tax or legal advice; before you settle on a scheme you will be living with for years, it is worth ten minutes with your own tax authority's guidance.

Four common schemes

• Plain sequential — 1, 2, 3, or padded as 0001, 0002. Easiest to audit, because a gap is visible at a glance. Its drawback is that the number is a public counter of how many invoices you have ever issued.
• Year-prefixed — 2026-001. The number tells you which year's records to open, and the counter resets each year, so it never grows unwieldy. The cost is that 001 recurs every year, so the year must always travel with it; never file or quote the tail on its own.
• Per-client prefixed — ACME-014. Convenient if you file by client and useful when a client asks for a history of their own invoices. But you now maintain one sequence per client rather than one overall, which makes a gap-free check harder to demonstrate and easier to get wrong when a new client arrives mid-year.
• Date-based — INV-20260812. Sorts correctly by default and needs no counter at all, which is why this site uses it as the fallback. It collides the moment you issue two invoices on one day, so it needs a suffix: INV-20260812-2.

Gaps and reused numbers

A gap is ambiguous. If 104 is missing, nobody reading your records — including you, in two years — can distinguish “never issued” from “issued and never recorded.” When an invoice is canceled, the usual practice is to keep the number and mark it void, or to offset it with a credit note, rather than reissue the number to something else. Which of those your jurisdiction expects is one of the things that genuinely varies.

A reused number is worse than a gap, because it fails silently. Two documents answering to INV-0042 means a payment can be allocated to the wrong one, a client who paid the first appears to have paid the second, and neither party can prove which is which from the number alone. If you discover a duplicate, a common fix is to reissue one of them under a fresh number and tell the client the old number is superseded — though jurisdictions that require a credit note for a cancellation may require one here too.

Do not encode more than you mean to

The number is printed on a document you hand to someone else, so treat it as public. An invoice reading INV-0003 tells the recipient you have issued three invoices in your life, which is information you may not want in the room during a rate conversation. The fix is not to start your counter at 1000 to look established — that is a small lie you then have to keep — but to pick a scheme that carries no headcount. Year-prefixed and date-based numbers both do this honestly. For the same reason, keep internal codes out: project margins, client rankings, and lead-source tags do not belong in a field the client reads.

Keep your own register

This tool stores nothing between visits, so it cannot number your documents sequentially. Leave the number field blank and it generates a date-based default — INV- for an invoice, RCT- for a receipt, QTE- for a quote — type one and yours is used instead. The default is date-only, with no collision suffix: two invoices built blank on the same date get the same number. It will not warn you about that, or any other duplicate, because it has never seen your other invoices.

That is a limitation of a tool with no account, not a feature; it is listed among the deliberate omissions on the methodology page, and the reasoning behind the no-account design is on the about page. So the register is yours to keep. A spreadsheet with five columns — number, date, client, amount, paid — is enough, and it is the thing you will actually reach for when someone asks which invoice a payment settled. Fill in the next number before you open the invoice generator, not after, so the register leads and the document follows. The number is one of the fields covered in what to put on an invoice.