Invoice Number Generator & Sequence Tracker
Why invoice numbering is worth getting right once
An invoice number feels like a formality until the day it isn’t. A client pays the wrong invoice because two of yours share a number; a bookkeeper can’t reconcile a month because one is missing; a reviewer asks why your invoices jump from 0032 to 0041. Every one of those problems traces back to a numbering scheme that was invented on the fly. The fix is to decide a format once, then keep the running sequence complete — no repeats, no unexplained gaps. That’s the whole job, and this tool does both halves in your browser.
What this tool does
Most “invoice number generators” online just paste a random or timestamped string on the screen and forget it the moment you close the tab. That’s the easy half. The hard half — the part that actually keeps your books clean — is remembering which number you used last for which client and catching mistakes in the sequence. So this tool has two parts:
- A format builder. Choose a prefix (like
INV), whether to include a date and in what form, whether to add a short client code, how many digits to pad the running number to, and a separator. You get a live preview of the next number as you change the settings. - A sequence tracker. Record each invoice you issue and the tool keeps a running log in this browser, suggests the next number, and flags repeated or missing sequence values for review. With a client-code segment it checks each client series; without one it checks one global series. You can export the log to CSV for your records or your accountant.
Nothing is uploaded. The format and the log live only in this browser’s local storage, and the Clear button wipes them.
How to choose a format
A good invoice number has three properties: it’s unique, it’s sequential, and it’s consistent. Beyond that, the structure is a matter of taste and how you file:
- Prefix —
INVis conventional, but a short business initialism works too. - Date — a
YYYYMMsegment groups invoices by month at a glance. The tracker does not reset the sequence automatically; skip the date if you’d rather keep the number visually simpler. - Client code — a short tag like
ACMElets each client have its own sequence, which is handy if you want per-client continuity or you branch numbering by account. - Padding — zero-padding (
0007rather than7) keeps numbers the same width so they sort correctly in folders and spreadsheets.
A frequent, sensible choice looks like INV-202608-ACME-0007. But there’s no single “correct” scheme — the guide on invoice numbering systems walks through sequential vs date-based vs client-based approaches and when each one earns its keep.
The rule that actually matters: no gaps, no duplicates
Whatever format you pick, use it consistently. A duplicate can make two invoices look like the same document and lead to a misapplied payment. A gap may be an error or a legitimate void, so the right response is to review and document it—not automatically renumber historical invoices. The IRS recordkeeping guidance allows a business to choose a recordkeeping system suited to it as long as income and expenses are shown clearly; it does not establish one mandatory invoice-number format. Check the rules that apply in your own jurisdiction.
A worked example
Say you set the format to prefix INV, a YYYYMM date, a client code, and 4-digit padding. For client ACME, you record invoices 1, 2 and 3 across the spring, so the tool shows numbers like INV-202603-ACME-0001 through -0003 and suggests 0004 next. Then you accidentally record 0003 again — the tracker immediately flags duplicate: 3. Later you jump to 0006, and it flags gap: 4, 5, so you can decide whether those were voided invoices (fine, if you can explain it) or a slip to correct. That running check is the difference between a scheme and a spreadsheet you hope is right.
Assumptions and limitations
- The log is per-browser. It’s saved in this browser’s local storage, so it won’t sync across devices — export the CSV if you need a copy elsewhere.
- You record what you issue. The tool tracks the numbers you enter; it doesn’t connect to your invoicing software, so keep the log and your invoices in step.
- Gaps aren’t always errors. A voided or cancelled invoice can leave a legitimate gap — the tool flags it so you can decide, not so you must “fix” it.
- Numbering rules vary. Some jurisdictions and tax schemes have specific invoice-numbering requirements; confirm yours with an accountant or the relevant authority.
Frequently asked questions
What is a good invoice numbering format?
Any format that is unique, sequential and consistent works. A common pattern is a prefix, an optional date, an optional client code, and a zero-padded running number, e.g. INV-202608-ACME-0007. The important rules are that numbers never repeat, never skip without a reason you can explain, and follow the same structure on every invoice.
Do invoice numbers have to be sequential?
A consistent sequence makes invoices easier to reconcile, but legal requirements vary by jurisdiction. If you use separate client series or restart a series, document the rule and keep it consistent. This tool flags repeated and missing sequence values for review; it does not determine legal compliance.
Can I start invoice numbers at any number?
You can choose a starting value such as 1001 if that fits your existing records. Record why the series starts there, then apply the same rule consistently; changing historical invoice numbers later can create reconciliation problems.
Is my invoice data uploaded anywhere?
No. The format builder and the sequence log run entirely in your browser and are saved only in this browser's local storage. Nothing is sent to a server, and you can clear the log at any time with the Clear button.
Why do gaps and duplicates in invoice numbers matter?
A duplicate number can make two invoices look like the same document and cause payment or bookkeeping errors. A gap may be legitimate, such as a voided invoice, but should be explainable in your records. Requirements vary, so confirm any jurisdiction-specific rules separately.