Message SettlementInstructions Scenario base

SYNOPSIS: 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.

ID	MsgType	Abbr	Flow
28	T	SettlInstrctns

Pedigree

Added	EP	Updated	EP	Deprecated	EP
FIX.4.1

Responses

None

Members

SettlementInstructions base members

ID	Name	Abbr	Presence	Description
1024	StandardHeader	BaseHeader	required	SYNOPSIS: The standard FIX message header ELABORATION:
777	SettlInstMsgID	SettlInstMsgID	required	SYNOPSIS: Unique identifier for Settlement Instruction message.
791	SettlInstReqID	SettlInstReqID	optional	SYNOPSIS: Unique ID of settlement instruction request message
160	SettlInstMode	SettlInstMode	required	SYNOPSIS: Indicates mode used for Settlement Instructions message. * SOME VALUES HAVE BEEN REPLACED - See "Replaced Features and Supported Approach" *
792	SettlInstReqRejCode	SettlInstReqRejCode	optional	SYNOPSIS: Identifies reason for rejection (of a settlement instruction request message).
58	Text	Txt	optional	SYNOPSIS: Free format text string (Note: this field does not have a specified maximum length)
354	EncodedTextLen	EncTxtLen	optional	SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedText (355) field.
355	EncodedText	EncTxt	optional	SYNOPSIS: Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text(58) field.
11	ClOrdID	ClOrdID	optional	SYNOPSIS: Unique identifier for Order as assigned by the buy-side (institution, broker, intermediary etc.) (identified by SenderCompID (49) or OnBehalfOfCompID (5) as appropriate). Uniqueness must be guaranteed within a single trading day. Firms, particularly those which electronically submit multi-day orders, trade globally or throughout market close periods, should ensure uniqueness across days, for example by embedding a date within the ClOrdID field.
60	TransactTime	TxnTm	required	SYNOPSIS: Timestamp when the business transaction represented by the message occurred.
2057	SettlInstGrp	SetInst	optional	SYNOPSIS: ELABORATION:
1025	StandardTrailer	Trlr	required	SYNOPSIS: The standard FIX message trailer ELABORATION: