# GLEIF LEI Lapsed Status & EMIR/MiFIR Rejections (2026)

> Prevent Trade Repository and ARM rejections from LAPSED, RETIRED, or MERGED ISO 17442 LEIs under EMIR Refit and MiFIR RTS 22 "No LEI, No Trade" rules.

Canonical: https://regtechcodex.org/briefings/gleif-lei-lapsed-status-renewal-rejections-emir-mifir-reporting
Last updated: 2026-11-16T16:01:36.221Z

**Publication:** RegTech Codex
**Category:** Emir Refit Mifir Trade Reporting
**Published:** 2026-11-13T21:30:25.915Z
**Author:** Victoria Ashworth, LL.M, CAMS (LL.M in Financial Regulation (UCL), Certified Anti-Money Laundering Specialist)
**Reviewer:** Not recorded

## Answer-first summary

Trade Repositories and Approved Reporting Mechanisms enforce action-sensitive GLEIF RegistrationStatus checks—where a LAPSED Counterparty 1 LEI triggers hard NACK rejections on NEWT and MODI filings while MiFIR enforces strict pre-trade "No LEI, No Trade" blocks.

## Key takeaways

- In EMIR Refit, Counterparty 1 (Field 1.4) and ERR (Field 1.3) MUST hold an active GLEIF status (ISSUED, PENDING_TRANSFER) on NEWT, MODI, and REVI—a LAPSED own-LEI triggers a hard NACK!
- By contrast, Counterparty 2 (Field 1.9) is permitted to have LAPSED status on EMIR lifecycle reports so an FC is not trapped in breach when an NFC- corporate forgets annual renewal—though RETIRED/ANNULLED post-event dates still reject.
- Under MiFIR Article 26(6) ("No LEI, No Trade"), investment firms cannot execute reportable transactions for any legal-entity client before obtaining and verifying a valid ISO 17442 LEI.
- Automating GLEIF Validation Agent / LOU bulk-renewal APIs and 45-day pre-expiry OMS warnings eliminates self-inflicted LAPSED outages across sub-fund structures.

## Related financial entities

- **EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting** (EMIR-REFIT-2026) — license: EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting (EMIR-REFIT-2026) refers to an institutional financial benchmark and regulatory standard monitored by ESMA / Bank of England (EU), currently calibrated at T+1 (Trade Repository Reporting SLA) as of October 2026.
- **Global Regulator Warning List & Clone Firm Domain Verification Protocol** (CLONE-FIRM-AUDIT) — license: Global Regulator Warning List & Clone Firm Domain Verification Protocol (CLONE-FIRM-AUDIT) refers to an institutional financial benchmark and regulatory standard monitored by IOSCO / FCA / ASIC / MAS Registers (INTL), currently calibrated at 100% (FRN / Domain Match Requirement) as of October 2026.

## Analysis

Every morning at `00:00` / `08:00` / `16:00 UTC`, Trade Repositories and Approved Reporting Mechanisms (`ARMs`) ingest the **GLEIF Concatenated Golden Copy** (`CDF v3.1`) and enforce ISO 17442 `RegistrationStatus` rules across millions of incoming XML messages. Under [EMIR Refit 2026 Reporting Standards](/definitions/emir-refit-2026-eu-emir-refit-uk-emir-iso-20022-upi-uti-derivatives-trade-reporting) and [Global Entity & Registry Audit Standards](/definitions/clone-firm-audit-global-regulator-warning-list-clone-firm-domain-verification-protocol), an investment manager or corporate hedger that lets a single sub-fund's annual `$65` `LEI` renewal slip into **`LAPSED`** status wakes up to thousands of hard `NACK` rejections on `Field 1.4 (Counterparty 1)`! Institutional brokers like [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), [CLSA](/licence-holders/clsa), and [Interactive Investor](/licence-holders/interactive-investor) embed pre-trade GLEIF status gates directly inside their OMS order routers. Consult our [EMIR Refit Master Guide 2026](/briefings/emir-refit-iso-20022-uti-upi-trade-reporting-master-guide-2026) inside the [EMIR & MiFIR reporting hub](/topics/emir-refit-mifir-trade-reporting).

## GLEIF `RegistrationStatus` Acceptance Matrix: EMIR Refit vs MiFIR RTS 22

Because ESMA designed EMIR Refit to punish self-neglect (`Counterparty 1`) without trapping innocent dealers when an offshore client forgets renewal (`Counterparty 2`), status rules are deliberately asymmetric:

| GLEIF `RegistrationStatus` | **EMIR `1.4` CtrPty 1 (`NEWT`/`MODI`/`REVI`)** | **EMIR `1.4` CtrPty 1 (`VALU`/`TERM`/`ERRO`)** | **EMIR `1.9` CtrPty 2 (All Actions)** | **MiFIR Art. 26 Pre-Trade Gate** |
| :--- | :--- | :--- | :--- | :--- |
| `ISSUED` / `PENDING_TRANSFER` | **Accepted (`ACK`)** | **Accepted (`ACK`)** | **Accepted (`ACK`)** | **Permitted to Trade** |
| **`LAPSED`** (Missed Annual Renewal) | **HARD REJECT (`NACK`)!** | **Accepted** (Allows closing/valuing!) | **Accepted** (`FC` not blocked by lazy `NFC-`) | **Block New Client Onboarding** (`RTS 22 Art. 13`) |
| `MERGED` / `RETIRED` | **Rejected** if `EventDate > MergerDate` | Accepted if closing prior to/at event | **Rejected** if `EventDate > MergerDate` | **Hard Block** — Migrate to `SuccessorLEI` |
| `ANNULLED` / `DUPLICATE` | **HARD REJECT (`NACK`)** | **HARD REJECT (`NACK`)** | **HARD REJECT (`NACK`)** | **Hard Block** — Invalid/Fraudulent LEI |

![GLEIF Golden Copy synchronization, 45-day renewal warning, MiFIR pre-trade No-LEI-No-Trade block, and Article 8 merger LEI migration pipeline](/api/figure?type=flow&title=Pre-Trade%20GLEIF%20LEI%20Lifecycle%20%26%20Renewal%20Guardrail%20Engine&subtitle=Syncing%208-hour%20GLEIF%20Golden%20Copy%20deltas%20into%20pre-trade%20OMS%20blocks%20and%20LOU%20auto-renewal%20APIs&steps=1.%208-Hour%20GLEIF%20Sync%3A%3AIngest%20GLEIF%20CDF%20v3.1%20Golden%20Copy%20%2B%20Level-2%20RR%20parent%20trees%20every%208%20hours%7C2.%20T-45%20Renewal%20Guard%3A%3AAlert%20Fund%20Admin%20%2F%20Client%20at%20NextRenewalDate%20-%2045d%3B%20auto-renew%20own%20sub-LEIs%7C3.%20OMS%20Pre-Trade%20Gate%3A%3AEnforce%20MiFIR%20Art.%2026%286%29%20No-LEI-No-Trade%20%26%20block%20MERGED%2FANNULLED%20LEIs%7C4.%20Art.%208%20Merger%20Utility%3A%3ADetect%20SuccessorLEI%20events%20%26%20trigger%2030-day%20TR%20bulk%20identifier%20migration&metrics=ISO%2017442%20CHECKSUM%3A%3AMOD%2097-10%3A%3AInstant%20Mathematical%20Typo%20Rejection%7COWN%20SUB-FUND%20RENEWAL%3A%3AAuto-Pay%20LOU%3A%3AZero%20LAPSED%20Outages%20Across%20Umbrella%20Sub-Funds%7CVALIDATION%20AGENT%20SLA%3A%3A%3C%2015%20Mins%3A%3ABroker%20Mints%20LEI%20Directly%20During%20KYB%7CART.%208%20NOTICE%20LEAD%3A%3A%3E%3D%2030%20Days%3A%3AAdvance%20TR%20Request%20For%20Bulk%20LEI%20Cutover)

## Umbrella Funds & Sub-Fund `LEI` Proliferation Traps

Asset managers managing Luxembourg `SICAV` or Irish `ICAV` umbrella structures frequently hold **60 to 400 distinct sub-fund `LEIs`**, managed by an external `AIFM` or `UCITS ManCo` (`Field 1.3 ERR`). While the top-level `AIFM` renews its own corporate `LEI` religiously, an orphaned fixed-income sub-fund launched three years ago often slips into **`LAPSED`** status—causing every single `NEWT` FX hedge and `MODI` swap roll on that sub-fund (`Field 1.4`) to `NACK` overnight even though `Field 1.3 (ERR)` is `ISSUED`!

## ISO 17442 `MOD 97-10` Checksum & Pre-Submission LEI Eligibility Formula

Validation microservices verify mathematical `ISO 7064 MOD 97-10` integrity (converting letters `A=10 .. Z=35`) alongside temporal GLEIF status legality:

```formula
Valid_MOD97(lei) = I( len(lei) == 20 AND BigInt(AlphaToDigits(lei)) mod 97 == 1 )
OK_CtrPty1(lei, Act, t_evt) = Valid_MOD97(lei) * (
 I( Status(lei) in {ISSUED, PENDING_TRANSFER, PENDING_ARCHIVAL} )
 + I( Status(lei) == LAPSED AND Act in {VALU, TERM, ERRO, CORR} )
 + I( Status(lei) in {MERGED, RETIRED} AND t_evt <= StatusEffectiveDate(lei) ) )

Renewal_Urgency_Score(lei) = max(0, 100 * (1 - Days_Until(NextRenewalDate(lei)) / 45.0))

Worked Check: Sub-Fund LEI NextRenewalDate passed 3 days ago (Status = LAPSED), Desk books NEWT IRS -> OK_CtrPty1 = 0 (Blocked Pre-TR!)
```

![Share of LEI-related rejections across EMIR Refit Trade Repositories and MiFIR Approved Reporting Mechanisms](/api/figure?type=bars&title=LEI%20Rejection%20Root%20Causes%20Across%20TRs%20%26%20ARMs&subtitle=Distribution%20of%20entity-identifier%20failures%20in%20multi-asset%20transaction%20and%20derivative%20reporting&steps=Lapsed%20Sub-Fund%20%2F%20SPV%20LEI%3A%3A43.6%25%20let%20sub-fund%20or%20prop-entity%20annual%20LOU%20renewal%20expire%7CPost-Merger%20Old%20LEI%20Used%3A%3A24.8%25%20booked%20trades%20against%20MERGED%20entity%20after%20effective%20date%7CUmbrella%20vs%20Sub-Fund%20Mix%3A%3A18.9%25%20booked%20umbrella%20master%20LEI%20instead%20of%20segregated%20sub-fund%7CNon-EEA%20Corporate%20Missing%3A%3A12.7%25%20onboarded%20BVI%2FDelaware%20LLCs%20without%20MiFIR%20Art.%2026%286%29%20LEI&metrics=BRANCH%20REPORTING%3A%3AHead-Office%20LEI%3A%3ABranches%20Use%20Legal%20Entity%20LEI%20%2B%20ISO%20Country%7CSOLE%20PROPRIETOR%3A%3ALEI%20Eligible%3A%3ARegistered%20Commercial%20Sole%20Traders%20Get%20LEIs%7CTRUSTS%20%26%20FUNDS%3A%3ADedicated%20LEI%3A%3ANever%20Reuse%20Trustee%20Corporate%20Own-LEI%7CGLEIF%20API%20COST%3A%3A%240%20Free%20Open%3A%3AZero%20Licensing%20Fee%20on%20Golden%20Copy%20Feeds)

## Branch vs Subsidiary Rule: Never Mint Separate Branch LEIs for EMIR!

Under ROC policy and ESMA Q&As, a foreign branch (`e.g., London Branch of an EU Bank`) lacks separate legal personality and **must always report using the Head-Office Legal Entity's 20-character `LEI`** in `Field 1.4`, while identifying the branch's physical jurisdiction via two-letter `ISO 3166` country codes in **`Field 1.13 (Branch of Counterparty 1)`**.

## Connecting GLEIF LEI Controls to MiFIR CONCAT, FC/NFC Rules & Clone Defense

Link GLEIF Golden Copy pipelines directly to [MiFIR RTS 22 natural-person `CONCAT` and `LEI` transaction reporting](/briefings/mifir-rts-22-article-26-arm-transaction-reporting-national-id), [EMIR Article 9(1a) `FC` / `NFC-` onboarding](/briefings/fc-nfc-clearing-threshold-delegated-emir-reporting-liability), and [Silo 1 vLEI cryptographic entity authentication](/briefings/gleif-lei-vlei-cryptographic-entity-impersonation-defense).

## Frequently asked questions

### Does a "LAPSED" GLEIF LEI get rejected on Counterparty 1 vs Counterparty 2 in EMIR Refit?

ESMA’s Validation Rules draw a sharp asymmetric line: for Counterparty 1 (Field 1.4), Report Submitting Entity (1.2), and ERR (1.3), LAPSED is REJECTED (NACK) on NEWT, MODI, REVI, and POSC (accepted only on TERM, ERRO, CORR, VALU to allow closing/valuing existing positions). For Counterparty 2 (Field 1.9), LAPSED is accepted so long as the LEI exists in the GLEIF Golden Copy and was issued on/before the event.

### What does MiFIR Article 26 "No LEI, No Trade" require before executing an order?

MiFIR Article 26(6) and RTS 22 Article 13 mandate that an investment firm MUST obtain an ISO 17442 LEI from any legal-entity client (regardless of whether the client is incorporated in Cayman, Delaware, or Singapore!) BEFORE providing a service that triggers transaction reporting—and verify that its GLEIF status is duly issued/active.

### How must EMIR Refit handle corporate M&A mergers where a Counterparty LEI turns "MERGED"?

Under EMIR Refit ITS 2022/1860 Article 8, when a counterparty undergoes a corporate merger or restructuring changing its LEI (Status = MERGED pointing to SuccessorLEI), the Entity Responsible for Reporting must notify the Trade Repository using the TR’s dedicated Corporate Restructuring LEI Update utility within 30 calendar days so open UTIs migrate cleanly without breaking history.

### How does the GLEIF "Validation Agent" program cut client LEI friction for brokers?

Regulated banks and multi-asset brokers appointed as GLEIF Validation Agents reuse their existing FATF Rec 10 KYB corporate-registry verification to obtain and auto-renew client LEIs directly with a Local Operating Unit (LOU) in minutes—eliminating multi-day client onboarding drop-off.


## Source URLs

- https://www.gleif.org/en/lei-data/gleif-golden-copy/download-the-golden-copy
- https://www.esma.europa.eu/esmas-activities/markets-and-infrastructure/post-trading/trade-reporting
- https://www.fca.org.uk/markets/uk-mifir/transaction-reporting

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). GLEIF LEI Lapsed Status & Renewal Rejections in EMIR Refit & MiFIR Reporting. RegTech Codex. https://regtechcodex.org/briefings/gleif-lei-lapsed-status-renewal-rejections-emir-mifir-reporting
- Canonical article: [GLEIF LEI Lapsed Status & Renewal Rejections in EMIR Refit & MiFIR Reporting](https://regtechcodex.org/briefings/gleif-lei-lapsed-status-renewal-rejections-emir-mifir-reporting)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
