semt.014.001.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:
- 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.
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 %% IntraPositionMovementStatusAdviceV07 recursion level 0 with max 0 IntraPositionMovementStatusAdviceV07 *-- "1..1" TransactionIdentifications29 : TransactionIdentification IntraPositionMovementStatusAdviceV07 *-- "0..1" IIntraPositionProcessingStatus9Choice : ProcessingStatus IntraPositionMovementStatusAdviceV07 *-- "0..1" ISettlementStatus16Choice : SettlementStatus IntraPositionMovementStatusAdviceV07 *-- "0..1" IntraPositionDetails60 : TransactionDetails IntraPositionMovementStatusAdviceV07 *-- "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 %% TransactionIdentifications29 recursion level 0 with max 1 class TransactionIdentifications29{ AccountOwnerTransactionIdentification IsoMax35Text AccountServicerTransactionIdentification IsoMax35Text MarketInfrastructureTransactionIdentification IsoMax35Text ProcessorTransactionIdentification IsoMax35Text }
TransactionIdentifications29 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 %% IIntraPositionProcessingStatus9Choice recursion level 0 with max 1
IntraPositionProcessingStatus9Choice 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 %% ISettlementStatus16Choice recursion level 0 with max 1
SettlementStatus16Choice 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 %% IntraPositionDetails60 recursion level 0 with max 1 class IntraPositionDetails60{ PoolIdentification IsoMax35Text AcknowledgedStatusTimeStamp IsoISODateTime } IntraPositionDetails60 *-- "0..1" IPartyIdentification127Choice : AccountOwner IntraPositionDetails60 *-- "0..1" SecuritiesAccount19 : SafekeepingAccount IntraPositionDetails60 *-- "0..1" BlockChainAddressWallet3 : BlockChainAddressOrWallet IntraPositionDetails60 *-- "1..1" SecurityIdentification19 : FinancialInstrumentIdentification IntraPositionDetails60 *-- "1..1" IFinancialInstrumentQuantity33Choice : SettlementQuantity IntraPositionDetails60 *-- "0..1" GenericIdentification37 : LotNumber IntraPositionDetails60 *-- "1..1" IDateAndDateTime2Choice : SettlementDate IntraPositionDetails60 *-- "0..1" ISecuritiesBalanceType7Choice : BalanceFrom IntraPositionDetails60 *-- "0..1" ISecuritiesBalanceType7Choice : BalanceTo %% IPartyIdentification127Choice recursion level 1 with max 1 %% SecuritiesAccount19 recursion level 1 with max 1 class SecuritiesAccount19{ Identification IsoMax35Text Name IsoMax70Text } SecuritiesAccount19 *-- "0..1" GenericIdentification30 : Type %% BlockChainAddressWallet3 recursion level 1 with max 1 class BlockChainAddressWallet3{ Identification IsoMax140Text Name IsoMax70Text } BlockChainAddressWallet3 *-- "0..1" GenericIdentification30 : Type %% SecurityIdentification19 recursion level 1 with max 1 class SecurityIdentification19{ ISIN IsoISINOct2015Identifier Description IsoMax140Text } SecurityIdentification19 *-- "0..0" OtherIdentification1 : OtherIdentification %% IFinancialInstrumentQuantity33Choice recursion level 1 with max 1 %% GenericIdentification37 recursion level 1 with max 1 class GenericIdentification37{ Identification IsoMax35Text Issuer IsoMax35Text } %% IDateAndDateTime2Choice recursion level 1 with max 1 %% ISecuritiesBalanceType7Choice recursion level 1 with max 1 %% ISecuritiesBalanceType7Choice recursion level 1 with max 1
IntraPositionDetails60 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. | IPartyIdentification127Choice - Optional 0..1 |
SafekeepingAccount | Account to or from which a securities entry is made. | SecuritiesAccount19 - Optional 0..1 |
BlockChainAddressOrWallet | Blockchain address or wallet where digital assets are maintained. This is the equivalent of safekeeping account for digital assets. | BlockChainAddressWallet3 - Optional 0..1 |
FinancialInstrumentIdentification | Financial instruments representing a sum of rights of the investor vis-a-vis the issuer. | SecurityIdentification19 - Required 1..1 |
SettlementQuantity | Total quantity of securities to be settled. | IFinancialInstrumentQuantity33Choice - Required 1..1 |
LotNumber | Number identifying a lot constituting the financial instrument. | GenericIdentification37 - 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. | ISecuritiesBalanceType7Choice - Optional 0..1 |
BalanceTo | Balance to which the securities are moving. | ISecuritiesBalanceType7Choice - 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 IntraPositionMovementStatusAdviceV07 implementation follows a specific implementaiton pattern. First of all, IntraPositionMovementStatusAdviceV07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, IntraPositionMovementStatusAdviceV07Document implements IOuterDocument. Because IntraPositionMovementStatusAdviceV07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type IntraPositionMovementStatusAdviceV07.
classDiagram class IOuterRecord IntraPositionMovementStatusAdviceV07 --|> IOuterRecord : Implements IntraPositionMovementStatusAdviceV07Document --|> IOuterDocument~IntraPositionMovementStatusAdviceV07~ : Implements class IOuterDocument~IntraPositionMovementStatusAdviceV07~ { IntraPositionMovementStatusAdviceV07 Message }
Document wrapper for serialization
The only real purpose IntraPositionMovementStatusAdviceV07Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:semt.014.001.07’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using IntraPositionMovementStatusAdviceV07.ToDocument() method. The returned IntraPositionMovementStatusAdviceV07Document value will serialize correctly according to ISO 20022 standards.
classDiagram IntraPositionMovementStatusAdviceV07Document *-- IntraPositionMovementStatusAdviceV07 : 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.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="_VxmU8Sp0EeyR9JrVGfaMKw"
previousVersion="_Y75IUewAEeiazoAmcoGsBQ"
name="IntraPositionMovementStatusAdviceV07"
definition="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:
- 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."
registrationStatus="Registered"
messageSet="_xiys0WfyEeOLcMuJoUvTAg"
xmlTag="IntraPosMvmntStsAdvc"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_VxmU-Sp0EeyR9JrVGfaMKw"
previousVersion="_Y75IU-wAEeiazoAmcoGsBQ"
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="_cYp1gTntEeWfSKvvZlhRKg" />
<messageBuildingBlock
xmi:id="_VxmU-yp0EeyR9JrVGfaMKw"
previousVersion="_Y75IVewAEeiazoAmcoGsBQ"
name="ProcessingStatus"
definition="Provides details on the processing status of the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PrcgSts"
complexType="_ZJraQStUEeyhipY4f42fZQ" />
<messageBuildingBlock
xmi:id="_VxmU_Sp0EeyR9JrVGfaMKw"
previousVersion="_Y75IV-wAEeiazoAmcoGsBQ"
name="SettlementStatus"
definition="Provides the status of settlement of a transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SttlmSts"
complexType="_zV8niTp4EeWVrPy0StzzSg" />
<messageBuildingBlock
xmi:id="_VxmU_yp0EeyR9JrVGfaMKw"
previousVersion="_Y75IWewAEeiazoAmcoGsBQ"
name="TransactionDetails"
definition="Identifies the details of the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="TxDtls"
complexType="_28KbYSp_EeyR9JrVGfaMKw" />
<messageBuildingBlock
xmi:id="_VxmVASp0EeyR9JrVGfaMKw"
previousVersion="_Y75IW-wAEeiazoAmcoGsBQ"
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="07" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.