Every bank's board deck has a slide on "responsible AI." Almost none of those slides survive contact with an RBI examiner who asks for the fairness test results, the explanation for a specific declined loan, or the sign-off record from the last AI incident review. Responsible AI in Indian financial services is now an examination subject, not a values statement. SEBI's AI/ML disclosure obligations for regulated intermediaries and RBI's FREE-AI framework both convert "responsible" into things a bank has to produce on demand, not describe in a policy document.

What RBI's FREE-AI framework actually asks for

That correction isn't pedantic — it's operationally costly to get wrong, because it tells the examiner where your governance program actually came from. What the report's risk-mitigation recommendations do ask for, in substance, lines up closely with what examiners actually probe in practice:

  • Fairness testing that covers India-specific proxy variables — pincode and surname as caste proxies, name patterns as religion proxies, device and mobile-usage signals standing in for language or disability. A fairness toolkit imported wholesale from a US or EU vendor doesn't test for any of this, because none of it is a protected characteristic there.
  • Decision-level explainability for consequential outcomes, especially credit decisions. A model card is documentation. It is not an explanation of why one specific customer's loan was declined.
  • Human oversight that functions as a real control. A second AI system rubber-stamping the first AI system's decision is not human oversight under any reading of the report's accountability principle, and examiners who have seen this pattern before will say so directly.
  • Adversarial and robustness testing for any AI system exposed to manipulation — for LLM-based customer service and advisory tools, that means prompt injection and jailbreak testing, not the back-testing statistics teams already run for credit scorecards.

What SEBI expects from capital markets participants

What has stayed consistent across SEBI's AI/ML guidance, regardless of which circular you point to, is the substance. Investment advisers and research analysts using AI have to be able to explain a recommendation to a client in plain language. Robo-advisory platforms need a documented human review step before material portfolio changes go out. Brokers using AI in order generation need an audit trail that can answer a market surveillance query inside SEBI's prescribed response window. None of this is new philosophy — it's the suitability and audit-trail obligations SEBI has always applied to a human adviser, extended to whichever system is actually making the call.

Five things that separate a program from a statement

A responsible AI program and a responsible AI statement look identical in a board deck. They diverge the moment an examiner asks for evidence, and five capabilities consistently make the difference between the two.

Test results, not test intentions, come first — a bank that says it tests for bias has said nothing until it produces the actual run, the demographic cuts used, and the date it ran. A working explanation mechanism is second: if nobody in the room can pull up a feature-level explanation for a specific credit decision during the examination meeting, the "explainability framework" slide was theatre. Human oversight with a paper trail is third — who reviewed the AI-generated advice, what qualified them to review it, and what happened on the occasions they disagreed; if that record doesn't exist, the review didn't happen in any sense that survives scrutiny.

Incident records are the fourth, and the one banks resist most. A responsible AI program with zero logged incidents across a material deployment has either not looked for problems or isn't writing them down when it finds them — neither reads well to an examiner who has walked through a hundred of these conversations before. The fifth is a connected audit trail running from board approval through to the individual decision, retrievable as one query rather than assembled from three systems that each hold a fragment of the story.

What to do about it this quarter

  • Pull the actual FREE-AI committee report — not a vendor's summary — and re-map your governance documentation to its Sutras and recommendations instead of an invented acronym structure.
  • Run, and keep on file, one concrete bias test result using India-specific proxy variables, even as a pilot on your highest-volume credit product.
  • Pick one AI-assisted decision type and build a working, on-demand explanation for it before an examiner asks for one.
  • Start an incident log for every production AI system today, backfilling anything your teams already know about from the last quarter.
  • Chain governance records — board approval, validation, monitoring, incidents — so a single query produces the full story for any system, not a scavenger hunt across departments.

Responsible AI that satisfies RBI and SEBI — not just a framework document

Five FREE-AI pillars covered. Tested fairness with India-specific proxies. Decision-level explainability. Connected audit trail for examination.