camt.060.001.04
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.03), a BankToCustomerStatement (camt.053.001.03) or a BankToCustomerDebitCreditNotification (camt.054.001.03). 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
%% AccountReportingRequestV04 recursion level 0 with max 0
AccountReportingRequestV04 *-- "1..1" GroupHeader76 : GroupHeader
AccountReportingRequestV04 *-- "1..1" ReportingRequest4 : ReportingRequest
AccountReportingRequestV04 *-- "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
%% GroupHeader76 recursion level 0 with max 1
class GroupHeader76{
MessageIdentification IsoMax35Text
CreationDateTime IsoISODateTime
}
GroupHeader76 *-- "0..1" IParty35Choice : MessageSender
%% IParty35Choice recursion level 1 with max 1
GroupHeader76 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. | IParty35Choice - 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
%% ReportingRequest4 recursion level 0 with max 1
class ReportingRequest4{
Identification IsoMax35Text
RequestedMessageNameIdentification IsoMax35Text
}
ReportingRequest4 *-- "0..1" CashAccount24 : Account
ReportingRequest4 *-- "1..1" IParty35Choice : AccountOwner
ReportingRequest4 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : AccountServicer
ReportingRequest4 *-- "0..1" ReportingPeriod2 : ReportingPeriod
ReportingRequest4 *-- "0..1" ISequenceRange1Choice : ReportingSequence
ReportingRequest4 *-- "0..1" TransactionType2 : RequestedTransactionType
ReportingRequest4 *-- "0..0" BalanceType13 : RequestedBalanceType
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
Currency ActiveOrHistoricCurrencyCode
Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% IParty35Choice recursion level 1 with max 1
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% ReportingPeriod2 recursion level 1 with max 1
class ReportingPeriod2{
Type QueryType3Code
}
ReportingPeriod2 *-- "1..1" DatePeriodDetails1 : FromToDate
ReportingPeriod2 *-- "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
ReportingRequest4 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. | CashAccount24 - Optional 0..1 |
| AccountOwner | Party that legally owns the account. | IParty35Choice - 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. | ReportingPeriod2 - 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 AccountReportingRequestV04 implementation follows a specific implementaiton pattern. First of all, AccountReportingRequestV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AccountReportingRequestV04Document implements IOuterDocument. Because AccountReportingRequestV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AccountReportingRequestV04.
classDiagram
class IOuterRecord
AccountReportingRequestV04 --|> IOuterRecord : Implements
AccountReportingRequestV04Document --|> IOuterDocument~AccountReportingRequestV04~ : Implements
class IOuterDocument~AccountReportingRequestV04~ {
AccountReportingRequestV04 Message
}
Document wrapper for serialization
The only real purpose AccountReportingRequestV04Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:camt.060.001.04’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AccountReportingRequestV04.ToDocument() method. The returned AccountReportingRequestV04Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AccountReportingRequestV04Document *-- AccountReportingRequestV04 : 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.04">
<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="_XlRbQV1rEeehlLdFiIrRgQ"
nextVersions="_eYI_k22PEei3KuUgpx7Xcw"
previousVersion="_sNdDw1kyEeGeoaLUQk__nA_-791582600"
name="AccountReportingRequestV04"
definition="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.03), a BankToCustomerStatement (camt.053.001.03) or a BankToCustomerDebitCreditNotification (camt.054.001.03).
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."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="AcctRptgReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_XlRbQ11rEeehlLdFiIrRgQ"
nextVersions="_eYI_lW2PEei3KuUgpx7Xcw"
previousVersion="_sNm0wFkyEeGeoaLUQk__nA_526020878"
name="GroupHeader"
definition="Set of elements used to provide further details on the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="GrpHdr"
complexType="_o3nFSbTgEeef0oKPLRNatg" />
<messageBuildingBlock
xmi:id="_XlRbRV1rEeehlLdFiIrRgQ"
nextVersions="_eYI_l22PEei3KuUgpx7Xcw"
previousVersion="_sNm0wVkyEeGeoaLUQk__nA_-471051475"
name="ReportingRequest"
definition="Set of elements used to provide further details on the reporting request."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="RptgReq"
complexType="_5CqQIYaAEee8r9VKRbnJSg" />
<messageBuildingBlock
xmi:id="_XlRbR11rEeehlLdFiIrRgQ"
nextVersions="_eYI_mW2PEei3KuUgpx7Xcw"
previousVersion="_sNwlwFkyEeGeoaLUQk__nA_1992302117"
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="04" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.