Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The New Order Cross message submits a Cross on CME Globex, a two-sided order submitted by a single party/broker at the same price and quantity.

The → symbol indicates a repeating tag.




Binary Type

Binary Length




Identifier for a cross order. Must be unique during a given trading day.
Use OrderRequestID to identify a request to enter a cross order. Echoed back on the Execution Report.


  • 0=Automated

  • 1=Manual

Indicates if the message was initially received manually.
Sequence number assigned to this message.

For futures and options markets:

Operator ID.

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.

For fixed income markets: represents the Entering Trader.

  • OrdType=2 (Limit order)

Only ‘2’ (limit order) supported.

Constant value.

  • CrossType=3

A cross order which is executed on one side with any unfilled quantity remaining active.

Constant value.

  • CrossPrioritization=0 (None)

Indicates if one side of the cross order should be prioritized.

Constant value.

Conditionally required when tag 40-OrdType=2 (Limit).
For derivatives, a timestamp to indicate when this order was booked with the agent prior to submission to the exchange. Indicates the time at which the order was finalized between the buyer and seller prior to submission. 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.
Text describing sender's location (i.e. geographic location and/or desk).

Security ID as defined in the market data Security Definition message.

  • minValue=2
  • maxValue=2

Number of Side repeating group instances.

2=Both Sides


Unique identifier for Order as assigned by the buy side (institution, broker, intermediary, etc.). 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; for example, by embedding a date within the ClOrdID field.


Refers to the ID of the related Party Details Definition Request message logically tied to this message.

For short messages:

  • Party Details Definition Request message should be sent prior and the unique ID provided here
  • PartyDetailsListReqID≠0

For long messages:

  • If not registered beforehand through iLink, then the Party Details Definition Request message should be sent along with the business message immediately preceding it and that ID provided here (ID should be designated as 0).
  • If the Party Details Definition Request message is received with PartyDetailsListReqID=0, then the very next message must be a business message also with PartyDetailsListReqID=0, else the next message will be rejected.

Order quantity. Must be the same for both sides.

  • Side=1 (Buy)
  • Side=2 (Sell)
Side of order.
  • SideTimeInForce=0 (Day)
  • SideTimeInForce=3 (FAK)
Indicates how long the order as specified in the side stays in effect. SideTimeInForce allows a two-sided cross order to specify order behavior separately for each side.

  • No labels