The cost of a broken invoice numbering system is not a fine. It is an afternoon in your sent folder, in November, while a client’s accounts payable team waits for you to tell them which of two invoices both stamped 14, for two different amounts, they are supposed to pay. You do not get paid that week.
Here is how it happens. You move from a spreadsheet to a proper app in March. The app helpfully starts you at invoice 1. You have already sent 1 through 41 from the spreadsheet. Nobody notices for eight months.
Numbering is the least interesting thing on the document and the one most likely to cost you an evening two years from now. It is also very cheap to get right, provided you decide the rule once and then stop improvising.
The part most guides skip is the split between format and continuity. The format is generally yours to choose: digits, letters, a year prefix, a client code, whatever suits how you work. The continuity usually is not. Tax authorities in most countries care that your invoices form a run that can be laid end to end and accounted for, with no missing numbers you cannot explain. Get that distinction and the rest is detail.
The short answer
A workable invoice numbering system does two things. Every invoice gets a number no other invoice has ever had, and the full set forms a sequence someone can audit without finding holes you cannot account for.
Beyond that, the format is normally up to you. Four schemes cover almost every real business:
- Pure sequential:
0001,0002,0003 - Year-prefixed:
2026-014 - Client-coded:
ACME-2026-003 - Date-based:
20260808-01
Year-prefixed is the one I would hand to most people. It sorts correctly, it tells you which tax year an invoice belongs to at a glance, and it gives you a clean place to restart each January without ever colliding with an old number.
Never delete an invoice number. If an invoice is wrong or cancelled, issue a credit note against it and keep both. Specific requirements differ by country and get amended, so confirm the detail with HMRC, the IRS, the GST portal, the ATO, the CRA or whichever authority you file with.
What the rules generally ask for
Nobody I have met chose their invoice numbering out of enthusiasm for compliance. Still, it helps to know which parts are actually load-bearing.
The recurring theme across tax systems is uniqueness plus a defensible sequence. In the UK, HMRC’s guidance on VAT invoices asks for a unique identifying number that follows on from the previous invoice. Across the EU, the VAT Directive (2006/112/EC, Article 226) lists among the required particulars a sequential number, based on one or more series, which uniquely identifies the invoice. That phrase “one or more series” is doing quiet work: it is the reason you are generally allowed to run separate runs for separate branches, currencies or client codes, provided each run is itself sequential.
India is stricter about the shape of the number. Under the CGST Rules, a GST tax invoice carries a consecutive serial number that is unique for the financial year, with a cap on length and a limited set of permitted characters. If you are billing under GSTIN, look up the current wording rather than trusting a blog, including this one.
The United States is the outlier that confuses everyone. There is no federal rule telling a freelancer how to number invoices. The obligation is to keep records adequate to support what you put on your return, and invoice numbering is simply the most practical way to do that. Australia and Canada sit closer to that model too: the ATO and CRA publish content requirements for tax invoices, and numbering falls mostly under general record keeping.
| Where you file | What the numbering expectation is generally about | Where to check |
|---|---|---|
| UK, VAT-registered | A unique identifying number that follows on from the last invoice | HMRC VAT invoice guidance |
| EU member states | A sequential number, based on one or more series, uniquely identifying the invoice | Your national authority’s implementation of Directive 2006/112/EC |
| India, GST-registered | A consecutive serial number, unique per financial year, length-capped and character-restricted | The GST portal and the current CGST Rules |
| United States | No prescribed invoice numbering; the duty is adequate records | IRS record-keeping guidance, plus any state requirements |
| Australia and Canada | Tax invoice content rules exist; numbering sits under record keeping | ATO and CRA guidance for your situation |
Treat that table as orientation, not as authority. Thresholds, wording and even which document counts as a tax invoice change from year to year, and an accountant who knows your country will settle in five minutes what a search engine will muddle for an hour.
Four schemes that actually hold up
Pure sequential
0001, 0002, 0147. One counter, no decoration. It is the easiest thing to defend because there is exactly one run and no argument about which series a number belongs to.
The cost is that the number tells you nothing. Invoice 0147 could be from last Tuesday or from 2023. If you keep files named invoice-0147.pdf in a folder, they sort beautifully, which is more than can be said for some of the alternatives.
Pad to four digits from the start. 0001 sorts before 0010; 1 does not.
Year-prefixed
2026-014, 2026-015, then 2027-001 in January. My default recommendation, and I will happily argue for it.
You get instant context, correct sorting for the next several thousand years, and a natural restart point. When your accountant asks for everything from the 2026 financial year, you filter on a prefix rather than remembering that the year began somewhere around invoice 88.
The only real decision is when the year rolls over. If your financial year is not the calendar year, decide whether 2026- means calendar 2026 or the year ending in 2026, write that down in one sentence, and never revisit it. UK sole traders and Indian businesses in particular should think about this, because a financial year that ends in April or March makes “the 2026 invoices” genuinely ambiguous.
Client-coded
ACME-2026-003, BRAV-2026-011. Popular with small agencies, and the scheme I see break most often.
The appeal is real. Large clients with purchase order systems find it easier to match your invoice to their record. Your own folder structure practically builds itself. If you bill six clients heavily and rarely take one-off work, the readability is worth something.
Where it breaks is that you no longer have one sequence. You have six parallel ones, plus whatever you did for the two one-off jobs. That is arguably fine under a rule that permits “one or more series”, but it puts the burden on you to keep a master log that stitches the runs together in date order. Without that log, the honest answer to “show me all invoices issued in order” is a shrug.
Date-based
20260808-01, 20260808-02. The date the invoice was raised, then a counter within the day.
This suits high volume and same-day multiples. A plumber issuing four invoices on a Friday, a photographer billing per shoot, anyone whose work arrives in bursts. Sorting is perfect. Duplication is nearly impossible if one person raises the invoices.
If two people raise invoices, it falls apart quickly, because both will reach for -01. You can fix that with initials (20260808-JM-01) at the cost of a longer number. Note also that date-based numbers are not strictly sequential in the “increment by one” sense, since you will skip every day you do not work. That is normally fine, but if you are in a regime that expects consecutive serial numbers, this scheme is the one most likely to cause a conversation.
| Scheme | Example | Good for | Breaks when |
|---|---|---|---|
| Pure sequential | 0001, 0147 |
Solo freelancers, low volume, minimum thinking | You want to know the year at a glance, or your padding runs out |
| Year-prefixed | 2026-014 |
Almost everyone; the safe default | Rarely; the only work is deciding your rollover date once |
| Client-coded | ACME-2026-003 |
Agencies with a few big clients and PO matching | Someone asks for one continuous sequence and you have eleven |
| Date-based | 20260808-01 |
High volume, several invoices a day, trades and shoots | Two people issue on the same day, or you need strict consecutiveness |
| Project-coded | P114-03 |
Long builds billed in stages | Every new bookkeeper needs the scheme explained to them |
Where to start, and the lie people tell
Start at 1. Or 001, or 2026-001. It is fine.
Most guides tell you to start at 0001 and leave it there. That is right, and it is also exactly why so many people quietly do something else: they know 0001 announces that the client in front of them is their first. So they start at 1047, or 3200, to look like a going concern.
I would push back on that hard, and not on moral grounds. It is a bad trade mechanically. You have now committed to a fiction you must sustain for the life of the business. Your accountant will see the ledger. If you are ever asked to produce invoices 1 through 1046, you cannot, and “I made the number up” is a worse sentence to say in a compliance meeting than “this was my first client”. Anyone senior enough to care has seen a real first invoice, and clients who are put off by low numbers were going to be difficult about something else anyway.
If you genuinely want the number to carry no signal, the honest fix is a format where the counter is not the salient part. 2026-014 reads as an internal reference. TF-0032 reads as a filing code. Neither announces much. That is a formatting choice, not a fabrication, and it costs you nothing later.
Restarting each January, and whether you should
The standard advice is to restart annually. It is common, it is usually permitted, and I do not think it is automatically the right call.
Restarting works when the year is baked into the number. 2026-047 followed by 2027-001 is clean: nothing repeats, everything sorts, and a year’s worth of invoices is one filter away. Restarting a bare counter is where it goes wrong. If you issue 047 in 2026 and 047 again in 2027, you now have two documents with the same identifier, and every reconciliation you ever do has to carry a mental footnote about which year you mean.
Running continuously has one underrated advantage: your invoice number becomes a rough count of your working life. Invoice 612 means 612 invoices. There is nothing to reconcile at the year boundary and no rollover conversation. Against that, a continuous number can drift high enough to look odd on a small business’s paperwork, and some accountants prefer the annual reset because it maps cleanly to the filing period.
Honestly, this is a preference rather than a rule, and it depends on whether you value cross-year continuity or year-by-year tidiness more. What matters is that you pick once and document it. A numbering scheme changed halfway through year two is worse than either option chosen badly.
Voided invoices, credit notes and the number you must not reuse
This is the section that saves people money, so read it even if you skim the rest.
You send invoice 2026-031 for £2,400. The client points out you billed for four days when the job was three. Your instinct is to open the file, change the number of days, and resend. Do not.
Once an invoice has left your hands, the correct move is to leave it standing and issue a credit note that references it. A credit note is a document that reduces or cancels a previously issued invoice, carrying its own number, its own date, and a line saying what it relates to. So you would issue CN-2026-004, “Credit against invoice 2026-031, adjustment for one day billed in error, £600 plus tax”, and either reissue at the correct amount or let the pair net out to £1,800.
Two reasons this matters. The first is that your client’s accounting system may already have posted 2026-031 at £2,400, and a silently edited version arriving later creates a mismatch that their accounts payable team has to investigate, which delays your payment. The second is that if you are registered for VAT or GST, the tax on that invoice may already sit in a filed or filing-period return, and the mechanism for unwinding it is a credit note rather than an edit. Check the specifics with your accountant, because how and when you adjust a filed return is precisely the sort of thing that differs by country and gets amended.
Give credit notes their own sequence. CN-2026-001 upward. Mixing them into the invoice run is legal in plenty of places but it makes your totals harder to read, since a “sum of all documents” no longer means anything useful.
What about an invoice you raised and never sent, or sent to the wrong company entirely? Mark it cancelled, keep the file, and record the reason in a line of your log. A void with an explanation is a non-event. A void with no paperwork is a gap, and gaps are what get questioned. For the difference between an invoice, a credit note and the half-dozen other documents people confuse for one another, we have a full breakdown in invoice, receipt, quote or estimate.
Worked example: Greta switches software in August
Say Greta runs a two-person branding studio in Bristol. She has been on a spreadsheet since January, using a client-coded scheme, and in August she moves to a proper accounting package.
Her position on 31 July looks like this:
ACME-2026-001toACME-2026-019: 19 invoicesBRAV-2026-001toBRAV-2026-008: 8 invoicesCDL-2026-001toCDL-2026-014: 14 invoices- Assorted one-off jobs numbered
MISC-2026-001toMISC-2026-022: 22 invoices
That is 19 + 8 + 14 + 22 = 63 invoices issued, totalling £48,210 net of tax. Her bank shows £46,930 received against them. The £1,280 difference is two credit notes she raised in May, CN-2026-001 for £480 and CN-2026-002 for £800, both against ACME jobs where scope was cut. 480 + 800 = 1,280, and the reconciliation closes. This is what a working system looks like: four parallel runs, one credit note run, and a master log that makes the arithmetic line up.
Now the migration. The new software offers her a single invoice sequence and defaults the next number to INV-0001. If she accepts that, she has an August invoice numbered 1 sitting after 63 invoices numbered something else entirely, and no way to show a continuous run.
What she actually does is switch schemes deliberately at the boundary, which is the one moment it is safe to do so:
- Export every invoice from the spreadsheet, including the two credit notes, into a single file with number, date, client, net amount and status.
- Save that export and a PDF of every invoice into one archive. Combining a year of separate PDFs into a single searchable file with PDF Merge takes about a minute and means the old run exists as one artefact, not 63 attachments.
- Set the new system’s next number manually to
2026-064, continuing the count rather than the format. - Write one line in her records: “Invoices 1 to 63 issued January to July 2026 under client-coded scheme, listed in the attached export. From invoice 2026-064 onward, single year-prefixed sequence.”
- Keep the credit note run going as
CN-2026-003in the new system rather than restarting it.
That note in step 4 is the whole trick. A scheme change with a written explanation and a reconciling export is a housekeeping decision. The same change without it is 63 invoices nobody can find.
If you would rather not rebuild an invoice template inside new software while all this is going on, the ToolFiddle invoice generator will produce a clean, correctly numbered PDF in the browser, with nothing uploaded anywhere. It is a useful bridge during a migration, when the old system is closed and the new one is still half-configured, and it costs you nothing while you decide where you are actually going to live.
Setting yours up in fifteen minutes
- Pick the format. If you have no strong reason to do otherwise, use
YYYY-NNN, three-digit padded, restarting in January. - Decide your rollover if your financial year is not the calendar year, and write the answer in one sentence.
- Decide the credit note prefix.
CN-is understood everywhere. - Open a plain spreadsheet with six columns: number, date issued, client, net amount, tax amount, status. Status holds one of paid, outstanding, credited, cancelled.
- Backfill every invoice you have already issued. This is the boring hour that makes everything else possible.
- Set the next number in whatever tool you use to generate invoices, so you are never typing it from memory.
- Put the rule itself somewhere you will find it: the top row of the spreadsheet, or a note in your business folder. “Format: YYYY-NNN. Restarts 1 January. Credit notes CN-YYYY-NNN, separate run. Never reuse, never delete.”
- Once a quarter, sort the log by number and read down the column looking for holes. Two minutes, and it catches the mistake while you still remember what happened.
Step 8 is the one people skip and the one that pays. Finding a duplicate in October when you raised it in September is trivial. Finding it in an audit is not.
Common problems and their causes
Duplicates from parallel tools are the most common failure by a distance. You raise most invoices in one place, then one Friday you are on a train and you knock one out from a different app, and both systems think they own the counter. If you use more than one route to produce an invoice, the log is the source of truth and the software is not.
Restarting a bare counter each year, covered above, generates duplicates on a one-year delay.
Reusing the number of an invoice you cancelled feels tidy and is the single worst habit here, because it produces two different documents with the same identifier that both genuinely existed. Leave the hole. Explain the hole.
Client-coded schemes with no master log are the slow-burn version. Everything is fine for eighteen months, and then a client’s finance team asks for copies of all invoices issued to them in the last financial year and you find that “CDL” became “CDLTD” somewhere around March when a different person raised one.
Then there is the format that sorts badly. 1, 2, 10, 11 will list as 1, 10, 11, 2 in any file browser you own. Pad your numbers.
Ambiguous dates cause a quieter problem: an invoice numbered 080926-01 means 8 September to a British reader and 9 August to an American one. If you are billing across borders, use YYYYMMDD and write the date on the document in an unambiguous form like 08 August 2026. If you are counting days for payment terms as well, Days Between Dates Calculator removes the guesswork about when Net 30 actually lands.
Finally, and less often discussed: numbering that leaks information you would rather keep. A pure sequential run tells every client roughly how many invoices you have ever issued, and a date-based scheme with a -01 suffix tells them you have issued exactly one invoice today. This is nearly always harmless. If it bothers you, a year prefix with a three-digit counter is the quiet middle ground.
Frequently asked questions
Can invoice numbers have letters in them?
In most systems, yes. Letters, digits and simple separators like hyphens are normally fine, which is why formats such as ACME-2026-003 are common. Some regimes do restrict things: Indian GST rules, for example, cap the serial number length and limit which characters you can use. Check the current guidance from the tax authority you file with before you commit to a format.
What should my first invoice number be?
Anything you like, as long as you can keep going from it. Starting at 0001 is honest and completely normal. Starting at 1047 to look established is a bad trade, because it locks you into a fiction you have to maintain forever and it fools nobody who has seen a real ledger. Pick something plain, write the rule down, and move on.
Do I have to restart invoice numbers each year?
Usually not, but you often may. A continuous run from your first invoice to your last is the simplest thing to defend. If you restart annually, put the year in the number so 2026-001 and 2027-001 can never collide. Some regimes expect uniqueness within a financial year rather than forever, so confirm what applies where you file.
What do I do if I need to cancel an invoice I already sent?
Issue a credit note that references the original invoice number and cancels all or part of it. Do not delete the invoice and do not reuse its number. The deleted invoice is the gap an auditor asks about, and you will have no paperwork to explain it. Credit notes should run on their own sequence, such as CN-2026-004.
Is it illegal to have gaps in invoice numbers?
A gap is not automatically an offence anywhere I am aware of, but an unexplained gap is a question you will have to answer. Auditors read missing numbers as possible hidden income. If a number was voided, keep the paperwork that shows why. Rules vary by country and change, so check with your tax authority or accountant.
How do I keep my numbering going after switching accounting software?
Before you issue anything from the new system, find the setting that controls the next invoice number and set it manually to carry on from your last one. Most tools default to 1, which is how duplicates happen. Export the full list from the old system first, store it as a PDF, and reconcile the two runs at year end.
Where this leaves you
Spend fifteen minutes on this today and you will not think about it again for years. Pick YYYY-NNN, pad the counter, give credit notes their own prefix, keep a six-column log, and set the next number manually in every tool you use.
The rest is discipline of a very low order: never reuse a number, never delete one, and write a sentence whenever you change something. Auditors are not looking for elegance. They are looking for a set of documents where every number is accounted for and the odd ones have an explanation attached.
If you are starting from nothing this week, the invoice generator will get a numbered, dated, professional-looking document out of the door in a few minutes, and you can build the log around it afterwards. Just decide the rule before you send the first one.