Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Most Odoo GST and e-invoicing failures come from one of three places: Indian localization or NIC configuration, invoice or tax data, or an IRN operation that has already happened. Check the setup and invoice status first, then fix the specific tax, GSTIN, HSN, UQC, or arithmetic error shown by the IRP. Do not resubmit blindly: an invoice may already have an IRN even when Odoo did not receive or display the successful response.
This guide covers Odoo’s Indian GST e-invoicing workflow, common IRP error codes, cancellation limits, and the checks to complete before filing GSTR-1. Odoo’s documentation describes its Indian localization as compliant with Indian GST e-invoice requirements, but a compliant system still depends on correctly configured credentials, eligible GSTINs, and valid invoice data.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsWhere should I start when Odoo e-invoice generation fails?
Start with configuration and processing status, not by changing invoice values at random. Confirm Indian Accounting, Indian E-Invoice Integration, NIC API credentials, and the sales journal’s E-Invoice option; then determine whether the invoice has already been submitted or assigned an IRN.
Check the Indian localization and NIC connection
- Confirm that Indian Accounting (
l10n_in) and Indian E-Invoice Integration (l10n_in_edi) are installed or enabled in the Odoo database. - Check that NIC e-invoice API credentials have been obtained and configured for the company’s e-invoicing connection.
- Confirm the sales journal used for the invoice has its E-Invoice option enabled. If this option is missing or disabled, resolve the journal configuration before diagnosing invoice fields.
- Verify that the relevant GSTIN is eligible and that e-invoice options are enabled for it on the portal. IRP error 3026 specifically indicates that e-invoice options are not enabled for the GSTIN.
These checks establish that Odoo is configured to create and transmit the e-invoice. They do not prove the invoice payload is valid: the IRP separately validates identity, tax treatment, codes, and totals.
#1 Best Overall
Inspect the invoice’s EDI status and response
Open the affected invoice and review its EDI or electronic-invoicing status and any processing error or invoice log available in Odoo. When processing fails, inspect the attached signed JSON if it is available. The payload helps distinguish a configuration failure from an incorrect value in the data Odoo sent.
After a successful submission, Odoo’s workflow can show the IRN, acknowledgment details, and QR code. If any of these already exist, treat the invoice as potentially registered and verify its status before requesting another IRN.
How do I fix GST validation errors in Odoo?
Match the tax treatment to the transaction’s place of supply, and reconcile the invoice’s line calculations with its totals. IRP validation checks taxable value and tax amounts, including CGST, SGST, IGST, cess, and the overall invoice value.
Choose the correct tax for the place of supply
For an intra-state transaction, the applicable split is CGST plus SGST; do not send IGST. For an inter-state transaction, use IGST rather than CGST and SGST. Where CGST and SGST both apply to a line, their amounts must be equal. Check the place of supply and state information before changing tax rates: a wrong place-of-supply value can make an otherwise familiar tax combination invalid.
| Transaction or validation issue | What to check | Relevant IRP error examples |
|---|---|---|
| Intra-state supply | Place of supply and state details; use CGST and SGST, not IGST. | 2172 |
| Inter-state supply | Place of supply and tax configuration; use IGST, not CGST and SGST. | Check the invoice’s tax and place-of-supply data; the supplied IRP error examples do not identify a separate inter-state code. |
| CGST and SGST split | Compare the two amounts on each line where both taxes apply. | 2182–2189, among the listed tax-total validation errors |
| Taxable value or tax totals disagree | Reconcile each line’s taxable value and taxes with the invoice-level totals. | 2182–2186; also 2227, 2234, 2235, and 2240 for listed tax and total conditions |
| GST rate is invalid or not notified | Use a notified GST rate appropriate to the supply and correct the tax configuration or invoice line. | 2240 |
The IRP lists errors 2172, 2182–2189, 2227, 2234, 2235, and 2240 for conditions involving tax selection, rates, or totals. Read the exact error returned for the invoice: a code points to a validation condition, not necessarily to the field that caused it in Odoo.
Reconcile line arithmetic before resubmitting
For each line, recalculate the assessable value from the amount and discount, then verify that the tax amount follows from that value and the selected rate. Compare the resulting line values with invoice-level taxable value, CGST, SGST, IGST, cess, and total invoice value in the payload. Errors 2182–2186 are examples of line and invoice-level taxable, tax, or cess totals not matching.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #2
- Review the invoice line’s quantity, unit, price, discount, and tax.
- Calculate the taxable or assessable value after discount.
- Check that the applicable tax amount is calculated from that value and that the tax type matches the place of supply.
- Add the line values and compare each tax category and the invoice total with the submitted payload.
- Correct the source invoice or its tax configuration, then generate and validate the updated payload.
Do not focus only on the grand total. A total can appear plausible while taxable value, one tax component, cess, or the line-to-invoice reconciliation is wrong.
Why am I getting invalid GSTIN, HSN, UQC, or location errors?
These errors usually point to master data or a missing invoice-line field. Verify both the value and its role in the transaction: supplier and recipient identities, product classification, unit code, quantity, and state or location codes all affect what the IRP accepts.
Verify supplier and recipient GSTINs
- Check that the supplier and recipient GSTINs are entered correctly and correspond to the intended parties.
- Confirm taxpayer type, active status, and registration dates in the relevant master data.
- Ensure the supplier and recipient are not the same GSTIN.
- For transactions where a registered supplier GSTIN is required, do not use URP as the supplier GSTIN.
IRP errors 2288 and 2291 identify invalid recipient or supplier GSTINs. Recheck the GSTN status and the party record rather than repeatedly resending an unchanged invoice. Registration dates and taxpayer type can matter even when the GSTIN string itself appears correctly formatted.
Check HSN, UQC, quantity, and invoice lines
Use the appropriate HSN classification for goods or services, and use a UQC from the IRP master-code list. Odoo’s GSTR-1 checks can flag missing or invalid HSN and invalid UQC; a value that is understandable to a user is not necessarily an accepted master code.
Recommended Free Tools
- Make sure the invoice contains at least one line.
- Check that each line has a quantity and a UQC.
- Use unique serial numbers for invoice lines.
- Confirm the HSN classification is present and appropriate for the line.
- Use a notified GST rate; do not substitute a rate based only on a similar product or service.
When Odoo’s GSTR-1 checks identify an HSN or UQC issue, correct the product or service data and the invoice as needed, then rerun the checks. Correcting only a return-level warning without correcting the source information can leave the submitted e-invoice payload invalid.
Validate state, pincode, country, port, and currency data
Check that the place-of-supply and state code agree with the transaction, and that the pincode-to-state mapping is valid. Also review country, port, and currency codes where those fields apply. A mismatch between a location code and its associated geography can cause validation problems even when the customer address looks complete to a person.
Rank #3
What do common Odoo e-invoice error codes mean?
Use the code to narrow the problem, then verify the underlying transaction and payload. The same broad symptom—such as “invalid data”—can have a different fix depending on whether the failure concerns identity, tax arithmetic, or an IRN that already exists.
| IRP code | Meaning described by the IRP guidance | Useful next check |
|---|---|---|
| 2150 | Duplicate IRN | Check whether the document has already been registered; avoid repeated or simultaneous requests and retrieve the existing IRN. |
| 2172 | IGST used for an intra-state transaction | Verify the place of supply and use CGST plus SGST where the supply is intra-state. |
| 2182–2186 | Line taxable, tax, or cess totals do not match invoice-level totals | Reconcile line calculations and each tax category with the submitted invoice totals. |
| 2240 | GST rate is incorrect or not notified | Check the line’s tax configuration and use a notified rate. |
| 2288 / 2291 | Invalid recipient / supplier GSTIN | Verify the GSTIN, party role, GSTN status, and master data. |
| 3026 | E-invoice options are not enabled for the GSTIN | Check GSTIN eligibility and portal configuration. |
The descriptions above are examples, not a complete list of IRP codes. If an error is not listed here, use the exact response returned with the invoice and inspect the relevant fields in Odoo’s status, log, or signed JSON rather than assuming it shares the cause of a similar-looking message.
Why does IRN say duplicate or already generated?
A duplicate IRN response means the document may already have been registered, or requests may have been sent repeatedly. First establish whether an IRN exists and to which GSTIN it belongs; do not create another submission simply because Odoo did not display the first response.
Check for an existing IRN before retrying
- Review the invoice’s EDI status and available acknowledgment details in Odoo.
- Check whether an IRN was returned or already recorded for the document.
- If the IRN exists, retrieve or store that existing IRN in the ERP workflow instead of resending blindly.
- If no IRN is recorded, investigate whether a prior request completed outside the visible Odoo status before making another request.
IRP error 2150 is the listed duplicate-IRN example. Avoid simultaneous or repeated requests for the same document, and allow the response to update the ERP record. If the existing IRN is associated with another GSTIN, the current user cannot perform cancellation or other operations on it; confirm that the logged-in GSTIN is the one entitled to act.
Also check whether the IRN has been cancelled and whether the requested operation is still within the permitted period. A duplicate response, an IRN owned by a different GSTIN, a cancelled IRN, and an expired operation window are distinct cases and should not be treated as one generic retry problem.
Can I amend or cancel an e-invoice to correct it?
An e-invoice cannot be amended on the IRP. IRIS IRP FAQ guidance says, “E-invoice cannot be amended but only cancelled.” Cancellation is the correction route within 24 hours; after that window, use a credit note or correct the GST return as applicable.
Cancel within the permitted window
For the Odoo 17 workflow described in Odoo’s documentation, cancellation requires a Cancel Reason and Cancel Remarks, followed by Request EDI cancellation. The same workflow states that cancelling the e-invoice also cancels the e-way bill. Verify the invoice and related e-way bill status before taking further action.
- Confirm the invoice has an IRN and determine whether it is still within the 24-hour cancellation window.
- In the Odoo cancellation workflow, enter the required Cancel Reason and Cancel Remarks.
- Select Request EDI cancellation and check the resulting EDI status or response.
- Confirm the e-invoice cancellation and, for the documented Odoo 17 workflow, the associated e-way bill cancellation.
Do not treat cancellation as an edit: it does not amend the registered document. If the cancellation window has passed, the stated IRP FAQ route is a credit note or a GSTR-1 correction as applicable. The appropriate accounting or return treatment depends on the transaction and filing context.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do I clear Odoo’s GSTR-1 checks and file?
Resolve the anomalies on the source records, rerun the report checks, and proceed only after the checks reach Reviewed or Supervised. Odoo’s GSTR-1 process can identify tax application problems, missing or invalid invoice data, and return-document issues that need resolution before validation and submission.
Work through each reported anomaly
The checks described for Odoo GSTR-1 include:
- Wrong tax application.
- Credit notes dated in the wrong fiscal year.
- Missing or invalid HSN.
- Invalid UQC.
- Missing document summaries.
- Missing e-invoices.
- Unlinked unregistered credit notes.
Use the report’s anomaly to identify the affected record, then correct that record rather than trying to bypass the check. For invoice-level errors, read the invoice log and fix the source invoice. For a missing e-invoice, check the invoice’s EDI status and configuration; for a document-summary or credit-note issue, correct the related return data.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Validate and push the return
- Resolve the reported anomalies in the invoice, customer or product master data, tax configuration, or return records.
- Rerun Odoo’s GSTR-1 checks.
- Continue only when checks show Reviewed or Supervised.
- Validate the return, then push it to GSTN.
- If the report reaches “Error in Invoice,” open the invoice log, correct the source invoice, and push again.
Odoo’s check status is a readiness signal for the report workflow; it does not remove the need to review the IRP response or confirm an IRN operation’s status.
How can I tell whether the problem is setup, data, or an existing IRN?
Classify the failure before making a change. Configuration issues prevent or misdirect transmission, data issues fail payload validation, and IRN-state issues require checking an operation that may already have succeeded.
| What you see | Likely area | First action |
|---|---|---|
| E-invoice option unavailable, submission not configured, or code 3026 | Odoo journal, NIC credentials, GSTIN eligibility, or portal setup | Confirm localization modules, credentials, the sales journal’s E-Invoice option, and GSTIN portal settings. |
| GSTIN, HSN, UQC, state, tax, or total validation error | Party, product, geography, or tax master data; invoice lines | Use the exact error to locate the field, then reconcile the source invoice and payload. |
| Duplicate or already-generated IRN | Existing registration or repeated request | Check the invoice’s IRN and acknowledgment before attempting another submission. |
| Cancellation or operation not permitted | GSTIN ownership, cancellation status, or elapsed operation window | Verify the logged-in GSTIN, existing IRN state, and whether the 24-hour cancellation period remains open. |
| GSTR-1 “Error in Invoice” | Source invoice or its EDI data | Read the invoice log, correct the invoice, and push the report again. |
Assign the fix to the record or configuration that owns the bad value. A tax mismatch belongs in tax or transaction setup; a wrong customer GSTIN belongs in the customer record; a missing HSN or UQC may require product or line correction; and a duplicate IRN is an operation-state issue, not an invitation to alter invoice data.
Frequently Asked Questions
Does a successful IRN mean the invoice is correct for GSTR-1?
Not necessarily. IRN generation and Odoo’s GSTR-1 report checks are separate parts of the workflow, so review the return’s own anomalies and status before validating and pushing it.
What should I do if Odoo shows no IRN but the IRP says it already exists?
Treat the IRP response as evidence that a prior registration may have completed, then verify the IRN and acknowledgment through the available records before retrying. If Odoo’s record is incomplete, reconcile the existing registration with the ERP rather than creating a second request.
Can I cancel an e-invoice from a different GSTIN login?
No, operations such as cancellation are not permitted from the current user when the IRN belongs to another GSTIN. Use the GSTIN associated with the registration and verify that the user is authorized to act for it.
Does cancelling an Odoo e-invoice automatically cancel its e-way bill?
The documented Odoo 17 cancellation workflow says that cancelling the e-invoice also cancels the e-way bill. Confirm the resulting status in the workflow rather than assuming the cancellation response was successful.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
