Iso20022

IntraPositionMovementStatusAdviceV02

semt.014.001.02

Scope An account servicer sends a IntraPositionMovementStatusAdvice to an account owner to advise the status of a intra-position movement instruction previously sent by the account owner. 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
%% IntraPositionMovementStatusAdviceV02 recursion level 0 with max 0
IntraPositionMovementStatusAdviceV02 *-- "1..1" TransactionIdentifications10 : TransactionIdentification
IntraPositionMovementStatusAdviceV02 *-- "0..1" IIntraPositionProcessingStatus1Choice : ProcessingStatus
IntraPositionMovementStatusAdviceV02 *-- "0..1" ISettlementStatus2Choice : SettlementStatus
IntraPositionMovementStatusAdviceV02 *-- "0..1" IntraPositionDetails9 : TransactionDetails
IntraPositionMovementStatusAdviceV02 *-- "0..1" SupplementaryData1 : SupplementaryData

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

TransactionIdentification building block

Unambiguous identification of a transaction as per the account owner (or the instructing party managing the account). Unique identifier of a document, message or transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransactionIdentifications10 recursion level 0 with max 1
class TransactionIdentifications10{
    AccountOwnerTransactionIdentification IsoMax35Text
    AccountServicerTransactionIdentification IsoMax35Text
    MarketInfrastructureTransactionIdentification IsoMax35Text
    ProcessorTransactionIdentification IsoMax35Text
}

TransactionIdentifications10 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

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

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

SettlementStatus2Choice members

Member name Description Data Type / Multiplicity

TransactionDetails building block

Identifies the details of the transaction. Details of the intra-position movement. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IntraPositionDetails9 recursion level 0 with max 1
class IntraPositionDetails9{
    PoolIdentification IsoMax35Text
}
IntraPositionDetails9 *-- "0..1" IPartyIdentification36Choice : AccountOwner
IntraPositionDetails9 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount
IntraPositionDetails9 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification
IntraPositionDetails9 *-- "1..1" IFinancialInstrumentQuantity1Choice : SettledQuantity
IntraPositionDetails9 *-- "1..1" IDateAndDateTimeChoice : SettlementDate
IntraPositionDetails9 *-- "0..1" ISecuritiesBalanceType2Choice : BalanceFrom
IntraPositionDetails9 *-- "0..1" ISecuritiesBalanceType2Choice : BalanceTo
%% 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
%% SecurityIdentification14 recursion level 1 with max 1
class SecurityIdentification14{
    ISIN IsoISINIdentifier
    Description IsoMax140Text
}
SecurityIdentification14 *-- "0..0" OtherIdentification1 : OtherIdentification
%% IFinancialInstrumentQuantity1Choice recursion level 1 with max 1
%% IDateAndDateTimeChoice recursion level 1 with max 1
%% ISecuritiesBalanceType2Choice recursion level 1 with max 1
%% ISecuritiesBalanceType2Choice recursion level 1 with max 1

IntraPositionDetails9 members

Member name Description Data Type / Multiplicity
PoolIdentification Collective reference identifying a set of messages. 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
FinancialInstrumentIdentification Financial instruments representing a sum of rights of the investor vis-a-vis the issuer. SecurityIdentification14 - Required 1..1
SettledQuantity Quantity of financial instrument effectively settled. IFinancialInstrumentQuantity1Choice - Required 1..1
SettlementDate Date and time at which the securities are to be moved. IDateAndDateTimeChoice - Required 1..1
BalanceFrom Balance from which the securities are moving. ISecuritiesBalanceType2Choice - Optional 0..1
BalanceTo Balance to which the securities are moving. ISecuritiesBalanceType2Choice - 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 IntraPositionMovementStatusAdviceV02 implementation follows a specific implementaiton pattern. First of all, IntraPositionMovementStatusAdviceV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, IntraPositionMovementStatusAdviceV02Document implements IOuterDocument. Because IntraPositionMovementStatusAdviceV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type IntraPositionMovementStatusAdviceV02.

classDiagram
    class IOuterRecord
    IntraPositionMovementStatusAdviceV02 --|> IOuterRecord : Implements
    IntraPositionMovementStatusAdviceV02Document --|> IOuterDocument~IntraPositionMovementStatusAdviceV02~ : Implements
    class IOuterDocument~IntraPositionMovementStatusAdviceV02~ {
        IntraPositionMovementStatusAdviceV02 Message
     }

Document wrapper for serialization

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

classDiagram
    IntraPositionMovementStatusAdviceV02Document *-- IntraPositionMovementStatusAdviceV02 : 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.014.001.02">
    <IntraPosMvmntStsAdvc>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <PrcgSts>
            <!-- ProcessingStatus inner content -->
        </PrcgSts>
        <SttlmSts>
            <!-- SettlementStatus inner content -->
        </SttlmSts>
        <TxDtls>
            <!-- TransactionDetails inner content -->
        </TxDtls>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </IntraPosMvmntStsAdvc>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_ZPl4AdtYEd-RF5yaMAVhAw"
  nextVersions="_onEuAfvfEeCBQp5TnX1XKQ"
  previousVersion="_MerQSNFSEd-BzquC8wXy7w_-1468598967"
  name="IntraPositionMovementStatusAdviceV02"
  definition="Scope&#xD;&#xA;An account servicer sends a IntraPositionMovementStatusAdvice to an account owner to advise the status of a intra-position movement instruction previously sent by the account owner.&#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&#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;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="IntraPosMvmntStsAdvc"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_ZPl4E9tYEd-RF5yaMAVhAw"
    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="_ZPl4FdtYEd-RF5yaMAVhAw"
    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" />
  <messageBuildingBlock
    xmi:id="_ZPl4BdtYEd-RF5yaMAVhAw"
    name="TransactionIdentification"
    definition="Unambiguous identification of a transaction as per the account owner (or the instructing party managing the account)."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_Wc6wYdzqEd-tnM7aRm4nqg" />
  <messageBuildingBlock
    xmi:id="_ZPl4B9tYEd-RF5yaMAVhAw"
    name="ProcessingStatus"
    definition="Provides details on the processing status of the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PrcgSts"
    complexType="_UW1baNp-Ed-ak6NoX_4Aeg_252032743" />
  <messageBuildingBlock
    xmi:id="_ZPl4CdtYEd-RF5yaMAVhAw"
    name="SettlementStatus"
    definition="Provides the status of settlement of a transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SttlmSts"
    complexType="_UZ9n4dp-Ed-ak6NoX_4Aeg_-647907102" />
  <messageBuildingBlock
    xmi:id="_ZPl4C9tYEd-RF5yaMAVhAw"
    name="TransactionDetails"
    definition="Identifies the details of the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="TxDtls"
    complexType="_qVQlB-aPEd-q8fx_Zl_34A" />
  <messageBuildingBlock
    xmi:id="_ZPl4EdtYEd-RF5yaMAVhAw"
    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="semt"
    messageFunctionality="014"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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