| ID | 14 |
| Pedigree | Added FIX.2.7, Updated FIX.4.2 |
The new order message type is used by institutions wishing to electronically submit securities and forex orders to a broker for execution.
Orders can be submitted with special handling instructions and execution instructions. Handling instructions refer to how the broker should handle the order on its trading floor (see HandlInst field). Execution instructions contain explicit directions as to how the order should be executed (see ExecInst field).
New Order messages received with the PossResend flag set in the header should be validated by ClOrdID and order parameters (side, symbol, quantity, etc.) to determine if the order had been previously submitted. PossResends previously received should be acknowledged back to the client via an Execution - Status message. PossResends not previously received should be processed as a new order and acknowledged via an Execution - New message.
The value specified in the TransactTime field should allow the receiver of the order to apply business rules to determine if the order is potentially "stale" (e.g. in the event that there have been communication problems). To support forex accommodation trades, two fields, ForexReq and SettlCurrency, are included in the message. To request a broker to execute a forex trade in conjunction with the securities trade, the institution would set the ForexReq = Y and SettlCurrency = “intended settlement currency”. The broker would then execute a forex trade from the execution currency to the settlement currency and report the results via the execution message in the SettlCurrAmt and SettlCurrency fields.
The order message can also be used to request a straight forex trade. Conventions for identifying a forex transaction are as follows:
- The forex
Symbolis defined in "EBS" (Electronic Banking System) format: "CCY1/CCY2". - Rates are expressed as "currency1 in currency2" (or "currency2 per currency1") and are calculated as CCY2 divided by CCY1 (NOT CCY1 divided by CCY2)
- (e.g. "GBP/USD" represents a rate expressed as USD per GBP, "USD/JPY" represents a rate expressed as JPY per USD, etc.).
- CCY1 and CCY2 are ISO currency codes
- The value of the
Currencyfield represents the denomination of the quantity fields (e.g. JPY represents quantity of JPY). - In the case of a Forex - Swap (buying (or selling) a currency at one value date and selling (or buying) the same currency at a different value date), Side should represent the side of the
FutSettDate2transaction. OrdType= Forex - Market, Forex - Limit, Forex- Swap, or Forex - Previously Quoted- Netting can be specified via the
ExecInstfield. - See Appendix O – Foreign Exchange Trading
Orders involving or requiring Pre-Trade Allocation consist of the following steps:
- Buyside sends a New Order request message specifying one or more
AllocAccountandAllocSharesvalues within the repeating group designated byNoAllocs. - Sellside sends Execution Report messages for the “New” and resulting fills.
- Post-Trade Allocation messaging takes place
To “take” an IOI (or Quote) from an ECN or exchange and not display the order on the book, the New Order message should contain the TimeInForce field with ImmediateOrCancel and an OrdType field with Previously Indicated ( or Previously Quoted).
The presence of DiscretionInst on an order indicates that the trader wishes to display one price but will accept trades at another price. For example a sell order with OrdType = Limit, Price=50.00, DiscretionInst = Related to displayed price and DiscretionOffset = -0.25 means that the order should be displayed as an offer for 50.00, but will match any bid >= 49.75 Discretionary pricing can also be used when pegging an order - for example to indicate that a buy order is to be displayed as pegged to the bid minus 0.25, but can be matched by anything <= the offer, set OrdType=Pegged, ExecInst = Primary Peg, PegDifference = -0.25, DiscretionInst = Related to market price and DiscretionOffset = 0.
See Appendix D: Order State Change Matrices
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
StandardHeader | Y | MsgType = D | Added FIX.2.7 | ||
11 | Y | Added FIX.2.7 | |||
109 | Used for firm identification in third-party transactions. | Added FIX.3.0 | |||
76 | Used for firm identification in third-party transactions. | Added FIX.3.0 | |||
1 | Added FIX.2.7 | ||||
PreAllocGrp | Number of repeating groups for pre-trade allocation | Added FIX.4.2 | |||
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 | ||||
TrdgSesGrp | Specifies the number of repeating TradingSessionIDs | Added FIX.4.2 | |||
81 | Used to identify soft trades at order entry. | Added FIX.2.7 | |||
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 | |||
231 | For Fixed Income, Convertible Bonds, Derivatives, etc. Note: If used, quantities should be expressed in the "nominal" (e.g. contracts vs. shares) amount. | Added FIX.4.2 | |||
223 | For Fixed Income. | Added FIX.4.2 | |||
207 | Can be used to identify the security. | Added FIX.4.1 | |||
106 | Added FIX.3.0 | ||||
348 | Must be set if EncodedIssuer field is specified and must immediately precede it. | Added FIX.4.2 | |||
349 | Encoded (non-ASCII characters) representation of the Issuer field in the encoded format specified via the MessageEncoding field. | Added FIX.4.2 | |||
107 | Added FIX.3.0 | ||||
350 | Must be set if EncodedSecurityDesc field is specified and must immediately precede it. | Added FIX.4.2 | |||
351 | Encoded (non-ASCII characters) representation of the SecurityDesc field in the encoded format specified via the MessageEncoding field. | Added FIX.4.2 | |||
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 | |||
60 | Y | Time this order request was initiated/released by the trader or trading system. | Added FIX.4.2 | ||
38 | Either CashOrderQty or OrderQty is required. | Added FIX.2.7 Updated FIX.4.1 | |||
152 | Either CashOrderQty or OrderQty is required. Specifies the approximate “monetary quantity” for the order. Broker is responsible for converting and calculating OrderQty in shares for subsequent messages. | Added FIX.4.1 Updated FIX.4.2 | |||
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 | |||
15 | Added FIX.2.7 Updated FIX.4.1-errata1 | ||||
376 | Added FIX.4.2 | ||||
377 | Added FIX.4.2 | ||||
23 | Required for Previously Indicated Orders (OrdType=E) | Added FIX.4.0 | |||
117 | Required for Previously Quoted Orders (OrdType=D) | Added FIX.4.0 | |||
59 | Absence of this field indicates Day order | Added FIX.2.7 | |||
168 | Can specify the time at which the order should be considered valid | Added FIX.4.2 | |||
432 | Conditionally required if TimeInForce = GTD and ExpireTime is not specified. | Added FIX.4.2 | |||
126 | Conditionally required if TimeInForce = GTD and ExpireDate is not specified. | Added FIX.4.0 Updated FIX.4.2 | |||
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 | ||||
354 | Must be set if EncodedText field is specified and must immediately precede it. | Added FIX.4.2 | |||
355 | Encoded (non-ASCII characters) representation of the Text field in the encoded format specified via the MessageEncoding field. | Added FIX.4.2 | |||
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 | ||||
211 | Amount (signed) added to the price of the peg | Added FIX.4.1 Updated FIX.4.2 | |||
388 | Code to identify the price a DiscretionOffset is related to and should be mathematically added to. Required if DiscretionOffset is specified. | Added FIX.4.2 | |||
389 | Amount (signed) added to the “related to” price specified via DiscretionInst. | Added FIX.4.2 | |||
439 | Added FIX.4.2 | ||||
440 | Added FIX.4.2 | ||||
StandardTrailer | Y | Added FIX.2.7 |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Service|Privacy Policy