Format Description Generic Payment File (Pain.001)

Format description
Generic Payment File
Rabo Direct Connect,

SWIFT FileAct,
Rabo Internet banking
(Professional) &
Rabo Business Banking
Contents
1 GENERAL ............................................................................................................................... 3
1.1 GENERAL CHARACTERISTICS..............................................................................................................3
1.2 STRUCTURE ...................................................................................................................................3
1.2.1 Introduction ........................................................................................................................3
1.2.2 Technical mapping..............................................................................................................3
1.2.3 Character set ......................................................................................................................5
1.2.4 Compatibility ......................................................................................................................5
1.2.5 Message structure ..............................................................................................................6
2 PAYMENT DETERMINATION ................................................................................................... 7
2.1 PROCESSING SCHEMA ......................................................................................................................7
3 SEGMENT DESCRIPTION ......................................................................................................... 8
3.1 GROUP HEADER .............................................................................................................................8
3.2 PAYMENT INFORMATION SEGMENT ................................................................................................ 10
3.3 TRANSACTION INFORMATION SEGMENT .......................................................................................... 19
APPENDIX A – PARTY IDENTIFIER ................................................................................................ 33
APPENDIX B – PAYMENT INFORMATION PER COUNTRY ............................................................... 36
CHANGELOG ............................................................................................................................... 39
Rabobank Format description Generic Payment File February 2021 | Version 1.9.3 2
1 General
Rabobank offers the possibility to import batches with Europayments, Urgent Europayments, Urgent
Domestic Europayments, Worldpayments and Multibank payments using one payment file format. This
format concerns the pain.001.001.03 standard which is already being used for Europayments within the
Single Euro Payment Area (SEPA) and will be referred to by Rabobank - because of the broader usage of
the format and differences between Euro- and Worldpayments - as the “Generic Payment File” format.
A file in the Generic Payment File format may contain one (1) or more batches, and a batch can contain
one or more payments being debited from a single current account. Furthermore the characteristics of
a batch are that the payment(s) within the batch will be processed using the specified Requested
Execution Date; And when the batch contains more than one payment, the payment type for all
payments must be equal. When the Generic Payment File contains Europayments as well as
Worldpayments these payments must be presented in separate batches - one batch may not contain
both Euro- and Worldpayments. Both Urgent Europayments and Worldpayments may be present in
one batch.
1.1 General characteristics

The Generic Payment File format supported by Rabobank is based on the specifications which are
published on the website of the International Organisation for Standardization (XML ISO20022) and
complies to the Implementation Guidelines as specified by the Common Global Implementation1. This
document contains the format description for Generic Payment File format as supported by the
Rabobank systems Rabo Direct Connect (RDC), SWIFT FileAct, Rabobank Internetbanking (Professional)
and Rabo Business Banking.
1.2 Structure
1.2.1 Introduction
A Generic Payment File contains (batches with) payments using the Extensible Markup
Language (XML), which is a structured language containing all necessary attributes (tags and
content) to be able to process payments. To be able to check if the structure and used
attributes are correct the Generic Payment File can be validated against the XML Schema
Definition (XSD) which is published on the ISO20022 website.
This XSD can be obtained via https://www.iso20022.org/catalogue-messages/iso-20022-

messages-archive
1.2.2 Technical mapping

To avoid rejection of payments and/or to prevent that instructions are ignored usage rules must be
followed. Only message elements which are described within these guidelines are allowed to be used:
Name Name of the element within the Generic Payment File message
XML-tag Short name to identify an element within a XML message, presented between
brackets, f.e. <Amt> which means Amount.
ISO ref. Numbering following the ISO 20022 standard.
Not all fields are numbered. Fields can be a subset of the parenting element.
Gaps in the numbering do exist because not all elements of ISO20022 are supported.
1
The Common Global Implementation (CGI) group aims to achieve a high degree of standardization as to limit the obstacles users encounter
when implementing XML credit transfer formats. Please refer to http://www.swift.com/corporates/cgi/index for more information.
Name Name of the element within the Generic Payment File message
Level Level of the element within the Generic Payment File message
<Top>
<Level 1>
<Level 2>
<Etc.>..</Etc.>
</Level 2>
</Level 1>
</Top>
Presence This determines if an element is optional or mandatory, and how many times the
element can be repeated. The number of times that an element can appear is
presented between square brackets.
[0..1] Shows that the element can appear 0 or 1 time.

The element is optional.
[0..n] Shows that the element can appear 0 or n time(s).
The element is optional.
[1..1] Shows that the element is mandatory and must appear once.
[1..n] Shows that the element is mandatory and must appear at least once. The
element can be presented n times.
A sub level element is mandatory only if the (optional) element above is present.
Type Field type indication:
- Numeric: only numbers are allowed
- Alphanumeric: may contain numbers and allowed characters (ref.
1.2.3 Character set)
- Date: CCYY-MM-DD
- Amount: numbers, with a decimal point as separator. The presentation of
the number of decimals are compliant with ISO4217.
The maximum length is 9 digits before the separator, and two behind it.
- Boolean: field with two options: ‘true’ or ‘false’
Length Maximum number of characters in the field.
Description Contains the definition of the message segment or element. Additional information
about usage of the element.
Europayments Indication 'X' means that this field is used for this type of payment.
Urgent Domestic Indication 'X' means that this field is used for this type of payment.
Europayments
Worldpayments + Indication 'X' means that this field is used for this type of payment.
Urgent Europayments
Multibank payments Indication 'X' means that this field is used for this type of payment.
When a message contains end-of-line characters and/or tab-characters, “Carriage Return” and
“LineFeed” (hexadecimal values 0x0D and 0x0A or decimal ASCII character values 13 and 10)
respectively, or a tab - “Horizontal Tab” (hexadecimal value 0x09 or decimal ASCII character value 9),
these characters are only allowed outside of the XML-tags; these characters are not allowed within the
tags or as field values. The only ‘practical’ use for these end-of-line and tab characters is for
readability/presentation within an editor which does not support a XML formatted presentation/view
of the information (and f.e. will present all the XML information in one line).
1.2.3 Character set
In Generic Payment File messages the standard UTF8 encoding must be used, using the Latin
characters which are common for international communication.
Rabobank accepts the following characters1:
 abcdefghijklmnopqrstuvwxyz
 ABCDEFGHIJKLMNOPQRSTUVWXYZ
 /-?:().,'+
 0123456789
 Space
UTF-8 must be used as the default way of encoding characters. Characters with a different coding (for
example ISO-8859-1) may lead to rejected files. Rabobank accepts the extended character set as
recommended by the EPC. Fields which are used to identify a batch or payment (transaction) are
excluded from this extended character set.
For pain.001 it includes the following fields: <PmtInfId>, <InstrId> and <EndToEndId>.
1.2.4 Compatibility
Currently Europayments are completely processed via XML formatted messages by all parties involved
in the payment chain. Worldpayments and Urgent Europayments however are not yet processed via
XML formatted messages, these payments are processed and forwarded using “legacy” formats2 within
the payment chain.
These “legacy” formats offer limited or no support for certain tags/fields within the XML messages,
which is why information within these tags/fields can be truncated or lost.
Also there are options (fields) which are not allowed for Europayments yet relevant for World- or Urgent
Europayments: For example for Worldpayments it is possible to present an e-mail address via the
tag/field InstructionsForDebtorAgent to have the bank send a payment confirmation to this address.
This option is not available for Europayments.
The following payments are supported for Rabobank accounts including Rabo Network Banking
accounts (=accounts which are held with Rabobank in Belgium, Germany and The United Kingdom:
 Europayments - payments in EUR currency to a beneficiary in a

SEPA country.
 Urgent Domestic Europayments - urgent payments in the EUR currency between Dutch
bank accounts. Not available for Rabo Network
Banking accounts.
 Urgent Europayments - urgent payments in the EUR currency to a beneficiary
in a SEPA country.
 Worldpayments - payments in foreign and EUR currency outside the
SEPA area.
The following payments are supported for foreign non-Rabobank accounts:
 Multibank payments - payments from accounts held with other banks.
1
Rabobank accepts diacritical characters, these characters will not be converted to the characters as specified in 2.3. Depending on the
diacritical characters being used, there is a risk that payments containing these characters will not be processed by the bank of the beneficiary
(when the bank of the beneficiary does not allow or support these characters).
2
A “legacy” format, between banks is SWIFT FIN MT103 message standard which is used for non-SEPA credit transfers. The term “legacy” format
is used relative to the pain.001.001.03 format, it does not mean that SWIFT FIN messages are old or outdated.
Important information about Urgent Domestic Europayments and Urgent Europayments:
Whereas it is guaranteed in The Netherlands that an Urgent Domestic Europayment will be available on
the account of the beneficiary within 1,5 hours, for an Urgent Europayment we can only guarantee that
the bank of the beneficiary will have received the payment within 1,5 hours (not guaranteed for the
beneficiary). Therefore Urgent Domestic payments are a separate type of payment from Urgent
Europayments.
Both Worldpayments and Urgent Europayments are processed equally (using the same fields/tags) and
sent as urgent payments, the difference being that Worldpayments will by default always be treated as
urgent payments whereas for Urgent Europayments it is mandatory to indicate that these
(Euro)payments must be treated as urgent payments.
Between Urgent Domestic Europayments and Urgent Europayments there are a few differences in
which fields/tags must be used and filled, these differences can be found in the Description column of
chapter 4.2 PaymentInformationSegment from page 12 onwards.
1.2.5 Message structure

A Generic Payment File message contains 3 segments/building blocks:
1. Group Header;
This building block is mandatory and present once. It contains elements such as Message
Identification, Creation Date and Time.
2. Payment Information (this segment/building block is also referred to as “batch” level;
This building block is mandatory and repetitive. Besides elements related to the debit side of
the transaction, such as Debtor and Payment Type Information, it contains one or more
Transaction Information Blocks.
3. (Credit Transfer) Transaction Information, this segment/building block is also referred to as
“payment” level;
This building block is mandatory and repetitive. It contains, amongst others, elements related
to the credit side of the transaction, such as Creditor and Remittance Information. The number
of occurrences of Payment Information Block and Transaction Information Block within a
message is indicated by the Grouping field in the Group Header.
Every segment/building block within the Generic Payment File must be opened and closed according
to the XSD definition. Between the opening tag and closing tag the information for this tag is
contained.
A XML-pain.001.001.03 file/message has the following structure:
2 Payment determination
This chapter provides information about the way in which Rabobank will determine and process
payments on Payment Information Segment level and Transaction Information Segment level, called
Batch level and Payment level respectively. Details about the index numbers used in the schema
below can be found in the next chapter 3 Segment description.
2.1 Processing schema
Batch level Payment level

PaymentTypeInformation (2.6) PaymentTypeInformation (2.31)
ServiceLevel Code ServiceLevel Code How payments will be processed
Empty or SEPA Empty or SEPA Only to be used for Europayments. Not allowed for
Worldpayments, Mu;tibank payments, Urgent
Europayments, and Urgent Domestic
Europayments, these will be rejected
Other value than SEPA Payment containing ServiceLevel code other than
SEPA will be rejected
NURG or SDVA Empty Only allowed for Worldpayments and Multibank
payments
Any value No ServiceLevel code allowed on Payment level
URGP Empty Only allowed for Worldpayments, Multibank
payments, Urgent Domestic Europayments and
Urgent Europayments.
Any value No ServiceLevel code allowed on Payment level
3 Segment description
This chapter describes all tags/fields which are relevant to Europayments, Urgent Europayments, Urgent Domestic Europayments, Worldpayments and Multibank
payments. Tags/fields which are supported in the pain.001.001.03 format but are not used or supported by Rabobank are omitted. If such fields are present in the file
they will be ignored but have to comply with XSD.
3.1 Group Header
Worldpayments + Urgent Europayments

Urgent Domestic Europayments
Multibank payments
Europayments
Name ISO- XML-tag Level Presence Type Length Description
ref.
Document <Document> Top [1..1] X X X X
<CstmrCdtTrfInitn> Top [1..1] X X X X
GroupHeader 1.0 <GrpHdr> Top [1..1] X X X X
MessageIdentification 1.1 <MsgId> 1 [1..1] Alphanumeric Max. 35 Unique file identification. X X X X
CreationDateTime 1.2 <CreDtTm> 1 [1..1] Date and Creationdate and –time of the file. X X X X
time Example: “2017-02-28T09:10:15”.
NumberOfTransactions 1.6 <NbOfTxs> 1 [1..1] Numeric Max. 15 Number of payments in the file. X X X X
ControlSum 1.7 <CtrlSum> 1 [0..1] Numeric Max. 18 Total/sum of all the individual payments, regardless X X X X
of the currency.
Decimals are separated by a point “.”.
InitiatingParty 1.8 <InitgPty> 1 [1..1] X X X X
Name <Nm> 2 [0..1] Alphanumeric Max. 70 Name of the ordering party. X X X X
Identification <Id> 2 [0..1] This tag/field is ignored for Worldpayments, X
Multibank payments, Urgent Europayments and
Multibank payments
Europayments
ref.
Urgent Domestic Europayments.
For Europayments please refer to appendix A.
3.2 Payment Information Segment

Multibank payments
Europayments
ref.
PaymentInformation 2.0 <PmtInf> Top [1..n] X X X X
PaymentInformationIdentification 2.1 <PmtInfId> 1 [1..1] Alphanumeric Max. 35 Unique reference number for the batch/PI. X X X X
For Worldpayments, Multibank payments, Urgent

Europayments and Urgent Domestic Europayments
this information is not presented in the account
information (account statements, account
information download formats).
PaymentMethod 2.2 <PmtMtd> 1 [1..1] Alphanumeric 3 Fixed mandatory value ‘TRF’ for payments. X X X X
BatchBooking 2.3 <BtchBookg> 1 [0..1] Boolean 4 or 5 When the value ‘true’ is provided for Europayments, X
only the total amount will be shown in one debit
transaction in the account information.
When the value ‘false’ is provided all Europayments
will be presented individually in the account
information.
When this tag is not provided Rabobank will use the
value ‘true’ when processing the Europayments.
Note: in case of value ‘false’, there is a maximum of

5.000 payments per batch. In case the batch exceeds
the maximum of 5.000, the batch will be rejected.
this tag is ignored, regardless if a value is provided all
Multibank payments
Europayments
ref.
payments will be presented individually in the
account information.
NumberofTransactions 2.4 <NbOfTxs> 1 [0..1] Numeric Max. 15 Number of payents in the batch/PI. X X X X
ControlSum 2.5 <CtrlSum> 1 [0..1] Amount Max. 18 Total/sum of all the individual payments in the batch X X X X
(this segment).
Decimals are separated by a point “.”.
PaymentTypeInformation 2.6 <PmtTpInf> 1 [0..1] The subtags below may either be present on this X X X X
level or on batch level (2.31), unless otherwise
described.
InstructionPriority 2.7 <InstrPrty> 2 [0..1] Alphanumeric 4 Any value specified will be ignored during
processing, even if the value contradicts the value
which is provided in tag 2.9 <Cd>. For Europayments
the value NORM is commonly used (however, as
mentioned, any value specified will be ignored).
ServiceLevel 2.8 <SvcLvl> 2 [0..1] For Europayments this tag is not mandatory and SEPA X X X X
may be presented on this (batch) level via 2.9 <Cd>
or on 2.34 payment level, but not on both levels;
For Worldpayments, Urgent Europayments, Urgent

Domestic Europayments and Multibank payments it
is mandatory to provide this tag for processing these
payments in the Rabobank payment processing
systems.
Code 2.9 <Cd> 3 [1..1] Alphanumeric 4 The Rabobank only accepts one of the following X X X X
values: NURG, URGP, SDVA, SEPA.
- SEPA for Europayments
Multibank payments
Europayments
ref.
- URGP for Urgent Domestic Europayments and
Urgent Europayments.
- SDVA, NURG and URGP 1 for Worldpayments and
Multibank Payments

Domestic Payments and Multibank payments it is
mandatory to provide one of the mentioned values.
When the Servicelevel/Code is omitted all payments
will be processed as Europayments and consequently
be rejected.
This tag/field may only be provided on (this) batch level .
LocalInstrument 2.11 <LclInstrm> 2 [0..1] This field/tag and underlying fields/tags are only used X
for Europayments. For Worldpayments, Urgent
Europayments, Urgent Domestic Europayments and
Multibank payments this field/tag will be ignored.
Code 2.12 <Cd> 3 [1..1] {OR Alphanumeric Max. 35 For Europayments within The Netherlands only the X
value ‘ACCEPT’ is allowed and relayed to the bank of
the beneficiary, provided that the tag/field
BatchBooking contain the value ‘false’.
Should the tag/field contain the value ‘true’ and
LocalInstrument/Code contain the value ‘ACCEPT’ the
batch will be rejected.
1
Worldpayments are always processed by Rabobank as urgent payments, provided that these payments are provided before cut-off time and correctly (Straight Through Processing, i.e. without manual intervention or correction by
Rabobank); it remains possible to indicate that Worldpayments are to be processed as urgent payments, but regardless of the value provided all such payments are processed as urgent payments by default.
Multibank payments
Europayments
ref.
This tag can be presented on batch/PI level or on
payment level (2.37), but not on both levels.
Other values for this tag will be ignored.
Proprietary 2.13 <Prtry> 3 [1..1] OR} Alphanumeric Max. 35 This information is not used for processing X
CategoryPurpose 2.14 <CtgyPurp> 2 [0..1] For Worldpayments, Urgent Europayments and X X
Urgent Domestic Europayments this field/tag and
underlying fields/tags will be ignored.
Code 2.15 <Cd> 3 [1..1] {OR Alphanumeric 4 Rabobank accepts and forwards all ISO Category X X
Purpose codes to the bank of the beneficiary.
This tag can be presented on batch/PI level or on
payment level (2.40), but not on both levels.
For Europayments only code ‘SALA’ for salary

payments on batch level is being used by Rabobank
to process and present these payments separately.
When using code ‘SALA’ on batch level combined
with BatchBooking ‘true’, only the total debited
amount will be shown in the account information (no
individual salary payments will be available). Also
insight of transactions in the batch can only be
viewed before and during signing by users who are
specifically authorized to view salary payments.
For Multibank payments: the code ‘INTC’ will be used

by Rabobank for Multibank payments, other codes
will be forwarded to the Servicing bank (where the
payment will be processed).
Multibank payments
Europayments
ref.
Proprietary 2.16 <Prtry> 3 [1..1] OR} Alphanumeric Max. 35 With Europayments and Multibank payments the X X
information provided in this field will be forwarded to
the receiving bank.
For Multibank payments this field can be used to

provide codewords which are not available in the
CategoryPurpose list (f.e. OTHR/ABCD).
Rabobank ignores the value provided in this field for
Worldpayments, Urgent Europayments and Urgent
Domestic Europayments.
This tag/field can be presented on batch/PI level or

on payment level (2.41), not on both levels.
RequestedExecutionDate 2.17 <ReqdExctnDt> 1 [1..1] Date This is the date on which the originator’s account is X X X X
to be debited. When a date is provided which is until
14 days in the past this date is changed by Rabobank
to the first possible processing date; when a date is
provided which is older than 14 days the batch will
be rejected.
It is possible to provide a date for future processing
until 365 calendar days.
Debtor 2.19 <Dbtr> 1 [1..1] X X X X
Name <Nm> 2 [1..1] Alphanumeric Max. 70 The name of the initiating party is mandatory. For X X X X
Urgent Domestic Europayments the name provided
in this tag/field will be used;
Multibank payments
Europayments
ref.
For Europayments, Worldpayments, Multibank
payments and Urgent Domestic Europayments the
name provided will be overwritten with the statutory
name as registered for the account by Rabobank.
PostalAddress <PstlAdr> 2 [0..1] For Europayments and Urgent Domestic X X X X
Europayments the fields Country and AddressLine are
available, these are not mandatory.
For Worldpayments, Urgent Europayments and

Multibank payments the fields StreetName, PostCode,
TownName en Country are available.
StreetName <StrtNm> 3 [0..1] Alphanumeric Max. 70 This field is only used for Worldpayments, Urgent X X
Europayments and Multibank payments
PostalCode <PstCd> 3 [0..1] Alphanumeric Max. 16 This field is only used for Worldpayments, Urgent X X
TownName <TwnNm> 3 [0..1] Alphanumeric Max. 35 This field is only used for Worldpayments, Urgent X X
Country <Ctry> 3 [0..1] Alphanumeric 2 Country where the initiating party resides, used for X X X X
Europayments, Urgent Domestic Europayments,
Urgent Europayments, Worldpayments and
Multibank payments.
AddressLine <AdrLine> 3 [0..2]1 Alphanumeric Max. 70 Address of the initiating party, used for X X
Europayments and Urgent Domestic Europayments:
1e line: Street and house number
2e line: Postal code and city.
1
The ISO20022 standard allows up to 7 address lines, however the EPC has limited the number of lines to 2 address lines.
Multibank payments
Europayments
ref.
For Urgent Domestic Europayments only the first 35

positions from the 1 st address line will be used and
the first 35 positions from the 2 nd address line. The
positions after the 35 th position on the 1 st and 2nd
address lines will be ignored.
Identification <Id> 2 [0..1] This tag/field is ignored for Worldpayments, Urgent X
Europayments, Urgent Domestic Europayments and
Multibank payments.
For Europayments please refer to appendix A.
DebtorAccount 2.20 <DbtrAcct> 1 [1..1] X X X X
Identification <Id> 2 [1..1] X X X X
IBAN <IBAN> 3 [1..1] {OR Alphanumeric Max. 34 IBAN account number of the initiating party. Only use X X X X
numbers and capital letters in the IBAN, usage of
spaces is not allowed.
Other <Othr> 3 [0..1] OR} X
Identification <Id> 4 [1..1] Alfanumeriek Max. 34 This field is only allowed for Multibank payments, and X
when specified may only contain a BBAN. It is not
allowed for Multibank payments to provide a value
for both this field <Id> as well as the <IBAN> field.
Currency <Ccy> 2 [0..1] Alphanumeric 3 ISO currency code of the account. X X X X
For Europayments, Urgent Europayments, Urgent

Domestic Europayments and Multibank payments
the currency code of the account is not mandatory.
For Worldpayments it is mandatory to provide the
Multibank payments
Europayments
ref.
currency code of the account in this tag/field.
- When the currency code of the account is provided,

the following rules apply:
EUR-account, payment currency non-EUR, is allowed
(will be processed).
USD-account (example), payment currency JPY: will
be processed for Rabobank WRR 1 accounts.
USD-account (example), payment currency JPY: will
not be processed for Rabobank (Nederland) 2
accounts, the payment will be rejected.
DebtorAgent 2.21 <DbtrAgt> 1 [1..1] X X X X
FinancialInstitutionIdentification <FinInstnId> 2 [1..1] X X X X
BIC <BIC> 3 [0..1] {OR Alphanumeric 8 of 11 SWIFT BIC code from the bank of the initiating party. X X X X
This field/tag is optional [0..1] however necessary
(and therefore mandatory) for Multibank payments
when the account of the initiating party is held with a
bank outside of the SEPA area . Only numbers and
capital letters are allowed.
Other <Othr> 3 [0..1] OR} X X X X
Identification <Id> 4 [1..1] Alphanumeric 11 When present, i.e. when no BIC has been provided, X X X X
Rabobank advises to provide the value
1
Wholesale and Rural refers to the Rabobank Current Account system for customers from (previously called) Rabobank International, for accounts in this system it is possible to transfer an amount using a currency amount which is
different from the currency of the account itself.
2
The Current Account system for customers from Rabobank Memberbanks (previously called) Rabobank The Netherlands where, contrary to Wholesale and Rural accounts, it is not allowed to transfer an amount in a currency that
is different from the currency of the account itself.
Multibank payments
Europayments
ref.
‘NOTPROVIDED’ in this field, however this value is not
validated by Rabobank.
UltimateDebtor 2.23 <UltmtDbtr> 1 [0..1] This field/tag and underlying fields/tags are ignored X
for Worldpayments, Urgent Europayments, Urgent
Domestic Payments and Multibank payments.
This element may not be present together with
element 2.70. Both elements may be absent.
Name <Nm> 2 [0..1] Alphanumeric Max. 70 Name of the (ultimate) initiating party. This name is
transferred to the bank of the beneficiary.
Identification <Id> 2 [0..1] For Europayments please refer to appendix A. X
ChargeBearer 2.24 <ChrgBr> 1 [0..1] Alphanumeric 4 - For Europayments only the value ‘SLEV’ is X X X X
allowed.
- For Urgent Domestic Payments, Urgent

Europayments, Worldpayments and
Multibank payments within the EER only the
value ‘SHAR’ is allowed.
- For all other Worldpayments and Multibank

payments the following values are allowed:
CRED - all costs for the beneficiary (BEN)
DEBT - all costs for the initiating party (OUR)
SHAR - costs are shared between the
initiating party and the beneficiary (SHA)
Note: When no value is provided the option
SHAR will be used.
Multibank payments
Europayments
ref.
ChargeBearer may be present on this level or

transaction level (2.51) but not on both levels.
3.3 Transaction Information Segment

Multibank payments
Europayments
ref.
CTTransactionInformation 2.27 <CdtTrfTxInf> 1 [1..n] X X X X
PaymentIdentification 2.28 <PmtId> 2 [1..1] This tag/field and underlying tags/fields are used for X X X X
Europayments, and will be ignored for
Worldpayments, Multibank payments, Urgent Urgent
Multibank payments
Europayments
ref.
Europayments and Urgent Domestic Europayments.
Important: Because of the fact that this tag/field is

mandatory, according to the [1..1] presence (XSD) a
value must be provided for Worldpayments, Multibank
payments, Urgent Europayments and Urgent
Domestic Europayments in the underlying tag/field
<EndToEndId> even though this value will not be
used when processing these payments.
InstructionIdentification 2.29 <InstrId> 3 [0..1] Alphanumeric Max. 35 Instructions from the initiating party for Rabobank. X
This tag/field is not forwarded to the bank of the
beneficiary.
EndToEndIdentification 2.30 <EndToEndId> 3 [1..1] Alphanumeric Max. 35 End-to-End ID for the payment, will be forwarded to X X X X
the beneficiary bank for Europayments.
Note: the payment order will be rejected when this
tag is only filled with one or more spaces.
PaymentTypeInformation 2.31 <PmtTpInf> 2 [0..1] The subtags below may either be present on this level X X
or on batch level (2.6), unless otherwise described.
InstructionPriority 2.32 <InstrPrty> 3 [0..1] Alphanumeric 4 Either the value ‘NORM’ or ‘HIGH’ is allowed.
The value specified will be ignored during processing.
ServiceLevel 2.33 <SvcLvl> 3 [0..1] X
Code 2.34 <Cd> 4 [0..1] Alphanumeric 4 For Europayments via Generic Payment File this tag is X
not mandatory and may be presented on this
(payment) level or on 2.8 batch level, but not on both
levels.
When specified on this level for Europayments, only
the value SEPA is allowed.
Multibank payments
Europayments
ref.

Domestic Payments and Multibank payments it is not
allowed to provide a value for this tag/field, for these
payments it is only allowed to provide a value on 2.9
batch level.
CategoryPurpose 2.39 <CtgyPurp> 3 [0..1] For Worldpayments, Urgent Europayments and Urgent X X
Domestic Europayments this field/tag and underlying
fields/tags will be ignored.
Code 2.40 <Cd> 4 [1..1] {OR Alphanumeric 4 Rabobank accepts and forwards all ISO Category X X
Purpose codes to the bank of the beneficiary.
This tag can be presented on batch/PI level (2.15) or
on payment level, but not on both levels.
For Europayments, specifically salary payments, code

‘SALA’ must be supplied on batch level (see tag 2.15)
so that Rabobank can offer a separate process and
presentation. Rabobank does not offer this when code
‘SALA’ is supplied on payment level. This means that
users without specific salary authorization can view
these payments.
For Multibank payments:
The code ‘INTC’ will be used by Rabobank for
Multibank payments, other codes will be forwarded to
the Servicing bank (where the payment will be
processed).
Multibank payments
Europayments
ref.
For Worldpayments towards a Multibank account:
The code ‘INTC’ will only be used when the Rabobank
recognizes the beneficiary account to be a Multibank
account.
Proprietary 2.41 <Prtry> 4 [1..1] OR} Alphanumeric Max. 35 With Europayments and Multibank payments the X X
information provided in this field will be forwarded to
the receiving bank, for Multibank payments this field
can be used to provide codewords which are not
available in the CategoryPurpose list (f.e. OTHR/ABCD).
Only the first codeword will be forwarded to the
receiving bank.
Rabobank ignores the value provided in this field for

Worldpayments, Urgent Europayments and Urgent
Domestic Europayments.
This tag/field can be presented on batch/PI level (2.16)

or on payment level, not on both levels.
Amount 2.42 <Amt> 2 [1..1] X X X X
InstructedAmount 2.43 <InstdAmt> 3 [1..1] Amount Max. 18 Amount of the payment. Decimals are separated with X X X X
a point “.”. The amount provided must be a value
between 0.01 and 999,999,999.99 (technical limit),
where the ‘real’ possible upper limit is determined by
regulatory restrictions for the selected payment type.
Multibank payments
Europayments
ref.
The currency for the amount must be provided within the
tag: <InstdAmt Ccy=”XXX”> where XXX must be a valid
ISO currency code (f.e. EUR, USD, GBP, JPY, etc.).
ChargeBearer 2.51 <ChrgBr> 2 [0..1] Alphanumeric 4 - For Europayments only the value ‘SLEV’ is X X X X
allowed.
- For Urgent Domestic Payments, Urgent

Europayments, Worldpayments and
Multibank payments within the EER only the
value ‘SHAR’ is allowed.
- For all other Worldpayments and Multibank

payments the following values are allowed:
CRED - all costs for the beneficiary (BEN)

DEBT - all costs for the initiating party (OUR)
SHAR - costs are shared between the initiating
party and the beneficiary (SHA)
Note: When no value is provided the option
SHAR will be used.
ChargeBearer may be present on this level or batch

(2.24) but not on both levels.
Ultimate Debtor 2.70 <UltmtDbtr> 2 [0..1] This tag/field and underlying tags/fields are ignored X
(not used) for Worldpayments, Multibank payments,
Urgent Europayments and Urgent Domestic
Multibank payments
Europayments
ref.
Europayments.
This element may not be present together with

element 2.23. Both elements may be absent.
Name <Nm> 3 [0..1] Alphanumeric Max. 70 Name of the ultimate debtor (ultimate initiating party). X
The information provided in this tag/field will not be
sent to the bank of the beneficiary.
Identification <Id> 3 [0..1] Please refer to appendix A. X
IntermediaryAgent1 2.71 <IntrmyAgt1> 2 [0..1] This tag/field can only be used for Worldpayments X
and is required when specific routing of the payment
is required by the bank of the beneficiary. Usage of
this tag/field will result in extra charges.
For Multibank payments, Europayments and Urgent
Domestic Europayments this tag/field is ignored.
FinancialInstitutionIdentification <FinInstnId> 3 [1..1] X
BIC <BIC> 4 [1..1] Alphanumeric Max 11 SWIFT BIC code of the bank of the intermediary agent. X
Only numbers and capital letters are allowed.
ClearingSystemMember <ClrSysMmbId> 4 [0..1] Data from the underlying tags only used when the bank X
Identification (intermediary) cannot be retrieved from the provided BIC
or name and location.
ClearingSystemIdentification <ClrSysId> 5 [1..1] This field is mandatory to identify the MemberID. X
Code <Cd> 6 [1..1] Alphanumeric Max 35 The bank code provided via this tag/field must be the X
code of the bank in the country where the bank
resides, for example ‘USABA’ for an ABA number for a
payment towards a bank in the United States.
Multibank payments
Europayments
ref.
A list of permitted National Bank codes can be found
in ‘Appendix B – Payment information per country’.
Only codes mentioned in the Appendix may be used.
Codes which are not mentioned in the appendix will
be rejected.
Rabobank will not check if the bank code provided is a

valid bank code, i.e. if the bank code matches with the
provided BIC of the beneficiary bank. This tag/field will
be relayed.
MemberIdentification <MmbId> 5 [1..1] Alphanumeric Max 35 The national bank code for the “Clearing System” bank X
in the country where the intermediary bank resides.
Specifications of which the National Bank Codes must

fulfill can be found in ‘Appendix B – Payment information
per country’.
CreditorAgent 2.77 <CdtrAgt> 2 [0..1] For Europayments and Urgent Domestic X X X X
Europayments: Only BIC may be provided.
For Worldpayments, Multibank payments and Urgent

Europayments: Rabobank strongly recommends to
provide the BIC. When the BIC is not provided, it is
mandatory to provide the name, country code and the
townname from the bank of the beneficiary.
If the BIC is not provided or the beneficiary’s bank
does not have a BIC, it is highly recommended to
supply the National Bank Code in tags
Multibank payments
Europayments
ref.
ClearingSystemIdentification and MemberId.
When 2.71 IntermediaryAgent1 information is

provided the payment will be routed accordingly;
when no inf1ormation is provided via this tag/field,
the payment will be routed via the CreditorAgent.
Note: additional costs will be charged if no BIC is

provided.
FinancialInstitutionIdentification <FinInstnId> 3 [1..1] X X X X
BIC <BIC> 4 [0..1] Alphanumeric 8 of 11 SWIFT BIC code from the bank of the beneficiary. X X X X
Usage of this tag/field is optional. Only numbers and
capital letters are allowed.
For Europayments:
Rabobank will always determine the BIC from the bank
of the beneficiary; when the BIC can be determined,
the BIC provided via this tag/field will be overwritten
with the determined BIC; When Rabobank cannot
determine the BIC, the BIC specified via this tag/field
will be used; Should the BIC be invalid, the payment
will be rejected.

Europayments and Urgent Domestic Payments:
When no BIC is specified Rabobank will try to
determine the BIC from the bank of the beneficiary,
Multibank payments
Europayments
ref.
and when the BIC can be found/determined it will be
used for the payment; When no BIC is specified and
Rabobank is not able to determine the BIC, the name
country code and town name from the bank of the
beneficiary will be used for the payment; When no BIC
is provided, and no name and country code (from the
beneficiary bank) are provided, the payment will be
rejected.
ClearingSystemMember <ClrSysMmbId> 4 [0..1] This tag/field may only be used for Worldpayments X
Identification and Urgent Europayments.
Rabobank will determine the National Bank Code on

the basis of the specified IBAN or BBAN. If this cannot
be derived, Rabobank uses the supplied National Bank
Code to determine the BIC. Irrespective of whether or
not Rabobank uses the information provided, it must
comply with the XSD.
ClearingSystemIdentification <ClrSysId> 5 [1..1] This field is mandatory to identify the MemberID. X
Code <Cd> 6 [1..1] Alphanumeric Max. 5 The bank code provided via this tag/field must be the X
code of the bank in the country where the bank
resides, for example ‘USABA’ for an ABA number for a
payment towards a bank in the United States.
A list of permitted National Bank Codes can be found

in ‘Appendix B – Payment information per country’.
Multibank payments
Europayments
ref.
Only codes mentioned in the Appendix may be used.
Codes which are not mentioned in the appendix will
be rejected.
Rabobank will not check if the bank code provided is a

valid bank code, i.e. if the bankcode matches with the
provided BIC of the beneficiary bank. This tag/field will
be relayed.
MemberIdentification <MmbId> 5 [1..1] Alphanumeric Max. 35 The national bank code for the “Clearing System” bank X
in the country where the bank of the beneficiary
resides.
Specifications of which the National Bank codes must

fulfill can be found in ‘Appendix B – Payment
information per country’.
Name <Nm> 4 [0..1] Alphanumeric Max. 35 Name of the bank of the beneficiary. For X
Worldpayments, Multibank payments and Urgent
Europayments it is mandatory to provide this name
when no BIC is provided.
PostalAddress <PstlAdr> 4 [1..1] X
Country <Ctry> 5 [1..1] Alphanumeric 2 Country code of the country where the bank of the X
beneficiary resides. For Worldpayments, Multibank
payments and Urgent Europayments it is mandatory
to provide this code when no BIC is provided.
AddressLine <AdrLine> 5 [0..2] Alphanumeric Max. 70 Address details of the bank of the beneficiary. X
The townname of bank beneficiary must at least be
provided.
Multibank payments
Europayments
ref.
Please note! Only the first 35 positions from the 1 st

and 2nd address lines will be used. The positions after
the 35th position on the 1 st and 2nd address lines will
be ignored.
Creditor 2.79 <Cdtr> 2 [1..1]1 X X X X
Name <Nm> 3 [1..1] Alphanumeric Max. 70 Name from the beneficiary, mandatory for all payment X X X X
types.
Note: for payments from RNB accounts applies that

the name of the Creditor have a maximum length of
35. If exceeding, the payment will be rejected.
PostalAddress <PstlAdr> 3 [0..1] For Europayments and Urgent Domestic Euro- X X X X
payments fields Country and AddressLine must be
used but are not mandatory, except for ‘Country’ for
Urgent Domestic Europayments.

Europayments the fields StreetName, PostCode,
TownName and Country must be used but are not
mandatory except for ‘Country’.
Please note: it is highly recommended to provide

postal address information because of inquiries in
case the information is not complete.
1 This tag/field is optional according to the ISO20022 standard, however Rabobank requires (i.e. mandatory) that the field is present.
Multibank payments
Europayments
ref.
StreetName <StrtNm> 4 [0..1] Alphanumeric Max. 70 This tag/field is used for Worldpayments, Multibank X X
payments and Urgent Europayments. If filled, it must
contain the location address. It is not allowed to
specify a postal box address.
PostalCode <PstCd> 4 [0..1] Alphanumeric Max. 16 This tag/field is used for Worldpayments, Urgent X X
TownName <TwnNm> 4 [0..1] Alphanumeric Max. 35 This tag/field is used for Worldpayments, Urgent X X
Country <Ctry> 4 [0..1] Alphanumeric 2 Country code of the country where the beneficiary X X X X
resides.
This field is mandatory for Urgent Europayments,
Urgent Domestic Europayments, Worldpayments and
Multibank payments.
AddressLine <AdrLine> 4 [0..2] Alphanumeric Max. 70 Address information of the beneficiary, only used for X X
For Europayments max. 2x70 positions:
1st line: Street and house number
2nd line: Postal code (zipcode) and city
For Urgent Domestic Europayments:

Please note!: Only the first 35 positions from the 1 st
and 2nd address lines will be used. The positions after
the 35th position on the 1 st and 2nd address lines will
be ignored.
Identification <Id> 3 [0..1] This tag/field is only used for Europayments. Please X
refer to appendix A.
Creditor Account 2.80 <CdtrAcct> 2 [1..1] X X X X
Multibank payments
Europayments
ref.
Identification <Id> 3 [1..1] X X X X
IBAN <IBAN> 4 [0..1] {OR Alphanumeric Max. 34 IBAN account number of the beneficiary. Only use X X X X
numbers and capital letters in the IBAN, usage of
spaces is not allowed.
For Europayments it is mandatory to provide the IBAN

of the beneficiary, when the IBAN is omitted the
payment will be rejected.
Other <Othr> 4 [0..1] OR} Only allowed for Woldpayments, Multibank payments X X
and Urgent Europayments
Identification <Id> 5 [1..1] Alphanumeric Max. 34 Account number of the beneficiary. X X
When a BBAN is specified for a country where usage of
an IBAN is mandatory the payment will be rejected.
Currency <Ccy> 3 [0..1] Alphanumeric 3 ISO currency code for the account. X X X X
Name <Nm> 2 [0..1] Alphanumeric Max. 70 X X X X
Ultimate Creditor 2.81 <UltmtCdtr> 2 [0..1] This tag/field and underlying tags/fields will be X
ignored for Worldpayments, Multibank payments,
Urgent Europayments and Urgent Domestic
Europayments
Name <Nm> 3 [1..1] Alphanumeric Max. 70 Name of the ultimate beneficiary. X
Country <Ctry> 4 [1..1] Alphanumeric 2 Country of the ultimate beneficiary. X
AddressLine <AdrLine> 4 [0..2] Alphanumeric Max. 70 Address information of the ultimate beneficiary. X
Identification <Id> 3 [0..1] Please refer to appendix A. X
Purpose 2.86 <Purp> 2 [0..1] This tag/field and underlying tags/fields are ignored X
for Worldpayments, Multibank payments, Urgent
Multibank payments
Europayments
ref.
Code 2.87 <Cd> 3 [1..1] Alphanumeric 4 The list of allowed purpose codes can be found here: X
http://www.iso20022.org/external_code_list.page
tab ’11-Purpose’.
RemittanceInformation 2.98 <RmtInf> 2 [0..1] For Europayments either the Structured or X X X X
Unstructured tags/fields may contain a value, not
both. When both Structured and Unstructured
tags/fields contain a value the payment will be
rejected.

only the Unstructured tag/field may contain a value;
when the Structured tag/field contains a value, this
value will be ignored.
Unstructured 2.99 <Ustrd> 3 [0..1] {OR Alphanumeric Max. 140 For Europayments all 140 positions will be read and X X X1 X
processed.
For Urgent Domestic Europayments only the first 96

positions will be read and processed.

Europayments only the first 98 positions will be read
and processed.
Please note: For all payments/payment types there is
Multibank payments
Europayments
ref.
a maximum of only one (1) Unstructured remittance
line.
Structured 2.100 <Strd> 3 [0..1] OR} Structured remittance information is only allowed for X
Europayments.

this tag/field is ignored.
CreditorReferenceInformation 2.120 <CdtrRefInf> 4 [0..1] X
Type 2.121 <Tp> 5 [1..1] X
CodeOrProprietary 2.122 <CdOrPrtry> 6 [1..1] X
Code 2.123 <Cd> 7 [1..1] Alphanumeric 4 Only ‘ SCOR’ is allowed. X
Issuer 2.125 <Issr> 6 [0..1] Alphanumeric Max. 35 Value CUR, ISO, BBA and other issuers are allowed. X
Rabobank does not check the content.
Reference 2.126 <Ref> 5 [1..1] Alphanumeric Max. 35 The max. length of Currence payment reference is 16. X
The max. length of ISO payment reference is 25 and
starts with RF.
The length of Belgium payment reference is 12.
Other/own payment reference have a max length of 35.
Rabobank does not check the content.
Appendix A – Party identifier

This appendix describes how the Party Identifier should be filled.
The described structure is applicable for the following fields:
1.8 2.19 2.23 2.70 2.79 2.81
Organisation Identification
For the identification of the organization the BIC must be filled. The three columns to the right indicate for each scenario whether the Party Identifier information is
passed on to the beneficiary bank (X) or ignored and not passed on (-).
Name XML-tag level Presence Type Length Description

OrganisationIdentification <OrgId> +1 [1..1]
BICorBEI <BICOrBEI> +2 [0..1] {OR Alphanumeric 11 BIC of the organization
Other <Othr> +2 [0..1] OR}
Identification <Id> +3 [1..1] Alphanumeric 35
SchemeName <SchmeNm> +3 [0..1]
Code <Cd> +4 [1..1] Alphanumeric 4 The ExternalOrganisationIdentification1Code
This code can be found on
tab ‘9-OrganisationIdentification’
Proprietary <Prtry> +4 [1..1] {OR Alphanumeric 35
Issuer <Issr> +3 [0..1] OR} Alphanumeric 35
Private identification
For the private identification the date and place of birth must be filled. In one occurrence you can use ‘other’. The three columns to the right indicate for each scenario
whether the information is passed on to the beneficiary bank (X) or ignored and not passed on (-).
Name XML-tag level Presence Type Length Description

Private Identification <PrvtId> +1 [1..1]
Date And Place Of Birth <DtAndPlcOfBirth> +2 [0..1]
Birth date <BirthDt> +3 [1..1] Date 10
Province of Birth <PrvcOfBirth> +3 [0..1] Alphanumeric 35
City of Birth <CityOfBirth> +3 [1..1] Alphanumeric 35
Country of Birth <CtryOfBirth> +3 [1..1] Alphanumeric 2 ISO country code
Other <Othr> +2 [0..1]
Identification <Id> +3 [1..1] Alphanumeric 35
Scheme Name <SchmeNm> +3 [0..1]
Code <Cd> +4 [1..1] {OR Alphanumeric 4 The ExternalPersonIdentification1Code
This code can be found on
tab ’10-PersonIdentification’
Proprietary <Prtry> +4 [1..1] OR} Alphanumeric 35
Issuer <Issr> +3 [0..1] Alphanumeric 35
Appendix B – Payment information per country
A national bank code uniquely identifies a bank or bank branch. For SEPA payments, providing a national bank code with your payment is not necessary as the IBAN is
mandatory. A national bank code is available within the IBAN. The same is true for countries outside of the SEPA area that use the IBAN account format. Please refer to
the IBAN registry available - here - for an overview of countries that use the IBAN as account number format.
For non-SEPA payments, providing a national bankcode can be essential. If BIC is not provided or beneficiary’s bank has no NIC then it is highly recommended to
supply the National Bank Code.
The table1 below gives an overview of the Clearing Systems that are registered with ISO, including the corresponding specifications of which the bank code must
meet. Information is extracted from the ISO External code list which can be found on http://www.iso20022.org/external_code_list.page see
tab '5- ClearingSystemIdentification'.
Please note: only National Bank Codes mentioned in the table underneath are used for processing. National Bank Codes which are also registered by ISO but not
listed in the table are JPZGN (Japan), SGIBG (Singapore), THCBC (Thailand), SESBA (Sweden), USPID (United States), CHSIC (Switzerland) and TWNCC (Taiwan). If one of
these National Bank Codes is provided, it will be ignored and not used for processing.
For other payment information of countries mentioned in the table and information of countries which are not mentioned in the table, please refer to the webpage
where payment information is described per country: https://www.rabobank.nl/particulieren/betalen/betalen-buitenland/betalingsinformatie/ (Dutch language only).
Country Country Content tag 2.71 and tag 2.77 Content tag 2.71 and 2.77 Member Remarks
code Clearing System Identification Identification
Abbreviation National Bank Code Length Type

Australia AU AUBSB Fixed length 6 Numbers Australian Bank State Branch Code (BSB-code): Bank Branch code
used in Australia.
Austria AT ATBLZ Fixed length 5 Numbers Austrian BankLeitZahl: Bank Branch code used in Austria.
Canada CA CACPA Fixed length 9 Numbers Canadian Payments Association Payment Routing Number: Bank
Branch code used in Canada.
China CN CNAPS Fixed length 12 Numbers CNAPS Identifier: Bank Branch code used in China.
Germany DE DEBLZ Fixed length 8 Numbers German BankLeitzahl: Bank Branch code used in Germany.
1
Updated on 7th December 2018.
Country Country Content tag 2.71 and tag 2.77 Content tag 2.71 and 2.77 Member Remarks
code Clearing System Identification Identification
Abbreviation National Bank Code Length Type

Greece GR GRBIC Fixed length 7 Numbers Helenic Bank Identification Code: Bank Branch code used in Greece.
Hong Kong HK HKNCC Fixed length 3 Numbers Hong Kong Bank Code: Bank Branch code used in Hong Kong.
India IN INFSC Fixed length 11 Numbers and letters Indian Financial System Code: Bank Branch code used in India.
Ireland IE IENCC Fixed length 6 Numbers Irish National Clearing Code: Bank Branch code used in Ireland.
Italy IT ITNCC Fixed length 10 Numbers Italian Domestic Identification Code: Bank Branch code used in Italy.
Liechtenstein LI CHBCC Length 3 or 5 Numbers Swiss Financial Institution Identification (short): Financial Institution
Identification (IID) used in Switzerland without check digits.
New Zealand NZ NZNCC Fixed length 6 Numbers New Zealand National Clearing Code: Bank Branch code used in
New Zealand.
Poland PL PLKNR Fixed length 8 Numbers Polish National Clearing Code: Bank Branch code used in Poland.
Portugal PT PTNCC Fixed length 8 Numbers Portuguese National Clearing Code: Bank Branch code used in
Portugal.
Russia RU RUCBC Fixed length 9 Numbers Russian Central Bank Identification Code: Russian Central Bank Id
Code.
South Africa ZA ZANCC Fixed length 6 Numbers South African National Clearing Code: Bank Branch code used in
South Africa.
Spain ES ESNCC Length 8 or 9 Numbers Spanish Domestic Interbanking Code: Bank Branch code used in
Spain.
Switzerland CH CHBCC Length 3 or 5 Numbers Swiss Financial Institution Identification (short): Financial Institution
Identification (IID) used in Switzerland without check digits.
United Kingdom GB GBDSC Fixed length 6 Numbers UK Domestic Sort Code: Bank Branch code used in the United
Kingdom.
United States US USABA Fixed length 9 Numbers United States Routing Number (Fedwire, NACHA): Routing Transit
number assigned by ABA for financial institutions in the United
States.
Example: National Bank Code of “Bank of New York Mellon”. The routing number is 021000018:
<ClrSysMmbId>
<ClrSysId>
<Cd>USABA</Cd>
</ClrSysId>
<MmbId>021000018</MmbId>
</ClrSysMmbId>
Example: National Bank Code of “Standard Chartered Bank branch London”. The Sort Code 60-91-04:
<ClrSysMmbId>
<ClrSysId>
<Cd>GBDSC</Cd>
</ClrSysId>
<MmbId>609104</MmbId>
</ClrSysMmbId>
Changelog
Titel : Format description Generic Payment File
Version : 1.9.3
Date : 25-02-2021
On behalf of : Rabo Direct Connect, SWIFT FileAct, Rabobank Internetbanking (Professional) and
Rabo Business Banking.
Date Version Change Reason

22-01-2019 1.8.3 Creditor Postal Address 2.79 Correction on subtag level: StreetName, Postal
correction. Code and Town Name are not mandatory.
17-04-2019 1.9 Appendix B changed. Some by ISO registered Clearing Systems will be
ignored when provided.
08-08-2019 1.9.1. Category Purpose Code 2.15 and 2.40 For Europayments: only code ‘SALA’ for salary
clarified. payments on batch level is being used by
Rabobank to process and present such
payments separately. Also insight of
transactions in the batch can only be viewed
before and during signing by users who are
specifically authorized to view salary payments.
18-01-2021 1.9.2 Added Rabo Business Banking This format description is also applicable for
Rabo Business Banking.
18-01-2021 1.9.2 EndToEndIdentification 2.30 note When this tag is only filled with one or more
added. spaces the payment order is rejected.
18-01-2021 1.9.2. Brexit update With effect from 1 January 2021 for SEPA
payment orders to the United Kingdom
Rabobank will pass on debtor’s address details,
known at Rabobank, to beneficiary’s bank.
25-02-2021 1.9.3. InstructionsForDebtorAgent 2.85 As of March 16, 2021 it is no longer possible to
removed. request for specific instructions for World-
payments and Urgent Europayments.
When this tag is provided it will be ignored
although it must be XSD compliant.
For specific routing of the payment tag 2.71

IntermediaryAgent1 can be used.
For a payment confirmation a copy of the
outgoing SWIFT message can be requested via
Rabo Business Banking (=RBB).
25-02-2021 1.9.3. CreditAgent 2.77 note added Additional costs will be charged if no BIC is
provided.

Format Description Generic Payment File (Pain.001)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Format Description Generic Payment File (Pain.001)

Uploaded by

Copyright:

Available Formats

Format description

Generic Payment File

Rabo Direct Connect,

1.1 General characteristics

This XSD can be obtained via https://www.iso20022.org/catalogue-messages/iso-20022-

1.2.2 Technical mapping

[0..1] Shows that the element can appear 0 or 1 time.

 Europayments - payments in EUR currency to a beneficiary in a

The following payments are supported for foreign non-Rabobank accounts:

 Multibank payments - payments from accounts held with other banks.

1.2.5 Message structure

A XML-pain.001.001.03 file/message has the following structure:

2.1 Processing schema

Batch level Payment level

3.1 Group Header

Worldpayments + Urgent Europayments

Worldpayments + Urgent Europayments

For Worldpayments, Multibank payments, Urgent

Note: in case of value ‘false’, there is a maximum of

For Worldpayments, Urgent Europayments, Urgent

- SEPA for Europayments

For Worldpayments, Urgent Europayments, Urgent

For Europayments only code ‘SALA’ for salary

For Multibank payments: the code ‘INTC’ will be used

For Multibank payments this field can be used to

This tag/field can be presented on batch/PI level or

For Worldpayments, Urgent Europayments and

For Urgent Domestic Europayments only the first 35

For Europayments, Urgent Europayments, Urgent

- When the currency code of the account is provided,

- For Urgent Domestic Payments, Urgent

- For all other Worldpayments and Multibank

ChargeBearer may be present on this level or

Worldpayments + Urgent Europayments

Important: Because of the fact that this tag/field is

For Worldpayments, Urgent Europayments, Urgent

For Europayments, specifically salary payments, code

Rabobank ignores the value provided in this field for

This tag/field can be presented on batch/PI level (2.16)

- For Urgent Domestic Payments, Urgent

- For all other Worldpayments and Multibank

CRED - all costs for the beneficiary (BEN)

ChargeBearer may be present on this level or batch

This element may not be present together with

Rabobank will not check if the bank code provided is a

Specifications of which the National Bank Codes must

For Worldpayments, Multibank payments and Urgent

When 2.71 IntermediaryAgent1 information is

Note: additional costs will be charged if no BIC is

For Worldpayments, Multibank payments, Urgent

Rabobank will determine the National Bank Code on

A list of permitted National Bank Codes can be found

Rabobank will not check if the bank code provided is a

Specifications of which the National Bank codes must

Please note! Only the first 35 positions from the 1 st

Note: for payments from RNB accounts applies that

For Worldpayments, Multibank payments and Urgent

Please note: it is highly recommended to provide

For Urgent Domestic Europayments:

For Europayments it is mandatory to provide the IBAN

For Worldpayments, Multibank payments, Urgent

For Urgent Domestic Europayments only the first 96