SecuritiesSettlementTransactionGenerationNotification002V11

Scope
An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer.
The account servicer/owner relationship may be:
- a central securities depository or another settlement market infrastructure acting on behalf of their participants
- an agent (sub-custodian) acting on behalf of their global custodian customer, or
- a custodian acting on behalf of an investment management institution or a broker/dealer

Usage
The message may also be used to:
- re-send a message previously sent,
- provide a third party with a copy of a message for information,
- re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

Message Identifier: sese.032.002.11

Elements

Name	Type	Multiplicity	Definition
TransactionIdentificationDetails	SettlementTypeAndIdentification28	[1..1]	Provides transaction type and identification information.
NumberCounts	NumberCount2Choice	[0..1]	Count of the number of transactions linked.
Linkages	Linkages68		Link to another transaction that must be processed after, before or at the same time.
TradeDetails	SecuritiesTradeDetails130	[1..1]	Details of the trade.
FinancialInstrumentIdentification	SecurityIdentification20	[1..1]	Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
FinancialInstrumentAttributes	FinancialInstrumentAttributes122	[0..1]	Elements characterising a financial instrument.
QuantityAndAccountDetails	QuantityAndAccount104	[1..∞]	Details related to the account and quantity involved in the transaction.
SettlementParameters	SettlementDetails212	[1..1]	Parameters which explicitly state the conditions that must be fulfilled before a particular transaction of a financial instrument can be settled. These parameters are defined by the instructing party in compliance with settlement rules in the market the transaction will settle in.
DeliveringSettlementParties	SettlementParties105	[0..1]	Identifies the chain of delivering settlement parties.
ReceivingSettlementParties	SettlementParties105	[0..1]	Identifies the chain of receiving settlement parties.
CashParties	CashParties38	[0..1]	Cash parties involved in the transaction if different from the securities settlement parties.
SettlementAmount	AmountAndDirection96	[0..1]	Total amount of money to be paid or received in exchange for the securities.
OtherAmounts	OtherAmounts43	[0..1]	Other amounts than the settlement amount.
OtherBusinessParties	OtherParties44	[0..1]	Other business parties relevant to the transaction.
AdditionalPhysicalOrRegistrationDetails	RegistrationParameters7	[0..1]	Information for registration or physical settlement.
GeneratedReason	GeneratedReason6		Specifies the reason why the transaction was generated.
StatusAndReason	StatusAndReason29	[0..1]	Status and reason of the transaction.
SupplementaryData	SupplementaryData1		Additional information that cannot be captured in the structured elements and/or any other specific block.

Validation Rules

SettlementAmountRule: If the instruction is against payment, then SettlementAmount must be present.

ReceivingDepositoryAndParty1Rule: If the instruction is a delivery and no standing settlement instruction applies, then ReceivingDepository and Party1 must be present. .

AdditionalPhysicalOrRegistrationDetailsRule: If AdditionalPhysicalOrRegistrationDetails is used, then the instruction must be free of payment.

DeliveringDepositoryAndParty1Rule: If the instruction is a receive and no standing settlement instruction applies, then DeliveringDepository and Party1 must be present.

CurrencyToSellRule: If CurrencytoSell is used, then the instruction must be a receive.

CurrencyToBuyRule: If CurrencytoBuy is used, then the instruction must be a delivery.