Lapsed LEI in Australia: ASIC Rules and Renewal
· Robert
For a lapsed LEI in Australia, the code remains valid, but its scheduled reference-data re-validation is overdue. ASIC requires a current, not lapsed, LEI for specified roles in derivative transaction reporting; its treatment of counterparty 2 differs. Check the role being reported, then renew the existing LEI registration if renewal is overdue.
What this means in Australia
Australian Securities and Investments Commission (ASIC) Regulatory Guide 251 (RG 251) distinguishes between the LEIs reported for different parties to a derivative transaction. Under RG 251.146, a current, not lapsed, LEI is required for the reporting entity, counterparty 1 and the central counterparty. RG 251.147 says an LEI that need not be current is also required for counterparty 2, subject to Rule S1.3.1(2). The distinction depends on which party the LEI identifies in the report.
Consider an Australian proprietary company hedging AUD/USD with an FX forward through its bank. A request concerning an LEI for that transaction should be checked against the party’s reporting role, rather than treated as proof that every lapsed LEI has the same reporting consequence. The same role-by-role check matters for a superannuation trustee reporting OTC derivatives. Where the report requires a current LEI, a LAPSED status calls for attention to the existing registration.
The scale of lapsing is visible in the GLEIF LEI statistics. On 19 October 2026, GLEIF data showed 21,462 LEIs with a legal address in Australia at LAPSED status and 28,123 at ISSUED status. These are counts for that date, not a measure of how many reports involve a particular party or require correction. Re-check the live figures before using them for a later date.
Key points for LEI renewal Australia
- LAPSED describes an overdue renewal of the LEI registration; it does not mean the code has disappeared.
- For Australian derivative reporting, check whether the LEI identifies the reporting entity, counterparty 1, the central counterparty or counterparty 2.
- Renew the existing registration when its reference data needs re-validation. Do not submit a new LEI application to address a lapse.
- Check the published status and Next Renewal Date before relying on an LEI for a report with a current-status requirement.
What LAPSED means in GLEIF records
The GLEIF LEI-CDF 3.1 format defines LAPSED as an LEI registration that has not been renewed by its NextRenewalDate and is not known from public sources to have ceased operation. The status concerns the registration’s renewal, not whether the legal entity has ceased to exist.
As GLEIF explains in its guidance on timely renewal, renewal re-validates LEI reference data against a third-party source. An LEI moves to LAPSED if it has not been renewed by its Next Renewal Date or within the grace period set by its LEI issuer. GLEIF says the lapsed LEI remains valid; its reference data is behind schedule for re-validation.
That difference is useful when someone asks whether an LEI has expired. The code still identifies the entity, but a rule requiring a current registration may make the overdue renewal relevant. The remedy described here is to renew the existing LEI registration, not apply for a different code.
Do other LEI rules treat lapses the same way?
No. The following EU provisions illustrate why the entity’s role and the applicable rule matter. They are EU examples, not Australian derivative-reporting rules; use ASIC RG 251 for the Australian distinction described above.
| Role under an EU rule | Requirement or guidance |
|---|---|
| Executing investment firm | Commission Delegated Regulation (EU) 2017/590 (RTS 22), Article 5, requires the firm to identify itself in a transaction report with a validated, issued and duly renewed ISO 17442 LEI, and to keep its own LEI reference data renewed. |
| Client or counterparty | Article 13(2) and (3) of that regulation requires an executing firm to obtain an eligible client’s LEI before providing a service that triggers a transaction report, then check the code against specified identification criteria. ESMA’s transaction-reporting guidelines, section 5.5, say Article 13(3) does not require the firm to ensure that the client’s or counterparty’s LEI has been renewed. |
| Issuer | ESMA’s Q&A on MiFIR data reporting, issuer LEI Q4, says issuers should ensure their LEI is renewed. Trading venues and systematic internalisers are not expected to perform that renewal check. |
| ICT third-party provider that is a legal person | Implementing Regulation (EU) 2024/2956 (DORA register of information), Article 3(5), requires financial entities to identify such providers with a valid and active LEI or an EUID. |
ESMA’s guidance about a client’s renewal does not remove the executing firm’s separate obligation to renew its own LEI. Nor should either EU position be substituted for ASIC’s role-specific guidance. If an Australian report or another obligation raises a question about a particular LEI, check the applicable requirement with your regulator or adviser.
How widespread is LAPSED status?
Worldwide, the GLEIF figures for 19 October 2026 showed 1,212,222 records at LAPSED status and 1,988,227 at ISSUED status. These dated counts show the volume of records in each category, not the number of entities unable to conduct an activity. Both the worldwide and Australian figures should be re-checked in the live GLEIF data when cited for a later date.
How to check and renew the existing LEI
- Locate the record. Find the existing LEI in global LEI data and check that it pertains to the entity. Read its registration status and Next Renewal Date.
- Identify the reporting role. If the LEI is used in an Australian derivative transaction report, check which party it identifies under ASIC RG 251. A current-status requirement for one party should not be assumed to apply identically to every party.
- Review the reference data. Where renewal is overdue, check the entity information that will need re-validation against a third-party source.
- Renew the existing registration. Submit updated information for verification through an LEI renewal process. As a description of the process in a separate UK context, the FCA’s guidance on UK MiFIR LEIs says the holder provides updated information to the Local Operating Unit for verification and that the LOU may charge an annual renewal fee. You can renew an LEI rather than request a replacement code.
- Verify the published record. Check the status and reference data after renewal, especially where a report calls for a current LEI.
An entity with no LEI has a different task: it can apply for an LEI. An entity with a LAPSED record should start with that existing registration instead.
Preventing another lapse
Track the Next Renewal Date and leave time to review the entity’s reference data before it arrives. GLEIF refers to a grace period set by the LEI issuer, so do not assume that every registration has the same period. A reminder should give the responsible person time to confirm the data and submit updates for verification.
For related explanations, see the LEIFast Australia blog. For an immediate reporting need, check the existing LEI’s published status, identify its role in the report and renew the registration if it is overdue.
FAQ
Is a lapsed LEI still valid?
Yes. GLEIF says a lapsed LEI remains valid. LAPSED means renewal and re-validation of its reference data are overdue.
Will I receive a new LEI when I renew a lapsed one?
Renewal re-validates the reference data for the existing LEI registration. Renew that registration rather than submitting a new application.
Can a broker trade for a client whose LEI has lapsed under EU MiFIR?
ESMA says an executing investment firm is not required under Article 13(3) to ensure that a client's LEI has been renewed. The firm must obtain an eligible client's LEI before providing a service that triggers a transaction report, and must keep its own LEI duly renewed. These are EU rules, not Australian reporting requirements.
Does ASIC accept a lapsed LEI in derivative transaction reports?
Not for the reporting entity, counterparty 1 or the central counterparty: ASIC RG 251.146 requires a current, not lapsed, LEI. For counterparty 2, an LEI that need not be current is required, subject to Rule S1.3.1(2).
Sources
- ASIC RG 251 Derivative transaction reporting (April 2026)
- GLEIF - LEI statistics (counts read via the GLEIF API)
- GLEIF - LEI-CDF 3.1 format
- GLEIF blog - The Importance of Timely Renewal of LEIs
- Commission Delegated Regulation (EU) 2017/590 of 28 July 2016 supplementing Regulation (EU) No 600/2014 of the European Parliament and of the Council with regard to regulatory technical standards for the reporting of transactions to competent authorities
- ESMA Guidelines on transaction reporting
- ESMA Q&A on MiFIR data reporting
- Commission Implementing Regulation (EU) 2024/2956 of 29 November 2024 laying down implementing technical standards for the application of Regulation (EU) 2022/2554 of the European Parliament and of the Council with regard to standard templates for the register of information
- FCA - UK MiFIR Legal Entity Identifiers