AI for chartered accountants in India: a guide

Most of the hours in a small or mid-sized CA practice go into work that is necessary, repetitive and checkable: turning bank statements and invoices into entries, matching records against each other, preparing returns and drafting replies. That is exactly where current AI is useful, because the output can be reviewed before it matters.

In each case the AI does the first pass and the CA does the part that needs professional judgement. The gain shows up as fewer hours on preparation and more on review and advice, which is also the more valuable work.

Know the weak spots too. Language models can state a section number, a due date or a rate with confidence and be wrong, especially after a recent notification. They struggle with poor scans and handwritten bills, and they cannot know what the client did not tell you. Treat any statement of law in an AI draft as unverified until you have checked it against the current notification, and keep a person on anything that depends on facts outside the documents.

Three things cannot be handed to a tool.

• Judgement. Whether a receipt is income or an advance, whether a credit is eligible, whether a provision is needed: these are professional calls, and an AI suggestion is an input to them, not a substitute.
• Sign-off. Audit reports, certificates and filings carry the CA's name and membership number. The responsibility does not move because a model drafted the working. The Standards on Auditing, including those on audit evidence and documentation, still govern any audit work AI assists.
• Confidentiality. The ICAI Code of Ethics requires members to protect client information. Pasting a client's ledger into a consumer chatbot that may retain or train on it is hard to reconcile with that duty.

The practical test is simple. For any AI-assisted output, could you explain to the client, the department or a peer reviewer what you checked and why you accepted it? If not, the review was not real.

Drafting outside the books is one thing; an agent that changes the books is another. When an agent can post entries in a client's accounting system, use a three-part pattern.

1. Propose. The agent drafts the change, a journal, an invoice, a reconciliation adjustment, as a draft or staged entry, not a posted one.
2. Approve. Rules decide what can post on its own, such as routine entries within limits, and what waits for the CA, such as entries above a value, entries to closed periods, or anything touching tax ledgers.
3. Record. Every proposal, approval and refusal is recorded with the rule that applied, linked to the entry number in the books.

This pattern also answers the question clients ask most: “who is responsible if the AI gets it wrong?” The client remains responsible for its books, and the CA for the work they sign; the record shows exactly which entries the CA approved and which posted within agreed limits. For an example, see a small firm's journal entry, read by its CA, an illustrative specimen.

For corporate clients, every entry, including one an agent posts, must sit in accounting software whose edit log records each change and its date and cannot be disabled, under the proviso to Rule 3(1) of the Companies (Accounts) Rules, 2014. As statutory auditor, you report on it under Rule 11(g).

Two consequences for AI. Give each agent its own user in the client's software, so the edit log attributes its changes to the agent rather than to you or to the client's accountant. And when you audit a client that uses agents, test the controls around them as well as the log: who can change the agent's permissions, what it may post without approval, and whether its changes reconcile to its records. The ICAI implementation guide on Rule 11(g) sets the reporting framework, and our guide to the MCA audit trail covers the detail.

For clients you only advise, the same points are good practice: ask to see the agent's permissions, the limits on what it can post alone and a month of its records before you rely on books it has touched. A short written note of what you checked protects both the client and the firm.

GST work suits AI well because so much of it is matching. Input tax credit depends on the supplier's invoices appearing in the recipient's GSTR-2B, under section 16(2)(aa) of the CGST Act, so a monthly match of the purchase register against GSTR-2B, with mismatches listed by supplier, is valuable and easy to check. The Invoice Management System on the GST portal, where recipients act on supplier invoices, makes timely matching more important still.

E-invoicing adds deadlines. Clients whose aggregate turnover has exceeded ₹5 crore in any year since 2017-18 must issue e-invoices for B2B supplies, and since 1 April 2025 those with turnover of ₹10 crore or more cannot report an invoice to the IRP more than 30 days after its date, under the GSTN advisory. An agent that watches for invoices approaching the limit prevents a lost invoice from becoming a lost credit for the customer.

Returns themselves should stay with review. Let AI prepare GSTR-1 and GSTR-3B drafts and the list of exceptions; let the CA decide what to file.

Client books contain personal data: names, PANs, bank details and salaries. Under the Digital Personal Data Protection Act, 2023, whoever decides why and how that data is processed is a Data Fiduciary, with duties of purpose limitation, security and breach notification; a firm processing data on a client's instructions acts for it. The DPDP Rules, 2025 bring most of those duties into force from 13 May 2027.

Before you use any AI tool on client data, ask four questions: where is the data stored and processed, is it kept in India, is it used to train anyone's model, and what does the contract say about deletion and breaches? Put the answers in your engagement letters, along with what the client must tell you, such as which systems hold its books and who may approve changes, and what you will do if a tool is found to have mishandled data. Our page on the DPDP Act and AI agents shows how one vendor answers them.

Suppose an engagement used to take 20 hours and now takes 8: billing 20 is not sustainable once clients notice, and they will, while billing 8 at the old rate gives away the investment you made. Most firms that handle this well move routine compliance to fixed monthly fees, priced on the value and the risk carried rather than the hours, and say plainly that AI does the preparation and a CA does the review.

Be specific about what the fee buys: the scope of review, the response time, who signs. The review is the product. Clients pay a CA for judgement and accountability, and AI makes it possible to spend more of the fee on exactly that.

Many clients who want agents in their books will need a system with an API, user roles and approval workflows, and for many small businesses that means moving from Tally to an ERP such as ERPNext. The CA's role in that move is central: agreeing the mapping, reviewing the reconciliation and signing off the opening position. Plan the move for a quiet month, ideally the start of a financial year, and keep the old data readable for the full retention period. Our step-by-step guide to Tally to ERPNext migration sets out the process and the evidence to keep.

Start with the guidance that already governs practice. The Code of Ethics governs confidentiality, professional competence and due care. The Standards on Auditing govern evidence and documentation in any audit AI assists. The implementation guide on Rule 11(g) governs audit trail reporting. ICAI's boards and committees publish technology guidance and training; check the ICAI website for the current material rather than relying on summaries.

Document your own policy too: which tools the firm uses, for what, with which client data, and how outputs are reviewed. A peer reviewer will ask.

1. Days 1–10: choose one workflow and three clients. Bank reconciliation or GSTR-2B matching are good first choices: high volume, easy to check. Pick clients whose books are already in reasonable order.
2. Days 11–20: write the firm's AI policy. Which tools, for which work, with which client data, where the data is stored, and how output is reviewed and recorded. Add a clause to engagement letters.
3. Days 21–40: run it alongside the old way. Do the work both ways for one cycle and compare. Note what the AI got wrong and how long review took.
4. Days 41–50: set the limits. Decide what can post without the CA, if anything, and what always waits. Write the limits as rules, per client.
5. Days 51–60: review and extend. Show the results to the partners, adjust the policy, and add the next workflow or the next set of clients.

Keep the comparison data from the parallel run. It is the evidence for your pricing conversation with clients and for your own peer review.

“elan1 Work for small firms, through your CA” is built around this pattern. An AI agent drafts and applies changes in a client's ERPNext books; each change passes a rule check, waits for the CA where the rules ask, and leaves a proof record the CA can read. CA seats are free for every client site, always, and the multi-client console is included. See AI for chartered accountants: governed client books.

The compliance filing pack, ₹1,999 per month exclusive of GST, prepares GSTR-1 and GSTR-3B, runs the GSTR-2B reconciliation and monitors e-invoices, all for review. Data stays in India, in AWS Mumbai.