Message NewOrderList (E)

The NewOrderList Message can be used in one of two ways depending on which market conventions are being followed.

Added in protocol FIX.2.7

See in: FIX.4.0, FIX.4.1, FIX.4.2, FIX.4.3, FIX.4.4, FIX.5.0, FIX.5.0SP1, FIX.5.0SP2.

Field or Component Name Description Is Required Added Is Deprecated
Block StandardHeader MsgType = E Y FIX.2.7
66 ListID Must be unique, by customer, for the day Y FIX.2.7
390 BidID Should refer to an earlier program if bidding took place. FIX.4.2
391 ClientBidID FIX.4.2
414 ProgRptReqs FIX.4.2
394 BidType e.g. Non Disclosed Model, Disclosed Model, No Bidding Process Y FIX.4.2
415 ProgPeriodInterval FIX.4.2
480 CancellationRights For CIV - Optional FIX.4.3
481 MoneyLaunderingStatus FIX.4.3
513 RegistID Reference to Registration Instructions message applicable to all Orders in this List. FIX.4.3
433 ListExecInstType Controls when execution should begin For CIV Orders indicates order of execution.. FIX.4.2
69 ListExecInst Free-form text. FIX.2.7
1385 ContingencyType Used for contingency orders. FIX.5.0
352 EncodedListExecInstLen Must be set if EncodedListExecInst (353) field is specified and must immediately precede it. FIX.4.2
353 EncodedListExecInst Encoded (non-ASCII characters) representation of the ListExecInst (69) field in the encoded format specified via the MessageEncoding (347) field. FIX.4.2
765 AllowableOneSidednessPct The maximum percentage that execution of one side of a program trade can exceed execution of the other. FIX.4.4
766 AllowableOneSidednessValue The maximum amount that execution of one side of a program trade can exceed execution of the other. FIX.4.4
767 AllowableOneSidednessCurr The currency that AllowableOneSidedness is expressed in if AllowableOneSidednessValue is used. FIX.4.4
2401 ListManualOrderIndicator FIX.5.0SP2 (182)
68 TotNoOrders Used to support fragmentation. Sum of NoOrders across all messages with the same ListID. Y FIX.2.7
893 LastFragment Indicates whether this is the last fragment in a sequence of message fragments. Only required where message has been fragmented. FIX.4.4
BlockRepeating RootParties Insert here the set of "Root Parties" fields defined in "common components of application messages" Used for acting parties that applies to the whole message, not individual orders. FIX.4.4
ImplicitBlockRepeating ListOrdGrp Number of orders in this message (number of repeating groups to follow) Y FIX.4.4
1685 ThrottleInst FIX.5.0SP2 (116)
Block StandardTrailer Y FIX.2.7