Professional illustration showing U.S. swap reporting and counterparty identification using a Legal Entity Identifier (LEI), featuring a swap report, LEI verification through a magnifying glass, financial institution icon, subtle New York skyline, Statue of Liberty, and U.S. flag in a clean, minimalist corporate design.
A swap report contains far more than the economic terms of a transaction.
It also needs to identify the organisations involved. That sounds simple until the same organisation appears under an abbreviated name in one system, a former address in another and a locally formatted registration record somewhere else.
The Legal Entity Identifier was created to reduce that ambiguity.
An LEI is a unique global identifier connected to verified reference information about an organisation. In the United States, it is used in swap recordkeeping, swap-data reporting and other financial workflows where organisations must be identified consistently.
Why names are not enough
Organisation names are not reliable identifiers on their own.
Two unrelated organisations may have similar names. One organisation may trade under a name that differs from its registered name. A name may also change following a restructuring while older records continue to circulate.
The LEI provides a persistent reference that reporting systems can use alongside the organisation’s official information.
This is particularly valuable in financial markets, where one transaction can pass through internal systems, execution venues, reporting providers, repositories and regulators.
Each handoff creates another opportunity for inconsistent information.
The LEI in U.S. swap reporting
U.S. swap-reporting rules require eligible counterparties and relevant market organisations to be identified through a single LEI.
The identifier may be used in recordkeeping and data submitted to a swap data repository. It helps reporting systems distinguish one counterparty from another and connect activity involving the same organisation.
The LEI does not describe the financial terms of the swap. It tells the system which legal organisation is involved.
That distinction is important. Transaction identifiers identify transactions. Product identifiers classify instruments. The LEI identifies the organisation.
Each code answers a different question.
Beyond the CFTC framework
The LEI also appears outside CFTC swap reporting.
It may be used in security-based swap reporting, issuer reference data, supervisory filings, broker onboarding and cross-border counterparty verification.
An organisation may first encounter the LEI because of a reporting rule. Later, the same identifier may be requested by a bank, a broker or an international counterparty.
This is one reason finance teams should manage the LEI as part of the organisation’s core reference data rather than as a code belonging to one transaction.
What the LEI record contains
The public LEI record connects the code to information used to identify the organisation.
This includes Level 1 information, which answers “who is who”. Typical fields include the official name, registered address and jurisdiction.
The record may also include Level 2 relationship information. This answers “who owns whom” by recording direct and ultimate accounting-consolidating parent relationships where applicable.
The LEI record is not a complete due-diligence file. It does not replace the checks a bank or regulated financial firm must perform.
It does, however, provide a standard starting point.
Why the status matters
An organisation does not receive an entirely new identity each time the LEI is renewed.
The existing record is revalidated. If information has changed, it can be updated while the same code continues to identify the organisation.
When the record is not renewed, its status may become lapsed. The code still exists, but the associated information has not been revalidated within the annual cycle.
That distinction can matter to reporting systems and counterparties. Some may accept the identifier in limited circumstances. Others may require an active status before proceeding.
Finance teams should not assume that a code is ready for use simply because it can be found in a search.
Common data problems
Many LEI issues begin with ordinary administrative changes.
An organisation may move to a new registered address. Its official name may change. A merger may alter its ownership relationships. An applicant may submit information that does not match the relevant state registry.
None of these situations is unusual, but they need to be reflected accurately.
Common problems include:
- Using a trading name instead of the registered name
- Entering an old address
- Providing an incorrect state registration number
- Leaving outdated parent information unchanged
- Assuming a transfer will create a new LEI
- Waiting until a reporting deadline to check the status
The last mistake is often the most disruptive because it leaves no room to resolve a discrepancy.
Registration, renewal and transfer
These three processes are related but serve different purposes.
Registration is used when an eligible organisation does not already have an LEI.
Renewal confirms and updates the reference information linked to an existing LEI.
Transfer moves management of the record from one GLEIF-accredited issuing organisation to another. The LEI itself remains unchanged.
Before submitting any request, the organisation should search the Global LEI Index. Duplicate applications create additional work and can delay the process.
A practical control for finance teams
The LEI should have an internal owner.
That person or team does not need to manage every transaction. The role is simply to make sure the identifier remains accurate and available when another department needs it.
A basic internal record should include:
- The LEI
- Current status
- Managing issuing organisation
- Renewal date
- Registered name
- Registered address
- Responsible internal contact
- Date of the most recent ownership review
This information can be maintained alongside other corporate reference data.
Where to find U.S. guidance
The U.S. LEI registration information published by TNV LEI explains registration, renewal and transfer for organisations registered in the United States.
The useful point is not the application link itself. It is the country context: validation sources, reporting uses and the information that should be checked before submission.
Final thought
The LEI is not the most visible part of a swap transaction, but it solves a basic problem that every reporting system faces: identifying the organisations on each side.
When that identity is accurate and current, data can move between systems with less ambiguity. When it is neglected, a simple reference field can become a reporting problem.
Frequently asked questions
Is an LEI the same as a transaction identifier?
No. An LEI identifies an organisation. Transaction identifiers identify individual transactions.
Can an organisation have more than one LEI?
A legal organisation should have one unique LEI. Teams should search existing records before submitting a new application.
Does transferring an LEI change the code?
No. Only the managing issuing organisation changes.
Is LEI data public?
Yes. The Global LEI Index provides public access to LEI records and associated reference information.
Does an LEI replace bank due diligence?
No. It supports entity identification but does not replace a bank’s own review obligations.
Research references: U.S. usage was checked against TNV LEI’s live country page, GLEIF guidance and the CFTC rule requiring eligible swap counterparties to obtain, maintain and use a single LEI in relevant recordkeeping and reporting.
