Iso20022

AccountReportingRequestV06

camt.060.001.06

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), a BankToCustomerStatement (camt.053) or a BankToCustomerDebitCreditNotification (camt.054).

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
%% AccountReportingRequestV06 recursion level 0 with max 0
AccountReportingRequestV06 *-- "1..1" GroupHeader77 : GroupHeader
AccountReportingRequestV06 *-- "1..1" ReportingRequest6 : ReportingRequest
AccountReportingRequestV06 *-- "0..1" SupplementaryData1 : SupplementaryData

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. Provides further details on the message. For comparison, see the ISO20022 official specification

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

GroupHeader77 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. IParty40Choice - 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
%% ReportingRequest6 recursion level 0 with max 1
class ReportingRequest6{
    Identification IsoMax35Text
    RequestedMessageNameIdentification IsoMax35Text
}
ReportingRequest6 *-- "0..1" CashAccount40 : Account
ReportingRequest6 *-- "1..1" IParty40Choice : AccountOwner
ReportingRequest6 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : AccountServicer
ReportingRequest6 *-- "0..1" ReportingPeriod5 : ReportingPeriod
ReportingRequest6 *-- "0..1" ISequenceRange1Choice : ReportingSequence
ReportingRequest6 *-- "0..1" TransactionType2 : RequestedTransactionType
ReportingRequest6 *-- "0..0" BalanceType13 : RequestedBalanceType
%% CashAccount40 recursion level 1 with max 1
class CashAccount40{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount40 *-- "0..1" IAccountIdentification4Choice : Identification
CashAccount40 *-- "0..1" ICashAccountType2Choice : Type
CashAccount40 *-- "0..1" ProxyAccountIdentification1 : Proxy
%% IParty40Choice recursion level 1 with max 1
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
%% ReportingPeriod5 recursion level 1 with max 1
class ReportingPeriod5{
    Type QueryType3Code
}
ReportingPeriod5 *-- "1..1" DatePeriod3 : FromToDate
ReportingPeriod5 *-- "0..1" TimePeriodDetails1 : FromToTime
%% ISequenceRange1Choice recursion level 1 with max 1
%% TransactionType2 recursion level 1 with max 1
class TransactionType2{
    CreditDebitIndicator CreditDebitCode
}
TransactionType2 *-- "1..1" IEntryStatus1Choice : Status
TransactionType2 *-- "0..0" Limit2 : FloorLimit
%% BalanceType13 recursion level 1 with max 1
BalanceType13 *-- "1..1" IBalanceType10Choice : CodeOrProprietary
BalanceType13 *-- "0..1" IBalanceSubType1Choice : SubType

ReportingRequest6 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. CashAccount40 - Optional 0..1
AccountOwner Party that legally owns the account. IParty40Choice - 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. BranchAndFinancialInstitutionIdentification6 - Optional 0..1
ReportingPeriod Specifies the requested reporting period. ReportingPeriod5 - Optional 0..1
ReportingSequence Specifies the range of identification sequence numbers which are being requested. ISequenceRange1Choice - Optional 0..1
RequestedTransactionType Identifies the transactions to be reported. TransactionType2 - Optional 0..1
RequestedBalanceType Provides details on the requested balance reporting. BalanceType13 - Unknown 0..0

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 AccountReportingRequestV06 implementation follows a specific implementaiton pattern. First of all, AccountReportingRequestV06 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AccountReportingRequestV06Document implements IOuterDocument. Because AccountReportingRequestV06 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AccountReportingRequestV06.

classDiagram
    class IOuterRecord
    AccountReportingRequestV06 --|> IOuterRecord : Implements
    AccountReportingRequestV06Document --|> IOuterDocument~AccountReportingRequestV06~ : Implements
    class IOuterDocument~AccountReportingRequestV06~ {
        AccountReportingRequestV06 Message
     }

Document wrapper for serialization

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

classDiagram
    AccountReportingRequestV06Document *-- AccountReportingRequestV06 : 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.06">
    <AcctRptgReq>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <RptgReq>
            <!-- ReportingRequest inner content -->
        </RptgReq>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </AcctRptgReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_7wrvkdb-Eeq_l4BJLVUF2Q"
  previousVersion="_eYI_k22PEei3KuUgpx7Xcw"
  name="AccountReportingRequestV06"
  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), a BankToCustomerStatement (camt.053) or a BankToCustomerDebitCreditNotification (camt.054)."
  registrationStatus="Registered"
  messageSet="_wRx2xE2rEeG_I4xRYCA_7g"
  xmlTag="AcctRptgReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_7wrvl9b-Eeq_l4BJLVUF2Q"
    previousVersion="_eYI_lW2PEei3KuUgpx7Xcw"
    name="GroupHeader"
    definition="Set of elements used to provide further details on the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="GrpHdr"
    complexType="_CFttTW49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_7wrvmdb-Eeq_l4BJLVUF2Q"
    previousVersion="_eYI_l22PEei3KuUgpx7Xcw"
    name="ReportingRequest"
    definition="Set of elements used to provide further details on the reporting request."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="RptgReq"
    complexType="_eoT28dcZEeqRFcf2R4bPBw" />
  <messageBuildingBlock
    xmi:id="_7wrvm9b-Eeq_l4BJLVUF2Q"
    previousVersion="_eYI_mW2PEei3KuUgpx7Xcw"
    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="camt"
    messageFunctionality="060"
    flavour="001"
    version="06" />
</messageDefinition>

ISO Building Blocks

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