Can a rejected e-invoice be edited and re-uploaded?

Yes. When the IRP rejects an upload, no IRN is generated, and the invoice is not locked in any way. Correct the relevant fields in your billing or accounting software and re-upload to the IRP. The original reporting deadline for that invoice still applies, so act quickly.

Can an IRN be cancelled and a new IRN generated for the same invoice number?

An IRN can be cancelled within 24 hours of generation, provided no e-way bill has been issued against it. Once cancelled, the same invoice number cannot be reused for a new IRN. A fresh, unique invoice number must be assigned before generating a new IRN.

What to do if goods have already been despatched but the e-invoice was rejected?

If goods leave the premises without a valid IRN, the consignment lacks the required e-invoice documentation. Upload the corrected invoice to the IRP as soon as possible. If the reporting window has not lapsed, the invoice can still be registered. Moving goods without a valid e-way bill (where required) is a separate violation under GST law and carries its own penalties.

Does every registered GST taxpayer need to generate e-invoices?

No. E-invoicing applies to businesses whose AATO exceeds the notified threshold. As of April 2023, this threshold is ₹5 crore. Businesses below this limit are not required to generate e-invoices, though they may do so voluntarily. Banks, insurance companies, financial institutions and certain government bodies are exempt regardless of turnover.

Common E-Invoice Rejection Errors and How to Fix Them

When an e-invoice is uploaded to the IRP, the portal runs automated checks before issuing an IRN. If any field fails validation, the IRP rejects the upload and returns a specific error code. There is no manual override. The invoice data must be corrected and re-uploaded. The most common reasons for rejection are invalid Goods and Services Tax Identification Numbers (GSTINs), duplicate invoice numbers, incorrect Harmonised System of Nomenclature (HSN) codes, tax calculation mismatches and expired reporting windows. Each error code maps to a specific field or rule, making it possible to trace and fix the problem at source.

Why does the IRP reject e-invoices?

The IRP is a validation engine before it is a registration system. It checks every field in the uploaded JSON against three sources: GSTIN master data from the GST portal, the HSN master and the e-invoice schema published by the GSTN.

If a field is missing, incorrectly formatted or inconsistent with GST rules, the IRP returns an error code and a description that identify the failing field. The invoice is not locked and can be corrected and re-uploaded. But the original reporting deadline for that invoice still applies, so quick resolution is important.

What are the most common e-invoice rejection errors?

The table below covers common e-invoice rejection errors and resolutions:

Error type	Likely reason	How to fix
Invalid supplier GSTIN	GSTIN not registered, incorrectly entered or belongs to a different PAN	Verify the GSTIN on the GST portal and update supplier master data.
Invalid recipient GSTIN	Buyer GSTIN is inactive or incorrectly entered	Check buyer details on the GST portal before invoicing.
Cancelled or inactive GSTIN	GSTIN was cancelled after registration	Confirm status on the GST portal. If cancelled, issue a bill of supply where applicable.
Duplicate invoice number	Same invoice number already has an IRN	Use a new unique invoice number. The existing IRN cannot be reassigned.
Invalid document date	Date is in the future or predates GST registration	Correct the invoice date to a valid past date within the financial year.
Invoice beyond reporting time limit	Invoice not uploaded within the permitted window for the turnover slab	Check the applicable time limit for your Annual Aggregate Turnover (AATO). Late invoices cannot be registered.
Wrong document type	Document type code does not match the transaction	Select the correct code: INV for a tax invoice, CRN for a credit note, DBN for a debit note.
HSN length error	HSN code has fewer digits than required for the turnover slab	Use 4-, 6- or 8-digit HSN codes based on AATO.
Invalid tax rate	Tax rate is not applicable to the HSN or SAC code entered	Verify the correct GST rate on the GST rate schedule for the relevant HSN.
Tax value mismatch	CGST, SGST or IGST does not match the schema-level calculated amount	Recalculate tax values using the system and avoid manual entry.
Invalid PIN code or state code	PIN code does not match the state code for the place of supply	Verify the PIN code and state code combination for the delivery address.
Wrong place of supply	State code does not match the buyer’s location	Correct the place of supply state code to match the delivery address.
E-way bill field error	Transporter or vehicle details missing for consignments above ₹50,000	Add transporter ID and vehicle number before uploading to the IRP.

What GSTIN errors cause e-invoice rejections?

GSTIN errors are among the most frequent reasons for IRN generation errors. The IRP checks supplier and recipient GSTINs against the GST portal’s master in real time. A GSTIN that is inactive, suspended or cancelled will not pass validation, even if the business was legitimate at the time of the transaction. GSTINs entered incorrectly (transposed digits, wrong state code prefix) also fail.

Before creating an invoice, verify both GSTINs on the GST portal. If a buyer’s GSTIN has been cancelled, a tax invoice cannot be issued in their name. The transaction may require a bill of supply or other documentation depending on the nature of the supply.

What invoice data errors trigger IRN generation failure?

Three invoice data errors account for a large share of rejections:

The invoice date must not be in the future and must not pre-date the supplier’s GST registration.
The invoice number must be unique within the Financial Year (FY). Once an IRN is issued for a number, the same number cannot be used again.
The IRP enforces a reporting time limit. From 1 May 2023, businesses with AATO above ₹100 crore must upload e-invoices within 30 days of the invoice date. Invoices uploaded after this window are rejected and cannot be registered.

Which HSN/SAC and tax errors affect e-invoice generation?

The required length of an HSN code depends on turnover. Businesses with AATO above ₹5 crore must use 6-digit HSN codes, while those in certain product categories with higher turnover must use 8-digit codes. An HSN code that does not exist in the GSTN master or that has fewer digits than required will be rejected.

Tax value errors usually come from manual entry. If CGST, SGST or IGST is keyed in rather than calculated by the system, rounding differences or arithmetic errors can produce a mismatch with the schema-level calculation. The fix is to rely on software-calculated tax values and avoid overriding them.

How do PIN code, state code and place of supply errors cause rejections?

The IRP cross-checks the PIN code of the delivery address against the state code for the place of supply. A PIN code from one state paired with a state code from another fails immediately. The place of supply also determines the tax type. An interstate supply requires IGST; an intrastate supply requires CGST and SGST or Union Territory Goods and Services Tax (UTGST). An incorrect place of supply can result in the wrong tax type being applied, creating both an IRP rejection and a compliance error that is difficult to reverse.

How do e-way bill errors affect e-invoice generation?

When a consignment’s value exceeds ₹50,000, the IRP can generate an e-way bill at the same time as the IRN if transporter details are included in the JSON payload. If these fields are missing, the e-invoice may still be registered, but no e-way bill is generated, which means goods may leave the premises without the required documentation. In some configurations, missing mandatory e-way bill fields cause the entire upload to fail. Always include the transporter ID and vehicle details in the payload for goods consignments above the threshold.

How can you prevent e-invoice rejection before upload?

Most rejections are avoidable. Running these checks before generating the JSON and uploading to the IRP will catch the majority of errors.

GSTIN validation

Old or incorrect GSTIN data is the leading cause of rejections. Verify the following before raising an invoice:

Check supplier and recipient GSTINs on the GST portal before creating the invoice.
Confirm both GSTINs are active and not suspended or cancelled.
Update buyer and supplier master data whenever GSTINs change.

HSN/SAC validation

An incorrect or incomplete HSN code will fail IRP validation. Run these checks for every line item:

Confirm the HSN or SAC code exists in the GSTN HSN master.
Match the digit count to your AATO bracket (4, 6 or 8 digits as applicable).
Do not use generic or placeholder HSN codes.

Invoice date checks

Date-related errors are easy to miss when invoices are raised near the end of a financial year or reporting period.

Ensure the invoice date is not a future date.
Verify the date falls within the permitted reporting window for your turnover slab.
Check the FY boundary carefully if the invoice is raised near 31 March.

Tax calculation checks

Tax mismatches typically come from manual overrides. These GST e-invoice error checks remove the most common trigger:

Use software-calculated tax values and avoid manual entries.
Confirm whether IGST or CGST/SGST applies based on the place of supply.
Verify the PIN code and state code of the delivery address match before upload.

Document type and invoice number checks

These two fields are often overlooked when reissuing or correcting invoices:

Select the correct document type code for the transaction (INV, CRN or DBN).
Verify the invoice number is unique within the FY before upload.

Conclusion

Most e-invoice rejection errors trace back to stale master data, manual entry mistakes or mismatched GST fields. The IRP error code tells you exactly which field failed. The fix is in correcting the source record and re-uploading within the reporting window. For businesses generating high volumes of invoices, a rejection is more than a correction task. A missed reporting window means the invoice cannot be registered at all. TallyPrime validates GSTIN, HSN and tax fields at the point of invoice creation, reducing the chance that an error reaches the IRP.