Invoice numbering: best practices for South African businesses
Invoice numbering best practices: what SARS expects of a serial number, formats that scale, handling voids and credit notes, and mistakes that cause audit headaches.
- Published
- Reading time
- 6 min read
- By
- CentraPoint Team
On this page
Good invoice numbering means every invoice gets a unique, sequential number that is never reused or edited, generated automatically by one system. In South Africa, a VAT tax invoice must show a serial number, so your numbering scheme is a compliance matter, not just an admin preference. The simplest robust format is a short prefix plus a running number, such as INV-004127.
Here is how to choose a format, handle the awkward cases, and avoid the mistakes that show up during an audit or a VAT verification.
Why invoice numbering matters
- VAT compliance. SARS lists a serial number among the required contents of a tax invoice. See our checklist of VAT invoice requirements in South Africa.
- Payment matching. Customers use the invoice number as their EFT reference. A clear, unique number makes reconciliation far easier.
- Audit trail. Gaps or duplicates prompt questions: was an invoice deleted? Was income left out?
- Customer queries. "Which invoice is this payment for?" is much easier to answer with clean numbers.
Rules every numbering scheme should follow
- Unique. No two tax invoices ever share a number, across all branches, systems and years.
- Sequential. Numbers increase in order of issue, so a gap is noticeable.
- System-generated. People should not type invoice numbers by hand.
- Never reused. A cancelled invoice keeps its number; it is reversed with a credit note.
- Never edited after issue. If something is wrong, credit and reissue.
- Separate series for different document types. Quotes, pro formas, credit notes and tax invoices each get their own prefix.
Common invoice number formats
| Format | Example | Good for | Watch out for |
|---|---|---|---|
| Plain running number | 4127 | Very small businesses | Looks like a quantity; easy to mistype |
| Prefix + padded number | INV-004127 | Most businesses | Choose enough padding for growth |
| Prefix + year + number | INV-2026-00412 | Businesses that like yearly grouping | Decide whether numbering restarts each year |
| Branch or entity code | JHB-INV-01233 | Multiple branches or companies | Each branch sequence must still be unique overall |
| Customer-based | ACME-017 | Rarely advisable | Sequence per customer hides gaps overall |
For most South African SMEs, prefix plus padded number is the best balance. It is short enough to fit an EFT reference field, looks professional, and is easy to search.
Should numbering restart every year?
It can, if the year is part of the number (INV-2026-00001 then INV-2027-00001), because the full number remains unique. If you use a plain running number, never restart it. Many businesses find a continuous sequence simpler.
Keep it reference-friendly
Customers often paste the invoice number into their banking app's reference field, which may be short. Avoid spaces, slashes and very long strings. INV-004127 survives a bank reference field; "Invoice #2026/Sept/Acme-Holdings/4127" may not.
Handling the awkward cases
A wrong invoice was issued
Do not delete or edit it. Issue a credit note for the full amount, referencing the original invoice number, then issue a new invoice with the next number. Credit note vs refund explains when you also need to return money.
An invoice number was skipped
Gaps happen, for example when a system crashes mid-issue. Record the reason in your notes or audit log so you can explain it later. A documented gap is far better than an unexplained one.
Quotes and pro formas
Give them their own prefixes, such as QT- and PF-, so they can never be mistaken for tax invoices. See tax invoice vs pro forma invoice.
Credit notes and debit notes
Use separate series (CN- and DN-) and always reference the original invoice number on the note.
Recurring and subscription invoices
Each billing period produces a new tax invoice with the next number from the same sequence. Do not reuse one number for "the monthly invoice".
Multiple systems
If your online store, your billing platform and your accounting package can all create invoices, pick one as the source of truth. Let the others sync from it, or give each system its own clearly distinct prefix. Two systems independently counting from INV-0001 is a recipe for duplicates.
Worked example: a clean month
A clearly illustrative September for a small design studio using the INV- and CN- prefixes:
| Date | Document | Customer | Amount |
|---|---|---|---|
| 1 Sep | INV-000871 | Karoo Coffee | R3,450.00 |
| 4 Sep | INV-000872 | Umhlanga Dental | R8,050.00 |
| 9 Sep | CN-000034 (ref INV-000872) | Umhlanga Dental | R8,050.00 |
| 9 Sep | INV-000873 | Umhlanga Dental | R7,475.00 |
| 15 Sep | INV-000874 | Karoo Coffee | R1,150.00 |
Invoice 872 had the wrong price, so it was credited in full and replaced with 873. Nothing was deleted, the sequence has no gaps, and anyone reviewing the ledger can follow what happened.
Record keeping
SARS generally expects VAT vendors to keep invoices and related records for at least five years from the submission of the relevant return. Keep issued PDFs as sent, not regenerated later with changed details. Check SARS's record-keeping guidance for the full requirements.
Checklist
- One system generates tax invoice numbers
- Prefix plus padded running number
- Separate prefixes for quotes, pro formas and credit notes
- No manual edits, no reuse, no deletion
- Gaps documented
- Numbers short enough for a bank reference
How CentraPoint helps
CentraPoint generates invoices from your customers, products and subscription plans, and produces branded PDF invoices, receipts, refund notes and statements from the same records. It keeps an audit log of account activity, and its accounting integrations with Sage, Xero, QuickBooks and Zoho Books help keep one system as the source of truth. Customers can pay by link, and bank statement import auto-matches collections to your records. See the invoices documentation.
Frequently asked questions
Does SARS require invoice numbers to be sequential?
SARS requires a serial number on a tax invoice. Sequential, unique numbering is the accepted good practice because it proves no invoices are missing and makes records easy to verify.
Can I use letters in my invoice numbers?
Yes. Prefixes such as INV- or a branch code are common and acceptable, as long as each full number is unique.
What should I do if I issued the same invoice number twice?
Keep both records, credit one of them with a credit note, and reissue it under a new, unique number. Then fix the process that allowed the duplicate.
Can I delete an invoice I issued by mistake?
You should not delete an issued invoice. Reverse it with a credit note that references the original number, so your records stay complete.
- #invoicing
- #invoice numbers
- #sars
- #bookkeeping