Skip to content

FIX MESSAGE 35=BH

ConfirmationRequest

MsgType (35) = BHConfirmationAdded FIX.4.4

Definition

The Confirmation Request message is used to request a Confirmation message.

Message structure 66 distinct fields

Source order, including nested components and groups. Group counts precede the repeated entries. “Required here” is relative to the enclosing component or group, not unconditional in the message. A dash means not marked required; conditional requirements remain in the source notes. This is a reference, not a counterparty-specific validator.

  1. StandardHeaderComponentRequired

    MsgType = BH

    1. 8 BeginStringStringRequired here

      FIX session profile (Always unencrypted, must be first field in message)

    2. 9 BodyLengthLengthRequired here

      (Always unencrypted, must be second field in message)

    3. 35 MsgTypeStringRequired here

      (Always unencrypted, must be third field in message)

    4. Indicates application version using a service pack identifier. The ApplVerID applies to a specific message occurrence.

    5. Used to support bilaterally agreed custom functionality

    6. 49 SenderCompIDStringRequired here

      (Always unencrypted)

    7. 56 TargetCompIDStringRequired here

      (Always unencrypted)

    8. Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

    9. Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

    10. 90 SecureDataLenDeprecated FIX.5.0SP2Length

      Required to identify length of encrypted section of message. (Always unencrypted)

    11. 91 SecureDataDeprecated FIX.5.0SP2data

      Required when message body is encrypted. Always immediately follows SecureDataLen field.

    12. 34 MsgSeqNumSeqNumRequired here

      (Can be embedded within encrypted data section.)

    13. (Can be embedded within encrypted data section.)

    14. Sender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

    15. "ADMIN" reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)

    16. Trading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

    17. Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    18. Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    19. Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    20. Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    21. 43 PossDupFlagBoolean

      Always required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.)

    22. 97 PossResendBoolean

      Required when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)

    23. 52 SendingTimeUTCTimestampRequired here

      (Can be embedded within encrypted data section.)

    24. 122 OrigSendingTimeUTCTimestamp

      Required for message resent as a result of a ResendRequest. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.)

    25. Required when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.)

    26. 213 XmlDataXMLData

      Can contain a XML formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.)

      See Volume 1: FIXML Support

    27. Type of message encoding (non-ASCII characters) used in a message's "Encoded" fields. Required if any "Encoding" fields are used.

    28. The last MsgSeqNum value received by the FIX engine and processed by downstream application, such as trading system or order routing system. Can be specified on every message sent. Useful for detecting a backlog with a counterparty.

    29. HopGrpRepeating groupCount tag 627

      Number of repeating groups of historical "hop" information. Only applicable if OnBehalfOfCompID is used, however, its use is optional. Note that some market regulations or counterparties may require tracking of message hops.

      1. 627 NoHopsGroup count
      2. 628 HopCompIDString
      3. 629 HopSendingTimeUTCTimestamp
      4. 630 HopRefIDSeqNum
  2. 859 ConfirmReqIDStringRequired

    Unique identifier for this message

  3. 773 ConfirmTypeintRequired

    Denotes whether this message is being used to request a confirmation or a trade status message

  4. OrdAllocGrpRepeating groupCount tag 73

    Indicates number of orders to be combined for allocation. If order(s) were manually delivered set to 1 (one).Required when AllocNoOrdersType = 1

    1. 73 NoOrdersGroup count

      Indicates number of orders to be combined for allocation. If order(s) were manually delivered set to 1 (one).Required when AllocNoOrdersType = 1

    2. 11 ClOrdIDString

      Order identifier assigned by client if order(s) were electronically delivered over FIX (or otherwise assigned a ClOrdID) and executed. If order(s) were manually delivered (or otherwise not delivered over FIX) this field should contain string "MANUAL". Note where an order has undergone one or more cancel/replaces, this should be the ClOrdID of the most recent version of the order.

      Required when NoOrders(73) > 0 and must be the first repeating field in the group.

    3. 37 OrderIDString
    4. Can be used to provide order id used by exchange or executing system.

    5. 66 ListIDString

      Required for List Orders.

    6. NestedParties2Repeating groupCount tag 756

      This is used to identify the executing broker for step in/give in trades

      1. 756 NoNested2PartyIDsGroup count

        Repeating group below should contain unique combinations of Nested2PartyID, Nested2PartyIDSource, and Nested2PartyRole

      2. Used to identify source of Nested2PartyID. Required if Nested2PartyIDSource is specified. Required if NoNested2PartyIDs > 0.

      3. Used to identify class source of Nested2PartyID value (e.g. BIC). Required if Nested2PartyID is specified. Required if NoNested2PartyIDs > 0.

      4. Identifies the type of Nested2PartyID (e.g. Executing Broker). Required if NoNested2PartyIDs > 0.

      5. NstdPtys2SubGrpRepeating groupCount tag 806

        Repeating group of Nested2Party sub-identifiers.

    7. Average price for this order.

      For FX, if specified, expressed in terms of Currency(15).

    8. Quantity of this order that is being booked out by this message (will be equal to or less than this order's OrderQty)

      Note that the sum of the OrderBookingQty values in this repeating group must equal the total quantity being allocated (in Quantity (53) field)

    9. 40 OrdTypechar
  5. 70 AllocIDString

    Used to refer to an earlier Allocation Instruction.

  6. Used to refer to an earlier Allocation Instruction via its secondary identifier

  7. Used to refer to an allocation account within an earlier Allocation Instruction.

  8. 60 TransactTimeUTCTimestampRequired

    Represents the time this message was generated

  9. Account number for the trade being confirmed by this message

  10. 58 TextString
  11. StandardTrailerComponentRequired
    1. 93 SignatureLengthDeprecated FIX.5.0SP2Length

      Required when trailer contains signature. Note: Not to be included within SecureData field

    2. 89 SignatureDeprecated FIX.5.0SP2data

      Note: Not to be included within SecureData field

    3. 10 CheckSumStringRequired here

      (Always unencrypted, always last field in message)