Odoo in India: GST, E-Invoicing and Implementation

India is one of Odoo's largest markets. That makes sense: there are huge numbers of growing manufacturers, traders and distributors who have outgrown Tally and spreadsheets but don't want SAP-level cost or complexity.

Running Odoo in India works well. But GST, e-invoicing and multi-state operations need to be designed properly from the start. Here's what to plan for.

Start with the Indian localisation

Install the Indian accounting localisation when you create the company. It gives you:

• An Indian chart of accounts
• GST taxes set up as CGST, SGST, IGST and cess where relevant
• Fiscal positions that switch between intra-state and inter-state tax automatically, based on the place of supply
• GSTIN fields on companies and partners
• GST-compliant invoice layouts

Set the state on every company and partner record. If the state is wrong or missing, the tax switch between CGST+SGST and IGST will be wrong too, and you'll find out at GSTR filing time.

HSN and SAC codes

Every product needs the correct HSN code (goods) or SAC code (services). This is tedious to set up and painful to fix later. Do it during data migration, not after go-live.

E-invoicing and e-way bills

Businesses above the government's turnover threshold must generate e-invoices through the Invoice Registration Portal (IRP) to receive an IRN and QR code. Goods moving above the value threshold need an e-way bill.

Odoo provides connectors for both. When planning:

• Confirm which edition and version includes the connector you need
• Register API credentials with the government portal or your GSP
• Test thoroughly in the sandbox, including cancellation within the allowed window
• Decide who handles rejected submissions and how they're noticed

Thresholds and rules change, so confirm the current requirements with your CA.

TDS and TCS

Configure TDS sections as withholding taxes on vendor bills and payments. Map each vendor to the right section. TCS applies in specific sales scenarios. Your CA should review this setup before go-live.

Migrating from Tally

Most of our Indian projects start from Tally. A clean migration usually moves:

• Ledgers mapped to the Odoo chart of accounts
• Customers and suppliers with GSTIN, state and payment terms
• Stock items with HSN codes, units and opening quantities
• Outstanding receivables and payables at cutover
• Opening trial balance

We rarely move years of historical vouchers. Keep Tally available in read-only mode for history and audits. See our ERP data migration guide for the general method.

Multi-state and multi-company setups

If you have GST registrations in several states, each registration usually becomes its own company in Odoo, or at least its own branch with a separate GSTIN. Stock transfers between states are then taxable supplies and need proper invoicing. Get this structure right before go-live. Changing it later is a major job.

Payroll

Indian payroll (PF, ESI, professional tax) is available in Odoo Enterprise for some versions. Many businesses keep a dedicated Indian payroll tool and post summary journals into Odoo. Both approaches work.

Choosing an Odoo partner in India

There are many Odoo firms in India, at very different quality levels. Before signing:

• Ask how they handle GST testing and e-invoice failures
• Speak to a client in your industry
• Ask who owns the custom code
• Check that they'll support the first GST return after go-live

Need help?

We implement Odoo for Indian manufacturers, traders and distributors, remotely and with on-site visits when needed. See our India page or book a consultation.