Devancore Inc.
Devancore Post-Trade Glossary
Glossary
FIGI Instrument Identifier
An open 12-character financial instrument identifier used to normalize securities, listings, share classes, and vendor symbols across systems.
Document source: https://devancore.com/glossary/figi-instrument-identifier
On this page
Actions
Devancore Post-Trade Glossary
FIGI Instrument Identifier
An open 12-character financial instrument identifier used to normalize securities, listings, share classes, and vendor symbols across systems.
Definition
What is a FIGI?
FIGI, or Financial Instrument Global Identifier, is an open financial instrument identifier used to map and identify financial instruments across fragmented vendor, venue, and asset-class symbol systems. It is part of the OpenFIGI / Open Symbology framework and is designed to give firms a persistent identifier that can sit across traditional vendor symbols, exchange codes, listings, and internal instrument records.
FIGI is useful because financial markets do not have one universal identifier that solves every operational problem. A security may have an ISIN or CUSIP, a ticker, an exchange code, vendor-specific symbols, a MIC venue context, an issuer LEI, a CFI classification, and multiple internal IDs. FIGI gives the instrument master another stable mapping layer that can help connect those fragments.
The identifier itself is semantically meaningless. The code does not embed issuer, country, asset class, maturity, tax treatment, or settlement terms. The useful information comes from the metadata and relationships attached to the FIGI record.
FIGI identifier levels
Use the right FIGI level for the operating question.
| Field | Meaning | Best use |
|---|---|---|
| figi | Identifier for a specific instrument or listed/traded context | Venue-level mapping, trade enrichment, vendor normalization |
| compositeFIGI | Aggregates related venue-level FIGIs within a country or market context | Country or market-level position aggregation |
| shareClassFIGI | Links share-class exposure across countries and venues where applicable | Issuer share-class linkage and cross-listing analysis |
| marketSector | Broad OpenFIGI sector signal | Initial taxonomy and routing hint |
| securityType | OpenFIGI instrument type label | Mapping seed for instrument master classification |
| ticker / exchCode | Vendor and venue-facing lookup context | Symbol mapping, not primary control |
The practical distinction is between FIGI levels. A venue-level FIGI can identify a specific listed or traded context. A compositeFIGI can aggregate related venue-level FIGIs inside a country or market context. A shareClassFIGI can link the same share-class exposure across countries and venues where applicable. Each level answers a different operational question. Using the wrong level can produce wrong aggregation, wrong reconciliation, or duplicate instrument records.
FIGI versus adjacent identifiers
FIGI is a mapping identifier. It should sit beside legal, venue, and classification identifiers.
| Identifier | Primary role | Why it still matters |
|---|---|---|
| FIGI | Cross-vendor and cross-asset instrument mapping | Reduces duplicate instruments and symbol fragmentation |
| ISIN | Global security identifier | Core for settlement, custody, and regulatory reporting |
| CUSIP | US and Canadian security identifier | Core for North American securities processing |
| MIC | Venue or market segment identifier | Explains where the instrument trades or where activity belongs |
| CFI | Instrument classification | Routes settlement, tax, corporate actions, controls, and reporting |
| LEI | Legal entity identifier | Links issuer, counterparty, venue operator, or reporting party |
FIGI is especially useful for vendor normalization. Tickers are not stable primary keys. The same ticker can exist on different venues. The same instrument can have different vendor symbols. Corporate actions, exchange changes, share-class structures, and cross-listings can all create mapping problems. A well-governed FIGI layer reduces those problems by providing a structured bridge into the instrument master.
The boundary is equally important. FIGI does not replace the legal instrument record. It does not replace prospectus terms, issuer LEI, CFI, MIC, country, currency, tax source evidence, settlement rules, or corporate-action terms. FIGI helps locate and normalize the instrument. It does not prove how the instrument should be taxed, settled, reported, or supervised.
FIGI — identifier levels
Devancore Glossary · devancore.com
How it works
How FIGI works in reference data
FIGI usually enters the workflow during instrument onboarding, vendor symbol mapping, trade enrichment, or reference-data repair. A system receives an input identifier such as ticker, exchange code, ISIN, CUSIP, vendor symbol, or descriptive instrument name. That input is mapped through OpenFIGI or another approved source to retrieve a FIGI and related metadata.
The first control is input quality. A ticker alone is not enough. A ticker should be joined with exchange, country, currency, MIC, or another disambiguating field before mapping. Otherwise the system may retrieve several plausible instruments and create a weak match.
The second control is level selection. If the workflow needs precise execution or listing context, the venue-level FIGI matters. If the workflow needs country or market aggregation, compositeFIGI may be more appropriate. If the workflow needs exposure across cross-listings or share classes, shareClassFIGI may be the better link. The system should not use one FIGI level for every workflow.
The third control is metadata review. OpenFIGI responses can include fields such as FIGI, compositeFIGI, shareClassFIGI, market sector, security type, ticker, exchange code, name, and security description. These fields are useful for mapping and classification, but they should be treated as source metadata, not final legal truth.
FIGI operating risks
FIGI is strong when used precisely. It creates risk when treated as the whole instrument record.
| Risk | Where it appears | Control response |
|---|---|---|
| Wrong FIGI level | Position aggregation and reconciliation | Use venue FIGI, compositeFIGI, or shareClassFIGI based on the workflow |
| Ticker-only matching | Instrument onboarding | Map ticker and exchange context through OpenFIGI or another approved source |
| Duplicate instrument records | Instrument master | Join FIGI with ISIN, CUSIP, MIC, currency, and issuer LEI |
| FIGI treated as legal terms | Tax, reporting, and lifecycle logic | Require CFI, prospectus terms, issuer, country, and source evidence |
| Vendor taxonomy overreach | Asset-class routing | Use securityType and marketSector as mapping seeds, not final truth |
| Digital asset ambiguity | Token and RWA operations | Join FIGI with DTI, contract address, chain ID, issuer, and economic instrument |
The fourth control is joining. FIGI becomes operationally strong when it is joined with ISIN, CUSIP, MIC, CFI, issuer LEI, country, currency, market master data, and source evidence. This joined record can then feed trade enrichment automation, settlement routing, tax review, corporate actions, controls, and reporting.
The fifth control is exception handling. Ambiguous matches, missing FIGIs, stale vendor symbols, conflicting identifiers, and duplicate candidate records should route to reference-data review. The system should preserve the raw input, the mapping result, the confidence level, and the source timestamp so the review trail is auditable.
FIGI is strongest when it is used for what it is: an open mapping identifier inside a controlled reference-data process.
FIGI — normalization workflow
Devancore Glossary · devancore.com
FIGI — normalization workflow
Devancore Glossary · devancore.com
In Devancore™
FIGI in Devancore — mapping inside the instrument record
Devancore Glossary · devancore.com
FIGI in Devancore
Devancore treats FIGI as part of the unified instrument master, not as a standalone answer. The platform can store FIGI, compositeFIGI, and shareClassFIGI alongside ISIN, CUSIP, CFI, MIC, issuer LEI, currency, country, contract address, chain ID, and lifecycle terms.
In instrument onboarding, FIGI helps normalize records that arrive from different systems with different identifiers. A broker file may use ticker and exchange code. A custodian file may use ISIN or CUSIP. A market-data vendor may use its own symbology. A digital-asset source may use contract address and chain ID. Devancore can use FIGI as one bridge into the golden instrument record while preserving every source identifier and its evidence trail.
In trade enrichment, FIGI helps connect incoming trade records to the right instrument. A trade captured with a ticker and venue can be mapped to a FIGI, joined to MIC and currency context, checked against the instrument master, and enriched before settlement, reconciliation, and reporting workflows begin.
In position control, the FIGI level matters. Venue-level FIGIs support precise listing and execution context. compositeFIGI can support country or market aggregation. shareClassFIGI can help reconcile exposure across cross-listings where the same economic share class appears in more than one market context. Devancore keeps these levels separate so aggregation does not destroy evidence.
In tax, compliance, and reporting workflows, FIGI is treated as a mapping input. It can help locate the instrument record, but final routing still depends on CFI, issuer LEI, market master data, country, currency, source tax evidence, documentation, and firm policy. The platform does not infer tax treatment from FIGI alone.
In hybrid and digital-asset operations, FIGI can help connect traditional and newer instrument universes where coverage exists. But tokenized instruments still require on-chain identifiers, chain ID, contract address, token standard, decimal precision, issuer data, and legal terms. Devancore stores those fields beside FIGI so the same economic instrument can be reconciled across traditional and digital rails.
The operating rule is clear: FIGI improves mapping. It does not replace the instrument master.
Related terms
- Instrument Master Data
https://devancore.com/glossary/instrument-master-securities
The authoritative golden record of reference data — identifiers, static attributes, and lifecycle parameters — for every instrument a firm can trade, settle, or report.
- Reference Data Management
https://devancore.com/glossary/reference-data-management
The governance and maintenance of static data that financial systems depend on — instrument identifiers, counterparty LEIs, and settlement rules — to process transactions correctly.
- Securities Identifiers ISIN and CUSIP
https://devancore.com/glossary/securities-identifier-isin-cusip
ISIN and CUSIP are the alphanumeric codes that uniquely identify financial instruments — referenced in almost every trade capture, matching, settlement instruction, and regulatory report.
- Market Identifier Code (MIC)
https://devancore.com/glossary/market-identifier-code-mic
The ISO 10383 four-character code that identifies trading venues, operating markets, and market segments for enrichment, reporting, and post-trade routing.
- Classification of Financial Instruments (CFI)
https://devancore.com/glossary/classification-of-financial-instruments-cfi
The ISO 10962 six-character code that classifies an instrument’s type and attributes for settlement, tax, corporate actions, controls, and reporting.
- Legal Entity Identifier (LEI)
https://devancore.com/glossary/legal-entity-identifier
20-character alphanumeric code under ISO 17442 that uniquely identifies legal entities in financial transactions, required for MiFID II, EMIR, and CAT regulatory reporting, and the primary party identifier in ISO 20022 sese.023 settlement instructions.
- Market Master Data
https://devancore.com/glossary/market-master-data
The authoritative reference layer for countries, currencies, venues, CSDs, settlement rules, tax signals, sanctions evidence, and market infrastructure.
- Trade Enrichment Automation
https://devancore.com/glossary/trade-enrichment-automation
The automated augmentation of a raw trade capture with settlement instructions, counterparty identifiers, and regulatory fields required for clearing and settlement.
- Trade Reconciliation
https://devancore.com/glossary/trade-reconciliation
The systematic comparison of internal trade and position records against external sources to identify breaks and resolve them before they become settlement failures.
- Securities Master Data
https://devancore.com/glossary/securities-master-data
The operational discipline of maintaining a firm's golden copy — the single authoritative securities reference record kept current through daily vendor scrubbing, conflict resolution, and event-driven lifecycle enrichment.
- Digital Token Identifier (DTI)
https://devancore.com/glossary/digital-token-identifier
A globally unique identifier under ISO 24165 that fingerprints a digital token by blockchain network, smart contract address, and genesis parameters.
- System of Record Securities Operations
https://devancore.com/glossary/system-of-record-securities-operations
The authoritative single source of truth for a firm's positions, trades, and accounts — the system of record that all other systems, reports, and compliance functions derive from.
Contact
Request a briefing or platform walkthrough with the Devancore team.
Request access https://devancore.com/access