Choosing an invoice numbering system that scales
The format you pick for invoice numbers is one of those tiny decisions that quietly compounds. Here's how to choose one you won't regret.
Invoice numbering looks trivial until you've been freelancing for two years, switched accounting tools twice, and now have three different sequences floating around your records. By then, untangling it costs real time — and in some jurisdictions, real money. A few minutes choosing the right scheme up front saves all of that.
Why the numbering scheme matters
Invoice numbers are not just a label. Most tax authorities require invoices to be issued in a consistent, sequential way so that gaps can be explained. If you skip from invoice 0014 to 0017 with no record of 0015 and 0016, an auditor is allowed to ask why. Your accounting software, your client's procurement system, and your own records all key off this number, so it needs to be unique forever.
Option 1: Pure sequential
The simplest scheme: 0001, 0002, 0003. It works, it's easy to explain, and there are no edge cases. The drawback is that the number reveals exactly how many invoices you've ever sent — which can feel awkward when invoice 0007 lands in a Fortune 500 inbox. Pad with leading zeros so sorting stays correct as you grow.
Option 2: Year-prefixed sequential
The format 2026-001, 2026-002 resets the counter each January. It hides your total volume, makes year-end bookkeeping easier, and gives you a natural visual cue when filing. The trade-off: you have to remember to reset on January 1st, and software-side, the "is this number unique?" check has to consider the year prefix.
Option 3: Date-based
Some freelancers use the full issue date, e.g.20260518-01. This makes the invoice number self-documenting — you can read the issue date right off it — but it's noisy to type and clients sometimes confuse it for an order number. Useful if you issue many invoices on the same day; overkill if you issue one or two a week.
Option 4: Client-prefixed
Agencies that serve repeat clients sometimes prefix with a client code: ACME-014, BETA-003. It's nice for scanning a folder, but it complicates the "must be sequential" requirement in some tax regimes. If you go this route, keep a global sequence in parallel for compliance and use the prefix only as a label.
What auditors actually look for
- Uniqueness — no two invoices share a number, ever.
- Continuity — gaps are either absent or explained (e.g. a voided invoice still has a number on file).
- Chronology — numbers go up with time, not down.
- Stability — the format doesn't change mid-year without a reason.
Handling voids and reissues
If you send an invoice and discover an error, do not delete it and re-issue with the same number. Issue a credit note (or void the invoice with a clear "VOID" stamp), keep the original on file, and send a new invoice with the next number in the sequence. Your future self — and your accountant — will thank you.
Switching tools without breaking the chain
When you migrate from one invoicing tool to another, start the new tool's counter where the old one left off. If your last invoice in the old system was 2026-042, configure the new tool to begin at 2026-043. Continuity across tools is what matters, not which software issued each invoice.
A recommendation for most freelancers
Year-prefixed sequential (YYYY-NNN) hits the best balance for the majority of solo operators and small studios. It scales to hundreds of invoices a year, resets cleanly for tax filing, and is immediately readable to any client's accounts department. AetherInvoice defaults to this format for exactly these reasons.