Definition
The Settlement Instructions message provides either the broker’s or the institution’s instructions for trade settlement.
FIX 4.2 group names/IDs were assigned during the official Orchestra translation; some mappings to later versions are approximate. This layout stays within the 4.2 source.
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.
StandardHeaderComponentRequired
MsgType = T
StandardHeader definition & usage →
FIX.4.2 (Always unencrypted, must be first field in message)
(Always unencrypted, must be second field in message)
(Always unencrypted, must be third field in message)
(Always unencrypted)
(Always unencrypted)
Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)
Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)
Required to identify length of encrypted section of message. (Always unencrypted)
Required when message body is encrypted. Always immediately follows SecureDataLen field.
(Can be embedded within encrypted data section.)
(Can be embedded within encrypted data section.)
Sender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)
"ADMIN" reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)
Trading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)
Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)
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.)
Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)
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.)
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.)
Required when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)
(Can be embedded within encrypted data section.)
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.)
Required when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.)
Can contain an XML-formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.) See Appendix M – FIXML Support
Type of message encoding (non-ASCII characters) used in a message’s "Encoded" fields. Required if any "Encoding" fields are used.
The last MsgSeqNum value received and processed. Can be specified on every message sent. Useful for detecting a backlog with a counterparty.
Used when a message is sent via a "hub" or "service bureau". If A sends to Q (the hub) who then sends to B via a separate FIX session, then when Q sends to B the value of this field should represent the SendingTime on the message A sent to Q. (always expressed in UTC (Universal Time Coordinated, also known as "GMT")
Unique message ID regardless of SettlInstMode
New, Replace, or Cancel
Required for Cancel and Replace SettlInstTransType messages
1=Standing Instructions, 2=Specific Allocation Account Overriding, 3=Specific Allocation Account Standing
1=Broker’s Settlement Instructions, 2=Institution’s Settlement Instructions
Required for SettlInstMode=1, 2, or 3
Required for SettlInstMode=2 or 3, may be required for SettlInstMode=1 (i.e. may not be required if StandInstDbType and StandInstDbID are used)
Required for SettlInstMode=2 or 3
Required for SettlInstMode=2 or 3
Required for SettlInstMode=2 or 3, May be required for SettlInstMode=1
Required for SettlInstMode=2 or 3, May be required for SettlInstMode=1
May be required for SettlInstMode=1
May be required for SettlInstMode=1 (timestamp when it goes in to effect)
Date/Time Settlement Instructions were generated
Used for firm identification in third-party transactions (should not be a substitute for OnBehalfOfCompID/DeliverToCompID).
Used for firm identification in third-party transactions (should not be a substitute for OnBehalfOfCompID/DeliverToCompID).
1=DTC SID, 2=Thomson ALERT, 3=Global Custodian’s, etc.
Name of StandInstDbType (i.e. DTC, Global Custodian’s name)
Identifier used within the StandInstDbType
Applicable when SettlLocation is a depository
Applicable when settlement is being performed at a country vs. a depository
Applicable when settlement is being performed at a country vs. a depository
Applicable when settlement is being performed at a country vs. a depository
Applicable when settlement is being performed at a country vs. a depository
Applicable when settlement is being performed at a country vs. a depository
Applicable when settlement is being performed at a country vs. a depository
Applicable when SettlDeliveryType=Free
Applicable when SettlDeliveryType=Free
Applicable when SettlDeliveryType=Free
Applicable when SettlDeliveryType=Free
Applicable when SettlDeliveryType=Free
Applicable when SettlDeliveryType=Free
StandardTrailerComponentRequired
StandardTrailer definition & usage →
Required when trailer contains signature. Note: Not to be included within SecureData field
Note: Not to be included within SecureData field
(Always unencrypted, always last field in message)