sese.024.001.06
Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. 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.
ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.
Message Construction
Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification
classDiagram direction LR %% SecuritiesSettlementTransactionStatusAdviceV06 recursion level 0 with max 0 SecuritiesSettlementTransactionStatusAdviceV06 *-- "1..1" TransactionIdentifications16 : TransactionIdentification SecuritiesSettlementTransactionStatusAdviceV06 *-- "0..1" IProcessingStatus37Choice : ProcessingStatus SecuritiesSettlementTransactionStatusAdviceV06 *-- "0..1" IMatchingStatus19Choice : InferredMatchingStatus SecuritiesSettlementTransactionStatusAdviceV06 *-- "0..1" IMatchingStatus19Choice : MatchingStatus SecuritiesSettlementTransactionStatusAdviceV06 *-- "0..1" ISettlementStatus7Choice : SettlementStatus SecuritiesSettlementTransactionStatusAdviceV06 *-- "0..1" TransactionDetails70 : TransactionDetails SecuritiesSettlementTransactionStatusAdviceV06 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
TransactionIdentification building block
Provides unambiguous transaction identification information. Provides transaction type and identification information. For comparison, see the ISO20022 official specification
classDiagram direction tb %% TransactionIdentifications16 recursion level 0 with max 1 class TransactionIdentifications16{ AccountOwnerTransactionIdentification IsoMax35Text AccountServicerTransactionIdentification IsoMax35Text MarketInfrastructureTransactionIdentification IsoMax35Text ProcessorTransactionIdentification IsoMax35Text CommonIdentification IsoMax35Text NettingServiceProviderIdentification IsoMax35Text }
TransactionIdentifications16 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
AccountOwnerTransactionIdentification | Unambiguous identification of the transaction as known by the account owner (or the instructing party managing the account). | IsoMax35Text - Required 1..1 |
AccountServicerTransactionIdentification | Unambiguous identification of the transaction as known by the account servicer. | IsoMax35Text - Optional 0..1 |
MarketInfrastructureTransactionIdentification | Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities. | IsoMax35Text - Optional 0..1 |
ProcessorTransactionIdentification | Identification of the transaction assigned by the processor of the instruction other than the account owner the account servicer and the market infrastructure. | IsoMax35Text - Optional 0..1 |
CommonIdentification | Unique reference agreed upon by the two trade counterparties to identify the trade. | IsoMax35Text - Optional 0..1 |
NettingServiceProviderIdentification | Identification assigned by the Netting Service Provider to identify the Nett transaction resulting from netting process. | IsoMax35Text - Optional 0..1 |
ProcessingStatus building block
Provides details on the processing status of the transaction. Choice of format for the processing status. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IProcessingStatus37Choice recursion level 0 with max 1
ProcessingStatus37Choice members
Member name | Description | Data Type / Multiplicity |
---|
InferredMatchingStatus building block
Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD). Choice of format for the matching status. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IMatchingStatus19Choice recursion level 0 with max 1
MatchingStatus19Choice members
Member name | Description | Data Type / Multiplicity |
---|
MatchingStatus building block
Provides the matching status of the instruction. Choice of format for the matching status. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IMatchingStatus19Choice recursion level 0 with max 1
MatchingStatus19Choice members
Member name | Description | Data Type / Multiplicity |
---|
SettlementStatus building block
Provides the status of settlement of a transaction. Choice of format for the settlement status. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ISettlementStatus7Choice recursion level 0 with max 1
SettlementStatus7Choice members
Member name | Description | Data Type / Multiplicity |
---|
TransactionDetails building block
Identifies the details of the transaction. Identifies the details of the transaction. For comparison, see the ISO20022 official specification
classDiagram direction tb %% TransactionDetails70 recursion level 0 with max 1 class TransactionDetails70{ TradeIdentification IsoMax35Text PoolIdentification IsoMax35Text CorporateActionEventIdentification IsoMax35Text TripartyAgentCollateralTransactionIdentification IsoMax35Text ClientTripartyCollateralTransactionIdentification IsoMax35Text ClientCollateralInstructionIdentification IsoMax35Text TripartyCollateralInstructionIdentification IsoMax35Text PlaceOfClearing IsoAnyBICIdentifier SecuritiesMovementType ReceiveDelivery1Code Payment DeliveryReceiptType2Code SettlementInstructionProcessingAdditionalDetails IsoMax350Text } TransactionDetails70 *-- "0..1" IPartyIdentification36Choice : AccountOwner TransactionDetails70 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount TransactionDetails70 *-- "0..1" ISafekeepingPlaceFormat3Choice : SafekeepingPlace TransactionDetails70 *-- "0..1" MarketIdentification78 : PlaceOfTrade TransactionDetails70 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification TransactionDetails70 *-- "1..1" IQuantity6Choice : SettlementQuantity TransactionDetails70 *-- "0..1" AmountAndDirection8 : SettlementAmount TransactionDetails70 *-- "0..1" IDateAndDateTimeChoice : LateDeliveryDate TransactionDetails70 *-- "0..1" IDateAndDateTimeChoice : ExpectedSettlementDate TransactionDetails70 *-- "0..1" IDateAndDateTimeChoice : ExpectedValueDate TransactionDetails70 *-- "1..1" ISettlementDate2Choice : SettlementDate TransactionDetails70 *-- "0..1" ITradeDate1Choice : TradeDate TransactionDetails70 *-- "1..1" SettlementDetails69 : SettlementParameters TransactionDetails70 *-- "0..1" SettlementParties13 : ReceivingSettlementParties TransactionDetails70 *-- "0..1" SettlementParties13 : DeliveringSettlementParties TransactionDetails70 *-- "0..1" IPartyIdentification37Choice : Investor TransactionDetails70 *-- "0..1" IPartyIdentification45Choice : QualifiedForeignIntermediary %% IPartyIdentification36Choice recursion level 1 with max 1 %% SecuritiesAccount13 recursion level 1 with max 1 class SecuritiesAccount13{ Identification IsoMax35Text Name IsoMax70Text } SecuritiesAccount13 *-- "0..1" GenericIdentification20 : Type %% ISafekeepingPlaceFormat3Choice recursion level 1 with max 1 %% MarketIdentification78 recursion level 1 with max 1 MarketIdentification78 *-- "0..1" IMarketIdentification1Choice : Identification MarketIdentification78 *-- "1..1" IMarketType3Choice : Type %% SecurityIdentification14 recursion level 1 with max 1 class SecurityIdentification14{ ISIN IsoISINIdentifier Description IsoMax140Text } SecurityIdentification14 *-- "0..0" OtherIdentification1 : OtherIdentification %% IQuantity6Choice recursion level 1 with max 1 %% AmountAndDirection8 recursion level 1 with max 1 class AmountAndDirection8{ Amount IsoActiveCurrencyAndAmount CreditDebitIndicator CreditDebitCode OriginalCurrencyAndOrderedAmount IsoActiveOrHistoricCurrencyAndAmount } %% IDateAndDateTimeChoice recursion level 1 with max 1 %% IDateAndDateTimeChoice recursion level 1 with max 1 %% IDateAndDateTimeChoice recursion level 1 with max 1 %% ISettlementDate2Choice recursion level 1 with max 1 %% ITradeDate1Choice recursion level 1 with max 1 %% SettlementDetails69 recursion level 1 with max 1 class SettlementDetails69{ PartialSettlementIndicator SettlementTransactionCondition5Code EligibleForCollateral IsoYesNoIndicator } SettlementDetails69 *-- "0..1" HoldIndicator4 : HoldIndicator SettlementDetails69 *-- "0..0" ISettlementTransactionCondition12Choice : SettlementTransactionCondition SettlementDetails69 *-- "1..1" ISecuritiesTransactionType9Choice : SecuritiesTransactionType SettlementDetails69 *-- "0..1" ISettlingCapacity4Choice : SettlingCapacity SettlementDetails69 *-- "0..1" GenericIdentification20 : StampDutyTaxBasis SettlementDetails69 *-- "0..1" ISecuritiesRTGS1Choice : SecuritiesRTGS SettlementDetails69 *-- "0..1" IRegistration1Choice : Registration SettlementDetails69 *-- "0..1" IBeneficialOwnership1Choice : BeneficialOwnership SettlementDetails69 *-- "0..1" IExposureType10Choice : ExposureType SettlementDetails69 *-- "0..1" ICashSettlementSystem1Choice : CashClearingSystem SettlementDetails69 *-- "0..1" ITaxCapacityParty1Choice : TaxCapacity SettlementDetails69 *-- "0..1" IRepurchaseType3Choice : RepurchaseType SettlementDetails69 *-- "0..1" IMarketClientSide1Choice : MarketClientSide SettlementDetails69 *-- "0..1" IBlockTrade1Choice : BlockTrade SettlementDetails69 *-- "0..1" IRestriction1Choice : LegalRestrictions SettlementDetails69 *-- "0..1" ISettlementSystemMethod1Choice : SettlementSystemMethod SettlementDetails69 *-- "0..1" INettingEligibility1Choice : NettingEligibility SettlementDetails69 *-- "0..1" ICentralCounterPartyEligibility1Choice : CCPEligibility SettlementDetails69 *-- "0..1" ILetterOfGuarantee1Choice : LetterOfGuarantee %% SettlementParties13 recursion level 1 with max 1 SettlementParties13 *-- "0..1" PartyIdentification46 : Depository SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party1 SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party2 SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party3 SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party4 SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party5 %% SettlementParties13 recursion level 1 with max 1 SettlementParties13 *-- "0..1" PartyIdentification46 : Depository SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party1 SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party2 SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party3 SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party4 SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party5 %% IPartyIdentification37Choice recursion level 1 with max 1 %% IPartyIdentification45Choice recursion level 1 with max 1
TransactionDetails70 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
TradeIdentification | Reference assigned to the trade by the investor or the trading party. This reference will be used throughout the trade life cycle to access/update the trade details. | IsoMax35Text - Unknown 0..0 |
PoolIdentification | Collective reference identifying a set of messages. | IsoMax35Text - Optional 0..1 |
CorporateActionEventIdentification | Identification assigned by the account servicer to unambiguously identify a corporate action event. | IsoMax35Text - Optional 0..1 |
TripartyAgentCollateralTransactionIdentification | Unique reference identifying the triparty collateral management transaction from the triparty agent’s point of view. | IsoMax35Text - Optional 0..1 |
ClientTripartyCollateralTransactionIdentification | Unique reference identifying the triparty collateral management transaction from the client’s point of view. | IsoMax35Text - Optional 0..1 |
ClientCollateralInstructionIdentification | Unique identification assigned to the instruction by the client. | IsoMax35Text - Optional 0..1 |
TripartyCollateralInstructionIdentification | Unique identification assigned to the instruction by the triparty agent. | IsoMax35Text - Optional 0..1 |
AccountOwner | Party that legally owns the account. | IPartyIdentification36Choice - Optional 0..1 |
SafekeepingAccount | Account to or from which a securities entry is made. | SecuritiesAccount13 - Required 1..1 |
SafekeepingPlace | Place where the securities are safe-kept, physically or notionally. This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD). | ISafekeepingPlaceFormat3Choice - Optional 0..1 |
PlaceOfTrade | Market in which a trade transaction has been executed. | MarketIdentification78 - Optional 0..1 |
PlaceOfClearing | Infrastructure which may be a component of a clearing house and which facilitates clearing and settlement for its members by standing between the buyer and the seller. It may net transactions and it substitutes itself as settlement counterparty for each position. | IsoAnyBICIdentifier - Optional 0..1 |
FinancialInstrumentIdentification | Financial instruments representing a sum of rights of the investor vis-a-vis the issuer. | SecurityIdentification14 - Required 1..1 |
SettlementQuantity | Total quantity of securities to be settled. | IQuantity6Choice - Required 1..1 |
SettlementAmount | Total amount of money to be paid or received in exchange for the securities. | AmountAndDirection8 - Optional 0..1 |
LateDeliveryDate | Date and time after the settlement date specified in the trade, used for pool trades resulting from the original To Be Assigned (TBA) securities. | IDateAndDateTimeChoice - Optional 0..1 |
ExpectedSettlementDate | Date/time at which the sender expects settlement. | IDateAndDateTimeChoice - Optional 0..1 |
ExpectedValueDate | For against payment transactions, the value date/time at which the Sender expects the settlement amount to be credited or debited. | IDateAndDateTimeChoice - Optional 0..1 |
SettlementDate | Date and time at which the securities are to be delivered or received. | ISettlementDate2Choice - Required 1..1 |
TradeDate | Specifies the date/time on which the trade was executed. | ITradeDate1Choice - Optional 0..1 |
SecuritiesMovementType | Specifies if the movement on a securities account results from a deliver or a receive instruction. | ReceiveDelivery1Code - Required 1..1 |
Payment | Specifies how the transaction is to be settled, for example, against payment. | DeliveryReceiptType2Code - Required 1..1 |
SettlementParameters | Parameters applied to the settlement of a security transfer. | SettlementDetails69 - Required 1..1 |
ReceivingSettlementParties | Identifies the chain of receiving settlement parties. | SettlementParties13 - Optional 0..1 |
DeliveringSettlementParties | Identifies the chain of delivering settlement parties. | SettlementParties13 - Optional 0..1 |
Investor | Party, either an individual or organisation, whose assets are being invested. | IPartyIdentification37Choice - Optional 0..1 |
QualifiedForeignIntermediary | Foreign Financial Institution which has been authorised by local authorities to act as account management institution in the country. | IPartyIdentification45Choice - Optional 0..1 |
SettlementInstructionProcessingAdditionalDetails | Provides additional settlement processing information which can not be included within the structured fields of the message. | IsoMax350Text - Optional 0..1 |
SupplementaryData building block
Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification
classDiagram direction tb %% SupplementaryData1 recursion level 0 with max 1 class SupplementaryData1{ PlaceAndName IsoMax350Text } SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope %% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
SupplementaryData1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
PlaceAndName | Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. | IsoMax350Text - Optional 0..1 |
Envelope | Technical element wrapping the supplementary data. | IsoSupplementaryDataEnvelope1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the SecuritiesSettlementTransactionStatusAdviceV06 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementTransactionStatusAdviceV06 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementTransactionStatusAdviceV06Document implements IOuterDocument. Because SecuritiesSettlementTransactionStatusAdviceV06 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementTransactionStatusAdviceV06.
classDiagram class IOuterRecord SecuritiesSettlementTransactionStatusAdviceV06 --|> IOuterRecord : Implements SecuritiesSettlementTransactionStatusAdviceV06Document --|> IOuterDocument~SecuritiesSettlementTransactionStatusAdviceV06~ : Implements class IOuterDocument~SecuritiesSettlementTransactionStatusAdviceV06~ { SecuritiesSettlementTransactionStatusAdviceV06 Message }
Document wrapper for serialization
The only real purpose SecuritiesSettlementTransactionStatusAdviceV06Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.024.001.06’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesSettlementTransactionStatusAdviceV06.ToDocument() method. The returned SecuritiesSettlementTransactionStatusAdviceV06Document value will serialize correctly according to ISO 20022 standards.
classDiagram SecuritiesSettlementTransactionStatusAdviceV06Document *-- SecuritiesSettlementTransactionStatusAdviceV06 : Document
Sample of message format
This is an abbreviated version of what the message should look like.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:sese.024.001.06">
<SctiesSttlmTxStsAdvc>
<TxId>
<!-- TransactionIdentification inner content -->
</TxId>
<PrcgSts>
<!-- ProcessingStatus inner content -->
</PrcgSts>
<IfrrdMtchgSts>
<!-- InferredMatchingStatus inner content -->
</IfrrdMtchgSts>
<MtchgSts>
<!-- MatchingStatus inner content -->
</MtchgSts>
<SttlmSts>
<!-- SettlementStatus inner content -->
</SttlmSts>
<TxDtls>
<!-- TransactionDetails inner content -->
</TxDtls>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</SctiesSttlmTxStsAdvc>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_KMAkAU3OEeS1yPC0JC-FvQ"
nextVersions="_YSWIIwCTEeW_3KiG8SEjHA"
previousVersion="_ZCNB8SRREeON6sEIseGaUg"
name="SecuritiesSettlementTransactionStatusAdviceV06"
definition="Scope
An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status.
The status advice may be sent as a response to the request of the account owner or not.
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.

ISO 15022 - 20022 Coexistence
This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="SctiesSttlmTxStsAdvc"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_KMAkA03OEeS1yPC0JC-FvQ"
nextVersions="_YSWIJQCTEeW_3KiG8SEjHA"
previousVersion="_ZCNB8yRREeON6sEIseGaUg"
name="ProcessingStatusPresenceRule"
definition="If InferredMatchingStatus, MatchingStatus and SettlementStatus are absent, then ProcessingStatus must be present."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ComplexRule xsi:type="ComplexRule"><mustBe><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/ProcessingStatus</leftOperand></BooleanRule></mustBe><onCondition><connector>AND</connector><BooleanRule xsi:type="Absence"><leftOperand>/MatchingStatus</leftOperand></BooleanRule><BooleanRule xsi:type="Absence"><leftOperand>/SettlementStatus</leftOperand></BooleanRule><BooleanRule xsi:type="Absence"><leftOperand>/InferredMatchingStatus</leftOperand></BooleanRule></onCondition></ComplexRule></RuleDefinition>
" />
<constraint
xmi:id="_KMAkBU3OEeS1yPC0JC-FvQ"
nextVersions="_YSWIJwCTEeW_3KiG8SEjHA"
previousVersion="_ZCNB9SRREeON6sEIseGaUg"
name="MatchingStatusPresenceRule"
definition="If ProcessingStatus, InferredMatchingStatus and SettlementStatus are absent, then MatchingStatus must be present."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ComplexRule xsi:type="ComplexRule"><mustBe><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/MatchingStatus</leftOperand></BooleanRule></mustBe><onCondition><connector>AND</connector><BooleanRule xsi:type="Absence"><leftOperand>/ProcessingStatus</leftOperand></BooleanRule><BooleanRule xsi:type="Absence"><leftOperand>/SettlementStatus</leftOperand></BooleanRule><BooleanRule xsi:type="Absence"><leftOperand>/InferredMatchingStatus</leftOperand></BooleanRule></onCondition></ComplexRule></RuleDefinition>
" />
<constraint
xmi:id="_KMAkB03OEeS1yPC0JC-FvQ"
nextVersions="_YSWIKQCTEeW_3KiG8SEjHA"
previousVersion="_ZCNB9yRREeON6sEIseGaUg"
name="SettlementStatusPresenceRule"
definition="If ProcessingStatus, InferredMatchingStatus and MatchingStatus are absent, then SettlementStatus must be present."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ComplexRule xsi:type="ComplexRule"><mustBe><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/SettlementStatus</leftOperand></BooleanRule></mustBe><onCondition><connector>AND</connector><BooleanRule xsi:type="Absence"><leftOperand>/ProcessingStatus</leftOperand></BooleanRule><BooleanRule xsi:type="Absence"><leftOperand>/MatchingStatus</leftOperand></BooleanRule><BooleanRule xsi:type="Absence"><leftOperand>/InferredMatchingStatus</leftOperand></BooleanRule></onCondition></ComplexRule></RuleDefinition>
" />
<constraint
xmi:id="_KMAkCU3OEeS1yPC0JC-FvQ"
nextVersions="_YSWIKwCTEeW_3KiG8SEjHA"
previousVersion="_ZCNB-SRREeON6sEIseGaUg"
name="InferredMatchingStatusStatusPresenceRule"
definition="If ProcessingStatus, MatchingStatus and SettlementStatus are absent, the InferredMatchingStatus must be present."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ComplexRule xsi:type="ComplexRule"><mustBe><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/InferredMatchingStatus</leftOperand></BooleanRule></mustBe><onCondition><connector>AND</connector><BooleanRule xsi:type="Absence"><leftOperand>/ProcessingStatus</leftOperand></BooleanRule><BooleanRule xsi:type="Absence"><leftOperand>/MatchingStatus</leftOperand></BooleanRule><BooleanRule xsi:type="Absence"><leftOperand>/SettlementStatus</leftOperand></BooleanRule></onCondition></ComplexRule></RuleDefinition>
" />
<constraint
xmi:id="_KMAkC03OEeS1yPC0JC-FvQ"
previousVersion="_ZCNB-yRREeON6sEIseGaUg"
name="CoexistenceCharacterSetXRule"
definition="During ISO 15022 – 20022 coexistence, characters used in all text fields must correspond to character set X, that is, a-z A-Z / - ? : ( ) . , ‘ + { } CR LF."
registrationStatus="Provisionally Registered" />
<constraint
xmi:id="_KMAkDU3OEeS1yPC0JC-FvQ"
previousVersion="_ZCNB_SRREeON6sEIseGaUg"
name="CoexistenceIdentificationRule"
definition="During ISO 15022 – 20022 coexistence, all transaction and document identifications or references must be 16 characters or less. The field must not start or end with a slash ‘/’ or contain two consecutive slashes ‘//’."
registrationStatus="Provisionally Registered" />
<constraint
xmi:id="_KMAkD03OEeS1yPC0JC-FvQ"
nextVersions="_YSWIMQCTEeW_3KiG8SEjHA"
previousVersion="_ZCNB_yRREeON6sEIseGaUg"
name="SettlementStatusAndMatchedRule"
definition="If settlement status/reason is used alone, then it means that the transaction is matched (if a matching process exists in the concerned market or at the concerned account servicer)."
registrationStatus="Provisionally Registered" />
<constraint
xmi:id="_KMAkEU3OEeS1yPC0JC-FvQ"
nextVersions="_YSWIMwCTEeW_3KiG8SEjHA"
previousVersion="_ZCNCASRREeON6sEIseGaUg"
name="SecuritiesMarketPracticeGroupGuideline"
definition="The Securities Market Practice Group (SMPG) has published market practice recommendations on the use of this message.
These market practices are available on www.smpg.info."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_KMAkE03OEeS1yPC0JC-FvQ"
nextVersions="_YSWINQCTEeW_3KiG8SEjHA"
previousVersion="_ZCNCAyRREeON6sEIseGaUg"
name="TransactionIdentification"
definition="Provides unambiguous transaction identification information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="TxId"
complexType="_UEvx0f7yEeCvPoRGOxRobQ" />
<messageBuildingBlock
xmi:id="_KMAkFU3OEeS1yPC0JC-FvQ"
nextVersions="_YSWINwCTEeW_3KiG8SEjHA"
previousVersion="_ZCNCBSRREeON6sEIseGaUg"
name="ProcessingStatus"
definition="Provides details on the processing status of the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PrcgSts"
complexType="_F0ajsSwuEeOEV5XHD-BKpw" />
<messageBuildingBlock
xmi:id="_KMAkF03OEeS1yPC0JC-FvQ"
nextVersions="_YSWIOQCTEeW_3KiG8SEjHA"
previousVersion="_ZCNCByRREeON6sEIseGaUg"
name="InferredMatchingStatus"
definition="Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD)."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="IfrrdMtchgSts"
complexType="_ZlY6ASwREeOEV5XHD-BKpw" />
<messageBuildingBlock
xmi:id="_KMAkGU3OEeS1yPC0JC-FvQ"
nextVersions="_YSWIOwCTEeW_3KiG8SEjHA"
previousVersion="_ZCNCCSRREeON6sEIseGaUg"
name="MatchingStatus"
definition="Provides the matching status of the instruction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="MtchgSts"
complexType="_ZlY6ASwREeOEV5XHD-BKpw" />
<messageBuildingBlock
xmi:id="_KMAkG03OEeS1yPC0JC-FvQ"
nextVersions="_YSWIPQCTEeW_3KiG8SEjHA"
previousVersion="_ZCNCCyRREeON6sEIseGaUg"
name="SettlementStatus"
definition="Provides the status of settlement of a transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SttlmSts"
complexType="_Bsv4If40EeClUvPNHKL9Zw" />
<messageBuildingBlock
xmi:id="_KMAkHU3OEeS1yPC0JC-FvQ"
nextVersions="_YSWIPwCTEeW_3KiG8SEjHA"
previousVersion="_ZCNCDSRREeON6sEIseGaUg"
name="TransactionDetails"
definition="Identifies the details of the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="TxDtls"
complexType="_VKn0kU34EeSGA7fXFuKIIQ" />
<messageBuildingBlock
xmi:id="_KMAkH03OEeS1yPC0JC-FvQ"
nextVersions="_YSWIQQCTEeW_3KiG8SEjHA"
previousVersion="_ZCNCDyRREeON6sEIseGaUg"
name="SupplementaryData"
definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="sese"
messageFunctionality="024"
flavour="001"
version="06" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.