Start with the fact pattern, because it's more revealing than any policy paper. A Lloyd's India-regulated insurance entity received a TPO show-cause notice giving it three days to produce documentary support for its transfer pricing position. It didn't manage it in time - not because the evidence didn't exist, but because its compliance bandwidth had gone into IRDAI regulatory requirements rather than TP file-building. By the time of the appeal, the taxpayer had assembled contemporaneous emails, contracts and invoices that plausibly supported its position. The ITAT Mumbai admitted this evidence under Rule 29 and sent the matter back for fresh adjudication. On the surface this is a routine remand order. Read against the backdrop of where Indian tax administration is heading, it's a warning shot.
What's changed is the operating environment around these notices. CBDT has been public about using AI-driven risk analytics - NUDGE, Project Insight, INTRAC - to flag taxpayers and compress the distance between detection and action; the department has described the next phase of AI deployment as 'more intense.' Separately, the Income-tax Act, 2025 and the Income-tax Rules, 2026 were framed explicitly as ushering in an algorithm-based, technology-driven assessment ecosystem, with the CBDT Chairman describing simplified statutory language as something that will 'enable algorithm-based implementation.' None of this is inherently bad - faster detection and cleaner drafting are good things. But faster detection paired with unchanged (or shortened) response windows means the gap between 'flagged by the algorithm' and 'must produce five years of DEMPE-level documentation' keeps narrowing, while the underlying task - assembling functional, contractual and economic evidence for related-party transactions - hasn't gotten any easier or faster to do properly.
Here is the piece a generic Taxmann write-up on this ruling will miss: India has, in parallel, been building an entire vocabulary for governing AI systems responsibly. The Finance Ministry has laid out how RBI's FREE-AI framework and MeitY's India AI Governance Guidelines are meant to apply to financial-sector AI, organised around principles like 'Accountability,' 'Understandable by Design,' and 'Trust is the Foundation.' These are aimed at banks and NBFCs deploying AI in lending and risk models. But the tax department's own algorithmic risk-scoring - the system that generates the show-cause notices and compressed timelines that produced this ITAT remand - sits outside that governance conversation entirely. Nobody is asking whether NUDGE or INTRAC's flagging logic is 'understandable by design' to the taxpayer who receives a three-day notice, or who is 'accountable' when an automated flag compresses due process past the point where a genuine, good-faith taxpayer can respond. The state has written AI governance principles for everyone except itself.
The CBDT's own APA numbers hint at how sophisticated taxpayers are already responding to this asymmetry: a record 220 APAs signed in FY2025-26, cumulative signings past 1,035, and a Finance Act 2026 that consolidated safe harbour categories and streamlined APA administration. APAs and safe harbours are, in effect, taxpayers pre-negotiating their way out of exactly the compressed, algorithm-driven scrutiny process that produced the insurance company's evidence crunch. That's a rational choice if you can afford the APA application fee and multi-year process. It's not a choice available to a mid-sized captive or a regulated entity whose compliance bandwidth is already stretched across sectoral requirements, as this case shows. The open question for practitioners to sit with: as India's tax administration becomes more algorithmic, should the same accountability and explainability standards the government is asking of private-sector AI deployers - logged reasoning, contestability, human-in-the-loop review before adverse action - apply symmetrically to the department's own risk-scoring systems, especially once (not if) that scoring logic extends into TP-specific audit selection and comparable-set flagging? Right now, that symmetry doesn't exist, and the insurance company's three-day notice is what the gap looks like in practice.
