Fix E-Invoice IRN Rejection: What Each Error Means and How to Get the IRN Generated
For billing clerks and accountants whose invoices come back from the portal without an IRN: what each error means, how to fix it, and how to catch it before you submit.
To fix e-invoice IRN rejection, read the error code first. The portal's messages are brief, and a rejection for a rounding difference looks just as alarming as one for a cancelled GSTIN. The fix for each is very different.
Most rejections come from a few causes that can be checked before submission. Businesses that check nothing in advance meet them at dispatch time, with a truck waiting and a customer asking for the invoice.
This page explains the common errors, gives an illustrative example from Hyderabad, and shows how Apragya checks the invoice before it reaches the portal.
Why the IRN is refused, and the fix
An IRN rejection means the Invoice Registration Portal checked your invoice and refused it. The invoice is not a valid e-invoice until an IRN is generated, so it should not go out with the goods.
The most common causes are: a document number that already has an IRN; a buyer GSTIN that is not active; a place of supply that does not match the buyer's state; line values and tax that do not add up to the total; an invalid HSN code; and a supplier GSTIN not enabled for e-invoicing. Authentication failures also look like rejections.
Read the error code, fix the cause on the invoice, and submit again. Do not change the invoice number to get past a duplicate error.
- Read the portal's error code and message, not just 'failed'.
- For a duplicate error, fetch the existing IRN for that document number instead of generating again.
- Check the buyer GSTIN is active, and that its first two digits match the place of supply.
- Recompute taxable value and tax line by line, and fix rounding on the total.
- Check HSN codes, the document number format and the invoice date.
- Check your own GSTIN is enabled for e-invoicing and your API credentials are valid.
- Submit again, and print the IRN and QR code on the invoice.
IRN generation error: what you see and what it means
What it means
- That document number already has an IRN; fetch it rather than regenerate.
- The buyer's GSTIN is cancelled or wrong; check it on the GST portal.
- For a registered buyer, the GSTIN's state decides the place of supply.
- Line values, tax and rounding do not add up exactly.
- Credentials, token or IP whitelisting need attention, not the invoice.
An example: a Hyderabad pharma distributor
Take an illustrative distributor raising 250 invoices a day. On a Monday, 14 invoices were refused. The billing lead went through each check before resubmitting.
The Monday rejections, checked one by one
- Duplicate document numberTwo retries of invoices that already had IRNs.Checked
- Buyer GSTIN activeOne chemist's GSTIN had been cancelled.Mismatch
- Place of supplyFive bills used a ship-to state.Mismatch
- Totals add upSix bills had a paisa rounding gap.Mismatch
- HSN codesAll codes valid.Checked
- API credentialsToken fine; no login issue.Ready
The two retries simply needed their existing IRNs fetched. Six invoices were rebuilt from their lines, five had the place of supply corrected from the buyer's GSTIN, and the cancelled-GSTIN chemist was billed after the sales team confirmed new details. All went out the same afternoon.
How Apragya reduces e-invoice error codes before submission
Step 1 of 5
Totals rebuilt from lines
The payload is computed from the lines, and a gap is flagged before sending.
- Totals rebuilt from lines: The payload is computed from the lines, and a gap is flagged before sending.
- Place of supply from GSTIN: A registered buyer's GSTIN decides the state, not the address.
- GSTIN lookup: Buyer GSTIN details can be fetched from the portal.
- Errors in plain words: Common portal codes are translated into what to fix.
- IRN and QR on the invoice: The IRN, acknowledgement and signed QR are saved on the record.
Handling IRN rejections: by hand or before submission
Fixing rejections one by one at the portal works on a quiet day. Checking the same rules before submission means most invoices go through the first time.
Portal-only e-invoicing, against Apragya
| Feature | Upload and retry | Apragya |
|---|---|---|
| Totals | Copied from the invoice header | Recomputed from lines, checked first |
| Place of supply | Taken from the address | Taken from the buyer's GSTIN |
| Error messages | Codes to look up | Plain explanation of the fix |
| Portal refusal | Sometimes taken as success | Treated as a failure |
| Cancellation | Missed window | Refused after 24 hours, with a credit note prompt |
Checked against public information on 16 September 2026.
What keeps IRN generation smooth
One record
Customer GSTIN and address come from the shared customer master.
E-way bill too
An e-way bill can be generated from the IRN.
Credentials kept safe
Portal credentials are stored encrypted.
Access by role
Who can generate and cancel IRNs can be set by role.
Audit log
Generation and cancellation are logged.
Multi-company
Each company keeps its own invoices and GSTIN.
Read the e-invoicing under GST guide and the IRN cancellation guide, and see e-invoicing in Apragya.
Getting started
- List last month's rejections by error code.
- Fix customer GSTINs and states in the master.
- Set up the portal credentials and whitelist the IP.
- Generate IRNs from the invoice record.
- Review any rejection the same day.
Once masters are clean, most rejections disappear.
What it costs to start
E-invoice IRN rejection, answered
Can I change the invoice number to get past a duplicate error?
How long can an IRN be cancelled?
Is there a time limit to report an invoice?
Why does a rounding difference cause a rejection?
What does it cost to start?
Get IRNs generated the first time
Check your invoices against the common rejection causes before they reach the portal.