The Execution Report - Trade Addendum Outright message notifies client system of trade cancellation or correction for outrights.

35=8, 39=H,G



Binary Type

Binary Length





Sequence number assigned to this message.

The max value is 999999999 which is 1 short of 1 billion.

Matches Establish.UUID used to establish the connection.

Globally unique identifier for each Execution Report message assigned by exchange.


For futures and options markets: represents Operator ID.

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.

This tag value is always uppercase, regardless of the case in the inbound message tag. Client systems are not required to submit capitalized identifier to CME Globex.


Unique identifier for Order as assigned by 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.


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
  • PartyDetailsListRequestID≠0.

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
  • PartyDetailsListRequestID=0.





Price of this (last) fill.

Globally unique identifier for each order assigned by the exchange.

Time the transaction represented by this Execution Report (35=8) occurred. Expressed as nanoseconds since epoch time.
Time when the message is sent. 64-bit integer expressing the number of nanoseconds since midnight January 1, 1970.

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) + TradeDate (75) + SecExecID (527) 

Unique identifier of the corrected fill.

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

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.

Security ID as defined in the market data Security Definition message.
Quantity bought/sold on this (last) fill.
Trade ID assigned to the trade once it is received or matched by the exchange.
Refers to the unique ID assigned to the corrected trade.

Indicates date of trading day (expressed in local time at place of trade).

Sent in number of days since Unix epoch.

  • OrdStatus=H (Trade Cancel)
  • OrdStatus=G (Trade Correction)

Identifies status of order as trade cancellation or correction.

  • ExecType=H (Trade Cancel)
  • ExecType=G (Trade Correction)

Describes the specific Execution Report as trade cancellation or correction.

  • Side=1 (Buy)
  • Side=2 (Sell)
Order side.
  • 0=Automated

  • 1=Manual

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.

  • 0=False
  • 1=True

Flags message as possible retransmission or duplicate.

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.

Possible duplicate means the same message may have been sent again with different sequence number.

  • 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.

  • A=Aggressive
  • P=Passive

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.

  • 0=False
  • 1=True

Indicates if an order was submitted for market making obligation as required for MIFID.

Applicable only for EU BrokerTec MiFID.

  • 0=False
  • 1=True

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 for guidance. 

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.

  • 1000=Trade at Fixing
Represents a trade at fixing price.
  • ExecRestatementReason=8 (Exchange) 
Will be present when trade at fixing is assigned fixing price.
Specific date of trade settlement.
Date of maturity.

Total amount traded (in notional) in counter currency for the Spot.

Total amount traded (in notional) in base currency for the Spot.
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.

Specifies the number of fill reasons included in this Execution Report.

Maximum number of fill reasons is 6.

Price of this fill reason or allocation. Required if NoFills(1362) > 0. Same as LastPx(31).
Quantity bought/sold for this fill reason.
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

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 markets only.

Refers to the fill price; same as tag 31-LastPx.
Will not be present for BrokerTec US; Will be populated with the firm ID of the opposite order for BrokerTec EU bilateral trades.
This is a unique ID which ties together a specific fill between two orders; It will be unique per instrument per day.
Refers to the specific fill quantity between this order and the opposite order.
  • 100=Trade Cancel
  • 101=Trade Correction
  • 4=Partially Filled
  • 5=Filled
The type of event affecting an order.
  • 100=Binary Trade Reporting
Action that caused the event to occur.

Contains the previous tag 1797-OrderEventExecID value of the trade being adjusted or busted.

Will not be present on the following message types:

  • Execution Report Trade Outright
  • Execution Report Trade Spread
  • Execution Report Trade Spread Leg
→ 5542ContraGrossTradeAmtDecimal64NULL9N
Amount traded (in notional) in base currency for the Spot with this counterparty.
→ 5971ContraCalculatedCcyLastQtyDecimal64NULL9N
Amount traded (in notional) in counter currency for the Spot with this counterparty.