# How to Design a GST Invoice Numbering System Across Financial Years A GST invoice numbering system should assign a consecutive number within a controlled series and keep that identifier unique for the financial year. Rule 46 permits one or multiple series and limits the invoice serial number to sixteen characters, using letters, numerals, hyphens and slashes. Build the system around those boundaries before adding branch names, document labels or software-generated prefixes. ## Choose a number people can read accurately A practical number might be MH/26-27/000123. Count every slash, hyphen and digit before approving it. This example has fifteen characters. A longer location name may exceed the limit even though the running number itself is short. Store the complete issued number as a text field so spreadsheets do not remove leading zeros. Write a short numbering policy that explains each component, the next available counter and the financial year covered. The policy should state which supplying GSTIN uses the series. Where multiple registrations share an accounting platform, do not rely on an internal database key that the customer never sees to distinguish otherwise confusing documents. ## Decide where separate series help Branches, sales channels or different operational teams may need separate series. Multiple series are allowed, but each should have a clear owner. Separate series can reduce collisions where a warehouse issues dispatch invoices while a service team bills milestones. They also create more counters to monitor, so avoid a new prefix for every salesperson. For an illustrative business, BLR/2627/00125 and DEL/2627/00086 distinguish two teams. Confirm the character counts and the exact registrations involved. The next Bengaluru invoice follows its own approved series; it does not copy Delhi's counter simply because Delhi issued the most recent invoice in the group. ## Plan the financial-year transition before April A financial-year change is a controlled configuration event. Decide whether the running counter restarts or continues and how the year is represented. Rule 46 requires uniqueness for the financial year; it does not prescribe a particular “2026-27” prefix or require every business to restart at one. Create the next year's series in advance, restrict its use until the correct date and test a draft. Review scheduled invoices, offline work and transactions awaiting approval. A draft created in March but issued in April needs the appropriate issue date and approved series. Do not move a completed March supply into April merely to make the counter convenient. ## Treat cancelled numbers as records If an issued invoice is cancelled, retain the number and reason in the register instead of returning it to the available pool. Reusing it can leave two customer copies with the same identity and different values. Keep the invoice status, cancellation date, approval and any electronic invoice or return actions together. A skipped number is not explained by deleting a row. For example, if invoices 00118 and 00120 exist, record whether 00119 was cancelled, reserved unsuccessfully or never issued because of a system failure. The response depends on the facts. Preserve evidence rather than manufacturing a sale or backdated document merely to make the sequence appear continuous. ## Prevent collisions at the point of issue The final number should be allocated through a controlled process. Two users opening the same draft counter must not both issue invoice 000451. If staff work offline, allocate distinct approved series or another reliable method that prevents duplicate issuance. Reconcile offline documents when they return to the main register. Keep quotation, pro forma, delivery challan and credit-note numbering separate from tax invoice numbering. Their internal references can be displayed on the invoice, but the customer should see one clear tax invoice identifier. Configure integrations to transmit the full number, including separators and leading zeros, without silently shortening it. ## Use a small month-end sequence review Review the first and last number issued in each active series, the count of issued invoices and the count of cancelled or otherwise explained numbers. Compare the resulting register with accounting records and relevant outward-supply reporting. Check for duplicate number/date combinations and unexpected series that someone activated during testing. Suppose a series runs from 000101 through 000140. There are forty positions. If thirty-eight invoices remain active and two are documented as cancelled, the sequence is explained. A sales value reconciliation is still needed: forty positions do not prove that the correct taxable amounts were reported. ## Keep the policy usable during a system change Before migrating billing software, export the existing invoice register and the last used counters. Test whether the new system preserves special characters and text values. If the old system issued MH/26-27/000123, importing it as MH2627000123 can break matching even though it looks similar. A strong numbering design is short, documented and difficult to bypass. Its success is measured by whether staff can locate an invoice unambiguously, explain gaps and carry the series across April without duplicate identities. That makes collection, correction and GST reconciliation far easier than an elaborate prefix that only its creator understands. During the first month after migration, compare customer payment references with imported invoice identifiers. A bank narration may omit punctuation, so search should tolerate that for locating a document while preserving the official number unchanged. Record any cross-reference used during migration. Staff should never have to invent a new invoice number merely because an older one is difficult to search. ## Sources and references - [CBIC CGST Rules: invoice, voucher, valuation and record provisions](https://cbic-gst.gov.in/pdf/01062021-CGST-Rules-2017-Part-A-Rules.pdf)