A security master file, often shortened to security master or securities master, is the central store of descriptive information about the financial instruments a firm deals with. It holds one record per security, containing the identifiers, terms and classifications that every other system needs in order to trade, price, settle, account for and report on that security. Banks, brokers, asset managers, custodians and fund administrators all maintain one.
It forms a core part of a firm's reference data, alongside records for counterparties, clients and accounts. The content it holds is instrument reference data; the security master is the system and process that keeps that data in one authoritative place, so that the trading desk, the operations team and the finance function all describe a bond or share in the same way. This single authoritative version is commonly called golden source data.
What a record contains
The fields vary by asset class, but a typical record includes:
- Identifiers. The ISIN, national codes such as CUSIP and SEDOL, the FIGI identifier, exchange tickers and internal codes, with cross-references between them.
- Descriptive terms. Name, issuer, currency, country, place of listing, lot size and status. This slow-changing content is known as security static data.
- Instrument-specific terms. For a bond, the coupon rate, coupon schedule, day count convention, maturity and call features; for a derivative, the underlying, strike and expiry; for a fund, dealing frequency and share class.
- Classifications. Asset class, instrument type, sector and regulatory flags, as described under security classification.
- Issuer links. A reference to issuer reference data, including the issuer's LEI identifier and parent group.
Prices and other fast-moving market data are usually stored separately and linked to the master record by identifier.
Where the data comes from
Few firms create this data themselves. Most buy it from commercial data vendors, exchanges, numbering agencies and depositories, and supplement it with documents such as prospectuses. Because vendors differ in coverage and occasionally disagree, larger firms take feeds from more than one source and apply rules to decide which value to trust for each field. Where sources conflict or a field is missing, the record is routed to a data analyst as an exception.
New securities are set up either in advance, from vendor new-issue feeds, or on demand when a trader wants to deal in something not yet on file. Slow set-up is a common cause of delayed trade booking, so firms measure how long it takes.
Keeping it current
Securities change over their lives. Names and identifiers change after mergers, bonds are called or have coupons reset, shares are split or consolidated, and listings move. Much of this arrives through a corporate action data feed, and the master record must be updated on the correct effective date, with history preserved so that past positions and reports can be reproduced. Matured or delisted securities are flagged as inactive, not deleted.
Changes to key fields are normally subject to four-eyes approval, audit trails and periodic comparison with external sources. Ownership of each field, quality standards and the handling of errors are set out in the firm's reference data governance framework.
Why accuracy matters
Errors in a security master spread to every system that reads it. A wrong day count or coupon date produces incorrect accrued interest; a wrong settlement calendar or place of settlement leads to failed trades; a wrong classification distorts risk and capital figures; a wrong identifier can cause a regulatory transaction report to be rejected. In fund administration, a faulty price link or missed corporate action can produce an error in the net asset value calculation.
Regulation has raised the stakes. Rules on transaction reporting, on risk data aggregation and on settlement discipline all depend on clean instrument data, and supervisors have criticised firms that run several inconsistent security masters across business lines. Consolidating them into one enterprise-wide master is a frequent, and costly, data project.
The security master is one of several master data stores. Counterparty and client masters hold legal entity data, and an issuer corporate hierarchy links each issuer to its parent so that exposure can be added up by group. In corporate finance systems the comparable record for suppliers is vendor master data. Industry utilities and open identifiers have been promoted as ways to reduce duplicated effort, though most firms still rely on their own reconciled copy.