Your invoice number is a legal audit trail, not just a label. Here's how the three main schemes work, which one suits your situation, and the mistakes that create headaches at tax time.
Most freelancers pick an invoice number by typing 001 on the first invoice and never think about it again — until a client's accounts-payable department rejects a duplicate, or a tax audit asks why there's a gap between invoice 47 and invoice 51. The number itself doesn't matter. The scheme matters. Pick it deliberately before you issue your first invoice and you won't have to untangle things later.
Three schemes cover probably 95% of use cases. Here's what each one actually looks like in practice, where it breaks, and when to reach for it.
1. Pure serial: the simplest thing that works
Serial numbering is just counting: 1, 2, 3, …, 1000. Or zero-padded: 0001, 0002, etc. That's it.
The appeal is obvious — it's unambiguous, every invoice has exactly one place in sequence, and any gap is immediately visible. Tax authorities love it for this reason. The UK's HMRC, for example, doesn't mandate a specific format but does require that VAT invoices carry a sequential number that "creates a unique and unbroken sequence." Pure serial satisfies that requirement with zero effort.
The downside: a bare number tells you nothing at a glance. Invoice 843 — is that from last month or three years ago? Fine when you have 20 clients; annoying at 200. And if you ever need to restart the sequence (new business entity, new accounting software), you need a clean break — which means your numbering history has a discontinuity that could raise questions even if it's perfectly legal.
Best for: solo freelancers, new businesses, anyone who wants accounting software to handle the incrementing without thinking about it.
2. Date-based: fast lookups, some risks
Date-based schemes embed the issue date into the number — 20240315-001, 2024-03-0042, or the shorter 240315-01. The sub-sequence (the -001 part) resets at whatever date boundary you choose: daily, monthly, or yearly.
The payoff is that the number is self-documenting. 2025-06-003 tells your client (and you) exactly when the invoice was raised, without opening a spreadsheet. Monthly sub-sequences also keep numbers short: invoice 6 of June is 202506-006, not 001892.
The risk is the reset. If you reset monthly and issue 12 invoices in January, then client A's AP system might already have a 202501-003 from another supplier — and your 202501-003 gets flagged as a duplicate. Adding a client or project prefix (see below) solves this, but then you're in hybrid territory.
There's also a sequentiality question: if you issue 202506-001 and 202506-002 in June, then in July you start at 202507-001, there's an implicit "gap" between June's last invoice and July's first. This is fine — it's a new date bucket — but it's worth documenting your scheme so it's clear the gaps are structural, not missing invoices.
Best for: agencies or consultancies billing many clients per month, businesses that need fast lookup by date, situations where clients might ask "what did we pay you in Q3?"
3. Prefix schemes: multi-entity and multi-client clarity
Prefixes attach a code to the front of a sequential counter — usually a client code, project code, year, or entity identifier: ACME-2025-041, PRJ-REBRAND-007, UK-2024-0156.
This is the scheme large companies and agencies with multiple legal entities reach for. If you run two businesses — say, a consultancy and a product company — keeping their invoice sequences separate under prefixes (CONS- vs PROD-) keeps your accountant sane. Similarly, if you have a retainer client and want their invoices to run in their own series for easy reconciliation, a per-client prefix handles that cleanly.
The trap: complexity multiplies. You now have N sequences to track rather than one. Lose track of where ACME- is up to, issue ACME-041 twice, and you've created an audit problem. This is manageable in software but painful in spreadsheets.
Prefixes also interact with international clients. Some jurisdictions require invoice numbers to be purely numeric — Romania and some Central European tax authorities, for instance, are stricter about format than the UK or US. If you invoice cross-border, check the rules before embedding letters.
Best for: multi-entity businesses, agencies with client-separated billing, anyone whose accounting software enforces per-series sequences.
What the IRS and HMRC actually say
"A tax invoice must have a unique identifying number that follows a sequential pattern."
— HMRC VAT invoice requirements (UK Government, Open Government Licence v3.0)
The US IRS doesn't mandate a specific invoice numbering format for most businesses — there's no federal requirement for a sequential number on a standard invoice. But IRS Publication 583 advises that your records must be "accurate, permanent, and complete," and sequential invoice numbers are the simplest way to demonstrate completeness under audit. The moment you can't account for a gap, you're explaining yourself.
The EU VAT Directive (Article 226) requires that invoices include "a sequential number, based on one or more series, which uniquely identifies the invoice." Note: "one or more series" is the explicit legal basis for prefix schemes in EU member states. You can have multiple numbered series as long as each series is internally sequential.
The gap problem — don't fudge it
Gaps happen: a client cancels before payment, you void a draft that got a number assigned, accounting software skips a number on a failed transaction. Don't renumber to close the gap — that's worse than the gap itself.
Instead, issue a voiding note against the gap number and keep it in your records. Invoice 047 — VOID, never sent — [date] is a perfectly defensible record. What isn't defensible is invoice 46, then invoice 48, with nothing explaining what happened to 47. Tax authorities are trained to spot this pattern; they'll assume you're hiding a transaction.
Picking your scheme — the one-line rule
If you can explain your invoicing sequence to an accountant in one sentence, it's probably fine. "I number invoices sequentially from 1, year-resetting January 1st, prefixed by the two-letter client code." Clear. Auditable. Defensible.
If the explanation takes a paragraph and includes "it depends," simplify before you issue more invoices.
For most solo freelancers: pure serial with a year prefix (2025-001, 2025-002, …) hits the sweet spot — date context without the reset complexity of monthly sub-sequences. For agencies with multiple clients: a client-code prefix on a per-client serial. For multi-entity businesses: per-entity series with distinct prefixes.
Whatever you pick, set it before invoice 1 and stick to it. Our invoice generator lets you set a custom prefix and starting number so the sequence is right from day one. If you're adding VAT, the VAT calculator handles the arithmetic — and if you're working out margins on top of cost, the markup and margin calculator is the other half of the picture.
← All articles