No sector carries more AI-specific regulatory surface area than BFSI, and the honest reason most institutions struggle isn't a lack of rules — it's that model validation and data privacy have historically lived in separate departments, run by separate teams, with separate evidence trails. An examiner who asks "show me your AI risk framework" is really asking whether those two things, plus fairness, security, and board reporting, connect into one program. Most banks' honest answer is still "no," and that gap, not any single missing policy, is what shows up in the finding letter.

The regulatory stack is real, but a few of its headline labels aren't

RBI's binding instruments for AI-adjacent governance are its existing IT governance, cyber-resilience, and outsourcing master directions, plus the non-binding but increasingly examined FREE-AI committee report released in August 2025. DPDP Act 2023 is real and binding — consent or legitimate-use basis for processing, purpose limitation, data minimization, and Data Protection Board enforcement up to ₹250 crore per instance of non-compliance — but it does not create an automated-decision human-review right the way EU law does. SEBI's AI/ML disclosure circular for registered intermediaries and IRDAI's underwriting and claims governance expectations are both real and worth building for; MAS's technology risk guidance for Singapore operations exists, though this review can't confirm a distinct 2024 AI-specific revision — verify the current version number before citing a date.

Decision stakes attach to a person, not a population — and that changes what you have to document

A bad decision from a population-level model shows up in an aggregate metric; a bad decision from a BFSI AI system shows up as one specific customer's denied loan or approved fraudulent claim, today. That's why EU AI Act Article 86, RBI's FREE-AI explainability expectations, and the DPDP Act's access rights all converge on the same operational requirement: an individual decision has to be explainable to the individual it affected, not just summarized in an aggregate accuracy number. Generic AI governance tools built for enterprise IT risk track model performance in the aggregate; BFSI governance has to track individual-decision evidence, retrievable on demand, because that's the level at which the obligation actually bites.

India fairness testing is the one capability competitors genuinely don't have

Caste proxies live in pincode and surname patterns; religion proxies live in counterparty names and geographic concentration; language-group proxies live in mobile network and social platform usage; disability proxies live in device-usage patterns and transaction timing. None of IBM's Fairness 360, Google's What-If Tool, or any Western fairness suite was built to test for these, because none of them were built for India's social structure. An Indian BFSI institution that has run standard demographic fairness testing and stopped there has not met the bar RBI's FREE-AI report actually sets — it's met a different, easier bar that happens to look similar on a slide.

Agentic AI needs a governance layer SR 11-7 genuinely doesn't have

A lending agent that queries a credit bureau and executes a disbursement isn't a model producing a prediction for a human to review — it's a system taking an action, some of them irreversible. SR 11-7 validates what a model predicts, not what an agent does, so the authorization-scope question — what can this agent do, who approved that scope, what happens if a prompt injection pushes it past the boundary mid-task — sits entirely outside the traditional MRM framework. Closing this gap means a written tool-authorization manifest, a human checkpoint above a defined threshold for irreversible financial actions, and an action-level audit trail distinct from the model-output log most banks already have.

Seven components, and which institution type needs which

An Indian scheduled commercial bank, an NBFC, an insurer, and a stockbroker or AMC don't need identical governance programs — a stockbroker without lending operations has limited exposure to India fairness testing but full exposure to SEBI's algorithmic-trading audit trail requirements, while an insurer's fairness obligation centers on underwriting and claims AI rather than credit scoring. Map each of the seven components — inventory and tiering, audit trail, fairness testing, explainability, security, monitoring, and board governance — against your specific regulator set before building, rather than building a generic program and discovering the gaps at examination time.

Action checklist for a BFSI AI governance build

  1. Re-verify every internal document that cites an "RBI 2024 AI Circular" or a "FREE-AI five pillars" structure against RBI's actual published instruments and the FREE-AI report text.
  2. Build India-specific proxy-variable fairness testing (caste, religion, language, disability) for every credit, underwriting, and fraud model — this is the longest-lead-time item, start it first.
  3. Write the agentic AI authorization manifest and human-checkpoint thresholds before any lending, claims, or trading agent goes into production.
  4. Build individual-decision-level explainability and audit trail capability, not just aggregate model performance dashboards.
  5. Map the seven governance components against your specific regulator combination (RBI/SEBI/IRDAI/MAS) rather than assuming a single generic program covers all of them equally.

BFSI AI governance — purpose-built, not adapted

India fairness testing, RBI FREE-AI alignment, eMRM-ready model governance, DPDP Act evidence trails. One program satisfying all seven governance components across RBI, SEBI, IRDAI, and DPDP Act.