AccountReportRequestV02

acmt.013.001.02

The AccountReportRequest message is sent from an organisation to a financial institution for reporting purposes. It is a request for an account report. This message can be sent at any time outside of account opening, maintenance or closing processes.

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
%% AccountReportRequestV02 recursion level 0 with max 0
AccountReportRequestV02 *-- "1..1" References4 : References
AccountReportRequestV02 *-- "0..1" OrganisationIdentification8 : From
AccountReportRequestV02 *-- "1..1" AccountForAction1 : AccountIdentification
AccountReportRequestV02 *-- "1..1" BranchAndFinancialInstitutionIdentification5 : AccountServicerIdentification
AccountReportRequestV02 *-- "1..1" OrganisationIdentification8 : OrganisationIdentification
AccountReportRequestV02 *-- "0..1" PartyAndSignature2 : DigitalSignature
AccountReportRequestV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

References building block

Set of elements for the identification of the message and related references. Set of elements for the identification of the message and related references. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% References4 recursion level 0 with max 1
class References4{
    AttachedDocumentName IsoMax70Text
}
References4 *-- "1..1" MessageIdentification1 : MessageIdentification
References4 *-- "1..1" MessageIdentification1 : ProcessIdentification
%% MessageIdentification1 recursion level 1 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
%% MessageIdentification1 recursion level 1 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
  

References4 members

Member name Description Data Type / Multiplicity
MessageIdentification Identifies a message by a unique identifier and the date and time when the message was created by the sender. MessageIdentification1 - Required 1..1
ProcessIdentification Identifies a process by a unique identifier and the date and time when the first message belonging to the process was created by the sender. The process identification remains the same in all messages belonging to the same process, from the initial request message to the final account report closing the process. MessageIdentification1 - Required 1..1
AttachedDocumentName File name of a document logically related to the request. IsoMax70Text - Unknown 0..0

From building block

Identifies the business sender of the message, if it is not the account owner or account servicing financial institution. Unique and unambiguous way to identify an organisation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OrganisationIdentification8 recursion level 0 with max 1
class OrganisationIdentification8{
    AnyBIC IsoAnyBICIdentifier
}
OrganisationIdentification8 *-- "0..0" GenericOrganisationIdentification1 : Other
%% GenericOrganisationIdentification1 recursion level 1 with max 1
class GenericOrganisationIdentification1{
    Identification IsoMax35Text
    Issuer IsoMax35Text
}
GenericOrganisationIdentification1 *-- "0..1" IOrganisationIdentificationSchemeName1Choice : SchemeName
  

OrganisationIdentification8 members

Member name Description Data Type / Multiplicity
AnyBIC Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 “Banking - Banking telecommunication messages - Business identifier code (BIC)”. IsoAnyBICIdentifier - Optional 0..1
Other Unique identification of an organisation, as assigned by an institution, using an identification scheme. GenericOrganisationIdentification1 - Unknown 0..0

AccountIdentification building block

Unique and unambiguous identification of the account between the account owner and the account servicer. Account to or from which a cash entry is made. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AccountForAction1 recursion level 0 with max 1
class AccountForAction1{
    Currency ActiveCurrencyCode
}
AccountForAction1 *-- "1..1" IAccountIdentification4Choice : Identification
%% IAccountIdentification4Choice recursion level 1 with max 1
  

AccountForAction1 members

Member name Description Data Type / Multiplicity
Identification Unique and unambiguous identification for the account between the account owner and the account servicer. IAccountIdentification4Choice - Required 1..1
Currency Medium of exchange of value. ActiveCurrencyCode - Required 1..1

AccountServicerIdentification building block

Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. . Set of elements used to uniquely and unambiguously identify a financial institution or a branch of a financial institution. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% BranchAndFinancialInstitutionIdentification5 recursion level 0 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% FinancialInstitutionIdentification8 recursion level 1 with max 1
class FinancialInstitutionIdentification8{
    BICFI IsoBICFIIdentifier
    Name IsoMax140Text
}
FinancialInstitutionIdentification8 *-- "0..1" ClearingSystemMemberIdentification2 : ClearingSystemMemberIdentification
FinancialInstitutionIdentification8 *-- "0..1" PostalAddress6 : PostalAddress
FinancialInstitutionIdentification8 *-- "0..1" GenericFinancialIdentification1 : Other
%% BranchData2 recursion level 1 with max 1
class BranchData2{
    Identification IsoMax35Text
    Name IsoMax140Text
}
BranchData2 *-- "0..1" PostalAddress6 : PostalAddress
  

BranchAndFinancialInstitutionIdentification5 members

Member name Description Data Type / Multiplicity
FinancialInstitutionIdentification Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. FinancialInstitutionIdentification8 - Required 1..1
BranchIdentification Identifies a specific branch of a financial institution.

OrganisationIdentification building block

Identification of the organisation requesting the report. Unique and unambiguous way to identify an organisation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OrganisationIdentification8 recursion level 0 with max 1
class OrganisationIdentification8{
    AnyBIC IsoAnyBICIdentifier
}
OrganisationIdentification8 *-- "0..0" GenericOrganisationIdentification1 : Other
%% GenericOrganisationIdentification1 recursion level 1 with max 1
class GenericOrganisationIdentification1{
    Identification IsoMax35Text
    Issuer IsoMax35Text
}
GenericOrganisationIdentification1 *-- "0..1" IOrganisationIdentificationSchemeName1Choice : SchemeName
  

OrganisationIdentification8 members

Member name Description Data Type / Multiplicity
AnyBIC Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 “Banking - Banking telecommunication messages - Business identifier code (BIC)”. IsoAnyBICIdentifier - Optional 0..1
Other Unique identification of an organisation, as assigned by an institution, using an identification scheme. GenericOrganisationIdentification1 - Unknown 0..0

DigitalSignature building block

Contains the signature with its components, namely signed info, signature value, key info and the object. Entity involved in an activity. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyAndSignature2 recursion level 0 with max 1
PartyAndSignature2 *-- "1..1" PartyIdentification43 : Party
PartyAndSignature2 *-- "1..1" ProprietaryData3 : Signature
%% PartyIdentification43 recursion level 1 with max 1
class PartyIdentification43{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification43 *-- "0..1" IParty11Choice : Identification
PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails
%% ProprietaryData3 recursion level 1 with max 1
ProprietaryData3 *-- "1..1" SkipProcessing : Any
  

PartyAndSignature2 members

Member name Description Data Type / Multiplicity
Party Entity involved in an activity. PartyIdentification43 - Required 1..1
Signature Signature of a party. ProprietaryData3 - Required 1..1

SupplementaryData 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
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
  

SupplementaryData1 members

Member name Description Data Type / Multiplicity
PlaceAndName Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. IsoMax350Text - Optional 0..1
Envelope Technical element wrapping the supplementary data. IsoSupplementaryDataEnvelope1 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AccountReportRequestV02 --|> IOuterRecord : Implements
    AccountReportRequestV02Document --|> IOuterDocument~AccountReportRequestV02~ : Implements
    class IOuterDocument~AccountReportRequestV02~ {
        AccountReportRequestV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AccountReportRequestV02Document *-- AccountReportRequestV02 : 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.013.001.02">
    <AcctRptReq>
        <Refs>
            <!-- References inner content -->
        </Refs>
        <Fr>
            <!-- From inner content -->
        </Fr>
        <AcctId>
            <!-- AccountIdentification inner content -->
        </AcctId>
        <AcctSvcrId>
            <!-- AccountServicerIdentification inner content -->
        </AcctSvcrId>
        <OrgId>
            <!-- OrganisationIdentification inner content -->
        </OrgId>
        <DgtlSgntr>
            <!-- DigitalSignature inner content -->
        </DgtlSgntr>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </AcctRptReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_eBAKYQ1TEeKGXqvMN6jpiw"
  nextVersions="_bfzgd22PEei3KuUgpx7Xcw"
  previousVersion="_vMh7-NE9Ed-BzquC8wXy7w_-1349901231"
  name="AccountReportRequestV02"
  definition="The AccountReportRequest message is sent from an organisation to a financial institution for reporting purposes. It is a request for an account report. This message can be sent at any time outside of account opening, maintenance or closing processes."
  registrationStatus="Registered"
  messageSet="_Q3UKwL0wEeKGooZDzppDJQ"
  xmlTag="AcctRptReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_eBAKYw1TEeKGXqvMN6jpiw"
    nextVersions="_bfzgeW2PEei3KuUgpx7Xcw"
    name="References"
    definition="Set of elements for the identification of the message and related references."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Refs"
    complexType="_Qn9899p-Ed-ak6NoX_4Aeg_-250058534" />
  <messageBuildingBlock
    xmi:id="_nJgNsA1YEeKGXqvMN6jpiw"
    nextVersions="_bfzge22PEei3KuUgpx7Xcw"
    name="From"
    definition="Identifies the business sender of the message, if it is not the account owner or account servicing financial institution."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="Fr"
    complexType="_QPiO1Np-Ed-ak6NoX_4Aeg_1971114098" />
  <messageBuildingBlock
    xmi:id="_eBAKZw1TEeKGXqvMN6jpiw"
    nextVersions="_bfzgfW2PEei3KuUgpx7Xcw"
    name="AccountIdentification"
    definition="Unique and unambiguous identification of the account between the account owner and the account servicer."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="AcctId"
    complexType="_SN5Y9Np-Ed-ak6NoX_4Aeg_1820239688" />
  <messageBuildingBlock
    xmi:id="_eBAKaw1TEeKGXqvMN6jpiw"
    nextVersions="_bfzgf22PEei3KuUgpx7Xcw"
    name="AccountServicerIdentification"
    definition="Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. &#xA;."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AcctSvcrId"
    complexType="_TFB1Qdp-Ed-ak6NoX_4Aeg_1367253312" />
  <messageBuildingBlock
    xmi:id="_eBAKbw1TEeKGXqvMN6jpiw"
    nextVersions="_bfzggW2PEei3KuUgpx7Xcw"
    name="OrganisationIdentification"
    definition="Identification of the organisation requesting the report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="OrgId"
    complexType="_QPiO1Np-Ed-ak6NoX_4Aeg_1971114098" />
  <messageBuildingBlock
    xmi:id="_eBAKdw1TEeKGXqvMN6jpiw"
    nextVersions="_bfzgg22PEei3KuUgpx7Xcw"
    name="DigitalSignature"
    definition="Contains the signature with its components, namely signed info, signature value, key info and the object."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="DgtlSgntr"
    complexType="_k4nFNZKuEeGnRMFvqYmPBQ" />
  <messageBuildingBlock
    xmi:id="_ZIPjEA4AEeKGXqvMN6jpiw"
    nextVersions="_bfzghW2PEei3KuUgpx7Xcw"
    name="SupplementaryData"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="acmt"
    messageFunctionality="013"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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