Source-aware field guide · 20 answers
Market Data, Quotes and Symbols
Operational answers for licensing, entitlements, executable quotes, symbol masters, normalization, stale-price controls and feed acceptance.
Published · reviewed for scope, source visibility and answer ownership
How to use this guide
Operational answers for licensing, entitlements, executable quotes, symbol masters, normalization, stale-price controls and feed acceptance. It is written for broker technology buyers, market-data teams, dealing operations, product owners and integration engineers. The collection separates data delivery from execution and licensing; it does not claim ownership, redistribution rights or executable liquidity for any feed. Use it to turn a sales conversation into a responsibility map, evidence request and acceptance plan that named reviewers can approve.
Each answer supports one operating decision: Who may receive and use each dataset, how is every instrument defined and normalized, and what evidence shows the feed is complete, current and fit for its approved purpose? Rights, fields, timing and quality differ by source, contract, product and use case, including display, non-display, derived and redistributed use. Work from the actual entity, instruments, client locations, counterparties and deployment design because the same label can describe materially different services.
The primary reference set is CME Group — Market Data Policy Education Center; CME Group — Information Policies; FIX Trading Community — Data and Transparency; ESMA — MiFIR Article 13 Market Data. These sources define standards, regulatory expectations or official operating concepts; they do not endorse FxTrusts or prove a feature in any deployment. Recheck the current source, signed order form, technical specification, permissions and test record before a production, trading or compliance decision.
How to Document Market Data Licensing Rights
Market data licensing documentation identifies the source, dataset, recipient entities, users, devices, locations, permitted purposes, redistribution and reporting obligations.
- Use it to
- Map every display, algorithm, risk, pricing, archive and downstream distribution use to the governing agreement and entitlement.
- Check the boundary
- Paying for connectivity or receiving a feed does not automatically grant rights for non-display use, derived products or client redistribution.
How to Build a Market Data Entitlement Register
A market data entitlement register records which identity, device, application and legal entity can access each product under a particular permission and effective period.
- Use it to
- Connect approval, activation, modification, deactivation, usage reporting and periodic review to technical access controls and audit evidence.
- Check the boundary
- Administrative lists or invoices may not prove that systems prevented unentitled access throughout the reporting period.
What Is the Difference Between a Quote and a Fill?
A quote communicates a price and sometimes size under stated conditions, while a fill confirms that an order executed for a particular quantity and price.
- Use it to
- Preserve quote identifiers or timestamps, order instructions, acknowledgements and executions when analyzing the relationship between displayed and realized prices.
- Check the boundary
- A visible or received quote may be indicative, stale, size-limited or otherwise unavailable to the submitted order.
Does a Price Feed Include Order Execution?
A price feed distributes market information, while order execution requires separate permissions, message flows, counterparty terms, credit and accepted trading instructions.
- Use it to
- Document market-data and order-entry endpoints independently even when the same provider, protocol or network supplies both.
- Check the boundary
- Successful quote receipt should not be presented as proof that orders can be routed or filled with that source.
How to Create a Broker Symbol Master
A broker symbol master is the governed source for instrument identifiers, economic terms, sessions, precision, status, source mappings and effective dates.
- Use it to
- Assign change ownership and distribute one approved record to platform, pricing, risk, CRM, reporting and reconciliation systems.
- Check the boundary
- Separate hand-maintained symbol tables can drift and produce prices, orders and reports that refer to different contracts.
Which Fields Belong in an Instrument Specification?
An instrument specification should define asset, base and quote currency, contract size, tick, precision, sessions, order limits, margin, financing and lifecycle events.
- Use it to
- Compare upstream source terms with the customer-facing contract and each system configuration before enabling the symbol.
- Check the boundary
- A matching symbol code does not establish matching contract economics or trading conditions across systems.
How to Map Symbols Between Market Data Sources
Symbol mapping links provider identifiers to a canonical instrument while preserving venue, tenor, currency, contract and source-specific attributes.
- Use it to
- Use immutable internal identifiers, effective-dated mappings and automated checks for duplicates, missing fields and economic mismatches.
- Check the boundary
- String substitution alone can map similarly named but economically different instruments into one price or risk record.
How to Normalize Bid and Ask Quotes
Bid and ask normalization aligns side, units, precision, currency, size, source timestamp and fee treatment without erasing the original source values.
- Use it to
- Define canonical units and rounding rules, then test inversions, crossed markets, missing sides and unusual precision.
- Check the boundary
- Rounding or inverting a quote incorrectly can create artificial spreads and invalid prices even when the source message is correct.
How to Build an Aggregated Price Book
An aggregated price book combines eligible source entries using defined normalization, credit, freshness, size, fee and ordering rules for a specific consumer.
- Use it to
- State whether levels are merged, source attributed, executable and filtered, then test ties, depletion and source withdrawal.
- Check the boundary
- The mathematically best displayed level may not be executable for the intended account, size or counterparty credit.
How Do Market Data Snapshots and Increments Work?
A snapshot describes state at a point, while incremental updates add, change or delete entries that a consumer applies in sequence to maintain current state.
- Use it to
- Define initialization, sequence validation, gap handling, reset, deletion and resubscription with source-specific examples.
- Check the boundary
- Applying an increment to an incomplete or stale base can produce a plausible but incorrect book.
How to Detect Market Data Sequence Gaps
Market data sequence-gap detection identifies missing or out-of-order updates using the source protocol, channel and recovery design.
- Use it to
- Measure expected continuity, quarantine uncertain state and trigger replay or a fresh snapshot before republishing affected instruments.
- Check the boundary
- Continuing to display a book after a gap can conceal missing deletions or price changes that never reached the consumer.
Which Market Data Timestamp Should Be Used?
Market data may carry event, source-send, gateway-receive, normalization and publication times, each answering a different timing question.
- Use it to
- Preserve named timestamps with precision, timezone and synchronized-clock context instead of overwriting them with one local time.
- Check the boundary
- Comparing unlike timestamps can misstate feed delay, price age and the order in which events occurred.
How to Set Stale Quote Controls
Stale-quote controls compare current time, source activity, expected session and upstream health against a governed freshness threshold for each instrument.
- Use it to
- Define warning, suppression, order-blocking, fallback and recovery actions with owner approval and observable reason codes.
- Check the boundary
- One global timeout can be too slow for active symbols and too aggressive for legitimately quiet markets.
How to Detect Bad Ticks and Price Outliers
Price-outlier controls flag observations that violate format, range, continuity, cross-source or economic checks without automatically assuming the source is wrong.
- Use it to
- Record the raw tick, comparison data, rule version, disposition and effect on display, orders, bars and downstream calculations.
- Check the boundary
- Aggressive filtering can remove real market moves, while weak filters can distribute obvious errors to clients and risk systems.
How to Handle Market Data Session Boundaries
Session-boundary handling defines open, close, auction, break, holiday and maintenance states plus the prices and orders permitted in each state.
- Use it to
- Use authoritative calendars and effective-dated exceptions, then test transitions across timezone and daylight-saving changes.
- Check the boundary
- Assuming a fixed daily schedule can publish stale prices or accept activity while the underlying market is closed.
How to Manage Trading Reference Data Changes
Reference-data change management controls new instruments, renames, expiries, rolls, corporate actions and modified economic terms across connected systems.
- Use it to
- Publish effective-dated changes through one workflow with impact review, preview validation, reconciliation and rollback.
- Check the boundary
- Updating only the visible symbol name can leave historical, risk, position and reporting records attached to the wrong definition.
What Is Derived Market Data?
Derived market data results from calculations or transformations using source information, but its permitted creation and distribution depend on the governing licenses.
- Use it to
- Document inputs, formula, reversibility, recipients, purposes, retention and contractual classification before product use.
- Check the boundary
- Changing a format, adding a markup or calculating a bar does not automatically remove source licensing obligations.
How to Govern Market Data Redistribution
Market data redistribution sends information beyond the licensed recipient or application and requires explicit rights, entitlements, reporting and downstream controls.
- Use it to
- Map websites, terminals, APIs, reports, affiliates and vendors to contracts and technical restrictions before enabling delivery.
- Check the boundary
- A public endpoint or customer portal can create redistribution even when the original feed was licensed for internal use.
How to Reconcile Prices Across Trading Platforms
Price reconciliation compares source and displayed values after expected timing, mapping, normalization, filtering and markup transformations for the same instrument.
- Use it to
- Sample normal and exceptional periods and retain each transformation input so unexplained differences can be assigned and corrected.
- Check the boundary
- Exact equality may be inappropriate across timing points, while unexplained persistent differences should not be dismissed as latency.
What Proves a Market Data Feed Is Ready?
Market data acceptance requires verified rights, instruments, dictionaries, completeness, freshness, normalization, recovery, entitlements, monitoring and support for the approved use.
- Use it to
- Run representative load, gap, stale, outlier, session, mapping and failover tests with signed results and unresolved limitations.
- Check the boundary
- A live chart or sample quote proves neither legal entitlement nor complete, accurate and recoverable production delivery.
Primary and official references
These sources establish definitions, standards or official product behavior used across this guide. Follow the exact source and check its current version before a live implementation.