AccountManagementStatusReportV05

acmt.006.001.05

Scope An account servicer, for example, a registrar, transfer agent, custodian bank or securities depository sends the AccountManagementStatusReport message to the account owner or its designated agent, for example, an investor to report on the receipt or the processing status of a previously received AccountOpeningInstruction or AccountModificationInstruction or GetAccountDetails message. Usage The AccountManagementStatusReport message is used to provide the processing status of a previously received AccountOpeningInstruction or of an AccountModificationInstruction message. The AccountManagementStatusReport message is also used by an account servicer to reject an AccountOpeningInstruction or AccountModificationInstruction or GetAccountDetails message when the message is not compliant with the agreed SLA or when the account cannot be uniquely identified. The account owner may report that the status of the instruction is either rejected, accepted, that the instruction is being processed or that the instruction has been forwarded to the next intermediary party for further processing.

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
%% AccountManagementStatusReportV05 recursion level 0 with max 0
AccountManagementStatusReportV05 *-- "1..1" MessageIdentification1 : MessageIdentification
AccountManagementStatusReportV05 *-- "1..2" AdditionalReference6 : RelatedReference
AccountManagementStatusReportV05 *-- "1..1" AccountManagementStatusAndReason4 : StatusReport
AccountManagementStatusReportV05 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
AccountManagementStatusReportV05 *-- "0..1" Extension1 : Extension
  

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

MessageIdentification building block

Reference that uniquely identifies the 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

Member name Description Data Type / Multiplicity
Identification Identification of the message. IsoMax35Text - Required 1..1
CreationDateTime Date of creation of the message. IsoISODateTime - Required 1..1

RelatedReference building block

Reference to a linked message that was previously received. Reference to a related message or transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference6 recursion level 0 with max 1
class AdditionalReference6{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference6 *-- "0..1" IPartyIdentification90Choice : ReferenceIssuer
%% IPartyIdentification90Choice recursion level 1 with max 1
  

AdditionalReference6 members

Member name Description Data Type / Multiplicity
Reference Message identification of a message. This reference was assigned by the party issuing the message. IsoMax35Text - Required 1..1
ReferenceIssuer Issuer of the reference. IPartyIdentification90Choice - Optional 0..1
MessageName Name of the message. IsoMax35Text - Optional 0..1

StatusReport building block

Status report details of an account opening instruction or account modification instruction that was previously received. Status information. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AccountManagementStatusAndReason4 recursion level 0 with max 1
class AccountManagementStatusAndReason4{
    AccountApplicationIdentification IsoMax35Text
    ExistingAccountIdentification IsoMax35Text
}
AccountManagementStatusAndReason4 *-- "1..1" IStatus20Choice : Status
%% IStatus20Choice recursion level 1 with max 1
  

AccountManagementStatusAndReason4 members

Member name Description Data Type / Multiplicity
Status Status of the account opening instruction or account modification instruction. IStatus20Choice - Required 1..1
AccountApplicationIdentification Unique and unambiguous identifier of the account opening or modification instruction at application level. IsoMax35Text - Optional 0..1
ExistingAccountIdentification Account to which the account opening is related. IsoMax35Text - Optional 0..1

MarketPracticeVersion building block

Identifies the market practice to which the message conforms. Identifies the implementation and version. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MarketPracticeVersion1 recursion level 0 with max 1
class MarketPracticeVersion1{
    Name IsoMax35Text
    Date IsoISOYearMonth
    Number IsoMax35Text
}
  

MarketPracticeVersion1 members

Member name Description Data Type / Multiplicity
Name Market practice, for example, “UKTRANSFERS”, “FINDELSLT”. IsoMax35Text - Required 1..1
Date Year and month, for example, 2013-06. IsoISOYearMonth - Optional 0..1
Number Version of the market practice. IsoMax35Text - Optional 0..1

Extension 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
%% Extension1 recursion level 0 with max 1
class Extension1{
    PlaceAndName IsoMax350Text
    Text IsoMax350Text
}
  

Extension1 members

Member name Description Data Type / Multiplicity
PlaceAndName Name qualifying the information provided in the Text field, and place where this information should be inserted. IsoMax350Text - Required 1..1
Text Text of the extension. IsoMax350Text - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AccountManagementStatusReportV05 --|> IOuterRecord : Implements
    AccountManagementStatusReportV05Document --|> IOuterDocument~AccountManagementStatusReportV05~ : Implements
    class IOuterDocument~AccountManagementStatusReportV05~ {
        AccountManagementStatusReportV05 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AccountManagementStatusReportV05Document *-- AccountManagementStatusReportV05 : 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.006.001.05">
    <AcctMgmtStsRpt>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <RltdRef>
            <!-- RelatedReference inner content -->
        </RltdRef>
        <StsRpt>
            <!-- StatusReport inner content -->
        </StsRpt>
        <MktPrctcVrsn>
            <!-- MarketPracticeVersion inner content -->
        </MktPrctcVrsn>
        <Xtnsn>
            <!-- Extension inner content -->
        </Xtnsn>
    </AcctMgmtStsRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_OT8o0R8LEeWpZde3LQh6dg"
  nextVersions="_9r1N0UNDEeaknIuOb43xYQ"
  previousVersion="_pfOqkR6qEeODgY9qxg6TFA"
  name="AccountManagementStatusReportV05"
  definition="Scope&#xD;&#xA;An account servicer, for example, a registrar, transfer agent, custodian bank or securities depository sends the AccountManagementStatusReport message to the account owner or its designated agent, for example, an investor to report on the receipt or the processing status of a previously received AccountOpeningInstruction or AccountModificationInstruction or GetAccountDetails message.&#xD;&#xA;Usage&#xD;&#xA;The AccountManagementStatusReport message is used to provide the processing status of a previously received AccountOpeningInstruction or of an AccountModificationInstruction message.&#xD;&#xA;The AccountManagementStatusReport message is also used by an account servicer to reject an AccountOpeningInstruction or AccountModificationInstruction or GetAccountDetails message when the message is not compliant with the agreed SLA or when the account cannot be uniquely identified.&#xD;&#xA;The account owner may report that the status of the instruction is either rejected, accepted, that the instruction is being processed or that the instruction has been forwarded to the next intermediary party for further processing."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AcctMgmtStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_OT8o0x8LEeWpZde3LQh6dg"
    nextVersions="_9r1N00NDEeaknIuOb43xYQ"
    previousVersion="_pfOqkx6qEeODgY9qxg6TFA"
    name="MessageIdentification"
    definition="Reference that uniquely identifies the message from a business application standpoint."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_OT8o1R8LEeWpZde3LQh6dg"
    nextVersions="_9r1N1UNDEeaknIuOb43xYQ"
    previousVersion="_pfOqlR6qEeODgY9qxg6TFA"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="2"
    minOccurs="1"
    xmlTag="RltdRef"
    complexType="_JBe719edEeSA_uUacqhl1Q" />
  <messageBuildingBlock
    xmi:id="_OT8o1x8LEeWpZde3LQh6dg"
    nextVersions="_9r1N10NDEeaknIuOb43xYQ"
    previousVersion="_pfOqlx6qEeODgY9qxg6TFA"
    name="StatusReport"
    definition="Status report details of an account opening instruction or account modification instruction that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="StsRpt"
    complexType="_pxVPYSGaEeWKAaDJcYGKLw" />
  <messageBuildingBlock
    xmi:id="_OT8o2R8LEeWpZde3LQh6dg"
    nextVersions="_9r1N2UNDEeaknIuOb43xYQ"
    previousVersion="_BbZhgSWKEeO47OP3Gphiaw"
    name="MarketPracticeVersion"
    definition="Identifies the market practice to which the message conforms."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MktPrctcVrsn"
    complexType="_FaNY0RUVEeOIaq8KyCdIDQ" />
  <messageBuildingBlock
    xmi:id="_OT8o2x8LEeWpZde3LQh6dg"
    nextVersions="_9r1N20NDEeaknIuOb43xYQ"
    previousVersion="_TcpB4SP0EeO-CsDf20Q5hg"
    name="Extension"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="Xtnsn"
    complexType="_Q6vvCNp-Ed-ak6NoX_4Aeg_1503007069" />
  <messageDefinitionIdentifier
    businessArea="acmt"
    messageFunctionality="006"
    flavour="001"
    version="05" />
</messageDefinition>

ISO Building Blocks

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