← Back to blog GST compliance

GST Rule 46(b) Explained: What It Means for Your Invoice Numbering

Most businesses think of a tax invoice number as an administrative detail — pick something that looks tidy, move on. Under GST, it isn't optional bookkeeping style. Rule 46(b) of the CGST Rules spells out exactly how a tax invoice must be numbered, and getting it wrong makes the invoice non-compliant even if every other field — GSTIN, tax amounts, place of supply — is correct.

This is a plain-language walkthrough of what the rule actually requires and the mistakes that quietly break it.

What Rule 46(b) requires

In substance, a valid GST tax invoice number must be:

  • Consecutive — no gaps, and no repeats, within a series.
  • Unique for the financial year — the same number cannot be reused within the same financial year, even across different invoice series.
  • Up to 16 characters — alphabets, numerals, and the special characters hyphen (-) and slash (/) are permitted, in any combination.
  • Generated in one or more defined series — a business can run multiple numbering series (for example, separate series for different branches or invoice types), as long as each one is itself consecutive and the whole set stays unique for the year.

The financial year in India runs 1 April to 31 March — so in practice, most businesses reset or clearly demarcate their invoice series at the start of each financial year (e.g. 2025-26/00001), even though the rule's actual requirement is uniqueness within the year, not a literal reset.

Why "consecutive and gap-free" is harder than it sounds

On paper this sounds trivial — just count up by one. In practice, gaps and collisions creep in from a few very ordinary situations:

  • Two people (or two browser tabs) creating an invoice at the same moment. If numbering is just "read the last number, add one," two near-simultaneous invoices can both read the same last number and both save with the same next number — a genuine duplicate, not a typo.
  • A draft or a failed save. If a number gets reserved the moment someone opens a "new invoice" form, but they abandon it or the save fails, that number is never used — a gap.
  • Manual edits or spreadsheet-based invoicing. Anyone can accidentally type the wrong next number, skip one, or duplicate one from memory.

None of these require carelessness — they're just what happens by default once more than one person (or one retry) touches invoice creation, unless the numbering itself is protected against it.

What "protected against it" actually means

The reliable fix is a numbering step that's atomic — the "read the last number" and "reserve the next number" happen as a single, locked operation, so two invoices being created at literally the same instant still can't land on the same number. This is a database/software design property, not a policy someone has to remember to follow.

Settle's invoice numbering works exactly this way: each new invoice number is generated under a row-level lock scoped to the workspace and financial year, so the "last number used" can never be read by two invoice creations at once. The result is what Rule 46(b) actually asks for — consecutive, gap-free, unique-per-financial-year numbers — by construction, not by discipline.

A quick way to check your own invoices

Pull up your last 20–30 issued invoices for the current financial year and check:

  1. Do the numbers increase by exactly one each time, with no skips?
  2. Is every number genuinely unique — no two invoices sharing a number, even across different customers?
  3. Does the series reset cleanly at the start of the financial year, rather than continuing an old year's sequence?

If any invoice was ever created, then deleted or voided and its number reused for a different invoice, that's also worth a second look — reusing a number that was ever issued (even briefly) is exactly the kind of gap this rule is meant to prevent.

This article explains the numbering requirement in plain language for a general business audience — it isn't legal or tax advice. For a specific compliance question, consult a GST practitioner or chartered accountant.

Stop worrying about invoice numbering

Settle generates Rule 46(b)-compliant, race-safe invoice numbers automatically — free, unlimited invoices during early access.

Create your free workspace →