LEI, ISIN, FIGI and MIC: identifying the entity, instrument and venue
A financial identifier names an object within a specified identification scheme, such as a legal entity, an instrument or a market. Matching an identifier resolves only the object and relationship covered by that scheme and mapping.
What each identifier names
Each identifier names one kind of object within one scheme. The scheme sets the object, the format and the route by which a code is assigned.
| Identifier | Names | Format | Assigned by |
|---|---|---|---|
| LEI | A legal entity; each LEI represents only one entity | 20 characters under ISO 17442: 4-character issuer prefix, 14-character entity identifier, 2 check digits | LEI issuers, also called Local Operating Units |
| ISIN | A financial instrument | 12 characters under ISO 6166: 2-character prefix, 9-character local code, 1 check digit | National Numbering Agencies; DSB for OTC derivatives |
| CUSIP | Issuers and their instruments in the US and Canada | 9 characters: the first 6 identify the issuer, the ninth is a check character | CUSIP Global Services |
| SEDOL | An instrument in one country, representing its place of listing or, without a listing, its place of trade | 7 characters: the seventh is a check digit | LSEG |
| FIGI | An individual instrument, in any asset class; records can sit at trading-venue level | 12 characters: 2-character provider code, the letter G, 8 random characters, 1 check digit | Certified Providers, under an Object Management Group standard |
| Composite FIGI | A link across venue-level FIGIs within one country or market | FIGI format | Certified Providers |
| Share Class FIGI | A link across Composite FIGIs for an instrument traded in more than one country | FIGI format | Certified Providers |
| MIC | An exchange, trading platform, market or trade reporting facility | 4 characters, [A-Z0-9]{4} | ISO 10383 Registration Authority, operated by SWIFT |
A check digit detects mistyped codes. It says nothing about whether the named object exists, whether the record is current or whether the identifier fits the use.
Entities, instruments and markets
A Legal Entity Identifier, or LEI, identifies a legal entity. The Global LEI Index contains historical and current entity records and reference data. Parent-relationship information adds another relationship; it does not make an entity identifier a security identifier.
An International Securities Identification Number, or ISIN, identifies a financial instrument within its framework. A Financial Instrument Global Identifier, or FIGI, supports instrument identification and mapping. OpenFIGI maps FIGIs and other market identifiers; the mapping’s instrument and listing context still matters.
A Market Identifier Code, or MIC, identifies a market within the ISO 10383 framework. An instrument match does not select the venue on which an order should execute.
Take one issuer with two securities, one of which trades on two venues. The issuer identity alone selects neither the security nor its execution venue. Adding a security identifier resolves another object, but the intended route still needs a venue and the relevant trading context.
One stock through every identifier
IBM common stock shows how the identifiers divide the work. The values below were checked on 5 November 2026 and describe that date.
The ISIN is US4592001014. Positions 3 to 11 are the CUSIP, 459200101, and the final 4 is the check digit. Sending that ISIN to OpenFIGI without a filter returns 217 FIGI records, all common stock, across 86 exchange codes and 97 Composite FIGIs. All 217 share one Share Class FIGI, BBG001S5S399. The CUSIP returns the same 217 records. An instrument identifier therefore did not select a listing in this case; a filter did.
| Question | Identifier used | Value | What it does not settle |
|---|---|---|---|
| Which legal entity is the issuer? | LEI | VGRQXHF3J8VDLUA7XE92 | The security or the venue |
| Which instrument is the common stock? | ISIN | US4592001014 | The venue or the FIGI record intended |
| What links the records across countries? | Share Class FIGI | BBG001S5S399 | A particular listing |
| Which record is the US composite? | ISIN with exchCode US | BBG000BLNNH6 | A specific venue |
| Which record is the NYSE listing? | ISIN with micCode XNYS | BBG000BLNQ16 | Where an order should route |
| Which legal entity owns that venue? | LEI in the XNYS record | 5493000F4ZO33MV32P92 | The issuer of the instrument |
The first and last rows both hold an LEI, and they name different companies. The issuer LEI belongs to International Business Machines Corporation. The LEI on the XNYS record belongs to Intercontinental Exchange, Inc. A record holding “the LEI” for a trade needs to state which role that entity plays.
Operating MICs and segment MICs
Every ISO 10383 record has an operating MIC and a type, OPRT or SGMT. A segment MIC is a section of an exchange, market or trade reporting facility that specialises in specific instruments or is regulated differently.
XNAS is the operating MIC for Nasdaq, and XNGS is a segment MIC for the Nasdaq Global Select Market. XNYS is the operating MIC for the New York Stock Exchange, and ARCX is a segment MIC for NYSE Arca whose operating MIC is XNYS.
XNGS and XNAS do not match as strings, although one is a segment of the other. A system comparing venues must decide whether it stores the operating MIC, the segment MIC or both, and must compare at one stated level.
An OpenFIGI exchCode is not a MIC. The two are separate request filters that cannot be combined. In the IBM example, the filter micCode XNYS returns a record whose exchCode is UN.
Identifier mappings in order routing
A routing instruction combines instrument identity with other information, including destination and permitted order behavior. If two applications exchange only a display symbol, the receiving application needs enough context to determine the intended instrument.
An identifier map therefore carries the scheme, mapped object, source and effective date. An ambiguous result needs an explicit resolution rule. Silently selecting one result turns a data ambiguity into an operational decision.
Mapping success is also narrower than trade authorization. Identifying the intended instrument does not establish the requester’s permission to trade it or the account’s available allowance.
Mapping limits in OpenFIGI
One mapping job can return many records, as the IBM ISIN does. A pipeline needs a filter that narrows the query or an explicit rule for choosing among results. A job also carries a warning when no FIGI is found, which a pipeline should record as an empty mapping rather than a match.
As documented on 5 November 2026, the Mapping API allows 25 requests per minute and 10 jobs per request without a key, and 250 requests per minute and 100 jobs per request with one. A job returns at most 15,000 results and carries an error when it would exceed that. A 429 response includes a retry-after header giving the wait before retrying. OpenFIGI’s overview describes the API as free without daily, weekly or monthly limits. The per-minute, per-request and per-job limits still apply, so a bulk security-master load has to be paced.
Counterparty identity and historical relationships
A counterparty to a trade is a legal entity recorded in the transaction relationship. It need not be the issuer of the instrument being traded. Using issuer identity as the counterparty aggregation key would combine different economic relationships.
Historical analysis needs the mapping effective for the relevant time. A present-day parent relationship or instrument mapping cannot silently replace an earlier relationship in a historical record. Corporate actions and reference-data corrections require versioned mappings.
What an identifier does over time
Persistence rules differ by scheme, so a stored code has to be read under the rules of its scheme.
An ISIN can become inactive or be replaced after a corporate action. Under ANNA’s guidelines, the ISINs of absorbed companies’ shares become inactive after a certain period following a merger by absorption. A merger by amalgamation allocates a new ISIN for the new company’s stock, and the former ones become inactive. On a change of domicile, the numbering agency in the new domicile weighs the corporate action, local practice and fungibility to decide whether a new ISIN is required. The guidelines say ISINs should never be re-used, and also record an Australian warrant practice in which re-use can occur after at least 45 business days.
OpenFIGI states that a FIGI never changes throughout the trade lifecycle. If the instrument ceases to exist, the FIGI is retired and never reused, but remains accessible. The code itself carries no information about the instrument, so its meaning comes entirely from the reference record.
An LEI is renewed annually. If an entity misses the renewal date and then its issuer’s grace period, the registration status becomes lapsed. GLEIF states that a lapsed LEI remains valid: the code still identifies the entity, while the reference data behind it is behind schedule for re-validation.
The MIC list is published on the second Monday of each month, and modifications become effective on the fourth Monday. Publication and effect are therefore different dates. A record’s status is active, updated or expired, and an expiry date is populated when a MIC is deactivated.
A mapping table therefore stores the identifier, its scheme and level, the mapped object, the source, the effective date and the status at that date.
Scope of identifier evidence
An identifier establishes identity within its documented object and scheme. It does not independently establish beneficial ownership, account entitlement or enforceable netting.
What changes among identifiers is the object named and the mapping context. Typed fields, effective dates and provenance preserve those distinctions when orders, holdings and exposures cross application boundaries.
Questions about LEI
Does an LEI identify a security?
No. An LEI identifies a legal entity.
Does an instrument match identify the counterparty to a trade?
No. The counterparty is a separate legal entity and relationship in the trade record.
Does an ISIN identify the trading venue?
No. An ISIN identifies a financial instrument, and a MIC identifies a market or a section of one.
Is a CUSIP part of an ISIN?
In an ISIN assigned by CUSIP Global Services, yes. The CUSIP or CINS identifier always appears in positions 3 to 11.
Does a FIGI replace an ISIN?
No. They are separate schemes, and OpenFIGI maps between them. One ISIN can map to many FIGI records.
Is a lapsed LEI still valid?
Yes. GLEIF states that a lapsed LEI remains valid. The status means renewal and re-validation of its reference data are behind schedule.
Sources and method
- LEI Data: Access & Use Global Legal Entity Identifier Foundation
- OpenFIGI API Overview OpenFIGI / Bloomberg
- About CGS Identifiers CUSIP Global Services
- Market Identifier Codes ISO 10383 Registration Authority / SWIFT
- Corporate Actions Data LSEG
- The Legal Entity Identifier (LEI) Global Legal Entity Identifier Foundation
- The Legal Entity Identifier (LEI): Questions and Answers Global Legal Entity Identifier Foundation
- Data Quality and Risk Management: The Importance of Timely Renewal of Legal Entity Identifiers Global Legal Entity Identifier Foundation
- LEI record VGRQXHF3J8VDLUA7XE92 Global Legal Entity Identifier Foundation
- Identifiers Association of National Numbering Agencies
- ISIN Uniform Guidelines 2026 Association of National Numbering Agencies
- SEDOL Masterfile Service & Technical Guide v8.8 LSEG
- FIGI Overview OpenFIGI / Bloomberg
- OpenFIGI API Documentation OpenFIGI / Bloomberg
- ISO 10383 Market Identifier Codes, Release 2.0 Factsheet ISO 10383 Registration Authority / SWIFT
- ISO 10383 MIC list (CSV) ISO 10383 Registration Authority / SWIFT
Read next
- What does a market-data API actually give you?
A market-data endpoint does not define your coverage or rights. Understand feeds, timing, entitlements and the limits of API access.
- KYC, AML and sanctions screening answer different questions
Customer identity, suspicious activity and sanctions restrictions need different controls. Follow the handoffs between KYC, AML and screening.
- Counterparty exposure: from trades to netting sets and collateral
Trade values become counterparty exposure through agreement scope, netting and collateral. Follow the calculation boundaries.
