SecuritiesSettlementTransactionStatusAdviceV04

sese.024.001.04

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
%% SecuritiesSettlementTransactionStatusAdviceV04 recursion level 0 with max 0
SecuritiesSettlementTransactionStatusAdviceV04 *-- "1..1" TransactionIdentifications16 : TransactionIdentification
SecuritiesSettlementTransactionStatusAdviceV04 *-- "0..1" IProcessingStatus19Choice : ProcessingStatus
SecuritiesSettlementTransactionStatusAdviceV04 *-- "0..1" IMatchingStatus7Choice : InferredMatchingStatus
SecuritiesSettlementTransactionStatusAdviceV04 *-- "0..1" IMatchingStatus7Choice : MatchingStatus
SecuritiesSettlementTransactionStatusAdviceV04 *-- "0..1" ISettlementStatus7Choice : SettlementStatus
SecuritiesSettlementTransactionStatusAdviceV04 *-- "0..1" TransactionDetails53 : TransactionDetails
SecuritiesSettlementTransactionStatusAdviceV04 *-- "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

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
%% IProcessingStatus19Choice recursion level 0 with max 1
  

ProcessingStatus19Choice members

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
%% IMatchingStatus7Choice recursion level 0 with max 1
  

MatchingStatus7Choice members

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
%% IMatchingStatus7Choice recursion level 0 with max 1
  

MatchingStatus7Choice members

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

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
%% TransactionDetails53 recursion level 0 with max 1
class TransactionDetails53{
    TradeIdentification IsoMax35Text
    PoolIdentification IsoMax35Text
    CorporateActionEventIdentification IsoMax35Text
    TripartyAgentCollateralTransactionIdentification IsoMax35Text
    ClientTripartyCollateralTransactionIdentification IsoMax35Text
    ClientCollateralInstructionIdentification IsoMax35Text
    TripartyCollateralInstructionIdentification IsoMax35Text
    PlaceOfClearing IsoAnyBICIdentifier
    SecuritiesMovementType ReceiveDelivery1Code
    Payment DeliveryReceiptType2Code
    SettlementInstructionProcessingAdditionalDetails IsoMax350Text
}
TransactionDetails53 *-- "0..1" IPartyIdentification36Choice : AccountOwner
TransactionDetails53 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount
TransactionDetails53 *-- "0..1" ISafekeepingPlaceFormat3Choice : SafekeepingPlace
TransactionDetails53 *-- "0..1" MarketIdentification4 : PlaceOfTrade
TransactionDetails53 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification
TransactionDetails53 *-- "1..1" IQuantity6Choice : SettlementQuantity
TransactionDetails53 *-- "0..1" AmountAndDirection8 : SettlementAmount
TransactionDetails53 *-- "0..1" IDateAndDateTimeChoice : LateDeliveryDate
TransactionDetails53 *-- "0..1" IDateAndDateTimeChoice : ExpectedSettlementDate
TransactionDetails53 *-- "0..1" IDateAndDateTimeChoice : ExpectedValueDate
TransactionDetails53 *-- "1..1" ISettlementDate2Choice : SettlementDate
TransactionDetails53 *-- "0..1" ITradeDate1Choice : TradeDate
TransactionDetails53 *-- "1..1" SettlementDetails44 : SettlementParameters
TransactionDetails53 *-- "0..1" SettlementParties13 : ReceivingSettlementParties
TransactionDetails53 *-- "0..1" SettlementParties13 : DeliveringSettlementParties
TransactionDetails53 *-- "0..1" IPartyIdentification37Choice : Investor
TransactionDetails53 *-- "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
%% MarketIdentification4 recursion level 1 with max 1
MarketIdentification4 *-- "0..1" IMarketIdentification1Choice : Identification
MarketIdentification4 *-- "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
%% SettlementDetails44 recursion level 1 with max 1
class SettlementDetails44{
    PartialSettlementIndicator SettlementTransactionCondition5Code
    EligibleForCollateral IsoYesNoIndicator
}
SettlementDetails44 *-- "0..1" HoldIndicator4 : HoldIndicator
SettlementDetails44 *-- "0..0" ISettlementTransactionCondition12Choice : SettlementTransactionCondition
SettlementDetails44 *-- "1..1" ISecuritiesTransactionType9Choice : SecuritiesTransactionType
SettlementDetails44 *-- "0..1" ISettlingCapacity1Choice : SettlingCapacity
SettlementDetails44 *-- "0..1" GenericIdentification20 : StampDutyTaxBasis
SettlementDetails44 *-- "0..1" ISecuritiesRTGS1Choice : SecuritiesRTGS
SettlementDetails44 *-- "0..1" IRegistration1Choice : Registration
SettlementDetails44 *-- "0..1" IBeneficialOwnership1Choice : BeneficialOwnership
SettlementDetails44 *-- "0..1" IExposureType4Choice : ExposureType
SettlementDetails44 *-- "0..1" ICashSettlementSystem1Choice : CashClearingSystem
SettlementDetails44 *-- "0..1" ITaxCapacityParty1Choice : TaxCapacity
SettlementDetails44 *-- "0..1" IRepurchaseType3Choice : RepurchaseType
SettlementDetails44 *-- "0..1" IMarketClientSide1Choice : MarketClientSide
SettlementDetails44 *-- "0..1" IBlockTrade1Choice : BlockTrade
SettlementDetails44 *-- "0..1" IRestriction1Choice : LegalRestrictions
SettlementDetails44 *-- "0..1" ISettlementSystemMethod1Choice : SettlementSystemMethod
SettlementDetails44 *-- "0..1" INettingEligibility1Choice : NettingEligibility
SettlementDetails44 *-- "0..1" ICentralCounterPartyEligibility1Choice : CCPEligibility
SettlementDetails44 *-- "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
  

TransactionDetails53 members

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

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the SecuritiesSettlementTransactionStatusAdviceV04 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementTransactionStatusAdviceV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementTransactionStatusAdviceV04Document implements IOuterDocument. Because SecuritiesSettlementTransactionStatusAdviceV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementTransactionStatusAdviceV04.

classDiagram
    class IOuterRecord
    SecuritiesSettlementTransactionStatusAdviceV04 --|> IOuterRecord : Implements
    SecuritiesSettlementTransactionStatusAdviceV04Document --|> IOuterDocument~SecuritiesSettlementTransactionStatusAdviceV04~ : Implements
    class IOuterDocument~SecuritiesSettlementTransactionStatusAdviceV04~ {
        SecuritiesSettlementTransactionStatusAdviceV04 Message
     }
  

Document wrapper for serialization

The only real purpose SecuritiesSettlementTransactionStatusAdviceV04Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.024.001.04’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesSettlementTransactionStatusAdviceV04.ToDocument() method. The returned SecuritiesSettlementTransactionStatusAdviceV04Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    SecuritiesSettlementTransactionStatusAdviceV04Document *-- SecuritiesSettlementTransactionStatusAdviceV04 : 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.04">
    <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="_BZiEcQxzEeKMmbvHOtE4SA"
  nextVersions="_ZCNB8SRREeON6sEIseGaUg"
  previousVersion="_N1B-8fvLEeCBQp5TnX1XKQ"
  name="SecuritiesSettlementTransactionStatusAdviceV04"
  definition="Scope&#xA;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.&#xA;The status advice may be sent as a response to the request of the account owner or not.&#xA;The account servicer/owner relationship may be:&#xA;- a central securities depository or another settlement market infrastructure acting on behalf of their participants&#xA;- an agent (sub-custodian) acting on behalf of their global custodian customer, or&#xA;- a custodian acting on behalf of an investment management institution or a broker/dealer.&#xA;&#xA;Usage&#xA;The message may also be used to:&#xA;- re-send a message previously sent,&#xA;- provide a third party with a copy of a message for information,&#xA;- re-send to a third party a copy of a message for information&#xA;using the relevant elements in the Business Application Header.&#xA;&#xA;ISO 15022 - 20022 Coexistence&#xA;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="_BZiEdQxzEeKMmbvHOtE4SA"
    nextVersions="_ZCNB8yRREeON6sEIseGaUg"
    name="ProcessingStatusPresenceRule"
    definition="If InferredMatchingStatus, MatchingStatus and SettlementStatus are absent, then ProcessingStatus must be present."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/ProcessingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/MatchingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/SettlementStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/InferredMatchingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_BZiEeQxzEeKMmbvHOtE4SA"
    nextVersions="_ZCNB9SRREeON6sEIseGaUg"
    name="MatchingStatusPresenceRule"
    definition="If ProcessingStatus, InferredMatchingStatus and SettlementStatus are absent, then MatchingStatus must be present."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/MatchingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/ProcessingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/SettlementStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/InferredMatchingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_BZiEfQxzEeKMmbvHOtE4SA"
    nextVersions="_ZCNB9yRREeON6sEIseGaUg"
    name="SettlementStatusPresenceRule"
    definition="If ProcessingStatus, InferredMatchingStatus and MatchingStatus are absent, then SettlementStatus must be present."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/SettlementStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/ProcessingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/MatchingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/InferredMatchingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_BZiEgQxzEeKMmbvHOtE4SA"
    nextVersions="_ZCNB-SRREeON6sEIseGaUg"
    name="InferredMatchingStatusStatusPresenceRule"
    definition="If ProcessingStatus, MatchingStatus and SettlementStatus are absent, the InferredMatchingStatus must be present."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/InferredMatchingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/ProcessingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/MatchingStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/SettlementStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_BZiEhQxzEeKMmbvHOtE4SA"
    nextVersions="_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="_BZiEiQxzEeKMmbvHOtE4SA"
    nextVersions="_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="_BZiEjQxzEeKMmbvHOtE4SA"
    nextVersions="_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="_BZiEkQxzEeKMmbvHOtE4SA"
    nextVersions="_ZCNCASRREeON6sEIseGaUg"
    name="SecuritiesMarketPracticeGroupGuideline"
    definition="The Securities Market Practice Group (SMPG) has published market practice recommendations on the use of this message.&#xD;&#xA;These market practices are available on www.smpg.info."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_BZiElQxzEeKMmbvHOtE4SA"
    nextVersions="_ZCNCAyRREeON6sEIseGaUg"
    name="TransactionIdentification"
    definition="Provides unambiguous transaction identification information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_UEvx0f7yEeCvPoRGOxRobQ" />
  <messageBuildingBlock
    xmi:id="_BZiEmQxzEeKMmbvHOtE4SA"
    nextVersions="_ZCNCBSRREeON6sEIseGaUg"
    name="ProcessingStatus"
    definition="Provides details on the processing status of the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PrcgSts"
    complexType="__qPVMf4wEeClUvPNHKL9Zw" />
  <messageBuildingBlock
    xmi:id="_BZiEnQxzEeKMmbvHOtE4SA"
    nextVersions="_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="_GJDy8f5WEeCtrO5qCU90cA" />
  <messageBuildingBlock
    xmi:id="_BZiEoQxzEeKMmbvHOtE4SA"
    nextVersions="_ZCNCCSRREeON6sEIseGaUg"
    name="MatchingStatus"
    definition="Provides the matching status of the instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MtchgSts"
    complexType="_GJDy8f5WEeCtrO5qCU90cA" />
  <messageBuildingBlock
    xmi:id="_BZiEpQxzEeKMmbvHOtE4SA"
    nextVersions="_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="_BZiEqQxzEeKMmbvHOtE4SA"
    nextVersions="_ZCNCDSRREeON6sEIseGaUg"
    name="TransactionDetails"
    definition="Identifies the details of the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="TxDtls"
    complexType="_ZQWDEQ3oEeKIIIcS0K4sAQ" />
  <messageBuildingBlock
    xmi:id="_BZiErQxzEeKMmbvHOtE4SA"
    nextVersions="_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="04" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.