Devancore Inc.
Devancore Post-Trade Glossary
Glossary
Golden Source Reference Data
Golden source reference data is the approved version of an instrument, entity, market, calendar, SSI, or price fact after sources conflict, a winner is chosen, and downstream systems are allowed to use that version at a stated as-of.
Document source: https://devancore.com/glossary/golden-source-reference-data/
Devancore Post-Trade Glossary
Golden Source Reference Data
Golden source reference data is the approved version of an instrument, entity, market, calendar, SSI, or price fact after sources conflict, a winner is chosen, and downstream systems are allowed to use that version at a stated as-of.
Definition
Golden source reference data is the authorized copy of a reference fact. Several sources will disagree on a coupon, an LEI status, a holiday, an SSI, or a price. The golden source is the version that hierarchy, validation, and approval released for use, with an as-of that downstream workflows can replay.
Reference data management is the discipline that runs that process. A securities or instrument master is the store that holds instrument rows. Enterprise data management joins those rows to entity, calendar, and SSI. The golden source is the authorized value inside the store: which source won, who approved an override, and which consumers may read it.
What the golden copy must hold
What the golden copy must hold
The golden source is the authorized value, the rule that chose it, and the time it may be used.
| Element | What it holds | Control question |
|---|---|---|
| Fact | The field: coupon, maturity, LEI, MIC, holiday, SSI, price, CFI | Which attribute is this copy authoritative for? |
| Sources | Vendor, issuer, CSD, custodian, internal override, with as-of | Which inputs were in play when the winner was chosen? |
| Winner rule | Field-level hierarchy, tolerance, and unmatched conflict | Why did this source beat the others for this field? |
| Approval | Passed validation, queued, overridden, with actor and reason | Was this copy released, or only loaded? |
| Time | Effective date of the term and as-of of the belief | Can Tuesday's instruct replay Tuesday's copy, not Wednesday's fix? |
| Publication | Consumers: instruct, IBOR, ABOR, tax, report | Which workflows were allowed to read this version? |
A system of record answers origin. The OMS may be the system of record for the order. A custodian file may be the system of record for an SSI. Those origins still need an authorized copy before instruct and NAV share a number. A warehouse answers history. It does not, by itself, decide Tuesday's settlement calendar.
Time is part of the copy. Effective date is when the economic term changed in the market. As-of is what the firm believed when it booked, instructed, or reported. Those clocks differ after late notices, vendor restatements, and corrections. A golden source that keeps only the latest value cannot defend the NAV or the instruction that already used the prior value.
Publication is part of the copy. If the authorized coupon sits in a master and the settlement engine still reads a desk spreadsheet, the firm has two golden sources. The operating test is whether every named consumer received the same released version, or an explicit exception.
Golden source — feeds to authorized copy
Devancore Glossary · devancore.com
Golden source — feeds to authorized copy
Devancore Glossary · devancore.com
How it works
Golden source production is a workflow. Collect sources. Normalize keys and units. Apply a field-level hierarchy. Queue conflicts. Release a copy. Stamp the consumers that read it.
From competing feeds to an authorized copy
From competing feeds to an authorized copy
If two sources disagree and no owner decides, every downstream system invents its own golden source.
| Step | Data required | Failure mode |
|---|---|---|
| Collect | Vendor, issuer, CSD, custodian, and internal rows with as-of | One feed is treated as truth because it arrived last |
| Normalize | Identifiers, field names, and units aligned to one model | Two coupons look different because one is in percent and one in decimal |
| Rank | Field-level hierarchy and numeric tolerance | Equity terms and structured-product terms share one vendor winner |
| Conflict | Owner, aging, and supporting evidence for an override | A 1bp coupon gap is auto-published and hits every book |
| Release | Approved copy, effective date, as-of, consumer list | The master store updates; settlement still reads a local cache |
| Replay | Version stamp on instruct, NAV, or report | A later correction cannot explain which copy was used |
Hierarchy is per field, not per vendor. One source may win listed-equity identifiers. Another may win structured-product terms. A third may win LEI status. A single "primary vendor" flag is how a good equity feed overwrites a better bond maturity.
Conflict is expected. Tolerance can auto-accept a rounding difference. A material coupon, factor, identifier, or holiday mismatch needs an owner and a reason. Auto-publishing the last file is how every book inherits the same error at once.
Overrides need evidence, not just a new number. The issuer notice, the CSD bulletin, or the maker-checker note is why the hierarchy was broken. Lineage without that reason still cannot explain the choice in review.
Release is a state change. The copy becomes readable to named consumers: enrichment, instruction, IBOR, ABOR, tax, reporting. Local caches that drift are competing golden sources. Digital-token identifiers and on-chain addresses belong in the same release process as ISIN and CUSIP when the firm holds both representations of one instrument.
Replay is the operating proof. Instruct, recon, and reports should retain which golden copy they used. A conversational query is useful after that stamp exists: which fields published from an override this week, which consumers still read an older as-of, which conflicts aged past the settlement cutoff with no winner.
Golden source — auto-win, conflict, or block
Devancore Glossary · devancore.com
Golden source — auto-win, conflict, or block
Devancore Glossary · devancore.com
In Devancore™
Devancore — golden source evidence chain
Devancore · evidence stack
Source rows
Vendor, issuer, CSD, custodian, and override values enter with as-of, field, and source identity.
Winner rule
Hierarchy, tolerance, and unmatched conflict remain attached to the field, not to a whole vendor.
Authorized copy
Released, overridden, or blocked is a state with actor and reason.
Time stamps
Effective date of the term and as-of of the belief stay distinct.
Consumer stamp
Instruct, books, and reports retain which golden copy they used.
Devancore supports golden source reference data as a post-trade operating-record layer around source rows, winner rules, authorized copies, as-of stamps, and the consumer that read them. It can help teams keep conflict, approval, and publication visible next to settlement and reporting events.
Devancore does not act as a data vendor, numbering agency, golden-source utility, or official master. It does not rank vendors as a market authority and it does not replace appointed data owners. The product boundary is the controlled operating copy of the authorized reference fact that post-trade already depends on.
In a Devancore-style workflow, a source row, conflict, override, release, or consumer stamp enters as an event. The record is mapped to field, source, version, as-of, consumer, and workflow state. Ranked, conflicted, overridden, published, or blocked remains visible with actor, timestamp, reason, and source reference.
That structure is what operations uses. The vendor may know a coupon. The custodian may know an SSI. Accounting may know a book. The operating question is which authorized copy those facts became, and whether instruct and NAV used the same one.
Conversational finance depends on the same chain. A user can ask which golden copies were overridden without evidence, which consumers missed a release, which holiday conflicts sat open through value date, or which as-of a report used after a restatement. The answer should resolve to sources, winner rules, versions, consumers, and evidence.
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.
- Market Master Data
https://devancore.com/glossary/market-master-data/
The authoritative reference layer for countries, currencies, venues, CSDs, settlement rules, tax signals, sanctions evidence, and market infrastructure.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Contact
Request a briefing or platform walkthrough with the Devancore team.
Request access https://devancore.com/access/