| ID | 9 |
| Pedigree | Added FIX.2.7, Updated FIX.3.0 |
The execution report message is used to:
- confirm the receipt of an order
- confirm changes to an existing order (i.e. accept cancel and replace requests)
- relay order status information
- relay fill information as orders are worked
- reject orders
NOTE: Execution reports do not replace the end-of-day confirm. Execution reports are to be regarded only as replacements for the existing fill messages currently communicated via telephone.
Each execution message will contain information that will describe the current state of the order and execution status as understood by the broker.
Execution report messages can be transmitted as transaction types (ExecTranType) NEW, CANCEL, CORRECT or STATUS. Transaction types CANCEL and CORRECT modify the state of the message identified in field ExecRefID. Transaction type STATUS indicates that the execution message contains no new information, only summary information regarding order status.
- The NEW transaction type indicates that this message represents a new order, a change in status of the order, or a new fill against an existing order. The combination of the
ExecTransTypeandOrdStatusfields will indicate how the message is to be applied to an order. - The CANCEL transaction type applies at the execution level. The Cancel transaction will be used to cancel an execution which has been reported in error. The cancelled execution will be identified in the
ExecRefIDfield. - The CORRECT transaction type applies at the execution level and is used to modify an incorrectly reported fill. The incorrect execution will be identified in the
ExecRefIDfield. Note: Data reported in theCumQtyandAvgPxfields represent the status of the order as of the time of the correction, not as of the time of the originally reported execution.
The OrdStatus field is used to identify the status of the current order. The order statuses are as follows:
| New | Outstanding order with no executions |
| Partially Filled | Outstanding order with executions and remaining quantity |
| Filled | Order completely filled, no remaining quantity |
| Done | Order not, or partially, filled; no further executions forthcoming |
| Canceled | Canceled order with or without executions |
| Replaced | Replaced order with or without executions |
| Pending Cancel/Replace | Order with cancel request pending, used to confirm receipt of cancel or replace request. DOES NOT INDICATE THAT THE ORDER HAS BEEN CANCELED OR REPLACED. |
| Stopped | Order has been stopped at the exchange |
| Rejected | Order has been rejected by broker. NOTE: An order can be rejected subsequent to order acknowledgement, i.e. an order can pass from New to Rejected status. |
| Suspended | Order has been placed in suspended state at the request of the client. |
| Pending New | Order has been received by brokers system but not yet accepted for execution. An execution message with this status will only be sent in response to a Status Request message. |
NOTE: The canceled and replaced order status is set in response to accepted cancel and replace requests. These requests are only acted upon when there is an outstanding order quantity. Requests to replace OrderQty to a level less than the LeavesQty will be rejected (OrderQty = CumQty + LeavesQty). Requests to change price on a filled order will be rejected (see Order Cancel Reject message type).
The CumQty and AvgPx fields should be calculated to reflect the fills on all versions of an order. For example, if partially filled order A were replaced by order B, the CumQty and AvgPx on order B’s fills should represent the fills on order A plus those on order B.
The field ClOrdID is provided for institutions to affix an identification number to an order to coincide with internal systems. The OrderId field is populated with the broker-generated order number.
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
StandardHeader | Y | MsgType = 8 | Added FIX.2.7 | ||
37 | Y | Added FIX.2.7 | |||
11 | Required for executions against electronically submitted orders which were assigned an ID by the institution. Not required for orders manually entered by the broker. | 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 | |||
66 | Required for executions against orders which were submitted as part of a list. | Added FIX.2.7 | |||
17 | Y | Added FIX.2.7 | |||
20 | Y | Added FIX.2.7 | |||
19 | Required for Cancel and Correct ExecTransType messages | Added FIX.2.7 | |||
39 | Y | Added FIX.2.7 | |||
103 | For optional use with OrdStatus = 8 (Rejected) | Added FIX.2.7 | |||
1 | Required for executions against electronically submitted orders which were assigned an account by the institution | 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 | |||
55 | Y | Added FIX.2.7 | |||
65 | Added FIX.2.7 | ||||
48 | Added FIX.2.7 | ||||
22 | Added FIX.2.7 | ||||
106 | Added FIX.3.0 | ||||
107 | Added FIX.3.0 | ||||
54 | Y | Added FIX.2.7 | |||
38 | Y | Added FIX.2.7 | |||
44 | Added FIX.2.7 | ||||
99 | Required for OrdType = 4 (Stop Limit). | Added FIX.2.7 | |||
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 | |||
18 | Can contain multiple instructions, space delimited. | Added FIX.2.7 Updated FIX.3.0 | |||
47 | Added FIX.2.7 | ||||
32 | Y | Not required ExecTransType = 3 (Status) | Added FIX.2.7 Updated FIX.3.0 | ||
31 | Y | Not required for ExecTransType = 3 (Status) | Added FIX.2.7 Updated FIX.3.0 | ||
30 | Added FIX.2.7 | ||||
29 | Added FIX.2.7 | ||||
14 | Y | Added FIX.2.7 Updated FIX.3.0 | |||
6 | Y | Added FIX.2.7 Updated FIX.3.0 | |||
75 | Used when reporting other than current day trades. | Added FIX.3.0 | |||
60 | Added FIX.2.7 | ||||
113 | Added FIX.3.0 | ||||
58 | Added FIX.2.7 | ||||
StandardTrailer | Y | Added FIX.2.7 |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Service|Privacy Policy