·6 min read
How to Reset Invoice Numbering for the New Year Without Duplicates or Gaps
A practical January guide to restarting invoice, PO, delivery note and receipt numbers with a year code, across branches, without duplicates or unexplained gaps. It also covers how to number December documents that are still being entered in January.
- document numbering
- invoice numbering
- new year
- year-end closing
- audit trail
- invoicing
- multi-outlet
- sme

It's the first week of January. Your admin has a stack of delivery notes from late December that still need invoicing and a new customer waiting for a quotation. There is also a question nobody answered last year: do invoice numbers continue from where they stopped, or start again at 0001? If you reset invoice numbering for the new year the wrong way, you end up with two invoices carrying the same number, or a block of missing numbers that your auditor will ask about. This guide shows how to restart invoices, purchase orders, delivery notes and receipts cleanly, including when you run more than one branch.
Why duplicates and gaps cause real problems
A document number looks like an admin detail. For everyone outside your company, it is how they find your paperwork and decide whether to trust it.
- Customers: when two invoices share a number, the customer's finance team may pay one and mark both as settled, or reject the second as a duplicate. You then spend weeks chasing money they believe they have already paid.
- Auditors: one of the first checks is whether the invoice sequence is complete. A jump from 0112 to 0118 means five documents you have to explain. If you can't show they were cancelled, it looks as if sales were removed from the books.
- Tax reconciliation: your sales invoices must match the faktur pajak you issued and the VAT you reported. The faktur pajak number comes from the tax office system, not from your own counter. That makes your invoice number the link between the two. Duplicates make this matching slow and error-prone at year end.
A gap is not a violation in itself. The trouble starts when you have a gap you can't explain.
Choosing a format to reset invoice numbering each new year
The simplest answer to the “continue or restart” question is to put the year inside the number. Restarting at 0001 every January then cannot create a duplicate, because INV/2025/0001 and INV/2026/0001 are different numbers.
Here is a format that works for most SMEs:
INV/JKT/2026/01/0001- INV: the document type. Use PO for purchase orders, SJ for delivery notes (surat jalan), KW for receipts (kwitansi), and so on.
- JKT: the branch or outlet code. Leave it out if you only have one location.
- 2026: the year.
- 01: the month. This part is optional.
- 0001: the running sequence.
Yearly or monthly reset?
If the month is in the number, you can reset monthly. A yearly reset gives one continuous sequence, which is easier for an auditor to check. A useful rule: if you issue fewer than a few hundred documents a month, reset yearly and treat the month as information only. Both approaches work. What matters is that you pick one and write it down.
Small decisions that save trouble later
- Use a four-digit year, not two.
- Give the sequence enough digits for your busiest year. Four digits (up to 9,999) suits most businesses. High-volume retail may need five.
- Take the year and month from the document date, not from the day someone typed it in.
- Don't change the format mid-year. If you must change it, do it on 1 January.
Resetting sequences per document type and per branch
Each document type needs its own counter. Invoice 0001, PO 0001 and delivery note 0001 can all exist on the same day without conflict, because their prefixes differ. The real danger is two people or two outlets drawing numbers from one counter without coordination.
With multiple branches, you have two options:
- A separate counter per branch, with the branch code in the number. Each outlet runs its own sequence, for example INV/SBY/2026/0001 and INV/MLG/2026/0001. This is the safer choice if outlets sometimes work offline or use separate cashier systems, because they never need to check with each other.
- One central counter for all branches. The whole company shares a single sequence. This only works if every branch is always connected to the same system. If one outlet types numbers by hand during an internet outage, duplicates are almost guaranteed.
Most multi-outlet businesses are better off with option 1. Receipts and payment vouchers follow the same logic. Keep them on their own sequence, separate from invoices, because one invoice can be paid in several instalments.
December documents entered in January
Most numbering mistakes happen here. Suppose goods were delivered on 30 December but the invoice is only typed on 5 January. Which number does it get?
The document date decides. If the invoice is dated 30 December, it takes the next number in the 2025 sequence, for example INV/2025/12/0154, even though it was created in January. The 2026 sequence stays untouched.
To make this work in practice:
- Set a cutoff date. For example, all December documents must be entered by 10 January. After that, December is closed.
- Keep the 2025 counter open until the cutoff. In early January your system needs two active sequences: 2025 for late entries and 2026 for new documents.
- Lock the period after closing. Once the 2025 books are closed, the system should refuse new documents dated 2025 unless a supervisor reopens the period.
- Never reuse numbers to fill gaps. Giving a cancelled number to a new document breaks the audit trail.
It may seem simpler to date the late invoice in January instead. Check with your accountant before you do. The date decides which year the revenue and VAT belong to.
What your software should enforce automatically
If numbering depends on an admin remembering the last number in a spreadsheet, duplicates are only a matter of time. A decent system should handle the following without anyone having to think about it:
- Assign the number on save or posting, not when the form opens. Otherwise every abandoned draft leaves a gap.
- Enforce unique numbers in the database. Two users saving at the same second must never get the same number.
- Block regular staff from editing numbers manually.
- Keep separate counters per document type, branch and year, and take the year from the document date.
- Cancel documents instead of deleting them. A cancelled invoice keeps its number, with a “void” status and a reason. Corrections go through a credit note.
- Lock periods after closing.
- Keep an audit log of who created, changed or cancelled each document, and when.
- Produce a gap and duplicate report that lists missing or repeated numbers for each period, so you can review it before closing.
Most invoicing and accounting apps on the market already offer these as settings. You set the prefix and reset rule once. If you use a custom-built system or spreadsheets, adding proper numbering logic usually takes a few days of developer work. Depending on how many document types and branches are involved, that often costs around Rp5–15 million. Cleaning up a year of duplicates during an audit costs far more.
Before your first 2026 invoice goes out, do three things:
- Run a gap report for 2025 and note the reason for every missing number.
- Confirm the new format and reset rule in your system settings.
- Agree on the December cutoff date with your team and your accountant.
Your system may not support some of the points above, or your branches may keep producing duplicate numbers. In that case, contact CodeWorks. We will review your setup and tell you honestly whether a settings change is enough or whether it needs development work.