The LEI portfolio nobody owns: why renewals fail in multi-entity groups
A Legal Entity Identifier lapses for one reason more often than any other, and it is not cost, complexity or regulatory confusion. It is that nobody was given the job.
In a single-entity company this rarely matters. One record, one renewal date, one person who remembers. In a group of fifty, or a hundred, or several hundred separately incorporated entities, it matters a great deal, because the task is small enough to fall between functions and public enough that failure is visible to anyone who looks.
An LEI lapses when its annual renewal is not completed on time. The code remains resolvable, but its registration status changes to LAPSED in the Global LEI Index, which is public. A lapsed LEI can block transaction reporting, stall client onboarding, and cause counterparties to reject trades.
That is the whole failure mode. What follows is why it happens to sophisticated organisations, and what actually fixes it.
Why LEI renewals get missed
1. No owner. LEI renewal sits between company secretarial, finance, compliance and operations, and is small enough that none of them claims it. The person who registered the LEI three years ago has changed roles. The renewal notice goes to their old address.
2. Distributed registration. Where each subsidiary or member firm registered independently, there is no list. Producing one requires querying public data, which almost nobody does about their own organisation.
3. Renewal reminders that depend on a mailbox. Every issuer sends reminders. They go to the email address captured at registration, which decays at the ordinary rate of staff turnover.
4. Corporate change. Mergers, name changes, entity migrations and restructures all disturb LEI records, and the record does not update itself. A renewal falling shortly after a restructure is the most commonly missed one of all.
None of these is negligence. They are structural, and they recur.
What a lapsed LEI actually costs
The consequences are operational. There is a set of things that stop working.
Transaction reporting. The FCA is explicit: “Firms subject to UK MiFIR transaction reporting obligations will not be able to execute a trade on behalf of a client who is eligible for a Legal Entity Identifier (LEI) and does not have one.” (FCA, updated 28 July 2026)
Client and counterparty onboarding. Financial institutions screen counterparty LEI status as part of due diligence. A lapsed status is a flag on an otherwise clean file.
Your clients’ own regulatory filings. This is the newest and least understood consequence. Under DORA (Regulation (EU) 2022/2554, Article 28(3)), EU financial entities must maintain a Register of Information covering every ICT third-party service provider. The implementing standards (Commission Implementing Regulation (EU) 2024/2956, Article 3(5)) require each provider to be identified by an LEI or a European Unique Identifier.
The European Banking Authority settled how that works in Single Rulebook Q&A 2024_7283, published 28 March 2025:
“Only LEI or EUID can be used for legal persons, as identified in B_05.01.0070, whereas alternative code may be used only for an individual acting in a business capacity. Only LEI can be used for legal persons that are not established in the Union.“
Deloitte’s Digital Operational Resilience Act: Survey for Financial Services Entities, Wave 3 (March 2025, 36 entities across 28 countries) found that 46% of respondents rated completing the Register of Information the single most challenging DORA requirement, ahead of every other obligation, and that only 8% considered themselves fully compliant with ICT third-party risk management. In Luxembourg, the CSSF reported that as at 16 March 2026, only 40% of financial entities had submitted their register ahead of the 31 March deadline.
Reputation. LEI status is published in the Global LEI Index and searchable by anyone, including clients, counterparties, regulators and competitors. Unlike most compliance failures, this one is visible from outside the building.
The instinct is to improve the reminder process. That does not work, because the reminder process was never the problem. Ownership was.
Step 1: map what you actually hold. Query the Global LEI Index for every entity registered under your organisation’s name. Record the LEI, jurisdiction, managing issuer, registration status, next renewal date and whether Level 2 parent data is complete. Most groups have never done this and are surprised by the result. It is public data about your own organisation.
Step 2: consolidate to one issuer. Transfers between LEI Issuers happen within GLEIF rules with no gap in coverage. The record keeps the same LEI code. Bulk transfer is supported, so entities move together rather than one at a time. Consolidation replaces many renewal cycles with one and gives you a single portfolio view.
Step 3: move to multi-year auto-renewal. This is the step that actually removes the failure mode. A multi-year plan with automatic renewal does not depend on anyone remembering, on a mailbox still being monitored, or on a role still existing. It changes renewal from a recurring task into a completed decision.
Step 4: assign an owner anyway. Automation handles renewal. It does not handle entity changes, name changes, new incorporations or Level 2 relationship data. Someone still needs to own the register. Name them.
| Consideration | What to check |
|---|---|
| Accreditation | Is the provider a GLEIF-accredited LEI Issuer, or a Registration Agent reselling through one? Only an accredited issuer publishes directly to the Global LEI Index. |
| Jurisdictional coverage | Can one issuer cover every jurisdiction your entities sit in? If not, you have not consolidated, you have reduced. |
| Renewal model | Are multi-year plans with automatic renewal available, or only annual manual renewal? |
| Portfolio visibility | Is there a dashboard covering the whole estate, or a separate account per entity? |
| Data quality | What are the provider’s Policy Conformity Flag metrics across its issued portfolio? |
| Pricing transparency | Is the GLEIF levy included, or added later? |
Frequently asked questions
What does it mean when an LEI is lapsed? A lapsed LEI is one whose annual renewal was not completed on time. The 20-character code remains valid and the record stays in the Global LEI Index, but its registration status shows as LAPSED. Reference data is no longer treated as verified, and many counterparties and reporting systems will reject it.
Can a lapsed LEI be reactivated? Yes. Completing the renewal returns the record to ISSUED status. You do not get a new code, and there is no penalty for reactivating, but the lapse remains visible in the record’s history.
How often does an LEI need to be renewed? Annually. Every LEI carries a next renewal date, published in the Global LEI Index, at which the entity’s reference data must be re-verified against an authoritative source.
Can I move my LEIs to a different issuer? Yes. Transfer between GLEIF-accredited LEI Issuers is a standard process that runs within GLEIF rules with no gap in coverage. The LEI code does not change. Bulk transfers are supported for groups moving multiple entities together.
Does DORA require my company to have an LEI? Not directly. DORA’s Register of Information obligation binds EU financial entities, not their suppliers. However, those financial entities must identify each ICT third-party service provider by LEI or EUID, and per EBA Q&A 2024_7283, only an LEI may be used for legal persons not established in the European Union.
How do I find out which LEIs my group holds? Search the Global LEI Index by legal name. Note that a name-prefix search will miss group entities registered under a different trading name, so treat any count you produce this way as a floor rather than a total.
What is Level 2 data? Level 1 data answers “who is who”: legal name, address, registration details. Level 2 data answers “who owns whom”: direct and ultimate parent relationships. Many group entities report a parent reporting exception rather than a parent LEI, which leaves the ownership picture incomplete in public data.
The conclusion
An LEI is a small obligation. That is exactly why it is neglected, and why the neglect is visible.
If you run a group of more than a handful of legal entities and cannot name the person who owns your LEI register, you already have the problem described in this article. The first step is not to buy anything. It is to look at your own public data and see what is there.
RapidLEI is a GLEIF-accredited LEI Issuer, accredited since June 2018, and the world’s largest LEI Issuer with more than 450,000 LEI clients across 150+ jurisdictions. We will assemble a verified map of your group’s LEI estate at no cost. Get in touch.
