A whole ERP, or the whole India-books job?

Odoo Community is free to licence, but it ships the Invoicing app only: no Balance Sheet, no P&L, no Trial Balance, no GSTR module and no bank sync. Those live in the paid plans (₹725–1,350 per user per month in India, billed yearly; first-year offers from ₹580), on top of a ₹5–25 lakh implementation and a partner. Finocket's free tier includes the statements and the GST/TDS returns.

Only partly, and only on Enterprise. The GSTR-1/3B report module is Enterprise-only, and there is no GSTR-9, GSTR-4/CMP-08, GSTR-8 or 2B IMS anywhere in Odoo. TDS/TCS is a banner that suggests a section, with no 26Q/27Q/27EQ returns, no challan register and no Form 16A. Finocket exports GSTR-1 and GSTR-3B files you or your CA upload, builds a GSTR-9 annual summary to check against the portal, reconciles GSTR-2B with IMS actions and has working files for the composition returns CMP-08 and GSTR-4. It does not prepare GSTR-8: it compares your invoices with marketplace settlements and does not check the TCS a marketplace reported.

When you genuinely need a website, webshop, barcode warehouse, shop-floor terminals or an HR suite in one system, and can fund the implementation and the yearly upgrade. That's a real fit for some businesses, just not the phone-first Indian SMB whose priority is filing every return correctly.

There is exactly one write path. Every action the assistant can take (eighteen of them, from recording a payment to installing an outreach sequence) is validated and then executed through the same code the manual screens use, so the AI path inherits the same permissions, the same validation and the same ledger projection, and no more; it adds no posting logic of its own. In front of that path sit two controls you own: a confirm card showing the money moving before and after, per bucket, in rupees (a classification of the action's impact, not a dry run of the exact voucher), and an autonomy dial that caps a single action by rupee value and by how many people it can reach. No setting removes the human confirm. Behind it sits an append-only audit table with no UPDATE and no DELETE policy, where each row carries a SHA-256 hash of the row before it, computed by a database trigger rather than by the app, with a function that recomputes the chain and returns the first row that doesn't match. That table is separate from the Rule 11g edit log on the books, which is a broader, older log covering ordinary record changes. Three honest limits: the hash chain makes tampering detectable but is not notarised by a third party; there is no in-app verify button today; and free text the assistant drafts for you to review is not covered by the grounding guard that governs what it tells you.