The 64-character hash that makes a GST invoice valid — where it comes from and what you can still change afterwards.
An IRN is a 64-character hash returned by the Invoice Registration Portal when a B2B invoice is successfully registered. It is derived from the supplier's GSTIN, the document number, the document type and the financial year, which means the same invoice cannot be registered twice. Alongside it the portal returns a digitally signed QR code that must be printed on the invoice.
The IRN is what turns a document your system produced into a tax invoice the government recognises. For the issuer it is a compliance obligation; for the recipient it is the basis of input tax credit. The derivation from your own GSTIN and document number is deliberate: it makes duplicate registration impossible and ties the document to your numbering series.
The invoice data is assembled in the prescribed JSON schema, including line-level HSN, rates and values.
Directly or via a GSP. The portal validates the structure and the GSTIN details.
Along with the acknowledgement number, acknowledgement date and the signed QR code.
The IRN belongs on the invoice record in your ERP, not in a spreadsheet. It will be needed for reconciliation and for any cancellation.
The signed QR code must appear on the issued document so it can be verified independently.
A business running three dispatch locations starts getting duplicate IRN errors a few weeks after go-live. The invoices are plainly different — different customers, different values, different dates.
The cause is in the numbering. Each location was configured with its own document sequence, and all three sequences were started at 1 under the same GSTIN. The IRN is computed from supplier GSTIN, financial year, document type and document number — so location A's invoice 247 and location B's invoice 247 are, as far as the portal is concerned, the same document submitted twice. The portal is right and the configuration is wrong.
The fix is a numbering scheme that is unique across the whole GSTIN: a location prefix, or non-overlapping ranges per site. It is a five-minute configuration change and a painful one to make three weeks in, because the invoices already issued have to be reconciled and the sequence restarted cleanly. This is the kind of decision that costs nothing before go-live and real time afterwards, which is the argument for walking through numbering before the first submission rather than after the first error.
| Term | What it means |
|---|---|
| Hash | A fixed-length value computed from the invoice contents. Change any input and the hash changes, which is what makes it tamper-evident. |
| Supplier GSTIN | One of the inputs to the IRN, along with financial year, document type and document number. |
| Document type | Invoice, credit note or debit note. Part of what makes the IRN unique. |
| Duplicate IRN | The error returned when the same supplier, year, type and number are submitted twice. Usually a numbering problem. |
| Ack number and date | The acknowledgement the portal returns alongside the IRN, recorded as proof of registration. |
The IRN derivation includes your document number. Reusing one within the same financial year will be rejected as a duplicate.
An IRN can be cancelled only within a limited period after generation. After that, the correction has to be made through a credit note.
Reconciling registered invoices against issued invoices is impossible if the IRN is not on the invoice record.
A registered invoice cannot be edited. Changes are made through credit or debit notes, which are themselves registered.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Duplicate IRN errors | Almost always a document numbering problem, and usually a structural one. | Treating them as transient and retrying, which never resolves the cause. |
| IRN-to-invoice reconciliation gaps | Invoices in your ledger with no IRN, or IRNs with no matching invoice. | Reconciling only on count rather than on value and number. |
| Cancellation rate | How often invoices are raised wrongly and withdrawn inside the window. | Cancellations replaced by a fresh invoice with no record of the original. |
| Average registration latency | Whether registration is keeping pace with invoicing or queueing up. | Measuring only successful calls, which excludes the slow ones that timed out. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.