SettlementInstructions

StandardHeader definition & usage →

1. 8 BeginStringStringRequired here

   FIX.4.4 (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. 49 SenderCompIDStringRequired here

   (Always unencrypted)

5. 56 TargetCompIDStringRequired here

   (Always unencrypted)

6. 115 OnBehalfOfCompIDString—

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

7. 128 DeliverToCompIDString—

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

8. 90 SecureDataLenLength—

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

9. 91 SecureDatadata—

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

10. 34 MsgSeqNumSeqNumRequired here

    (Can be embedded within encrypted data section.)

11. 50 SenderSubIDString—

    (Can be embedded within encrypted data section.)

12. 142 SenderLocationIDString—

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

13. 57 TargetSubIDString—

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

14. 143 TargetLocationIDString—

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

15. 116 OnBehalfOfSubIDString—

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

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

17. 129 DeliverToSubIDString—

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

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

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

20. 97 PossResendBoolean—

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

21. 52 SendingTimeUTCTimestampRequired here

    (Can be embedded within encrypted data section.)

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

23. 212 XmlDataLenLength—

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

24. 213 XmlDatadata—

    Can contain an XML formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.) See Volume 1: FIXML Support

25. 347 MessageEncodingString—

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

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

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

    Hop definition & usage →

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

SettlInstGrp definition & usage →

1. 778 NoSettlInstGroup count—
2. 162 SettlInstIDString—
3. 163 SettlInstTransTypechar—
4. 214 SettlInstRefIDString—
5. PartiesRepeating groupCount tag 453—

   Parties definition & usage →

   1. 453 NoPartyIDsGroup count—

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

   2. 448 PartyIDString—

      Used to identify source of PartyID. Required if PartyIDSource is specified. Required if NoPartyIDs > 0.

   3. 447 PartyIDSourcechar—

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

   4. 452 PartyRoleint—

      Identifies the type of PartyID (e.g. Executing Broker). Required if NoPartyIDs > 0.

   5. 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—
7. 460 Productint—
8. 167 SecurityTypeString—
9. 461 CFICodeString—
10. 168 EffectiveTimeUTCTimestamp—
11. 126 ExpireTimeUTCTimestamp—
12. 779 LastUpdateTimeUTCTimestamp—
13. 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. SettlPtysSubGrpRepeating groupCount tag 801—

             Repeating group of SettlParty sub-identifiers.

             SettlPtysSubGrp definition & usage →

             1. 801 NoSettlPartySubIDsGroup count—
             2. 785 SettlPartySubIDString—
             3. 786 SettlPartySubIDTypeint—
14. 492 PaymentMethodint—
15. 476 PaymentRefString—
16. 488 CardHolderNameString—
17. 489 CardNumberString—
18. 503 CardStartDateLocalMktDate—
19. 490 CardExpDateLocalMktDate—
20. 491 CardIssNumString—
21. 504 PaymentDateLocalMktDate—
22. 505 PaymentRemitterIDString—

StandardTrailer definition & usage →

1. 93 SignatureLengthLength—

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

2. 89 Signaturedata—

   Note: Not to be included within SecureData field

3. 10 CheckSumStringRequired here

   (Always unencrypted, always last field in message)