LEIFast

LEI Data Correction: Update or Challenge a Record

·

LEI data correction depends on whose record is wrong. If it is your entity’s record, notify the LEI issuer that manages it; if you find an error in another entity’s record, use GLEIF’s Data Challenge Facility. The issuer reviews the information and updates a record only after verifying a change against an authoritative source.

LEI data correction: key points

  • Your own reference data has changed: tell your managing LEI issuer rather than waiting for someone else to challenge the record.
  • Another entity’s record appears wrong: any LEI data user can submit a Data Challenge through the GLEIF – Challenge LEI and vLEI Data page.
  • A challenge covers one LEI record. Submit a separate challenge for each additional record, even if the errors are related.
  • GLEIF says the aim is typically to resolve a challenge within ten business days. This is an aim, not a guaranteed deadline.
  • After resolution, the person who submitted the challenge has 28 days to rate the result or resubmit it.

Your own LEI record or someone else’s?

The distinction determines the route to take. GLEIF – Data Quality Management says a legal entity must notify its managing LEI issuer when its reference data changes. Annual renewal also ensures, at a minimum, that the entity and issuer review and re-validate the data. If your own details are out of date, contact your issuer about the change; you can also renew your LEI and review its data at renewal.

For a record belonging to another entity, the Data Challenge Facility gives data users a way to flag a suspected error. You do not have to establish the correct replacement value before raising a concern: GLEIF allows a comment explaining why the field should change if the correct data is unknown. A challenge starts a review; it does not itself amend the published record.

Not sure what the record currently shows? Start by checking its details and status. The guide to looking up and checking an LEI record explains how to inspect the information before deciding what needs attention.

What LEI information can you challenge?

GLEIF permits challenges about the accuracy and completeness of an LEI record’s reference data, the referential integrity between records, possible duplicate entries, and a lack of timely response to corporate actions. Relationship data shown in LEI Search can also be challenged, including direct and ultimate parent information and reporting exceptions. This provides a route if, for example, you believe an LEI parent relationship is wrong.

A challenge can also concern the LEI code itself. GLEIF identifies exclusivity concerns, where an entity has more than one LEI, and eligibility concerns, where a legal construct does not meet the ISO 17442 criteria. These are distinct from changing a name or other reference-data field: explain the specific concern and provide the supporting information you have.

How to file a GLEIF Data Challenge

Use the GLEIF – Challenge LEI and vLEI Data page to submit the challenge. GLEIF also makes a User Guide available there if you need help with the form.

  1. Find the LEI record and identify the field or issue you want reviewed. A challenge concerns one record, but you can flag as many fields within that record as needed.
  2. Enter proposed new values where you know them. If you do not know the correct value, add a comment explaining why the existing field should change.
  3. Provide supporting evidence. The facility accepts a file upload, text containing links, or a free-text explanation or reference.
  4. Check the submission for consistency. GLEIF automatically checks challenges for data errors and contradictions, and you must complete a Captcha.
  5. Submit the challenge and keep the summary and email confirmation for reference. If several records need review, file a separate challenge for each.

What evidence should you provide?

Make the concern specific enough for the managing issuer to investigate. Identify the field you dispute, state what appears wrong, and supply a proposed value if you know it. When the correct value is uncertain, explain the reason for your doubt rather than guessing.

GLEIF accepts evidence as an uploaded file or as text, including a URL, an explanation, or a reference. Choose material that helps the issuer check the disputed information against an authoritative source: the issuer updates the record only after that verification. Supplying evidence supports a review but does not mean a proposed change will automatically be accepted.

What happens after submission?

GLEIF immediately passes a submitted challenge to the LEI issuer managing the record and sends the challenger a summary and confirmation by email. The issuer works through the issue in dialogue with the legal entity, verifies any correction against an authoritative source, and contacts the challenger with the result. While the challenge remains open, the challenger can email the issuer.

In a blog published on 7 September 2026, GLEIF blog – After the Challenge: Rate, Resubmit, Improve (7 September 2026) describes an aim to resolve challenges typically within ten business days. The same post describes options to rate the resolution or resubmit a challenge, both available for 28 days after resolution. Neither the aim nor the availability of those options means the issuer must accept the requested correction.

If you resubmit, the previously challenged fields and proposed values are copied into the new submission. You add a comment and new evidence, and the original and resubmitted challenges remain linked. This gives you a way to explain why you still dispute the result without treating the earlier review as if it never happened.

Choose the route that matches the problem

Situation What to do
Your entity’s reference data has changed Notify the issuer managing your LEI. Review and re-validation also take place at annual renewal.
Another entity’s record appears inaccurate Submit a Data Challenge for that record with the disputed fields and supporting information.
Several records appear inaccurate Submit a separate challenge for each record.
You disagree with a resolved challenge Rate the result or resubmit with a comment and new evidence within 28 days of resolution.
You want a different issuer to manage your LEI Consider transferring your LEI to another issuer; a transfer is distinct from challenging another entity’s data.

An LEI record identifies its responsible issuer in its ManagingLOU field, and the record format includes transfer statuses, according to GLEIF – LEI-CDF 3.1 format. Transfer is therefore a separate decision about who manages your record, not a substitute for telling the issuer about incorrect information. If your concern is instead a lapsed record, consult the guide to lapsed LEI status and renewal before deciding which action fits.

Check the record first, then contact your issuer about changes to your own data or submit a separate GLEIF Data Challenge for each other record you believe is wrong.

FAQ

Who can challenge LEI data?

Any user of LEI data. You do not need to be the entity or its LEI issuer. GLEIF passes the challenge to the LEI issuer that manages the record.

How long does a data challenge take?

GLEIF says the aim is typically to resolve a challenge within ten business days. The LEI issuer contacts you with the result.

What if I disagree with the result?

For 28 days after resolution you can rate the outcome or resubmit the challenge with a comment and new evidence. The resubmitted challenge stays linked to the original.

Should I use a challenge to fix my own company's LEI data?

Usually not. As the LEI owner you report changes to your own LEI issuer, and the data is re-validated at least at every annual renewal. The challenge facility is meant for users who spot errors in any record.

Sources

  1. gleif.org gleif.org
  2. gleif.org gleif.org
  3. gleif.org gleif.org
  4. gleif.org gleif.org

Related

Get LEI Renew