An e-invoice gets rejected the moment the Invoice Registration Portal can't validate the data you've sent it. Sometimes that's something as small as a wrong PIN code; other times it's a deeper mismatch between what your line items add up to and what your invoice total says. Either way, no valid IRN or signed QR code comes out the other end until the error is fixed.

For businesses pushing through a high volume of B2B invoices, repeated rejections aren't just annoying - they hold up dispatch, delay customer payments, stall e-way bill generation, and complicate GST return preparation.

This guide walks through the error codes that come up most often, what typically causes each one, and how to fix the underlying issue instead of just resubmitting and hoping.

• Key Takeaways
• What E-Invoice Validation Errors Are
• Quick Reference: Common Error Codes
• Fixing the Most Common Errors
• A Repeatable Process for Any IRP Error
• Recent and Upcoming Validation Changes
• Frequently Asked Questions

Key Takeaways

• An IRN is only issued once an invoice clears the IRP's schema, GSTIN, tax and business-rule checks.
• Don't keep resubmitting a rejected invoice blindly - read the error code and fix the actual cause first.
• Duplicate IRNs, invalid GSTINs, wrong HSN codes, tax mismatches and place-of-supply errors account for most rejections.
• Invoice-level totals must reconcile exactly with line-item taxable values, taxes, cess, discounts and other charges.
• Businesses with AATO of ₹10 crore or more can't report eligible documents once they age past the applicable 30-day window.
• Since 1 June 2025, invoice numbers are treated as case-insensitive during IRN generation.
• Additional Ship-to GSTIN checks are scheduled to take effect from 1 August 2026 for e-way-bill-linked IRNs.

What E-Invoice Validation Errors Are

An e-invoice validation error is the rejection message the IRP sends back when submitted data doesn't satisfy the e-invoice schema or the underlying GST business rules. Before issuing an IRN, the portal checks details including supplier and recipient GSTIN, document type, invoice number and date, transaction type, HSN/SAC, quantity and unit, taxable value, GST rate, CGST/SGST/IGST, place of supply, state and PIN code, export details, invoice-level totals, and whether the document has already been submitted.

If even one of those fields fails, the request comes back with an error code and message rather than an IRN. It's worth distinguishing this from a general invoice mistake: an e-invoice validation error is specifically what the portal flags during IRN generation, whereas a broader invoicing error - say, a wrong address or an incorrect tax rate - can exist quietly in your books long before it ever reaches the IRP.

Most rejections fall into a handful of buckets:

Quick Reference: Common Error Codes

This isn't an exhaustive list of every code the IRP can return, but it covers the ones that come up most often in practice:

For the full and current list, the official NIC IRP error-code reference is the authoritative source.

Fixing the Most Common Errors

Duplicate IRN (2150)

This usually means the document was already registered, or your system sent the generation request more than once - often from a double click, an API timeout that actually succeeded, two people submitting the same invoice, or an automatic retry firing before the first response was saved. Don't create a fresh invoice to work around it. Search for the document by invoice number, date and type, confirm whether an IRN already exists, retrieve it, and update your accounting record with that IRN instead of generating a new one.

Wrong Tax Type (2172 / 2174)

These two mirror each other. 2172 fires when IGST is applied to what looks like an intrastate transaction - supplier state matching place of supply, which should normally carry CGST and SGST. 2174 fires the opposite way, when CGST/SGST is applied to what looks like an interstate transaction. Don't just flip the tax type to make the error disappear - check the supplier state, buyer state, place of supply, and the bill-to/ship-to setup to confirm which treatment is actually correct for the transaction.

Invalid HSN or Unit Code (2176 / 2177)

A code that doesn't match the IRP's HSN or UQC master gets rejected outright - often from a typo, an outdated code, too few digits, or goods and services classifications getting mixed up. Search the correct code through the IRP's HSN lookup, confirm whether the item is goods or services, and update your item master so the fix carries forward instead of needing to be repeated on every invoice.

Invoice-Total Mismatches (2182-2194)

This family of errors means the numbers don't add up between line items and the invoice as a whole. As a working reconciliation:

Total taxable value = sum of all line-item taxable values
Invoice value = taxable value + GST + cess + other charges − invoice-level discount

Recheck quantity, unit price, discounts, taxable value, tax rate, CGST/SGST/IGST, cess, other charges and rounding. Avoid manually overriding a final total after the line items have already been calculated - that's the single most common way this mismatch creeps in.

GSTIN-Related Errors (2211, 2212, 2258, 2265, 2288, 3028, 3029)

These cover a range of GSTIN problems: supplier and recipient GSTIN being identical, an unregistered-person code used where a real GSTIN is needed, a GSTIN whose state prefix doesn't match the selected state, or a GSTIN that's simply invalid, inactive or not on file with the IRP. Check the GSTIN directly on the GST Portal, confirm its legal name and registration status, use the sync/update option where available, and correct the party master so the same mistake doesn't repeat on the next invoice.

Reporting-Window Errors (2284 / 2305)

These flag a document that's aged past the reporting period your turnover category allows - currently 30 days for businesses with AATO of ₹10 crore or more, counted from the document date. Confirm the date is correct, check your AATO-based reporting limit, and resist the temptation to backdate an invoice to slip past the check - that creates bigger compliance problems than the rejection itself. For the full deadline-management workflow, see our guide on the e-invoice 30-day reporting rule.

A Repeatable Process for Any IRP Error

Rather than treating every rejection as a one-off puzzle, a consistent process gets you to a fix faster and stops the same mistake from recurring:

At step 1, record the error code, full message, invoice number, document date, GSTIN, timestamp and the submitted JSON where relevant. At step 7, don't assume success just because the request was sent - confirm the response actually contains a valid IRN, acknowledgement number and date, the signed invoice, and the signed QR code before treating the invoice as reported.

Recent and Upcoming Validation Changes

A few rule changes are worth having on your radar if you're troubleshooting errors in 2026:

• Invoice numbers became case-insensitive from 1 June 2025 - "INV-101" and "inv-101" are now treated as the same document, so standardise your numbering rather than relying on letter case to differentiate invoices
• From 1 February 2026, certain item-value validations (errors 2194, 2234, 2235) were relaxed for notified HSNs using Retail Sale Price-based tax calculation - this relaxation only applies where the specific RSP conditions are met, not as a general workaround
• From 1 August 2026, additional Ship-to GSTIN checks apply where an e-way bill is generated with or through an IRN - Ship-to GSTIN becomes conditionally mandatory, Bill-to and Ship-to GSTINs can't be identical in a genuine bill-to/ship-to transaction, and Ship-to GSTIN, state and PIN code get validated together

If your billing setup uses ERP or API integration, it's worth testing against these changes well ahead of the effective dates rather than discovering the gap in production.

Preventing Errors Before They Happen

A handful of habits eliminate most rejections before they ever reach the portal:

• Validate buyer GSTINs at the point of billing, not at IRN generation
• Keep a controlled item master with correct HSN/SAC, classification, GST rate and unit code for every product or service
• Let your billing software calculate CGST, SGST and IGST automatically instead of typing values manually
• Standardise invoice numbering under one sequence per series and financial year
• Generate IRNs the same day an invoice is created rather than batching them at month-end
• Track which error codes recur most often - a repeated code usually points to a master-data or process problem, not a one-off mistake

How Billing Software Helps

Most validation errors trace back to the same handful of places: inconsistent customer records, an outdated item master, or tax values typed by hand instead of calculated automatically. Hitech Billsoft keeps GST-compliant invoicing, customer and item master data, and automated tax calculations in one workflow, which is exactly where most of these errors get caught before they ever reach the IRP.

Final Checklist Before Submission

Run through this before sending any invoice to the IRP:

• Invoice number is unique, correctly formatted, and no cancelled number has been reused
• Document date is accurate, not in the future, and within the applicable reporting window
• Supplier and recipient GSTINs are active, valid, and match their stated state codes
• HSN/SAC codes, unit codes and GST rates match the item master
• Quantity × price, discounts, taxable value and taxes reconcile at both line-item and invoice level
• CGST/SGST or IGST is applied correctly based on the actual place of supply
• The request is submitted once, and the response is checked for a valid IRN, acknowledgement and signed QR code

Conclusion

Most e-invoice validation errors trace back to one of four places: inaccurate customer or item data, incorrect transaction classification, mismatched tax calculations, or an uncontrolled invoice-generation process. Fixing the rejection in front of you matters, but fixing the master record behind it matters more - that's what keeps the same code from showing up again next week.

Treat a recurring error code as a signal to check your customer onboarding, product classification, tax configuration or billing controls, not just as one more invoice to patch and resubmit.