Back

24 September 2026 · 6 min read

Fundamentals

How to Number Invoices Correctly

An invoice number looks like the least interesting field on the page. It is also the field that will be quoted back to you for years — by a client's bookkeeper, by your accountant, and by anyone trying to prove that a particular document exists. Ten minutes of decisions now buys decades of a trail that holds.

A number is a handle, and handles get pulled

Every conversation about a payment, a credit, a dispute or a tax return begins by identifying one document among hundreds. The invoice number is how that identification happens. When the handle is missing or unreliable, the conversation starts with a hunt.

That is the whole case for numbering discipline — not tidiness for its own sake, but making sure that any document you have ever sent can be found, referenced and reconciled without guesswork. Picture the query eighteen months later: an auditor wants the document behind one payment on a bank statement. A working series turns that into a single search; a broken one turns it into an afternoon.

Dates, terms and client details deserve the same respect — the step-by-step guide to creating an invoice covers those fields in the order they matter.

Three schemes that hold up

SchemeLooks likeSuitsWatch out for
Continuous seriesINV-0042, INV-0043Very small businesses; historical exports that expect plain integersNothing — this is the simplest option that survives scrutiny
Year-prefixedINV-2026-0042Businesses that search their records by periodDeciding at year-end whether the counter restarts, and doing it inconsistently
Type-prefixed pairQUO-0042 with INV-0031Anyone who sends quotes before invoicesAssuming the quote and the invoice share a counter — they should not

All three share one property: they are deterministic. From the last number you can calculate the next one, and from any number you can find its neighbours. Schemes that fail — client initials, project names, dates reinvented per document — fail precisely because the next number cannot be derived from the last.

The rules that matter more than the scheme

  • Treat a sent number as spent. If a document was issued with it, the sequence now includes it, whether or not it was ever paid.
  • Do not reuse a number after voiding a document; the replacement gets the next number in line, and the void stands recorded where it is.
  • Keep one series per document type, not one per client. Per-client series explode into ambiguity the moment a client changes name or a dispute involves two entities.
  • Record the number the moment the document exists — even a draft you might discard should not leave a hole behind it if it was numbered when sent.
  • Never renumber to make the sequence look better. The sequence is not a presentation; it is an index.

Worked example: crossing into a new year

You end December 2026 having issued up to INV-2026-0187, and January opens with a clean calendar. There are two defensible moves, and the right one depends on how you (and your accountant) look things up.

One habit makes either option safe: the first document of the new year gets its number before the work begins, because retro-numbering a busy January is where gaps are born.

Option one: keep counting — INV-2026-0188 in January, accepting that the year inside the number no longer matches the year of issue. Option two: restart the counter for 2027 and let the prefix change to INV-2027-0001, where the year itself marks the reset. What makes either option safe is consistency: the reset is announced by the prefix, not hidden inside a counter that quietly returns to 1 under the same label. Whatever you choose, record the decision where you keep your bookkeeping notes, because the question will come up again in twelve months.

When a number is wrong

Mistakes happen: the wrong client's details under a fresh number, a duplicate caused by two people invoicing the same delivery. The repair is always the same shape — leave the original visible in the record, mark it void where it can be seen, and issue the corrected document under the next number, referencing what it replaces. Quietly editing the faulty document is the one move that turns a small error into a finding, because it is the only move that makes two documents disagree about history. When you tell the client, name both documents in the same line — the void original and its replacement — so their filing follows yours.

What the editor does for you

In FreeInvoices, quotes and invoices advance on separate counters. Converting an approved quote produces an invoice with a number from the invoice series, while the quote keeps the reference it was sent with and records what it became — so a client can always match the two documents by their own numbers. When you make a fresh document, it arrives already numbered; typing over a number is possible, and if you do it, the series simply continues from wherever you left it. The guide walks through the workflow end to end if you want the tour first.

Frequently asked questions

Can I start my invoice numbering at any number?

Yes — pick a starting point that matches your reality, higher than any number you have ever issued, and then treat the sequence as unbreakable from there. Starting at 1001 because it looks established is harmless; starting at 1001 and later issuing a 42 is not.

Do I legally need invoice numbers if I am not VAT registered?

There is no general statute that numbers every invoice in South Africa — the serial-number duty attaches to tax invoices issued by VAT vendors. Number anyway: the sequence is what lets you and your clients find documents years later, which is a business need, not a filing formality.

What if two invoices end up sharing a number?

In practice this comes from two sources feeding one series — two people, two apps, two bank accounts. Fix the immediate pair by correcting the later one under a fresh number, and then fix the source by keeping a single place where numbers are issued.

The editor keeps a separate number series for quotes and invoices, advances it as documents are created, and records what a converted quote became — so the reference trail between the two documents survives the conversation.

Create a numbered invoice