Murex has added native connectivity between MX.3 and the ICE Consolidated Feed, allowing banks and asset managers to stream normalized multi-asset market data directly into trading and risk workflows. The new IDS CF MD interface is available from MX.3 version 3.1.68 and extends a relationship that already covers interest-rate curves, inflation curves, volatility data, credit-default-swap data and fixed-income pricing.
The integration removes part of the custom connectivity work required to bring an external feed into MX.3. It does not remove market-data licensing, entitlements or usage reporting. Clients still need an entitlement system connected through Murex’s interface or a supported native control such as the Real-Time Data Access Control System.
Native Connectivity Reduces an Integration Layer
Market-data projects often involve feed handlers, symbol mapping, normalization, permissions and distribution to multiple applications. A native interface can shorten implementation because MX.3 and ICE define the connection rather than leaving each institution to build and maintain its own adapter.
That can reduce operational risk when fields change or new content is added. It can also make support responsibilities clearer. A client still needs to configure instruments and workflows, but the transport and data model are part of a supported product relationship.
Murex has followed the same approach with other datasets. FinanceFeeds previously covered the integration of S&P Global OTC derivatives data, which brought cross-asset information into model-validation and pricing processes. It also reported on Kaiko digital-asset data in MX.3, extending the platform beyond conventional market sources.
The pattern is part of a wider move toward modular institutional infrastructure. Brokerage platforms are combining external liquidity, execution and risk components behind a common workflow. Murex is applying the same logic to market data, giving clients a supported connection while leaving the source, licensing and internal governance with the relevant providers.
One Feed Can Support Trading, Valuation and Risk
ICE Consolidated Feed aggregates content from global marketplaces and third-party providers into a normalized service. Bringing that stream into MX.3 means the same data can support front-office pricing, position monitoring, intraday risk and downstream controls without separate connections for each workflow.
Consistency matters because small differences in timestamps, symbology or price selection can produce different valuations across desks. If trading uses one source while risk and collateral systems use another, institutions spend time explaining breaks that come from data rather than positions. A shared feed can reduce those reconciliation points.
It does not guarantee that every use case should rely on the same field. A trader may need executable bid and offer data, while valuation control may require a governed close or evaluated price. The integration supplies access. Each institution remains responsible for deciding which source is appropriate for each model and control.
Entitlements Remain Separate From Technical Access
ICE lets customers choose their usage-reporting and data-management technology. Murex therefore requires its Entitlement SPI to connect the selected permission system, unless the client uses a natively supported alternative. This separation is important because the ability to receive a feed does not give every user or application the right to consume every instrument.
Exchange data contracts can distinguish display use, non-display use, derived data and redistribution. Automated valuation or algorithmic trading may carry different terms from a human viewing a price. Institutions need permissions that follow the data through MX.3 rather than stopping at the point of ingestion.
The issue becomes more significant as firms distribute data to more regions and automated services. FinanceFeeds has reported how overnight equity pricing incorporates additional venues. More complete coverage improves the reference rate, but it also expands the set of licences, quality checks and source dependencies behind it.
Real-Time Risk Depends on Reliable Time and Symbology
A normalized feed can simplify cross-asset coverage, but the institution still needs to monitor latency, stale prices and instrument mapping. A bond, future, option and OTC derivative may refer to related economic exposure while using different identifiers and trading calendars. Incorrect mapping can propagate a plausible but wrong price into valuation and risk.
MX.3 clients also need fallback policies. If the primary feed becomes unavailable, the system must identify stale data, switch to an approved source or suspend a calculation rather than silently reusing an old value. Those controls are particularly important for margin and intraday limit monitoring, where a delayed price can understate exposure.
Longer market hours raise the requirement. As brokers extend commodity trading through weekends, price sources become thinner and more provider-dependent. Institutional platforms cannot infer that a continuously updating number has the same quality throughout the day.
The same principle applies to perpetual markets, where prices continue while funding and liquidity conditions change by hour. Institutional perpetual-futures connectivity can improve execution access, but risk systems still need accurate marks and clear fallback rules during stress. Continuous markets make data resilience a front-office requirement rather than a background technology concern.
ICE Gains Distribution Inside an Established Workflow
Murex Head of Market Data Connectivities Alexandre Bélingard said the interface gives clients more choice among streaming sources. ICE Vice President Maurisa Bauman said the feed can reach customers in workflows they already use. That distribution advantage is the commercial core of the deal.
Replacing a market-data provider is difficult when feeds are tied into models, permissions and operations. Native support lowers the switching cost at the technical layer and gives ICE access to institutions already running MX.3. Murex, in turn, makes its platform more useful without becoming the original source of the data.
The integration is not a new trading venue or analytics model. It is infrastructure that reduces the distance between a data source and the decisions built on it. Its value will be measured in implementation time, data consistency and resilience, while the less visible work remains entitlement governance, mapping and fallback control.
