Summary: Client display, internal research, valuation support, and executable quoting carry different control requirements. Before building a process, define whether the price is informational only or enters a higher-governance workflow. A label should not carry an undefined use. One traditional asset can have multiple issuers,…
Define the purpose of a “reference price” first
Client display, internal research, valuation support, and executable quoting carry different control requirements. Before building a process, define whether the price is informational only or enters a higher-governance workflow. A label should not carry an undefined use.
Product identity matters more than choosing a single source
One traditional asset can have multiple issuers, structures, and venue versions. Before selecting a reference, confirm issuer, product type, venue, quote currency, price type, and data time. Activity and depth can provide context, but they do not replace an institution’s own product, licensing, and governance assessment.
Create an auditable record of time and method
Record data time, capture time, calculation time, and applicable window separately. Retain sources, fields, calculation logic, and exception handling. Timestamps do not need to be forced into the same second, but their meaning must be clear.
Write exceptions into the process
Unavailable sources, changing terms, anomalous quotes, and missing data will occur. The process should define review and escalation paths and trigger method checks when material changes happen—not rely only on an annual review.
Closing
Explore structured tokenized-asset data and market information on RootData: https://www.rootdata.com/tokenized-assets

