Indexes

Message Layouts
Session
PreTrade
Trade
PostTrade

  • Documentation

  • Message

    ExecutionReport (8)

    ID9
    PedigreeAdded FIX.2.7

    The execution report message is used to:

    1. confirm the receipt of an order
    2. confirm changes to an existing order (i.e. accept cancel and replace requests)
    3. relay order status information
    4. relay fill information as orders are worked

    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 ExecTransType and OrdStatus fields 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 incorrect execution will be identified in the ExecRefID field.
    • 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 ExecRefID field. Note: Data reported in the CumQty and AvgPx fields 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:

    NewOutstanding order with no executions
    Partially FilledOutstanding order with executions and remaining quantity
    FilledOrder completely filled, no remaining quantity
    DoneOrder not, or partially, filled; no further executions forthcoming
    CanceledCanceled order with or without executions
    ReplacedReplaced order with or without executions
    Pending Cancel/ReplaceOrder with cancel request pending, used to confirm receipt of cancel or replace request. DOES NOT INDICATE THAT THE ORDER HAS BEEN CANCELED OR REPLACED.
    StoppedOrder has been stopped at the exchange
    RejectedOrder 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.

    NOTE: The canceled and replaced order status are 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 field ClOrdID is provided for institutions to affix an identification number to an order to coincide with internal systems. The OrdId field is populated with a broker generated order number.

    Field
    Name
    Type
    Req'd
    Comments
    Pedigree
    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
    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
    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
    May be defined repeated times in a single message to indicate multiple instructions
    Added FIX.2.7
    47
    Added FIX.2.7
    32
    Y
    Not required for OrdStatus = 0 (New) or ExecTransType = 3 (Status)
    Added FIX.2.7
    31
    Y
    Not required for OrdStatus = 0 (New) or ExecTransType = 3 (Status)
    Added FIX.2.7
    30
    Added FIX.2.7
    29
    Added FIX.2.7
    14
    Y
    Not required for OrdStatus = 0 (New)
    Added FIX.2.7
    6
    Y
    Not required for OrdStatus = 0 (New)
    Added FIX.2.7
    60
    Added FIX.2.7
    58
    Added FIX.2.7
    Y
    Added FIX.2.7

    Orchimate Copyright 2026 Atomic Wire Technology Limited
    Orchestra Copyright 2026 FIX Protocol Ltd
    Terms of Service|Privacy Policy