Odoo Accounting Consultant, India

From Tally groups to a Schedule III friendly chart in Odoo

Indian accountants think in Tally groups: sundry debtors, sundry creditors, duties and taxes, direct and indirect expenses. Odoo thinks in accounts with account types, and its reports group those types into balance sheet and profit and loss lines. The Indian localization provides a chart template to start from, but it does not know your business, and it will not automatically produce the Schedule III layout your auditor uses for statutory statements.

The adaptation I do with your accounts team and CA:

• Account types first: receivable, payable, bank, current asset, fixed asset, current liability and so on assigned correctly, because Odoo's aging, reconciliation and year-end logic depend on them.
• Statutory grouping: accounts arranged so that current and non-current items, trade payables, short-term borrowings and other Schedule III headings can be pulled straight from the trial balance.
• Duties and taxes: separate accounts for CGST, SGST, IGST and cess, input and output, per GSTIN where your structure needs it, plus TDS payable by section and TDS receivable.
• Cost centers: Tally cost centers and cost categories moved into analytic plans rather than turned into extra ledgers.

Your CA should sign off the chart before any data loads. Later account additions then follow the same rules. This sits within the solution design rather than being left to whoever configures the system.

GST return grids, fiscal positions and input credit matching

Configuring CGST, SGST and IGST on invoices is the visible part of GST in Odoo. Making sure each tax feeds the right section of the outward supplies return and the monthly summary return is the less visible part, and it depends on tax grids, the report tags attached to every GST tax that decide where its amounts appear in Odoo's GST reports. Custom taxes added during implementation, such as a special rate or a cess, are where tags are most often missing.

With your CA I review the reporting of:

• Registered and unregistered customers, and inter-state sales to consumers.
• Exports and SEZ supplies, with or without payment of tax, as your CA advises.
• Reverse charge purchases, posting both liability and eligible credit.
• Exempt, nil-rated and non-GST supplies, kept apart.
• Credit and debit notes, and how they adjust each section.

Fiscal positions apply the right outcome automatically, switching between intra-state and inter-state taxes by the customer's state and handling SEZ and export customers.

Input credit needs a routine of its own. Credit you can claim depends on what suppliers have filed. Some Odoo versions can compare your purchase bills with the supplier data available on the GST portal; where yours cannot, a structured monthly export and reconciliation does the job. Mismatches are followed up with suppliers before the return is filed, and a tax lock date protects each filed period.

TDS deducted, TDS suffered and the tax credit statement

Indian businesses deal with TDS in two directions, and mixing them is one of the most common problems I find in existing Odoo setups.

TDS you deduct on payments to vendors, contractors and professionals is a liability. Odoo's Indian localization supports withholding on vendor bills or payments in recent versions; I confirm how your version does it, set up the sections your CA specifies and keep a payable account per section, so monthly deposits and quarterly returns reconcile.

TDS your customers deduct from what they pay you is an asset, a credit you will claim. When a customer pays short because of TDS, the receipt should clear the invoice in full, with the deducted amount posted to TDS receivable rather than left as an open balance. A reconciliation model can do this when the deduction follows a predictable pattern. The receivable is then matched each quarter against the tax credit statement on the income tax portal, and missing credits are chased with the customer.

TCS, where it applies to your business, needs the same care on the collection side. Thresholds, rates and sections change, so your accounts team maintains them with your CA, and the configuration makes sure each deduction lands in the right account with the right reference. The finance automation page describes how these routines reduce month-end work.

UPI, payment gateways and Indian bank reconciliation

Bank synchronization coverage for Indian banks is limited, so most Indian teams import statements in Excel or CSV. That is fine if imports are routine and reconciliation models handle the volume. The patterns I set up most often:

1. UPI receipts: many small payments with references that do not always include the invoice number, matched by amount and customer where possible, with the rest in a short exceptions list.
2. Payment gateway settlements: a single credit covering many orders, net of gateway fees and GST on those fees. The model splits the settlement into customer receipts, fee expense and input GST.
3. NEFT and RTGS: customer and vendor payments matched to open invoices and bills by reference.
4. Bounced checks: the receipt reversed, the customer balance reopened and the bank's return charge booked, all in one defined step.

Several bank accounts across branches each get their own journal. Cash deposited at branches is matched to the right point of sale session or cash journal.

Vendor payment files for bulk transfers depend on your bank's format and on what your Odoo version can produce, so I test the full vendor payment flow before go-live. The result I aim for is a daily bank book that closes, the standard Indian accounts teams already hold themselves to in Tally.

Multi-entity groups, analytics and the edition question

Indian groups often combine a private limited company, an LLP and sometimes a proprietorship run by the promoter, plus several GSTINs within the main company. Each legal entity becomes its own Odoo company. Within a company, recent Odoo versions support branches that share the legal entity but carry their own GSTIN and document sequences; check whether your version has this before designing around it.

When one group entity bills another, Odoo's intercompany rules can raise the mirror vendor bill automatically; expect that to need Enterprise. Loans and advances between group entities and with directors need their own accounts, because your auditor will look at them specifically.

Analytic plans give management views that Tally cost centers only partly delivered: profit by plant, product line, project or sales channel, with distribution models spreading shared overheads. Manufacturers often combine a plant plan with a product line plan on the same line.

The edition decision affects Indian accounting directly. In most versions, the full Accounting app, GST reports, e-invoice and e-way bill integrations, reconciliation tools and intercompany rules belong to Enterprise, while Community gives you invoicing. Running Indian compliance on community modules is possible but shifts maintenance to you or your implementer. Check the current edition list before committing. The multi-company ERP page explains entity design further.

Carrying Tally balances across, and the limits of Odoo Accounting

Beyond cleaning masters, the opening position from Tally needs specific attention:

• Group-wise trial balance mapped to the new chart and agreed with your CA.
• Bill-wise receivables and payables loaded as individual open documents, not net balances.
• Advances received or paid, with GST already discharged on them.
• GST input credit carried in the books agreed to what the portal shows.
• TDS payable for the open period and TDS receivable not yet matched.
• Fixed asset register brought in asset by asset, with gross block and depreciation to date.

The cleanest cutover is the start of the financial year; otherwise straight after a monthly return is filed. ERP data migration describes the reconciliation and sign-off.

Odoo Accounting handles book depreciation, but depreciation under income tax rules is usually computed by your CA outside the system, as are tax audit annexures. Payroll with PF, ESI and professional tax often sits in a dedicated product. If accounting is the only requirement, disciplined Tally may be enough. For cost-sensitive groups I also compare ERPNext in India and, for finance-led needs, Business Central in India. E-invoice, e-way bill and implementer topics live on Odoo in India. The global Odoo Accounting page has product-level detail, while ERP consultant India and the India hub describe how I support Indian businesses more broadly.