RequestForAccountManagementStatusReportV03

acmt.005.001.03

Scope An account owner, for example, an investor or its designated agent, sends the RequestForAccountManagementStatusReport message to the account servicer, for example, a registrar, transfer agent or custodian bank to request the status of an AccountOpeningInstruction or an AccountModificationInstruction. Usage The RequestForAccountManagementStatusReport message is used to request the processing status of a previously sent AccountOpeningInstruction message or AccountModificationInstruction message for which a AccountDetailsConfirmation message has not yet been received.

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
%% RequestForAccountManagementStatusReportV03 recursion level 0 with max 0
RequestForAccountManagementStatusReportV03 *-- "1..1" MessageIdentification1 : MessageIdentification
RequestForAccountManagementStatusReportV03 *-- "1..1" AccountManagementMessageReference2 : RequestDetails
  

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

MessageIdentification building block

Reference that uniquely identifies a message from a business application standpoint. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
  

MessageIdentification1 members

RequestDetails building block

Information to identify the account management instruction for which the status is requested. Information about the message reference of the account management instruction message for which the status is requested. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AccountManagementMessageReference2 recursion level 0 with max 1
class AccountManagementMessageReference2{
    StatusRequestType AccountManagementType1Code
    AccountApplicationIdentification IsoMax35Text
}
AccountManagementMessageReference2 *-- "0..1" ILinkedMessage2Choice : LinkedReference
AccountManagementMessageReference2 *-- "0..1" InvestmentAccount45 : InvestmentAccount
%% ILinkedMessage2Choice recursion level 1 with max 1
%% InvestmentAccount45 recursion level 1 with max 1
class InvestmentAccount45{
    AccountName IsoMax35Text
    AccountDesignation IsoMax35Text
}
InvestmentAccount45 *-- "1..1" AccountIdentification1 : AccountIdentification
InvestmentAccount45 *-- "0..1" IOwnerIdentification1Choice : OwnerIdentification
InvestmentAccount45 *-- "0..1" IPartyIdentification2Choice : AccountServicer
  

AccountManagementMessageReference2 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    RequestForAccountManagementStatusReportV03 --|> IOuterRecord : Implements
    RequestForAccountManagementStatusReportV03Document --|> IOuterDocument~RequestForAccountManagementStatusReportV03~ : Implements
    class IOuterDocument~RequestForAccountManagementStatusReportV03~ {
        RequestForAccountManagementStatusReportV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    RequestForAccountManagementStatusReportV03Document *-- RequestForAccountManagementStatusReportV03 : 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:acmt.005.001.03">
    <ReqForAcctMgmtStsRpt>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <ReqDtls>
            <!-- RequestDetails inner content -->
        </ReqDtls>
    </ReqForAcctMgmtStsRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_DNhXIQguEeSy_NqeitQG4Q"
  nextVersions="_Kn-tYR8LEeWpZde3LQh6dg"
  previousVersion="_043Mq9E9Ed-BzquC8wXy7w_2127190710"
  name="RequestForAccountManagementStatusReportV03"
  definition="Scope&#xD;&#xA;An account owner, for example, an investor or its designated agent, sends the RequestForAccountManagementStatusReport message to the account servicer, for example, a registrar, transfer agent or custodian bank to request the status of an AccountOpeningInstruction or an AccountModificationInstruction.&#xD;&#xA;Usage&#xD;&#xA;The RequestForAccountManagementStatusReport message is used to request the processing status of a previously sent AccountOpeningInstruction message or AccountModificationInstruction message for which a AccountDetailsConfirmation message has not yet been received."
  registrationStatus="Provisionally Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="ReqForAcctMgmtStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_DNhXIwguEeSy_NqeitQG4Q"
    nextVersions="_Kn-tYx8LEeWpZde3LQh6dg"
    previousVersion="_043MrNE9Ed-BzquC8wXy7w_-809277134"
    name="MessageIdentification"
    definition="Reference that uniquely identifies a message from a business application standpoint."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_DNhXJQguEeSy_NqeitQG4Q"
    nextVersions="_Kn-tZR8LEeWpZde3LQh6dg"
    previousVersion="_043MrdE9Ed-BzquC8wXy7w_2127190736"
    name="RequestDetails"
    definition="Information to identify the account management instruction for which the status is requested."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="ReqDtls"
    complexType="_KUjOwQgvEeSy_NqeitQG4Q" />
  <messageDefinitionIdentifier
    businessArea="acmt"
    messageFunctionality="005"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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