Devancore Inc.
Devancore Post-Trade Glossary
Glossary
Instrument Master Data Quality
Instrument master data quality is the control on whether an instrument record may be used: identifiers, terms, classification, and settlement attributes are complete, consistent, timely, and evidenced before post-trade consumes them.
Document source: https://devancore.com/glossary/instrument-master-data-quality/
Devancore Post-Trade Glossary
Instrument Master Data Quality
Instrument master data quality is the control on whether an instrument record may be used: identifiers, terms, classification, and settlement attributes are complete, consistent, timely, and evidenced before post-trade consumes them.
Definition
Instrument master data quality is the control that decides whether an instrument record may be used. The master holds identifiers, economic terms, classification, issuer, venue, and settlement attributes. Quality tests those fields for completeness, uniqueness, consistency, timeliness, and fitness for a named consumer. If the test is missing, settlement, tax, corporate actions, reporting, and position aggregation inherit a quiet error.
The instrument master is the repository. Securities master operations keep that repository current. Instrument master data quality is the gate: which fields must be present, which maps must be unique, which overrides need an approver, and which workflow is blocked until the record is fit.
Quality tests the instrument record must pass
Quality tests the instrument record must pass
A complete identifier set can still be unfit for tax, corporate actions, or aggregation.
| Quality test | What it checks | Break if it fails |
|---|---|---|
| Completeness | Required fields for the next workflow: identifiers, PSET or CSD eligibility, day count, decimals | Instruct or accrual runs on a blank that operations later calls a fail |
| Uniqueness | One economic instrument, not two masters for the same ISIN, listing, or token | Positions split; risk and custody recon cannot join |
| Mapping | ISIN, CUSIP, FIGI, DTI, and listing line point at the same instrument at the right FIGI level | Venue line aggregated as share class, or token and security treated as two assets |
| Consistency | CFI, coupon, maturity, currency, and issuer LEI agree with each other | Reporting classifies debt while the books accrue equity-style events |
| Timeliness | Factors, ex-dates, maturity changes, and identifier replacements as-of the event | Entitlement, tax lot, or settlement uses yesterday's terms |
| Evidence | Source, override, approver, and the version stamped on the consumer | A corrected coupon cannot explain which NAV or instruction used the old value |
Downstream breaks cluster by use. Settlement fails when the identifier map, depository eligibility, or place of settlement is wrong. Tax processing fails when withholding or issuance attributes are blank or stale. Corporate actions fail when terms, ratios, or old-to-new identifiers are not as-of the event. Regulatory reporting fails when CFI, issuer LEI, or MIC is missing or inconsistent with the terms. Aggregation fails when a listing FIGI, a share-class FIGI, and an ISIN are treated as the same grain.
Identifier quality is a map, not a single code. ISIN and CUSIP identify the security for custody and settlement. FIGI can pin a listing, a composite, or a share class. DTI and contract address identify the token. A quality rule that stores all of them without checking that they join one economic instrument still splits positions. A quality rule that collapses every FIGI level into one quantity still mis-aggregates listings as share class.
Classification quality is consistency with terms. CFI says what the instrument is. Coupon, maturity, optionality, and currency say how it behaves. When those disagree, reporting and servicing follow the wrong playbook. Issuer LEI and MIC are links, not decorations: they are how tax, concentration, and venue reporting join the record to a person and a market.
Timeliness is as-of, not last-file-wins. Pool factors, ex-dates, called maturities, and identifier replacements have event time. A correct coupon entered tomorrow does not explain yesterday's accrual. Token decimal precision and dual-key links for tokenized securities are the same class of test: if they are wrong, quantity and cash are wrong by construction.
Instrument master data quality — record to consumer gate
Devancore Glossary · devancore.com
Instrument master data quality — record to consumer gate
Devancore Glossary · devancore.com
How it works
Quality works as a gate in front of each consumer. Profile the use. Validate identity, terms, and links. Open an exception or release the record. Stamp the version the workflow actually used.
Quality gates before a consumer may use the record
Quality gates before a consumer may use the record
Fitness is per workflow. Passing settlement completeness does not pass tax or reporting.
| Step | Data required | Failure mode |
|---|---|---|
| Profile the use | Whether the consumer is instruct, tax, corporate action, report, or aggregation | One generic score is applied to every downstream job |
| Validate identity | ISIN, CUSIP, FIGI level, DTI or contract address, and duplicate-key scan | Two records share one ISIN, or FIGI listing is rolled into share-class quantity |
| Validate terms | Coupon, day count, maturity, factor, currency, decimals, CFI versus terms | Bond accrual uses a missing day count; a token posts off by token decimals |
| Validate links | Issuer LEI, MIC, CSD eligibility, old-to-new identifier after an event | CA applied to the wrong line; report files without issuer LEI |
| Exception | Owner, reason, blocked consumer, and aging | A known bad CFI still enriches the regulatory file |
| Release evidence | Rule version, source, approver, as-of, and consumer stamp | Operations cannot show which master version settlement used |
Sources include vendor reference files, numbering agencies, OpenFIGI maps, DTI registries, issuer and agent notices, CSD eligibility lists, and internal overrides. Normalization is not the quality control. Normalization produces a candidate row. Quality is the set of tests that row must pass for a named use.
Completeness is per workflow. Instruct may require ISIN or CUSIP, PSET or CSD eligibility, and currency. Accrual may require day count, coupon, and factor. Reporting may require CFI, issuer LEI, and MIC. A dashboard that scores "percent complete" across all fields still releases a bond into settlement with no depository eligibility.
Uniqueness and mapping are where FIGI earns its keep in operations. Duplicate masters for one ISIN split custody recon. Mapping a venue FIGI to share-class quantity inflates or hides exposure. Mapping a DTI to the wrong ISIN breaks the dual-key join for a tokenized line. Identifier mapping is a quality rule with an owner, not a nightly spreadsheet.
Exceptions need a blocked consumer. If CFI is unknown, reporting should not silently guess. If maturity was overridden, accrual should carry the approver. If a corporate-action identifier replacement is unconfirmed, entitlement should wait. Data quality management that only ranks records still lets the bottom rank instruct.
Evidence is the version stamp. Lineage shows which file supplied the day count. Approval shows who overrode it. The consumer stamp shows which test result settlement, tax, or the report actually used. Conversational queries are useful only after those are records: which instruments failed uniqueness this week, which CFI-term mismatches still enrich reporting, which overrides lack an approver, which listing FIGIs were aggregated as share class.
Instrument quality — release, exception, or block
Devancore Glossary · devancore.com
Instrument quality — release, exception, or block
Devancore Glossary · devancore.com
In Devancore™
Devancore — instrument quality evidence chain
Devancore · evidence stack
Master row
Identifiers, terms, classification, and settlement attributes enter with source, as-of, and version.
Quality tests
Completeness, uniqueness, mapping, CFI consistency, and timeliness remain named results, not a single score.
Fitness by use
Instruct, tax, corporate action, report, and aggregation each carry a pass, fail, or blocked state.
Exception state
Owner, reason, override, and aging stay on the record that failed the test.
Consumer stamp
The version and test result used by settlement, NAV, or reporting remain replayable.
Devancore supports instrument master data quality as a post-trade operating-record layer around tests, exceptions, fitness by consumer, and the version a workflow stamped. It can help teams keep identifier maps, CFI consistency, settlement attributes, and override evidence attached to instruct, servicing, and reporting events.
Devancore does not act as a numbering agency, FIGI issuer, tax authority, CSD, or official instrument master utility. It does not certify ISIN, CUSIP, CFI, or DTI values, and it does not replace the firm's data owners. The product boundary is the controlled operating copy of quality state that post-trade already depends on.
In a Devancore-style workflow, a master change, map break, CFI mismatch, factor update, override, or consumer stamp enters as a source event. The record is mapped to instrument, test, consumer, owner, and workflow state. Passed, failed, blocked, overridden, or stamped remains visible with actor, timestamp, reason, and source reference.
That structure is what operations actually uses. The vendor file may be complete. The master may have an ISIN. The operating question is whether the record was fit for the workflow that just failed.
Conversational finance depends on the same chain. A user can ask which instruments are blocked for instruct, which FIGI listing maps break share-class aggregation, which CFI values disagree with coupon terms, or which tax attributes changed without an approver. The answer should resolve to tests, owners, consumers, versions, and evidence.
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.
- 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.
- FIGI Instrument Identifier
https://devancore.com/glossary/figi-instrument-identifier/
An open 12-character financial instrument identifier used to normalize securities, listings, share classes, and vendor symbols across systems.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Corporate Action Processing
https://devancore.com/glossary/corporate-action-processing/
Corporate action processing is the operational workflow that captures issuer events, calculates per-account entitlements, and reconciles cash and position changes against custodian records.
- Bond Accrual Accounting
https://devancore.com/glossary/bond-accrual-accounting/
Bond accrual accounting is the controlled workflow that connects coupon accruals, clean-to-dirty price math, settlement cash, premium or discount treatment, and accounting records.
- Custody Reconciliation
https://devancore.com/glossary/custody-reconciliation/
Custody reconciliation is the daily match of internal positions and cash to the custodian statement: timing versus genuine breaks, owners, aging, and the evidence that holdings are actually safekept.
Contact
Request a briefing or platform walkthrough with the Devancore team.
Request access https://devancore.com/access/