Definitions
In plain terms
It is the lookup layer that answers which instrument a market record refers to, even when names or tickers have changed.
Technical
A reliable security master maintains source provenance, bitemporal or effective-dated history, typed identifier crosswalks, relationship cardinality, and non-destructive revisions.
Scope
A security master is a system and data contract, not a single universal vendor file.
Examples
- A governed dataset records security master explicitly instead of inferring it from an ambiguous field.
Common misconceptions
- Security Master does not have one universal meaning without its stated market, source, and time context.
Concept relationships
Prerequisites
Related
Required by
Where this concept is used
- ImportantPermanent Security Identifier Mapping: Scoped, Effective-Dated CrosswalksD02-F03-A01
- ImportantTicker-Change Chain ResolutionD02-F03-A02
- ImportantShare-Class Relationship Mapping: Same Issuer Does Not Mean Same SecurityD02-F03-A03
- ImportantMerger Predecessor/Successor Mapping: Preserve Identity and Entitlements Without Inventing ContinuityD02-F03-A04
- ImportantDelisting Return Reconstruction: Separate Observed Proceeds from EstimatesD02-F03-A05
- ImportantHistorical Constituent Reconstruction: Rebuild the Roster Without Looking AheadD02-F04-A01
Evidence and governance
- Fintech Builder Glossary Definition Contract The Fintech Builder · internal governed contract
Supports: preferred label, short definition, technical definition
Limits: Defines governed platform behavior rather than claiming these policies are universally prescribed by external McClellan methodology.
- Reviewed by
- fintech-builder-owner-approved
- Last reviewed
- 2026-07-26
- Next review
- 2027-07-26
- Record status
- published