AI in Tax Assessment 2026: How the Income Tax Department Uses Data Analytics and AI
CA Gagan Gupta
Founder & Principal, Kishnani & Associates
CA Gagan Gupta is a seasoned Chartered Accountant with extensive expertise in taxation, audit, financial consulting, and business advisory. A fellow member of the ICAI since 2021, he has been practicing since 2016, providing strategic financial solutions to businesses, startups, and individuals. Under his leadership, Kishnani & Associates delivers precise and ethical financial services, ensuring seamless regulatory compliance and sustainable growth for clients.
AI in Tax Assessment: How the Department Is Actually Using It in 2026
Â
When AI in tax assessment gets discussed in industry circles, the conversation still often oscillates between two extremes — either “the algorithm decides everything” or “it is all just marketing.” Neither is accurate. The truth, from what I have observed across client assessments in the Delhi zone through 2025 and into 2026, is that AI is now genuinely embedded in specific parts of the department’s workflow. It does not pass assessment orders. It does, however, decide which cases you enter and what questions you get asked. Understanding where the algorithm sits changes how a CA prepares documentation and drafts responses.
Where AI is actually being used
Â
The department’s technology stack now touches at least six operational functions:
- Case selection for scrutiny — INSIGHT (formerly Project Insight) risk-scores taxpayers using data from ITR filings, AIS, GST returns, TDS returns, MCA filings, property registration, foreign remittance reports, and transaction reports. Cases with anomalous risk scores are pushed into the scrutiny pipeline. Human officers still make the final selection call, but the algorithm sets the shortlist.
- Automated notice generation — Section 143(1) intimations and Section 245 refund adjustments are now generated substantially without human intervention. The processing engine reconciles ITR data with 26AS, TDS records, and AIS, and issues intimations for mismatches automatically.
- AIS and TIS compilation — the Annual Information Statement and Taxpayer Information Summary aggregate data from multiple sources. The compilation engine flags outliers — high-value transactions, cash deposits above threshold, property purchases, foreign remittances — for both the taxpayer and the department’s risk system.
- Faceless assessment case allocation — the National Faceless Assessment Centre uses algorithmic allocation of cases to Assessment Units, Verification Units, and Review Units across the country. The allocation is deliberately opaque to reduce influence.
- High-risk transaction detection — specific transaction categories (large cash deposits, benami property indicators, cryptocurrency movements, high-value foreign remittances) trigger algorithmic flags that surface to human officers.
- GST-IT reconciliation — GSTN data is now systematically cross-checked against IT return data. Businesses whose GST turnover materially exceeds their IT turnover receive automated queries.
What this means for taxpayer documentation
Â
The practical consequences for how a taxpayer or CA prepares and defends returns:
- Reconciliation is no longer a courtesy exercise. The department has automated reconciliation on its side; the taxpayer needs matching internal reconciliation.
- AIS review before filing is now a mandatory discipline. Filing a return without opening AIS first invites automated adjustments in the intimation.
- Outlier transactions need documented reasons proactively. If a cash deposit or property purchase is unusual against your return profile, prepare the explanation in the file — it will almost certainly be asked.
- Response drafting must address the specific algorithmic flag. Generic replies to automated notices produce escalation to human scrutiny.
- Timing matters. AIS is updated throughout the year; catching mismatches in October rather than in March gives materially more time to correct.
What AI is NOT doing — and where the boundary matters
Â
It is equally important to understand the limits of the algorithm’s reach in 2026:
- AI does not pass assessment orders. A human officer at the National Faceless Assessment Centre or the jurisdictional office still writes and signs every order.
- AI does not adjudicate on legal questions. Where the response involves an interpretive dispute (a claim under a particular deduction, a valuation position), the algorithm hands the matter to a human officer for reasoned adjudication.
- AI is not making prosecution decisions. Section 279 sanction requires human evaluation.
- AI does not have access to privileged CA-client correspondence. Documents shared only with your CA and not filed with the department remain outside the algorithm’s view.
Recent trends I have observed in Delhi zone assessments
Â
- Sharper AIS-based reconciliation questions in first-round faceless notices — the algorithm now flags specific line items, not general mismatches.
- Higher rate of automated Section 245 adjustments where refunds are being adjusted against outstanding demand — even old demands that were long dormant.
- Faster issue of reassessment (Section 280) notices where AIS has flagged material transactions not reported in the return.
- More consistent GST-IT cross-checks — mismatches that would previously have been ignored are now producing routine automated queries.
What CAs should do differently in 2026
Â
- Run monthly AIS reviews for clients above a materiality threshold. Do not wait for year-end.
- Build a reconciliation checklist across 26AS, AIS, TDS, GST, and books before filing. Not after.
- Document reasons for outlier transactions in the file — cash deposits above ₹2 lakh, property transactions above ₹30 lakh, foreign remittances above ₹7 lakh under LRS.
- When responding to automated notices, address the specific algorithmic flag with supporting documents attached — not just legal argument.
- For high-net-worth clients, prepare an annual “AIS audit” — a preventive review of what the department already knows about the client.
Closing action list
Â
- Treat AIS as a real-time compliance document, not a year-end reference.
- Build reconciliation discipline into your monthly close, not just filing time.
- Document outliers proactively — the algorithm will find them anyway.
- Draft notice responses to the specific flag, not to a template.
- Track your firm’s notice pattern — algorithmic triggers show emerging risk categories before they become widespread.
AI in Indian tax assessment in 2026 is not a threat to good practitioners. It is a shift in what “good” looks like. Practitioners who build reconciliation discipline and proactive documentation into their workflow find the department’s automated infrastructure actually reduces friction — cleaner returns produce fewer notices. Practitioners who treat AIS and reconciliation as optional face a much noisier assessment cycle than they did five years ago.
Disclaimer
The material presented on this blog is intended solely for informational purposes. The opinions expressed here are solely those of the respective authors and do not necessarily reflect the views of Fintrac Advisors. No warranties are made regarding the completeness, reliability, or accuracy of this information. Any actions taken based on the information presented in this blog are solely at the reader’s risk, and we will not be liable for any losses or damages resulting from its use. Seeking professional expertise for such matters is strongly recommended. External links on this blog may direct users to third-party sites beyond our control. We do not take responsibility for their nature, content, or availability.
For any clarifications or queries, please feel free to reach out to us at: admin@fintracadvisors.com

