sese: Securities Settlement
sese.030 Securities Settlement Conditions Modification Request
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
sese.030 is the ISO 20022 SecuritiesSettlementConditionsModificationRequest message in the Securities Settlement business area (sese). The latest version is sese.030.001.10, and 14 versions are in the repository.
- Message
- SecuritiesSettlementConditionsModificationRequest
- Latest version
- sese.030.001.10
- Submitting organisation
- Not read from the catalogue
- MT equivalent
- MT530
In use: published in the current ISO 20022 catalogue.
What sese.030 is for
An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.
The account owner/servicer relationship may be:
- a central securities depository participant which has an account with a central securities depository.
It could also be, if agreed in a service level agreement:
- a global custodian which has an account with its local agent (sub-custodian), or
- an investment management institution which manage a fund account opened at a custodian, or
- a broker which has an account with a custodian, or
- a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.
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.
In markets where this applies (for example, securities market infrastructures with no pre-settlement matching process), it is used by a party to approve, cancel or reject a transaction instructed by the counterparty.
This message cannot be used to request the modification of trade or event details.
The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice.
sese.030 versions
Every version published in the e-Repository, newest first. Variant 001 and 002 are listed together: a variant other than 001 is a restricted form of the same message with its own schema.
| Version | Registration status | Published in |
|---|---|---|
| sese.030.002.09 | Registered | Latest version set |
| sese.030.002.08 | Registered | Previous version set |
| sese.030.002.07 | Registered | Archive |
| sese.030.002.06 | Registered | Archive |
| sese.030.001.10latest | Registered | Latest version set |
| sese.030.001.09 | Registered | Previous version set |
| sese.030.001.08 | Registered | Archive |
| sese.030.001.07 | Registered | Archive |
| sese.030.001.06 | Registered | Archive |
| sese.030.001.05 | Registered | Archive |
| sese.030.001.04 | Registered | Archive |
| sese.030.001.03 | Registered | Archive |
| sese.030.001.02 | Registered | Archive |
| sese.030.001.01 | Registered | Archive |
sese.030 message structure
The building blocks of sese.030.001.10 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.
Document[1..1]SctiesSttlmCondsModReqSecuritiesSettlementConditionsModificationRequest [1..1]AcctOwnrAccount Owner [0..1]PartyIdentification144Party that legally owns the account.
IdIdentification [1..1]PartyIdentification127Choice (choice)Unique identification of the party.
AnyBICAny BIC [1..1]AnyBICDec2014IdentifierPrtryIdProprietary Identification [1..1]GenericIdentification36
LEILEI [0..1]LEIIdentifierLegal entity identification as an alternate identification for a party.
SfkpgAcctSafekeeping Account [0..1]SecuritiesAccount19Account to or from which a securities entry is made.
IdIdentification [1..1]Max35TextUnambiguous identification for the account between the account owner and the account servicer.
TpType [0..1]GenericIdentification30Specifies the type of securities account.
IdIdentification [1..1]Exact4AlphaNumericTextIssrIssuer [1..1]Max35TextSchmeNmScheme Name [0..1]Max35Text
NmName [0..1]Max70TextDescription of the account.
BlckChainAdrOrWlltBlock Chain Address Or Wallet [0..1]BlockChainAddressWallet3Blockchain address or wallet where digital assets are maintained.
IdIdentification [1..1]Max140TextUnambiguous identification for the account between the account owner and the account servicer.
TpType [0..1]GenericIdentification30Specifies the type of securities account.
IdIdentification [1..1]Exact4AlphaNumericTextIssrIssuer [1..1]Max35TextSchmeNmScheme Name [0..1]Max35Text
NmName [0..1]Max70TextDescription of the account.
ReqDtlsRequest Details [1..*]RequestDetails31Details of the request.
RefReference [1..1]References29References of the transaction for which the securities settlement condition modification is requested.
AcctOwnrTxIdAccount Owner Transaction Identification [0..1]Max35TextAcctSvcrTxIdAccount Servicer Transaction Identification [0..1]Max35TextMktInfrstrctrTxIdMarket Infrastructure Transaction Identification [0..1]Max35TextCtrPtyMktInfrstrctrTxIdCounterparty Market Infrastructure Transaction Identification [0..1]Max35TextPrcrTxIdProcessor Transaction Identification [0..1]Max35TextPoolIdPool Identification [0..1]Max35TextCmonIdCommon Identification [0..1]Max35TextTradIdTrade Identification [0..1]Max35TextUnqTxIdrUnique Transaction Identifier [0..1]UTIIdentifier
RstrctnRefRestriction Reference [0..*]RestrictionIdentification1Restriction references applied on the transaction for which the securities settlement condition modification is requested.
CdCode [1..1]RestrictionReference1CodeIdIdentification [1..1]Max35Text
AutomtcBrrwgAutomatic Borrowing [0..1]AutomaticBorrowing7Choice (choice)Condition for automatic borrowing.
CdCode [1..1]AutoBorrowing2CodePrtryProprietary [1..1]GenericIdentification30
RtnIndRetain Indicator [0..1]YesNoIndicatorIndicates whether the instruction due to expire is confirmed for settlement.
LkgLinkage [0..1]LinkageType3Choice (choice)Specifies the type of linkage requested.
CdCode [1..1]LinkageType1CodePrtryProprietary [1..1]GenericIdentification30
PrtyPriority [0..1]PriorityNumeric4Choice (choice)Specifies whether the transaction is to be executed with a high priority.
NmrcNumeric [1..1]Exact4NumericTextPrtryProprietary [1..1]GenericIdentification30
OthrPrcgOther Processing [0..*]GenericIdentification30Specifies another type of processing change request.
IdIdentification [1..1]Exact4AlphaNumericTextIssrIssuer [1..1]Max35TextSchmeNmScheme Name [0..1]Max35Text
PrtlSttlmIndPartial Settlement Indicator [0..1]SettlementTransactionCondition5CodeSpecifies whether partial settlement is allowed.
SctiesRTGSSecurities RTGS [0..1]SecuritiesRTGS4Choice (choice)Specifies whether the settlement transaction is to be settled through an RTGS or a non RTGS system.
IndIndicator [1..1]YesNoIndicatorPrtryProprietary [1..1]GenericIdentification30
HldIndHold Indicator [0..1]HoldIndicator6Specifies whether the transaction is on hold/blocked/frozen.
IndIndicator [1..1]YesNoIndicatorRsnReason [0..*]RegistrationReason5
MtchgDnlMatching Denial [0..1]MatchingDenied3Choice (choice)Specifies the matching processing change requested.
CdCode [1..1]MatchingProcess1CodePrtryProprietary [1..1]GenericIdentification30
UnltrlSpltUnilateral Split [0..1]UnilateralSplit3Choice (choice)Specifies that the transaction is requested to be unilaterally split.
CdCode [1..1]SecuritiesTransactionType5CodePrtryProprietary [1..1]GenericIdentification30
LnkgsLinkages [0..*]Linkages73Information regarding the linkage requested.
PrcgPosProcessing Position [0..1]ProcessingPosition8Choice (choice)MsgNbMessage Number [0..1]DocumentNumber5Choice (choice)RefReference [1..1]References80Choice (choice)RefOwnrReference Owner [0..1]PartyIdentification127Choice (choice)
AddtlInfAdditional Information [0..*]AdditionalInformation26Additional information that cannot be captured in the structured elements and/or any other specific block.
AcctOwnrTxIdAccount Owner Transaction Identification [0..1]Max35TextIdentification of the transaction as known by the account owner.
ClssfctnTpClassification Type [0..1]ClassificationType32Choice (choice)Type of instrument involved in the transactions on which the modification request should apply.
ClssfctnFinInstrmClassification Financial Instrument [1..1]CFIOct2015IdentifierAltrnClssfctnAlternate Classification [1..1]GenericIdentification36
SfkpgAcctSafekeeping Account [0..1]SecuritiesAccount19Account to or from which a securities entry is made.
IdIdentification [1..1]Max35TextTpType [0..1]GenericIdentification30NmName [0..1]Max70Text
BlckChainAdrOrWlltBlock Chain Address Or Wallet [0..1]BlockChainAddressWallet3Blockchain address or wallet where digital assets are maintained.
IdIdentification [1..1]Max140TextTpType [0..1]GenericIdentification30NmName [0..1]Max70Text
FinInstrmIdFinancial Instrument Identification [0..1]SecurityIdentification19Identification of the financial instrument to which the modification request applied.
ISINISIN [0..1]ISINOct2015IdentifierOthrIdOther Identification [0..*]OtherIdentification1DescDescription [0..1]Max140Text
QtyQuantity [0..1]FinancialInstrumentQuantity33Choice (choice)Quantity of financial instrument concerned by the settlement condition modification request.
UnitUnit [1..1]DecimalNumberFaceAmtFace Amount [1..1]ImpliedCurrencyAndAmountAmtsdValAmortised Value [1..1]ImpliedCurrencyAndAmountDgtlTknUnitDigital Token Unit [1..1]Max30DecimalNumber
FctvDtEffective Date [0..1]DateAndDateTime2Choice (choice)Date/time when the request should take effect.
DtDate [1..1]ISODateDtTmDate Time [1..1]ISODateTime
XpryDtExpiry Date [0..1]DateAndDateTime2Choice (choice)Date/time when the request should cease to be in effect.
DtDate [1..1]ISODateDtTmDate Time [1..1]ISODateTime
CutOffDtCut Off Date [0..1]DateAndDateTime2Choice (choice)Date/time of the release.
DtDate [1..1]ISODateDtTmDate Time [1..1]ISODateTime
InvstrInvestor [0..1]PartyIdentification136Party, either an individual or organisation, whose assets are being invested.
IdIdentification [1..1]PartyIdentification120Choice (choice)LEILEI [0..1]LEIIdentifier
DlvrgPty1Delivering Party1 [0..1]PartyIdentificationAndAccount195Party that, in a settlement chain, interacts with the depository.
IdIdentification [1..1]PartyIdentification120Choice (choice)LEILEI [0..1]LEIIdentifierSfkpgAcctSafekeeping Account [0..1]SecuritiesAccount19BlckChainAdrOrWlltBlock Chain Address Or Wallet [0..1]BlockChainAddressWallet3PrcgIdProcessing Identification [0..1]Max35Text
RcvgPty1Receiving Party1 [0..1]PartyIdentificationAndAccount195Party that, in a settlement chain, interacts with the depository.
IdIdentification [1..1]PartyIdentification120Choice (choice)LEILEI [0..1]LEIIdentifierSfkpgAcctSafekeeping Account [0..1]SecuritiesAccount19BlckChainAdrOrWlltBlock Chain Address Or Wallet [0..1]BlockChainAddressWallet3PrcgIdProcessing Identification [0..1]Max35Text
TxSbjtToBuyInTransaction Subject To Buy In [0..1]YesNoIndicatorThe transaction relates to a buy-in by the market following a delivery transaction failure.
SplmtryDataSupplementary Data [0..*]SupplementaryData1Additional information that cannot be captured in the structured elements and/or any other specific block.
PlcAndNmPlace And Name [0..1]Max350TextUnambiguous reference to the location where the supplementary data must be inserted in the message instance.
EnvlpEnvelope [1..1]SupplementaryDataEnvelope1Technical element wrapping the supplementary data.
Have a sese.030 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.
External code sets used in sese.030
These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.
sese.030 questions
- What is the latest version of sese.030?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is sese.030.001.10.
- What is the root element of sese.030?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:sese.030.001.10, and its message element is SctiesSttlmCondsModReq (SecuritiesSettlementConditionsModificationRequest).
- Is there an MT equivalent of sese.030?
- Yes. sese.030 does the same business job as MT530. Field-level translation has gaps in both directions.
All ISO 20022 messages · ISO 20022 code sets · MT messages
The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.