SecuritiesSettlementTransactionStatusAdviceV03

sese.024.001.03

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:

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

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

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

MatchingStatus7Choice 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
%% TransactionDetails36 recursion level 0 with max 1
class TransactionDetails36{
    TradeIdentification IsoMax35Text
    PoolIdentification IsoMax35Text
    CorporateActionEventIdentification IsoMax35Text
    TripartyAgentCollateralTransactionIdentification IsoMax35Text
    ClientTripartyCollateralTransactionIdentification IsoMax35Text
    PlaceOfClearing IsoAnyBICIdentifier
    SecuritiesMovementType ReceiveDelivery1Code
    Payment DeliveryReceiptType2Code
    SettlementInstructionProcessingAdditionalDetails IsoMax350Text
}
TransactionDetails36 *-- "0..1" IPartyIdentification36Choice : AccountOwner
TransactionDetails36 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount
TransactionDetails36 *-- "0..1" ISafekeepingPlaceFormat3Choice : SafekeepingPlace
TransactionDetails36 *-- "0..1" MarketIdentification4 : PlaceOfTrade
TransactionDetails36 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification
TransactionDetails36 *-- "1..1" IQuantity6Choice : SettlementQuantity
TransactionDetails36 *-- "0..1" AmountAndDirection8 : SettlementAmount
TransactionDetails36 *-- "0..1" IDateAndDateTimeChoice : LateDeliveryDate
TransactionDetails36 *-- "0..1" IDateAndDateTimeChoice : ExpectedSettlementDate
TransactionDetails36 *-- "0..1" IDateAndDateTimeChoice : ExpectedValueDate
TransactionDetails36 *-- "1..1" ISettlementDate2Choice : SettlementDate
TransactionDetails36 *-- "0..1" ITradeDate1Choice : TradeDate
TransactionDetails36 *-- "1..1" SettlementDetails44 : SettlementParameters
TransactionDetails36 *-- "0..1" SettlementParties13 : ReceivingSettlementParties
TransactionDetails36 *-- "0..1" SettlementParties13 : DeliveringSettlementParties
TransactionDetails36 *-- "0..1" IPartyIdentification37Choice : Investor
TransactionDetails36 *-- "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
  

TransactionDetails36 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
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. MarketIdentification4 - 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 and time at which the securities are to be delivered or received. 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. SettlementDetails44 - 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 SecuritiesSettlementTransactionStatusAdviceV03 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementTransactionStatusAdviceV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementTransactionStatusAdviceV03Document implements IOuterDocument. Because SecuritiesSettlementTransactionStatusAdviceV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementTransactionStatusAdviceV03.

classDiagram
    class IOuterRecord
    SecuritiesSettlementTransactionStatusAdviceV03 --|> IOuterRecord : Implements
    SecuritiesSettlementTransactionStatusAdviceV03Document --|> IOuterDocument~SecuritiesSettlementTransactionStatusAdviceV03~ : Implements
    class IOuterDocument~SecuritiesSettlementTransactionStatusAdviceV03~ {
        SecuritiesSettlementTransactionStatusAdviceV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesSettlementTransactionStatusAdviceV03Document *-- SecuritiesSettlementTransactionStatusAdviceV03 : 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.03">
    <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="_N1B-8fvLEeCBQp5TnX1XKQ"
  nextVersions="_BZiEcQxzEeKMmbvHOtE4SA"
  previousVersion="_utzQkdtZEd-RF5yaMAVhAw"
  name="SecuritiesSettlementTransactionStatusAdviceV03"
  definition="Scope&#xD;&#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.&#xD;&#xA;The status advice may be sent as a response to the request of the account owner or not.&#xD;&#xA;The account servicer/owner relationship may be:&#xD;&#xA;- a central securities depository or another settlement market infrastructure acting on behalf of their participants&#xD;&#xA;- an agent (sub-custodian) acting on behalf of their global custodian customer, or&#xD;&#xA;- a custodian acting on behalf of an investment management institution or a broker/dealer.&#xD;&#xA;Usage&#xD;&#xA;The message may also be used to:&#xD;&#xA;- re-send a message previously sent,&#xD;&#xA;- provide a third party with a copy of a message for information,&#xD;&#xA;- re-send to a third party a copy of a message for information.&#xD;&#xA;using the relevant elements in the Business Application Header.&#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="_N1B-9fvLEeCBQp5TnX1XKQ"
    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="_N1B--fvLEeCBQp5TnX1XKQ"
    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="_N1B-_fvLEeCBQp5TnX1XKQ"
    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="_N1B_AfvLEeCBQp5TnX1XKQ"
    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="_N1B_BfvLEeCBQp5TnX1XKQ"
    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="_N1B_CfvLEeCBQp5TnX1XKQ"
    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="_N1B_DfvLEeCBQp5TnX1XKQ"
    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="_N1B_EfvLEeCBQp5TnX1XKQ"
    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="_N1B_FfvLEeCBQp5TnX1XKQ"
    name="TransactionIdentification"
    definition="Provides unambiguous transaction identification information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_UEvx0f7yEeCvPoRGOxRobQ" />
  <messageBuildingBlock
    xmi:id="_N1B_GfvLEeCBQp5TnX1XKQ"
    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="_N1B_HfvLEeCBQp5TnX1XKQ"
    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="_N1B_IfvLEeCBQp5TnX1XKQ"
    name="MatchingStatus"
    definition="Provides the matching status of the instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MtchgSts"
    complexType="_GJDy8f5WEeCtrO5qCU90cA" />
  <messageBuildingBlock
    xmi:id="_N1B_JfvLEeCBQp5TnX1XKQ"
    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="_N1B_KfvLEeCBQp5TnX1XKQ"
    name="TransactionDetails"
    definition="Identifies the details of the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="TxDtls"
    complexType="_aJKrXfvlEeCBQp5TnX1XKQ" />
  <messageBuildingBlock
    xmi:id="_N1B_LfvLEeCBQp5TnX1XKQ"
    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="03" />
</messageDefinition>

ISO Building Blocks

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