GST e-invoicing is not a separate invoice format created by the government. The supplier continues to prepare the invoice in its own accounting or ERP system and reports the prescribed invoice data to an Invoice Registration Portal (IRP). After validation, the IRP returns an Invoice Reference Number (IRN) and signed QR code. GSTN's official e-invoice overview explains this reporting model and the flow to GSTR-1.
What makes an e-invoice different from an ordinary GST invoice?
The key difference is registration of the prescribed document data with an IRP. A successful report produces a unique IRN and signed QR code. The IRN is generated from key document attributes, including supplier GSTIN, financial year, document type and document number. The official IRP guidance on IRN explains the hash-based identifier and supported document types.
This matters operationally because an invoice can look correct in an ERP yet still fail IRP validation. Finance teams therefore need controls for both the accounting document and the IRP response.
Can an e-invoice be amended after IRN generation?
No. The IRP does not provide an amendment facility for a generated e-invoice. The official IRP FAQ states that details furnished to the IRP cannot be amended. If an error is identified within the permitted cancellation window, the IRN can instead be cancelled and the transaction can be corrected through the appropriate process.
This distinction is easy to miss: correcting an invoice in the ERP does not itself alter the IRN already registered with the IRP.
How long is the IRN cancellation window?
The IRP permits cancellation of an active IRN within 24 hours of generation. The IRIS IRP cancellation guide confirms that only active IRNs generated within the last 24 hours are considered for cancellation through that facility.
If an e-way bill has already been generated for the invoice, the interaction between e-way bill status and IRN cancellation must also be checked. The official FAQ explains that an active e-way bill can prevent IRN cancellation and may need to be cancelled first, subject to the applicable conditions.
What should you do if the 24-hour cancellation window has expired?
Once the IRP cancellation window has expired, the original IRN cannot simply be amended on the IRP. The accounting and GST-return correction must instead follow the legally appropriate route for the underlying transaction, which may involve a credit note or other return-level correction depending on the facts. Do not create a second invoice merely to hide the original error: duplicate or inconsistent document trails create reconciliation problems.
The correct treatment depends on what was wrong. A wrong commercial value, cancelled supply, incorrect customer GSTIN and wrong tax treatment can have different downstream consequences. Finance teams should document the error, preserve the original IRN trail and determine the correct GST document before changing return data.
Why duplicate IRN errors occur
The IRP performs de-duplication checks. The official troubleshooting guide lists duplicate IRN error code 2150 and explains that it can arise when a document already registered is submitted again. Before retrying a failed integration call, first check whether the earlier request actually generated an IRN.
This is especially important for ERP/API integrations. A network timeout can make the ERP appear to have failed even though the IRP accepted the request. Blindly resending the same payload can then produce a duplicate error.
Practical error-handling workflow
- Check the IRP response first: record the IRN, acknowledgement number, acknowledgement date and signed QR code when generation succeeds.
- Do not blindly retry timeouts: query the IRN or document details before resubmitting the same invoice.
- Classify the error: separate schema or validation failures from business-data mistakes and duplicate-reporting issues.
- Correct before registration where possible: maker-checker controls on GSTIN, document number, tax values and document type reduce costly post-IRN corrections.
- Use the 24-hour window carefully: if a registered invoice genuinely needs cancellation, act promptly and check e-way bill status.
- Preserve the audit trail: retain the original invoice, IRP response, cancellation response and any subsequent credit note or corrected document.
Worked example: wrong customer GSTIN
Suppose an accounts team generates an IRN but then discovers that the buyer GSTIN was entered incorrectly. The IRP does not allow the registered invoice to be edited. If the error is found within 24 hours and the cancellation conditions are satisfied, the team can cancel the IRN and then issue and report the corrected document through the proper process. If the 24-hour window has expired, the team should not assume that changing the ERP master or GSTR-1 alone rewrites the original IRN; the appropriate GST correction route must be evaluated and documented.
How long can e-invoice JSON be downloaded?
GSTN's official e-Invoice JSON download FAQ states that generated and received e-invoice JSON is available for download for six months from IRN generation. Businesses should nevertheless maintain their own records rather than relying on portal availability as their document-retention system.
Key takeaway
Good e-invoice compliance depends as much on exception handling as on IRN generation. An e-invoice cannot be amended on the IRP, IRN cancellation is limited to the permitted 24-hour window, and duplicate retries can create avoidable errors. A strong process validates master data before reporting, checks IRP responses before retrying, acts quickly on genuine cancellation cases and preserves a complete audit trail for every correction.
