Iso20022

AccountReportingRequestV02

camt.060.001.02

Scope The AccountReportingRequest message is sent by the account owner, either directly or through a forwarding agent, to one of its account servicing institutions. It is used to ask the account servicing institution to send a report on the account owner’s account in a BankToCustomerAccountReport (camt.052.001.02), a BankToCustomerStatement (camt.053.001.02) or a BankToCustomerDebitCreditNotification (camt.054.001.02). Usage The AccountReportingRequest message is used to advise the account servicing institution of funds that the account owner expects to have credited to its account. The message can be used in either a direct or a relay scenario.

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
%% AccountReportingRequestV02 recursion level 0 with max 0
AccountReportingRequestV02 *-- "1..1" GroupHeader43 : GroupHeader
AccountReportingRequestV02 *-- "1..1" ReportingRequest2 : ReportingRequest

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

GroupHeader building block

Set of elements used to provide further details on the message. Set of elements used to provide further details on the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% GroupHeader43 recursion level 0 with max 1
class GroupHeader43{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
GroupHeader43 *-- "0..1" IParty7Choice : MessageSender
%% IParty7Choice recursion level 1 with max 1

GroupHeader43 members

Member name Description Data Type / Multiplicity
MessageIdentification Point to point reference, as assigned by the account owner or the party authorised to send the message, and sent to the account servicing institution, to unambiguously identify the message. Usage: The sender has to make sure that ‘MessageIdentification’ is unique per account servicing institution for a pre-agreed period.
CreationDateTime Date and time at which the message was created. IsoISODateTime - Required 1..1
MessageSender Identification of the party that is sending the message, when different from the account owner. IParty7Choice - Optional 0..1

ReportingRequest building block

Set of elements used to provide further details on the reporting request. Provides further details on the reporting request. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ReportingRequest2 recursion level 0 with max 1
class ReportingRequest2{
    Identification IsoMax35Text
    RequestedMessageNameIdentification IsoMax35Text
}
ReportingRequest2 *-- "0..1" CashAccount16 : Account
ReportingRequest2 *-- "1..1" IParty12Choice : AccountOwner
ReportingRequest2 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : AccountServicer
ReportingRequest2 *-- "0..1" ReportingPeriod1 : ReportingPeriod
ReportingRequest2 *-- "0..1" TransactionType1 : RequestedTransactionType
ReportingRequest2 *-- "0..0" BalanceType12 : RequestedBalanceType
%% CashAccount16 recursion level 1 with max 1
class CashAccount16{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount16 *-- "0..1" CashAccountType2 : Type
%% IParty12Choice recursion level 1 with max 1
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% ReportingPeriod1 recursion level 1 with max 1
class ReportingPeriod1{
    Type QueryType3Code
}
ReportingPeriod1 *-- "1..1" DatePeriodDetails1 : FromToDate
ReportingPeriod1 *-- "1..1" TimePeriodDetails1 : FromToTime
%% TransactionType1 recursion level 1 with max 1
class TransactionType1{
    Status EntryStatus2Code
    CreditDebitIndicator CreditDebitCode
}
TransactionType1 *-- "0..0" Limit2 : FloorLimit
%% BalanceType12 recursion level 1 with max 1
BalanceType12 *-- "1..1" IBalanceType5Choice : CodeOrProprietary
BalanceType12 *-- "0..1" IBalanceSubType1Choice : SubType

ReportingRequest2 members

Member name Description Data Type / Multiplicity
Identification Unique identification, as assigned by the account owner, to unambiguously identify the account reporting request. IsoMax35Text - Optional 0..1
RequestedMessageNameIdentification Specifies the type of the requested reporting message. IsoMax35Text - Required 1..1
Account Unambiguous identification of the account to which the reporting request refers. CashAccount16 - Optional 0..1
AccountOwner Party that legally owns the account. IParty12Choice - Required 1..1
AccountServicer Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account. BranchAndFinancialInstitutionIdentification5 - Optional 0..1
ReportingPeriod Specifies the requested reporting period. ReportingPeriod1 - Optional 0..1
RequestedTransactionType Identifies the transactions to be reported. TransactionType1 - Optional 0..1
RequestedBalanceType Provides details on the requested balance reporting. BalanceType12 - Unknown 0..0

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AccountReportingRequestV02 --|> IOuterRecord : Implements
    AccountReportingRequestV02Document --|> IOuterDocument~AccountReportingRequestV02~ : Implements
    class IOuterDocument~AccountReportingRequestV02~ {
        AccountReportingRequestV02 Message
     }

Document wrapper for serialization

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

classDiagram
    AccountReportingRequestV02Document *-- AccountReportingRequestV02 : 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:camt.060.001.02">
    <AcctRptgReq>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <RptgReq>
            <!-- ReportingRequest inner content -->
        </RptgReq>
    </AcctRptgReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_sd2raGtdEeCY4-KZ9JEyUQ_1430848689"
  nextVersions="_sNdDw1kyEeGeoaLUQk__nA_-791582600"
  name="AccountReportingRequestV02"
  definition="Scope&#xD;&#xA;The AccountReportingRequest message is sent by the account owner, either directly or through a forwarding agent, to one of its account servicing institutions. It is used to ask the account servicing institution to send a report on the account owner's account in a BankToCustomerAccountReport (camt.052.001.02), a BankToCustomerStatement (camt.053.001.02) or a BankToCustomerDebitCreditNotification (camt.054.001.02).&#xD;&#xA;Usage&#xD;&#xA;The AccountReportingRequest message is used to advise the account servicing institution of funds that the account owner expects to have credited to its account. The message can be used in either a direct or a relay scenario."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AcctRptgReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_sd2raWtdEeCY4-KZ9JEyUQ_1191907994"
    name="GroupHeader"
    definition="Set of elements used to provide further details on the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="GrpHdr"
    complexType="_P9WSoNp-Ed-ak6NoX_4Aeg_1664465107" />
  <messageBuildingBlock
    xmi:id="_seAcYGtdEeCY4-KZ9JEyUQ_308674707"
    name="ReportingRequest"
    definition="Set of elements used to provide further details on the reporting request."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="RptgReq"
    complexType="_xSL-8BvlEd-sd4QFmfAhcQ" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="060"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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