Invoice Numbering and Series Control: How It Breaks and How to Prevent It

Invoice numbering is a sequence that must be continuous, unique and explainable. It breaks almost always for the same three reasons: two systems issuing documents in parallel, a system migration mid-year, and somebody issuing a manual document when the system was down. All three are prevented by one decision made in advance.

This is an operational description, not advice. For what is required of your specific business, consult your accountant and the Tax Authority pages.

What breaks the numbering?

The last row matters in a multi-branch business: a separate series per branch is a legitimate decision, but it has to be a declared decision with a clear prefix - not the result of each branch setting up its own system.

What to do before starting in a new system

1. Check which number you reached - the last document issued under the old method.
2. Decide whether to continue the sequence or start a new series - both approaches exist, and the decision is made with your accountant.
3. Record the decision in writing, with a date. That is the document that will explain the jump a year from now.
4. Set the starting number in the system before the first document, not after.
5. Make sure the old system is blocked from issuing, so nobody keeps using it by mistake.

Step five is the forgotten one, and it is the common cause of two parallel series: the old system stayed open, and somebody used to it kept working there for another two months.

What to do when numbering has already broken

• Do not fix retroactively. A document already given to a customer is not changed; if it needs cancelling, issue a credit note.
• Record the gap - from which number to which, and why.
• Check there is no duplication - the same number on two different documents is worse than a jump.
• Close the source of the problem before continuing, or it happens again next month.
• Tell your accountant, so they do not discover it alone at year-end closing.

The rule: a jump in the sequence with a recorded explanation is a minor matter. A number appearing twice is a real problem, and so is a document the customer has that does not exist in the system.

Document types and separate series

In most systems each document type is managed in its own series - tax invoice, receipt, invoice-receipt, credit note, quote, payment demand. That is normal and even desirable, and the difference between the types is explained in tax invoice, receipt and invoice-receipt.

What to check in a system:

• That each document type gets its own series and they do not mix.
• That a credit note carries its own number and links to the original document.
• That a quote converted into an invoice does not create two documents in the same series.
• That the number appears on the document itself, prominently, not only in the system.

The monthly check, two minutes

Open the month's document list, sort by number, and look at three things: whether there are jumps in the sequence; whether any number appears twice; and whether the document count matches what you remember happening. Those three checks catch almost every problem in the month it was created, rather than at year-end closing.

How this relates to allocation numbers

An allocation number is an identifier obtained from the Tax Authority for an invoice above a given threshold, and it is entirely separate from your own invoice number. Both appear on the same document and serve different purposes: one is your internal sequence, the other is external confirmation for that invoice. The practical meaning: a document can take a number in your series and then wait for an allocation number, and you need to know what your system does in that state - as covered in what Israeli invoicing software must have.

What happens at a tax-year boundary

The start of a year is the natural moment to tidy numbering, and also the moment businesses unintentionally create two series. Three questions worth settling in December rather than January: whether to continue the sequence or open a new series; whether to embed the year in the number or keep a clean sequence; and whether the system can do it by itself or a setting must be changed manually. The answer to the third decides whether somebody has to remember to do something on 1 January - and memory is a poor mechanism.

What to check after changing systems

In the first month after a migration, three short checks prevent most problems: confirm the first document in the new system carries the number you decided on; confirm the old system is no longer issuing, by accident or by hand; and compare the month's document count against what you expect. The three checks take ten minutes and catch the problem while it is still two weeks old.

Sources

• Israel Tax Authority - Israeli invoices, the official page
• Morning - document issuing and document types
• Hashavshevet - modules and interface documentation