AccountManagementStatusReportV04

acmt.006.001.04

Scope An account servicer, for example, a registrar, transfer agent or custodian bank 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
%% AccountManagementStatusReportV04 recursion level 0 with max 0
AccountManagementStatusReportV04 *-- "1..1" MessageIdentification1 : MessageIdentification
AccountManagementStatusReportV04 *-- "1..2" AdditionalReference3 : RelatedReference
AccountManagementStatusReportV04 *-- "1..1" AccountManagementStatusAndReason3 : StatusReport
AccountManagementStatusReportV04 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
AccountManagementStatusReportV04 *-- "0..1" Extension1 : Extension
  

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

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

StatusReport building block

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

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

AccountManagementStatusAndReason3 members

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

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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AccountManagementStatusReportV04 --|> IOuterRecord : Implements
    AccountManagementStatusReportV04Document --|> IOuterDocument~AccountManagementStatusReportV04~ : Implements
    class IOuterDocument~AccountManagementStatusReportV04~ {
        AccountManagementStatusReportV04 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AccountManagementStatusReportV04Document *-- AccountManagementStatusReportV04 : 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.04">
    <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="_pfOqkR6qEeODgY9qxg6TFA"
  nextVersions="_OT8o0R8LEeWpZde3LQh6dg"
  previousVersion="_NL03ERGzEeKVqeHljBM1MQ"
  name="AccountManagementStatusReportV04"
  definition="Scope&#xD;&#xA;An account servicer, for example, a registrar, transfer agent or custodian bank 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="_pfOqkx6qEeODgY9qxg6TFA"
    nextVersions="_OT8o0x8LEeWpZde3LQh6dg"
    previousVersion="_NL03ExGzEeKVqeHljBM1MQ"
    name="MessageIdentification"
    definition="Identifies the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_pfOqlR6qEeODgY9qxg6TFA"
    nextVersions="_OT8o1R8LEeWpZde3LQh6dg"
    previousVersion="_NL03FxGzEeKVqeHljBM1MQ"
    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="_pfOqlx6qEeODgY9qxg6TFA"
    nextVersions="_OT8o1x8LEeWpZde3LQh6dg"
    previousVersion="_NL03GxGzEeKVqeHljBM1MQ"
    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="_VTO14R6rEeODgY9qxg6TFA" />
  <messageBuildingBlock
    xmi:id="_BbZhgSWKEeO47OP3Gphiaw"
    nextVersions="_OT8o2R8LEeWpZde3LQh6dg"
    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="_TcpB4SP0EeO-CsDf20Q5hg"
    nextVersions="_OT8o2x8LEeWpZde3LQh6dg"
    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="04" />
</messageDefinition>

ISO Building Blocks

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