An Invoice Reference Number (IRN) is not the same thing as the invoice number created in a seller's accounting system. Under India's GST e-invoicing system, the supplier first creates the invoice in its own ERP or billing software and then reports the prescribed invoice data to an Invoice Registration Portal (IRP). After validation, the IRP returns an IRN and a digitally signed QR code. The GSTN-authorised IRIS IRP e-invoicing FAQ explains this process and the role of the IRN.
Invoice number, IRN and QR code: the basic difference
The invoice number is the supplier's own document number. It is part of the tax invoice and is generated according to the supplier's numbering system, subject to GST invoice requirements. The IRN is a unique hash generated when the invoice is successfully registered with an IRP. The QR code is the digitally signed code returned by the IRP and contains selected invoice particulars, including the IRN.
These three identifiers therefore perform different jobs. The invoice number identifies the commercial document in the supplier's books. The IRN establishes successful registration of the reported invoice data in the e-invoicing system. The signed QR code provides a practical way to verify key registered invoice details.
How an e-invoice is generated in practice
- Create the invoice in the normal accounting system. E-invoicing does not mean that every supplier must prepare its commercial invoice inside the government portal.
- Report the prescribed invoice data to an IRP. Applicable taxpayers can use the available reporting modes supported by the e-invoicing ecosystem.
- IRP validates the submitted data. If the data passes validation, the system generates the IRN.
- Receive the signed QR code. The IRP returns the registered invoice information with the digitally signed QR code.
- Issue the invoice to the customer. The seller's final invoice should carry the required e-invoice particulars, including the QR code where the mandate applies.
What exactly is the IRN?
The IRN is a 64-character hash associated with a registered invoice. It is generated after the invoice data is uploaded to and validated by the IRP. It should not be confused with the acknowledgement number or the supplier's invoice number.
A useful control for finance teams is to retain the supplier invoice number, IRN and IRP acknowledgement details as separate fields in the ERP or reconciliation file. Combining them into one field can make cancellation, GSTR-1 reconciliation and audit tracing unnecessarily difficult.
What information does the signed QR code contain?
The GSTN-authorised IRP FAQ lists key particulars embedded in the QR code, including the supplier GSTIN, recipient GSTIN, supplier invoice number, invoice date, invoice value, number of line items, HSN code of the main item, the IRN and the IRN generation date. Because the QR code is digitally signed by the IRP, it can be used to verify that the invoice was registered.
Does e-invoicing replace the seller's ERP invoice?
No. The practical model is reporting rather than government-side invoice creation. The taxpayer continues to create the invoice in its accounting or billing system and reports the prescribed data to the IRP. After the IRN and signed QR code are received, the ERP can incorporate the returned information into the invoice shared with the customer.
This distinction matters during ERP implementation. Businesses should design a workflow that prevents an invoice requiring e-invoicing from being treated as fully issued before successful IRP registration.
Can an e-invoice be amended on the IRP?
The IRP FAQ states that an e-invoice cannot be amended on the IRP after registration. It can be cancelled within the permitted 24-hour window, subject to the system conditions described in the guidance. If an error is discovered, finance teams should not simply overwrite the IRN-linked record in the ERP and assume the registered data has changed.
This creates an important internal-control point: master data, GSTIN, document type, invoice number, taxable values, tax rates and HSN details should be validated before the invoice is sent for registration.
How e-invoice data connects with GSTR-1
Successful e-invoice reporting also supports downstream GST compliance. The IRP FAQ explains that reported invoice data is transmitted to the GST system for auto-population into the supplier's GSTR-1. Auto-population reduces duplicate data entry, but it does not remove the need for reconciliation.
Before filing GSTR-1, businesses should compare the sales register, successfully generated IRNs, cancelled IRNs and the e-invoice-populated data. This helps identify missing registrations, duplicates, cancellations or ERP-to-portal mismatches.
Worked example
Suppose ABC Pvt Ltd creates invoice INV-2458 in its ERP for a registered customer. INV-2458 is the supplier's invoice number. ABC reports the prescribed data to an IRP. After successful validation, the IRP generates a 64-character IRN and returns a digitally signed QR code. ABC's customer may therefore see all three on or in connection with the invoice: INV-2458 as the commercial invoice number, the IRN as the registration identifier, and the QR code as the machine-readable signed verification element.
If ABC later searches its ERP only by IRN, it should still be able to trace back to INV-2458. Conversely, searching INV-2458 should reveal the IRN status and whether the registration was active or cancelled.
Finance-team checklist for e-invoice controls
- Keep identifiers separate: store invoice number, IRN and acknowledgement details in distinct ERP fields.
- Block dispatch or final issuance when required registration fails: build an exception workflow rather than allowing users to ignore IRP errors.
- Validate customer GSTIN and master data: incorrect recipient data can create difficult corrections after registration.
- Track cancellations: preserve the link between the original invoice number and cancelled IRN for audit trail purposes.
- Reconcile with GSTR-1: compare the sales register, IRN register and portal-populated data before return filing.
- Verify suspicious invoices: use the signed QR-code verification functionality available in the e-invoicing ecosystem.
Common mistakes to avoid
- Calling the IRN the 'invoice number' in ERP fields or customer communication.
- Assuming that generating a PDF invoice in accounting software automatically creates an e-invoice.
- Editing ERP data after IRN generation without considering the registered invoice data.
- Assuming GSTR-1 auto-population eliminates the need for sales-register reconciliation.
- Treating the QR code as a decorative image rather than a signed verification element returned through the IRP process.
Practical takeaway
For GST e-invoicing, think of the three elements as a chain: the supplier creates an invoice number, the IRP registers the reported invoice and generates an IRN, and the IRP returns a digitally signed QR code carrying selected registered particulars. Keeping these concepts separate makes ERP design, customer verification, cancellation tracking and GSTR-1 reconciliation much cleaner.
