Instrument reference data is the set of descriptive facts about a financial instrument that systems need in order to trade, settle, value and report it. It says what the instrument is, who issued it, how it is identified, and what its terms are: for a bond, the coupon, payment dates and maturity; for a share, the class, currency and listing venues; for a derivative, the underlying asset, expiry and contract size. It changes rarely compared with prices and positions, and is sometimes called security static data.
Every stage of a transaction depends on it. An order is routed using an identifier and a venue code; a trade is confirmed and settled using the same identifier, currency and settlement place; interest is accrued using the instrument's day count and coupon schedule; and regulators receive reports keyed to it. Firms store it in a security master file, and it is one of the main domains covered by reference data governance.
Main data elements
- Identifiers. The ISIN is the global standard. National and proprietary codes are used alongside it, including CUSIP in North America, SEDOL in the United Kingdom and the FIGI, together with exchange tickers.
- Descriptive attributes. These include the instrument's name and standard short name, issuer, currency, country, denomination and form.
- Classification. Codes describing the type of instrument, such as the CFI code under an ISO standard, and the firm's own security classification and asset class classification.
- Terms and schedules. For debt, these are the coupon rate and type, coupon schedule, day count convention, maturity, call and put features and redemption terms. For derivatives, they are the underlying, strike, expiry and settlement method.
- Market and settlement data. Listing venues, identified by market identifier codes, trading currency, lot size, tick size, settlement cycle and place of safekeeping.
- Links to other data. The issuer and its legal entity identifier, guarantors, ratings and related instruments, which connect to issuer reference data.
Where the data comes from
The original source is the issuer's documentation: the prospectus, final terms or term sheet. Identifiers are assigned by national numbering agencies, exchanges publish listing details, and depositories hold settlement attributes. Few firms collect all of this directly. Most buy consolidated feeds from data vendors, which gather, normalise and distribute it, and supplement those feeds with records created in-house for private or newly issued instruments.
Because vendors differ in coverage, timing and interpretation, large firms take more than one feed and compare them to produce a single approved record, the approach described under golden source data. Changes to an instrument during its life, such as a name change, a coupon reset or a redemption, arrive through a corporate action data feed and must be reflected in the master record.
Regulatory uses
Regulation has increased the importance of consistent instrument data. Under MiFID II and its accompanying regulation, trading venues and certain dealers in the European Union submit reference data for instruments admitted to trading, which the European Securities and Markets Authority publishes in a central database. Firms use it to determine whether a trade must be reported, and transaction reports identify instruments by ISIN. To make this possible for over-the-counter derivatives, a utility set up by the association of numbering agencies began issuing ISINs for those contracts in 2017, and it now also issues the unique product identifier used in global derivatives reporting. Similar dependencies exist in rules on market abuse surveillance, short selling, fund reporting and bank capital.
Operational importance
Errors and gaps in instrument data are a leading cause of exceptions in post-trade processing. A wrong settlement place or currency causes a mismatch with the counterparty; a wrong coupon date causes an incorrect accrual and a break against the custodian; a missing instrument stops a trade from booking at all. Such problems feed directly into settlement fail management and manual repair. Under shorter settlement cycles there is less time to correct them, so instruments must be set up accurately before or immediately after the first trade.
Data operations teams therefore monitor new issues, set up instruments on request from the front office, review vendor exceptions and maintain audit trails of every change. Quality is measured by completeness, accuracy and timeliness, and by the rate of downstream breaks traced to reference data.
Persistent problems
There is no single global source that is complete and free. Identifiers overlap and some are subject to licence fees, which has been a long-running point of dispute between users and code owners. One instrument may carry several identifiers, and one identifier may cover lines trading on many venues, so mapping tables are needed. Complex and bespoke instruments do not fit standard fields. Data for private assets, loans and newer instruments such as tokenised securities is less standardised still. Industry initiatives have promoted open identifiers, common data models and standard digital formats for bond terms, but adoption is uneven, and most firms continue to spend heavily on cleansing data that their competitors are cleansing too.