acmt.006.001.03
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 %% AccountManagementStatusReportV03 recursion level 0 with max 0 AccountManagementStatusReportV03 *-- "1..1" MessageIdentification1 : MessageIdentification AccountManagementStatusReportV03 *-- "1..2" AdditionalReference3 : RelatedReference AccountManagementStatusReportV03 *-- "1..1" AccountManagementStatusAndReason2 : 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 an account opening instruction or account modification instruction that was previously received. For comparison, see the ISO20022 official specification
classDiagram direction tb %% AccountManagementStatusAndReason2 recursion level 0 with max 1 class AccountManagementStatusAndReason2{ AccountApplicationIdentification IsoMax35Text } AccountManagementStatusAndReason2 *-- "1..1" IStatus12Choice : Status %% IStatus12Choice recursion level 1 with max 1
AccountManagementStatusAndReason2 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Status | Status of the account opening instruction or account modification instruction. | IStatus12Choice - 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 AccountManagementStatusReportV03 implementation follows a specific implementaiton pattern. First of all, AccountManagementStatusReportV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AccountManagementStatusReportV03Document implements IOuterDocument. Because AccountManagementStatusReportV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AccountManagementStatusReportV03.
classDiagram class IOuterRecord AccountManagementStatusReportV03 --|> IOuterRecord : Implements AccountManagementStatusReportV03Document --|> IOuterDocument~AccountManagementStatusReportV03~ : Implements class IOuterDocument~AccountManagementStatusReportV03~ { AccountManagementStatusReportV03 Message }
Document wrapper for serialization
The only real purpose AccountManagementStatusReportV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:acmt.006.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AccountManagementStatusReportV03.ToDocument() method. The returned AccountManagementStatusReportV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram AccountManagementStatusReportV03Document *-- AccountManagementStatusReportV03 : 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.03">
<AcctMgmtStsRpt>
<MsgId>
<!-- MessageIdentification inner content -->
</MsgId>
<RltdRef>
<!-- RelatedReference inner content -->
</RltdRef>
<StsRpt>
<!-- StatusReport inner content -->
</StsRpt>
</AcctMgmtStsRpt>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_NL03ERGzEeKVqeHljBM1MQ"
nextVersions="_pfOqkR6qEeODgY9qxg6TFA"
previousVersion="_qp9IqNE9Ed-BzquC8wXy7w_6558662"
name="AccountManagementStatusReportV03"
definition="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."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="AcctMgmtStsRpt"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_NL03ExGzEeKVqeHljBM1MQ"
nextVersions="_pfOqkx6qEeODgY9qxg6TFA"
name="MessageIdentification"
definition="Identifies the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_NL03FxGzEeKVqeHljBM1MQ"
nextVersions="_pfOqlR6qEeODgY9qxg6TFA"
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="_NL03GxGzEeKVqeHljBM1MQ"
nextVersions="_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="_xpyPYRc5EeK5g-3oYI0_9Q" />
<messageDefinitionIdentifier
businessArea="acmt"
messageFunctionality="006"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.