# Canadian Regulators Cannot Share Data — And That Is the Problem *The IMF, FSB, and IOSCO have all identified inter-agency data sharing as essential to financial stability oversight. Canada's regulators agree in principle. The missing piece is a common entity identifier. The LEI already exists.* --- ## The Mandate Is Clear The OSC's financial stability mandate requires systemic risk surveillance — tracking exposures, concentrations, and contagion pathways across the financial system. That mandate cannot be fulfilled by any single regulator acting alone. Systemic risk is, by definition, a cross-institutional phenomenon. A fund manager's leverage, a dealer's counterparty exposure, a bank's liquidity position — these risks interact across the perimeters of OSC, OSFI, the Bank of Canada, FINTRAC, and CIRO. Monitoring them requires aggregating data across all five. Today, that aggregation is not possible in any reliable, timely, or systematic way. The IMF's Financial Sector Assessment Program (FSAP) for Canada identified this directly: inter-agency data sharing is a structural weakness in Canada's financial stability framework.[^1] The FSB has flagged the same gap at the international level.[^2] The recommendation is not ambiguous. --- ## Why Sharing Fails: The Identifier Problem Each regulatory database identifies entities differently. | Identifier | System | Issuer | |------------------|---------------------------------|--------| | Profile ID | SEDAR+ | CSA | | NRD Number | National Registration Database | CSA / CIRO | | SIRFF Code | Fund registration | CIRO | | Fund Code | Investment Fund Survey | OSC | | Business Number | Tax administration | CRA | A single registrant — a fund manager with multiple series, a dealer with affiliated entities — appears under a different identifier in every dataset. Linking records across agencies requires manually maintained mapping tables: labour-intensive, perpetually lagging, and not shared between the agencies that need them. When the next stress event arrives, regulators will be building those tables in real time. This is not a data quality problem. It is an architectural failure that makes cross-agency surveillance structurally impossible at the moment it is most needed. ### A Partial Workaround — and Its Limits The OSC Investment Fund Survey (IFS) has already recognized this problem. To enable cross-dataset linkage, the IFS explicitly collects multiple identifiers for each fund and its associated entities: LEI (for the investment fund manager, portfolio manager, and fund itself), CUSIP (for trading and holdings data), NRD number (for the IFM), the OSC fund code, and SEDAR+ profile numbers. This is identifier bridging by design — an acknowledgement that no single upstream identifier is sufficient to link a fund across the regulatory datasets that reference it. The IFS mapping approach works within the current fragmented landscape, but it is a workaround, not a solution. Every new regulatory dataset that needs to join on entity identity must build its own bridge. The maintenance burden compounds across agencies and over time. Mandatory LEI adoption would make the IFS mapping exercise unnecessary: one identifier, present at source in every system, from day one. --- ## LEI Is the Missing Join Key The Legal Entity Identifier (LEI) is a 20-character alphanumeric code that uniquely identifies any legal entity engaging in financial transactions. Governed under ISO 17442 and administered through the Global LEI System (GLEIS), the registry is free, open-licensed, machine-readable, and updated daily.[^3] If every regulated entity in Canada were required to obtain and report its LEI: > One identifier would link every SEDAR+ filing, NRD registration, SIRFF record, and CRA business entry to the same entity — automatically, without mapping tables, without bilateral data agreements, without manual reconciliation. Cross-agency data sharing becomes a database join. Systemic risk surveillance becomes possible. --- ## The World Has Already Moved The EU mandated LEI for derivatives reporting under EMIR in 2012 and extended it to securities transactions under MiFID II in 2018.[^4] The US CFTC and SEC followed. The UK retained the requirement post-Brexit. IOSCO has recommended LEI adoption as foundational to cross-border regulatory data infrastructure.[^5] Canada's regulatory datasets are already downstream of counterparties who carry LEIs — every cross-border swap, every foreign issuer filing arrives with an LEI attached on the other side. Canada reads it and discards it. Adopting LEI domestically is not a new initiative. It is closing the gap between Canada and the standard its own counterparties already use — and that its own international assessors have already recommended. --- ## A Phased Path Forward The barriers are political, not technical. A realistic adoption sequence: 1. **Reporting issuers and investment fund managers** filing on SEDAR+ — many already hold LEIs for cross-border activity 2. **Registered dealers and advisers** on the National Registration Database — NRD already captures entity-level data; LEI is a field, not a rebuild 3. **Federally incorporated financial institutions** reporting to OSFI and the Bank of Canada — the highest-priority cohort for systemic risk monitoring Each phase extends the shared key further into the system, compounding the value of every subsequent integration. An LEI costs under $100 annually to obtain and maintain. The cost of the status quo is the surveillance capacity Canada does not have. --- [^1]: International Monetary Fund, *Canada: Financial Sector Assessment Program — Technical Note on Systemic Risk Monitoring and Macroprudential Policy* (2019), IMF Country Report No. 19/244. [^2]: Financial Stability Board, *Thematic Review on Implementation of the Legal Entity Identifier* (2019). [^3]: Global Legal Entity Identifier Foundation (GLEIF), *About the Global LEI System*, gleif.org. [^4]: European Securities and Markets Authority (ESMA), *EMIR* (2012); *MiFID II / MiFIR* (2018). [^5]: IOSCO, *Use of the LEI in Securities Markets* (2020). --- *lei.johnbulmer.org · June 2026*