Invoice numbering: best practices
Invoice numbering looks like a tiny detail until the day you need to find the invoice you sent in March, prove to a tax auditor that you didn't skip any sales, or figure out which version of invoice 47 the client actually paid. Get the system right at the start and you'll save yourself hours of digging later.
This guide walks through the five rules that matter: pick a sensible starting number, pick a format you can stick with, never reuse a number, keep the sequence tight with no gaps, and pick something an accounting tool can read if you ever switch software. Each step takes about a minute to decide. The hard part is choosing once and then not changing your mind six months in. By the end you'll have a numbering plan you can apply to the next invoice you write and every invoice after that.
Why invoice numbers matter
Every invoice you send needs its own unique number. That number is what your client writes on the cheque, what your bank statement quotes when the payment lands, and what you or your accountant use to tie a sale to a deposit.
Three concrete reasons the number matters:
- Tax audits. Tax offices in most countries can ask to see a continuous list of invoices for a given year. They're checking that you didn't quietly skip a sale. In Australia, the UK, Canada, and most of the EU, gaps in your numbering are a flag to look closer. In the US, the IRS doesn't require sequential numbers by federal rule, but state sales-tax auditors often expect them, and a clean sequence is much easier to defend than a messy one either way.
- Finding the invoice in an email thread. A client emails you saying "I paid invoice 47 last week, why are you chasing me?" If you have one invoice numbered 47, you can pull it up in two seconds. If you reset your numbers every January and have three different invoice 47s sitting in your sent folder, you'll waste time trying to figure it out.
- Double-billing. If you ever accidentally send the same invoice twice with two different numbers, the client may pay it twice, and you have a refund to issue. A clean numbering scheme makes duplicates obvious before they go out.
The good news: this is a one-time decision. Pick a system in the next five minutes, write it down somewhere you'll see it again, and you're done. The rest of this guide are the five rules that make the choice almost automatic.
Step 1: Pick a starting number
Your first decision is what number invoice number one will actually be. There are three common choices and none of them are wrong.
- Start at 1001. This is what most consultants and freelancers do. It avoids the optics of sending a client "Invoice 1", which some people worry signals you just started out. Whether a client actually notices is a different question (more on that in the FAQ below), but 1001 is a safe, common starting point.
- Start at 0001. Padded with zeros so the number is always four digits. Looks tidy in a spreadsheet because every row is the same width. The downside: once you cross 9999, you have to add a fifth digit, which can look odd next to the older ones.
- Start at INV-2026-001. A year prefix plus a counter. Good if you want the invoice year visible right in the number, and useful if you file invoices in folders by year.
People sometimes argue that starting at a higher number, like 5000 or 10000, makes a new business look more established. There's no real evidence clients care. What they care about is that the invoice is clear, accurate, and matches the work you did. Starting at 1001 versus 5001 versus 10001 is cosmetic. Pick the one you find easiest to remember and move on.
One practical note: don't start at a giant random number like 837492. If you ever need to type the invoice number into a payment processor, a bank reference field, or a spreadsheet, shorter numbers are faster and less mistake-prone. Four to six digits is the sweet spot.
Step 2: Pick a format
Once you know your starting number, decide on the shape of every invoice number after it. Three formats cover almost every small business.
Sequential. Just a counter. 1001, 1002, 1003, 1004, etc. This is the simplest format and the easiest to keep straight in your head. Most accounting software defaults to this. If you're billing fewer than a hundred invoices a year and only have a handful of clients, sequential is almost always the right answer.
Date-prefixed. A year (and sometimes a month) followed by a counter. 2026-001, 2026-002, or 2026-05-001 for May 2026 invoice one. Pros: you can tell when the invoice was issued just by looking at the number, and filing by year in folders is automatic. Cons: longer to type and read, and the year prefix can look like the invoice is part of a yearly batch, which makes it tempting to restart the counter each January. Restarting per year is one of the most common mistakes (see the last section).
For most small businesses, plain sequential with a four-digit counter is the simplest format that survives growth, software changes, and audits. Date-prefixed is fine if you genuinely want the year visible. Client-prefixed is the format that causes the most headaches later.
Step 3: Never reuse a number
This is the one hard rule. Every invoice number you ever issue points to exactly one invoice, forever. Once you've used 1024, it's taken. Even if you void that invoice five minutes later, you don't reuse 1024 for the next one. The next invoice is 1025.
Why this matters in practice:
- Your client may have already saved the PDF. If they then receive a different invoice with the same number, your records and theirs no longer match. When they pay later and reference "invoice 1024", neither of you can be sure which one they mean.
- Tax records. If invoice 1024 was voided and then the same number was reused for a different sale, an auditor can't tell which sale the number was supposed to represent without digging into emails and bank records.
- Payment processors. Stripe, Square, PayPal, and most bank statements store the invoice number with each payment. If two different invoices share a number, the payment history becomes ambiguous.
What to do if you void an invoice:
- Mark the original invoice as voided in your records. A "VOIDED" stamp or a status flag in your accounting tool is enough if the invoice has never left your system. If you already sent the invoice to a VAT-registered customer or filed it in a VAT return period, you must issue a formal credit note (sometimes called a credit memo) with its own separate sequence (CN-001, CN-002) that references the original invoice number. That's the required mechanism in the UK, the EU, and Australia. The credit note cancels the original; the original invoice number stays in the sequence, you don't delete or reuse it.
- If you're issuing a replacement, give it the next number in line. So if 1024 was voided, the replacement is 1025, not 1024-A or 1024-v2.
- Keep a one-line note (in the invoice notes field, or in a side log) explaining which invoice was voided and why. Two months from now you won't remember, and your accountant will appreciate the explanation.
The credit note approach isn't optional for VAT-registered businesses once an invoice has been sent to a customer or included in a filed VAT return. The internal "VOIDED" stamp is fine only for invoices that never left your records.
Step 4: Keep them sequential
Step 3 says never reuse a number. Step 4 says the flip side: don't skip numbers either. The sequence should run 1001, 1002, 1003, 1004, with every number accounted for.
This matters mainly for tax purposes. In the UK, Australia, Canada, the EU, and most other countries with a VAT or GST system, your invoice register is expected to be a continuous run of numbers. A gap between 1023 and 1025 with no 1024 anywhere raises the question: was there a sale you forgot to record? In the US, the federal rules are looser, but state sales-tax audits and most accountants still want a clean continuous list.
The fix is straightforward. If you void 1024, keep 1024 in your records with a "voided" status. The number is still in the sequence, it just points to a cancelled invoice. The next invoice is 1025 and the auditor can see the full chain.
A few situations that look like gaps but aren't:
- Draft invoices that never got sent. Most cloud invoicing tools (Xero, QuickBooks Online, FreshBooks, Wave, Zoho Invoice) assign the invoice number when you start a draft. If you delete the draft, the number disappears from the sequence and creates a gap. There's no setting in any of these tools to defer numbering until send. The practical workaround is the same in all of them: keep a separate written register of any deleted-draft numbers so you can explain the gap if an auditor or tax office asks.
- Numbers used in tests. If you ever test your invoicing with a fake invoice and then delete it, do the same: note it in your register so the sequence is complete.
If you genuinely have a gap from before you knew this rule, don't panic and don't try to fill it in by backdating a fake invoice. That's much worse than the gap. Just keep the sequence clean from now on, and if an auditor asks, the honest answer is that the older numbering was inconsistent and you tightened it up. They've heard it before.
Step 5: Match what your accounting software expects
Even if you're sending invoices from a free generator or a Word template today, there's a good chance you'll move to dedicated accounting software at some point. Maybe you start using Argo Books, or your accountant asks you to switch to QuickBooks, Xero, FreshBooks, or Wave. Almost all of these tools can import an existing list of invoices, but they're pickier than you might expect about what an invoice number can look like.
Formats that import cleanly into almost everything:
- Plain digits:
1001,1002,1003. - Letters then digits with a hyphen:
INV-1001,INV-1002. - Year then digits with a hyphen:
2026-001,2026-002.
Formats that often cause import problems:
- Slashes inside the number:
2026/05/001. Some tools interpret the slash as a path separator and fail. - Spaces:
INV 1001. Get stripped or replaced inconsistently between tools. - Symbols beyond the hyphen:
#1001,1001*,1001!. Often rejected by stricter validators. - Mixed case in unpredictable spots:
Inv-1001in some,INV-1002in others. Importers may treat these as different prefixes.
Two practical rules. First, stick to letters, digits, and hyphens. Second, be consistent: if you start with INV-1001, keep INV- on every invoice. Don't mix INV-1001 with 1002 with #1003. A consistent format imports in one click. A mixed bag means you spend an evening cleaning up a spreadsheet before the import will run.
Even if you have no plans to switch tools, this rule is also a kindness to your future self. A consistent format sorts properly in a spreadsheet, searches cleanly, and copies into emails without any quoting weirdness.
Common mistakes
The same handful of mistakes come up over and over. They're easy to avoid once you've seen them.
Restarting the numbering each year without a year prefix. This is the most common mistake. You finish 2025 at 1001, then on January 1st you start 2026 back at 0001 (or 1001) with no year in the number. Now you have two invoice 1001s in your records, one from each year. Both your accounting software and any tax audit treat that as a duplicate. If you do want to reset per year, embed the year in the format: 2026-001, 2027-001. That keeps every number unique across your history while still letting you start fresh each year, and it's the standard way to do it in the UK and EU. The mistake is only the unprefixed reset, not the reset itself.
Restarting per client. Each client gets their own counter starting at 001. ACME gets ACME-001, ACME-002. BETA gets BETA-001, BETA-002. Looks tidy from one client's view. The problem hits when you list invoices across all clients: you have three different invoice 001s sitting in the same spreadsheet, and your bank statement quotes "Payment for 001" with no way to tell which client paid. If you want client info, append it (1001-ACME) so the leading counter stays unique across the whole business.
Using human names. Naming invoices things like "Smith renovation invoice" or "March consulting work" instead of a real number. Accounting software can't sort these, auditors can't follow them, and you can't find them in an inbox search. You can put a description in the invoice notes or memo field, but the name itself should be a number (with an optional prefix).
Using random numbers. Picking a fresh random number for each invoice so they "look like" big-company invoices. Defeats the entire point of having a sequence. You can't verify completeness, you can't tell which invoice came first, and duplicates are easy to create without noticing. Random is the opposite of what you want.
Avoid these four and the rest of the system almost takes care of itself.
Frequently asked questions
You can, but it causes more headaches than it solves. The most common pattern is to leave the counter running across years (1247, 1248, 1249) so every number is unique forever. If you really want the year visible in the number, put it inside the number as a prefix like 2026-001, 2026-002, and just keep going next year with 2027-001. Either way, don't run two separate counters that both start at 001 in different years. When a client emails about "invoice 1001", you should be able to find one invoice, not three.
Keep the number in the sequence and don't reuse it. The next invoice you issue is 1025. If 1024 never left your system, marking it voided in your records is enough. If you already sent 1024 to a VAT-registered customer in the UK, EU, or Australia, or if it landed in a VAT return period you've already filed, you need to issue a formal credit note (CN-001, CN-002 on its own separate sequence) that references invoice 1024. The credit note is the legally required way to cancel a sent invoice in those jurisdictions; an internal "voided" flag alone isn't enough once the invoice is out the door. Either way, don't delete 1024 and don't reissue the number. An auditor looking at your records later will see a clean sequence with one voided entry (or one credit note attached), which is normal and easy to defend.
In practice, almost no client checks. They look at the invoice itself: is it clear, is the math right, does it match what we agreed. If you're worried about the optics, start at 1001 or pick a format that doesn't lean on a single small digit, like INV-2026-001. Higher starting numbers can give the impression of more history, but the impression fades quickly once the client has worked with you for a few months. Pick whatever lets you sleep, then never think about it again.
Across all clients. Each invoice number should appear exactly once in your entire business, not once per client. If you want client information visible, the cleanest way is to put it after the counter (1001-ACME, 1002-BETA) so the leading number is still unique across the board. Using a per-client counter means ACME-001 and BETA-001 share the same digits, which causes problems on bank statements, payment processor screens, and any spreadsheet that lists invoices across all customers.
Letters and hyphens are fine and supported by almost every accounting tool: INV-1001, ACME-1002, 2026-001 all work. Avoid slashes, spaces, hash signs, asterisks, and other symbols. They cause problems when you import invoices into accounting software, and they can break URL links and bank reference fields. Stick to letters, digits, and the hyphen as a separator. If you want a prefix, pick one short prefix and use it on every invoice. Mixing prefixes mid-year (INV-1001 then 1002 then #1003) is the part that causes confusion later.