The Execution Report Acknowledgement message is an optional message that provides dual functionality to notify a trading partner that an electronically received execution has either been accepted or rejected (DK’d).

Added in protocol FIX.4.4

See in: FIX.5.0, FIX.5.0SP1, FIX.5.0SP2 EP240.

Field or Component Name Description Is Required Added Is Deprecated
Block StandardHeader MsgType = BN Y FIX.4.4
37 OrderID Y FIX.4.4
198 SecondaryOrderID FIX.4.4
11 ClOrdID Conditionally required if the Execution Report message contains a ClOrdID. FIX.4.4
1036 ExecAckStatus Indicates the status of the execution acknowledgement. The "received, not yet processed" is an optional intermediary status that can be used to notify the counterparty that the Execution Report has been received. Y FIX.4.4
17 ExecID The ExecID of the Execution Report being acknowledged. Y FIX.4.4
127 DKReason Conditionally required when ExecAckStatus = 2 (Don’t know / Rejected). FIX.4.4
Block Instrument Y FIX.4.4
OptimisedImplicitBlockRepeating UndInstrmtGrp FIX.4.4
OptimisedImplicitBlockRepeating InstrmtLegGrp FIX.4.4
54 Side Y FIX.4.4
Block OrderQtyData Y FIX.4.4
32 LastQty Conditionally required if specified on the Execution Report FIX.4.4
31 LastPx Conditionally Required if specified on the Execution Report FIX.4.4
423 PriceType Conditionally required if specified on the Execution Report FIX.4.4
669 LastParPx Conditionally required if specified on the Execution Report FIX.4.4
14 CumQty Conditionally required if specified on the Execution Report FIX.4.4
6 AvgPx Conditionally required if specified on the Execution Report FIX.4.4
58 Text Conditionally required if DKReason = "other" FIX.4.4
354 EncodedTextLen FIX.4.4
355 EncodedText FIX.4.4
Block StandardTrailer Y FIX.4.4