Why unique and sequential numbering matters
The identifier ties the sale, customer record, payment, correction and tax record together. A duplicate creates ambiguity about which document a payment or adjustment belongs to. A clear sequence also lets a reviewer follow what was issued and investigate a canceled or unused number.
Do not turn that practical benefit into a universal legal rule. EU VAT law calls for a sequential number, based on one or more series, that uniquely identifies the invoice. HMRC likewise requires VAT invoices to have a unique identification number that follows on from the previous one. Other systems may use different language or allow other identifiers. Check the rule for the invoice you are issuing and preserve the records that explain any break.
The core rules for a compliant invoice number
Start with the legal rule that applies, then use these controls to keep the records understandable. They are sensible practices, but not every item below is a statutory requirement in every country.
- Unique reference
- Within its scope, one full identifier should point to one invoice.
- Required sequence
- Where the law calls for a sequential series, define the series and advance it consistently.
- Explained gaps
- Retain canceled, void or failed records where required so a missing value has an audit trail.
- Controlled resets
- Start a new year or entity series only when local rules allow it and the prefix makes the new series unambiguous.
- Stable format
- Document the pattern and any series boundaries so another person can follow the records.
- Traceable corrections
- Do not silently edit or reuse an issued identifier; follow the applicable cancellation or correction process.
What are the common invoice number formats?
There is no single global format. A prefix can identify the document type, year or entity, while the counter provides the order. Treat each reset or prefix as a deliberate series boundary and verify that separate series are permitted. FreeBillGen guests enter their own number; a signed-in workspace can suggest a number from saved invoices, but it cannot reconcile documents issued elsewhere.
| Format | Example | How it works | Check before use |
|---|---|---|---|
| Simple running series | INV-0001, INV-0002 | A prefix plus one continuing counter. | Whether the prefix and starting value meet local rules. |
| Year series | 2026-001, 2026-002 | The year identifies a distinct annual series. | Whether annual resets are allowed and clearly separated. |
| Monthly series | 2026-08-001 | Year and month identify a monthly series. | Whether many separate series remain acceptable and manageable. |
| Entity or branch series | VNO-0007 | A stable code identifies the issuing entity or establishment. | That the scope is documented and full identifiers stay unique. |
| Date plus counter | 20260827-01 | The issue date is followed by a same-day counter. | How backdated, corrected or offline invoices are handled. |
What to avoid when numbering invoices
Avoid duplicate full identifiers, undocumented resets and deleting the only trace of a canceled issued invoice. Do not use an order number as the invoice number unless it independently meets the invoice rule; several invoices can relate to one order. A random identifier may be unique but still fail a local sequential-number requirement.
If an invoice was omitted, duplicated or dated incorrectly, do not invent a universal repair. Preserve what was issued and follow the correction, cancellation, credit-memo, or credit-note rules for the jurisdiction. Automation reduces collisions inside one system, but it cannot see an offline book or another invoicing service unless you reconcile them.
How to keep your numbering compliant in practice
The practical goal is a scheme another person can explain from the records. Write down the format, starting value, scope and reset rule. Restrict who or which system can allocate a number, and reconcile all channels that issue invoices.
Preserve cancellations and corrections in the manner your rules require. FreeBillGen guests enter a number. In a signed-in workspace, saved invoices can suggest the next number and duplicate saved full numbers are blocked, but you remain responsible for voids, separate series and documents created elsewhere.
Invoice numbering questions
Do invoice numbers have to be sequential?
It depends on the applicable rules. EU VAT law requires a sequential number, based on one or more series, that uniquely identifies the invoice, and HMRC requires a unique VAT-invoice number that follows on from the previous one. Do not assume the same wording or permitted series apply everywhere.
Can I start invoice numbers from any number?
Often, but check local rules and any migration requirements. A starting value such as INV-0100 can be clear if the subsequent series is controlled and the opening point is documented. Never choose a number that collides with an existing invoice in the same scope.
What happens if there is a gap in my invoice numbers?
Investigate and document it. A gap may come from a cancellation, failed issue or another channel, but an unexplained gap weakens the audit trail. Keep the evidence and use the cancellation or correction method required by your jurisdiction instead of reusing the value.
Can I include letters in an invoice number?
Often, but verify the permitted format. Prefixes such as INV, a year or an entity code can define or clarify a series. The full identifier must meet the applicable uniqueness and sequence rules; do not assume client or monthly prefixes are accepted everywhere.
Should I reset invoice numbers each year?
A year-prefixed format such as 2026-001 can define a separate annual series where local rules allow it. A continuing counter may be simpler. Document the boundary and make the full identifier unambiguous; do not assume annual or monthly resets are accepted in every jurisdiction.
Can two invoices ever share the same number?
Within the scope of the series, the full identifier should point to one invoice. If a duplicate was issued, preserve the records and follow the applicable correction process rather than silently editing both files. A system can prevent duplicates only among the invoices it knows about.