OSFI B-12 2027: an implementation and evidence checklist.
The final B-12 update gives Canadian banking teams a short implementation window. Start with the institution's fiscal year-end, then connect each change to a tested configuration, an accountable owner and a reviewable decision.
Regulatory snapshot
Status: final supervisory guideline, with implementation pending as of this article's review date. The controlling instrument is the 2027 B-12 guideline. Its scope covers banks, including federal credit unions, bank holding companies, and federally regulated trust and loan companies. It applies on a consolidated basis, proportionate to the institution's characteristics. This is a banking-book interest-rate risk framework, not an insurer capital standard.
What changed
OSFI's final letter identifies three changes from the 2019 version: Annex 1 incorporates the Basel Committee's revised interest-rate shocks; the earnings-measure guidance addresses balance-sheet scenarios; and detailed public-disclosure provisions are replaced by a reference to OSFI's Pillar 3 guidelines.
Paragraph 34 of the final guideline specifies a constant balance sheet for earnings measures. Depending on the institution, a dynamic view that includes future business can supplement that assessment. Teams should avoid treating a business-plan forecast as an automatic substitute for the constant-balance-sheet result.
What did not change
B-12 still addresses both economic-value and earnings exposure. The final text retains governance, independent review and model-control expectations. A revised scenario table does not remove the need to understand the institution's assumptions. See the guideline's principles and measurement sections.
The related Pillar 3 amendment is a separate workstream. OSFI's September 10 backgrounder says it plans to finalize that draft on November 19, 2026. B-12's final status should not be copied onto the outstanding disclosure amendment.
An implementation checklist for the evidence owner
The following is Sia's suggested operating approach, not an OSFI-prescribed template or additional supervisory requirement. Adapt the roles and approval route to the institution.
- Record the covered entities and fiscal year-end. Have compliance confirm the applicable implementation date before assigning delivery milestones.
- Create a paragraph-level comparison against the version currently in use. Classify each item as a configuration change, methodology decision, documentation update or separate disclosure dependency.
- Ask treasury and risk technology to identify where scenario parameters are stored. Include production settings, test scripts and downstream reports; a corrected policy with an unchanged system is an incomplete implementation.
- Agree an acceptance test with independent risk or model validation before running it. Preserve the input date, configuration version and reviewer, so a result can be reproduced.
- Give exceptions an owner and a decision date. Distinguish an accepted limitation from an unresolved defect, and avoid closing either through a generic project-status label.
- Put the separate disclosure amendment on a monitored dependency list. Reassess its impact when the final text appears rather than assuming the draft survives unchanged.
A compact evidence pack
For a practical handover, use an evidence register with one reviewable artifact per decision. The suggested owners below are illustrative, not roles assigned by the guideline.
| Decision | Suggested owner | Evidence to retain |
|---|---|---|
| Which version and date apply? | Compliance | Scope record, source version and approved delivery date |
| What changed in the implementation? | Treasury and risk technology | Parameter comparison, release record and linked test results |
| Can differences be explained? | Independent risk or model validation | Reconciliation, reviewer challenge and disposition of exceptions |
| Who accepted readiness? | Accountable management | Approval record identifying residual issues and follow-up dates |
Illustrative example: hold a portfolio snapshot constant and compare runs using the old and new parameter sets. Record unexplained movements as issues before updating the management report. Then test the revised implementation with current inputs. This proposed sequence separates configuration effects from portfolio changes; it does not establish regulatory compliance or replace specialist validation.
The same source-to-decision discipline is covered in our regulatory change management guide. Our comparison of GRC and regulatory intelligence explains the handoff between detecting a change and managing its implementation.
How RegReview and RegMatcher can support the workflow
Subject to confirming and configuring the relevant source coverage, RegReview can support monitoring of subsequent publications. RegMatcher can help map selected source requirements to policies and supporting evidence. This article does not claim an existing OSFI connector. Neither workflow replaces an interest-rate calculation engine, model validation, treasury judgment or an accountable compliance decision. Discuss the source and evidence requirements for your institution.
What to watch next
Check OSFI's stated November 19 Pillar 3 finalization milestone and any intervening clarification. Keep that planned publication date separate from the institution's B-12 effective date. Before closing the implementation, verify the source version again and confirm that open dependencies remain visible to the decision-maker.
Primary sources
- OSFI: final Interest Rate Risk Management Guideline (2027), September 10, 2026
- OSFI: final B-12 publication letter, September 10, 2026
- OSFI: final B-12 backgrounder and separate Pillar 3 timetable
This analysis is general information, not legal, regulatory or financial advice. Confirm the current guideline, institutional scope and applicable supervisory expectations with qualified advisers.