LEI data: what information is public, and how to keep it accurate

A Legal Entity Identifier is often described as a passport for organisations in financial markets. That description fits, yet it misses a key point: the passport is only as useful as the details printed inside it.

LEI reference data is public by design, and that openness is precisely why accuracy matters. When your name, address, registration details, or ownership links are wrong or out of date, the friction tends to show up at the least convenient moment: onboarding, reporting deadlines, trade execution, or a counterparty review.

What “LEI reference data” actually means

An LEI is a 20-character code, but the code is only the index key. The value sits in the record attached to it: a standard set of fields defined by ISO 17442 and shaped by global policy rules.

Reference data is split into two broad layers:

  • Level 1 answers “who is who?” with business-card style facts about the entity.
  • Level 2 answers “who owns whom?” with parent relationships based on accounting consolidation.

That combination is what allows firms, platforms, and regulators to match the legal entity behind a trade or report with confidence, even when names are similar or translated.

What information is public, and why that is the point

LEI data is intended to be a public good. Anyone can look it up and use it without paywalls, because the system is meant to reduce ambiguity across markets, jurisdictions, and internal databases.

In practice, this means your LEI record is not “private account data”. It is closer to a standardised listing: visible to counterparties, vendors, clients, and regulators.

A useful mental model is this: LEI reference data is the minimum set of facts that lets others identify your entity correctly and place it in a corporate group structure when relevant.

Level 1 data: the “who is who” fields you will see

Level 1 reference data typically includes the entity’s legal name and registered address, plus the country of formation and coded jurisdiction information. It also includes key dates, which show when the LEI was first issued, when it was last updated, and the current registration status.

Many records also show details that make matching far easier in real-world operations, including legal form and registration authority information.

After checking a typical record, you will often see fields along these lines:

  • Legal name (as recorded in an official register)
  • Registered address (street, locality, region, postcode, country)
  • Country of formation and relevant ISO codes
  • Registration authority and registration number (when available)
  • Legal form
  • Managing LOU (the issuer responsible for the record)
  • Key timestamps (initial registration date, last update date, next renewal date, plus status markers)

One sentence matters here: the “right” version of your name and address is the version held in the authoritative public register, not the version used on stationery, websites, or invoices.

Level 2 data: the “who owns whom” relationships

Level 2 is about corporate structure, expressed through accounting consolidation. Where applicable, it identifies:

  • The direct accounting consolidating parent
  • The ultimate accounting consolidating parent

Those parents are represented by their own LEIs, which creates a machine-readable chain through corporate groups.

Level 2 is not always present. Some entities have no parent under the relevant accounting definition, and some cannot report a parent relationship for valid policy reasons (including cases where a parent does not have an LEI).

When Level 2 is present and correct, it can speed up due diligence and reduce repeated questions about group structure, especially where multiple subsidiaries trade or report across venues.

How the public data is published, searched, and reused

The Global LEI Index, maintained by GLEIF, is the authoritative directory for LEI reference data. The data is distributed in standard formats (Common Data File schemas), and it is updated frequently, at least daily, with options for higher-frequency snapshots and change files.

Because the licensing is open (CC0), LEI data is used in internal reference databases, onboarding tools, risk systems, reporting workflows, and counterparty screening.

The practical routes to access it are varied, and they suit different needs:

Access methodBest forWhat you getTypical cadence
Web search (GLEIF search)Quick checks by humansFull Level 1 and linked Level 2Always current view
REST APISystem-to-system checksFiltered lookups, fuzzy matching, relationshipsNear real time through updates
Daily bulk files (concatenated)Large-scale reconciliationA full snapshot of the populationDaily
Golden Copy filesHigh-control data pipelinesCurated snapshots plus structured change handlingMultiple times per day
Delta filesMonitoring changesOnly what changed in a time windowSeveral windows available
Mapping files (e.g. BIC, ISIN mappings)Cross-referencing identifiersLinks between LEI and other codesUpdated as published

This openness has a simple implication: if your record is wrong, it is not only “wrong in one place”. It is likely to be replicated into many downstream systems, then rechecked at the point of trading or reporting.

The accuracy rule that catches people out: annual validation

LEI reference data is not “set once”. Each LEI must be revalidated at least every 12 months. If it is not renewed on time, the status becomes lapsed, and many market participants will treat that as a stop signal.

The renewal is more than a fee payment. It is the formal point at which the record is checked again against authoritative sources, and corrected if anything has changed.

A lapsed record tends to create operational delays that feel disproportionate to the task required to fix it.

What to keep accurate, and what usually changes first

Most inaccuracies are not dramatic. They are ordinary corporate housekeeping that never made it into the LEI record.

Common triggers include registered office moves, legal name updates, changes to legal form, or corporate actions that alter group structure. Even punctuation and spacing differences can matter if a counterparty’s matching rules are strict.

After considering the typical change patterns, it helps to treat these as “update events” rather than “nice-to-have improvements”:

  • Registered office address: changed at Companies House, but not reflected in the LEI record yet
  • Legal name: rebranding is not the same as a legal name change, and the LEI must follow the legal register
  • Registration details: wrong authority code or number can block matching in onboarding tools
  • Parent relationships: group restructures can make Level 2 stale quickly
  • Status and dates: a renewal missed by a few days can still cause a trade failure

That list is short, because it is meant to be. The aim is reliable identification, not a marketing profile.

What “keeping it accurate” looks like in practice

Good LEI hygiene is a blend of process and timing. You want updates to happen when the underlying facts change, and you want renewals handled before expiry becomes visible to the outside world.

A workable operating rhythm for many UK entities is:

  • Review the LEI record during annual compliance or corporate secretarial cycles
  • Trigger an immediate update after a material change is filed in the official register
  • Renew early enough to absorb validation questions without pressure

After you have checked the rhythm, the next question is ownership: who inside the organisation is responsible for the record?

A short set of roles tends to work well:

  • Company secretariat or legal operations
  • Compliance (where the LEI is tied to reporting obligations)
  • Treasury or dealing teams (where “no LEI, no trade” is felt first)

Where errors come from, even with good intentions

Many mistakes occur because people submit the information they use day to day, rather than the information as stated in the official register.

Another source is timing. An address change may be filed and visible publicly, but the LEI update waits until renewal. That gap can be enough to trigger mismatches with banks and platforms that compare records automatically.

Then there is simple fragmentation: different teams hold different “master” records, and the LEI is treated as a reporting detail rather than an enterprise identifier.

The operational cost of a lapsed or inconsistent record

In many settings, an LEI is checked automatically. A lapsed status can lead to rejected submissions, failed onboarding checks, or a paused trade.

Even when nothing is formally rejected, counterparties may interpret a lapsed record as a sign that key corporate data is not being maintained carefully. That impression is avoidable.

Accuracy also affects analytics. If Level 2 parent data is wrong, group exposure and concentration views can be distorted. If Level 1 address data is wrong, location-based controls and jurisdiction filters can misfire.

How registration agents help, and what to look for

Many entities prefer not to manage LEI administration directly, especially when multiple entities, renewals, or time-sensitive issuance are involved. A registration agent can handle the application workflow, follow up validation requests, and keep renewals on schedule.

LEI Service, for example, acts as an official LEI registration agent of Ubisecure RapidLEI and focuses on UK entities. Services commonly include registration, renewal, transfers between issuers, express handling where deadlines are tight, and support by phone and email. Some agents also offer free updates to LEI reference data when official register details change.

After you have decided to use an agent, it helps to check for a few practical capabilities:

  • Speed options: standard and express issuance when a trade deadline is close
  • Support: responsive, English-speaking help when validation questions arise
  • Data handling: ability to update reference data without adding friction or hidden fees

Those are not “nice extras”. They are the difference between an LEI being a quiet utility and an annual scramble.

A simple control checklist for UK entities

Treat this as a lightweight control, not a bureaucratic exercise. It fits well into existing corporate administration.

  1. Pull your current LEI record from the GLEIF search.
  2. Compare legal name, registered address, and registration number against Companies House (or the relevant authoritative register).
  3. Check the LEI status and renewal date, then schedule renewal well ahead of expiry.
  4. If Level 2 applies, confirm direct and ultimate parent relationships still match current consolidation.
  5. After any corporate filing that changes reference details, trigger an LEI update rather than waiting for renewal.

One sentence can guide the whole approach: the goal is that the public record matches the official record, all year round, with no surprises for the people who rely on it.

back to top