Skip to content
FIXtags

FIX MESSAGE 35=T

SettlementInstructions

MsgType (35) = TSettlementInstructionAdded FIX.4.1

Definition

The Settlement Instructions message provides the broker’s, the institution’s, or the intermediary’s instructions for trade settlement. This message has been designed so that it can be sent from the broker to the institution, from the institution to the broker, or from either to an independent "standing instructions" database or matching system or, for CIV, from an intermediary to a fund manager.

Message structure 91 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 = T

    StandardHeader definition & usage →

    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. 1128 ApplVerIDString—

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

    5. 1156 ApplExtIDint—
    6. 1129 CstmApplVerIDString—

      Used to support bilaterally agreed custom functionality

    7. 49 SenderCompIDStringRequired here

      (Always unencrypted)

    8. 56 TargetCompIDStringRequired here

      (Always unencrypted)

    9. 115 OnBehalfOfCompIDString—

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

    10. 128 DeliverToCompIDString—

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

    11. 90 SecureDataLenDeprecated FIX.5.0SP2Length—

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

    12. 91 SecureDataDeprecated FIX.5.0SP2data—

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

    13. 34 MsgSeqNumSeqNumRequired here

      (Can be embedded within encrypted data section.)

    14. 50 SenderSubIDString—

      (Can be embedded within encrypted data section.)

    15. 142 SenderLocationIDString—

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

    16. 57 TargetSubIDString—

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

    17. 143 TargetLocationIDString—

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

    18. 116 OnBehalfOfSubIDString—

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

    19. 144 OnBehalfOfLocationIDString—

      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.)

    20. 129 DeliverToSubIDString—

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

    21. 145 DeliverToLocationIDString—

      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.)

    22. 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.)

    23. 97 PossResendBoolean—

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

    24. 52 SendingTimeUTCTimestampRequired here

      (Can be embedded within encrypted data section.)

    25. 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.)

    26. 212 XmlDataLenLength—

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

    27. 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

    28. 347 MessageEncodingString—

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

    29. 369 LastMsgSeqNumProcessedSeqNum—

      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.

    30. 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.

      HopGrp definition & usage →

      1. 627 NoHopsGroup count—
      2. 628 HopCompIDString—
      3. 629 HopSendingTimeUTCTimestamp—
      4. 630 HopRefIDSeqNum—
  2. 777 SettlInstMsgIDStringRequired

    Unique identifier for this message

  3. 791 SettlInstReqIDString—

    Only used when this message is used to respond to a settlement instruction request (to which this ID refers)

  4. 160 SettlInstModecharRequired

    1=Standing Instructions, 2=Specific Allocation Account Overriding, 3=Specific Allocation Account Standing , 4=Specific Order, 5=Reject SSI request

  5. 792 SettlInstReqRejCodeint—

    Required for SettlInstMode = 5. Used to provide reason for rejecting a Settlement Instruction Request message.

  6. 58 TextString—

    Can be used to provide any additional rejection text where rejecting a Settlement Instruction Request message.

  7. 354 EncodedTextLenLength—
  8. 355 EncodedTextdata—
  9. 11 ClOrdIDString—

    Required for SettlInstMode(160) = 4 and when referring to orders that where electronically submitted over FIX or otherwise assigned a ClOrdID.

  10. 60 TransactTimeUTCTimestampRequired

    Date/time this message was generated

  11. SettlInstGrpRepeating groupCount tag 778—

    Required except where SettlInstMode is 5=Reject SSI request

    SettlInstGrp definition & usage →

    1. 778 NoSettlInstGroup count—

      Required except where SettlInstMode is 5=Reject SSI request

    2. 162 SettlInstIDString—

      Unique ID for this settlement instruction.

      Required except where SettlInstMode is 5=Reject SSI request

    3. 163 SettlInstTransTypechar—

      New, Replace, Cancel or Restate

      Required except where SettlInstMode is 5=Reject SSI request

    4. 214 SettlInstRefIDString—

      Required where SettlInstTransType is Cancel or Replace

    5. PartiesRepeating groupCount tag 453—

      Used here for settlement location.

      Also used for executing broker for CIV settlement instructions

      Parties definition & usage →

      1. 453 NoPartyIDsGroup count—

        Repeating group below should contain unique combinations of PartyID, PartyIDSource, and PartyRole

      2. 448 PartyIDString—

        Required if NoPartyIDs(453) > 0.

        Identification of the party.

      3. 447 PartyIDSourcechar—

        Required if NoPartyIDs(453) > 0.

        Used to identify classification source.

      4. 452 PartyRoleint—

        Required if NoPartyIDs(453) > 0.

        Identifies the type of PartyID(448).

      5. 2376 PartyRoleQualifierint—
      6. PtysSubGrpRepeating groupCount tag 802—

        Repeating group of Party sub-identifiers.

        PtysSubGrp definition & usage →

        1. 802 NoPartySubIDsGroup count—
        2. 523 PartySubIDString—
        3. 803 PartySubIDTypeint—
    6. 54 Sidechar—

      Can be used for SettleInstMode 1 if SSIs are being provided for a particular side.

    7. 460 Productint—

      Can be used for SettleInstMode 1 if SSIs are being provided for a particular product.

    8. 167 SecurityTypeString—

      Can be used for SettleInstMode 1 if SSIs are being provided for a particular security type (as alternative to CFICode).

    9. 461 CFICodeString—

      Can be used for SettleInstMode 1 if SSIs are being provided for a particular CFI (as identified by CFI code).

    10. 2891 UPICodeString—

      Can be used for SettleInstMode 1 if SSIs are being provided for a particular UPI (as identified by UPI code).

    11. 120 SettlCurrencyCurrency—

      Can be used for SettleInstMode 1 if SSIs are being provided for a particular settlement currency

    12. 2899 SettlCurrencyCodeSourceString—
    13. 168 EffectiveTimeUTCTimestamp—

      Effective (start) date/time for this settlement instruction.

      Required except where SettlInstMode is 5=Reject SSI request

    14. 126 ExpireTimeUTCTimestamp—

      Termination date/time for this settlement instruction.

    15. 779 LastUpdateTimeUTCTimestamp—

      Date/time this settlement instruction was last updated (or created if not updated since creation).

      Required except where SettlInstMode is 5=Reject SSI request

    16. SettlInstructionsDataComponent—

      SettlInstructionsData definition & usage →

      1. 172 SettlDeliveryTypeint—

        Required if AllocSettlInstType = 1 or 2

      2. 169 StandInstDbTypeint—

        Required if AllocSettlInstType = 3 (should not be populated otherwise)

      3. 170 StandInstDbNameString—

        Required if AllocSettlInstType = 3 (should not be populated otherwise)

      4. 171 StandInstDbIDString—

        Identifier used within the StandInstDbType

        Required if AllocSettlInstType = 3 (should not be populated otherwise)

      5. DlvyInstGrpRepeating groupCount tag 85—

        Required (and must be > 0) if AllocSettlInstType = 2 (should not be populated otherwise)

        DlvyInstGrp definition & usage →

        1. 85 NoDlvyInstGroup count—
        2. 165 SettlInstSourcechar—
        3. 787 DlvyInstTypechar—
        4. SettlPartiesRepeating groupCount tag 781—

          SettlParties definition & usage →

          1. 781 NoSettlPartyIDsGroup count—

            Repeating group below should contain unique combinations of SettlPartyID, SettlPartyIDSource, and SettlPartyRole

          2. 782 SettlPartyIDString—

            Used to identify source of SettlPartyID. Required if SettlPartyIDSource is specified. Required if NoSettlPartyIDs > 0.

          3. 783 SettlPartyIDSourcechar—

            Used to identify class source of SettlPartyID value (e.g. BIC). Required if SettlPartyID is specified. Required if NoSettlPartyIDs > 0.

          4. 784 SettlPartyRoleint—

            Identifies the type of SettlPartyID (e.g. Executing Broker). Required if NoSettlPartyIDs > 0.

          5. 2389 SettlPartyRoleQualifierint—
          6. SettlPtysSubGrpRepeating groupCount tag 801—

            Repeating group of SettlParty sub-identifiers.

            SettlPtysSubGrp definition & usage →

            1. 801 NoSettlPartySubIDsGroup count—
            2. 785 SettlPartySubIDString—
            3. 786 SettlPartySubIDTypeint—
    17. 492 PaymentMethodint—

      For use with CIV settlement instructions

    18. 476 PaymentRefString—

      For use with CIV settlement instructions

    19. 488 CardHolderNameString—

      For use with CIV settlement instructions

    20. 489 CardNumberString—

      For use with CIV settlement instructions

    21. 503 CardStartDateLocalMktDate—

      For use with CIV settlement instructions

    22. 490 CardExpDateLocalMktDate—

      For use with CIV settlement instructions

    23. 491 CardIssNumString—

      For use with CIV settlement instructions

    24. 504 PaymentDateLocalMktDate—

      For use with CIV settlement instructions

    25. 505 PaymentRemitterIDString—

      For use with CIV settlement instructions

  12. StandardTrailerComponentRequired

    StandardTrailer definition & usage →

    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)