Guide
Invoice numbering best practices
How to number invoices so they stay consistent, audit-ready, and easy for clients to pay: the schemes that work, what to avoid, and how to switch without breaking your records.
An invoice number is a unique identifier assigned to each invoice you issue. Good invoice numbering follows three rules: every number is unique, the sequence has no gaps, and the format is consistent over time. The most common schemes are a plain sequential counter (0001, 0002, 0003), a date-based number (2026-001), or a per-client number (ACME-001). Any of these is fine as long as it is applied consistently. The numbering exists so that you, your client's accounts payable team, and both sets of accountants can refer to a specific invoice without ambiguity, and so an auditor can confirm none are missing.
Why invoice numbers matter
It looks like a formality, but the number is doing real work:
- →Payment matching. Your client's AP team references the invoice number on the payment. Without a clear, unique number, payments get misapplied.
- →Audit and tax. Tax authorities in most countries expect invoice numbers to be sequential and gap-free, so it can be shown that no invoice (and no revenue) was hidden.
- →Dispute resolution. "Invoice ACME-014" is unambiguous. "The invoice from last month" is not.
- →Your own bookkeeping. A consistent scheme makes reconciliation, follow-ups, and year-end accounting far faster.
The main numbering schemes
Plain sequential
Example: 0001, 0002, 0003
Simplest possible scheme. One running counter across all clients. Gap-free by construction. The downside: the number reveals your total invoice volume to every client, and it carries no context.
Date-based
Example: 2026-001, 2026-002
A year (or year and month) prefix plus a counter that resets each period. Easy to scan by date. Make sure the reset still leaves the full number unique across all time.
Per-client
Example: ACME-001, ACME-002
A short client code plus a per-client counter. Each client sees a tidy sequence starting at 001 and never learns your total volume. This is the Stripe-style format and the one most B2B suppliers prefer.
Project-based
Example: REDESIGN-01
A project code plus a counter. Useful for milestone billing on a single large engagement, but it does not scale as your main scheme. Best used alongside one of the others.
What to avoid
- •Gaps in the sequence. A jump from 014 to 017 looks, to an auditor, like two invoices were deleted. If you void an invoice, keep the number and mark it voided rather than removing it.
- •Reusing a number. Two different invoices with the same number is the fastest way to get a payment misapplied. Numbers are permanent and single-use.
- •Random or unstructured numbers. A random string is unique but unsortable and unmemorable, and it makes reconciliation painful.
- •Starting at 1. Invoice
0001tells a new client they are your very first. Starting a few hundred in, or using a per-client scheme, avoids signalling that. - •Changing format mid-stream without a plan. Switching schemes is fine, but do it cleanly (see below) rather than leaving an inconsistent trail.
A scheme that works for most people
If you bill businesses and want one recommendation: use a per-client scheme with a zero-padded counter, for example ACME-001. It gives each client a clean sequence, hides your total volume, sorts correctly, and is instantly readable in an AP system. Zero-pad to three or four digits so the numbers sort properly in spreadsheets.
If you would rather keep one global sequence, a date-prefixed counter (2026-001) is the next best choice: gap-free, sortable, and it carries the year for free.
JupiterInvoice supports per-client numbering out of the box: see custom invoice numbers. If you just need the next number in a sequence, the invoice number generator produces one in any of these formats.
Switching schemes without breaking things
You can change your numbering scheme. The rule is that you never break uniqueness and you never create a real gap. A clean switch:
- Pick a switch-over date, ideally the start of a financial year, so the old and new schemes do not interleave.
- Do not renumber old invoices. Issued invoices keep their original numbers permanently. The switch only applies going forward.
- Make sure the new format cannot collide with any old number. A new prefix (or a year component) guarantees that.
- Note the change in your records so an accountant or auditor can see the sequence is intentional, not broken.
Invoice numbering FAQ
Do invoice numbers have to be sequential?
Can two invoices have the same number?
What number should my first invoice be?
What do I do with the number when I void an invoice?
Is a per-client invoice number better than a global sequence?
Can I change my invoice numbering format later?
Number every invoice consistently
JupiterInvoice assigns clean per-client invoice numbers automatically, so the sequence stays gap-free without you tracking it. Free, no signup.
Create your first invoiceNo signup required. Build now, save later.