Invoice numbering done right — one sequence, no mysteries

One unbroken run of numbers per document type, issued in order, never reused. Quotes, invoices and credit notes each keep their own sequence with their own prefix — in InstaJack that is Q-1001 up for quotes, INV-2001 up for invoices and CN-4001 up for credit notes — so the type is visible from the number alone and no two document families can collide.

The sequence must not skip silently. Gaps happen legitimately — a draft abandoned before issue is not an issued number — but an issued number that vanishes (a deleted invoice, a re-used number) reads at audit like a hidden sale. The rule that protects you: once a number is issued, the document exists forever, even if it is later cancelled — cancelled by a credit note, not by deletion.

Both Gulf e-invoicing systems build on the sequence. The UAE's system runs on structured invoices whose identity includes their number, and Saudi's Phase 2 chains every invoice cryptographically to the one before it — a missing or duplicated number is not a cosmetic issue in either design, it is a broken chain. Firms whose numbering is already disciplined will feel no change; firms whose numbers live in a spreadsheet edited by three people will.

The small-firm guide to UAE e-invoicing sets out the wider preparation; numbering is the cheapest part of it to fix early.

Three habits. Issuing by hand alongside the system — one invoice from the app, one from a Word template — splits the sequence into two runs that cannot be reconciled. Reusing a cancelled invoice's number for the next job, which makes two customers hold the same identity. And back-dating into a closed period, which puts numbers out of date order and invites the exact questions the sequence exists to answer.

The fix is boring and total: every document of a type comes from the one sequence, in the one system, in date order. Where a mistake happens, the correction is a document too — credited, noted, explained — never an erasure.