Why a name is an unstable join key
A company can appear under a legal name, an abbreviation, a translated name and an old name in different systems. Two unrelated companies can also have very similar names. Joining financial records by name alone risks splitting one entity into several records or merging distinct entities. Those errors can distort exposure totals, transaction reporting and the history of a business relationship.
The Legal Entity Identifier, or LEI, supplies a unique 20-character alphanumeric identifier linked to reference data. GLEIF describes it as identifying one entity. Its value is the stable reference across records, rather than an attempt to encode a company’s entire identity or risk profile inside the characters. An LEI is not a credit rating, bank account number or proof that the person presenting it is authorized to act for that entity. [1]
Identity and accounting relationships are separate layers
GLEIF’s Level 1 data includes reference information such as legal name and registered address. Level 2 records describe direct and ultimate accounting-consolidating parents. The direct parent is the relevant closest consolidating parent; the ultimate parent is at the top of that consolidation relationship. These definitions concern financial-statement consolidation, not a complete list of shareholders or every person who exercises control. [2, 5]
Analysis: the distinction matters when aggregating exposures. Three subsidiaries can share an accounting parent while remaining separate contractual borrowers. Summing their balances may reveal a group concentration, but it does not establish that the parent guarantees repayment. Conversely, two businesses can share an investor or influential person without creating the accounting-parent relationship represented in Level 2. An identity database and a legal analysis answer different questions.
A matching example with two valid levels of aggregation
Hypothetical records show “Harbor Equipment Ltd.” owing $4 million in one system and “Harbor Equip Limited” owing $3 million in another. Assume both are verified against the same LEI. The combined entity exposure is $7 million, not two unrelated customer exposures. Now assume a different company, “Harbor Leasing Ltd.,” owes $5 million and has its own LEI but the same reported accounting parent. The group view totals $12 million, while the two-entity view remains $7 million and $5 million.
The correct total depends on the question. Customer servicing may need the legal-entity split. A concentration analysis may need the group total. A recovery forecast would also need guarantees, security and claim priority that the LEI relationship does not supply. If the second $3 million record was merely a duplicate import of part of the first balance, summing it would still overstate exposure. Identifying the entity resolves one dimension of duplication, not every accounting reconciliation.
Missing parents do not prove independence
GLEIF provides explicit reporting-exception records. Reasons include the absence of a qualifying parent, a parent without an LEI and permissible non-public reporting exceptions. Its documentation distinguishes non-consolidating cases, including natural-person control, from non-public relationships and missing parent identifiers. A blank parent field and a documented exception therefore convey different information. [3]
Analysis: a graph showing no link can mean there is no relationship of the specified kind, the relationship cannot be publicly reported, or the necessary identifier is missing. Treating all three as “independent company” would create false certainty. Treating an exception as evidence of misconduct would be equally unsound. The exception describes a reporting state within this system, not a conclusion about business conduct.
Accounting-parent data also cannot substitute for jurisdiction-specific beneficial-ownership records. A natural person may sit behind a business without appearing as a parent LEI. The database’s public character and defined scope are strengths for reuse, but limits when a question requires sensitive ownership information or evidence outside the consolidation framework.
Renewal status is different from the entity’s operating status
GLEIF explains that LAPSED means the LEI reference data has not been reverified within the planned interval. It does not mean that the entity has stopped operating. Similarly, a lapsed relationship record does not establish that the relationship ended. Registration and relationship status need to be read separately from the entity’s own status and the relevant dates. [4]
Analysis: an old but correctly linked identifier can still help locate historical records. It may be insufficient to establish a current address or parent. A reporting regime can impose its own requirements for current identifiers; the database’s ability to display a record does not settle whether that record meets a specific legal obligation. This article does not present one universal LEI mandate across countries and transaction types.
Annual renewal is the usual reference-data maintenance cycle described by the LEI Regulatory Oversight Committee. Its report explains that lapsed records remain in the database to preserve transparency and history. The same policy record discusses the system’s defined treatment of entities and international branches. A branch identifier, where permitted, does not create separate legal personality, and an organizational identifier is not a general identity number for every private individual. [5]
Changes require time-aware interpretation
Hypothetical: a borrower belongs to Group A at the start of a year and is acquired by Group B in June. A year-end parent map applied mechanically to January transactions would describe the earlier transactions using the later ownership structure. That may be useful for one present-day concentration analysis but wrong for a historical question about who controlled the business at the time.
Names, addresses and relationship records also change on different dates. A name change need not imply a new legal obligor; a legal reorganization may be more consequential than a name change. Analysis therefore depends on both entity continuity and the period represented by the source records. A single latest snapshot cannot reconstruct every historical corporate event.
Benefits, costs and the limits of an open identifier
Analysis: a common identifier can reduce repeated name matching across counterparties, reports and internal applications. Its benefits are larger when coverage is broad and the original identifier is preserved through downstream systems. Maintaining separate local identifiers is not inherently a problem if the mappings remain accurate; silently losing the external identifier is more damaging.
Public reference data also does not authorize unrestricted combination with private customer records. Access to the public identifier and permission to use sensitive associated information are distinct questions. An accurate join can create a more revealing dataset, which changes privacy and access considerations even when the original LEI record was public.
Evidence of value would include fewer false merges and splits, reconciled exposure totals, current relationship coverage and understandable treatment of exceptions. Growth in the number of identifiers alone cannot establish those outcomes. The LEI is a shared anchor for organizational identity: useful because its meaning is bounded, and liable to mislead when it is treated as a complete ownership, authority or risk assessment.
Sources
- GLEIF: The Legal Entity IdentifierSourceBack to text: ↑
- GLEIF: Level 2 Data: Who Owns WhomSourceBack to text: ↑
- GLEIF: Level 2 Data: Reporting Exceptions Format 2.1SourceBack to text: ↑
- GLEIF: How to use LEI Search; lapsed record definitionsSourceBack to text: ↑
- LEI Regulatory Oversight Committee: Progress report, May 2018; renewal and system scopeSource · PDFBack to text: ↑1↑2