GST e-invoicing in Odoo
Where the line falls
Worth establishing first, because it determines the shape of the work and most pages on this subject get it wrong.
-
Community gives you
Indian chart of accounts, GST tax structure, fiscal positions, HSN and SAC fields on products, GSTIN on partners — plus IRN generation against the IRP and e-way bill EDI. Enough to invoice correctly and to file e-invoices and e-way bills.
-
Enterprise adds
GSTR-1 push and GSTR-2B fetch with reconciliation against vendor bills — the return-filing layer. Not IRN. Not e-way bill. Those already ship on Community.
That is why “does Odoo support Indian e-invoicing” has one answer for IRNs, and a different one for return filing. The useful answer depends on which layer you actually need.
Both editions
Which edition you run is usually settled long before we are involved. We scope against what you have. For IRN and e-way bill, both editions start from the same native modules.
On Community
The IRN and e-way bill modules are Odoo’s. The work is configuration — wiring your GSP credentials, mapping the document types you actually issue, getting master data to a state the portal accepts, and testing before go-live rather than after. When the portal schema changes, the modules move with the version. What Community does not carry is GSTR return e-filing. If returns have to push from the same system, that gap is the real edition question — or a separate delivery choice — not the absence of IRN.
On Enterprise
You get the Community IRN and e-way bill stack, plus GSTR-1 push and GSTR-2B reconciliation. The work is still configuration: GSP credentials, document mapping, master data, and a first filing cycle that includes returns where those are in scope. When India is already part of an implementation, this layer belongs in that scope from the start.
Both routes end in a signed invoice carrying an IRN, and an e-way bill that clears. What changes is whether return filing rides along, and who owns that layer through the next upgrade.
The work, honestly
-
01
Edition and scope
Confirm what you already run, and whether the requirement stops at IRN and e-way bill or includes GSTR-1 / GSTR-2B. On Community the first two are native; return e-filing is not. Getting that line wrong is the expensive mistake, because it resurfaces at go-live rather than at install.
-
02
GSP account
Filing goes through a GST Suvidha Provider, not directly to the portal. You hold the account and its API charges. We configure against your credentials and do not resell access.
-
03
Integration and mapping
Wiring to your chart of accounts, tax structure and document flows. Domestic B2B is the straightforward case; exports with and without payment of tax, SEZ supply, reverse charge and credit notes each route differently and each needs mapping before go-live.
-
04
Master data
The portal rejects what it does not recognise. Partner GSTINs, HSN and SAC codes, units of measure mapped to the portal’s UQC list, complete state and PIN data. This takes the longest and is underestimated more often than anything else here.
-
05
E-way bill
Generated per invoice or on confirmation, with Part-B vehicle details, validity and cancellation. Transport data has to reach the system before the consignment leaves, which is an operations change more than a configuration one.
-
06
First filing cycle
Generate, submit, receive the signed invoice with its IRN, then run a full cycle before the team is on its own. Cancellation has a fixed window and amendments do not go back through the IRN — your AR team needs both facts before month end rather than during it.
What needs to be true first
- Edition
- Either. IRN and e-way bill are Community-native. Enterprise adds the GSTR return layer. If an edition or version move is the real answer, that is a migration question first.
- Portal registration
- Active, per GSTIN. Separate from GST registration, and separate again for multi-state entities.
- GSP account
- Yours. Odoo files through a Suvidha Provider and the account sits with you.
- Master data
- Partner GSTINs, product HSN/SAC, UQC-mapped units, complete state and PIN data.
- Named owner
- Someone accountable for the cancellation window and the error queue. An operations role, not an IT one.
- Mandate
- If e-invoicing applies to your turnover band, portal registration comes before go-live. Thresholds change by notification — check the current CBIC / e-invoice portal notifications rather than a figure on this page.
Running in production
Cemseal runs Odoo Community across 72 users, with e-invoicing and e-way bill filing to the IRP in production — GSP wiring, master data, document mapping and the operational layer we configured and still carry. Manufacturing, 18,000+ manufacturing orders, 561 vendors, ICICI banking integration on the same install, and the interface running in eight Indian languages.
That is Community IRN and e-way bill, live daily. Where return filing is also required, the edition and delivery choice are scoped separately — not because Community lacks IRN modules.
Need IRNs live, or returns too?
If the requirement is live, tell us your edition, user count and invoice volume — that is most of what determines the shape of the work. If you are scoping an implementation and India is in it, the compliance layer belongs in that scope from the start rather than after go-live.