Skip to content

·The Apsis team

Invoice numbering in Australia: rules and a system that scales

What the ATO expects of invoice numbers, why gaps and duplicates cause trouble, and three numbering schemes that stay tidy from invoice 1 to invoice 1000.

No tax law prescribes an invoice numbering format. The ATO’s list of details a tax invoice must contain does not include an invoice number at all, and business.gov.au treats one as good practice rather than a requirement. What matters in practice is that every invoice carries a unique identifier, that no identifier is ever used twice, and that you can produce any invoice from the last five years when someone asks for it by number. Sequential numbering is the expected practice because it makes all three of those easy and nothing else does.

So the format is yours to choose. The discipline around it is not really optional, and the cost of getting it wrong lands years later, when you are trying to reconstruct what happened.

General information, not tax advice. The ATO is the authority - see ato.gov.au or ask a registered tax or BAS agent.

What is actually required

The ATO’s tax invoices page sets out 7 details a tax invoice for a taxable sale under $1,000 has to show clearly enough to be determined: that the document is intended to be a tax invoice, the seller’s identity, the seller’s ABN, the date of issue, a brief description of what was sold, the GST amount payable, and the extent to which each sale is taxable. Sales of $1,000 or more need the buyer’s identity or ABN as well. An invoice number appears nowhere on that list. The full field-by-field walkthrough is in how to create a tax invoice, step by step.

business.gov.au’s how to invoice page puts “a unique invoice number” among the things it is “also a good idea to add” to a tax invoice, and says outright that no law sets out what to put in a regular invoice. That is the honest status of it: strongly expected, near-universal, not a legal field.

Two other rules make it effectively compulsory anyway. The ATO’s record-keeping rules for business require most records to be kept for 5 years and to be produced when asked, and a number is how you find one document among five years of them. And your customer’s accounts system almost certainly files by invoice number, which means an invoice without one creates work for the person who has to pay you.

Why gaps and duplicates cause trouble

At audit. Anyone reconciling your reported sales against your invoices reads a sequence as a completeness check. A missing number is not evidence of anything by itself, but it is a question, and the answer has to come from you. “Invoice 42 was cancelled, here is the voided record” ends the conversation. “I deleted it” does not.

In disputes. Two documents both headed invoice 118, with different amounts, is a problem that only appears when it matters most: months later, when a customer says they already paid 118 and you are looking at a different 118. Reused numbers are rare, and the reason they are rare is that people who reuse them stop doing it after the first time.

In your own bookkeeping. The invoice number is the payment reference you asked the customer to use, so it is what appears on your bank statement. If numbers repeat, reconciliation stops being mechanical. If they are unique and sequential, matching payments to invoices is a sorting job.

Three schemes that scale

A plain sequence. INV-0001, INV-0002, INV-0003. Pad to four digits so the numbers sort correctly in a file list and stay the same width on the page. This is the least clever option and the hardest to break, which is exactly why most businesses end up here. Its one real drawback is that it advertises your volume: a new customer receiving INV-0003 can tell it is your third invoice ever. Starting at a higher number is a common and unremarkable answer, because uniqueness is the requirement, not starting at 1.

A year prefix. 2026-001, or INV-2026-001. The sequence restarts each year and the year is carried in the number, so a stack of invoices sorts into financial or calendar years without opening any of them, and reconstructing a BAS quarter is faster. The trap is restarting the count without the prefix, which is how you end up with two documents called invoice 7. If the year is not in the number, the number does not reset.

A client prefix. ACME-001, ACME-002. Useful in one specific situation: subcontract work where a head contractor requires their own reference on every document, or where a large customer processes your invoices in a system keyed to a job code. Otherwise it backfires in four predictable ways. Two clients share initials. A client changes their trading name and the prefix now names a business that does not exist. Answering “how many invoices did I issue in March” means merging a dozen separate sequences. And a customer looking at ACME-002 can see precisely how much of your work is theirs, which is information you may not have meant to hand over.

Any of the three is defensible. The scheme that fails is the one chosen again each time an invoice goes out, because that is the one that eventually collides.

Never reuse or delete a number

An invoice that has been sent is a fixed record. If the job is cancelled, the customer pulls out, or you issued the document by mistake, the number stays in the sequence and the invoice is marked cancelled or void, at nil. The gap does not appear, the record explains itself, and nobody has to remember what happened.

If you have already reported the GST from that invoice on a business activity statement, cancelling it is not just a filing change. The ATO’s page on adjusting GST covers when a change to a sale you have already reported means making an adjustment on a later statement.

If the invoice was simply wrong and the job still stands, the correction goes out as a new document, not an edit. Where the sale itself changed after the fact, an adjustment note (most people still call it a credit note) reduces or reverses the original and references it by number. Where the document just got a detail wrong, a corrected invoice with its own new number, referencing the original, does the job. Which one applies is worth checking with a registered tax or BAS agent on anything substantial.

Quietly editing a document that has already been sent leaves two different versions of the same numbered invoice in the world, and your customer may have already claimed a GST credit against the first one.

Starting number when you switch tools

The safe move when moving to new software is to continue the old sequence: set the next number in the new system to one above the highest you have ever issued, not to 1. Restarting produces exact duplicates of numbers already in a customer’s system, which is the one failure mode worth actively avoiding.

If your old records are incomplete and you cannot be certain of the highest number issued, jump well clear of it and make the gap deliberate rather than mysterious. A single line in your records - “INV numbers 1 to 486 issued in the previous system, new sequence starts at INV-0500” - converts an unexplained hole into a documented one, and answers the audit question before it is asked. The same note is worth writing when you change scheme, say from a plain sequence to a year prefix.

Whatever you pick, the last decision to make is who is allowed to override the next number. In most small businesses the answer is nobody, and the numbering problem disappears permanently. The other half of getting paid - terms, due dates and follow-up - is in how to get invoices paid on time.

How Apsis helps

Apsis numbers invoices sequentially as you create them, so the next number is never something you have to remember or look up, and two invoices cannot end up sharing one. Cancelling an invoice voids it and keeps it in the list rather than removing it, which leaves the sequence intact and the reason visible. Invoices, quotes and expenses with receipt uploads are all on the free plan, which covers 5 clients and 20 invoices a month, and share the same client records, so an invoice you issued three years ago is still one search away when someone queries it.