Devancore Inc.
Devancore Post-Trade Glossary
Glossary
Market Master Data
The authoritative reference layer for countries, currencies, venues, CSDs, settlement rules, tax signals, sanctions evidence, and market infrastructure.
Document source: https://devancore.com/glossary/market-master-data
On this page
Actions
Devancore Post-Trade Glossary
Market Master Data
The authoritative reference layer for countries, currencies, venues, CSDs, settlement rules, tax signals, sanctions evidence, and market infrastructure.
Definition
What is market master data?
Market master data is the authoritative reference layer that describes each market a firm can trade, settle, clear, report, or monitor. It is not price data. It is not a chart feed. It is the controlled operating record for market identity and market obligations.
A complete market master connects country identity, currency, venue codes, market infrastructure, tax signals, sanctions-screening evidence, and source lineage. It answers practical questions that every post-trade system eventually needs to answer: what country is this market in, what currency does it use, which MIC identifies the venue, which CSD or settlement infrastructure supports the instrument, what settlement convention applies, what tax evidence may be required, and what control flags should be reviewed before the workflow is treated as complete?
Market master data sits beside instrument master data and reference data management. The instrument master describes what the firm trades. The market master describes where the trade belongs and which market-specific rules, infrastructures, and evidence requirements attach to it. The two records must work together. A security can have a valid ISIN and still fail operationally if the venue, currency, CSD, settlement calendar, or jurisdictional profile is wrong.
Market master data domains
The record connects market identity, infrastructure, and obligations into one controlled reference layer.
| Domain | Examples | Operational use |
|---|---|---|
| Country identity | ISO 3166 country code, region, jurisdiction | Country exposure, reporting scope, sanctions context |
| Currency | ISO 4217 currency code, numeric code, minor units | Cash movement, rounding, settlement amount validation |
| Venue identity | ISO 10383 MIC, operating MIC, segment MIC | Trade enrichment, venue reporting, routing logic |
| Market infrastructure | CSDs, clearing systems, payment rails | Settlement route, finality model, operating calendar |
| Tax profile | Domestic withholding, treaty ceilings, transaction taxes | Dividend processing, tax evidence, investor reporting |
| Sanctions evidence | OFAC, BIS, State, CSL screening signals | Control review, jurisdictional monitoring, escalation |
| Source evidence | Source URL, retrieved date, raw field, review status | Audit trail, refresh control, data lineage |
In traditional securities operations, market master data supports venue enrichment, settlement instruction generation, regulatory reporting, dividend processing, and reconciliation. In digital and hybrid settlement environments, the same concept becomes more important. A tokenized instrument may have on-chain settlement attributes, but the underlying economic exposure may still point to a country, currency, issuer jurisdiction, CSD record, tax profile, and regulatory reporting context. The rail changes. The market obligations do not disappear.
Market master data also creates the control boundary between source evidence and final decisioning. A market profile can store domestic withholding tax signals, treaty-rate references, sanctions-screening flags, and retrieved source dates. It should not pretend to be legal or tax advice. The purpose is to give operational systems a governed, auditable, reviewable reference layer so that tax, compliance, finance, and operations teams can make decisions from the same evidence base.
The quality standard is simple: every material market attribute should have a source, a retrieved date, a review status, and a lineage trail. Without that, the record may still be useful for exploration, but it is not yet strong enough to drive regulated operations.
Market master data — governed reference structure
Devancore Glossary · devancore.com
How it works
How market master data works
Market master data begins with source intake. Country identity may come from ISO 3166. Currency identity may come from ISO 4217. Venue identity may come from ISO 10383 MIC data. Market infrastructure may come from CSD references, exchange materials, regulator publications, and operational source files. Tax signals may come from public tax profiles, treaty sources, and reviewed internal tax guidance. Sanctions signals may come from screening-list sources and jurisdictional control reviews.
The first control is normalization. A market record should not treat country names, venue names, and currency labels as free text. The controlled fields should map to identifiers: country code, currency code, MIC, operating MIC, segment MIC, legal entity identifier where relevant, and source-specific IDs where available. Free text can describe the source, but it should not be the primary key.
The second control is enrichment. A country or venue record becomes operationally useful only when it is linked to the infrastructure and obligations that matter downstream: settlement systems, CSD relationships, payment rails, holiday calendars, market-specific settlement conventions, domestic withholding profiles, treaty-rate evidence, securities transaction tax signals, and sanctions-screening flags.
The third control is review status. Not every source has the same reliability. A raw scraped source, a public tax table, a treaty-rate extract, a vendor feed, and a reviewed internal operating rule should not carry the same operational status. Market master data needs to distinguish raw source data, normalized source data, reviewed operating data, and approved production data.
Market master data failure modes
Most failures do not look like market data problems when they first appear.
| Bad or missing field | Where it surfaces | Likely impact |
|---|---|---|
| Incorrect MIC | Trade enrichment and reporting | Wrong venue record, rejected report, broken audit trail |
| Wrong currency minor unit | Cash and settlement amount validation | Rounding error, failed payment, reconciliation break |
| Missing CSD linkage | Settlement instruction generation | Wrong route, manual repair, preventable settlement fail |
| Stale tax profile | Dividend and income processing | Incorrect withholding assumption or missing review flag |
| Unreviewed treaty rate | Tax operations and investor reporting | Overstated entitlement or unsupported reduction claim |
| Weak sanctions source evidence | Compliance controls | Poor escalation record and incomplete examination package |
The fourth control is effective dating. Market rules change. Settlement cycles compress. Venues open, close, merge, or change segment structures. Tax rates and treaty positions change. Sanctions lists update. A market master record should preserve prior versions so the firm can reconstruct what the system knew when a trade was booked, settled, reported, or reviewed.
The final control is distribution. Downstream systems should not re-interpret market sources independently. The trade enrichment engine, settlement instruction workflow, corporate action processing workflow, dividend tax workflow, sanctions control, and reporting engine should consume the same governed market profile. If each system maintains its own country, venue, tax, and sanctions logic, the firm has created hidden reconciliation problems before any trade is booked.
Market master data is therefore an operating control. It reduces ambiguity before the transaction enters the post-trade lifecycle.
Market master data — control lifecycle
Devancore Glossary · devancore.com
Market master data — control lifecycle
Devancore Glossary · devancore.com
In Devancore™
Devancore market intelligence layer
Devancore Glossary · devancore.com
Market master data in Devancore
Devancore treats market master data as part of the institutional reference-data foundation, not as a side spreadsheet. The market profile connects countries, currencies, venues, CSDs, settlement conventions, tax signals, sanctions evidence, and source lineage into one governed record that downstream workflows can consume.
In trade capture and enrichment, the market profile helps stamp each transaction with the correct country, currency, venue, MIC, settlement context, and control attributes. That gives the trade lifecycle management layer the market context it needs before matching, settlement, reconciliation, finance, or reporting processes begin.
In settlement operations, the market profile supports routing and validation. A workflow can distinguish the trading venue from the settlement location, the operating MIC from a segment MIC, and the instrument's country exposure from the cash currency used for settlement. That distinction matters when a firm operates across traditional CSD settlement, bank cash rails, and digital settlement rails.
In income and tax operations, the market profile gives dividend, coupon, and fund-distribution workflows a source-backed starting point. Devancore can store domestic withholding signals, treaty-rate evidence, securities transaction tax indicators, and review status, while preserving the boundary that final tax treatment depends on eligibility, documentation, legal analysis, and firm policy. The system provides evidence and control structure. It does not replace tax judgment.
In compliance and supervision workflows, the market profile can carry sanctions-screening evidence, jurisdictional flags, source dates, and escalation status. That makes market controls explainable. A reviewer can see which source was used, when it was retrieved, whether the record was reviewed, and which downstream workflow consumed it.
In finance and reporting, the same market profile supports country exposure, currency exposure, IBOR and ABOR classification, net capital inputs, tax operations, and audit evidence. This is where market master data becomes more than static data. It becomes the connective tissue between accounting book of record, position control, regulatory reporting, and operational supervision.
Devancore's approach is deliberately conservative: preserve source evidence, separate raw data from reviewed operating data, apply effective dating, and expose review status. That lets a firm use market intelligence to improve automation without pretending that every public source is production-ready on arrival.
Related terms
- 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.
- 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.
- 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.
- 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.
- CSD Reference Data
https://devancore.com/glossary/csd-reference-data
The governed reference layer for CSD identity, market coverage, participants, settlement calendars, eligible securities, notices, and source evidence.
- 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.
- 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.
- Standing Settlement Instructions
https://devancore.com/glossary/standing-settlement-instructions
Pre-agreed instructions specifying how a counterparty's securities and cash should be delivered or received, applied automatically to every qualifying trade.
- Settlement Finality Securities
https://devancore.com/glossary/settlement-finality-securities
The irrevocable transfer of legal ownership in a securities transaction — achieved through deterministic, conditional, or probabilistic finality depending on the settlement rail.
- Central Securities Depository (CSD)
https://devancore.com/glossary/central-securities-depository
The financial market infrastructure that holds securities in book-entry form and executes DvP settlement finality — the legal transfer of ownership that converts a CCP's netted instruction into a confirmed change in beneficial ownership.
- ISO 20022 Securities Settlement
https://devancore.com/glossary/iso-20022-securities-settlement
International financial messaging standard where sese.023 settlement instructions and sese.025 confirmations replace legacy SWIFT MT54x messages, enabling richer settlement data, STP, and interoperability across global custodians and CSDs.
- 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.
- 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.
- Dividend Processing Operations
https://devancore.com/glossary/dividend-processing-operations
The ops function that turns a dividend announcement into a closed income entry — covering ex-date entitlement, payable-date receipt, rate-vs-amount reconciliation, tax withholding, and failed-trade claims.
- Counterparty Risk Management
https://devancore.com/glossary/counterparty-risk-management
The identification and control of risk that a counterparty fails to settle a trade, exposing the surviving party to replacement cost or principal loss.
- AML Transaction Monitoring
https://devancore.com/glossary/aml-transaction-monitoring
Monitoring systems and procedures used by broker-dealers to detect suspicious activity under the Bank Secrecy Act and FINRA Rule 3310, with SAR filing to FinCEN as the required reporting output.
- Accounting Book of Record
https://devancore.com/glossary/accounting-book-of-record
The ABOR: custodian-confirmed settled positions used as the authoritative basis for NAV calculation, financial statements, and regulatory reporting.
Contact
Request a briefing or platform walkthrough with the Devancore team.
Request access https://devancore.com/access