B2C Cash Management
B2C Cash Management
B2C Cash Management
_______
Overview
Scope
This document describes a set of account information messages approved by the ISO 20022 Payments Standards
Evaluation Group as UNIFI messages in March 2007. These messages can be used to provide account information for
reconciliation and cash positioning.
How to read
In compliance with ISO 20022, UML (Unified Modelling Language) is used to depict business and logical models. As
knowledge of UML is not a requirement to discuss the business standards, the data format for the messages is presented
in a user-friendlier way. This way of representation is automatically generated from the models, thereby ensuring absolute
consistency between the model information and the published standard.
Page 1
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Flows
Message Flows
Reporting from Account Servicer to Account Owner
Introduction
The Bank-to-Customer Cash Management messages are sent from the Account Servicer to the Account Owner, or a party
authorised by the Account Owner to receive the account information (i.e. the Message Recipient).
Sequence Diagrams
The scenarios illustrate the reporting from Account Servicer to Account Owner
Scenario 1
The following service has been agreed between Account Owner and Account Servicer : During the day, the Account
Servicer sends one or more BankToCustomerAccountReport messages to inform the AccountOwner of any intraday
movements (booked and pending) on the account. At the end of the business day, the Account Servicer summarizes all
booked entries in the BankToCustomerStatement and provides booked and available balance information.
AccountServicer AccountOwner
BankToCustomerAccountReport
Scenario 2
The following service has been agreed between Account Owner and Account Servicer : During the day, the Account
Servicer will send a BankToCustomerDebitCreditNotification for any incoming credits above a certain threshold. At a
pre-agreed time during the day, the Account Servicer will also provide an intraday BankToCustomerAccountReport,
summarizing all movements (booked and pending) which have been posted to the account since the start of the business
day. The Account Servicer will also include balance information (booked and expected) in the message. At the end of the
Page 2
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Flows
business day, the Account Servicer summarizes all booked entries in the BankToCustomerStatement and provides booked
and available balance information.
AccountServicer AccountOwner
BankToCustomerDebitCreditNotification
BankToCustomerAccountReport
BankToCustomerStatement
Scenario 3
This scenario shows that the Bank to Customer Cash Management messages can also be delivered to a party authorised
by the Account Owner to receive the account information (ie the Message Recipient).
Page 3
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Flows
BankToCustomerDebitCreditNotification
BankToCustomerDebitCreditNotifi
cation or similar internal message
BankToCustomerStatement
BankToCustomerStatement or
similar internal message
Introduction
The Bank-to-Customer Cash Management messages are sent from the Account Servicer through a Forwarding Agent
(who plays the role of ‘concentrating institution’ for the account owner) to the the Account Owner, or a party authorised
by the Account Owner to receive the account information (i.e. the Message Recipient). Which messages will be sent will
be agreed between the 3 parties.
Sequence Diagrams
The scenarios illustrate the reporting through a Forwarding Agent
Page 4
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Flows
Scenario
BankToCustomerStatement or
BankToCustomerAccountReport
BankToCustomerStatement or
BankToCust omerAccountReport
Page 5
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
MX camt.052.001.01 BankToCustomerAccountReportV01
Message Scope and Usage
Scope
The Bank-to-Customer Account Report 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 the
entries reported to the account, and/or to provide the owner with balance information on the account at a given point in
time.
Usage
The Bank-to-Customer Account Report message can contain reports for more than 1 account. It provides information
for cash management and/or reconciliation. It can be used to :
- report pending and booked items;
- provide balance information
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).
For a statement that is required due to local legal stipulations, the Bank-to-Customer Account Statement message should
be used.
Outline
The Bank-to-Customer Account Report message is composed of 2 building blocks:
A. Group Header
This building block is mandatory and present once. It contains elements such as Message Identification and
CreationDateTime.
B. Report
This building block is mandatory and repetitive. It should be repeated for each account on which a report is provided. The
report contains components such as Balance and Entry information.
Message Structure
Index Or Message Item <XML Tag> Mult. Represent./ Rule/
Type Guid.
No.
Message root <BkToCstmrAcctRpt [1..1]
V01>
Page 6
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 7
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 8
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 9
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 10
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 11
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 12
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 13
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 14
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 15
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 16
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: The account servicing institution has to make sure that 'MessageIdentification' is unique per instructed
party for a pre-agreed period.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Guideline : MessageRecipient should only be identified when different from the account owner.
Type: This message item is composed of the following PartyIdentification8 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
Name <Nm> [0..1] Text
PostalAddress <PstlAdr> [0..1]
Identification <Id> [0..1]
CountryOfResidence <CtryOfRes> [0..1] Code
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 17
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: the pagination of the message is only allowed when agreed between the parties.
Type: This message item is composed of the following Pagination element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
1.5 PageNumber <PgNb> [1..1] Text
1.6 LastPageIndicator <LastPgInd> [1..1] Indicator
Page 18
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage : in those scenarios where eg a paper statement is a legal requirement, the paper statement may have
a different numbering than the electronic sequential number. Paper statements can for instance only be sent
if movement on the account has taken place, whereas electronic statements can be sent eg each day, regardless
of whether movements have taken place or not.
Data Type: Number
Format: fractionDigits: 0
totalDigits: 18
Page 19
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Definition: Range of time between the start date and the end date for which the account report is issued.
Type: This message item is composed of the following DateTimePeriodDetails element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FromDateTime <FrDtTm> [1..1] DateTime
ToDateTime <ToDtTm> [1..1] DateTime
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Page 20
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to AccountIdentification3Choice p.333 in 'Message Item Types' section.
Page 21
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage : the account name is different from the account owner name. The account name is used in certain
user communities to provide a means of identifying the account, in addition to the account owner's identity
and the account number.
Data Type: Max70Text
Format: maxLength: 70
minLength: 1
Page 22
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
Page 23
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 24
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 25
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyAndAmountRange p.339 in 'Message Item Types' section.
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Rule(s): AvailabilityAndTypeRule
If Type is equal to ForwardAvailable, Availability is not allowed.
Page 26
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 27
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 28
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 29
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage : if not present, credit line is not included in the balance amount.
Data Type: One of the following TrueFalseIndicator values must be used:
MeaningWhenTrue: True
MeaningWhenFalse: False
Page 30
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
ValidationByTable
For additional Type information, please refer to DateAndDateTimeChoice p.345 in 'Message Item Types' section.
Usage : this type of info is eg used in US, and is linked to particular instruments, such as cheques.
Example : When a cheque is deposited, it will be booked on the deposit day, but the funds will only be
accessible as of the indicated availability day (according to national banking regulations).
Page 31
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 32
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Guideline(s): DebitCreditIndicatorGuideline
DebitCreditIndicator should be present when TotalNetEntryAmount is present.
Page 33
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 34
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Guideline(s): DebitCreditIndicatorGuideline
DebitCreditIndicator should be present when TotalNetEntryAmount is present.
Page 35
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
Page 36
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.63 Code <Cd> [1..1] Code
2.64 Family <Fmly> [1..1]
Page 37
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 38
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Type: This message item is composed of one of the following CashBalanceAvailabilityDate1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.72 {Or NumberOfDays <NbOfDays> [1..1] Text
2.73 Or} ActualDate <ActlDt> [1..1] DateTime
Page 39
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: At least one reference must be provided to identify the entry and its underlying transaction(s).
Type: This message item is composed of the following ReportEntry1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.77 Amount <Amt> [1..1] Amount
2.78 CreditDebitIndicator <CdtDbtInd> [1..1] Code
2.79 ReversalIndicator <RvslInd> [0..1] Indicator
2.80 Status <Sts> [1..1] Code
2.81 BookingDate <BookgDt> [0..1] +
2.82 ValueDate <ValDt> [0..1] +
2.83 AccountServicerReference <AcctSvcrRef> [0..1] Text
2.84 Availability <Avlbty> [0..n]
2.90 BankTransactionCode <BkTxCd> [1..1]
2.99 CommissionWaiverIndicator <ComssnWvrInd> [0..1] Indicator
2.100 AdditionalInformationIndicator <AddtlInfInd> [0..1]
2.103 Batch <Btch> [0..n]
2.107 AmountDetails <AmtDtls> [0..1]
2.124 Charges <Chrgs> [0..n]
2.137 Interest <Intrst> [0..n]
2.150 TransactionDetails <TxDtls> [0..n]
2.329 AdditionalEntryInformation <AddtlNtryInf> [0..1] Text
Rule(s): StatusAndBookingDateRule
If Status is pending, BookingDate is not allowed.
Guideline(s): ReferenceGuideline
At least one reference should present to identify the underlying transaction(s).
Page 40
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Rule(s): CurrencyCode
ValidationByTable
Usage : this element should only be present if the entry is the result of a reversal operation.
If the CreditDebitIndicator is CRDT and ReversalIndicator is Yes, the original operation was a debit entry.
If the CreditDebitIndicator is DBIT and ReversalIndicator is Yes, the original operation was a credit entry.
Data Type: One of the following TrueFalseIndicator values must be used:
MeaningWhenTrue: True
MeaningWhenFalse: False
Usage :
Status Booked does not necessarily imply finality of money
as this depends on other factors such as the payment system
used, the completion of the end-to-end transaction and the
terms agreed between account servicer and owner.
Status Booked is the only status that can be reversed.
INFO Information Entry is only provided for information, and no booking on
the account owner's account in the account servicer's ledger
has been performed.
PDNG Pending Booking on the account owner's account in the account
servicer's ledger has not been completed.
Page 41
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to DateAndDateTimeChoice p.345 in 'Message Item Types' section.
Usage : When entry status is pending , and value date is present, value date refers to an expected/requested
value date.
For entries which are subject to availability/float (and for which availability information is present), value
date must not be used, as the availability component identifies the number of availability days.
Type: This message item is composed of one of the following DateAndDateTimeChoice element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
{Or Date <Dt> [1..1] DateTime
Or} DateTime <DtTm> [1..1] DateTime
For additional Type information, please refer to DateAndDateTimeChoice p.345 in 'Message Item Types' section.
Page 42
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage : this type of info is eg used in US, and is linked to particular instruments, such as cheques.
Example : When a cheque is deposited, it will be booked on the deposit day, but the funds will only be
accessible as of the indicated availability day (according to national banking regulations).
Type: This message item is composed of the following CashBalanceAvailability1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.85 Date <Dt> [1..1]
2.88 Amount <Amt> [1..1] Amount
2.89 CreditDebitIndicator <CdtDbtInd> [1..1] Code
Page 43
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Format: CurrencyAndAmount
fractionDigits: 5
minInclusive: 0
totalDigits: 18
CurrencyCode
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Page 44
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 45
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 46
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage : this element can be repeated in case more than one batch is included in the entry, eg, in lockbox
scenarios, to specify the ID and number of transactions included in each of the batches.
Type: This message item is composed of the following BatchInformation1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.104 MessageIdentification <MsgId> [0..1] Text
2.105 PaymentInformationIdentification <PmtInfId> [0..1] Text
2.106 NumberOfTransactions <NbOfTxs> [0..1] Text
Page 47
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage : This component (on entry level) should be used when a total original batch or aggregate amount has
to be provided. (If required, the individual original amounts can be included in the same component on
transaction details level).
Type: This message item is composed of the following AmountAndCurrencyExchange2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.108 InstructedAmount <InstdAmt> [0..1]
2.111 TransactionAmount <TxAmt> [0..1]
2.114 CounterValueAmount <CntrValAmt> [0..1]
2.117 AnnouncedPostingAmount <AnncdPstngAmt> [0..1]
2.120 ProprietaryAmount <PrtryAmt> [0..n]
Page 48
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 49
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 50
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Amount of money, based on terms of corporate action event and balance of underlying securities, entitled
to/from the account owner.
In those situations, this amount may alternatively be called entitled amount.
Type: This message item is composed of the following AmountAndCurrencyExchangeDetails1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.118 Amount <Amt> [1..1] Amount
2.119 CurrencyExchange <CcyXchg> [0..1] +
Page 51
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 52
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Usage : this component is used on entry level in case of batch or aggregate bookings.
Type: This message item is composed of the following ChargesInformation3 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.125 TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt> [0..1] Amount
2.126 Amount <Amt> [1..1] Amount
2.127 Type <Tp> [0..1]
2.130 Rate <Rate> [0..1] Rate
2.131 Bearer <Br> [0..1] Code
2.132 Party <Pty> [0..1] +
2.133 Tax <Tax> [0..1]
Page 53
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Page 54
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Format: [a-zA-Z0-9]{1,4}
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 55
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage : This component is used on entry level in case of batch or aggregate bookings.
Type: This message item is composed of the following TransactionInterest1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.138 Amount <Amt> [1..1] Amount
2.139 CreditDebitIndicator <CdtDbtInd> [1..1] Code
Page 56
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 57
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 58
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyAndAmountRange p.339 in 'Message Item Types' section.
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Page 59
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Definition: Underlying reason for the interest, eg, yearly credit interest on a savings account.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Page 60
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: the instruction identification is a point to point reference that can be used between the instructing
party and the instructed party to refer to the individual instruction. It can be included in several messages
related to the instruction.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction.
It can be included in several messages related to the transaction.
Page 61
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: In case there are technical limitations to carry on multiple references, the end-to-end identification
must be carried on throughout the entire end-to-end chain.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the
transaction on the interbank level.
Usage: The instructing agent has to make sure the transaction identification is unique for a pre-agreed period.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Page 62
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: This component (on transaction level) should be used in case booking is for a single transaction and
the original amount is different from the entry amount. It can also be used in case individual original amounts
are provided in case of a batch or aggregate booking.
Type: This message item is composed of the following AmountAndCurrencyExchange2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.164 InstructedAmount <InstdAmt> [0..1]
2.167 TransactionAmount <TxAmt> [0..1]
2.170 CounterValueAmount <CntrValAmt> [0..1]
2.173 AnnouncedPostingAmount <AnncdPstngAmt> [0..1]
2.176 ProprietaryAmount <PrtryAmt> [0..n]
Page 63
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 64
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 65
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Amount of money, based on terms of corporate action event and balance of underlying securities, entitled
to/from the account owner.
In those situations, this amount may alternatively be called entitled amount.
Type: This message item is composed of the following AmountAndCurrencyExchangeDetails1 element(s):
Page 66
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 67
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 68
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Definition: Set of elements used to indicate when the booked funds will become available, ie can be accessed and start
generating interest.
Usage : this type of info is eg used in US, and is linked to particular instruments, such as cheques.
Example : When a cheque is deposited, it will be booked on the deposit day, but the funds will only be
accessible as of the indicated availability day (according to national banking regulations).
Type: This message item is composed of the following CashBalanceAvailability1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.181 Date <Dt> [1..1]
2.184 Amount <Amt> [1..1] Amount
2.185 CreditDebitIndicator <CdtDbtInd> [1..1] Code
Page 69
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
totalDigits: 18
CurrencyCode
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Page 70
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 71
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage : This component (on transaction level) can be used in case the booking is for a single transaction,
and charges are included in the entry amount. It can also be used in case individual charge amounts are
applied to individual transactions in case of a batch or aggregate amount booking.
Type: This message item is composed of the following ChargesInformation3 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.196 TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt> [0..1] Amount
2.197 Amount <Amt> [1..1] Amount
2.198 Type <Tp> [0..1]
2.201 Rate <Rate> [0..1] Rate
2.202 Bearer <Br> [0..1] Code
2.203 Party <Pty> [0..1] +
2.204 Tax <Tax> [0..1]
Page 72
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Format: CurrencyAndAmount
fractionDigits: 5
minInclusive: 0
totalDigits: 18
CurrencyCode
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Page 73
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 74
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 75
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage : This component (on transaction level) can be used in case the booking is for a single transaction,
and interest amount is included in the entry amount. It can also be used in case individual interest amounts
are applied to individual transactions in case of a batch or aggregate amount booking.
Type: This message item is composed of the following TransactionInterest1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.209 Amount <Amt> [1..1] Amount
2.210 CreditDebitIndicator <CdtDbtInd> [1..1] Code
2.211 Type <Tp> [0..1]
2.214 Rate <Rate> [0..n]
2.219 FromToDate <FrToDt> [0..1] +
2.220 Reason <Rsn> [0..1] Text
Page 76
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 77
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to CurrencyAndAmountRange p.339 in 'Message Item Types' section.
Page 78
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Page 79
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 80
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 81
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Definition: Party that plays an active role in planning and executing the transactions that create or liquidate investments
of the investors assets, or that move the investor's assets from one investment to another. A trading party is
a trade instructor, an investment decision-maker, a post trade administrator, or a trader. In the context of
treasury, it is the party negotiates and executes the treasury transaction.
Type: This message item is composed of the following PartyIdentification8 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
Name <Nm> [0..1] Text
PostalAddress <PstlAdr> [0..1]
Identification <Id> [0..1]
CountryOfResidence <CtryOfRes> [0..1] Code
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 82
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 83
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: If more than one intermediary agent is present, then IntermediaryAgent1 identifies the agent between
the debtor agent and the intermediary agent 2.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Usage: If more than two intermediary agents are present, then IntermediaryAgent2 identifies the agent
between the intermediary agent 1 and the intermediary agent 3.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Usage: If IntermediaryAgent3 is present, then it identifies the agent between the intermediary agent 2 and
the creditor agent.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
Page 84
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 85
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Note : this is typed by a financial institution identification - as this is the standard way of identifying eg
securities settlement agent/central system.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 86
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: purpose is used by the end-customers, ie originating party, initiating party, debtor, creditor, final
party, to provide information concerning the nature of the payment transaction. Purpose is a content element,
which is not used for processing by any of the agents involved in the payment chain.
Type: This message item is composed of one of the following Purpose1Choice element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.247 {Or Code <Cd> [1..1] Code
2.248 Or} Proprietary <Prtry> [1..1] Text
Page 87
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 88
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to PostalAddress1 p.369 in 'Message Item Types' section.
Page 89
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 90
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 91
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 92
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
CurrencyCode
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Page 93
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Rule(s): CurrencyCode
ValidationByTable
Page 94
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: if available, the initiating party should provide this reference in the structured remittance information,
to enable reconciliation by the creditor upon receipt of the cash.
If the business context requires the use of a creditor reference or a payment remit identification, and only
one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance
identification should be quoted in the end-to-end transaction identification.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 95
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Definition: Identification of the party to whom an invoice is issued, when different than the originator or debtor.
Type: This message item is composed of the following PartyIdentification8 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
Name <Nm> [0..1] Text
PostalAddress <PstlAdr> [0..1]
Identification <Id> [0..1]
CountryOfResidence <CtryOfRes> [0..1] Code
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 96
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 97
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 98
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 99
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to FinancialInstrumentQuantityChoice p.371 in 'Message Item Types'
section.
Page 100
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 101
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
For additional Type information, please refer to TaxInformation2 p.372 in 'Message Item Types' section.
Rule(s): ReturnReasonRule
If ReturnReason/Code is equal to 'NARR', then at least one occurrence of AdditionalReturnReasonInformation
must be present.
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Page 102
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.311 Code <Cd> [1..1] Code
2.312 Family <Fmly> [1..1]
Page 103
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
minLength: 1
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 104
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 105
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 106
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 107
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
contain holdings in any investment fund or investment fund class managed (or distributed) by the fund
manager, within the same fund family.
Type: This message item is composed of the following CashAccount7 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
Identification <Id> [1..1]
Type <Tp> [0..1]
Currency <Ccy> [0..1] Code
Name <Nm> [0..1] Text
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
Business Example
Narrative
AAAA Banken has agreed to provide an intraday account report to its customer Finpetrol. Each business day, at 12.30
PM, AAAA Banken will provide Finpetrol with an overview of all booked and expected entries since the start of the
business day. On 18 October, at 12.30 PM, AAAASESS sends such an intraday BankToCustomerAccountReport to
Company Finpetrol. It contains two entries : one booked, and one expected item. It has been pre-agreed between account
servicer and account owner that AAAA Banken will not include (expected) balance info in this intraday report.
Business Description
Page 108
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
Page 109
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
XML Instance
<?xml version = "1.0" encoding = "UTF-8"?>
<Document xmlns = "urn:iso:std:iso:20022:tech:xsd:camt.052.001.01" xmlns:xsi = "http://www.w3.org/2001/
XMLSchema-instance">
<BkToCstmrAcctRptV01>
<GrpHdr>
<MsgId>AAAASESS-FP-ACCR001</MsgId>
<CreDtTm>2007-10-18T12:30:00+01:00</CreDtTm>
<MsgPgntn>
<PgNb>1</PgNb>
<LastPgInd>true</LastPgInd>
Page 110
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
</MsgPgntn>
</GrpHdr>
<Rpt>
<Id>AAAASESS-FP-ACCR001</Id>
<CreDtTm>2007-10-18T12:30:00+01:00</CreDtTm>
<FrToDt>
<FrDtTm>2007-10-18T08:00:00+01:00</FrDtTm>
<ToDtTm>2007-10-18T12:30:00+01:00</ToDtTm>
</FrToDt>
<Acct>
<Id>
<PrtryAcct>
<Id>50000000054910000003</Id>
</PrtryAcct>
</Id>
<Ownr>
<Nm>FINPETROL</Nm>
</Ownr>
<Svcr>
<FinInstnId>
<NmAndAdr>
<Nm>AAAA BANKEN</Nm>
<PstlAdr>
<Ctry>SE</Ctry>
</PstlAdr>
</NmAndAdr>
</FinInstnId>
</Svcr>
</Acct>
<Ntry>
<Amt Ccy = "SEK">200000</Amt>
<CdtDbtInd>DBIT</CdtDbtInd>
<Sts>BOOK</Sts>
<BookgDt>
<DtTm>2007-10-18T10:15:00+01:00</DtTm>
</BookgDt>
<ValDt>
<Dt>2007-10-18</Dt>
</ValDt>
<AcctSvcrRef>AAAASESS-FP-ACCR-01</AcctSvcrRef>
<BkTxCd>
<Domn>
<Cd>PAYM</Cd>
<Fmly>
<Cd>0001</Cd>
<SubFmlyCd>0003</SubFmlyCd>
</Fmly>
</Domn>
</BkTxCd>
<Btch>
<MsgId>FINP-0055</MsgId>
<PmtInfId>FINP-0055-001</PmtInfId>
Page 111
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.052.001.01 BankToCustomerAccountReportV01
<NbOfTxs>20</NbOfTxs>
</Btch>
</Ntry>
<Ntry>
<Amt Ccy = "SEK">30000</Amt>
<CdtDbtInd>CRDT</CdtDbtInd>
<Sts>PDNG</Sts>
<ValDt>
<Dt>2007-10-18</Dt>
</ValDt>
<AcctSvcrRef>AAAASESS-FP-CONF-FX</AcctSvcrRef>
<BkTxCd>
<Domn>
<Cd>TREA</Cd>
<Fmly>
<Cd>0002</Cd>
<SubFmlyCd>0000</SubFmlyCd>
</Fmly>
</Domn>
</BkTxCd>
<TxDtls>
<Refs>
<InstrId>FP-004567-FX</InstrId>
<EndToEndId>AAAASS1085FINPSS</EndToEndId>
</Refs>
<AmtDtls>
<CntrValAmt>
<Amt Ccy = "EUR">3255.5694</Amt>
<CcyXchg>
<SrcCcy>EUR</SrcCcy>
<XchgRate>0.1085</XchgRate>
</CcyXchg>
</CntrValAmt>
</AmtDtls>
</TxDtls>
</Ntry>
</Rpt>
</BkToCstmrAcctRptV01>
</Document>
Page 112
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
MX camt.053.001.01 BankToCustomerStatementV01
Message Scope and Usage
Scope
The Bank-to-Customer Statement 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 is used to inform the account owner, or authorised party, of the entries booked
to the account, and to provide the owner with balance information on the account at a given point in time.
Usage
The Bank-to-Customer Statement message can contain reports for more than 1 account. It provides information for cash
management and/or reconciliation.
It contains information on booked entries only.
It can include underlying details of transactions that have been included in the entry.
The message is exchanged as defined between the account servicer and the account owner. It provides information on
items that have been booked to the account (and therefore are ‘binding’) and also balance information. Depending on
services agreed between banks and their customers, ‘binding’ statements can be generated and exchanged intraday.
Depending on legal requirements in local jurisdictions, ‘end-of-day’ statements may need to be mandatorily generated
and exchanged.
It is possible that the receiver of the message is not the account owner, but a party entitled through arrangement with the
account owner to receive the account information (also known as recipient).
Outline
The Bank-to-Customer Statement message is composed of 2 building blocks:
A. Group Header
This building block is mandatory and present once. It contains elements such as Message Identification and
CreationDateTime.
B. Statement
This building block is mandatory and repetitive. It should be repeated for each account on which a statement is provided.
The report contains components such as Balance and Entry information.
Message Structure
Index Or Message Item <XML Tag> Mult. Represent./ Rule/
Type Guid.
No.
Message root <BkToCstmrStmtV01 [1..1]
>
Page 113
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 114
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 115
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 116
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 117
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 118
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 119
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 120
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 121
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 122
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 123
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage: The account servicing institution has to make sure that 'MessageIdentification' is unique per instructed
party for a pre-agreed period.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Guideline : MessageRecipient should only be identified when different from the account owner.
Type: This message item is composed of the following PartyIdentification8 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
Name <Nm> [0..1] Text
PostalAddress <PstlAdr> [0..1]
Identification <Id> [0..1]
CountryOfResidence <CtryOfRes> [0..1] Code
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 124
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage: the pagination of the message is only allowed when agreed between the parties.
Type: This message item is composed of the following Pagination element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
1.5 PageNumber <PgNb> [1..1] Text
1.6 LastPageIndicator <LastPgInd> [1..1] Indicator
Page 125
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage : in those scenarios where eg a paper statement is a legal requirement, the paper statement may have
a different numbering than the electronic sequential number. Paper statements can for instance only be sent
if movement on the account has taken place, whereas electronic statements can be sent eg each day, regardless
of whether movements have taken place or not.
Data Type: Number
Format: fractionDigits: 0
totalDigits: 18
Page 126
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Page 127
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to AccountIdentification3Choice p.333 in 'Message Item Types' section.
Page 128
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage : the account name is different from the account owner name. The account name is used in certain
user communities to provide a means of identifying the account, in addition to the account owner's identity
and the account number.
Data Type: Max70Text
Format: maxLength: 70
minLength: 1
Page 129
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
Page 130
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Definition: Provides general interest information that applies to the account at a particular moment in time.
Type: This message item is composed of the following AccountInterest1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.18 Type <Tp> [0..1]
2.21 Rate <Rate> [0..n]
2.26 FromToDate <FrToDt> [0..1] +
2.27 Reason <Rsn> [0..1] Text
Page 131
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 132
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyAndAmountRange p.339 in 'Message Item Types' section.
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Rule(s): AvailabilityAndTypeRule
If Type is equal to ForwardAvailable, Availability is not allowed.
Page 133
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 134
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 135
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 136
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage : if not present, credit line is not included in the balance amount.
Data Type: One of the following TrueFalseIndicator values must be used:
MeaningWhenTrue: True
MeaningWhenFalse: False
Page 137
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to DateAndDateTimeChoice p.345 in 'Message Item Types' section.
Usage : this type of info is eg used in US, and is linked to particular instruments, such as cheques.
Example : When a cheque is deposited, it will be booked on the deposit day, but the funds will only be
accessible as of the indicated availability day (according to national banking regulations).
Type: This message item is composed of the following CashBalanceAvailability1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.39 Date <Dt> [1..1]
2.42 Amount <Amt> [1..1] Amount
2.43 CreditDebitIndicator <CdtDbtInd> [1..1] Code
Page 138
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 139
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Guideline(s): DebitCreditIndicatorGuideline
DebitCreditIndicator should be present when TotalNetEntryAmount is present.
Page 140
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 141
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Guideline(s): DebitCreditIndicatorGuideline
DebitCreditIndicator should be present when TotalNetEntryAmount is present.
Page 142
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Page 143
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Definition: Specifies the domain, the family and the sub-family of the bank transaction code, in a structured and
hierarchical format.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.63 Code <Cd> [1..1] Code
2.64 Family <Fmly> [1..1]
Page 144
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 145
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 146
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage: At least one reference must be provided to identify the entry and its underlying transaction(s).
Type: This message item is composed of the following StatementEntry1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.77 Amount <Amt> [1..1] Amount
2.78 CreditDebitIndicator <CdtDbtInd> [1..1] Code
2.79 ReversalIndicator <RvslInd> [0..1] Indicator
2.80 Status <Sts> [1..1] Code
2.81 BookingDate <BookgDt> [0..1] +
2.82 ValueDate <ValDt> [0..1] +
2.83 AccountServicerReference <AcctSvcrRef> [0..1] Text
2.84 Availability <Avlbty> [0..n]
2.90 BankTransactionCode <BkTxCd> [1..1]
2.99 CommissionWaiverIndicator <ComssnWvrInd> [0..1] Indicator
2.100 AdditionalInformationIndicator <AddtlInfInd> [0..1]
2.103 Batch <Btch> [0..n]
2.107 AmountDetails <AmtDtls> [0..1]
2.124 Charges <Chrgs> [0..n]
2.137 Interest <Intrst> [0..n]
2.150 TransactionDetails <TxDtls> [0..n]
2.329 AdditionalEntryInformation <AddtlNtryInf> [0..1] Text
Rule(s): StatusAndBookingDateRule
If Status is pending, BookingDate must is not allowed.
Guideline(s): ReferenceGuideline
At least one reference should present to identify the underlying transaction(s).
Page 147
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage : this element should only be present if the entry is the result of a reversal operation.
If the CreditDebitIndicator is CRDT and ReversalIndicator is Yes, the original operation was a debit entry.
If the CreditDebitIndicator is DBIT and ReversalIndicator is Yes, the original operation was a credit entry.
Data Type: One of the following TrueFalseIndicator values must be used:
MeaningWhenTrue: True
MeaningWhenFalse: False
Usage :
Status Booked does not necessarily imply finality of money
as this depends on other factors such as the payment system
used, the completion of the end-to-end transaction and the
terms agreed between account servicer and owner.
Status Booked is the only status that can be reversed.
Page 148
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to DateAndDateTimeChoice p.345 in 'Message Item Types' section.
Usage : For entries which are subject to availability/float (and for which availability information is present),
value date must not be used, as the availability component identifies the number of availability days.
Type: This message item is composed of one of the following DateAndDateTimeChoice element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
{Or Date <Dt> [1..1] DateTime
Or} DateTime <DtTm> [1..1] DateTime
For additional Type information, please refer to DateAndDateTimeChoice p.345 in 'Message Item Types' section.
Usage : this type of info is eg used in US, and is linked to particular instruments, such as cheques.
Example : When a cheque is deposited, it will be booked on the deposit day, but the funds will only be
accessible as of the indicated availability day (according to national banking regulations).
Type: This message item is composed of the following CashBalanceAvailability1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.85 Date <Dt> [1..1]
2.88 Amount <Amt> [1..1] Amount
2.89 CreditDebitIndicator <CdtDbtInd> [1..1] Code
Page 149
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 150
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.92 Code <Cd> [1..1] Code
2.93 Family <Fmly> [1..1]
Page 151
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 152
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage : this element can be repeated in case more than one batch is included in the entry, eg, in lockbox
scenarios, to specify the ID and number of transactions included in each of the batches.
Type: This message item is composed of the following BatchInformation1 element(s):
Page 153
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage : This component (on entry level) should be used when a total original batch or aggregate amount has
to be provided. (If required, the original amounts for each individual transaction can be included in the same
component on transaction details level.)
Type: This message item is composed of the following AmountAndCurrencyExchange2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.108 InstructedAmount <InstdAmt> [0..1]
2.111 TransactionAmount <TxAmt> [0..1]
2.114 CounterValueAmount <CntrValAmt> [0..1]
2.117 AnnouncedPostingAmount <AnncdPstngAmt> [0..1]
2.120 ProprietaryAmount <PrtryAmt> [0..n]
Page 154
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 155
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 156
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Definition: Identifies the countervalue amount and provides currency exchange information. Either the counter amount
quoted in an FX deal, or the result of the currency information applied to an instructed amount, before
deduction of charges.
Type: This message item is composed of the following AmountAndCurrencyExchangeDetails1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.115 Amount <Amt> [1..1] Amount
2.116 CurrencyExchange <CcyXchg> [0..1] +
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 157
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Amount of money, based on terms of corporate action event and balance of underlying securities, entitled
to/from the account owner.
In those situations, this amount may alternatively be called entitled amount.
Type: This message item is composed of the following AmountAndCurrencyExchangeDetails1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.118 Amount <Amt> [1..1] Amount
2.119 CurrencyExchange <CcyXchg> [0..1] +
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 158
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 159
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 160
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 161
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 162
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 163
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Page 164
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 165
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyAndAmountRange p.339 in 'Message Item Types' section.
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Page 166
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 167
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Format: maxLength: 35
minLength: 1
Usage: the instruction identification is a point to point reference that can be used between the instructing
party and the instructed party to refer to the individual instruction. It can be included in several messages
related to the instruction.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction.
It can be included in several messages related to the transaction.
Usage: In case there are technical limitations to carry on multiple references, the end-to-end identification
must be carried on throughout the entire end-to-end chain.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the
transaction on the interbank level.
Usage: The instructing agent has to make sure the transaction identification is unique for a pre-agreed period.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Page 168
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 169
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage: This component (on transaction level) should be used in case booking is for a single transaction and
the original amount is different from the entry amount. It can also be used in case individual original amounts
are provided in case of a batch or aggregate booking.
Type: This message item is composed of the following AmountAndCurrencyExchange2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.164 InstructedAmount <InstdAmt> [0..1]
2.167 TransactionAmount <TxAmt> [0..1]
2.170 CounterValueAmount <CntrValAmt> [0..1]
2.173 AnnouncedPostingAmount <AnncdPstngAmt> [0..1]
2.176 ProprietaryAmount <PrtryAmt> [0..n]
Page 170
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 171
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 172
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Amount of money, based on terms of corporate action event and balance of underlying securities, entitled
to/from the account owner.
In those situations, this amount may alternatively be called entitled amount.
Type: This message item is composed of the following AmountAndCurrencyExchangeDetails1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.174 Amount <Amt> [1..1] Amount
2.175 CurrencyExchange <CcyXchg> [0..1] +
Page 173
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 174
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Usage : this type of info is eg used in US, and is linked to particular instruments, such as cheques.
Example : When a cheque is deposited, it will be booked on the deposit day, but the funds will only be
accessible as of the indicated availability day (according to national banking regulations).
Type: This message item is composed of the following CashBalanceAvailability1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.181 Date <Dt> [1..1]
2.184 Amount <Amt> [1..1] Amount
2.185 CreditDebitIndicator <CdtDbtInd> [1..1] Code
Page 175
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 176
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.188 Code <Cd> [1..1] Code
2.189 Family <Fmly> [1..1]
Page 177
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage : This component (on transaction level) can be used in case the booking is for a single transaction,
and charges are included in the entry amount. It can also be used in case individual charge amounts are
applied to individual transactions in case of a batch or aggregate amount booking.
Page 178
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 179
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 180
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 181
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage : This component (on transaction level) can be used in case the booking is for a single transaction,
and interest amount is included in the entry amount. It can also be used in case individual interest amounts
are applied to individual transactions in case of a batch or aggregate amount booking.
Type: This message item is composed of the following TransactionInterest1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.209 Amount <Amt> [1..1] Amount
2.210 CreditDebitIndicator <CdtDbtInd> [1..1] Code
2.211 Type <Tp> [0..1]
2.214 Rate <Rate> [0..n]
2.219 FromToDate <FrToDt> [0..1] +
2.220 Reason <Rsn> [0..1] Text
Page 182
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 183
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 184
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to CurrencyAndAmountRange p.339 in 'Message Item Types' section.
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Page 185
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
Page 186
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
Page 187
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 188
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 189
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Usage: If more than one intermediary agent is present, then IntermediaryAgent1 identifies the agent between
the debtor agent and the intermediary agent 2.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Usage: If more than two intermediary agents are present, then IntermediaryAgent2 identifies the agent
between the intermediary agent 1 and the intermediary agent 3.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 190
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage: If IntermediaryAgent3 is present, then it identifies the agent between the intermediary agent 2 and
the creditor agent.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 191
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Note : this is typed by a financial institution identification - as this is the standard way of identifying eg
securities settlement agent/central system.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 192
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Usage: purpose is used by the end-customers, ie originating party, initiating party, debtor, creditor, final
party, to provide information concerning the nature of the payment transaction. Purpose is a content element,
which is not used for processing by any of the agents involved in the payment chain.
Type: This message item is composed of one of the following Purpose1Choice element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.247 {Or Code <Cd> [1..1] Code
2.248 Or} Proprietary <Prtry> [1..1] Text
Page 193
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 194
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to PostalAddress1 p.369 in 'Message Item Types' section.
Page 195
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 196
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 197
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 198
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Page 199
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Rule(s): CurrencyCode
ValidationByTable
Page 200
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Usage: if available, the initiating party should provide this reference in the structured remittance information,
to enable reconciliation by the creditor upon receipt of the cash.
If the business context requires the use of a creditor reference or a payment remit identification, and only
one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance
identification should be quoted in the end-to-end transaction identification.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Page 201
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 202
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 203
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 204
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by CurrencyCode.
Format: CurrencyAndAmount
fractionDigits: 5
minInclusive: 0
totalDigits: 18
CurrencyCode
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Page 205
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to FinancialInstrumentQuantityChoice p.371 in 'Message Item Types'
section.
Page 206
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 207
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to TaxInformation2 p.372 in 'Message Item Types' section.
Rule(s): ReturnReasonRule
If ReturnReason/Code is equal to 'NARR', then at least one occurrence of AdditionalReturnReasonInformation
must be present.
Page 208
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.311 Code <Cd> [1..1] Code
2.312 Family <Fmly> [1..1]
Page 209
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
minLength: 1
Page 210
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 211
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 212
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 213
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Format: maxLength: 35
minLength: 1
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
Business Example
Narrative
On 18 October, at 5.00 PM, AAAASESS sends an end-of-day BankToCustomerStatement to Company Finpetrol. It
contains all booked items during the business day.
Page 214
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Business Description
Page 215
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
Page 216
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
XML Instance
<?xml version = "1.0" encoding = "UTF-8"?>
<Document xmlns = "urn:iso:std:iso:20022:tech:xsd:camt.053.001.01" xmlns:xsi = "http://www.w3.org/2001/
XMLSchema-instance">
<BkToCstmrStmtV01>
<GrpHdr>
<MsgId>AAAASESS-FP-STAT001</MsgId>
<CreDtTm>2007-10-18T17:00:00+01:00</CreDtTm>
<MsgPgntn>
<PgNb>1</PgNb>
<LastPgInd>true</LastPgInd>
</MsgPgntn>
Page 217
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
</GrpHdr>
<Stmt>
<Id>AAAASESS-FP-STAT001</Id>
<CreDtTm>2007-10-18T17:00:00+01:00</CreDtTm>
<FrToDt>
<FrDtTm>2007-10-18T08:00:00+01:00</FrDtTm>
<ToDtTm>2007-10-18T17:00:00+01:00</ToDtTm>
</FrToDt>
<Acct>
<Id>
<PrtryAcct>
<Id>50000000054910000003</Id>
</PrtryAcct>
</Id>
<Ownr>
<Nm>FINPETROL</Nm>
</Ownr>
<Svcr>
<FinInstnId>
<NmAndAdr>
<Nm>AAAA BANKEN</Nm>
<PstlAdr>
<Ctry>SE</Ctry>
</PstlAdr>
</NmAndAdr>
</FinInstnId>
</Svcr>
</Acct>
<Bal>
<Tp>
<Cd>OPBD</Cd>
</Tp>
<Amt Ccy = "SEK">500000</Amt>
<CdtDbtInd>CRDT</CdtDbtInd>
<Dt>
<Dt>2007-10-17</Dt>
</Dt>
</Bal>
<Bal>
<Tp>
<Cd>CLBD</Cd>
</Tp>
<Amt Ccy = "SEK">435678.50</Amt>
<CdtDbtInd>CRDT</CdtDbtInd>
<Dt>
<Dt>2007-10-18</Dt>
</Dt>
</Bal>
<Ntry>
<Amt Ccy = "SEK">105678.50</Amt>
<CdtDbtInd>CRDT</CdtDbtInd>
<Sts>BOOK</Sts>
Page 218
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
<BookgDt>
<DtTm>2007-10-18T13:15:00+01:00</DtTm>
</BookgDt>
<ValDt>
<Dt>2007-10-18</Dt>
</ValDt>
<AcctSvcrRef>AAAASESS-FP-CN-98765/01</AcctSvcrRef>
<BkTxCd>
<Domn>
<Cd>PAYM</Cd>
<Fmly>
<Cd>0001</Cd>
<SubFmlyCd>0005</SubFmlyCd>
</Fmly>
</Domn>
</BkTxCd>
<TxDtls>
<Refs>
<EndToEndId>MUELL/FINP/RA12345</EndToEndId>
</Refs>
<RltdPties>
<Dbtr>
<Nm>MUELLER</Nm>
</Dbtr>
</RltdPties>
</TxDtls>
</Ntry>
<Ntry>
<Amt Ccy = "SEK">2000000</Amt>
<CdtDbtInd>DBIT</CdtDbtInd>
<Sts>BOOK</Sts>
<BookgDt>
<DtTm>2007-10-18T10:15:00+01:00</DtTm>
</BookgDt>
<ValDt>
<Dt> 2007-10-18</Dt>
</ValDt>
<AcctSvcrRef> AAAASESS-FP-ACCR-01</AcctSvcrRef>
<BkTxCd>
<Domn>
<Cd>PAYM</Cd>
<Fmly>
<Cd>0001</Cd>
<SubFmlyCd>0003</SubFmlyCd>
</Fmly>
</Domn>
</BkTxCd>
<Btch>
<MsgId>FINP-0055</MsgId>
<PmtInfId>FINP-0055-001</PmtInfId>
<NbOfTxs>20</NbOfTxs>
</Btch>
Page 219
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.053.001.01 BankToCustomerStatementV01
</Ntry>
<Ntry>
<Amt Ccy = "SEK">30000</Amt>
<CdtDbtInd>CRDT</CdtDbtInd>
<Sts>BOOK</Sts>
<BookgDt>
<DtTm>2007-10-18T15:15:00+01:00</DtTm>
</BookgDt>
<ValDt>
<Dt>2007-10-18</Dt>
</ValDt>
<AcctSvcrRef>AAAASESS-FP-CONF-FX</AcctSvcrRef>
<BkTxCd>
<Domn>
<Cd>TREA</Cd>
<Fmly>
<Cd>0002</Cd>
<SubFmlyCd>0000</SubFmlyCd>
</Fmly>
</Domn>
</BkTxCd>
<TxDtls>
<Refs>
<InstrId>FP-004567-FX</InstrId>
<EndToEndId>AAAASS1085FINPSS</EndToEndId>
</Refs>
<AmtDtls>
<CntrValAmt>
<Amt Ccy = "EUR">3255.5694</Amt>
<CcyXchg>
<SrcCcy>EUR</SrcCcy>
<XchgRate>0.1085</XchgRate>
</CcyXchg>
</CntrValAmt>
</AmtDtls>
</TxDtls>
</Ntry>
</Stmt>
</BkToCstmrStmtV01>
</Document>
Page 220
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
MX camt.054.001.01
BankToCustomerDebitCreditNotificationV01
Message Scope and Usage
Scope
The Bank-to-Customer Debit/Credit Notification 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 Bank-to-Customer Debit/Credit Notification message can contain reports for more than 1 account. It provides
information for cash management and/or reconciliation.
It 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.
Outline
The Bank-to-Customer DebitCreditNotification message is composed of 2 building blocks:
A. Group Header
This building block is mandatory and present once. It contains elements such as Message Identification and
CreationDateTime.
B. 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 and pending debit and/or credit entries.
Message Structure
Index Or Message Item <XML Tag> Mult. Represent./ Rule/
Type Guid.
No.
Message root <BkToCstmrDbtCdtN [1..1]
tfctnV01>
Page 221
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 222
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 223
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 224
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 225
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 226
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 227
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 228
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 229
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 230
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage: The account servicing institution has to make sure that 'MessageIdentification' is unique per instructed
party for a pre-agreed period.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Page 231
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Definition: Party that is entitled by the account owner to receive information about movements in the account.
Guideline : MessageRecipient should only be identified when different from the account owner.
Type: This message item is composed of the following PartyIdentification8 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
Name <Nm> [0..1] Text
PostalAddress <PstlAdr> [0..1]
Identification <Id> [0..1]
CountryOfResidence <CtryOfRes> [0..1] Code
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Usage: the pagination of the message is only allowed when agreed between the parties.
Type: This message item is composed of the following Pagination element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
1.5 PageNumber <PgNb> [1..1] Text
1.6 LastPageIndicator <LastPgInd> [1..1] Indicator
Page 232
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage : in those scenarios where eg a paper statement is a legal requirement, the paper statement may have
a different numbering than the electronic sequential number. Paper statements can for instance only be sent
if movement on the account has taken place, whereas electronic statements can be sent eg each day, regardless
of whether movements have taken place or not.
Page 233
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Page 234
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to AccountIdentification3Choice p.333 in 'Message Item Types' section.
Page 235
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 236
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage : the account name is different from the account owner name. The account name is used in certain
user communities to provide a means of identifying the account, in addition to the account owner's identity
and the account number.
Data Type: Max70Text
Format: maxLength: 70
minLength: 1
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 237
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
Guideline(s): DebitCreditIndicatorGuideline
DebitCreditIndicator should be present when TotalNetEntryAmount is present.
Page 238
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
totalDigits: 18
Page 239
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Guideline(s): DebitCreditIndicatorGuideline
DebitCreditIndicator should be present when TotalNetEntryAmount is present.
Page 240
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Page 241
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Definition: Specifies the domain, the family and the sub-family of the bank transaction code, in a structured and
hierarchical format.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.36 Code <Cd> [1..1] Code
2.37 Family <Fmly> [1..1]
Page 242
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 243
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 244
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage: At least one reference must be provided to identify the entry and its underlying transaction(s).
Type: This message item is composed of the following NotificationEntry1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.50 Amount <Amt> [1..1] Amount
2.51 CreditDebitIndicator <CdtDbtInd> [1..1] Code
2.52 ReversalIndicator <RvslInd> [0..1] Indicator
2.53 Status <Sts> [1..1] Code
2.54 BookingDate <BookgDt> [0..1] +
2.55 ValueDate <ValDt> [0..1] +
2.56 AccountServicerReference <AcctSvcrRef> [0..1] Text
2.57 Availability <Avlbty> [0..n]
2.63 BankTransactionCode <BkTxCd> [1..1]
2.72 CommissionWaiverIndicator <ComssnWvrInd> [0..1] Indicator
2.73 AdditionalInformationIndicator <AddtlInfInd> [0..1]
2.76 Batch <Btch> [0..n]
2.80 AmountDetails <AmtDtls> [0..1]
2.97 Charges <Chrgs> [0..n]
2.110 Interest <Intrst> [0..n]
2.123 TransactionDetails <TxDtls> [0..n]
2.302 AdditionalEntryInformation <AddtlNtryInf> [0..1] Text
Rule(s): StatusAndBookingDateRule
If Status is pending, BookingDate is not allowed.
Guideline(s): ReferenceGuideline
At least one reference should present to identify the underlying transaction(s).
Page 245
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage : this element should only be present if the entry is the result of a reversal operation.
If the CreditDebitIndicator is CRDT and ReversalIndicator is Yes, the original operation was a debit entry.
If the CreditDebitIndicator is DBIT and ReversalIndicator is Yes, the original operation was a credit entry.
Data Type: One of the following TrueFalseIndicator values must be used:
MeaningWhenTrue: True
MeaningWhenFalse: False
Usage :
Status Booked does not necessarily imply finality of money
as this depends on other factors such as the payment system
used, the completion of the end-to-end transaction and the
terms agreed between account servicer and owner.
Status Booked is the only status that can be reversed.
PDNG Pending Booking on the account owner's account in the account
servicer's ledger has not been completed.
Usage : this can be used for expected items, or for items for
which some conditions still need to be fulfilled before they
can be booked. If booking takes place, the entry will be
included with status Booked in subsequent account report
or statement. Status Pending cannot be reversed.
Page 246
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to DateAndDateTimeChoice p.345 in 'Message Item Types' section.
Usage : When entry status is pending , and value date is present, value date refers to an expected/requested
value date.
For entries which are subject to availability/float (and for which availability information is present), value
date must not be used, as the availability component identifies the number of availability days.
Type: This message item is composed of one of the following DateAndDateTimeChoice element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
{Or Date <Dt> [1..1] DateTime
Or} DateTime <DtTm> [1..1] DateTime
For additional Type information, please refer to DateAndDateTimeChoice p.345 in 'Message Item Types' section.
Usage : this type of info is eg used in US, and is linked to particular instruments, such as cheques.
Page 247
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Example : When a cheque is deposited, it will be booked on the deposit day, but the funds will only be
accessible as of the indicated availability day (according to national banking regulations).
Type: This message item is composed of the following CashBalanceAvailability1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.58 Date <Dt> [1..1]
2.61 Amount <Amt> [1..1] Amount
2.62 CreditDebitIndicator <CdtDbtInd> [1..1] Code
Page 248
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
ValidationByTable
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.65 Code <Cd> [1..1] Code
2.66 Family <Fmly> [1..1]
Page 249
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 250
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 251
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage : this element can be repeated in case more than one batch is included in the entry, eg, in lockbox
scenarios, to specify the ID and number of transactions included in each of the batches.
Type: This message item is composed of the following BatchInformation1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.77 MessageIdentification <MsgId> [0..1] Text
2.78 PaymentInformationIdentification <PmtInfId> [0..1] Text
2.79 NumberOfTransactions <NbOfTxs> [0..1] Text
Usage : This component (on entry level) should be used when a total original batch or aggregate amount has
to be provided. (If required, the individual original amounts can be included in the same component on
transaction details level).
Type: This message item is composed of the following AmountAndCurrencyExchange2 element(s):
Page 252
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 253
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 254
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 255
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Amount of money, based on terms of corporate action event and balance of underlying securities, entitled
to/from the account owner.
In those situations, this amount may alternatively be called entitled amount.
Type: This message item is composed of the following AmountAndCurrencyExchangeDetails1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.91 Amount <Amt> [1..1] Amount
2.92 CurrencyExchange <CcyXchg> [0..1] +
Page 256
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 257
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Usage : this component is used on entry level in case of batch or aggregate bookings.
Type: This message item is composed of the following ChargesInformation3 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.98 TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt> [0..1] Amount
2.99 Amount <Amt> [1..1] Amount
2.100 Type <Tp> [0..1]
2.103 Rate <Rate> [0..1] Rate
2.104 Bearer <Br> [0..1] Code
2.105 Party <Pty> [0..1] +
2.106 Tax <Tax> [0..1]
Page 258
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Page 259
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Format: [a-zA-Z0-9]{1,4}
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 260
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage : This component is used on entry level in case of batch or aggregate bookings.
Type: This message item is composed of the following TransactionInterest1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.111 Amount <Amt> [1..1] Amount
2.112 CreditDebitIndicator <CdtDbtInd> [1..1] Code
Page 261
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 262
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 263
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyAndAmountRange p.339 in 'Message Item Types' section.
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Page 264
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Definition: Underlying reason for the interest, eg, yearly credit interest on a savings account.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Page 265
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage: the instruction identification is a point to point reference that can be used between the instructing
party and the instructed party to refer to the individual instruction. It can be included in several messages
related to the instruction.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction.
It can be included in several messages related to the transaction.
Page 266
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage: In case there are technical limitations to carry on multiple references, the end-to-end identification
must be carried on throughout the entire end-to-end chain.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the
transaction on the interbank level.
Usage: The instructing agent has to make sure the transaction identification is unique for a pre-agreed period.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
Page 267
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage: This component (on transaction level) should be used in case booking is for a single transaction and
the original amount is different from the entry amount. It can also be used in case individual original amounts
are provided in case of a batch or aggregate booking.
Type: This message item is composed of the following AmountAndCurrencyExchange2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.137 InstructedAmount <InstdAmt> [0..1]
2.140 TransactionAmount <TxAmt> [0..1]
2.143 CounterValueAmount <CntrValAmt> [0..1]
2.146 AnnouncedPostingAmount <AnncdPstngAmt> [0..1]
2.149 ProprietaryAmount <PrtryAmt> [0..n]
Page 268
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 269
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 270
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Amount of money, based on terms of corporate action event and balance of underlying securities, entitled
to/from the account owner.
In those situations, this amount may alternatively be called entitled amount.
Type: This message item is composed of the following AmountAndCurrencyExchangeDetails1 element(s):
Page 271
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 272
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyExchange3 p.343 in 'Message Item Types' section.
Page 273
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Definition: Set of elements used to indicate when the booked funds will become available, ie can be accessed and start
generating interest.
Usage : this type of info is eg used in US, and is linked to particular instruments, such as cheques.
Example : When a cheque is deposited, it will be booked on the deposit day, but the funds will only be
accessible as of the indicated availability day (according to national banking regulations).
Type: This message item is composed of the following CashBalanceAvailability1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.154 Date <Dt> [1..1]
2.157 Amount <Amt> [1..1] Amount
2.158 CreditDebitIndicator <CdtDbtInd> [1..1] Code
Page 274
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
totalDigits: 18
CurrencyCode
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Page 275
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 276
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage : This component (on transaction level) can be used in case the booking is for a single transaction,
and charges are included in the entry amount. It can also be used in case individual charge amounts are
applied to individual transactions in case of a batch or aggregate amount booking.
Type: This message item is composed of the following ChargesInformation3 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.169 TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt> [0..1] Amount
2.170 Amount <Amt> [1..1] Amount
2.171 Type <Tp> [0..1]
2.174 Rate <Rate> [0..1] Rate
2.175 Bearer <Br> [0..1] Code
2.176 Party <Pty> [0..1] +
2.177 Tax <Tax> [0..1]
Page 277
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Format: CurrencyAndAmount
fractionDigits: 5
minInclusive: 0
totalDigits: 18
CurrencyCode
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Page 278
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 279
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 280
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage : This component (on transaction level) can be used in case the booking is for a single transaction,
and interest amount is included in the entry amount. It can also be used in case individual interest amounts
are applied to individual transactions in case of a batch or aggregate amount booking.
Type: This message item is composed of the following TransactionInterest1 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.182 Amount <Amt> [1..1] Amount
2.183 CreditDebitIndicator <CdtDbtInd> [1..1] Code
2.184 Type <Tp> [0..1]
2.187 Rate <Rate> [0..n]
2.192 FromToDate <FrToDt> [0..1] +
2.193 Reason <Rsn> [0..1] Text
Page 281
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 282
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to CurrencyAndAmountRange p.339 in 'Message Item Types' section.
Page 283
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to DateTimePeriodDetails p.345 in 'Message Item Types' section.
Page 284
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 285
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 286
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Definition: Party that plays an active role in planning and executing the transactions that create or liquidate investments
of the investors assets, or that move the investor's assets from one investment to another. A trading party is
a trade instructor, an investment decision-maker, a post trade administrator, or a trader. In the context of
treasury, it is the party negotiates and executes the treasury transaction.
Type: This message item is composed of the following PartyIdentification8 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
Name <Nm> [0..1] Text
PostalAddress <PstlAdr> [0..1]
Identification <Id> [0..1]
CountryOfResidence <CtryOfRes> [0..1] Code
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 287
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 288
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage: If more than one intermediary agent is present, then IntermediaryAgent1 identifies the agent between
the debtor agent and the intermediary agent 2.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Usage: If more than two intermediary agents are present, then IntermediaryAgent2 identifies the agent
between the intermediary agent 1 and the intermediary agent 3.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Usage: If IntermediaryAgent3 is present, then it identifies the agent between the intermediary agent 2 and
the creditor agent.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
Page 289
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 290
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Note : this is typed by a financial institution identification - as this is the standard way of identifying eg
securities settlement agent/central system.
Type: This message item is composed of the following BranchAndFinancialInstitutionIdentification3 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
FinancialInstitutionIdentification <FinInstnId> [1..1]
BranchIdentification <BrnchId> [0..1]
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
For additional Type information, please refer to BranchAndFinancialInstitutionIdentification3 p.346 in 'Message Item
Types' section.
Page 291
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage: purpose is used by the end-customers, ie originating party, initiating party, debtor, creditor, final
party, to provide information concerning the nature of the payment transaction. Purpose is a content element,
which is not used for processing by any of the agents involved in the payment chain.
Type: This message item is composed of one of the following Purpose1Choice element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.220 {Or Code <Cd> [1..1] Code
2.221 Or} Proprietary <Prtry> [1..1] Text
Page 292
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 293
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to PostalAddress1 p.369 in 'Message Item Types' section.
Page 294
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 295
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 296
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 297
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
CurrencyCode
[A-Z]{3,3}
Rule(s): CurrencyCode
ValidationByTable
Page 298
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Rule(s): CurrencyCode
ValidationByTable
Page 299
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage: if available, the initiating party should provide this reference in the structured remittance information,
to enable reconciliation by the creditor upon receipt of the cash.
If the business context requires the use of a creditor reference or a payment remit identification, and only
one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance
identification should be quoted in the end-to-end transaction identification.
Data Type: Max35Text
Format: maxLength: 35
minLength: 1
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 300
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Definition: Identification of the party to whom an invoice is issued, when different than the originator or debtor.
Type: This message item is composed of the following PartyIdentification8 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
Name <Nm> [0..1] Text
PostalAddress <PstlAdr> [0..1]
Identification <Id> [0..1]
CountryOfResidence <CtryOfRes> [0..1] Code
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 301
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 302
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 303
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 304
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to FinancialInstrumentQuantityChoice p.371 in 'Message Item Types'
section.
Page 305
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 306
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
For additional Type information, please refer to TaxInformation2 p.372 in 'Message Item Types' section.
Rule(s): ReturnReasonRule
If ReturnReason/Code is equal to 'NARR', then at least one occurrence of AdditionalReturnReasonInformation
must be present.
Rule(s): DomainAndProprietary1Rule
If Domain is absent, then Proprietary must be present.
DomainAndProprietary2Rule
If Proprietary is absent, then Domain must be present.
FamilyAndSubFamilyRule
A specific (non-generic) SubFamily code may only be provided if a specific (non-generic) Family code is present.
Page 307
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Usage: If a specific family or subfamily code cannot be provided, the generic family code defined for the
domain or the generic subfamily code defined for the family should be provided.
Type: This message item is composed of the following BankTransactionCodeStructure2 element(s):
Index Or Message Item <XML Tag> Mult. Represent./
Type
2.284 Code <Cd> [1..1] Code
2.285 Family <Fmly> [1..1]
Page 308
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
minLength: 1
For additional Type information, please refer to PartyIdentification8 p.358 in 'Message Item Types' section.
Page 309
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 310
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 311
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 312
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
contain holdings in any investment fund or investment fund class managed (or distributed) by the fund
manager, within the same fund family.
Type: This message item is composed of the following CashAccount7 element(s):
Or Message Item <XML Tag> Mult. Represent./
Type
Identification <Id> [1..1]
Type <Tp> [0..1]
Currency <Ccy> [0..1] Code
Name <Nm> [0..1] Text
For additional Type information, please refer to CashAccount7 p.335 in 'Message Item Types' section.
Business Example
Narrative
Besides providing an intraday AccountReport at 12.30 PM (see example with AccountReport), AAAA Banken and
Finpetrol have agreed on a credit notification service, for all incoming credits above a certain threshold. On 18 October,
at 1.20 PM, AAAASESS sends a DebitCreditNotification to Company Finpetrol, to advise Finpetrol of an incoming credit
on its account.
Business Description
Page 313
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
Page 314
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
XML Instance
Page 315
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
MX camt.054.001.01 BankToCustomerDebitCreditNotificationV01
<SubFmlyCd>0005</SubFmlyCd>
</Fmly>
</Domn>
</BkTxCd>
<TxDtls>
<Refs>
<EndToEndId>MUELL/FINP/RA12345</EndToEndId>
</Refs>
<RltdPties>
<Dbtr>
<Nm>MUELLER</Nm>
<PstlAdr>
<Ctry>DE</Ctry>
</PstlAdr>
</Dbtr>
</RltdPties>
</TxDtls>
</Ntry>
</Ntfctn>
</BkToCstmrDbtCdtNtfctnV01>
</Document>
Page 316
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
2 Date Time
2.1 ISODate
2.2 ISODateTime
2.3 ISOTime
2.4 ISOYear
3 Identifier
3.1 AustrianBankleitzahlIdentifier
3.2 BBANIdentifier
3.3 BEIIdentifier
3.4 BICIdentifier
3.5 BelgianIdentifier
3.6 BloombergIdentifier
3.7 CHIPSParticipantIdentifier
3.8 CHIPSUniversalIdentifier
3.9 CUSIPIdentifier
3.10 CanadianPaymentsARNIdentifier
3.11 ConsolidatedTapeAssociationIdentifier
3.12 CountryCode
3.13 CurrencyCode
3.14 DunsIdentifier
3.15 DutchIdentifier
3.16 EANGLNIdentifier
3.17 EuroclearClearstreamIdentifier
3.18 ExtensiveBranchNetworkIdentifier
3.19 ExternalBankTransactionDomainCode
3.20 ExternalBankTransactionFamilyCode
3.21 ExternalBankTransactionSubFamilyCode
3.22 ExternalClearingSystemMemberCode
3.23 ExternalPurposeCode
3.24 FedwireRoutingNumberIdentifier
3.25 GermanBankleitzahlIdentifier
3.26 HellenicBankIdentificationCodeIdentifier
3.27 HongKongBankIdentifier
3.28 IBANIdentifier
3.29 IBEIIdentifier
3.30 ISINIdentifier
3.31 IndianFinancialSystemCodeIdentifier
3.32 IrishNSCIdentifier
3.33 ItalianDomesticIdentifier
Page 317
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
3.34 LanguageCode
3.35 MICIdentifier
3.36 NationalityCode
3.37 NewZealandNCCIdentifier
3.38 PolishNationalClearingCodeIdentifier
3.39 PortugueseNCCIdentifier
3.40 QUICKIdentifier
3.41 RICIdentifier
3.42 RussianCentralBankIdentificationCodeIdentifier
3.43 SEDOLIdentifier
3.44 SicovamIdentifier
3.45 SmallNetworkIdentifier
3.46 SouthAfricanNCCIdentifier
3.47 SpanishDomesticInterbankingIdentifier
3.48 SwissBCIdentifier
3.49 SwissSICIdentifier
3.50 TickerIdentifier
3.51 UKDomesticSortCodeIdentifier
3.52 UPICIdentifier
3.53 ValorenIdentifier
3.54 WertpapierIdentifier
5 Rate
5.1 BaseOneRate
5.2 PercentageRate
6 Text
6.1 Max1025Text
6.2 Max105Text
6.3 Max128Text
6.4 Max140Text
6.5 Max15NumericText
6.6 Max15PlusSignedNumericText
6.7 Max16Text
6.8 Max256Text
6.9 Max34Text
6.10 Max350Text
6.11 Max35Text
6.12 Max3NumericText
6.13 Max4AlphaNumericText
6.14 Max500Text
6.15 Max5NumericText
6.16 Max6Text
6.17 Max70Text
Page 318
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
1.2 ImpliedCurrencyAndAmount
Definition: Number of monetary units specified in a currency where the unit of currency is implied by
the context and compliant with ISO 4217. The decimal separator is a dot.
Note: a zero amount is considered a positive amount.
Format: fractionDigits: 5
minInclusive: 0
totalDigits: 18
Example: 500000
2 Date Time
2.1 ISODate
Definition: A particular point in the progression of time in a calendar year expressed in the YYYY-
MM-DD format. This representation is defined in "XML Schema Part 2: Datatypes Second
Edition - W3C Recommendation 28 October 2004" which is aligned with ISO 8601.
Example: 2002-02-25
2.2 ISODateTime
Definition: A particular point in the progression of time defined by a mandatory date and a mandatory
time component, expressed in either UTC time format (YYYY-MM-DDThh:mm:ss.sssZ),
local time with UTC offset format (YYYY-MM-DDThh:mm:ss.sss+/-hh:mm), or local time
format (YYYY-MM-DDThh:mm:ss.sss). These representations are defined in "XML
Schema Part 2: Datatypes Second Edition - W3C Recommendation 28 October 2004" which
is aligned with ISO 8601.
Note on the time format:
1) beginning / end of calendar day
00:00:00 = the beginning of a calendar day
Page 319
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
2.3 ISOTime
Definition: A particular point in the progression of time in a calendar day expressed in either UTC time
format (hh:mm:ss.sssZ), local time with UTC offset format (hh:mm:ss.sss+/-hh:mm), or
local time format (hh:mm:ss.sss). These representations are defined in "XML Schema Part
2: Datatypes Second Edition - W3C Recommendation 28 October 2004" which is aligned
with ISO 8601.
Note on the time format:
1) beginning / end of calendar day
00:00:00 = the beginning of a calendar day
24:00:00 = the end of a calendar day
2) fractions of second in time format
Decimal fractions of seconds may be included. In this case, the involved parties shall agree
on the maximum number of digits that are allowed.
Example: 16:34:44
2.4 ISOYear
Definition: Year represented by YYYY (ISO 8601)
Example: 2000
3 Identifier
3.1 AustrianBankleitzahlIdentifier
Definition: Austrian Bankleitzahl. Identifies Austrian financial institutions on the Austrian national
clearing system.
Format: AT[0-9]{5,5}
Example: AT12345
3.2 BBANIdentifier
Definition: Basic Bank Account Number (BBAN). Identifier used nationally by financial institutions,
ie, in individual countries, generally as part of a National Account Numbering Scheme(s),
which uniquely identifies the account of a customer.
Format: [a-zA-Z0-9]{1,30}
Example: BARC12345612345678
3.3 BEIIdentifier
Definition: Business Entity Identifier. Code allocated to non-financial institutions by the ISO 9362
Registration Authority. The Business Entity Identifier (BEI) has the same format as the BIC
code (8 up to 11 characters) as stipulated in the standard ISO 9362 Banking (Banking
Telecommunication Messages, Bank Identifier Codes, BIC).
Page 320
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Format: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}
Rule(s): BEI
Only Business Entity Identifiers registered with the ISO 9362 Registration Authority and
consisting of 8 or 11 contiguous characters comprising the first three or all four of the
following components: BANK CODE, COUNTRY CODE, LOCATION CODE,
BRANCH CODE, are valid BEIs.
Example: USINFRPP
3.4 BICIdentifier
Definition: Bank Identifier Code. code allocated to a financial institution by a Registration Authority
under an international identification scheme, as described in the latest edition of the
international standard ISO 9362 "Banking - Banking telecommunication messages - Bank
identifier codes".
Format: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}
Rule(s): BIC
Valid BICs are registered with the ISO 9362 Registration Authority, and consist of eight
(8) or eleven (11) contiguous characters comprising the first three or all four of the following
components: BANK CODE, COUNTRY CODE, LOCATION CODE, BRANCH CODE.
The bank code, country code and location code are mandatory, while the branch code is
optional.
Example: CHASUS33
3.5 BelgianIdentifier
Definition: Identifier for Belgian securities.
Example: 359203
3.6 BloombergIdentifier
Definition: An identifier of a security assigned by the Bloomberg organisation.
Format: maxLength: 35
minLength: 1
Example: GGF.FP
3.7 CHIPSParticipantIdentifier
Definition: (United States) Clearing House Interbank Payment System (CHIPS) Participant Identifier
(ID). Identifies financial institutions participating on CHIPS. The CHIPS Participant ID is
assigned by the New York Clearing House.
Format: CP[0-9]{4,4}
Example: CP1234
3.8 CHIPSUniversalIdentifier
Definition: (United States) Clearing House Interbank Payments System (CHIPS) Universal
Identification (UID). Identifies entities that own accounts at CHIPS participating financial
Page 321
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
institutions, through which CHIPS payments are effected. The CHIPS UID is assigned by
the New York Clearing House.
Format: CH[0-9]{6,6}
Example: CH123456
3.9 CUSIPIdentifier
Definition: Committee on Uniform Securities and Identification Procedures (CUSIP). The standards
body that created and maintains the securities classification system in the US. Non-US
securities have a similar number called the CINS number.
Example: 3134A33L8
3.10 CanadianPaymentsARNIdentifier
Definition: Canadian Payments Association Routing Number. Identifies Canadian financial institutions
on the Canadian national clearing system.
Format: CA[0-9]{9,9}
Example: CA123456789
3.11 ConsolidatedTapeAssociationIdentifier
Definition: Identifier of a security assigned by the Consolidated Tape Association.
Format: maxLength: 35
minLength: 1
Example: 483894
3.12 CountryCode
Definition: Code to identify a country, a dependency, or another area of particular geopolitical interest,
on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
Format: [A-Z]{2,2}
Rule(s): Country
The code is checked against the list of country names obtained from the United Nations
(ISO 3166, Alpha-2 code).
Example: BE
3.13 CurrencyCode
Definition: Code allocated to a currency, by a maintenance agency, under an international identification
scheme as described in the latest edition of the international standard ISO 4217 "Codes for
the representation of currencies and funds". Valid currency codes are registered with the
ISO 4217 Maintenance Agency, and consist of three contiguous letters.
Format: [A-Z]{3,3}
Rule(s): ValidationByTable
Example: AWG
Page 322
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
3.14 DunsIdentifier
Definition: Data Universal Numbering System. A unique identification number provided by Dun &
Bradstreet to identify an organization.
Format: [0-9]{9,9}
Example: 578942538
3.15 DutchIdentifier
Definition: Identifier for Dutch securities.
Example: 234123
3.16 EANGLNIdentifier
Definition: Global Location Number. A non-significant reference number used to identify legal entities,
functional entities or physical entities according to the European Association for Numbering
(EAN) numbering scheme rules. The number is used to retrieve the detailed information
linked to it.
Format: [0-9]{13,13}
Example: 7265658971233
3.17 EuroclearClearstreamIdentifier
Definition: Identifier of securities issued in Luxembourg. The common code is a 9-digit code that
replaces the CEDEL (Clearstream) and Euroclear codes.
Format: maxLength: 12
minLength: 1
Example: 12197
3.18 ExtensiveBranchNetworkIdentifier
Definition: The extensive branch network list of the Australian Bank State Branch (BSB) Code. The
codes are used for identifying Australian financial institutions, as assigned by the Australian
Payments Clearing Association (APCA).
Format: AU[0-9]{6,6}
Example: AU123456
3.19 ExternalBankTransactionDomainCode
Definition: Specifies the external domain code of the bank transaction code in the format of character
string with a maximum length of 4 characters.
The list of valid codes is an external code list published separately.
Format: maxLength: 4
minLength: 1
Example: D001
Page 323
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
3.20 ExternalBankTransactionFamilyCode
Definition: Specifies the external family code of the bank transaction code in the format of character
string with a maximum length of 4 characters.
The list of valid codes is an external code list published separately, and is a sub-list of the
bank transaction domain list.
Format: maxLength: 4
minLength: 1
Example: F001
3.21 ExternalBankTransactionSubFamilyCode
Definition: Specifies the external sub-family code of the bank transaction code in the format of character
string with a maximum length of 4 characters.
The list of valid codes is an external code list published separately, and is a sub-list of the
bank transaction family code list.
Format: maxLength: 4
minLength: 1
Example: S001
3.22 ExternalClearingSystemMemberCode
Definition: Specifies the external clearing system member code in the format of character string with
a maximum length of 35 characters.
The list of valid codes is an external code list published separately.
Format: maxLength: 35
minLength: 1
Example: External Member Code 1
3.23 ExternalPurposeCode
Definition: Specifies the external purpose code in the format of character string with a maximum length
of 35 characters.
The list of valid codes is an external code list published separately.
Format: maxLength: 35
minLength: 1
Example: External Purpose Code 1
3.24 FedwireRoutingNumberIdentifier
Definition: Fedwire Routing Number. Identifies financial institutions, in the US, on the FedWire
system. The routing number is assigned by the American Bankers Association (ABA).
Format: FW[0-9]{9,9}
Example: FW123456789
Page 324
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
3.25 GermanBankleitzahlIdentifier
Definition: German Bankleitzahl. Identifies German financial institutions on the German national
clearing systems.
Format: BL[0-9]{8,8}
Example: BL12345678
3.26 HellenicBankIdentificationCodeIdentifier
Definition: Hellenic Bank Identification Code Identifier. Identifies Greek financial institutions on the
greek national clearing system.
Format: GR[0-9]{7,7}
Example: GR1234567
3.27 HongKongBankIdentifier
Definition: Hong Kong Bank Code. Identifies Hong Kong financial institutions on the Hong Kong local
clearing system.
Format: HK[0-9]{3,3}
Example: HK123
3.28 IBANIdentifier
Definition: An identifier used internationally by financial institutions to uniquely identify the account
of a customer at a financial institution, as described in the latest edition of the international
standard ISO 13616. "Banking and related financial services - International Bank Account
Number (IBAN)".
Format: [a-zA-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}
Rule(s): IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits
and BBAN.
Example: AT611904300234573201
3.29 IBEIIdentifier
Definition: International Business Entity Identifier to uniquely identify business entities playing a role
in the lifecycle of and events related to a financial instrument. (tentative - to be confirmed).
Format: [A-Z]{2,2}[B-DF-HJ-NP-TV-XZ0-9]{7,7}[0-9]{1,1}
Example: DEXBC823N0
3.30 ISINIdentifier
Definition: International Securities Identification Number (ISIN). A numbering system designed by
the United Nation's International Organisation for Standardisation (ISO). The ISIN is
composed of a 2-character prefix representing the country of issue, followed by the national
security number (if one exists), and a check digit. Each country has a national numbering
agency that assigns ISIN numbers for securities in that country.
Format: [A-Z0-9]{12,12}
Page 325
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Example: US3134A33L82
3.31 IndianFinancialSystemCodeIdentifier
Definition: Indian Financial System Code Identifier. Identifies Indian financial institutions on the Indian
national clearing system.
Format: IN[a-zA-Z0-9]{11,11}
Example: IN12azBX12345
3.32 IrishNSCIdentifier
Definition: Irish National Sorting Code. Identifies Irish financial institutions on the Irish national
clearing system.
Format: IE[0-9]{6,6}
Example: IE123456
3.33 ItalianDomesticIdentifier
Definition: Italian Domestic Identification Code. Identifies Italian financial institutions on the Italian
national clearing system. The code is assigned by the Associazione Bancaria Italiana (ABI).
Format: IT[0-9]{10,10}
Example: IT1234567890
3.34 LanguageCode
Definition: Specifies a language.
Rule(s): ValidationByTable
Example: ENG
3.35 MICIdentifier
Definition: Market Identifier Code. The identification of a financial market, as stipulated in the norm
ISO 10383 'Codes for exchanges and market identifications'.
Format: [A-Z0-9]{4,4}
Example: XTKS
3.36 NationalityCode
Definition: Specifies the country where a person was born or is naturalised.
Rule(s): ValidationByTable
Example: US
3.37 NewZealandNCCIdentifier
Definition: New Zealand Bank/Branch Code. Identifies New Zealand institutions on the New Zealand
national clearing system. The code is assigned by the New Zealand Bankers' Association
(NZBA).
Format: NZ[0-9]{6,6}
Page 326
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Example: NZ123456
3.38 PolishNationalClearingCodeIdentifier
Definition: Polish National Clearing Code Identifier. Identifies Polish financial institutions on the
Polish national clearing system.
Format: PL[0-9]{8,8}
Example: PL12345678
3.39 PortugueseNCCIdentifier
Definition: Portuguese National Clearing Code. Identifies Portuguese financial institutions on the
Portuguese national clearing system.
Format: PT[0-9]{8,8}
Example: PT12345678
3.40 QUICKIdentifier
Definition: Identifier of a security assigned by the Japanese QUICK identification scheme for financial
instruments.
Example: 97334
3.41 RICIdentifier
Definition: Reuters Identification Code (RIC). A numbering system used within the Reuters system to
identify instruments worldwide. The RIC contains an X-character market specific code (can
be the CUSIP or EPIC codes) followed by a full stop, then the two-digit ISO country code,
eg, IBM in UK is IBM.UK.
Format: maxLength: 35
minLength: 1
Example: TDVd.CR
3.42 RussianCentralBankIdentificationCodeIdentifier
Definition: Russian Central Bank Identification Code. Identifies Russian financial institutions on the
Russian national clearing system.
Format: RU[0-9]{9,9}
Example: RU123456789
3.43 SEDOLIdentifier
Definition: Stock Exchange Daily Official List (SEDOL) number. A code used by the London Stock
Exchange to identify foreign stocks, especially those that aren't actively traded in the US
and don't have a CUSIP number.
Example: 5719210
3.44 SicovamIdentifier
Definition: Identifier for French securities assigned by the Societe Interprofessionnelle Pour La
Compensation des Valeurs Mobilieres in France. The Sicovam is composed of 5-digits.
Page 327
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Example: 12777
3.45 SmallNetworkIdentifier
Definition: The small network list of the Australian Bank State Branch (BSB) Code. The codes are
used for identifying Australian financial institutions, as assigned by the Australian Payments
Clearing Association (APCA).
Format: AU[0-9]{6,6}
Example: AU123456
3.46 SouthAfricanNCCIdentifier
Definition: South African National Clearing Code (NCC). Identifies South African financial institutions
on the South African national clearing system. The code is assigned by the South African
Bankers Services Company Ltd. (BankServ).
Format: ZA[0-9]{6,6}
Example: ZA123456
3.47 SpanishDomesticInterbankingIdentifier
Definition: Spanish Domestic Interbanking Code. Identifies Spanish financial institutions on the
Spanish national clearing system. The code is assigned by the Centro de Cooperacion
Interbancaria (CCI).
Format: ES[0-9]{8,9}
Example: ES12345678
3.48 SwissBCIdentifier
Definition: Swiss Bank Code. Identifies Swiss institutions on the Swiss national clearing system.
Format: SW[0-9]{3,5}
Example: SW123
3.49 SwissSICIdentifier
Definition: Swiss Interbank Clearing (SIC) Code. Identifies Swiss financial institutions domestically,
on the Swiss national clearing system.
Format: SW[0-9]{6,6}
Example: SW123456
3.50 TickerIdentifier
Definition: Letters that identify a stock traded on a stock exchange. The Ticker Symbol is a short and
convenient way of identifying a stock, eg, RTR.L for Reuters quoted in London.
Format: maxLength: 35
minLength: 1
Example: SOL
Page 328
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
3.51 UKDomesticSortCodeIdentifier
Definition: United Kingdom (UK) Sort Code. Identifies British financial institutions on the British
national clearing systems. The sort code is assigned by the Association for Payments and
Clearing Services (APACS).
Format: SC[0-9]{6,6}
Example: SC123456
3.52 UPICIdentifier
Definition: Universal Payment Identification Code (UPIC). Identifier used by the New York Clearing
House to mask confidential data, such as bank accounts and bank routing numbers. UPIC
numbers remain with business customers, regardless of banking relationship changes.
Format: [0-9]{8,17}
Example: 12345678
3.53 ValorenIdentifier
Definition: Identifier for Swiss securities assigned by Telekurs Financial, the Swiss numbering agency.
Example: 832614
3.54 WertpapierIdentifier
Definition: Wertpapier Kenn-nummer. A number issued in Germany by the Wertpapier
Mitteilungen.The Wertpapier Kenn-nummer, sometimes called WPK, contains 6-digits, but
no check digit. There are different ranges of numbers representing different classes of
securities.
Example: 911958
4.2 Number
Definition: Number of objects represented as an integer.
Format: fractionDigits: 0
totalDigits: 18
Example: 123456789012345678
5 Rate
5.1 BaseOneRate
Definition: Rate expressed as a decimal, eg, 0.7 is 7/10 and 70%.
Page 329
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Format: fractionDigits: 10
totalDigits: 11
Example: 0.60
5.2 PercentageRate
Definition: Rate expressed as a percentage, ie, in hundredths, eg, 0.7 is 7/10 of a percent, and 7.0 is 7%.
Format: fractionDigits: 10
totalDigits: 11
Example: 35
6 Text
6.1 Max1025Text
Definition: Specifies a character string with a maximum length of 1025 characters.
Format: maxLength: 1025
minLength: 1
Example: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789
6.2 Max105Text
Definition: Specifies a character string with a maximum length of 105 characters.
Format: maxLength: 105
minLength: 1
Example: azefgvgldfpgtvcvlmgovl;v ; :B;lgkdfwxcvljfqsifj
6.3 Max128Text
Definition: Specifies a character string with a maximum length of 128 characters.
Format: maxLength: 128
minLength: 1
Example: A string value of maximum 128 characters.
6.4 Max140Text
Definition: Specifies a character string with a maximum length of 140 characters.
Format: maxLength: 140
minLength: 1
Example: ABCDEFGHIJKLMNOPQRST1234567890123456789012345678901234567890123456
789012345678901234567890123456789012345678901234567890123456789012345678
90
6.5 Max15NumericText
Definition: Specifies a numeric string with a maximum length of 15 digits.
Format: [0-9]{1,15}
Example: 458793625148975
Page 330
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
6.6 Max15PlusSignedNumericText
Definition: Specifies a numeric string with a maximum length of 15 digits and may be prefixed with a
plus sign.
Format: [+]{0,1}[0-9]{1,15}
Example: +2450
6.7 Max16Text
Definition: Specifies a character string with a maximum length of 16 characters.
Format: maxLength: 16
minLength: 1
Example: ABCdEFghIJKLMNO?
6.8 Max256Text
Definition: Specifies a character string with a maximum length of 256 characters.
Format: maxLength: 256
minLength: 1
Example: ABCDEFGHIJKLMNOPQRST1234567890123456789012345678901234567890123456
789012345678901234567890123456789012345678901234567890123456789012345678
90
6.9 Max34Text
Definition: Specifies a character string with a maximum length of 34 characters.
Format: maxLength: 34
minLength: 1
Example: ABCDEFGHIJKLMNOPQRST12345678901234
6.10 Max350Text
Definition: Specifies a character string with a maximum length of 350 characters.
Format: maxLength: 350
minLength: 1
Example: 123456789012345678901234567890123456789012345678901234567890123456789012
345678901234567890123456789012345678901234567890123456789012345678901234
567890123456789012345678901234567890123456789012345678901234567890123456
789012345678901234567890123456789012345678901234567890123456789012345678
90123456789012345678901234567890123456789012345678901234567890
6.11 Max35Text
Definition: Specifies a character string with a maximum length of 35 characters.
Format: maxLength: 35
minLength: 1
Example: ABCDEFGHIJKLMNOPQRST123456789012345
Page 331
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
6.12 Max3NumericText
Definition: Specifies a numeric string with a maximum length of 3 digits.
Format: [0-9]{1,3}
Example: 003
6.13 Max4AlphaNumericText
Definition: Specifies an alphanumeric string with a maximum length of 4 characters.
Format: [a-zA-Z0-9]{1,4}
Example: aBc9
6.14 Max500Text
Definition: Specifies a character string with a maximum length of 350 characters.
Format: maxLength: 500
minLength: 1
Example: 123456789012345678901234567890123456789012345678901234567890123456789012
345678901234567890123456789012345678901234567890123456789012345678901234
567890123456789012345678901234567890123456789012345678901234567890123456
789012345678901234567890123456789012345678901234567890123456789012345678
901234567890123456789012345678901234567890123456789012345678901234567890
123456789012345678901234567890123456789012345678901234567890123456789012
34567890123456789012345678901234567890123456789012345678901234567890
6.15 Max5NumericText
Definition: Specifies a numeric string with a maximum length of 5 digits.
Format: [0-9]{1,5}
Example: 1
6.16 Max6Text
Definition: Specifies a character string with a maximum length of 6 characters.
Format: maxLength: 6
minLength: 1
Example: ABCDEF
6.17 Max70Text
Definition: Specifies a character string with a maximum length of 70characters.
Format: maxLength: 70
minLength: 1
Example: A string value of maximum 70 characters.
Page 332
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
End Points
End Points Index
1 Account identification
1.1 AccountIdentification3Choice
1.2 CashAccount7
2 Amount range
2.1 CurrencyAndAmountRange
3 CurrencyExchange
3.1 CurrencyExchange3
4 Date time
4.1 DateAndDateTimeChoice
7 Party identification
7.1 PartyIdentification8
8 Postal address
8.1 PostalAddress1
9 Securities quantity
9.1 FinancialInstrumentQuantityChoice
10 Tax
10.1 TaxInformation2
Page 333
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 334
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
1.2 CashAccount7
CashAccount7 is used in message BankToCustomerAccountReportV01 p.7, p.13, p.13, p.16, message
BankToCustomerDebitCreditNotificationV01 p.222, p.228, p.228, p.231, message BankToCustomerStatementV01
p.114, p.120, p.120, p.123.
Page 335
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 336
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 337
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Usage: Currency should only be used in case one and the same account number covers several currencies
and the initiating party needs to identify which currency needs to be used for settlement on the account.
Data Type: CurrencyCode
Format: [A-Z]{3,3}
Rule(s): ValidationByTable
Usage : the account name is different from the account owner name. The account name is used in certain
user communities to provide a means of identifying the account, in addition to the account owner's identity
and the account number.
Data Type: Max70Text
Format: maxLength: 70
minLength: 1
Page 338
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
2 Amount range
2.1 CurrencyAndAmountRange
CurrencyAndAmountRange is used in message BankToCustomerAccountReportV01 p.7, p.11, p.13, message
BankToCustomerDebitCreditNotificationV01 p.225, p.227, message BankToCustomerStatementV01 p.114, p.118,
p.120.
Page 339
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 340
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 341
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 342
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
3 CurrencyExchange
3.1 CurrencyExchange3
CurrencyExchange3 is used in message BankToCustomerAccountReportV01 p.10, p.10, p.10, p.10, p.10, p.12, p.12,
p.12, p.12, p.12, message BankToCustomerDebitCreditNotificationV01 p.224, p.224, p.224, p.224, p.225, p.226,
p.226, p.226, p.226, p.226, message BankToCustomerStatementV01 p.117, p.117, p.117, p.117, p.117, p.119, p.119,
p.119, p.119, p.119.
Page 343
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Usage: ExchangeRate expresses the ratio between UnitCurrency and QuotedCurrency (ExchangeRate =
UnitCurrency/QuotedCurrency).
Data Type: BaseOneRate
Format: fractionDigits: 10
totalDigits: 11
Page 344
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
4 Date time
4.1 DateAndDateTimeChoice
DateAndDateTimeChoice is used in message BankToCustomerAccountReportV01 p.8, p.9, p.9, message
BankToCustomerDebitCreditNotificationV01 p.223, p.223, message BankToCustomerStatementV01 p.115, p.116,
p.116.
Definition: Time span defined by a start date and time, and an end date and time.
Type: The following DateTimePeriodDetails element(s) must be used:
Ref Or Message Item <XML Tag> Mult. Represent./
Type
5.1.0 FromDateTime <FrDtTm> [1..1] DateTime
5.1.1 ToDateTime <ToDtTm> [1..1] DateTime
Page 345
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Definition: Unique and unambiguous identifier of a financial institution or a branch of a financial institution, as assigned
under an internationally recognised or proprietary identification scheme.
Type: The following BranchAndFinancialInstitutionIdentification3 element(s) must be used:
Ref Or Message Item <XML Tag> Mult. Represent./
Type
6.1.0 FinancialInstitutionIdentification <FinInstnId> [1..1]
6.1.1 {Or BIC <BIC> [1..1] Identifier
6.1.2 Or ClearingSystemMemberIdentification <ClrSysMmbId> [1..1]
6.1.3 {{Or Identification <Id> [1..1] Code
6.1.4 Or}} Proprietary <Prtry> [1..1] Text
6.1.5 Or NameAndAddress <NmAndAdr> [1..1]
6.1.6 Name <Nm> [1..1] Text
6.1.7 PostalAddress <PstlAdr> [1..1]
6.1.8 AddressType <AdrTp> [0..1] Code
6.1.9 AddressLine <AdrLine> [0..5] Text
6.1.10 StreetName <StrtNm> [0..1] Text
6.1.11 BuildingNumber <BldgNb> [0..1] Text
6.1.12 PostCode <PstCd> [0..1] Text
6.1.13 TownName <TwnNm> [0..1] Text
6.1.14 CountrySubDivision <CtrySubDvsn> [0..1] Text
6.1.15 Country <Ctry> [1..1] Code
6.1.16 Or ProprietaryIdentification <PrtryId> [1..1]
6.1.17 Identification <Id> [1..1] Text
6.1.18 Issuer <Issr> [0..1] Text
6.1.19 Or} CombinedIdentification <CmbndId> [1..1]
Page 346
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 347
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 348
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 349
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 350
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 351
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 352
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 353
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 354
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 355
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Usage : this component should be used in case the identification information in the financial institution
component does not provide identification up to branch level.
Type: This message item is composed of the following BranchData element(s):
Ref Or Message Item <XML Tag> Mult. Represent./
Type
6.1.38 Identification <Id> [0..1] Text
6.1.39 Name <Nm> [0..1] Text
6.1.40 PostalAddress <PstlAdr> [0..1]
Page 356
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 357
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
7 Party identification
7.1 PartyIdentification8
PartyIdentification8 is used in message BankToCustomerAccountReportV01 p.6, p.7, p.13, p.13, p.13, p.13, p.13,
p.13, p.13, p.15, p.15, p.16, message BankToCustomerDebitCreditNotificationV01 p.222, p.222, p.227, p.227, p.228,
p.228, p.228, p.228, p.228, p.229, p.229, p.230, message BankToCustomerStatementV01 p.114, p.114, p.120, p.120,
p.120, p.120, p.120, p.120, p.120, p.122, p.122, p.123.
Page 358
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 359
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 360
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 361
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 362
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 363
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Definition: (United States) Clearing House Interbank Payments System (CHIPS) Universal Identification (UID) -
identifies entities that own accounts at CHIPS participating financial institutions, through which CHIPS
payments are effected. The CHIPS UID is assigned by the New York Clearing House.
Data Type: CHIPSUniversalIdentifier
Format: CH[0-9]{6,6}
Page 364
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 365
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
minLength: 1
Page 366
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 367
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 368
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
8 Postal address
8.1 PostalAddress1
PostalAddress1 is used in message BankToCustomerAccountReportV01 p.14, message
BankToCustomerDebitCreditNotificationV01 p.228, message BankToCustomerStatementV01 p.121.
Definition: Information that locates and identifies a specific address, as defined by postal services.
Type: The following PostalAddress1 element(s) must be used:
Ref Or Message Item <XML Tag> Mult. Represent./
Type
8.1.0 AddressType <AdrTp> [0..1] Code
8.1.1 AddressLine <AdrLine> [0..5] Text
8.1.2 StreetName <StrtNm> [0..1] Text
8.1.3 BuildingNumber <BldgNb> [0..1] Text
8.1.4 PostCode <PstCd> [0..1] Text
8.1.5 TownName <TwnNm> [0..1] Text
8.1.6 CountrySubDivision <CtrySubDvsn> [0..1] Text
8.1.7 Country <Ctry> [1..1] Code
Page 369
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Definition: Information that locates and identifies a specific address, as defined by postal services, that is presented in
free format text.
Data Type: Max70Text
Format: maxLength: 70
minLength: 1
Page 370
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Format: [A-Z]{2,2}
Rule(s): Country
The code is checked against the list of country names obtained from the United Nations (ISO 3166, Alpha-2
code).
9 Securities quantity
9.1 FinancialInstrumentQuantityChoice
FinancialInstrumentQuantityChoice is used in message BankToCustomerAccountReportV01 p.15, message
BankToCustomerDebitCreditNotificationV01 p.230, message BankToCustomerStatementV01 p.122.
Page 371
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
minInclusive: 0
totalDigits: 18
10 Tax
10.1 TaxInformation2
TaxInformation2 is used in message BankToCustomerAccountReportV01 p.16, message
BankToCustomerDebitCreditNotificationV01 p.230, message BankToCustomerStatementV01 p.123.
Definition: Details about tax paid, or to be paid, to the government in accordance with the law, including pre-defined
parameters such as thresholds and type of account.
Type: The following TaxInformation2 element(s) must be used:
Ref Or Message Item <XML Tag> Mult. Represent./
Type
10.1.0 CreditorTaxIdentification <CdtrTaxId> [0..1] Text
10.1.1 CreditorTaxType <CdtrTaxTp> [0..1] Text
10.1.2 DebtorTaxIdentification <DbtrTaxId> [0..1] Text
10.1.3 TaxReferenceNumber <TaxRefNb> [0..1] Text
10.1.4 TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount
10.1.5 TotalTaxAmount <TtlTaxAmt> [0..1] Amount
10.1.6 TaxDate <TaxDt> [0..1] DateTime
10.1.7 TaxTypeInformation <TaxTpInf> [0..n]
10.1.8 CertificateIdentification <CertId> [0..1] Text
10.1.9 TaxType <TaxTp> [0..1]
10.1.10 CategoryDescription <CtgyDesc> [0..1] Text
10.1.11 Rate <Rate> [0..1] Rate
10.1.12 TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount
10.1.13 Amount <Amt> [0..1] Amount
Page 372
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Page 373
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Rule(s): CertificateIdentificationAndOrTaxTypeRule
If CertificateIdentification is not present, then TaxType is mandatory.
If CertificateIdentification is present, then TaxType is optional.
Page 374
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Message Item Types
Format: fractionDigits: 10
totalDigits: 11
Page 375
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Indexes
Index of Message Items
A
AcceptanceDateTime: <AccptncDtTm>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
Account: <Acct>
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
AccountServicerReference: <AcctSvcrRef>
Message BankToCustomerAccountReportV01 9, 11
Message BankToCustomerStatementV01 116, 118
Message BankToCustomerDebitCreditNotificationV01 223, 225
ActualDate: <ActlDt>
Message BankToCustomerAccountReportV01 8, 9, 9, 12
Message BankToCustomerStatementV01 115, 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226
AdditionalEntryInformation: <AddtlNtryInf>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 231
AdditionalInformation: <AddtlInf>
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
AdditionalInformationIndicator: <AddtlInfInd>
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
AdditionalNotificationInformation: <AddtlNtfctnInf>
Message BankToCustomerDebitCreditNotificationV01 231
AdditionalRemittanceInformation: <AddtlRmtInf>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
AdditionalReportInformation: <AddtlRptInf>
Message BankToCustomerAccountReportV01 16
Page 376
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
AdditionalReturnReasonInformation: <AddtlRtrRsnInf>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
AdditionalStatementInformation: <AddtlStmtInf>
Message BankToCustomerStatementV01 123
AdditionalTransactionInformation: <AddtlTxInf>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 231
Address: <Adr>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
AddressLine: <AdrLine>
346, 347, 347, 359, 369
AddressType: <AdrTp>
346, 347, 347, 359, 369
Agent: <Agt>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
AlienRegistrationNumber: <AlnRegnNb>
359
AmortisedValue: <AmtsdVal>
371
Amount: <Amt>
339, 372
Message BankToCustomerAccountReportV01 8, 8, 8, 9, 9, 9, 10, 10, 10, 10, 10, 10, 11, 11, 11, 12, 12, 12, 12, 12,
12, 13, 13
Message BankToCustomerStatementV01 115, 115, 115, 116, 116, 116, 117, 117, 117, 117, 117, 117, 118, 118, 119,
119, 119, 119, 119, 119, 119, 120, 120
Message BankToCustomerDebitCreditNotificationV01 223, 223, 224, 224, 224, 224, 224, 225, 225, 225, 225, 226,
226, 226, 226, 226, 226, 227, 227, 227
AmountDetails: <AmtDtls>
Message BankToCustomerAccountReportV01 10, 11
Message BankToCustomerStatementV01 117, 118
Message BankToCustomerDebitCreditNotificationV01 224, 226
AnnouncedPostingAmount: <AnncdPstngAmt>
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Page 377
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Availability: <Avlbty>
Message BankToCustomerAccountReportV01 8, 9, 9, 12
Message BankToCustomerStatementV01 115, 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 223, 226
B
Balance: <Bal>
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
BankPartyIdentification: <BkPtyId>
359
BankTransactionCode: <BkTxCd>
Message BankToCustomerAccountReportV01 8, 9, 12
Message BankToCustomerStatementV01 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226
Batch: <Btch>
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
BBAN: <BBAN>
334, 335
Bearer: <Br>
Message BankToCustomerAccountReportV01 11, 13
Message BankToCustomerStatementV01 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
BEI: <BEI>
359
BIC: <BIC>
346, 347, 359
BirthDate: <BirthDt>
359
BookingDate: <BookgDt>
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
BoundaryAmount: <BdryAmt>
339, 339, 339, 339
BranchIdentification: <BrnchId>
Page 378
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
347
BuildingNumber: <BldgNb>
346, 347, 347, 359, 369
C
CategoryDescription: <CtgyDesc>
372
CertificateIdentification: <CertId>
372
Charges: <Chrgs>
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 225, 227
ChequeNumber: <ChqNb>
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
CHIPSUniversalIdentification: <USCHU>
359
CityOfBirth: <CityOfBirth>
359
ClearingSystemMemberIdentification: <ClrSysMmbId>
346, 347
ClearingSystemReference: <ClrSysRef>
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
Code: <Cd>
335
Message BankToCustomerAccountReportV01 7, 7, 8, 9, 9, 9, 9, 9, 10, 10, 11, 12, 12, 12, 12, 13, 14, 14, 15, 16, 16,
16, 16, 16
Message BankToCustomerStatementV01 114, 114, 115, 116, 116, 116, 116, 116, 117, 117, 118, 119, 119, 119, 120,
120, 121, 121, 122, 123, 123, 123, 123, 123
Message BankToCustomerDebitCreditNotificationV01 222, 223, 223, 223, 224, 224, 224, 225, 225, 226, 227, 227,
227, 227, 228, 229, 229, 230, 230, 230, 230, 230
CombinedIdentification: <CmbndId>
346
CommissionWaiverIndicator: <ComssnWvrInd>
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Page 379
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
ContractIdentification: <CtrctId>
343
CopyDuplicateIndicator: <CpyDplctInd>
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
CorporateAction: <CorpActn>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
CounterValueAmount: <CntrValAmt>
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
Country: <Ctry>
346, 347, 347, 359, 369
CountryOfBirth: <CtryOfBirth>
359
CountryOfResidence: <CtryOfRes>
360
CountrySubDivision: <CtrySubDvsn>
346, 347, 347, 359, 369
CreationDateTime: <CreDtTm>
Message BankToCustomerAccountReportV01 6, 7
Message BankToCustomerStatementV01 113, 114
Message BankToCustomerDebitCreditNotificationV01 222, 222
CreditDebitIndicator: <CdtDbtInd>
339
Message BankToCustomerAccountReportV01 8, 8, 8, 8, 9, 9, 9, 11, 12, 13
Message BankToCustomerStatementV01 115, 115, 115, 116, 116, 116, 116, 118, 119, 120
Message BankToCustomerDebitCreditNotificationV01 222, 223, 223, 223, 224, 225, 226, 227
CreditLine: <CdtLine>
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
CreditNoteAmount: <CdtNoteAmt>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
Page 380
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Creditor: <Cdtr>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
CreditorAccount: <CdtrAcct>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
CreditorAgent: <CdtrAgt>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
CreditorReference: <CdtrRef>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
CreditorReferenceInformation: <CdtrRefInf>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
CreditorReferenceType: <CdtrRefTp>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
CreditorTaxIdentification: <CdtrTaxId>
372
CreditorTaxType: <CdtrTaxTp>
372
Currency: <Ccy>
335, 339
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
CurrencyExchange: <CcyXchg>
Message BankToCustomerAccountReportV01 10, 10, 10, 10, 10, 12, 12, 12, 12, 12
Message BankToCustomerStatementV01 117, 117, 117, 117, 117, 119, 119, 119, 119, 119
Message BankToCustomerDebitCreditNotificationV01 224, 224, 224, 224, 225, 226, 226, 226, 226, 226
CustomerNumber: <CstmrNb>
359
Page 381
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
D
Date: <Dt>
345
Message BankToCustomerAccountReportV01 8, 8, 9, 9, 12, 15
Message BankToCustomerStatementV01 115, 115, 116, 116, 119, 122
Message BankToCustomerDebitCreditNotificationV01 223, 223, 226, 229
DateAndPlaceOfBirth: <DtAndPlcOfBirth>
359
DateTime: <DtTm>
345
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
DealPrice: <DealPric>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
Debtor: <Dbtr>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 227
DebtorAccount: <DbtrAcct>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
DebtorAgent: <DbtrAgt>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
DebtorTaxIdentification: <DbtrTaxId>
372
DeliveringAgent: <DlvrgAgt>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
DiscountAppliedAmount: <DscntApldAmt>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
Domain: <Domn>
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Page 382
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
DriversLicenseNumber: <DrvrsLicNb>
359
DuePayableAmount: <DuePyblAmt>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
DUNS: <DUNS>
359
E
EANGLN: <EANGLN>
359
ElectronicSequenceNumber: <ElctrncSeqNb>
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
EmployerIdentificationNumber: <MplyrIdNb>
359
EndDate: <EndDt>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
EndToEndIdentification: <EndToEndId>
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
Entry: <Ntry>
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
EqualAmount: <EQAmt>
339
ExchangeRate: <XchgRate>
343
F
FaceAmount: <FaceAmt>
Page 383
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
371
Family: <Fmly>
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 116, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226, 230
FinancialInstitutionIdentification: <FinInstnId>
346
FinancialInstrumentIdentification: <FinInstrmId>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
FromAmount: <FrAmt>
339, 339
FromDateTime: <FrDtTm>
345
FromToAmount: <FrToAmt>
339
FromToDate: <FrToDt>
Message BankToCustomerAccountReportV01 7, 7, 11, 13
Message BankToCustomerStatementV01 114, 115, 118, 120
Message BankToCustomerDebitCreditNotificationV01 222, 225, 227
G
GroupHeader: <GrpHdr>
Message BankToCustomerAccountReportV01 6
Message BankToCustomerStatementV01 113
Message BankToCustomerDebitCreditNotificationV01 221
I
IBAN: <IBAN>
334, 335
IBEI: <IBEI>
359
Identification: <Id>
334, 335, 335, 346, 346, 347, 347, 347, 359, 359, 360
Message BankToCustomerAccountReportV01 7, 7, 11, 13, 16
Message BankToCustomerStatementV01 114, 114, 118, 120, 123
Message BankToCustomerDebitCreditNotificationV01 222, 222, 225, 227, 230
IdentificationType: <IdTp>
Page 384
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
360
IdentityCardNumber: <IdntyCardNb>
359
Included: <Incl>
339, 339, 339, 339
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
InitiatingParty: <InitgPty>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 227
InstructedAmount: <InstdAmt>
Message BankToCustomerAccountReportV01 10, 11
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
InstructionIdentification: <InstrId>
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 225
InterbankSettlementDate: <IntrBkSttlmDt>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
Interest: <Intrst>
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
IntermediaryAgent1: <IntrmyAgt1>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
IntermediaryAgent2: <IntrmyAgt2>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
IntermediaryAgent3: <IntrmyAgt3>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
Invoicee: <Invcee>
Message BankToCustomerAccountReportV01 15
Page 385
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Invoicer: <Invcr>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
ISIN: <ISIN>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
Issuer: <Issr>
346, 347, 359, 360
Message BankToCustomerAccountReportV01 9, 10, 12, 14, 15, 16
Message BankToCustomerStatementV01 116, 117, 119, 121, 122, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 227, 229, 229, 230
IssuingAgent: <IssgAgt>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
L
LastPageIndicator: <LastPgInd>
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
LegalSequenceNumber: <LglSeqNb>
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
M
MandateIdentification: <MndtId>
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
MessageIdentification: <MsgId>
Message BankToCustomerAccountReportV01 6, 10, 10, 11
Message BankToCustomerStatementV01 113, 117, 117, 118
Message BankToCustomerDebitCreditNotificationV01 221, 224, 224, 225
MessageNameIdentification: <MsgNmId>
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Page 386
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
MessagePagination: <MsgPgntn>
Message BankToCustomerAccountReportV01 6
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
MessageRecipient: <MsgRcpt>
Message BankToCustomerAccountReportV01 6
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
N
Name: <Nm>
335, 346, 347, 347, 358
Message BankToCustomerAccountReportV01 7, 14
Message BankToCustomerStatementV01 114, 121
Message BankToCustomerDebitCreditNotificationV01 222, 228
NameAndAddress: <NmAndAdr>
346
NotEqualAmount: <NEQAmt>
339
Notification: <Ntfctn>
Message BankToCustomerDebitCreditNotificationV01 222
Number: <Nb>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
NumberOfDays: <NbOfDays>
Message BankToCustomerAccountReportV01 8, 9, 9, 12
Message BankToCustomerStatementV01 115, 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226
NumberOfEntries: <NbOfNtries>
Message BankToCustomerAccountReportV01 8, 8, 8, 8
Message BankToCustomerStatementV01 115, 115, 115, 115
Message BankToCustomerDebitCreditNotificationV01 222, 222, 223, 223
NumberOfTransactions: <NbOfTxs>
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
Page 387
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
O
OrganisationIdentification: <OrgId>
359
OriginalBankTransactionCode: <OrgnlBkTxCd>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
OtherIdentification: <OthrId>
360
Owner: <Ownr>
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
P
PageNumber: <PgNb>
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
Party: <Pty>
Message BankToCustomerAccountReportV01 11, 13, 13
Message BankToCustomerStatementV01 118, 120, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227, 228
PassportNumber: <PsptNb>
359
PaymentInformationIdentification: <PmtInfId>
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
PercentageRate: <PctgRate>
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
PostalAddress: <PstlAdr>
346, 347, 347, 359
PostCode: <PstCd>
346, 347, 347, 359, 369
Price: <Pric>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Page 388
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
PrivateIdentification: <PrvtId>
359
Proprietary: <Prtry>
335, 346, 347
Message BankToCustomerAccountReportV01 7, 7, 8, 9, 9, 11, 11, 12, 13, 13, 14, 14, 14, 15, 15, 15, 15, 16, 16, 16,
16
Message BankToCustomerStatementV01 114, 114, 115, 116, 117, 118, 118, 119, 120, 120, 121, 121, 121, 122, 122,
122, 122, 123, 123, 123, 123
Message BankToCustomerDebitCreditNotificationV01 222, 223, 224, 225, 226, 227, 227, 228, 228, 228, 229, 229,
229, 230, 230, 230, 230, 230, 231
ProprietaryAccount: <PrtryAcct>
334, 335
ProprietaryAmount: <PrtryAmt>
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
ProprietaryCode: <PrtryCd>
Message BankToCustomerAccountReportV01 10, 13
Message BankToCustomerStatementV01 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
ProprietaryIdentification: <PrtryId>
346, 347, 359
ProvinceOfBirth: <PrvcOfBirth>
359
Purpose: <Purp>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
Q
Quantity: <Qty>
Message BankToCustomerAccountReportV01 15, 15
Message BankToCustomerStatementV01 122, 123
Message BankToCustomerDebitCreditNotificationV01 230, 230
QuotationDate: <QtnDt>
343
R
Rate: <Rate>
Page 389
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
372
Message BankToCustomerAccountReportV01 7, 7, 10, 11, 11, 11, 13, 13, 13, 13
Message BankToCustomerStatementV01 114, 114, 118, 118, 118, 118, 120, 120, 120, 120
Message BankToCustomerDebitCreditNotificationV01 225, 225, 225, 225, 227, 227, 227, 227
Reason: <Rsn>
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 115, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
ReceivingAgent: <RcvgAgt>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
Reference: <Ref>
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
References: <Refs>
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 225
ReferredDocumentAmount: <RfrdDocAmt>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
ReferredDocumentInformation: <RfrdDocInf>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
ReferredDocumentNumber: <RfrdDocNb>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
ReferredDocumentRelatedDate: <RfrdDocRltdDt>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
ReferredDocumentType: <RfrdDocTp>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
RelatedAccount: <RltdAcct>
Message BankToCustomerAccountReportV01 7
Page 390
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
RelatedAgents: <RltdAgts>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
RelatedDates: <RltdDts>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
RelatedParties: <RltdPties>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 227
RelatedPrice: <RltdPric>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
RelatedQuantities: <RltdQties>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
RelatedRemittanceInformation: <RltdRmtInf>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
RemittanceIdentification: <RmtId>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
RemittanceInformation: <RmtInf>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
RemittanceLocationElectronicAddress: <RmtLctnElctrncAdr>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
RemittanceLocationMethod: <RmtLctnMtd>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
Page 391
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
RemittanceLocationPostalAddress: <RmtLctnPstlAdr>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
RemittedAmount: <RmtdAmt>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
Report: <Rpt>
Message BankToCustomerAccountReportV01 7
ReturnInformation: <RtrInf>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
ReturnOriginator: <RtrOrgtr>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
ReturnReason: <RtrRsn>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
ReversalIndicator: <RvslInd>
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
S
SafekeepingAccount: <SfkpgAcct>
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 231
Servicer: <Svcr>
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
SettlementPlace: <SttlmPlc>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
SocialSecurityNumber: <SclSctyNb>
Page 392
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
359
SourceCurrency: <SrcCcy>
343
StartDate: <StartDt>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
Statement: <Stmt>
Message BankToCustomerStatementV01 114
Status: <Sts>
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
StreetName: <StrtNm>
346, 347, 347, 359, 369
Structured: <Strd>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
SubFamilyCode: <SubFmlyCd>
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 117, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 227, 230
Sum: <Sum>
Message BankToCustomerAccountReportV01 8, 8, 8, 8
Message BankToCustomerStatementV01 115, 115, 115, 115
Message BankToCustomerDebitCreditNotificationV01 222, 223, 223, 223
T
TargetCurrency: <TrgtCcy>
343
Tax: <Tax>
Message BankToCustomerAccountReportV01 11, 13, 16
Message BankToCustomerStatementV01 118, 120, 123
Message BankToCustomerDebitCreditNotificationV01 225, 227, 230
TaxableBaseAmount: <TaxblBaseAmt>
372
TaxAmount: <TaxAmt>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Page 393
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
TaxDate: <TaxDt>
372
TaxIdentificationNumber: <TaxIdNb>
359, 359
TaxReferenceNumber: <TaxRefNb>
372
TaxType: <TaxTp>
372
TaxTypeInformation: <TaxTpInf>
372
TextualRate: <TxtlRate>
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
ToAmount: <ToAmt>
339, 339
ToDateTime: <ToDtTm>
345
TotalChargesAndTaxAmount: <TtlChrgsAndTaxAmt>
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 225, 227
TotalCreditEntries: <TtlCdtNtries>
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 222
TotalDebitEntries: <TtlDbtNtries>
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 223
TotalEntries: <TtlNtries>
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 222
TotalEntriesPerBankTransactionCode: <TtlNtriesPerBkTxCd>
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 223
Page 394
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
TotalNetEntryAmount: <TtlNetNtryAmt>
Message BankToCustomerAccountReportV01 8, 8
Message BankToCustomerStatementV01 115, 115
Message BankToCustomerDebitCreditNotificationV01 222, 223
TotalTaxableBaseAmount: <TtlTaxblBaseAmt>
372
TotalTaxAmount: <TtlTaxAmt>
372
TownName: <TwnNm>
346, 347, 347, 359, 369
TradeDate: <TradDt>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
TradingParty: <TradgPty>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
TransactionAmount: <TxAmt>
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
TransactionDateTime: <TxDtTm>
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
TransactionDetails: <TxDtls>
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 225
TransactionIdentification: <TxId>
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
TransactionsSummary: <TxsSummry>
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 222
Type: <Tp>
335
Page 395
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Message BankToCustomerAccountReportV01 7, 7, 8, 10, 10, 11, 11, 12, 12, 13, 13, 14, 15, 15, 15, 16
Message BankToCustomerStatementV01 114, 114, 115, 117, 117, 118, 118, 119, 120, 120, 120, 121, 122, 122, 122,
123
Message BankToCustomerDebitCreditNotificationV01 222, 225, 225, 225, 226, 226, 227, 227, 228, 228, 229, 230,
230, 230
U
UltimateCreditor: <UltmtCdtr>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
UltimateDebtor: <UltmtDbtr>
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
Unit: <Unit>
371
UnitCurrency: <UnitCcy>
343
Unstructured: <Ustrd>
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
UPIC: <UPIC>
334, 335
V
ValidityRange: <VldtyRg>
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
ValueDate: <ValDt>
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
Page 396
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<Acct>: Account
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
<AcctSvcrRef>: AccountServicerReference
Message BankToCustomerAccountReportV01 9, 11
Message BankToCustomerStatementV01 116, 118
Message BankToCustomerDebitCreditNotificationV01 223, 225
<ActlDt>: ActualDate
Message BankToCustomerAccountReportV01 8, 9, 9, 12
Message BankToCustomerStatementV01 115, 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226
<AddtlInf>: AdditionalInformation
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
<AddtlInfInd>: AdditionalInformationIndicator
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
<AddtlNtfctnInf>: AdditionalNotificationInformation
Message BankToCustomerDebitCreditNotificationV01 231
<AddtlNtryInf>: AdditionalEntryInformation
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 231
<AddtlRmtInf>: AdditionalRemittanceInformation
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<AddtlRptInf>: AdditionalReportInformation
Message BankToCustomerAccountReportV01 16
<AddtlRtrRsnInf>: AdditionalReturnReasonInformation
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
<AddtlStmtInf>: AdditionalStatementInformation
Message BankToCustomerStatementV01 123
<AddtlTxInf>: AdditionalTransactionInformation
Page 397
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 231
<Adr>: Address
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<AdrLine>: AddressLine
346, 347, 347, 359, 369
<AdrTp>: AddressType
346, 347, 347, 359, 369
<Agt>: Agent
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<AlnRegnNb>: AlienRegistrationNumber
359
<Amt>: Amount
339, 372
Message BankToCustomerAccountReportV01 8, 8, 8, 9, 9, 9, 10, 10, 10, 10, 10, 10, 11, 11, 11, 12, 12, 12, 12, 12,
12, 13, 13
Message BankToCustomerStatementV01 115, 115, 115, 116, 116, 116, 117, 117, 117, 117, 117, 117, 118, 118, 119,
119, 119, 119, 119, 119, 119, 120, 120
Message BankToCustomerDebitCreditNotificationV01 223, 223, 224, 224, 224, 224, 224, 225, 225, 225, 225, 226,
226, 226, 226, 226, 226, 227, 227, 227
<AmtDtls>: AmountDetails
Message BankToCustomerAccountReportV01 10, 11
Message BankToCustomerStatementV01 117, 118
Message BankToCustomerDebitCreditNotificationV01 224, 226
<AmtsdVal>: AmortisedValue
371
<AnncdPstngAmt>: AnnouncedPostingAmount
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
<Avlbty>: Availability
Message BankToCustomerAccountReportV01 8, 9, 9, 12
Message BankToCustomerStatementV01 115, 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 223, 226
Page 398
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
B
<Bal>: Balance
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
<BBAN>: BBAN
334, 335
<BdryAmt>: BoundaryAmount
339, 339, 339, 339
<BEI>: BEI
359
<BIC>: BIC
346, 347, 359
<BirthDt>: BirthDate
359
<BkPtyId>: BankPartyIdentification
359
<BkTxCd>: BankTransactionCode
Message BankToCustomerAccountReportV01 8, 9, 12
Message BankToCustomerStatementV01 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226
<BldgNb>: BuildingNumber
346, 347, 347, 359, 369
<BookgDt>: BookingDate
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
<Br>: Bearer
Message BankToCustomerAccountReportV01 11, 13
Message BankToCustomerStatementV01 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
<BrnchId>: BranchIdentification
347
<Btch>: Batch
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
Page 399
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
C
<Ccy>: Currency
335, 339
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
<CcyXchg>: CurrencyExchange
Message BankToCustomerAccountReportV01 10, 10, 10, 10, 10, 12, 12, 12, 12, 12
Message BankToCustomerStatementV01 117, 117, 117, 117, 117, 119, 119, 119, 119, 119
Message BankToCustomerDebitCreditNotificationV01 224, 224, 224, 224, 225, 226, 226, 226, 226, 226
<Cd>: Code
335
Message BankToCustomerAccountReportV01 7, 7, 8, 9, 9, 9, 9, 9, 10, 10, 11, 12, 12, 12, 12, 13, 14, 14, 15, 16, 16,
16, 16, 16
Message BankToCustomerStatementV01 114, 114, 115, 116, 116, 116, 116, 116, 117, 117, 118, 119, 119, 119, 120,
120, 121, 121, 122, 123, 123, 123, 123, 123
Message BankToCustomerDebitCreditNotificationV01 222, 223, 223, 223, 224, 224, 224, 225, 225, 226, 227, 227,
227, 227, 228, 229, 229, 230, 230, 230, 230, 230
<CdtDbtInd>: CreditDebitIndicator
339
Message BankToCustomerAccountReportV01 8, 8, 8, 8, 9, 9, 9, 11, 12, 13
Message BankToCustomerStatementV01 115, 115, 115, 116, 116, 116, 116, 118, 119, 120
Message BankToCustomerDebitCreditNotificationV01 222, 223, 223, 223, 224, 225, 226, 227
<CdtLine>: CreditLine
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
<CdtNoteAmt>: CreditNoteAmount
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<Cdtr>: Creditor
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
<CdtrAcct>: CreditorAccount
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
<CdtrAgt>: CreditorAgent
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
Page 400
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<CdtrRef>: CreditorReference
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<CdtrRefInf>: CreditorReferenceInformation
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<CdtrRefTp>: CreditorReferenceType
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<CdtrTaxId>: CreditorTaxIdentification
372
<CdtrTaxTp>: CreditorTaxType
372
<CertId>: CertificateIdentification
372
<ChqNb>: ChequeNumber
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
<Chrgs>: Charges
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 225, 227
<CityOfBirth>: CityOfBirth
359
<ClrSysMmbId>: ClearingSystemMemberIdentification
346, 347
<ClrSysRef>: ClearingSystemReference
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
<CmbndId>: CombinedIdentification
346
<CntrValAmt>: CounterValueAmount
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
Page 401
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<ComssnWvrInd>: CommissionWaiverIndicator
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
<CorpActn>: CorporateAction
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
<CpyDplctInd>: CopyDuplicateIndicator
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
<CreDtTm>: CreationDateTime
Message BankToCustomerAccountReportV01 6, 7
Message BankToCustomerStatementV01 113, 114
Message BankToCustomerDebitCreditNotificationV01 222, 222
<CstmrNb>: CustomerNumber
359
<CtgyDesc>: CategoryDescription
372
<CtrctId>: ContractIdentification
343
<Ctry>: Country
346, 347, 347, 359, 369
<CtryOfBirth>: CountryOfBirth
359
<CtryOfRes>: CountryOfResidence
360
<CtrySubDvsn>: CountrySubDivision
346, 347, 347, 359, 369
D
<Dbtr>: Debtor
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 227
<DbtrAcct>: DebtorAccount
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Page 402
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<DbtrAgt>: DebtorAgent
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<DbtrTaxId>: DebtorTaxIdentification
372
<DealPric>: DealPrice
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
<DlvrgAgt>: DeliveringAgent
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<Domn>: Domain
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 116, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226, 230
<DrvrsLicNb>: DriversLicenseNumber
359
<DscntApldAmt>: DiscountAppliedAmount
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<Dt>: Date
345
Message BankToCustomerAccountReportV01 8, 8, 9, 9, 12, 15
Message BankToCustomerStatementV01 115, 115, 116, 116, 119, 122
Message BankToCustomerDebitCreditNotificationV01 223, 223, 226, 229
<DtAndPlcOfBirth>: DateAndPlaceOfBirth
359
<DtTm>: DateTime
345
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<DuePyblAmt>: DuePayableAmount
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
Page 403
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<DUNS>: DUNS
359
E
<EANGLN>: EANGLN
359
<ElctrncSeqNb>: ElectronicSequenceNumber
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
<EndDt>: EndDate
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<EndToEndId>: EndToEndIdentification
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
<EQAmt>: EqualAmount
339
F
<FaceAmt>: FaceAmount
371
<FinInstnId>: FinancialInstitutionIdentification
346
<FinInstrmId>: FinancialInstrumentIdentification
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
<Fmly>: Family
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 116, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226, 230
<FrAmt>: FromAmount
339, 339
<FrDtTm>: FromDateTime
345
Page 404
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<FrToAmt>: FromToAmount
339
<FrToDt>: FromToDate
Message BankToCustomerAccountReportV01 7, 7, 11, 13
Message BankToCustomerStatementV01 114, 115, 118, 120
Message BankToCustomerDebitCreditNotificationV01 222, 225, 227
G
<GrpHdr>: GroupHeader
Message BankToCustomerAccountReportV01 6
Message BankToCustomerStatementV01 113
Message BankToCustomerDebitCreditNotificationV01 221
I
<IBAN>: IBAN
334, 335
<IBEI>: IBEI
359
<Id>: Identification
334, 335, 335, 346, 346, 347, 347, 347, 359, 359, 360
Message BankToCustomerAccountReportV01 7, 7, 11, 13, 16
Message BankToCustomerStatementV01 114, 114, 118, 120, 123
Message BankToCustomerDebitCreditNotificationV01 222, 222, 225, 227, 230
<IdntyCardNb>: IdentityCardNumber
359
<IdTp>: IdentificationType
360
<Incl>: Included
339, 339, 339, 339
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
<InitgPty>: InitiatingParty
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 227
<InstdAmt>: InstructedAmount
Message BankToCustomerAccountReportV01 10, 11
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
<InstrId>: InstructionIdentification
Page 405
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 225
<IntrBkSttlmDt>: InterbankSettlementDate
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<IntrmyAgt1>: IntermediaryAgent1
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<IntrmyAgt2>: IntermediaryAgent2
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<IntrmyAgt3>: IntermediaryAgent3
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<Intrst>: Interest
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
<Invcee>: Invoicee
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<Invcr>: Invoicer
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<ISIN>: ISIN
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
<IssgAgt>: IssuingAgent
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<Issr>: Issuer
346, 347, 359, 360
Message BankToCustomerAccountReportV01 9, 10, 12, 14, 15, 16
Page 406
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
L
<LastPgInd>: LastPageIndicator
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
<LglSeqNb>: LegalSequenceNumber
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
M
<MndtId>: MandateIdentification
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
<MplyrIdNb>: EmployerIdentificationNumber
359
<MsgId>: MessageIdentification
Message BankToCustomerAccountReportV01 6, 10, 10, 11
Message BankToCustomerStatementV01 113, 117, 117, 118
Message BankToCustomerDebitCreditNotificationV01 221, 224, 224, 225
<MsgNmId>: MessageNameIdentification
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
<MsgPgntn>: MessagePagination
Message BankToCustomerAccountReportV01 6
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
<MsgRcpt>: MessageRecipient
Message BankToCustomerAccountReportV01 6
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
N
<Nb>: Number
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
Page 407
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<NbOfDays>: NumberOfDays
Message BankToCustomerAccountReportV01 8, 9, 9, 12
Message BankToCustomerStatementV01 115, 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226
<NbOfNtries>: NumberOfEntries
Message BankToCustomerAccountReportV01 8, 8, 8, 8
Message BankToCustomerStatementV01 115, 115, 115, 115
Message BankToCustomerDebitCreditNotificationV01 222, 222, 223, 223
<NbOfTxs>: NumberOfTransactions
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
<NEQAmt>: NotEqualAmount
339
<Nm>: Name
335, 346, 347, 347, 358
Message BankToCustomerAccountReportV01 7, 14
Message BankToCustomerStatementV01 114, 121
Message BankToCustomerDebitCreditNotificationV01 222, 228
<NmAndAdr>: NameAndAddress
346
<Ntfctn>: Notification
Message BankToCustomerDebitCreditNotificationV01 222
<Ntry>: Entry
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
O
<OrgId>: OrganisationIdentification
359
<OrgnlBkTxCd>: OriginalBankTransactionCode
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
<OthrId>: OtherIdentification
360
<Ownr>: Owner
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Page 408
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
P
<PctgRate>: PercentageRate
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
<PgNb>: PageNumber
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
<PmtInfId>: PaymentInformationIdentification
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
<Pric>: Price
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
<Prtry>: Proprietary
335, 346, 347
Message BankToCustomerAccountReportV01 7, 7, 8, 9, 9, 11, 11, 12, 13, 13, 14, 14, 14, 15, 15, 15, 15, 16, 16, 16,
16
Message BankToCustomerStatementV01 114, 114, 115, 116, 117, 118, 118, 119, 120, 120, 121, 121, 121, 122, 122,
122, 122, 123, 123, 123, 123
Message BankToCustomerDebitCreditNotificationV01 222, 223, 224, 225, 226, 227, 227, 228, 228, 228, 229, 229,
229, 230, 230, 230, 230, 230, 231
<PrtryAcct>: ProprietaryAccount
334, 335
<PrtryAmt>: ProprietaryAmount
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
<PrtryCd>: ProprietaryCode
Message BankToCustomerAccountReportV01 10, 13
Message BankToCustomerStatementV01 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
<PrtryId>: ProprietaryIdentification
346, 347, 359
<PrvcOfBirth>: ProvinceOfBirth
359
Page 409
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<PrvtId>: PrivateIdentification
359
<PsptNb>: PassportNumber
359
<PstCd>: PostCode
346, 347, 347, 359, 369
<PstlAdr>: PostalAddress
346, 347, 347, 359
<Pty>: Party
Message BankToCustomerAccountReportV01 11, 13, 13
Message BankToCustomerStatementV01 118, 120, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227, 228
<Purp>: Purpose
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
Q
<QtnDt>: QuotationDate
343
<Qty>: Quantity
Message BankToCustomerAccountReportV01 15, 15
Message BankToCustomerStatementV01 122, 123
Message BankToCustomerDebitCreditNotificationV01 230, 230
R
<Rate>: Rate
372
Message BankToCustomerAccountReportV01 7, 7, 10, 11, 11, 11, 13, 13, 13, 13
Message BankToCustomerStatementV01 114, 114, 118, 118, 118, 118, 120, 120, 120, 120
Message BankToCustomerDebitCreditNotificationV01 225, 225, 225, 225, 227, 227, 227, 227
<RcvgAgt>: ReceivingAgent
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<Ref>: Reference
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
<Refs>: References
Page 410
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 225
<RfrdDocAmt>: ReferredDocumentAmount
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
<RfrdDocInf>: ReferredDocumentInformation
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
<RfrdDocNb>: ReferredDocumentNumber
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
<RfrdDocRltdDt>: ReferredDocumentRelatedDate
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
<RfrdDocTp>: ReferredDocumentType
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
<RltdAcct>: RelatedAccount
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
<RltdAgts>: RelatedAgents
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<RltdDts>: RelatedDates
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<RltdPric>: RelatedPrice
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
<RltdPties>: RelatedParties
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Page 411
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<RltdQties>: RelatedQuantities
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
<RltdRmtInf>: RelatedRemittanceInformation
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<RmtdAmt>: RemittedAmount
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<RmtId>: RemittanceIdentification
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<RmtInf>: RemittanceInformation
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<RmtLctnElctrncAdr>: RemittanceLocationElectronicAddress
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<RmtLctnMtd>: RemittanceLocationMethod
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<RmtLctnPstlAdr>: RemittanceLocationPostalAddress
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<Rpt>: Report
Message BankToCustomerAccountReportV01 7
<Rsn>: Reason
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 115, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
<RtrInf>: ReturnInformation
Message BankToCustomerAccountReportV01 16
Page 412
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<RtrOrgtr>: ReturnOriginator
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
<RtrRsn>: ReturnReason
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
<RvslInd>: ReversalIndicator
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
S
<SclSctyNb>: SocialSecurityNumber
359
<SfkpgAcct>: SafekeepingAccount
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 231
<SrcCcy>: SourceCurrency
343
<StartDt>: StartDate
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<Stmt>: Statement
Message BankToCustomerStatementV01 114
<Strd>: Structured
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
<StrtNm>: StreetName
346, 347, 347, 359, 369
<Sts>: Status
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
Page 413
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<SttlmPlc>: SettlementPlace
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
<SubFmlyCd>: SubFamilyCode
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 117, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 227, 230
<Sum>: Sum
Message BankToCustomerAccountReportV01 8, 8, 8, 8
Message BankToCustomerStatementV01 115, 115, 115, 115
Message BankToCustomerDebitCreditNotificationV01 222, 223, 223, 223
<Svcr>: Servicer
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
T
<Tax>: Tax
Message BankToCustomerAccountReportV01 11, 13, 16
Message BankToCustomerStatementV01 118, 120, 123
Message BankToCustomerDebitCreditNotificationV01 225, 227, 230
<TaxAmt>: TaxAmount
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<TaxblBaseAmt>: TaxableBaseAmount
372
<TaxDt>: TaxDate
372
<TaxIdNb>: TaxIdentificationNumber
359, 359
<TaxRefNb>: TaxReferenceNumber
372
<TaxTp>: TaxType
372
<TaxTpInf>: TaxTypeInformation
372
<ToAmt>: ToAmount
339, 339
Page 414
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<ToDtTm>: ToDateTime
345
<Tp>: Type
335
Message BankToCustomerAccountReportV01 7, 7, 8, 10, 10, 11, 11, 12, 12, 13, 13, 14, 15, 15, 15, 16
Message BankToCustomerStatementV01 114, 114, 115, 117, 117, 118, 118, 119, 120, 120, 120, 121, 122, 122, 122,
123
Message BankToCustomerDebitCreditNotificationV01 222, 225, 225, 225, 226, 226, 227, 227, 228, 228, 229, 230,
230, 230
<TradDt>: TradeDate
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<TradgPty>: TradingParty
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
<TrgtCcy>: TargetCurrency
343
<TtlCdtNtries>: TotalCreditEntries
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 222
<TtlChrgsAndTaxAmt>: TotalChargesAndTaxAmount
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 225, 227
<TtlDbtNtries>: TotalDebitEntries
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 223
<TtlNetNtryAmt>: TotalNetEntryAmount
Message BankToCustomerAccountReportV01 8, 8
Message BankToCustomerStatementV01 115, 115
Message BankToCustomerDebitCreditNotificationV01 222, 223
<TtlNtries>: TotalEntries
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 222
<TtlNtriesPerBkTxCd>: TotalEntriesPerBankTransactionCode
Message BankToCustomerAccountReportV01 8
Page 415
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<TtlTaxAmt>: TotalTaxAmount
372
<TtlTaxblBaseAmt>: TotalTaxableBaseAmount
372
<TwnNm>: TownName
346, 347, 347, 359, 369
<TxAmt>: TransactionAmount
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
<TxDtls>: TransactionDetails
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 225
<TxDtTm>: TransactionDateTime
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
<TxId>: TransactionIdentification
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
<TxsSummry>: TransactionsSummary
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 222
<TxtlRate>: TextualRate
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
U
<UltmtCdtr>: UltimateCreditor
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
<UltmtDbtr>: UltimateDebtor
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Page 416
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
<Unit>: Unit
371
<UnitCcy>: UnitCurrency
343
<UPIC>: UPIC
334, 335
<USCHU>: CHIPSUniversalIdentification
359
<Ustrd>: Unstructured
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
V
<ValDt>: ValueDate
Message BankToCustomerAccountReportV01 9
Message BankToCustomerStatementV01 116
Message BankToCustomerDebitCreditNotificationV01 223
<VldtyRg>: ValidityRange
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
X
<XchgRate>: ExchangeRate
343
AccountInterest1
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
AccountNotification1
Page 417
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
AccountReport9
Message BankToCustomerAccountReportV01 7
AccountStatement1
Message BankToCustomerStatementV01 114
AddressType2Code
346, 347, 347, 359, 369
AlternateSecurityIdentification2
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
AmountAndCurrencyExchange2
Message BankToCustomerAccountReportV01 10, 11
Message BankToCustomerStatementV01 117, 118
Message BankToCustomerDebitCreditNotificationV01 224, 226
AmountAndCurrencyExchangeDetails1
Message BankToCustomerAccountReportV01 10, 10, 10, 10, 11, 12, 12, 12
Message BankToCustomerStatementV01 117, 117, 117, 117, 119, 119, 119, 119
Message BankToCustomerDebitCreditNotificationV01 224, 224, 224, 224, 226, 226, 226, 226
AmountAndCurrencyExchangeDetails2
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 224, 226
AmountRangeBoundary1
339, 339, 339, 339
AustrianBankleitzahlIdentifier
320
B
BalanceType1Choice
Message BankToCustomerAccountReportV01 8
BalanceType2Choice
Message BankToCustomerStatementV01 115
BalanceType8Code
Message BankToCustomerAccountReportV01 8
BalanceType9Code
Message BankToCustomerStatementV01 115
BankTransactionCodeStructure1
Page 418
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
BankTransactionCodeStructure2
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 116, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226, 230
BankTransactionCodeStructure3
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 116, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226, 230
BaseOneRate
329, 343
BatchInformation1
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
BBANIdentifier
320, 334, 335
BEIIdentifier
320, 359
BelgianIdentifier
321
BICIdentifier
321, 346, 347, 359
BloombergIdentifier
321
BranchAndFinancialInstitutionIdentification3
346
Message BankToCustomerAccountReportV01 7, 11, 13, 13, 14, 14, 14, 14, 14, 14, 14, 14, 14
Message BankToCustomerStatementV01 114, 118, 120, 121, 121, 121, 121, 121, 121, 121, 121, 121, 121
Message BankToCustomerDebitCreditNotificationV01 222, 225, 227, 228, 228, 228, 228, 228, 228, 228, 228, 228,
228
BranchData
347
C
CanadianPaymentsARNIdentifier
322
Page 419
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
CashAccount13
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
CashAccount7
335
Message BankToCustomerAccountReportV01 7, 13, 13, 16
Message BankToCustomerStatementV01 114, 120, 120, 123
Message BankToCustomerDebitCreditNotificationV01 222, 228, 228, 231
CashAccountType2
335
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
CashAccountType4Code
335
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
CashBalance1
Message BankToCustomerAccountReportV01 8
CashBalance2
Message BankToCustomerStatementV01 115
CashBalanceAvailability1
Message BankToCustomerAccountReportV01 8, 9, 9, 12
Message BankToCustomerStatementV01 115, 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 223, 226
CashBalanceAvailabilityDate1
Message BankToCustomerAccountReportV01 8, 9, 9, 12
Message BankToCustomerStatementV01 115, 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 223, 226
ChargeBearerType1Code
Message BankToCustomerAccountReportV01 11, 13
Message BankToCustomerStatementV01 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
ChargesInformation3
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 119
Message BankToCustomerDebitCreditNotificationV01 225, 227
ChargeType1Code
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 120
Page 420
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
ChargeTypeChoice
Message BankToCustomerAccountReportV01 10, 12
Message BankToCustomerStatementV01 117, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
CHIPSParticipantIdentifier
321
CHIPSUniversalIdentifier
321, 359
ClearingSystemMemberIdentification3Choice
346, 347
ConsolidatedTapeAssociationIdentifier
322
CopyDuplicate1Code
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
CorporateAction1
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
CountryCode
322, 346, 347, 347, 359, 359, 360, 369
CreditDebitCode
339
Message BankToCustomerAccountReportV01 8, 8, 8, 8, 9, 9, 9, 11, 12, 13
Message BankToCustomerStatementV01 115, 115, 115, 116, 116, 116, 116, 118, 119, 120
Message BankToCustomerDebitCreditNotificationV01 222, 223, 223, 223, 224, 225, 226, 227
CreditLine1
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
CreditorReferenceInformation1
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
CreditorReferenceType1
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
Page 421
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
CurrencyAndAmount
319, 372, 372, 372, 372
Message BankToCustomerAccountReportV01 8, 8, 8, 9, 9, 9, 10, 10, 10, 10, 10, 10, 10, 11, 11, 11, 12, 12, 12, 12,
12, 12, 12, 13, 13, 14, 14, 15, 15, 15, 15, 15
Message BankToCustomerStatementV01 115, 115, 115, 116, 116, 116, 117, 117, 117, 117, 117, 117, 117, 118, 118,
119, 119, 119, 119, 119, 119, 119, 119, 120, 120, 122, 122, 122, 122, 122, 122, 122
Message BankToCustomerDebitCreditNotificationV01 223, 223, 224, 224, 224, 224, 224, 225, 225, 225, 225, 225,
226, 226, 226, 226, 226, 226, 227, 227, 227, 227, 229, 229, 229, 229, 229, 230, 230
CurrencyAndAmountRange
339
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
CurrencyCode
322, 335, 339, 343, 343, 343, 372, 372, 372, 372
Message BankToCustomerAccountReportV01 7, 8, 8, 8, 9, 9, 9, 10, 10, 10, 10, 10, 10, 10, 11, 11, 11, 12, 12, 12, 12,
12, 12, 12, 13, 13, 14, 14, 15, 15, 15, 15, 15
Message BankToCustomerStatementV01 114, 115, 115, 115, 116, 116, 116, 117, 117, 117, 117, 117, 117, 117, 118,
118, 119, 119, 119, 119, 119, 119, 119, 119, 120, 120, 122, 122, 122, 122, 122, 122, 122
Message BankToCustomerDebitCreditNotificationV01 222, 223, 223, 224, 224, 224, 224, 224, 225, 225, 225, 225,
225, 226, 226, 226, 226, 226, 226, 227, 227, 227, 227, 229, 229, 229, 229, 229, 230, 230
CurrencyExchange3
343
Message BankToCustomerAccountReportV01 10, 10, 10, 10, 10, 12, 12, 12, 12, 12
Message BankToCustomerStatementV01 117, 117, 117, 117, 117, 119, 119, 119, 119, 119
Message BankToCustomerDebitCreditNotificationV01 224, 224, 224, 224, 225, 226, 226, 226, 226, 226
CUSIPIdentifier
322
D
DateAndDateTimeChoice
345
Message BankToCustomerAccountReportV01 8, 9, 9
Message BankToCustomerStatementV01 115, 116, 116
Message BankToCustomerDebitCreditNotificationV01 223, 223
DateAndPlaceOfBirth
359
DateTimePeriodDetails
345
Message BankToCustomerAccountReportV01 7, 7, 11, 13
Message BankToCustomerStatementV01 114, 115, 118, 120
Message BankToCustomerDebitCreditNotificationV01 222, 225, 227
DecimalNumber
329, 371
Page 422
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Message BankToCustomerAccountReportV01 8, 8, 8, 8, 8, 8
Message BankToCustomerStatementV01 115, 115, 115, 115, 115, 115
Message BankToCustomerDebitCreditNotificationV01 222, 222, 223, 223, 223, 223
DocumentType2Code
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
DocumentType3Code
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
DunsIdentifier
323, 359
DutchIdentifier
323
E
EANGLNIdentifier
323, 359
EntryStatus2Code
Message BankToCustomerAccountReportV01 9
EntryStatus3Code
Message BankToCustomerStatementV01 116
EntryStatus4Code
Message BankToCustomerDebitCreditNotificationV01 223
EntryTransaction1
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 225
EuroclearClearstreamIdentifier
323
ExtensiveBranchNetworkIdentifier
323
ExternalBankTransactionDomainCode
323
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 116, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226, 230
ExternalBankTransactionFamilyCode
Page 423
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
324
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 116, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 227, 230
ExternalBankTransactionSubFamilyCode
324
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 117, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 227, 230
ExternalClearingSystemMemberCode
324, 346, 347
ExternalPurposeCode
324
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
F
FedwireRoutingNumberIdentifier
324
FinancialInstitutionIdentification3
346
FinancialInstitutionIdentification5Choice
346
FinancialInstrumentQuantityChoice
371
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
FromToAmountRange
339
G
GenericIdentification3
346, 347, 359
GenericIdentification4
360
GermanBankleitzahlIdentifier
325
Page 424
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
GroupHeader23
Message BankToCustomerAccountReportV01 6
Message BankToCustomerStatementV01 113
Message BankToCustomerDebitCreditNotificationV01 221
H
HellenicBankIdentificationCodeIdentifier
325
HongKongBankIdentifier
325
I
IBANIdentifier
325, 334, 335
IBEIIdentifier
325, 359
ImpliedCurrencyAmountRangeChoice
339
ImpliedCurrencyAndAmount
319, 339, 339, 339, 339, 339, 339, 371, 371
IndianFinancialSystemCodeIdentifier
326
InterestType1Choice
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
InterestType1Code
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
IrishNSCIdentifier
326
ISINIdentifier
325
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
ISODate
319, 345, 359, 372
Page 425
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
ISODateTime
319, 343, 345, 345, 345
Message BankToCustomerAccountReportV01 6, 7, 15, 15, 15
Message BankToCustomerStatementV01 113, 114, 122, 122, 122
Message BankToCustomerDebitCreditNotificationV01 222, 222, 229, 229, 229
ISOTime
320
ISOYear
320
ItalianDomesticIdentifier
326
L
LanguageCode
326
M
Max1025Text
330
Max105Text
330
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
Max128Text
330
Max140Text
330, 372
Message BankToCustomerAccountReportV01 14, 15
Message BankToCustomerStatementV01 121, 122
Message BankToCustomerDebitCreditNotificationV01 228, 229
Max15NumericText
330
Message BankToCustomerAccountReportV01 8, 8, 8, 8, 10
Message BankToCustomerStatementV01 115, 115, 115, 115, 117
Message BankToCustomerDebitCreditNotificationV01 222, 222, 223, 223, 224
Max15PlusSignedNumericText
Page 426
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
331
Message BankToCustomerAccountReportV01 8, 9, 9, 12
Message BankToCustomerStatementV01 115, 116, 116, 119
Message BankToCustomerDebitCreditNotificationV01 223, 224, 226
Max16Text
331, 346, 346, 347, 347, 347, 347, 359, 359, 369, 369
Max256Text
331
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
Max34Text
331, 334, 335
Max350Text
331
Max35Text
331, 335, 343, 346, 346, 346, 346, 346, 347, 347, 347, 347, 347, 347, 347, 347, 347, 359, 359, 359, 359, 359, 359,
359, 359, 359, 359, 359, 359, 359, 359, 359, 359, 360, 360, 360, 369, 369, 372, 372, 372, 372, 372
Message BankToCustomerAccountReportV01 6, 7, 7, 7, 7, 7, 8, 9, 9, 9, 10, 10, 10, 10, 10, 10, 10, 11, 11, 11, 11, 11,
11, 11, 11, 11, 11, 11, 11, 11, 11, 12, 12, 12, 13, 13, 13, 13, 13, 14, 14, 14, 14, 14, 14, 15, 15, 15, 15, 15, 15, 15, 16,
16, 16, 16, 16, 16, 16, 16
Message BankToCustomerStatementV01 113, 114, 114, 114, 114, 115, 115, 116, 116, 116, 117, 117, 117, 117, 117,
117, 117, 118, 118, 118, 118, 118, 118, 118, 118, 118, 118, 118, 118, 118, 118, 119, 119, 119, 120, 120, 120, 120,
120, 121, 121, 121, 121, 121, 121, 122, 122, 122, 122, 122, 122, 123, 123, 123, 123, 123, 123, 123, 123, 123
Message BankToCustomerDebitCreditNotificationV01 221, 222, 222, 223, 223, 223, 224, 224, 224, 224, 224, 224,
225, 225, 225, 225, 225, 225, 225, 225, 226, 226, 226, 226, 226, 226, 226, 226, 227, 227, 227, 227, 227, 227, 228,
228, 228, 228, 229, 229, 229, 229, 229, 229, 229, 230, 230, 230, 230, 230, 230, 230, 230, 230, 230, 231
Max3NumericText
332
Max4AlphaNumericText
332
Message BankToCustomerAccountReportV01 10, 13
Message BankToCustomerStatementV01 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
Max500Text
332
Message BankToCustomerAccountReportV01 7, 16, 16, 16
Message BankToCustomerStatementV01 114, 123, 123, 123
Message BankToCustomerDebitCreditNotificationV01 222, 231, 231, 231
Max5NumericText
332
Message BankToCustomerAccountReportV01 7
Message BankToCustomerStatementV01 114
Page 427
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Max6Text
332
Max70Text
332, 335, 346, 346, 346, 347, 347, 347, 347, 347, 358, 359, 359, 369, 369
Message BankToCustomerAccountReportV01 7, 14
Message BankToCustomerStatementV01 114, 121
Message BankToCustomerDebitCreditNotificationV01 222, 228
MessageIdentification2
Message BankToCustomerAccountReportV01 10
Message BankToCustomerStatementV01 117
Message BankToCustomerDebitCreditNotificationV01 224
MICIdentifier
326
N
NameAndAddress3
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
NameAndAddress7
346
NationalityCode
326
NewZealandNCCIdentifier
326
NotificationEntry1
Message BankToCustomerDebitCreditNotificationV01 223
Number
329
Message BankToCustomerAccountReportV01 7, 7
Message BankToCustomerStatementV01 114, 114
Message BankToCustomerDebitCreditNotificationV01 222, 222
NumberAndSumOfTransactions1
Message BankToCustomerAccountReportV01 8, 8
Message BankToCustomerStatementV01 115, 115
Message BankToCustomerDebitCreditNotificationV01 222, 223
NumberAndSumOfTransactions2
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Page 428
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
NumberAndSumOfTransactionsPerBankTransactionCode1
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 223
O
OrganisationIdentification2
359
P
Pagination
Message BankToCustomerAccountReportV01 6
Message BankToCustomerStatementV01 114
Message BankToCustomerDebitCreditNotificationV01 222
Party2Choice
359
PartyIdentification8
358
Message BankToCustomerAccountReportV01 6, 7, 13, 13, 13, 13, 13, 13, 13, 15, 15, 16
Message BankToCustomerStatementV01 114, 114, 120, 120, 120, 120, 120, 120, 120, 122, 122, 123
Message BankToCustomerDebitCreditNotificationV01 222, 222, 227, 227, 228, 228, 228, 228, 228, 229, 229, 230
PercentageRate
330, 372
Message BankToCustomerAccountReportV01 7, 10, 11, 11, 13, 13, 13
Message BankToCustomerStatementV01 114, 118, 118, 118, 120, 120, 120
Message BankToCustomerDebitCreditNotificationV01 225, 225, 225, 227, 227, 227
PersonIdentification3
359
PolishNationalClearingCodeIdentifier
327
PortugueseNCCIdentifier
327
PostalAddress1
346, 347, 347, 359, 369
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
ProprietaryAgent1
Message BankToCustomerAccountReportV01 14
Page 429
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
ProprietaryBankTransactionCodeStructure1
Message BankToCustomerAccountReportV01 9, 9, 12, 16
Message BankToCustomerStatementV01 116, 117, 119, 123
Message BankToCustomerDebitCreditNotificationV01 223, 224, 227, 230
ProprietaryDate1
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
ProprietaryParty1
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 228
ProprietaryPrice1
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
ProprietaryQuantity1
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
ProprietaryReference1
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 226
Purpose1Choice
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
Q
QUICKIdentifier
327
R
Rate1
Message BankToCustomerAccountReportV01 7, 11, 13
Message BankToCustomerStatementV01 114, 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
RateTypeChoice
Page 430
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
ReferredDocumentAmount1Choice
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
ReferredDocumentInformation1
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
ReferredDocumentType1
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
RemittanceInformation1
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
RemittanceLocation1
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
RemittanceLocationMethod1Code
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
ReportEntry1
Message BankToCustomerAccountReportV01 9
ReturnReason1Choice
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
ReturnReasonInformation5
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
RICIdentifier
327
RussianCentralBankIdentificationCodeIdentifier
327
Page 431
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
S
SecurityIdentification4Choice
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
SEDOLIdentifier
327
SicovamIdentifier
327
SimpleIdentificationInformation2
334, 335
SmallNetworkIdentifier
328
SouthAfricanNCCIdentifier
328
SpanishDomesticInterbankingIdentifier
328
StatementEntry1
Message BankToCustomerStatementV01 116
StructuredRemittanceInformation6
Message BankToCustomerAccountReportV01 14
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 229
SwissBCIdentifier
328
SwissSICIdentifier
328
T
TaxCharges1
Message BankToCustomerAccountReportV01 11, 13
Message BankToCustomerStatementV01 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
TaxDetails
372
TaxInformation2
Page 432
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
372
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
TaxType
372
TickerIdentifier
328
TotalTransactions1
Message BankToCustomerAccountReportV01 8
Message BankToCustomerStatementV01 115
Message BankToCustomerDebitCreditNotificationV01 222
TransactionAgents1
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 121
Message BankToCustomerDebitCreditNotificationV01 228
TransactionDates1
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 229
TransactionInterest1
Message BankToCustomerAccountReportV01 11, 13
Message BankToCustomerStatementV01 118, 120
Message BankToCustomerDebitCreditNotificationV01 225, 227
TransactionParty1
Message BankToCustomerAccountReportV01 13
Message BankToCustomerStatementV01 120
Message BankToCustomerDebitCreditNotificationV01 227
TransactionPrice1Choice
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
TransactionQuantities1Choice
Message BankToCustomerAccountReportV01 15
Message BankToCustomerStatementV01 122
Message BankToCustomerDebitCreditNotificationV01 230
TransactionReferences1
Message BankToCustomerAccountReportV01 11
Message BankToCustomerStatementV01 118
Message BankToCustomerDebitCreditNotificationV01 225
TransactionRejectReason2Code
Page 433
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Indexes
Message BankToCustomerAccountReportV01 16
Message BankToCustomerStatementV01 123
Message BankToCustomerDebitCreditNotificationV01 230
TrueFalseIndicator
Message BankToCustomerAccountReportV01 8, 9
Message BankToCustomerStatementV01 115, 116
Message BankToCustomerDebitCreditNotificationV01 223
U
UKDomesticSortCodeIdentifier
329
UPICIdentifier
329, 334, 335
V
ValorenIdentifier
329
W
WertpapierIdentifier
329
Y
YesNoIndicator
339, 339, 339, 339
Message BankToCustomerAccountReportV01 7, 10
Message BankToCustomerStatementV01 114, 117
Message BankToCustomerDebitCreditNotificationV01 222, 224
Page 434
UNIFI (ISO 20022) - Bank-to-Customer Cash Management Standards April 2007
Revision Record
Revision Record
Revision Date Author Description Sections affected
1.0 20/04/2007 ISO 20022 RA Initial version All
Page 435