What Is a Security Master? Identification and Evaluated Pricing in Structured Credit
A security master is the central database a financial firm uses to define each instrument it holds or trades. For every security it stores the identifiers, the descriptive terms, the issuer, and the classifications that accounting, risk, compliance, and pricing systems read before they do anything else. Nothing downstream works reliably until the instrument has been set up correctly.
For most bonds, that setup is routine. A corporate bond's identifiers and terms are fixed at issuance and rarely change before maturity. CLOs and other securitized products are harder to handle. A single CLO can issue eight or more classes of notes, each class may exist as two separate securities with different identifiers, and a refinancing can retire part of the capital structure years before final maturity.
This guide covers what a security master holds, how the major identifier schemes relate, how structured credit complicates identification, and why those problems tend to surface later as pricing and audit problems.
What a security master contains
Reference data describes what an instrument is. Market data describes what it is worth on a given day. The security master holds the first kind, which changes far less often than prices do.
A fixed income record starts with identification, meaning the firm's internal key plus the external identifiers that custodians, counterparties, and data vendors use. It then holds the instrument's terms: coupon type, fixed rate or floating spread, reference rate, day count, payment dates, issue and maturity dates, currency, and call and redemption provisions. Classification fields follow, covering asset class, sector, rating, and the regulatory and accounting tags that determine how the position is reported. Finally the record captures relationships. For an ordinary bond the important relationship is to the issuer. A securitized product adds a second one that downstream systems depend on just as heavily, which is the link between each tranche and the deal that issued it.
Reference data management
Reference data management is the ongoing work of keeping those records accurate. Terms are best taken from offering documents, because trade tickets and counterparty files sometimes carry abbreviated or outdated values. When two vendors disagree on a field, someone has to decide which source prevails and record the decision. When an instrument is amended, partially redeemed, called, or exchanged, the record has to change on the correct effective date, and the prior values have to stay retrievable.
That last requirement is the one most often missed. An auditor reviewing a valuation from last March needs to see the instrument record as it stood in March. A system that overwrites fields in place cannot show that. Many firms discover this at quarter-end, when a valuation will not reconcile and the investigation leads back to a field that changed months earlier.
CUSIP vs ISIN
A CUSIP is a nine-character code used to identify securities in the United States and Canada. The first six characters identify the issuer, the next two identify the specific issue, and the ninth is a check digit. CUSIP Global Services assigns CUSIPs and operates the system on behalf of the American Bankers Association. Issuers outside North America can receive a CINS, which follows the CUSIP format but uses a letter as the first character to indicate the issuer's country or region.
An ISIN is a twelve-character code defined by the ISO 6166 standard and assigned by national numbering agencies. It opens with a two-letter prefix, continues with a nine-character national identifier, and ends with a check digit. In the United States the national identifier is the CUSIP, so a US ISIN is the letters US, then the CUSIP, then a check digit. Securities issued and settled through Euroclear or Clearstream generally receive ISINs beginning with XS.
The practical difference between CUSIP vs ISIN is reach. A CUSIP is native to North American settlement and data systems. An ISIN is recognized across markets and is frequently the one identifier that a US custodian, a European counterparty, and a data vendor all carry for the same instrument.
FIGI and SEDOL
The Financial Instrument Global Identifier, or FIGI, is a twelve-character identifier published as an open standard through the Object Management Group, with Bloomberg acting as registration authority. FIGIs can be used and redistributed without the license terms that apply to CUSIP-derived data and have become a common cross-reference key in vendor files. SEDOL, a seven-character code issued by the London Stock Exchange, appears in many of the same files and remains in wide use for UK securities.
A firm does not have to pick one scheme. What it needs is a cross-reference table that maps every identifier it receives to a single internal record and keeps it current as identifiers are issued and retired.
Why CLO tranches are hard to identify
A CLO issues its notes from one special purpose vehicle, usually in several rated debt classes plus subordinated notes that function as the equity. Each class is its own security with its own identifiers and terms. Five features of the structure make those identifiers harder to manage than a corporate bond's.
The deal sits above the tranche
Many of the attributes that drive a tranche's value belong to the deal. The collateral manager, the trustee, the reinvestment period end date, the non-call period, the underlying portfolio of leveraged loans, and the monthly coverage test results are all deal-level facts. A security master that stores tranches as standalone bonds has nowhere to keep them, so every system that needs them has to source them separately. A deal-level record with each tranche linked to it keeps those facts in one place and shows the firm its total exposure to a deal or manager.
One tranche, two securities
US CLO notes are commonly offered to qualified institutional buyers under Rule 144A and to investors outside the United States under Regulation S. The two portions of a class have the same coupon, the same seniority, and the same position in the payment waterfall, but they are issued as separate securities. The 144A notes typically carry a standard CUSIP and the US ISIN built from it. The Regulation S notes carry their own CUSIP-format identifier, often a CINS whose leading letter reflects the issuer's jurisdiction, and their own ISIN. They are one exposure for pricing and risk and two securities for settlement, and the security master has to support both views.
Refinancings and resets retire identifiers
After a CLO's non-call period ends, the equity holders can direct a refinancing of one or more debt classes at a lower spread, or a reset that replaces the full debt stack and generally extends the reinvestment period and final maturity. In either case the affected notes are redeemed and replacement notes are issued with new identifiers. Replacement classes are commonly labeled with an R suffix, so Class A becomes Class A-R and a second refinancing produces Class A-RR, while the deal keeps its original name. If the security master does not process the event, the redeemed notes remain on the books as open positions and the replacement notes arrive on the custody file as unrecognized securities.
Issuer domicile varies
US CLO issuers have traditionally been incorporated offshore, European CLO issuers are commonly Irish, and the mix of jurisdictions has shifted over time with regulatory and tax changes. Because the issuer's jurisdiction affects CINS prefixes and ISIN assignment, structurally similar deals can carry identifiers that look quite different. A validation rule written around the identifier pattern of one market can reject legitimate identifiers from another.
Deal names are inconsistent
There is no standard naming format for CLOs. Trustee reports, custody statements, and vendor files may order the manager's shelf name, vintage year, series number, and refinancing suffix differently, or abbreviate some of them. Matching by name produces both missed matches and false ones.
These features explain a result operations teams see often. When a list of CLO identifiers from one source is matched against a security master built from another, a large share of the list may fail to join. The instruments exist in both places. What is missing is a complete cross-reference between the identifier schemes each source uses, and closing that gap is a mapping exercise.
What evaluated pricing is
Evaluated pricing produces a daily fair value estimate for an instrument that has no reliable closing price. Most bonds do not trade on a given day, and an over-the-counter trade may say little about where the next one would print. An evaluated price combines the market observations available for the instrument and for comparable instruments with a model that turns those observations into a price.
For a fixed rate corporate bond, the usual approach is to build a yield curve for the issuer or a peer group and discount the bond's cash flows along it. CLO debt pays a floating coupon, so the comparable measure is discount margin, the spread over the reference rate at which the present value of the tranche's projected cash flows equals its price. The projected cash flows come from the deal's structure and current collateral, combined with assumptions about loan defaults, recoveries, and prepayments. The model then takes spreads observed on the tranche itself or on comparable tranches, converts them into a discount margin for the tranche being priced, and applies that margin to the projected cash flows.
Market observations for CLOs are sparse. Trades are reported to FINRA through TRACE, but public dissemination of that activity is more limited than it is for corporate bonds, and on most days a given tranche does not trade. Dealer quotes are indicative. They are most plentiful for AAA notes from large, frequent managers and scarcest for BB tranches, single-B tranches, and equity. A CLO evaluated price is best understood as a documented, model-based estimate, and a user should expect to see the inputs and methodology behind it.
Level 3 assets and the fair value hierarchy
In the United States, ASC 820 sorts fair value measurements into three levels based on how observable their inputs are. Level 1 measurements use quoted prices in active markets for identical assets. Level 2 measurements use other observable inputs, such as quotes for similar assets or observable spreads and yield curves. Level 3 measurements rely on significant unobservable inputs, which reflect the reporting entity's own assumptions about how market participants would price the asset.
The holder determines where a CLO position sits, usually with input from its auditor and pricing vendor, and the classification can change between reporting periods as observable data appears or disappears. In practice, AAA and AA tranches with reasonable quote coverage are often reported as Level 2, while lower mezzanine tranches and CLO equity, whose values depend heavily on default and recovery assumptions, are more often reported as Level 3.
Level 3 assets carry heavier disclosure. Reporting entities provide quantitative information about the significant unobservable inputs, and public entities also provide a reconciliation of opening and closing balances and a narrative description of how sensitive the measurement is to changes in those inputs. For registered funds and BDCs, SEC Rule 2a-5 requires the board, or a valuation designee operating under board oversight, to assess valuation risks, select and test fair value methodologies, and oversee pricing services.
All of this assumes the firm knows exactly which instrument it is valuing. A carefully modeled price attached to the wrong tranche still misstates the position, and the supporting documentation ends up describing a security the fund does not hold.
Where identification errors turn into pricing errors
A hypothetical example shows how the problems described above compound. Suppose a fund holds the Regulation S version of the Class B notes in a US CLO we will call Example CLO 2019-1. In 2021 the deal refinances its Class A and Class B notes at tighter spreads. The original Class B notes are redeemed, and the fund receives Class B-R notes with new identifiers.
The custodian processes the exchange, and the next position file shows the new Regulation S identifier. The fund's security master has not recorded the refinancing, so the identifier matches nothing and the position lands in an exception queue. The original Class B record is still active, and the fund's pricing request asks its vendor for a note that has already been redeemed. Depending on the vendor, the response is either no price or a final price from before the redemption.
Once someone sets up the new notes, a second issue can appear. Much of the market activity in Class B-R may occur in the 144A version. If neither the vendor nor the fund links the two versions, the Regulation S position can end up priced from a thinner set of inputs than the tranche actually has.
A third issue sits underneath both. The cash flow projection for Class B-R depends on deal-level terms that the refinancing changed, including the new spreads on both refinanced classes, which alter how interest moves through the waterfall. If the tranche is linked to a deal record that still shows the 2019 terms, the model projects cash flows on the old spreads. The resulting price moves with the market each day and looks plausible, and it is off by an amount nobody has measured.
A simpler error is also common. Two deals from the same manager with similar names and adjacent vintages get confused during manual setup, and a position is priced as a tranche from the wrong deal. A senior note priced as a mezzanine note can move a fund's reported net asset value.
Every step in these examples is an ordinary operational event. A security master that models deals, links 144A and Regulation S versions of the same class, and records refinancings with effective dates handles each of them without manual intervention.
How SQX supports identification and pricing
SQX fixed income pricing covers corporate bonds, municipal bonds, syndicated bank loans, agency MBS, non-agency CMOs, CMBS, ABS, and CLOs. Pricing draws on observable trade data sourced through trade reporting utilities and on indicative sell-side quotes, which feed industry-standard models used to build issuer-level yield curves or to derive implied discount margins. Valuations are calculated daily at the close of major markets, with intraday valuations available for more liquid instruments, and are delivered on a same-day or next-day basis. Detailed methodology documentation is available on request, and the CLO and CDO page describes the structured credit service in more depth.
On the identification side, the SQX Securities Reference File carries ISIN, SEDOL, FIGI, ticker, and US local code alongside issuer name, country of register, CFI code, and industry classification. It includes a Point in Time feed recording historical changes to securities coding and reference data, and a related event feed that connects those changes to the corporate actions behind them. Point-in-time history of this kind is what allows a firm to close retired identifiers on their effective date, open replacements on theirs, and trace an earlier valuation back to the record in force at the time.
For deal-level information, the SQX Document Retrieval Service provides access to fixed income offering documents, including prospectuses and offering circulars, searchable by ISIN, US code, or symbol. SQX Bespoke Data Offerings include transcription of investor, pool, and servicing reports for CDO, MBS, and ABS securities into client-specified templates. The full set of services is listed on the SQX reference data and corporate actions page.
Checking your own setup
A firm holding structured credit can test its security master against a short list of capabilities. Tranches should link to a deal record that stores the manager, trustee, reinvestment period, non-call date, and current deal terms. The 144A and Regulation S versions of each class should both be present and flagged as the same economic instrument. Refinancings and resets should be processed as corporate actions, with redeemed identifiers closed and replacements opened on their effective dates. Historical versions of each record should be retrievable, so that any past valuation can be tied to the instrument data that produced it. And the pricing vendor's identifier universe should join to the firm's through a documented cross-reference, with exceptions reviewed and resolved on a schedule.
A firm that meets each of these has an identification layer that will stand up to audit review and board scrutiny. Gaps in any of them tend to appear first as pricing exceptions, and they are frequently misdiagnosed as model problems.
To learn more about CLOs,
follow SQX
on LinkedIn and subscribe to our
LinkedIn
newsletter to stay ahead of the curve.
Latest News
