As we are rolling out more algo venues, it has become necessary to see the trading strategy information on the ExecutionReport. This will also help with queries/analytics.
As a result, we have introduced HasExtendedOrderFields to ExecutionReport in the Whisperer schema version 19458, and will populate the fields in the repeating group according to the timeline below.
We have introduced HasExtendedOrderFields to ExecutionReport to pass on the trading strategy information to clients. The change will normalise how the information is passed on to the clients without inconsistencies, and the use of BodyPassthruFields.
Warning
title
HasExtendedOrderFields and Schema Upgrade
Please note that clients should be prepared to consume HasExtendedOrderFields in ExecutionReport when they upgrade to Whisperer schema version 19458.
Timeline
Phase 1
- UAT - MarketFactory will introduce the HasExtendedOrderFields to ExecutionReport for clients to test the affected venues in UAT.
At client discretion - PROD - Whisperer release 2025.10.XX.WE will be available for clients interested in consuming HasExtendedOrderFields in ExecutionReport.
Phase 2
Introduce the ability to identify the Liquidity Provider that Filled or Rejected an order in the Taker ESP and Taker RFS workflows.
This feature will help users get a complete view of orders Filled or Rejected by an LP on an ECN + orders executed directly on the native bank API.
We will enrich ExecutionReport with ExecutionVenuePartyRole and PartyID populated with the MIC of the Liquidity Provider that Filled or Rejected an order.
Timeline
- UAT - The feature will be available for clients to test in UAT if they are trading on the affected venues.
At client's discretion
- UAT - MarketFactory will introduce the HasExtendedOrderFields to ExecutionReport for clients to test the affected venues in UAT.
At client discretion - PROD - Whisperer release 2025.1011.XX.WE or a later version will be available for clients interested in consuming HasExtendedOrderFields in ExecutionReportwho are ready to consume ExecutionReport consistently populated with ExecutionVenuePartyRole.