Message
| ID | 15 |
| Pedigree | Added FIX.2.7, Updated FIX.4.1 |
The new order list message type is used by institutions wishing to electronically submit lists of related orders to a broker for execution.
The New Order List is intended for use in staging lists to be executed by the broker. If the institution wishes to work a list using the broker's execution services, the orders should be submitted as individual New Order - Single's.
After staging, the list can be operated on in the following ways:
| Execute | The broker can be instructed to release the list for execution by sending the List-Execute message. |
| Cancel | After the list has been staged with the broker, it can be canceled via the submission of the List Cancel message. If the list has not yet been submitted for execution, the List Cancel message will instruct the broker not to execute it, if the list is being executed, the List Cancel message should trigger the broker's system to generate cancel requests for the remaining quantities of each order within the list. Individual orders within the list can be canceled via the Order Cancel Request message. |
| Status | A status of the list can be requested via the submission of the List-Status Request message. The broker will respond with one or more List-Status messages which will report executed quantity, canceled quantity and average price for each order in the list. |
| Replace | Individual orders within the list can be replaced via Order Cancel/Replace Request messages. |
Executions against orders within the list will not normally be reported as they occur. (If this feature is desired the institution and broker should arrange for this reporting as a custom feature using the Execution message.) Executions against the list will be reported within the List-Status message.
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
StandardHeader | Y | MsgType = E | Added FIX.2.7 | ||
66 | Y | Must be unique, by customer, for the day | Added FIX.2.7 | ||
105 | Added FIX.3.0 | ||||
67 | Y | Added FIX.2.7 | |||
68 | Y | Added FIX.2.7 | |||
69 | Include only in ListSeqNo = 1 message | Added FIX.2.7 | |||
11 | Y | Unique identifier of the order as assigned by institution. | Added FIX.2.7 Updated FIX.4.1 | ||
109 | Used for third-party transactions | Added FIX.4.0 | |||
76 | Used for third-party transactions | Added FIX.4.0 | |||
1 | Added FIX.2.7 | ||||
63 | Absence of this field is interpreted as Regular. | Added FIX.2.7 | |||
64 | Required when SettlmntTyp = 6 (Future) or SettlmntTyp = 8 (Sellers Option) | Added FIX.2.7 | |||
21 | Y | Added FIX.2.7 | |||
18 | Can contain multiple instructions, space delimited. | Added FIX.2.7 Updated FIX.3.0 | |||
110 | Added FIX.3.0 | ||||
111 | Added FIX.3.0 | ||||
100 | Added FIX.2.7 | ||||
81 | Added FIX.4.0 | ||||
55 | Y | Added FIX.2.7 | |||
65 | Added FIX.2.7 | ||||
48 | Added FIX.2.7 | ||||
22 | Added FIX.2.7 | ||||
167 | Must be specified if a Future or Option. If a Future: Symbol, SecurityType, and MaturityMonthYear are required. If an Option: Symbol, SecurityType, MaturityMonthYear, PutOrCall, and StrikePrice are required. | Added FIX.4.1 | |||
200 | For Options or Futures to specify the month and year of maturity. | Added FIX.4.1 | |||
205 | For Options or Futures and can be used in conjunction with MaturityMonthYear to specify a particular maturity date. | Added FIX.4.1 | |||
201 | For Options. | Added FIX.4.1 | |||
202 | For Options. | Added FIX.4.1 | |||
206 | For Options. | Added FIX.4.1 | |||
207 | Can be used to identify the security. | Added FIX.4.1 | |||
106 | Added FIX.3.0 | ||||
107 | Added FIX.3.0 | ||||
140 | Useful for verifying security identification | Added FIX.4.0 | |||
54 | Y | Added FIX.2.7 | |||
114 | Required for short sell orders | Added FIX.4.0 | |||
38 | Y | Added FIX.2.7 | |||
40 | Y | Added FIX.2.7 | |||
44 | Required for limit OrdTypes. For F/X orders, should be the “all-in” rate (spot rate adjusted for forward points). Can be used to specify a limit price for a pegged order, previously indicated, etc. | Added FIX.2.7 Updated FIX.4.1 | |||
99 | Required for OrdType = “Stop” or OrdType = “Stop limit”. | Added FIX.2.7 Updated FIX.4.1 | |||
211 | Added FIX.4.1 | ||||
15 | Message without currency field is interpreted as US dollars | Added FIX.2.7 | |||
59 | Absence of this field indicates Day order | Added FIX.2.7 | |||
126 | Required in TimeInForce = GTD | Added FIX.4.0 | |||
12 | Added FIX.2.7 | ||||
13 | Added FIX.2.7 | ||||
47 | Added FIX.2.7 | ||||
121 | Indicates that broker is requested to execute a Forex accommodation trade in conjunction with the security trade. | Added FIX.4.0 | |||
120 | Required if ForexReq = Y. | Added FIX.4.0 | |||
58 | Added FIX.2.7 | ||||
193 | Can be used with OrdType = “Forex - Swap” to specify the “value date” for the future portion of a F/X swap. | Added FIX.4.1 | |||
192 | Can be used with OrdType = “Forex - Swap” to specify the order quantity for the future portion of a F/X swap. | Added FIX.4.1 | |||
77 | For options | Added FIX.4.1 | |||
203 | For options | Added FIX.4.1 | |||
204 | For options when delivering the order to execution system/exchange. | Added FIX.4.1 | |||
210 | Added FIX.4.1 | ||||
StandardTrailer | Y | Added FIX.2.7 |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Service|Privacy Policy