Country-by-Country
LEI Requirements
Legal Entity Identifiers are now required by more than 200 regulatory mandates in 40+ jurisdictions. From MiFID II in the EU to the RBI circular in India, see precisely when and where your organisation, in Luxembourg or elsewhere, needs an LEI code.
A Worldwide Drive for Entity Identification
The Legal Entity Identifier emerged from the 2008 financial crisis, when regulators found they were unable to follow counterparty exposures across borders. In 2012 the G20 endorsed the LEI system, and the Financial Stability Board set up the Global Legal Entity Identifier Foundation (GLEIF) to oversee the worldwide LEI infrastructure.
More than 3.3 million LEI codes have now been issued in 200+ jurisdictions. The European Union is at the forefront, with six major regulations requiring LEI codes, ahead of the United States, the United Kingdom and a growing set of mandates in Asia-Pacific and Latin America.
Uptake is spreading beyond financial markets. LEI fields now form part of ISO 20022, the messaging standard for cross-border payments. In force since January 2025, the EU's Digital Operational Resilience Act (DORA) requires LEI codes for ICT third-party risk reporting, while India's RBI has lowered its LEI threshold step by step, bringing millions of borrowers into scope.
The sections that follow set out regulatory details by region, a full reference table for 40 countries, the activities that trigger requirements, information on penalties and a regulatory timeline.
Key Regions
- European Union — MiFID II, EMIR, SFTR, Solvency II, CRR, CSDR and DORA
- United Kingdom — UK MiFIR, UK EMIR and FCA enforcement
- United States — Dodd-Frank, SEC CAT, CFTC and the Federal Reserve
- Asia-Pacific — JFSA (Japan), MAS (Singapore), SFC (HK), RBI (India), ASIC (Australia)
- Americas — OSC/AMF (Canada), BCB/CVM (Brazil), CNBV (Mexico)
- Middle East & Africa — DFSA (UAE), FSCA (South Africa), CMA (Saudi Arabia)
Regulations in the European Union
No region has gone further with LEI adoption than the EU. LEI requirements apply in all 27 member states through ESMA, EBA and EIOPA, while national competent authorities take charge of enforcement locally.
MiFID II / MiFIR
January 2018"No LEI, no trade" — the foundation of LEI adoption in the EU. Before executing any transaction in financial instruments admitted to trading or traded on a trading venue, an investment firm must hold the LEI code of each client that is a legal entity. Equities, bonds, ETFs, derivatives and structured products are all covered. Firms must additionally report their own LEI code and that of the issuer. Failure to comply means the trade is rejected.
EMIR (Refit)
February 2014For trade repository reporting, each counterparty to an OTC derivative contract must hold a valid, renewed LEI code. EMIR Refit (2019) tightened this: the reporting counterparty has to report the other counterparty's LEI code, and trade repositories must check LEI codes against the GLEIF database. Interest rate swaps, FX forwards, credit default swaps, equity options and commodity derivatives all fall within scope.
SFTR
July 2020SFT reports filed with trade repositories must identify counterparties, issuers, agents, triparty agents and CCPs by LEI code. Repurchase agreements (repos), securities lending, buy-sell back transactions and margin lending are in scope. Every report comprises 155 data fields, at least 10 of which use LEI codes. Implementation was staggered: banks (Jul 2020), insurers/funds (Oct 2020), NFCs (Jan 2021).
Solvency II
January 2016The Quantitative Reporting Templates (QRTs) that insurers and reinsurers file with EIOPA must include LEI codes. They serve to identify counterparties in assets (S.06), derivatives (S.08), securities lending (S.10) and reinsurance arrangements (S.31). Within the Solvency II reporting framework, group supervisors rely on LEI codes to map exposures inside groups.
CRD IV / CRR
January 2014LEI codes must appear in banks' large exposure reports (COREP), credit risk reporting and supervisory benchmarking. Under the EBA's Implementing Technical Standards, counterparties are identified by LEI code in C 26.00 (Large Exposures), C 28.00–C 31.00 (Concentration Limits) and AnaCredit granular credit reporting. CRR2 broadened LEI requirements to cover resolution reporting.
CSDR
February 2022Under the settlement discipline regime, parties to failed settlements are identified by LEI code. CSDs must carry LEI codes in settlement instructions, penalty calculations and monthly reports to NCAs, and cash penalties for settlement fails are calculated for each failing participant, identified by its LEI code. The CSDR Refit proposal seeks to simplify the regime while retaining LEI requirements.
DORA
January 2025Under the Digital Operational Resilience Act, financial entities must keep a register of information on their ICT third-party service providers, using LEI codes where these exist. Within the oversight framework, critical ICT providers are to be identified by LEI code. For the first time in EU regulation, LEI requirements thus reach past conventional financial transactions into operational risk and vendor management.
Major Non-EU Regulations
The main jurisdictions outside the EU with mandatory or recommended LEI requirements, each with its own scope and enforcement approach.
United Kingdom
Separate regime since BrexitUK MiFIR / FCA Handbook
Following Brexit, the UK transposed MiFID II into domestic legislation as UK MiFIR. The FCA kept the "No LEI, no trade" rule for investment firms transacting on behalf of legal entity clients, and its MDP Gateway checks LEI codes in real time as firms file transaction reports.
UK EMIR & the Bank of England
UK EMIR replicates the EU EMIR rules on OTC derivatives reporting, with the Bank of England supervising trade repository reporting. Since October 2024, UK EMIR Refit has obliged reporting counterparties to report the LEI code of the entity responsible for the report, as well as that of any execution agent.
United States
Regulation spread across several agenciesDodd-Frank Act / CFTC
Under the Dodd-Frank Wall Street Reform Act (2010), swap dealers, major swap participants and security-based swap entities must obtain and report LEI codes. The CFTC made LEI codes compulsory for all swap data reported to Swap Data Repositories (SDRs), the first significant US LEI mandate, in effect from 2012.
SEC Rule 613 (CAT) & Form PF
Broker-dealers must report LEI codes for institutional customers to the Consolidated Audit Trail (CAT). Under SEC Form PF (private fund reporting), advisers with AUM over $150M must report LEI codes, and the SEC's EDGAR filing systems also use LEI codes to identify issuers and reporting entities.
Federal Reserve / OFR
Bank holding companies, savings and loan holding companies and intermediate holding companies with consolidated assets of $50B+ must hold LEI codes under Federal Reserve rules. For the Office of Financial Research (OFR), LEI codes are central to systemic risk monitoring and financial stability analysis.
NAIC / State Insurance
LEI requirements for insurers' statutory filings have been adopted by the National Association of Insurance Commissioners (NAIC). State insurance regulators apply LEI codes in the Group Capital Calculation (GCC) and to identify entities when analysing holding company systems.
India
A growing LEI marketRBI Framework for Large Borrowers
Under Reserve Bank of India rules, every borrower whose aggregate fund-based and non-fund-based exposure stands at ₹5 crore and above must hold an LEI code. Implementation started in stages in 2017, with the threshold reduced over time. Banks may not renew or extend credit facilities to entities lacking a valid LEI code.
SEBI / OTC Derivatives
SEBI requires every participant in non-centrally cleared OTC derivative transactions in the interest rate, forex and credit derivative markets to hold an LEI code. The RBI has likewise required LEI codes of all participants in non-derivative markets (government securities and money markets), under phased deadlines.
Japan
JFSA mandate since 2014All OTC derivative transaction reporting in Japan must include LEI codes under JFSA rules. In line with its G20 commitments, Japan was among the earliest Asian jurisdictions to introduce LEI mandates. The Bank of Japan also relies on LEI codes in monetary policy operations and financial stability monitoring, and every financial institution under JFSA supervision must hold a valid LEI code.
Australia
ASIC Derivative RulesUnder ASIC's Derivative Transaction Rules (Reporting), reporting entities must obtain and report LEI codes for every counterparty to a reportable OTC derivative transaction. Australia operates a compulsory trade reporting regime consistent with G20 and IOSCO standards, applying to Australian financial services licensees that deal in OTC derivatives above set thresholds.
Singapore
MAS OTC ReportingUnder the Securities and Futures Act, the Monetary Authority of Singapore (MAS) requires LEI codes in OTC derivative trade reporting. Banks, licensed financial advisers and fund managers whose notional amounts exceed S$8 billion must report with LEI codes. MAS has also brought its reporting formats into line with international standards, establishing the LEI code as a core identifier.
Hong Kong
HKMA / SFC regimeOTC derivative reporting in Hong Kong is regulated jointly by the HKMA and the SFC. Authorized institutions and licensed corporations must report the LEI codes of both counterparties to reportable transactions. The regime was introduced in phases, starting with mandatory reporting of interest rate and FX derivatives, and Hong Kong, an early mover in Asia, has had requirements in place since 2015.
Canada
Provincial regulatorsIn Canada, the LEI mandate is applied by the provincial securities regulators. The Ontario Securities Commission (OSC), the Autorité des marchés financiers (AMF) and other CSA members require LEI codes for OTC derivative trade reporting by local counterparties dealing in interest rate, FX, equity, credit and commodity derivatives above set thresholds.
Switzerland
FMIA / FINMAThe Financial Market Infrastructure Act (FMIA) requires Swiss counterparties to OTC derivative transactions to report to trade repositories using LEI codes. FINMA enforces these obligations for banks, securities dealers and operators of financial market infrastructure. Switzerland's recognised equivalence with EU regimes eases cross-border compliance.
Requirements Country by Country
A full reference spanning 40+ countries. In each jurisdiction, the enforcement bodies listed monitor compliance and impose penalties.
| Country | Key Regulation | Status |
|---|---|---|
| 🇩🇪 Germany | MiFID II, EMIR, CRR | Mandatory |
| 🇫🇷 France | MiFID II, EMIR, SFTR | Mandatory |
| 🇳🇱 Netherlands | MiFID II, EMIR, SFTR | Mandatory |
| 🇮🇹 Italy | MiFID II, EMIR | Mandatory |
| 🇪🇸 Spain | MiFID II, EMIR | Mandatory |
| 🇦🇹 Austria | MiFID II, EMIR, CRR | Mandatory |
| 🇧🇪 Belgium | MiFID II, EMIR | Mandatory |
| 🇮🇪 Ireland | MiFID II, EMIR, UCITS | Mandatory |
| 🇱🇺 Luxembourg | MiFID II, AIFMD, UCITS | Mandatory |
| 🇵🇹 Portugal | MiFID II, EMIR | Mandatory |
| 🇬🇷 Greece | MiFID II, EMIR | Mandatory |
| 🇵🇱 Poland | MiFID II, EMIR | Mandatory |
| 🇨🇿 Czech Republic | MiFID II, EMIR | Mandatory |
| 🇷🇴 Romania | MiFID II, EMIR | Mandatory |
| 🇭🇺 Hungary | MiFID II, EMIR | Mandatory |
| 🇸🇪 Sweden | MiFID II, EMIR, SFTR | Mandatory |
| 🇩🇰 Denmark | MiFID II, EMIR | Mandatory |
| 🇫🇮 Finland | MiFID II, EMIR | Mandatory |
| 🇱🇻 Latvia | MiFID II, EMIR | Mandatory |
| 🇱🇹 Lithuania | MiFID II, EMIR | Mandatory |
| 🇪🇪 Estonia | MiFID II, EMIR | Mandatory |
| 🇧🇬 Bulgaria | MiFID II, EMIR | Mandatory |
| 🇭🇷 Croatia | MiFID II, EMIR | Mandatory |
| 🇸🇰 Slovakia | MiFID II, EMIR | Mandatory |
| 🇸🇮 Slovenia | MiFID II, EMIR | Mandatory |
| 🇨🇾 Cyprus | MiFID II, EMIR | Mandatory |
| 🇲🇹 Malta | MiFID II, EMIR | Mandatory |
| 🇬🇧 United Kingdom | UK MiFIR, UK EMIR | Mandatory |
| 🇺🇸 United States | Dodd-Frank, SEC CAT, CFTC | Mandatory |
| 🇨🇦 Canada | OSC/AMF derivatives rules | Mandatory |
| 🇦🇺 Australia | ASIC Derivative Rules | Mandatory |
| 🇯🇵 Japan | JFSA OTC reporting | Mandatory |
| 🇸🇬 Singapore | MAS SFA reporting | Mandatory |
| 🇭🇰 Hong Kong | OTC Derivative Rules | Mandatory |
| 🇮🇳 India | RBI circular, SEBI rules | Mandatory |
| 🇨🇭 Switzerland | FMIA | Mandatory |
| 🇳🇴 Norway | MiFID II (EEA), EMIR | Mandatory |
| 🇮🇸 Iceland | MiFID II (EEA), EMIR | Mandatory |
| 🇱🇮 Liechtenstein | MiFID II (EEA), EMIR | Mandatory |
| 🇦🇪 UAE (DIFC) | DFSA Derivative Rules | Mandatory |
| 🇰🇷 South Korea | FSC OTC reporting | Mandatory |
| 🇲🇽 Mexico | CNBV derivative rules | Recommended |
| 🇧🇷 Brazil | BCB/CVM regulations | Recommended |
| 🇿🇦 South Africa | FSCA OTC reporting | Recommended |
| 🇸🇦 Saudi Arabia | CMA Capital Markets Law | Recommended |
| 🇳🇿 New Zealand | FMA proposed reporting | Recommended |
The table focuses on the principal jurisdictions and may not capture each regulatory change. For current requirements, please refer to official regulatory sources.
Consequences of Non-Compliance
Not obtaining or not maintaining a valid LEI code can have serious repercussions. Penalties differ between jurisdictions, yet may affect business operations considerably.
Trade Rejection
Under MiFID II and UK MiFIR, it is prohibited for an investment firm to transact on behalf of a legal entity client that lacks a valid LEI code. Such trades are refused at execution, with neither a grace period nor any way around the rule.
Administrative Fines
Reporting failures can draw heavy administrative fines from national competent authorities. For legal entities in the EU, MiFID II fines may amount to €5 million or 10% of annual turnover, and the UK FCA may levy unlimited fines for market abuse and reporting failures.
Report Rejection
LEI codes are checked by trade repositories against the GLEIF database, and reports carrying invalid, expired or missing LEI codes are rejected. Under EMIR and SFTR, a rejected report amounts to a reporting breach that has to be remedied and may prompt a supervisory investigation.
Credit Facility Denial
The RBI has instructed Indian banks to not renew or enhance credit facilities for borrowers (≥ ₹5 crore exposure) without a valid LEI code. Non-compliance therefore cuts off access to bank credit, with direct effects on operations and growth.
Registration Revocation
In the United States, sustained failure to meet CFTC or SEC reporting requirements, LEI obligations included, may result in registration revocation for swap dealers, major swap participants and broker-dealers, in practice excluding the entity from regulated markets.
Lapsed LEI Code Consequences
An LEI code has to be renewed annually. Most regulators consider a lapsed LEI code (status: LAPSED) invalid, and it carries the same consequences as holding none at all: rejected trades, rejected reports and possible enforcement action. At present, over 30% of all issued LEI codes have lapsed.
LEI Code Regulatory Timeline
The worldwide growth of LEI mandates since the G20 first backed the system in 2011.
G20 Endorsement
At the Cannes Summit, G20 leaders back the creation of a worldwide LEI system and ask the Financial Stability Board (FSB) to design its governance framework.
LEI ROC & GLEIF Set Up
The LEI Regulatory Oversight Committee (LEI ROC) is formed and the first LEI codes are issued. GLEIF is set up in Basel to run the global LEI system.
EU EMIR & CRR Go Live
EU EMIR makes LEI codes compulsory in OTC derivative reporting, and CRD IV/CRR requires them in prudential reporting. The US CFTC mandates LEI codes for swap reporting, and Japan's JFSA starts to require them.
Solvency II & Wider Adoption
EU Solvency II introduces LEI requirements in insurance reporting. India's RBI sets a mandate for large borrowers (₹50 crore+), Australia's ASIC requires LEI codes and Hong Kong starts phased reporting.
MiFID II Revolution
On Jan 3rd, MiFID II takes effect, bringing "No LEI, no trade" to the whole EU. As the largest single driver of LEI adoption, it leads millions of entities to register. Canada launches OSC/AMF OTC reporting.
SFTR & Pandemic Response
EU SFTR requires LEI codes in securities financing reporting, and regulators hold to their timelines despite COVID-19. GLEIF adds Level 2 relationship data, and India's RBI cuts the threshold to ₹25 crore.
CSDR & India Expansion
The EU CSDR settlement discipline regime requires LEI codes for settlement fail penalties. India's RBI cuts the threshold to ₹5 crore, the 2M LEI codes mark is passed and UK EMIR Refit is announced.
DORA & ISO 20022
EU DORA brings LEI requirements into ICT risk management. Cross-border payment messaging under ISO 20022 carries LEI fields, SWIFT promotes LEI adoption and UK EMIR Refit enters into force.
Activities That Typically Trigger an LEI Requirement
Should your organisation undertake any of the following, an LEI code is probably required. As requirements differ between jurisdictions, please see the country table above for details.
Trading Securities
Purchasing or selling equities, bonds, ETFs, structured products or any instrument admitted to trading on a regulated market, MTF or OTF. MiFID II requires the investment firm to obtain your LEI code before the trade is executed, in all 27 EU states and in the UK.
OTC Derivatives
Concluding any over-the-counter derivative contract, such as interest rate swaps, FX forwards, credit default swaps, equity options, commodity derivatives or total return swaps. Required under EMIR (EU), Dodd-Frank (US), MAS (Singapore) and ASIC (Australia).
Bank Lending & Credit
Taking out corporate loans, revolving credit facilities or bank guarantees. In India, the RBI requires LEI codes of every borrower with aggregate exposure ≥ ₹5 crore, and in the EU, banks must report borrower LEI codes under AnaCredit for credit exposures ≥ €25,000.
Fund Management
Managing, administering or distributing investment funds, whether UCITS, AIFs, pension schemes, ETFs, REITs or private equity vehicles. Under AIFMD and UCITS V, both the management companies and the funds must hold LEI codes. Principal jurisdictions: Luxembourg, Ireland, UK.
Regulatory Reporting
Submitting transaction reports, trade reports, prudential returns or supervisory data of any kind to financial regulators, for example EMIR reports to trade repositories, MiFIR transaction reports to NCAs, COREP/FINREP to the EBA, Solvency II QRTs to EIOPA and CAT reports to the SEC.
Cross-Border Payments
Making or receiving cross-border payments through ISO 20022 messaging. SWIFT's move to ISO 20022 for CBPR+ incorporates LEI fields, and the ECB promotes LEI code use in TARGET2 and TIPS. This emerging requirement is expected to become compulsory as adoption widens.
Securities Financing
Taking part in repos, reverse repos, securities lending, buy-sell back transactions or margin lending. Under SFTR, every party to a securities financing transaction reported to an EU trade repository must have an LEI code, phased in for banks, insurers, funds and non-financial counterparties.
ICT Risk Management
Supplying or using critical ICT services within the financial sector. DORA (in force since January 2025) requires EU financial entities to identify ICT third-party service providers by LEI code in their register of information, the first LEI requirement unrelated to transactions.
Issuing Securities
Issuing shares, bonds, commercial paper or other securities on regulated markets. Issuers need LEI codes for prospectus filings, ongoing disclosure and transparency directive reporting, and national securities registers increasingly identify issuers by LEI code.
Common Questions
In which countries is a Legal Entity Identifier required?
What if I trade in the EU without an LEI code?
Is an LEI code required in the United States?
Must entities in India hold an LEI code?
What are the penalties for lacking an LEI code?
Is an LEI code needed if I trade only in my home market?
Must my LEI code be renewed to remain compliant?
Which forthcoming LEI mandates should I prepare for?
Unsure whether your jurisdiction requires an LEI code?
Our specialists can assess whether LEI requirements apply to your organisation, taking account of your country, sector and activities. Contact us and we will review your situation.
Ready to Obtain Your LEI Code?
Your Legal Entity Identifier can be issued in as little as 24 hours, with clear pricing, issuance through a GLEIF-accredited LOU and dedicated support for entities in every jurisdiction.