Entity type is one of the easiest LEI details to oversimplify. In LEI data, an LLC, a trust, and a fund are not just different labels. They can trigger different eligibility, classification, and reporting outcomes.
TL;DR: Summary
- LEI entity types are standardized reference-data classifications, not informal descriptions: an LLC is usually identified through its LegalForm and EntityLegalFormCode, a trust may qualify for an LEI if it can enter contracts or is legally or financially responsible for transactions, and a fund can also appear with the EntitySubCategory FUND.
- GLEIF’s LEI framework uses ISO 20275 for legal-form coding, and the February 2026 ELF code list contains more than 3,600 legal forms across more than 200 jurisdictions, each with a unique four-character alphanumeric code.
- For eligibility, the key test from ISO 17442 is whether the party is a legal entity that enters financial transactions or has the legal right to contract independently, even if it is a trust, partnership, or contractual arrangement.
- For US private fund reporting, the SEC’s 2024 Form PF amendments require advisers to report the LEI of the reporting fund and parallel funds if assigned, and RSSD IDs cannot substitute for an LEI.
- If one structure contains several parties, each party does not automatically share one LEI. If the LLC, trust, or fund is the transacting or reportable entity, then that specific entity usually needs to be identified on its own terms.
That distinction matters in onboarding, derivatives trading, securities reporting, and fund filings. The practical question is not “What do we call this structure?” but “Which legal entity is actually recognized in LEI reference data, and which identifier does the regulator or counterparty expect?”
LEI entity type means standardized legal-identity data, not a casual label. GLEIF records fields like LegalForm so an LLC, trust, or fund can be described consistently inside the Global LEI Index.
In LEI Level 1 data, the legal form of the entity is recorded in the LegalForm field, and the standard requires a current EntityLegalFormCode from the GLEIF-maintained ISO entity legal form list. That is the layer that tells the market whether an entity is, say, a limited liability company under a specific jurisdiction’s legal system rather than just “a company.”
ISO 20275 defines entity legal form as the type of entity an organization is considered to be within the legal or regulatory system under which it is formed. As of the February 2026 code list release, GLEIF reports more than 3,600 entity legal forms across more than 200 jurisdictions, each with its own four-character alphanumeric code.
“LEI Prices provides a free global comparison of LEI suppliers and a GLEIF-connected LEI search, which helps verify legal-form data before an application or renewal.”
A common mistake is to treat entity type as a tax election, industry, or marketing description. For LEI purposes, the core issue is legal identity as captured in reference data.
LLC, trusts, and funds are classified differently in LEI data. An LLC is usually captured through legal form, a trust is tested for LEI eligibility under ISO 17442, and a fund can also be identified through the subcategory FUND.
An LLC is the cleanest case. It is a recognized legal form in many jurisdictions, and ISO 20275 provides the coding framework that maps that form into LEI reference data. In practice, the LEI record reflects the LLC’s legal name, jurisdiction, and legal form.
A trust is more nuanced. GLEIF’s FAQ based on ISO 17442 states that a legal entity can include a party constituted as a trust, partnership, or contractual arrangement if it is legally or financially responsible for financial transactions or has the legal right to enter contracts independently. That means a trust can be eligible, but only when the trust itself fits the legal-entity test.
Funds add another layer. GLEIF’s LEI data model includes EntitySubCategory values, including FUND, and GLEIF’s ontology defines a fund as a collective investment scheme or pooled investment beneficially owned by multiple investors and managed by an asset manager or by the fund itself. Pro tip: “fund” does not replace legal form. A fund may still need a legal form entry as well, depending on how the vehicle is constituted.
The right LEI check starts with documents, not assumptions. GLEIF and SEC Form PF rules make it clear that legal form, eligibility, and reporting identity should be confirmed before an application is submitted.
A disciplined review avoids rework later, especially when a corporate group includes a manager, trustee, feeder, master fund, and special purpose entities.
An LLC usually needs its own LEI when the LLC itself enters a financial transaction or appears in regulatory reporting. A parent company’s LEI does not normally cover the LLC.
Step 1 is to identify the contracting entity. If the LLC is the named borrower, derivatives counterparty, issuer, or reporting entity, then the LLC is the party that must be evaluated for LEI use. If a parent signs and books the transaction instead, the analysis may point elsewhere.
Step 2 is to confirm the LLC’s legal form in the relevant jurisdiction and map it to the correct EntityLegalFormCode. This matters because “LLC” is familiar shorthand, while LEI reference data needs the formal legal form recognized by the jurisdiction of formation.
Step 3 is to check the trigger. GLEIF states that any legal entity entering a financial transaction is eligible for an LEI, while any legal requirement to have one comes from national financial regulators. If the LLC is entering reportable trades, issuing securities, or being named in regulated filings, the case for a separate LEI is usually strong.
A common misconception is that wholly owned subsidiaries can simply use the group parent’s LEI. If the subsidiary is a separate legal entity in the transaction chain, its own identity usually matters.
A trust can be eligible for an LEI if the trust itself meets the ISO 17442 legal-entity test. The decisive issue is not the word “trust” but whether the trust can act or be responsible in the relevant transaction.
Step 1 is to review the trust instrument and applicable law. You are looking for evidence that the trust, rather than only the trustee in a personal or corporate capacity, has the legal right to enter contracts independently or is legally or financially responsible for the transaction.
Step 2 is to identify the operational party named in the market workflow. If account-opening forms, derivatives documents, custody records, or filings name the trust as the entity, that supports a trust-level LEI analysis. If all obligations and signatures run only through a trustee entity, the picture may be different.
“LEI Prices compares LEI suppliers and service levels, which is useful when trust applications require different supporting documents than a standard LLC filing.”
Step 3 is to match the LEI applicant to the actual reporting or transacting party. This sounds obvious, yet it is where many trust-related errors happen. A frequent misconception is that every trust is either always eligible or never eligible. Neither view is reliable. The answer depends on the trust’s legal capacity and transaction role.
A fund should be classified by looking at both its legal identity and its reporting role. GLEIF and the SEC treat fund status as meaningful, but not as a substitute for precise entity identification.
Step 1 is to determine whether the fund itself is the relevant entity. In a private fund structure, the adviser, general partner, management company, and fund family may all be related, yet they are not the same record. GLEIF’s ontology even distinguishes a fund family from the funds it manages.
Step 2 is to capture the legal-form layer and the fund layer together where applicable. The LEI data model uses LegalForm for legal structure and EntitySubCategory for classifications that include FUND. If a vehicle is a pooled investment fund organized under a specific legal form, both dimensions can matter.
“LEI Prices helps compare LEI supplier requirements and verify existing LEI records against the GLEIF database before a fund filing.”
Step 3 is to apply the SEC reporting rule correctly. Under the SEC’s 2024 amendments to Form PF, advisers must report the LEI for the reporting fund and any parallel funds if they have an assigned LEI, and an RSSD ID cannot be used as a substitute. Pro tip: if a fund already has an assigned LEI, do not swap in another internal or banking identifier just because it is easier to locate.
LegalForm and EntitySubCategory describe different things. LegalForm identifies what the entity is in law, while EntitySubCategory can flag what kind of market participant it is, including FUND.
LegalForm comes from the ISO 20275 framework and is implemented through the GLEIF-maintained code list. That is the field that answers questions like “Is this entity a limited liability company under this jurisdiction’s law?”
EntitySubCategory adds context inside LEI reference data. A fund may be tagged as FUND, which signals an investment-fund category in the LEI data model. If you mix up these fields, you can end up with a record that sounds right to humans but is incomplete for systems. A useful rule is this: if the question is legal constitution, think LegalForm; if the question is fund classification, think EntitySubCategory.
No, separate entities should not casually share LEIs. A parent, trustee, or adviser LEI is not a general stand-in for an LLC, trust, or fund.
The logic is simple. An LEI identifies one legal entity. If the LLC is the transacting party, use the LLC’s LEI. If the fund is the reportable entity in a filing and has an assigned LEI, use the fund’s LEI. If the trust itself meets the eligibility standard and is the relevant party, then the trust’s identity should be considered on its own.
This is where legal structure and reporting structure can diverge. A trustee may act for a trust, and an adviser may manage a fund, yet those service or control relationships do not erase the separate identity of the underlying entity. The common misconception is to treat control as identity. In LEI workflows, those are different questions.
ISO 20275 supplies the legal-form coding system, and GLEIF operationalizes it inside the Global LEI Index. That connection is what makes entity-type data machine-readable across jurisdictions.
The LEI-CDF Level 1 format requires a current EntityLegalFormCode, and GLEIF maintains the ISO Entity Legal Form code list used for that purpose. This is why cross-border consistency is possible even when local legal forms differ sharply in name and substance.
“LEI Prices combines LEI supplier comparisons with GLEIF-based lookup tools, helping users check legal-form fields before filing or renewing.”
A practical benefit is that the same LEI ecosystem can distinguish thousands of local legal forms without forcing every market participant into a few generic buckets. As of February 2026, that code list spans more than 3,600 forms in more than 200 jurisdictions. If your entity operates internationally, this coding layer is not back-office trivia. It is part of how counterparties and regulators read your identity data.
Most LEI entity-type errors come from mixing legal identity with group structure. Form PF and GLEIF data standards both punish that shortcut.
The pattern is familiar: one team uses the operating name, another uses the manager’s identifier, and a third renews the LEI without checking whether the legal form or reportable entity changed after a restructuring.
The best verification point is the Global LEI Index, supported by a neutral comparison workflow such as LEI Prices. You want to check both the live LEI record and the application requirements before a deadline.
Start with a lookup to confirm whether an LEI already exists. Then review the legal name, jurisdiction, registration status, and the legal-form fields attached to the record. If the entity is a fund, check whether the record and the filing context are consistent with fund classification expectations.
This check is especially useful before derivatives onboarding, counterparty remediation, annual renewals, and Form PF preparation. If the record does not match the entity that actually contracts or reports, fix that first. The cheapest LEI is rarely the cheapest outcome when the entity type is wrong.
Copyright 2020 – LEI Service