Iso20022

IntraPositionMovementStatusAdvice002V07

semt.014.002.07

Scope An account servicer sends a IntraPositionMovementStatusAdvice to an account owner to advise the status of an intra-position movement instruction previously sent by the account owner. The account servicer/owner relationship may be:

Usage The message may also be used to:

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
%% IntraPositionMovementStatusAdvice002V07 recursion level 0 with max 0
IntraPositionMovementStatusAdvice002V07 *-- "1..1" TransactionIdentifications34 : TransactionIdentification
IntraPositionMovementStatusAdvice002V07 *-- "0..1" IIntraPositionProcessingStatus10Choice : ProcessingStatus
IntraPositionMovementStatusAdvice002V07 *-- "0..1" ISettlementStatus20Choice : SettlementStatus
IntraPositionMovementStatusAdvice002V07 *-- "0..1" IntraPositionDetails64 : TransactionDetails
IntraPositionMovementStatusAdvice002V07 *-- "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
%% TransactionIdentifications34 recursion level 0 with max 1
class TransactionIdentifications34{
    AccountOwnerTransactionIdentification IsoRestrictedFINXMax16Text
    AccountServicerTransactionIdentification IsoRestrictedFINXMax16Text
    MarketInfrastructureTransactionIdentification IsoRestrictedFINXMax16Text
    ProcessorTransactionIdentification IsoRestrictedFINXMax16Text
}

TransactionIdentifications34 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). IsoRestrictedFINXMax16Text - Required 1..1
AccountServicerTransactionIdentification Unambiguous identification of the transaction as known by the account servicer. IsoRestrictedFINXMax16Text - Optional 0..1
MarketInfrastructureTransactionIdentification Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities. IsoRestrictedFINXMax16Text - 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. IsoRestrictedFINXMax16Text - 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
%% IIntraPositionProcessingStatus10Choice recursion level 0 with max 1

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

SettlementStatus20Choice 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
%% IntraPositionDetails64 recursion level 0 with max 1
class IntraPositionDetails64{
    PoolIdentification IsoRestrictedFINXMax16Text
    AcknowledgedStatusTimeStamp IsoISODateTime
}
IntraPositionDetails64 *-- "0..1" IPartyIdentification136Choice : AccountOwner
IntraPositionDetails64 *-- "0..1" SecuritiesAccount30 : SafekeepingAccount
IntraPositionDetails64 *-- "0..1" BlockChainAddressWallet7 : BlockChainAddressOrWallet
IntraPositionDetails64 *-- "1..1" SecurityIdentification20 : FinancialInstrumentIdentification
IntraPositionDetails64 *-- "1..1" IFinancialInstrumentQuantity36Choice : SettlementQuantity
IntraPositionDetails64 *-- "0..1" GenericIdentification39 : LotNumber
IntraPositionDetails64 *-- "1..1" IDateAndDateTime2Choice : SettlementDate
IntraPositionDetails64 *-- "0..1" ISecuritiesBalanceType11Choice : BalanceFrom
IntraPositionDetails64 *-- "0..1" ISecuritiesBalanceType11Choice : BalanceTo
%% IPartyIdentification136Choice recursion level 1 with max 1
%% SecuritiesAccount30 recursion level 1 with max 1
class SecuritiesAccount30{
    Identification IsoRestrictedFINXMax35Text
    Name IsoMax70Text
}
SecuritiesAccount30 *-- "0..1" GenericIdentification47 : Type
%% BlockChainAddressWallet7 recursion level 1 with max 1
class BlockChainAddressWallet7{
    Identification IsoRestrictedFINXMax140Text
    Name IsoRestrictedFINXMax70Text
}
BlockChainAddressWallet7 *-- "0..1" GenericIdentification47 : Type
%% SecurityIdentification20 recursion level 1 with max 1
class SecurityIdentification20{
    ISIN IsoISINOct2015Identifier
    Description IsoRestrictedFINXMax140Text
}
SecurityIdentification20 *-- "0..0" OtherIdentification2 : OtherIdentification
%% IFinancialInstrumentQuantity36Choice recursion level 1 with max 1
%% GenericIdentification39 recursion level 1 with max 1
class GenericIdentification39{
    Identification IsoRestrictedFINMax30Text
    Issuer IsoRestrictedFINMax8Text
}
%% IDateAndDateTime2Choice recursion level 1 with max 1
%% ISecuritiesBalanceType11Choice recursion level 1 with max 1
%% ISecuritiesBalanceType11Choice recursion level 1 with max 1

IntraPositionDetails64 members

Member name Description Data Type / Multiplicity
PoolIdentification Collective reference identifying a set of messages. IsoRestrictedFINXMax16Text - Optional 0..1
AccountOwner Party that legally owns the account. IPartyIdentification136Choice - Optional 0..1
SafekeepingAccount Account to or from which a securities entry is made. SecuritiesAccount30 - Optional 0..1
BlockChainAddressOrWallet Blockchain address or wallet where digital assets are maintained. This is the equivalent of safekeeping account for digital assets. BlockChainAddressWallet7 - Optional 0..1
FinancialInstrumentIdentification Financial instruments representing a sum of rights of the investor vis-a-vis the issuer. SecurityIdentification20 - Required 1..1
SettlementQuantity Total quantity of securities to be settled. IFinancialInstrumentQuantity36Choice - Required 1..1
LotNumber Number identifying a lot constituting the financial instrument. GenericIdentification39 - Optional 0..1
SettlementDate Date and time at which the securities are to be moved. IDateAndDateTime2Choice - Required 1..1
AcknowledgedStatusTimeStamp Time stamp on when the transaction is acknowledged. IsoISODateTime - Optional 0..1
BalanceFrom Balance from which the securities are moving. ISecuritiesBalanceType11Choice - Optional 0..1
BalanceTo Balance to which the securities are moving. ISecuritiesBalanceType11Choice - 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 IntraPositionMovementStatusAdvice002V07 implementation follows a specific implementaiton pattern. First of all, IntraPositionMovementStatusAdvice002V07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, IntraPositionMovementStatusAdvice002V07Document implements IOuterDocument. Because IntraPositionMovementStatusAdvice002V07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type IntraPositionMovementStatusAdvice002V07.

classDiagram
    class IOuterRecord
    IntraPositionMovementStatusAdvice002V07 --|> IOuterRecord : Implements
    IntraPositionMovementStatusAdvice002V07Document --|> IOuterDocument~IntraPositionMovementStatusAdvice002V07~ : Implements
    class IOuterDocument~IntraPositionMovementStatusAdvice002V07~ {
        IntraPositionMovementStatusAdvice002V07 Message
     }

Document wrapper for serialization

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

classDiagram
    IntraPositionMovementStatusAdvice002V07Document *-- IntraPositionMovementStatusAdvice002V07 : 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.002.07">
    <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="_cdkNYzi8Eeydid5dcNPKvg"
  previousVersion="_65NZ7_fUEeiNZp_PtLohLw"
  name="IntraPositionMovementStatusAdvice002V07"
  definition="Scope&#xD;&#xA;An account servicer sends a IntraPositionMovementStatusAdvice to an account owner to advise the status of an 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;&#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 using the relevant elements in the Business Application Header."
  registrationStatus="Registered"
  messageSet="_KoChkKS_EeWiN6v48CBCXg _26G2kVI3EeyUbfjRDFS84A"
  xmlTag="IntraPosMvmntStsAdvc"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_cdk0czi8Eeydid5dcNPKvg"
    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="_5SFAI5NLEeWGlc8L7oPDIg" />
  <messageBuildingBlock
    xmi:id="_cdk0dTi8Eeydid5dcNPKvg"
    name="ProcessingStatus"
    definition="Provides details on the processing status of the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PrcgSts"
    complexType="_cdk0oTi8Eeydid5dcNPKvg" />
  <messageBuildingBlock
    xmi:id="_cdk0dzi8Eeydid5dcNPKvg"
    name="SettlementStatus"
    definition="Provides the status of settlement of a transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SttlmSts"
    complexType="_5SGOQ5NLEeWGlc8L7oPDIg" />
  <messageBuildingBlock
    xmi:id="_cdk0eTi8Eeydid5dcNPKvg"
    name="TransactionDetails"
    definition="Identifies the details of the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="TxDtls"
    complexType="_cdlc1Ti8Eeydid5dcNPKvg" />
  <messageBuildingBlock
    xmi:id="_cdk0ezi8Eeydid5dcNPKvg"
    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="002"
    version="07" />
</messageDefinition>

ISO Building Blocks

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