Americas · Canada

OSFI E-23

Guideline E-23: Model Risk Management (2027)

Canada's federal financial regulator's principles for managing the risk of every model a bank or insurer uses, written with AI and machine learning explicitly in mind, effective 1 May 2027.

SupervisoryRegulatory GuidanceDevelopers and deployersNot an AI-specific law
Regulator
Office of the Superintendent of Financial Institutions (OSFI)
Adopted
11 Sep 2025
In force
1 May 2027
Sectors
Financial services
Penalties
None stated in the guideline. OSFI guidelines set supervisory expectations; OSFI assesses compliance through its normal supervisory work.
Last verified
19 Oct 2026Official source

Summary

  • OSFI published the final Guideline E-23 on 11 September 2025; it takes effect on 1 May 2027 after an 18-month transition.
  • It is principles-based and risk-based: the effort a firm spends on a model should match the model's risk rating.
  • It is organised around 3 outcomes and 12 numbered principles: (1) model risk is understood and managed across the enterprise, (2) model risk is managed with a risk-based approach, (3) governance covers the whole model lifecycle.
  • Its model definition names AI/ML methods directly and points to the OECD definition of an AI system. AI-specific expectations appear throughout: explainability, bias, black-box and autonomous models, self-learning drift and third-party libraries.
  • It widens the 2017 E-23 (which covered only deposit-taking institutions) to all federally regulated financial institutions, including insurers and foreign branches; pension plans were dropped from the final version.
  • Status (as of 2026-10-19): final but not yet in effect.

Who it applies to

  • All federally regulated financial institutions (FRFIs): banks, foreign bank branches, life insurance and fraternal companies, property and casualty companies, and trust and loan companies. Foreign bank and foreign insurance branches are covered to the extent consistent with Guideline E-4.
  • Application is proportional to size, strategy, risk profile, nature and complexity of operations, and interconnectedness (A.3).
  • All models are in scope, but only models with non-negligible inherent risk must go in the inventory and through full lifecycle governance.
  • Not in scope: federally regulated pension plans (removed after consultation).
  • Vendor and third-party models are covered through the institution's own duties and Guideline B-10 (Third-Party Risk Management).
  • Not extraterritorial. Non-Canadian companies are reached only as vendors or parent groups of Canadian FRFIs.

Key dates

  1. Draft revised Guideline E-23 published for consultation
  2. Consultation closes
  3. Final Guideline E-23 (2027) published with a cover letter and backgrounder
  4. Guideline takes effect for all federally regulated financial institutionsUpcoming
Full date record
Date Event
2017 Earlier Guideline E-23, Enterprise-Wide Model Risk Management for Deposit-Taking Institutions (the 2025 letter describes the new text as a revision of it but does not say explicitly when it is superseded)
2023-11-20 Draft revised E-23 released for consultation
2024-03-22 Consultation closes
2025-09-11 Final E-23 (2027) published with cover letter and backgrounder; implementation period extended from the draft's proposed 12 months
2027-05-01 Effective date for all FRFIs

Penalties and enforcement

  • The guideline states no penalties. It sets supervisory expectations, not statutory offences.
  • OSFI checks compliance through supervision; institutions should be able to show evidence that they are structured and resourced for sound model governance (Principle 1.1).
  • OSFI did not add a grace period for third-party models, but its cover letter says an exceptions policy may allow limited use before validation is complete.
  • The cover letter says OSFI will support institutions during the transition; it sets no specific interim milestones before 1 May 2027.

What it means for an Indian company

  • Indian banks with Canadian subsidiaries or branches (for example ICICI Bank Canada): from 1 May 2027 every model, including AML, credit and treasury models, needs a risk rating, inventory entry, independent review, approval and monitoring proportionate to its risk. Start the model census and gap assessment now.
  • IT, analytics and AI vendors supplying Canadian banks and insurers: model reviews may cover your platforms, sub-components, data and libraries (Principle 3.4), and deployment needs cyber and operational risk assessments (Principle 3.5). Expect requests for documentation, explainability evidence, data lineage, version update notices and support for decommissioning.
  • Insurers: unlike PRA SS1/23 and the US guidance, E-23 also covers life and P&C insurers, so Indian insurers or insurtech suppliers with Canadian exposure are affected.
  • Comparison with RBI: E-23 is the closest overseas match to where RBI is heading. RBI's draft model risk guidance (24 June 2026, still draft as of 2026-10-19) also covers AI and ML models, and RBI FREE-AI asks for board-approved AI policy, model inventory, explainability, bias checks and decommissioning. An E-23-aligned framework would cover most of that ground.
  • Of the three model risk texts in this library, E-23 is the most AI-explicit; the US version (US Interagency MRM Guidance (SR 26-2, formerly SR 11-7)) carves out generative and agentic AI, while E-23 does not.

Obligations

Principle numbers are from sections B to D of the guideline; section letters and numbers are given where no principle number applies.

Showing 24 of 24
IDObligationReferenceApplies toControls
OSFIE23-01Apply model risk management on a risk basis, scaled to size, strategy, risk profile, complexity and interconnectednessA.3Deployer
OSFIE23-02Use OSFI's model definition, which includes AI/ML methods, and the OECD AI definition to decide what counts as a modelA.4; footnote 1Both
OSFIE23-03Senior management defines MRM roles and accountability, staffs MRM with the right skills (especially for AI) and reports model risk to the board; be able to evidence adequate resourcingPrinciple 1.1Deployer
OSFIE23-04Set up an MRM framework that fits the wider risk framework, reflects model risk appetite, defines how to identify, assess, manage, monitor and report model risk, and is reviewed as new technology emergesPrinciple 1.2Deployer
OSFIE23-05Make the framework cover models and data from foreign offices and third-party vendors, in line with Guideline B-10Principle 1.2Deployer
OSFIE23-06Deploy models only where they add real value and give reliable results for their intended use; modify, replace or retire models that no longer fitPrinciple 1.3Deployer
OSFIE23-07Periodically survey the organisation to find all models (including vendor models), triage whether each has non-negligible risk, and give new models a provisional ratingPrinciple 2.1Deployer
OSFIE23-08Keep an enterprise-level, accurate and up-to-date inventory of non-negligible risk models (including recently decommissioned ones) with at least the Appendix 1 fieldsPrinciple 2.1; Appendix 1Deployer
OSFIE23-09Rate every model's inherent risk with clear quantitative and qualitative criteria (including complexity, level of autonomy, data reliability and customer impact); re-rate on triggers; rate external models standalone; track any negligible-risk exemptionsPrinciple 2.2Both
OSFIE23-10Take remediation action where model risk falls outside appetite, and keep visibility of both inherent and residual model risk for senior management reportingPrinciple 2.2Deployer
OSFIE23-11Let the risk rating drive review depth and frequency, documentation, approval authority, monitoring and usage limits; match governance maturity to the extent of advanced AI/ML usePrinciple 2.3Deployer
OSFIE23-12Write lifecycle policies and procedures that apply by risk, assign explicit responsibilities, involve data science, business, compliance, ethics, legal, IT and risk early, keep independence, and stay flexible for black-box and autonomous AIPrinciple 3.1Deployer
OSFIE23-13Give each new or changed model a documented rationale and use case; for AI/ML also assess required explainability, alternative controls for black-box or autonomous models, and risks of bias, ethical harm or privacy breachD.2 Model rationaleBoth
OSFIE23-14Govern development data so it is accurate, representative, compliant with privacy and data ethics rules, traceable (lineage and provenance) and timely, with bias understood and managedPrinciple 3.2Developer
OSFIE23-15Run regular data quality checks and control the provenance and use of synthetic and proxy data and data cleansingPrinciple 3.2Developer
OSFIE23-16Set development standards for documentation, method and algorithm selection, explainability requirements, selection criteria, output use and monitoring criteriaPrinciple 3.3Developer
OSFIE23-17Independently review models for conceptual soundness and performance, triggered by new models, modifications, performance breaches, significant data changes and scheduled periodic reviewsPrinciple 3.4Deployer
OSFIE23-18Make reviews cover risk rating, data, novel AI/ML methods, explainability against intended use, and third-party platforms, data and libraries; report findings with an approval recommendationPrinciple 3.4Deployer
OSFIE23-19Approve models throughout the lifecycle (before changes go live and after periodic reviews), confirming suitability and the risk rating; approve models with known weaknesses only with mitigants or documented justificationD.2 Model approvalDeployer
OSFIE23-20Deploy models under quality and change control: check production data matches development data, test in production, document procedures (including overlays), assess cyber and operational risks first, and communicate explanations to stakeholdersPrinciple 3.5Both
OSFIE23-21Set monitoring standards by risk rating and model type, using quantitative and qualitative criteria, tracking changes in performance, usage, input data and external dependencies (such as version updates), with breach thresholdsPrinciple 3.6Deployer
OSFIE23-22Plan for model unavailability, performance deterioration or failure, with escalation procedures and prompt sharing of issuesPrinciple 3.6Deployer
OSFIE23-23Handle AI/ML-specific risks in monitoring (autonomous decisions, self re-parametrisation, higher drift) and set internal criteria for when a self-learning model has materially changedPrinciple 3.6; cover letterBoth
OSFIE23-24Decommission models through a disciplined process: notify stakeholders, retain the model and documentation for a set period as benchmark or fallback, handle third-party model exits and watch downstream effectsD.2 Model decommissionDeployer

Evidence an auditor will ask for

  • Approved MRM framework and model risk appetite.
  • Org chart, role descriptions and resourcing analysis for MRM, including AI skills.
  • Model identification survey results and triage records.
  • Enterprise model inventory with all Appendix 1 fields, including decommissioned models.
  • Risk rating methodology with criteria for autonomy, customer impact and data reliability, and evidence of trigger-based re-rating.
  • Model rationale documents for AI/ML models, covering explainability needs, bias and privacy risks.
  • Data governance evidence: lineage, quality check results, synthetic and proxy data controls.
  • Independent review reports and approval records, including approvals with known limitations.
  • Pre-deployment cyber and operational risk assessments and production test results.
  • Monitoring dashboards, thresholds, contingency plans and criteria for material change in self-learning models.
  • Decommissioning records and retained model archives.
  • Third-party model files linked to B-10 vendor risk assessments.

Common mistakes

  • Waiting for May 2027. Building an enterprise inventory and rating every model takes longer than most teams expect.
  • Treating E-23 as a banking-only rule; insurers and trust and loan companies are now in scope.
  • Leaving vendor and foreign-office models out of the inventory.
  • Rating AI models only on business size and ignoring autonomy, explainability and customer impact.
  • Monitoring a self-learning model without a defined point at which change counts as "material" and triggers review and approval.
  • Forgetting to check third-party libraries and version updates, which E-23 explicitly names.
  • Deleting retired models instead of keeping them as benchmarks or fallbacks.

Glossary

  • OSFI: Office of the Superintendent of Financial Institutions, Canada's federal regulator for banks, insurers and federally regulated pension plans.
  • FRFI: federally regulated financial institution, the set of firms OSFI supervises.
  • Guideline: an OSFI document setting out supervisory expectations for sound practice.
  • Inherent model risk: the risk a model carries before any controls are applied.
  • Residual model risk: the risk left over after controls, validation and monitoring.
  • Model risk rating: the risk tier assigned to a model, which decides how much scrutiny it gets.
  • Model lifecycle: design, review, deployment, monitoring and decommission of a model.
  • Explainability: how well people can understand why a model produced a given output.
  • Self-learning model: a model that updates its own parameters as new data arrives.
  • Synthetic data: artificially generated data used in place of, or alongside, real data.
  • B-10: OSFI's guideline on third-party risk management.

Key takeaways

  • Final on 11 September 2025, effective 1 May 2027; status is supervisory with the effective date still ahead.
  • Covers every model at every FRFI, including insurers and foreign branches; pension plans excluded.
  • The most AI-explicit of the three model risk texts: AI/ML is in the model definition, and explainability, bias, autonomy, drift and third-party libraries are addressed directly.
  • 24 obligations across 3 outcomes and 12 principles, from model identification to decommissioning.
  • A strong template for Indian banks and vendors preparing for RBI's model risk guidance.

Official sources

This is general information, not legal advice. Last verified 19 Oct 2026 against the official source. Laws change; confirm the current position with qualified counsel before acting.

Check your readiness

See where your controls stand today with our free compliance gap assessment.

Start the gap assessment

Talk to us about AI Governance

We map OSFI E-23 and the other rules that reach you onto one control set, and build the evidence your auditors and customers will ask for.

Explore AI Governance