AccountManagementStatusReportV02

acmt.006.001.02

Scope An account servicer, eg, a registrar, transfer agent or custodian bank sends the AccountManagementStatusReport message to an account owner or its designated agent, eg, 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
%% AccountManagementStatusReportV02 recursion level 0 with max 0
AccountManagementStatusReportV02 *-- "1..1" MessageIdentification1 : MessageIdentification
AccountManagementStatusReportV02 *-- "1..2" AdditionalReference3 : RelatedReference
AccountManagementStatusReportV02 *-- "1..1" AccountManagementStatusAndReason1 : StatusReport
  

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

MessageIdentification building block

Identifies the message. 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. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

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

AdditionalReference3 members

Member name Description Data Type / Multiplicity
Reference Business reference of a message assigned by the party issuing the message. This reference must be unique amongst all messages of the same name sent by the same party. IsoMax35Text - Required 1..1
ReferenceIssuer Issuer of the reference. IPartyIdentification2Choice - Optional 0..1
MessageName Name of a 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 report of a account opening instruction or account modification instruction that was previously received. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AccountManagementStatusAndReason1 recursion level 0 with max 1
class AccountManagementStatusAndReason1{
    Status AccountManagementStatus1Code
    AccountApplicationIdentification IsoMax35Text
}
AccountManagementStatusAndReason1 *-- "1..1" RejectedStatus5 : Rejected
%% RejectedStatus5 recursion level 1 with max 1
class RejectedStatus5{
    Reason RejectedStatusReason6Code
    ExtendedReason IsoExtended350Code
}
  

AccountManagementStatusAndReason1 members

Member name Description Data Type / Multiplicity
Status Status of the account opening instruction or account modification instruction. AccountManagementStatus1Code - Required 1..1
Rejected Status of the order is rejected. RejectedStatus5 - Required 1..1
AccountApplicationIdentification Unique and unambiguous identifier of the account opening or modification instruction at application level. IsoMax35Text - Optional 0..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AccountManagementStatusReportV02 --|> IOuterRecord : Implements
    AccountManagementStatusReportV02Document --|> IOuterDocument~AccountManagementStatusReportV02~ : Implements
    class IOuterDocument~AccountManagementStatusReportV02~ {
        AccountManagementStatusReportV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AccountManagementStatusReportV02Document *-- AccountManagementStatusReportV02 : 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.02">
    <AcctMgmtStsRptV02>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <RltdRef>
            <!-- RelatedReference inner content -->
        </RltdRef>
        <StsRpt>
            <!-- StatusReport inner content -->
        </StsRpt>
    </AcctMgmtStsRptV02>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_qp9IqNE9Ed-BzquC8wXy7w_6558662"
  nextVersions="_NL03ERGzEeKVqeHljBM1MQ"
  name="AccountManagementStatusReportV02"
  definition="Scope&#xD;&#xA;An account servicer, eg, a registrar, transfer agent or custodian bank sends the AccountManagementStatusReport message to an account owner or its designated agent, eg, 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="AcctMgmtStsRptV02"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_qqG5oNE9Ed-BzquC8wXy7w_-1412150000"
    name="MessageIdentification"
    definition="Identifies the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_qqG5odE9Ed-BzquC8wXy7w_1684015362"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="2"
    minOccurs="1"
    xmlTag="RltdRef"
    complexType="_Q6vvAdp-Ed-ak6NoX_4Aeg_2101402955" />
  <messageBuildingBlock
    xmi:id="_qqG5otE9Ed-BzquC8wXy7w_200483730"
    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="_RElAd9p-Ed-ak6NoX_4Aeg_-169847202" />
  <messageDefinitionIdentifier
    businessArea="acmt"
    messageFunctionality="006"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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