Intellectual
← All Insights
AI & Enterprise AI7 October 20257 min read

Banking AI Compliance in 2025 — What Regulators Are Expecting

Banking regulators have published more specific AI expectations through 2024 and 2025. The institutions that engage with the expectations early have an easier 2026 ahead.

Banking regulators have moved from generic AI guidance to specific expectations through 2024 and 2025. The Federal Reserve, OCC, FCA, ECB, MAS, RBI, and others have published more detailed frameworks. Sector-specific expectations are crystallising. The institutions engaging with these expectations early — building the capability, the documentation, the audit posture — have an easier 2026 and 2027 ahead.

This piece is a practitioner view of what banking AI regulation looks like in late 2025, what regulators are asking for, and how institutions are organising to meet the expectations.

What the regulators are signalling

A consistent set of themes across jurisdictions:

Existing frameworks apply

AI doesn't get a separate framework; the existing model risk management (SR 11-7 in the US, similar elsewhere) applies. AI/ML models are models. The conventional discipline of model validation, monitoring, and governance applies.

Documentation and explainability

For AI/ML used in consequential decisions, the institution must be able to explain how the model works to regulators, to affected customers, and to internal stakeholders. Black-box models in consequential roles are a problem.

Bias and fairness testing

For models that affect customer outcomes (credit, pricing, fraud), explicit testing for disparate impact across protected populations. The testing methodology has to be defensible.

Performance monitoring

Models in production must be monitored. Drift, degradation, anomalies must be detected and acted upon. Periodic re-validation must happen.

Vendor governance

For vendor-provided AI capabilities, the institution remains accountable. Vendor management has to demonstrate validation of vendor claims.

Cyber and operational resilience

AI systems are critical infrastructure for some workloads. The same operational resilience requirements apply.

Customer transparency

For AI-affected customer decisions, the customer's right to explanation and challenge. Communications must be clear about when AI is involved.

What institutions are building

In response, institutions are building capability:

Centralised model inventory

Every AI/ML model in the institution registered. Each entry: description, owner, risk classification, dependencies, validation status. The inventory is the foundation for everything else.

Tiered model risk management

Models classified by risk tier. Higher-tier models get more validation, more frequent monitoring, more stringent governance. Lower-tier models get lighter treatment.

Model validation function

A function — often inside risk management — that independently validates models before deployment and periodically thereafter. The validators are independent of the developers.

AI risk committee

A cross-functional committee — risk, compliance, technology, business — that reviews AI initiatives, approves new deployments, oversees portfolio risk.

Bias and fairness testing infrastructure

Tools and methodologies for testing models against protected populations. Periodic execution; documented results; remediation when issues found.

Performance monitoring infrastructure

Continuous monitoring of in-production model performance. Drift detection, degradation alerts, periodic re-validation triggers.

Vendor governance enhancement

Enhanced vendor management for AI vendors. Contractual provisions for audit access, model version control, training data, validation evidence.

Customer communication framework

Standardised communications for AI-affected customer decisions. Right to explanation procedures, escalation paths, dispute handling.

Audit and evidence infrastructure

Detailed logging of AI decisions, retention per regulatory requirements, accessible for regulator examinations and customer inquiries.

The specifics by use case

The expectations vary by what the AI is used for:

Credit decisions

The most heavily scrutinised. Strong documentation, validation, bias testing, customer explanation, appeals process. Fair lending requirements apply directly.

Fraud detection

High volume; low-stakes per case but high in aggregate. Strong monitoring; bias testing; investigation procedures.

AML / sanctions screening

Regulated specifically. AI assistance is becoming common; the regulatory comfort is rising. Audit trails are dense.

Customer service AI

Less heavily regulated; expectations focus on appropriate disclosure, escalation paths, complaint handling.

Internal employee productivity AI

Lowest scrutiny; standard cyber and data protection apply.

Trading and quantitative use

Regulated under separate trading frameworks. Model risk management applies; specific market risk frameworks apply.

Generative AI in customer interactions

Emerging regulatory attention. Disclosure requirements, accuracy standards, complaint handling.

What's hard

Genuine challenges:

Model validation for generative AI

The conventional model validation framework was designed for predictive models with measurable accuracy. Generative AI requires different methodology. The discipline is still developing.

Bias testing for generative AI

What does fairness look like for a generative model? The question is methodologically harder than for predictive models.

Multi-model systems

When an AI workload involves several models, what gets validated? The components, the integrated system, or both? The answer is evolving.

Vendor models

Validating vendor models requires vendor cooperation that may not be forthcoming. Negotiating audit access is a procurement art.

Cross-jurisdictional consistency

Different jurisdictions have different expectations. Multinational institutions need to satisfy several frameworks simultaneously.

Pace of capability evolution

The regulatory framework lags the technology. Institutions need to anticipate where regulation is heading, not just where it currently is.

What we keep seeing

Patterns in banking AI compliance engagements:

The capability investment is significant. Model inventory, validation function, monitoring infrastructure, governance — all real investments. The mature institutions have been building for several years.

Regulator interactions are intensifying. AI questions are now part of standard examinations. Institutions need to be ready to answer.

Vendor governance gaps are the most common finding. Vendor models without adequate validation evidence are appearing in examinations.

Generative AI in customer interactions is the new frontier. Regulators are paying attention; expectations are forming.

The capability differentiator is the platform. Institutions with strong AI platforms — model inventory, validation tooling, monitoring infrastructure — handle the regulatory expectations more cleanly than institutions building each capability per-system.

What we recommend

For banking institutions in 2025:

  1. Build the model inventory if you haven't. Without it, nothing else works.
  2. Apply existing model risk management to AI/ML. Don't create a parallel framework.
  3. Build the validation function with appropriate independence. Self-validation by developers isn't credible.
  4. Invest in monitoring infrastructure. Drift and degradation must be visible.
  5. Negotiate vendor governance at procurement. Retrofit is expensive.
  6. Track regulator publications and engagement. The expectations are evolving; staying current matters.
  7. Plan for generative AI in customer interactions specifically. The regulatory framework is forming; engage early.

Banking AI compliance in 2025 is a serious enterprise discipline. The institutions that have built capability operate confidently in regulator interactions. The institutions that are still building should plan for the next 12-24 months as construction time. The expectations will continue to specify; staying ahead requires sustained investment, not occasional sprints.

RELATED READING

More from the field.

Service practices the article draws on, related programmes, and other pieces on adjacent topics.

Discuss this work

Bring an enterprise programme.

If anything in this piece resonates with what you're building, talk to us. Senior practitioners engage directly on architecture and delivery.

Work with the practitioners

Bring an enterprise programme.

Architecture audit, new delivery, modernisation, or in-flight rescue — Intellectual engages directly on enterprise programmes with senior practitioners.