- Fill Execution Report only for outright instruments
Bolded red text indicates support for EBS Market.
For fixed income markets: represents the Entering Trader
Sequence number assigned to this message.
The max value is 999999999 which is 1 short of 1 billion.
|39001||UUID||uInt64||8||Y||Matches Establish.UUID used to establish the connection.|
Unique identifier of Execution Report message as assigned by exchange. Uniqueness is guaranteed within a single trading day or the life of a multi-day order.
For futures and options markets:
Should be unique per Firm ID.
Assigned value used to identify specific message originator.
Represents last individual or team responsible for the system that modifies the order prior to submission to CME Globex.
the buy side (institution, broker, intermediary, etc.). Uniqueness
For EBS and fixed income markets: represents the Entering Trader. For EBS this value must be 3 characters.
This value represents the individual or team submitting the message and is subject to registration requirements and character limits as required by Rule 576 and the Advisory below:
In FirmSoft and Global Command Center queries for order status and cancellations, this value must be exact.
Unique identifier for Order as assigned by
; for example, by embedding a date within the ClOrdID field
client system. Uniqueness must be guaranteed within a single trading day.
Firms, particularly those which electronically submit multi-day orders, trade globally, or throughout market close periods, should ensure uniqueness across days
SecExecID 527 TradeDate 75
The unique identifier of the Party Details Definition Request Acknowledgment associated with this message; this is the value submitted on the inbound message.
For pre-registered messages:
- Unique ID from Party Details Definition Request Acknowledgment message
For on-demand messages:
- If not registered beforehand through iLink then Party Details Definition Request message will be sent along with the business message and will immediately precede it
|Y||Price of this (last) fill.|
|37||OrderID||uInt64||8||Y||Unique identifier for order as assigned by the exchange. Uniqueness is guaranteed within a single trading day across all instruments.|
|44||Price||PRICE9||8||Y||Price per share or contract.|
|99||StopPx||PRICENULL9||8||N||The stop price of a stop limit and stop protect order (Conditionally present if tag 40-OrdType=4).|
|60||TransactTime||uInt64||8||Y||Time the transaction represented by this Execution Report (35=8) occurred. Expressed as nanoseconds since epoch time.|
|5297||SendingTimeEpoch||uInt64||8||Y||Time when the message is sent. 64-bit integer expressing the number of nanoseconds since midnight January 1, 1970.|
OrderRequestID used to identify a request to enter, modify, or delete an order. Echoed back on the Execution Report.
For the unsolicited events (e.g. fills and end of day eliminations), echo the value on the ExecutionReport representing the last accepted OrderRequestID on the corresponding order.
Unique identifier linking spread summary fill notice with leg fill notice and trade cancel messages.
To uniquely identify each fill, Client System can concatenate: OrderID (37) +
|548||CrossID||uInt64NULL||8||N||Identifier for a Cross order. Will be present if execution report is in response to a Cross order.|
Host-assigned entity ID used to reference all components of a Cross: sides + strategy + legs.
The HostCrossID also links components of the Cross order. For example, each individual Execution Report associated with the order will contain HostCrossID to tie them to the original Cross order.
ISO identifier of the physical location of the individual or team head trader identified by the tag 5392 (SenderID) in the message.
The first two bytes as per ISO 3166-1, identify the country (e.g., JP = Japan, CN = China).
The next three bytes indicate a comma-delimited state or province code (e.g., CA = California, QC = Quebec).
For valid values, refer to ftp.cmegroup.com/fix/coo.
Market Regulation requires only the submission of the two first characters of tag 9537-Location for all countries with the exception of Canada. For Canada, the 5 bytes including the province code must be submitted.
Note: this field is optional for EBS Market and eFIX Matching Service instruments.
|48||SecurityID||Int32||4||Y||Security ID as defined in the market data Security Definition message.|
Number of shares or contracts ordered.
|32||LastQty||uInt32||4||Y||Quantity bought/sold on this (last) fill.|
|14||CumQty||uInt32||4||Y||Total quantity filled.|
|37711||MDTradeEntryID||uInt32||4||Y||Market Data Trade Entry ID. This identifier is assigned to all trades that take place for an instrument at a particular price level.|
|1506||SideTradeID||uInt32||4||Y||The unique ID assigned to the trade once it is received or matched by the exchange.|
|820||TradeLinkID||uInt32NULL||4||N||Contains the workup ID; unique per instrument per day.|
Quantity open for further execution.
LeavesQty = OrderQty (tag 38) - CumQty (tag 14)
Only present for outrights and spreads
, not spread legs.
Indicates date of trading day (expressed in local time at place of trade).
Sent in number of days since Unix epoch.
Date of order expiration (last day the order can trade), always expressed in terms of the local market date.
Sent in number of days since Unix epoch.
- OrdStatus=1 (Partially Filled)
- OrdStatus=2 (Filled)
|Identifies status of order as partially filled or completely filled.|
Describes the specific Execution Report (e.g. Cancel) while tag 39-OrdStatus will always identify the current order status (e.g. Partially Filled).
- OrdType=1 (Market order with protection)
- OrdType=2 (Limit order)
- OrdType=4 (Stop limit order)
- OrdType=K (Market limit order)
- Side=1 (Buy)
- Side=2 (Sell)
|Side of order.|
- TimeInForce=0 (Day)
- TimeInForce=1 (GTC)
- TimeInForce=3 (FAK)
- TimeInForce=4 (FOK)
- TimeInForce=6 (GTD)
- TimeInForce=99 (GFS)
Specifies how long the order remains in effect
.Conveys whether a
FOK is supported only for BrokerTec/EBS
GFS is supported only for EBS
Indicates if the message was initially received manually.
'0' indicates the message was generated by automated trading logic.
iLink messages containing a value other than '0' or '1' in this tag will be rejected.
This tag is subject to Rule 536.B.2 Electronic Audit Trail Requirements for Electronic Order Routing/Front-End Systems.
Flags message as possible retransmission
Indicates if message is an original transmission or duplicate in response to Retransmission Request
or possible duplicate
Used when original messages are interleaved with Retransmission responses
fixed income markets
Possible duplicate means the same message may have been sent again with different sequence number
- AggressorIndicator=0 (No)
- AggresorIndicator=1 (Yes)
Indicates if order was incoming or resting for the match event.
Type of Cross submitted to the market (if in response to a Cross order).
- Bit 0=AON
- Bit 1=Only Best
- Bit 2=Not Held
Instructions for order handling for fixed income markets.
Only Best may be applied to resting and aggressing orders and:
- Prevents submission of an order if the order’s price is not equal to or better than the best price on the book.
- Cancels an order from the book if a new order with a better price enters the queue.
- This order condition permits the order to be alone at the best price level or join other orders at the best price level.
Not Held (applies only to US Repo) eliminates quantity remaining from an FaKi order (tag 59=3) and ensures it will it not be included in a work-up session; however, the order can still trigger a work-up session.
AONs will have a separate book with a separate ISIN. The AON orders that cannot trade immediately can rest in the AON book. They can only trade with AON orders on the other side of the AON book that have the SAME PRICE and SAME QUANTITY.
Applicable only for BrokerTec Markets; should not be used for future and options markets.
Instruction for whether the order should rest on the book upon entry or match as an aggressor.
A Passive Order will rest in the market without executing unless matched with an Aggressive Order on the other side.
An Aggressive Order will match against any other order on the opposite side.
Applicable for US & EU Repos.
Indicates if an order was submitted for market making obligation as required for MIFID.
Applicable only for EU
BrokerTec and EBS MiFID.
Boolean: flags a managed order.
Applicable only to Repo fixed income markets.
- 0=Long Sell
- 1=Short Sale With No Exemption (SESH)
- 2=Short Sale With Exemption (SSEX)
- 3=Undisclosed Sell (Information not available – UNDI)
Indicates the type of short sale on Sell orders only as required for MIFID.
Should not be used for Buy orders.
Applicable only for EU fixed income markets.
|The Short-Selling Field is only required from Participants when BrokerTec EU has a regulatory obligation (pursuant to Article 26(5) of MiFIR) to conduct transaction reporting on behalf of the Participant. This obligation only applies to BrokerTec EU when the relevant participant is exempt from MiFIR (typically non-EEA (European Economic Area) firms, corporate entities or certain asset managers). Please reach out to TradingVenueCompliance@cmegroup.com for guidance. |
Specifies the owner of the work up private phase.
- included in workup
- 1 – Passive owner
- included in workup
- 2 – Aggressive owner
- fill price from order excluded from workup during sweep
- 3 – Passive owner
.Maximum number of fill reasons is 6.
- fill price from order excluded from workup during sweep
- 9 - Not Applicable
The discretion price of an order. Conditionally required if the trader wishes to display one price but will accept trades at another price)
- The discretion price for a bid must be greater than the shown Limit price (e.g. Buy order: tag 44-Price = 115.05; tag 845-DiscretionPrice = 115.06)
- The discretion price for an ask must be less than the shown Limit price (e.g. Buy order: tag 44-Price = 115.05; tag 845-DiscretionPrice = 115.04)
Applicable only for EBS.
|828||TradeType||uInt16NULL||2||N||Represents a trade at fixing price|
- ExecRestatementReason=8 (Exchange)
|Will be present when trade at fixing is assigned fixing price|
|64||SettlDate||LocalMktDate||2||N||Specific date of trade settlement|
|541||MaturityDate||LocalMktDate||2||N||Date of maturity|
Total amount traded (in notional) in counter currency for the Spot
|381||GrossTradeAmt||Decimal64NULL||9||N||Total amount traded (in notional) in base currency for the Spot|
|6262||BenchmarkPrice||PRICENULL9||8||N||The price assigned to an eFix matched trade which is determined by an automated set market mid-price from a third|
party market data feed. The Fixing Price will be distributed as soon as practicable after the Fixing Time
|1362||NoFills||groupSize||3||Y||Specifies the number of fill reasons included in this Execution Report|
|→1364||FillPx||PRICE9||8||Y||Price of this fill reason or allocation. Required if NoFills(|
|1362) > 0. Same as LastPx(|
|→1365||FillQty||uInt32||4||Y||Quantity bought/sold for this fill reason|
|→1363||FillExecID||String2||2||Y||Used as an identifier for each fill reason or allocation reported in single Execution Report. Required if NoFills(|
|1362) > 0. Append FillExecID with ExecID to derive unique identifier for each fill reason or allocation|
0 – Future Hedge
1 – Pro Rata
2 – LMM
3 – TOP
4 – FIFO
5 – Cross BMG
8 – Covering
9 – Cross BPM
10 – Leveling
11 – Aggressor
14 – Leg
16 – Opening
18 – Implied Opening
19 – FIFO Percent
22 – Institutional Prioritization
23 - Price Discretion
|Enumeration of the Fill Reason field using Integer. This identifies the type of match algorithm|
Number of fills which comprise fill quantity
The maximum number of fills is configured 100.
Applicable for BrokerTec and EBS Market only.
|→ 1799||OrderEventPx||PRICE9||8||Y||Refers to the fill price; same as LastPx (tag 31|
Will not be present for BrokerTec US; Will be populated with the firm ID of the opposite order for BrokerTec EU bilateral trades
|Will be populated with the Settlement Counterparty Public ID for EBS Market. |
This is a unique ID which ties together a specific fill between two orders; It will be unique per instrument per day
For EBS and BrokerTec US and EU Repo markets: this tag will be globally unique across all EBS and Repo instruments. Uniqueness is guaranteed within the configured range per market segment.
|For EBS customers, this field is equivalent to the Deal ID in Ai.|
|→ 1800||OrderEventQty||uInt32||4||Y||Refers to the specific fill quantity between this order and the opposite order|
- 4=Partially Filled
|The type of event affecting an order|
. 100=Binary Trade Reporting
- 100=Binary Trade Reporting
|Action that caused the event to ||→6555||OriginalOrderEventExecID||uInt32NULL||4||N|
Contains the previous tag 1797-OrderEventExecID value of the trade being adjusted or busted.
Will not be present on the following message typesExecutionReportTradeOutrightExecutionReportTradeSpreadExecutionReportTradeSpreadLeg
|→ 5542||ContraGrossTradeAmt||Decimal64NULL||9||N||Amount traded (in notional) in base currency for the Spot with this counterparty|
|→ 5971||ContraCalculatedCcyLastQty||Decimal64NULL||9||N||Amount traded (in notional) in counter currency for the Spot with this counterparty|