8.1 Generation of MX Type Messages
This topic describes the generation of MX type messages supported in OBCL for cash management which is camt.054 BankToCustomerDebitCreditNotification
Table 8-1 Cash Management and customer status.
The BankToCustomerDebitCreditNotification message is sent by the account
servicer to an account owner or to a party authorized by the account owner to receive
the message. It can be used to inform the account owner, or authorized party, of single
or multiple debit and/or credit entries reported to the account
Table 8-1 BankToCustomerDebitCreditNotification
| MT Number | MT Name | MX ID | MX Name |
|---|---|---|---|
| MT 900 | Confirmation of Debit camt.054 | camt.054 | BankToCustomerDebit CreditNotification |
| MT 910 | Confirmation of Credit | camt.054 | BankToCustomerDebit CreditNotification |
This new ISO 20022 message replaces both the FIN MT900 confirmation of debit and the MT910 confirmation of credit messages. It is worth noting that the use of the camt.054 message is optional – meaning that, even though it is part of the CBPR+ message portfolio, banks are not obliged to send it and it is bilaterally agreed
The camt.054 BankToCustomerDebitCreditNotification is composed of:
- Group Header: This building block is mandatory and present once. It contains elements such as MessageIdentification and CreationDateTime
- Notification: This building block is mandatory and repetitive. It should be repeated for each account on which a notification is provided. The Notification contains information on the booked debit and credit entries.
- Entry: Entry is part of the Notification and can be repetitive. It contains information related to the entry in the account, such as Amount, Booking or ValueDate and BankTransactionCode. EntryDetails
- Entry detail: This is part of the Entry and there can only be one EntryDetails in each Entry. This part contains detailed information related to the entry, such as References, Amount Details, Related Parties and RemittanceInformation.