SecuritiesTransactionPendingReportV04

semt.018.001.04

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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
%% SecuritiesTransactionPendingReportV04 recursion level 0 with max 0
SecuritiesTransactionPendingReportV04 *-- "1..1" Pagination : Pagination
SecuritiesTransactionPendingReportV04 *-- "1..1" Statement14 : StatementGeneralDetails
SecuritiesTransactionPendingReportV04 *-- "0..1" IPartyIdentification36Choice : AccountOwner
SecuritiesTransactionPendingReportV04 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount
SecuritiesTransactionPendingReportV04 *-- "0..1" StatusAndReason16 : Status
SecuritiesTransactionPendingReportV04 *-- "0..1" Transaction27 : Transactions
  

Now, we will zero-in one-by-one on each of these building blocks.

Pagination building block

Page number of the message (within a statement) and continuation indicator to indicate that the statement is to continue or that the message is the last page of the statement. Number used to sequence pages when it is not possible for data to be conveyed in a single message and the data has to be split across several pages (messages). For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Pagination recursion level 0 with max 1
class Pagination{
    PageNumber IsoMax5NumericText
    LastPageIndicator IsoYesNoIndicator
}
  

Pagination members

StatementGeneralDetails building block

Provides general information on the report. Characteristics of the statement. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Statement14 recursion level 0 with max 1
class Statement14{
    QueryReference IsoMax35Text
    StatementIdentification IsoMax35Text
    StatementStructure StatementStructure1Code
    ActivityIndicator IsoYesNoIndicator
}
Statement14 *-- "0..1" INumber3Choice : ReportNumber
Statement14 *-- "1..1" IDateAndDateTimeChoice : StatementDateTime
Statement14 *-- "0..1" IFrequency4Choice : Frequency
Statement14 *-- "0..1" IUpdateType2Choice : UpdateType
%% INumber3Choice recursion level 1 with max 1
%% IDateAndDateTimeChoice recursion level 1 with max 1
%% IFrequency4Choice recursion level 1 with max 1
%% IUpdateType2Choice recursion level 1 with max 1
  

Statement14 members

AccountOwner building block

Party that legally owns the account. Choice of identification of a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IPartyIdentification36Choice recursion level 0 with max 1
  

PartyIdentification36Choice members

SafekeepingAccount building block

Account to or from which a securities entry is made. Account to or from which a securities entry is made. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecuritiesAccount13 recursion level 0 with max 1
class SecuritiesAccount13{
    Identification IsoMax35Text
    Name IsoMax70Text
}
SecuritiesAccount13 *-- "0..1" GenericIdentification20 : Type
%% GenericIdentification20 recursion level 1 with max 1
class GenericIdentification20{
    Identification IsoExact4AlphaNumericText
    Issuer IsoMax35Text
    SchemeName IsoMax35Text
}
  

SecuritiesAccount13 members

Status building block

Status information. Status and reason of an instructed order. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% StatusAndReason16 recursion level 0 with max 1
StatusAndReason16 *-- "1..1" IStatus9Choice : StatusAndReason
StatusAndReason16 *-- "0..0" Transaction28 : Transaction
%% IStatus9Choice recursion level 1 with max 1
%% Transaction28 recursion level 1 with max 1
class Transaction28{
    AccountOwnerTransactionIdentification IsoMax35Text
    AccountServicerTransactionIdentification IsoMax35Text
    MarketInfrastructureTransactionIdentification IsoMax35Text
    ProcessorTransactionIdentification IsoMax35Text
    TradeIdentification IsoMax35Text
    PoolIdentification IsoMax35Text
    CommonIdentification IsoMax35Text
    CorporateActionEventIdentification IsoMax35Text
    TripartyAgentCollateralTransactionIdentification IsoMax35Text
    ClientTripartyCollateralTransactionIdentification IsoMax35Text
    ClientCollateralInstructionIdentification IsoMax35Text
    TripartyCollateralInstructionIdentification IsoMax35Text
}
Transaction28 *-- "0..1" TransactionDetails56 : TransactionDetails
  

StatusAndReason16 members

Transactions building block

Details of the transactions reported. Identifies the details of the transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Transaction27 recursion level 0 with max 1
class Transaction27{
    AccountOwnerTransactionIdentification IsoMax35Text
    AccountServicerTransactionIdentification IsoMax35Text
    MarketInfrastructureTransactionIdentification IsoMax35Text
    ProcessorTransactionIdentification IsoMax35Text
    TradeIdentification IsoMax35Text
    PoolIdentification IsoMax35Text
    CommonIdentification IsoMax35Text
    CorporateActionEventIdentification IsoMax35Text
    TripartyAgentCollateralTransactionIdentification IsoMax35Text
    ClientTripartyCollateralTransactionIdentification IsoMax35Text
    ClientCollateralInstructionIdentification IsoMax35Text
    TripartyCollateralInstructionIdentification IsoMax35Text
}
Transaction27 *-- "0..1" TransactionDetails56 : TransactionDetails
Transaction27 *-- "0..0" IStatus9Choice : StatusAndReason
%% TransactionDetails56 recursion level 1 with max 1
class TransactionDetails56{
    SecuritiesMovementType ReceiveDelivery1Code
    Payment DeliveryReceiptType2Code
    PlaceOfClearing IsoAnyBICIdentifier
    TransactionAdditionalDetails IsoMax350Text
}
TransactionDetails56 *-- "1..1" ITransactionActivity1Choice : TransactionActivity
TransactionDetails56 *-- "0..1" ISettlementOrCorporateActionEvent10Choice : SettlementTransactionOrCorporateActionEventType
TransactionDetails56 *-- "0..1" SettlementDetails47 : SettlementParameters
TransactionDetails56 *-- "0..1" MarketIdentification4 : PlaceOfTrade
TransactionDetails56 *-- "0..1" ISafekeepingPlaceFormat3Choice : SafekeepingPlace
TransactionDetails56 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification
TransactionDetails56 *-- "1..1" IQuantity6Choice : PostingQuantity
TransactionDetails56 *-- "0..1" AmountAndDirection8 : PostingAmount
TransactionDetails56 *-- "0..1" ITradeDate1Choice : TradeDate
TransactionDetails56 *-- "0..1" IDateAndDateTimeChoice : ExpectedSettlementDate
TransactionDetails56 *-- "1..1" ISettlementDate2Choice : SettlementDate
TransactionDetails56 *-- "0..1" IDateAndDateTimeChoice : LateDeliveryDate
TransactionDetails56 *-- "0..1" IDateAndDateTimeChoice : ExpectedValueDate
TransactionDetails56 *-- "0..1" SettlementParties13 : DeliveringSettlementParties
TransactionDetails56 *-- "0..1" SettlementParties13 : ReceivingSettlementParties
TransactionDetails56 *-- "0..0" SupplementaryData1 : SupplementaryData
%% IStatus9Choice recursion level 1 with max 1
  

Transaction27 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    SecuritiesTransactionPendingReportV04 --|> IOuterRecord : Implements
    SecuritiesTransactionPendingReportV04Document --|> IOuterDocument~SecuritiesTransactionPendingReportV04~ : Implements
    class IOuterDocument~SecuritiesTransactionPendingReportV04~ {
        SecuritiesTransactionPendingReportV04 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesTransactionPendingReportV04Document *-- SecuritiesTransactionPendingReportV04 : 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:semt.018.001.04">
    <SctiesTxPdgRpt>
        <Pgntn>
            <!-- Pagination inner content -->
        </Pgntn>
        <StmtGnlDtls>
            <!-- StatementGeneralDetails inner content -->
        </StmtGnlDtls>
        <AcctOwnr>
            <!-- AccountOwner inner content -->
        </AcctOwnr>
        <SfkpgAcct>
            <!-- SafekeepingAccount inner content -->
        </SfkpgAcct>
        <Sts>
            <!-- Status inner content -->
        </Sts>
        <Txs>
            <!-- Transactions inner content -->
        </Txs>
    </SctiesTxPdgRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_-XWQYQxzEeKMmbvHOtE4SA"
  nextVersions="_EB1YwSRMEeON6sEIseGaUg"
  previousVersion="_Z2HLMfvLEeCBQp5TnX1XKQ"
  name="SecuritiesTransactionPendingReportV04"
  definition="Scope&#xA;An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. &#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 statement may also include future settlement or forward transactions which have become binding on the account owner.&#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="SctiesTxPdgRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_-XWQYwxzEeKMmbvHOtE4SA"
    nextVersions="_EB1YwyRMEeON6sEIseGaUg"
    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="_-XWQZwxzEeKMmbvHOtE4SA"
    nextVersions="_EB1YxSRMEeON6sEIseGaUg"
    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="_-XWQawxzEeKMmbvHOtE4SA"
    nextVersions="_EB1YxyRMEeON6sEIseGaUg"
    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="_-XWQbwxzEeKMmbvHOtE4SA"
    nextVersions="_EB1YySRMEeON6sEIseGaUg"
    name="Pagination"
    definition="Page number of the message (within a statement) and continuation indicator to indicate that the statement is to continue or that the message is the last page of the statement."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Pgntn"
    complexType="_Q65gBdp-Ed-ak6NoX_4Aeg_-21330104" />
  <messageBuildingBlock
    xmi:id="_-XWQcwxzEeKMmbvHOtE4SA"
    nextVersions="_EB1YyyRMEeON6sEIseGaUg"
    name="StatementGeneralDetails"
    definition="Provides general information on the report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="StmtGnlDtls"
    complexType="_Qq8_gNp-Ed-ak6NoX_4Aeg_-2134324614" />
  <messageBuildingBlock
    xmi:id="_-XWQdwxzEeKMmbvHOtE4SA"
    nextVersions="_EB1YzSRMEeON6sEIseGaUg"
    name="AccountOwner"
    definition="Party that legally owns the account."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="AcctOwnr"
    complexType="_qU9DBeaPEd-q8fx_Zl_34A" />
  <messageBuildingBlock
    xmi:id="_-XWQewxzEeKMmbvHOtE4SA"
    nextVersions="_EB1YzyRMEeON6sEIseGaUg"
    name="SafekeepingAccount"
    definition="Account to or from which a securities entry is made."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SfkpgAcct"
    complexType="_T_vKAdp-Ed-ak6NoX_4Aeg_-178975462" />
  <messageBuildingBlock
    xmi:id="_-XWQfwxzEeKMmbvHOtE4SA"
    nextVersions="_EB1Y0SRMEeON6sEIseGaUg"
    name="Status"
    definition="Status information."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="Sts"
    complexType="_9aRywQ31EeKRyJSEMMwa2w" />
  <messageBuildingBlock
    xmi:id="_-XWQgwxzEeKMmbvHOtE4SA"
    nextVersions="_EB1Y0yRMEeON6sEIseGaUg"
    name="Transactions"
    definition="Details of the transactions reported."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="Txs"
    complexType="__r8NAQ3tEeKIIIcS0K4sAQ" />
  <messageDefinitionIdentifier
    businessArea="semt"
    messageFunctionality="018"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

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