Invoice numbers: rules, format and practical number sequences
An invoice number makes a document unique – that is all it has to do. It doesn’t need to be complicated, but three things have to hold: assigned traceably, never duplicated, never quietly changed. Here is which system does that and why you never touch a number once it has been assigned.
Unique rather than obsessively gapless
The number does not necessarily have to be a pure, gapless sequence of digits. A prefix for the year or document type can make sense if you document the format. For many small businesses, a number like RE-2026-0042 is easier to follow than a random string.
Gaps can occur when a draft is discarded or a number was reserved. What matters is that you can trace the reason internally. Avoid renaming invoices that have already been sent just so a list looks gapless.
One number sequence per workspace
In a multi-tenant application, a number sequence must not accidentally be shared by all customers. Each workspace needs its own sequence and its own settings. That prevents duplicates and protects against data getting mixed up.
Estimates, invoices and credit notes can also get separate prefixes. Choose a system that supports your daily work and stays understandable in exports and for your tax advisor.
- Distinguish document types with a prefix
- Decide on the change of year in advance
- Don’t change numbers after sending
- Use a separate sequence per workspace
Change of year and corrections
At the change of year, you can reset the number sequence or continue it. Both can work as long as you use them consistently and uniquely. A year in the prefix often makes searching easier, but it is not mandatory for every organization.
An incorrect invoice that has already been sent should not simply be overwritten. Depending on the case, a correction, a cancellation or a new invoice referencing the original document may be appropriate. The correct approach depends on the facts.
What software should handle
Software should assign the next free number in a transaction-safe way, prevent duplicates in the database and keep number sequences per workspace. When a trial has expired, no new finalized invoices may be created without the status being clearly explained.
What should stay visible to you: the number sequence, the next expected document and the link between estimate, invoice, payment and cancellation.
Example with three separate document types
A small service business can number estimates as ANG-2026-0012, invoices as RE-2026-0042 and credit notes as GS-2026-0003. The prefix makes the document type recognizable; the year part makes searching easier. What matters isn’t this particular pattern, but that you define the rules once and apply them the same way to every document.
If several people work in the workspace, the next number must not be calculated in the browser. Otherwise two invoices saved at the same time could get the same value. Transaction-safe assignment in the database and a uniqueness check on finalizing prevent this error even when operations run in parallel.
- Define prefixes and the year change in writing
- Assign numbers transaction-safely on finalizing
- Keep document types and workspaces separate
Corrections and the archive after sending
A typo in a draft is quickly fixed. After sending, the situation is different: the original version is part of the history, and a new correction needs a clear reference. Depending on the error, a corrected invoice, a cancellation invoice or a credit note may be appropriate. The number of the original invoice should remain findable.
Avoid numbers built from client names, sensitive data or random information. A short, stable number sequence is enough for everyday searching and reveals less about the transaction. Exports and backups should treat the number as a permanent identifier.
Sources and context
Legal and tax rules can change. What counts are the current primary sources and your professional advice.
Put this into practice on your very next job.
Test Sumaro with a real client case and take it from estimate or invoice through to payment. Free for 30 days, no contract.