camt.054.001.07
Scope The BankToCustomerDebitCreditNotification message is sent by the account servicer to an account owner or to a party authorised by the account owner to receive the message. It can be used to inform the account owner, or authorised party, of single or multiple debit and/or credit entries reported to the account. Usage The BankToCustomerDebitCreditNotification message can contain reports for more than one account. It provides information for cash management and/or reconciliation. The BankToCustomerDebitCreditNotification message can be used to:
- report pending and booked items;
- notify one or more debit entries;
- notify one or more credit entries;
- notify a combination of debit and credit entries. It can include underlying details of transactions that have been included in the entry. It is possible that the receiver of the message is not the account owner, but a party entitled by the account owner to receive the account information (also known as recipient). It does not contain balance information.
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
%% BankToCustomerDebitCreditNotificationV07 recursion level 0 with max 0
BankToCustomerDebitCreditNotificationV07 *-- "1..1" GroupHeader73 : GroupHeader
BankToCustomerDebitCreditNotificationV07 *-- "1..1" AccountNotification15 : Notification
BankToCustomerDebitCreditNotificationV07 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
GroupHeader building block
Common information for the message. Provides further details on the message. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% GroupHeader73 recursion level 0 with max 1
class GroupHeader73{
MessageIdentification IsoMax35Text
CreationDateTime IsoISODateTime
AdditionalInformation IsoMax500Text
}
GroupHeader73 *-- "0..1" PartyIdentification125 : MessageRecipient
GroupHeader73 *-- "0..1" Pagination1 : MessagePagination
GroupHeader73 *-- "0..1" OriginalBusinessQuery1 : OriginalBusinessQuery
%% PartyIdentification125 recursion level 1 with max 1
class PartyIdentification125{
Name IsoMax140Text
CountryOfResidence CountryCode
}
PartyIdentification125 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification125 *-- "0..1" IParty34Choice : Identification
PartyIdentification125 *-- "0..1" ContactDetails2 : ContactDetails
%% Pagination1 recursion level 1 with max 1
class Pagination1{
PageNumber IsoMax5NumericText
LastPageIndicator IsoYesNoIndicator
}
%% OriginalBusinessQuery1 recursion level 1 with max 1
class OriginalBusinessQuery1{
MessageIdentification IsoMax35Text
MessageNameIdentification IsoMax35Text
CreationDateTime IsoISODateTime
}
GroupHeader73 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageIdentification | Point to point reference, as assigned by the account servicing institution, and sent to the account owner or the party authorised to receive the message, to unambiguously identify the message. | Usage: The account servicing institution has to make sure that MessageIdentification is unique per account owner for a pre-agreed period. |
| CreationDateTime | Date and time at which the message was created. | IsoISODateTime - Required 1..1 |
| MessageRecipient | Party authorised by the account owner to receive information about movements on the account. | Usage: MessageRecipient should only be identified when different from the account owner. |
| MessagePagination | Provides details on the page number of the message. | |
| OriginalBusinessQuery | Unique identification, as assigned by the original requestor, to unambiguously identify the business query message. | OriginalBusinessQuery1 - Optional 0..1 |
| AdditionalInformation | Further details of the message. | IsoMax500Text - Optional 0..1 |
Notification building block
Notifies debit and credit entries for the account. Provides further details of the account notification. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AccountNotification15 recursion level 0 with max 1
class AccountNotification15{
Identification IsoMax35Text
ElectronicSequenceNumber IsoNumber
LegalSequenceNumber IsoNumber
CreationDateTime IsoISODateTime
CopyDuplicateIndicator CopyDuplicate1Code
AdditionalNotificationInformation IsoMax500Text
}
AccountNotification15 *-- "0..1" Pagination1 : NotificationPagination
AccountNotification15 *-- "0..1" ISequenceRange1Choice : ReportingSequence
AccountNotification15 *-- "0..1" DateTimePeriod1 : FromToDate
AccountNotification15 *-- "0..1" IReportingSource1Choice : ReportingSource
AccountNotification15 *-- "1..1" CashAccount36 : Account
AccountNotification15 *-- "0..1" CashAccount24 : RelatedAccount
AccountNotification15 *-- "0..0" AccountInterest4 : Interest
AccountNotification15 *-- "0..1" TotalTransactions6 : TransactionsSummary
AccountNotification15 *-- "0..0" ReportEntry9 : Entry
%% Pagination1 recursion level 1 with max 1
class Pagination1{
PageNumber IsoMax5NumericText
LastPageIndicator IsoYesNoIndicator
}
%% ISequenceRange1Choice recursion level 1 with max 1
%% DateTimePeriod1 recursion level 1 with max 1
class DateTimePeriod1{
FromDateTime IsoISODateTime
ToDateTime IsoISODateTime
}
%% IReportingSource1Choice recursion level 1 with max 1
%% CashAccount36 recursion level 1 with max 1
class CashAccount36{
Currency ActiveOrHistoricCurrencyCode
Name IsoMax70Text
}
CashAccount36 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount36 *-- "0..1" ICashAccountType2Choice : Type
CashAccount36 *-- "0..1" PartyIdentification125 : Owner
CashAccount36 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : Servicer
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
Currency ActiveOrHistoricCurrencyCode
Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% AccountInterest4 recursion level 1 with max 1
class AccountInterest4{
Reason IsoMax35Text
}
AccountInterest4 *-- "0..1" IInterestType1Choice : Type
AccountInterest4 *-- "0..0" Rate4 : Rate
AccountInterest4 *-- "0..1" DateTimePeriod1 : FromToDate
AccountInterest4 *-- "0..1" TaxCharges2 : Tax
%% TotalTransactions6 recursion level 1 with max 1
TotalTransactions6 *-- "0..1" NumberAndSumOfTransactions4 : TotalEntries
TotalTransactions6 *-- "0..1" NumberAndSumOfTransactions1 : TotalCreditEntries
TotalTransactions6 *-- "0..1" NumberAndSumOfTransactions1 : TotalDebitEntries
TotalTransactions6 *-- "0..0" TotalsPerBankTransactionCode5 : TotalEntriesPerBankTransactionCode
%% ReportEntry9 recursion level 1 with max 1
class ReportEntry9{
EntryReference IsoMax35Text
Amount IsoActiveOrHistoricCurrencyAndAmount
CreditDebitIndicator CreditDebitCode
ReversalIndicator IsoTrueFalseIndicator
AccountServicerReference IsoMax35Text
CommissionWaiverIndicator IsoYesNoIndicator
AdditionalEntryInformation IsoMax500Text
}
ReportEntry9 *-- "1..1" IEntryStatus1Choice : Status
ReportEntry9 *-- "0..1" IDateAndDateTime2Choice : BookingDate
ReportEntry9 *-- "0..1" IDateAndDateTime2Choice : ValueDate
ReportEntry9 *-- "0..0" CashAvailability1 : Availability
ReportEntry9 *-- "1..1" BankTransactionCodeStructure4 : BankTransactionCode
ReportEntry9 *-- "0..1" MessageIdentification2 : AdditionalInformationIndicator
ReportEntry9 *-- "0..1" AmountAndCurrencyExchange3 : AmountDetails
ReportEntry9 *-- "0..1" Charges4 : Charges
ReportEntry9 *-- "0..1" ITechnicalInputChannel1Choice : TechnicalInputChannel
ReportEntry9 *-- "0..1" TransactionInterest4 : Interest
ReportEntry9 *-- "0..1" CardEntry3 : CardTransaction
ReportEntry9 *-- "0..0" EntryDetails8 : EntryDetails
AccountNotification15 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Unique identification, as assigned by the account servicer, to unambiguously identify the account notification. | IsoMax35Text - Required 1..1 |
| NotificationPagination | Provides details on the page number of the notification. Usage: The pagination of the notification is only allowed when agreed between the parties. | Pagination1 - Optional 0..1 |
| ElectronicSequenceNumber | Sequential number of the notification, as assigned by the account servicer. | Usage: The sequential number is increased incrementally for each notification sent electronically. |
| ReportingSequence | Specifies the range of identification sequence numbers, as provided in the request. | ISequenceRange1Choice - Optional 0..1 |
| LegalSequenceNumber | Legal sequential number of the notification, as assigned by the account servicer. It is increased incrementally for each notification sent. | IsoNumber - Optional 0..1 |
| CreationDateTime | Date and time at which the notification was created. | IsoISODateTime - Optional 0..1 |
| FromToDate | Range of time between a start date and an end date for which the account notification is issued. | DateTimePeriod1 - Optional 0..1 |
| CopyDuplicateIndicator | Indicates whether the document is a copy, a duplicate, or a duplicate of a copy. | CopyDuplicate1Code - Optional 0..1 |
| ReportingSource | Specifies the application used to generate the reporting. | IReportingSource1Choice - Optional 0..1 |
| Account | Unambiguous identification of the account to which credit and debit entries are made. | CashAccount36 - Required 1..1 |
| RelatedAccount | Identifies the parent account of the account for which the notification has been issued. | CashAccount24 - Optional 0..1 |
| Interest | Provides general interest information that applies to the account at a particular moment in time. | AccountInterest4 - Unknown 0..0 |
| TransactionsSummary | Provides summary information on entries. | TotalTransactions6 - Optional 0..1 |
| Entry | Specifies an entry in the debit credit notification. Usage: At least one reference must be provided to identify the entry and its underlying transaction(s). Usage Rule: In case of a Payments R-transaction the creditor / debtor referenced of the original payment initiation messages is also used for reporting of the R-transaction. The original debtor/creditor in the reporting of R-Transactions is not inverted. Following elements all defined in the TransactionDetails in RelatedParties or RelatedAgents are impacted by this usage rule: Creditor, UltimateCreditor, CreditorAccount, CreditorAgent, Debtor, UltimateDebtor, DebtorAccount and DebtorAgent. | ReportEntry9 - Unknown 0..0 |
| AdditionalNotificationInformation | Further details of the account notification. | IsoMax500Text - Optional 0..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 BankToCustomerDebitCreditNotificationV07 implementation follows a specific implementaiton pattern. First of all, BankToCustomerDebitCreditNotificationV07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, BankToCustomerDebitCreditNotificationV07Document implements IOuterDocument. Because BankToCustomerDebitCreditNotificationV07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type BankToCustomerDebitCreditNotificationV07.
classDiagram
class IOuterRecord
BankToCustomerDebitCreditNotificationV07 --|> IOuterRecord : Implements
BankToCustomerDebitCreditNotificationV07Document --|> IOuterDocument~BankToCustomerDebitCreditNotificationV07~ : Implements
class IOuterDocument~BankToCustomerDebitCreditNotificationV07~ {
BankToCustomerDebitCreditNotificationV07 Message
}
Document wrapper for serialization
The only real purpose BankToCustomerDebitCreditNotificationV07Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:camt.054.001.07’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using BankToCustomerDebitCreditNotificationV07.ToDocument() method. The returned BankToCustomerDebitCreditNotificationV07Document value will serialize correctly according to ISO 20022 standards.
classDiagram
BankToCustomerDebitCreditNotificationV07Document *-- BankToCustomerDebitCreditNotificationV07 : 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.054.001.07">
<BkToCstmrDbtCdtNtfctn>
<GrpHdr>
<!-- GroupHeader inner content -->
</GrpHdr>
<Ntfctn>
<!-- Notification inner content -->
</Ntfctn>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</BkToCstmrDbtCdtNtfctn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_XlRbVV1rEeehlLdFiIrRgQ"
nextVersions="_eYI_YW2PEei3KuUgpx7Xcw"
previousVersion="_7u9RUTquEeWZFYSPlduMhw"
name="BankToCustomerDebitCreditNotificationV07"
definition="Scope
The BankToCustomerDebitCreditNotification message is sent by the account servicer to an account owner or to a party authorised by the account owner to receive the message. It can be used to inform the account owner, or authorised party, of single or multiple debit and/or credit entries reported to the account.
Usage
The BankToCustomerDebitCreditNotification message can contain reports for more than one account. It provides information for cash management and/or reconciliation.
The BankToCustomerDebitCreditNotification message can be used to: 
- report pending and booked items;
- notify one or more debit entries;
- notify one or more credit entries;
- notify a combination of debit and credit entries.
It can include underlying details of transactions that have been included in the entry.
It is possible that the receiver of the message is not the account owner, but a party entitled by the account owner to receive the account information (also known as recipient).
It does not contain balance information."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="BkToCstmrDbtCdtNtfctn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_XlRbV11rEeehlLdFiIrRgQ"
nextVersions="_eYI_Y22PEei3KuUgpx7Xcw"
previousVersion="_7u9RUzquEeWZFYSPlduMhw"
name="MessageOrNotificationPaginationRule"
definition="MessagePagination may be present or NotificationPagination may be present, but not both."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition><SimpleRule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="SimpleRule"><mustBe><connector>OR</connector><BooleanRule xsi:type="Absence"><leftOperand>/GroupHeader/MessagePagination</leftOperand></BooleanRule><BooleanRule xsi:type="Absence"><leftOperand>/Notification[*]/NotificationPagination</leftOperand></BooleanRule></mustBe></SimpleRule></RuleDefinition>" />
<constraint
xmi:id="_XlRbWV1rEeehlLdFiIrRgQ"
nextVersions="_eYI_ZW2PEei3KuUgpx7Xcw"
previousVersion="_7u9RVTquEeWZFYSPlduMhw"
name="SupplementaryDataRule"
definition="The SupplementaryData building block at message level must not be used to provide additional information about a transaction. The SupplementaryData element at transaction level should be used for that purpose."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_XlRbW11rEeehlLdFiIrRgQ"
nextVersions="_eYI_Z22PEei3KuUgpx7Xcw"
previousVersion="_7u9RVzquEeWZFYSPlduMhw"
name="GroupHeader"
definition="Common information for the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="GrpHdr"
complexType="_m3Y3sbTREeeyuKckOGlwuA" />
<messageBuildingBlock
xmi:id="_XlRbXV1rEeehlLdFiIrRgQ"
nextVersions="_eYI_aW2PEei3KuUgpx7Xcw"
previousVersion="_7u9RWTquEeWZFYSPlduMhw"
name="Notification"
definition="Notifies debit and credit entries for the account."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="Ntfctn"
complexType="_tppSIa6QEeexrtTFgmVD3Q" />
<messageBuildingBlock
xmi:id="_XlRbX11rEeehlLdFiIrRgQ"
nextVersions="_eYI_a22PEei3KuUgpx7Xcw"
previousVersion="_7u9RWzquEeWZFYSPlduMhw"
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="054"
flavour="001"
version="07" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.