Format Description - Rabobank · Our reference Format Description ... 2 Clieop 03 Format 2.1 Clieop03 ... With regard to business payment instructions it is recommend that the creditor

1

Format Description

Version, date

Project

6, March 10, 2011

Rabo Cash Management

2

Colophon

Title Format Description

Version, date 6, March 10, 2011

Our reference Format Description COS

On behalf of Corporates, Operations & Services

Contact address Rabobank International,

UCR 191

Croeselaan 18,

Postbus 2626

3500 HG Utrecht

The Netherlands

Rabobank, 2011

No part of this publication may be reproduced in any form by print, photo print, microfilm or any other means without

written permission by Rabobank.

3

Contents

1 General information 4

2 Clieop 03 Format 5 2.1 Clieop03 Description 5 2.2 Structure of CLIEOP03 5 2.3 CLIEOP03 Info classification 8 2.4 CLIEOP03 Fields 12 2.5 CLIEOP03 validations by Rabobank 15

3 BTL91 IMPORT FORMAT 17 3.1 BTL’91 General 17 3.2 BTL’91 Record layout 17 3.3 BTL’91 Field description 20 3.4 BTL’91 Appendix 29

4 Rabo MT940 Extended 35 4.1 General information. 35 4.2 SWIFT MT940 Specifics 35 4.3 SWIFT MT940 file structure 37 4.4 SWIFT MT940 File layout 37 4.5 Extended options 39

Examples: 41

5 SWIFT MT940 standard 42 5.1 General information. 42 5.2 Format structure 42 5.3 Content description 44

6 SWIFT MT942 48 6.1 General information 48 6.2 Content 48 6.3 Detailed description 49

7 Comma Separated Values (CSV) 53 7.1 General information 53

4

1 General information

Click here for information regarding the Clieop03 & VerwInfo format from Equens.

http://www.equens.com/support/filelayout/index.jsp

5

2 Clieop 03 Format

2.1 Clieop03 Description

2.1.1 Clieop03 Description

The Clieop classification has been set up to be independent of the media used. The classification is

suitable for delivery of direct debit- or payment instructions via data communication. The

classification is single file/multi-batch.

This classification does not use the term „record‟, but rather the term „info‟. The classification is

modular; information which functionally belongs together is always grouped.

2.1.2 General features

Only one file may exist on one information carrier.

Direct debit and business payment instructions may not occur in one file, i.e., the transaction

group must be the same within one file.

During processing the fixed description is automatically added to every transaction in the

batch. The total number of info‟s for Fixed Description (batch level), Description Info

(transaction level) and Payment Reference (transaction level) may no be greater than four per

transaction.

Information contained at tag 150A will be shown prior to "BETALINGSKENM.:”. If the

information exceeds the allotted number of lines the file will be aborted during import.

Paymentsorders with a tag 150 will be processed as an Accept Giro. Whenever a

descriptionfield is submitted in a CLIEOP03, then the descriptionfield will be shown at tag

150A.

The initiator‟s name must be filled.

Maximum one payment reference per transaction with a maximum length of 16 positions.

With regard to business payment instructions it is recommend that the creditor and salary

payments be included in a separate batch. The salary payments, compacted, can then be

acknowledged as a single total transaction.

2.2 Structure of CLIEOP03

2.2.1 Structure

These specifications of the CLIEOP 03 are according to Equens (Dutch clearing institute) standards.

2.2.2 Version

CLIEOP 03 can be used for:

(non) nett creditor and salary payments

nett direct debits

non-nett direct debits

2.2.3 Technical description

Clieop03 records must be closed with CR (Carriage Return) and LF (Line Feed); the file must be

closed with an EOF (End Of File) Marker.

2.2.4 Lay-out

The following lay-out is also used by the Dutch clearing institute.

6

Initiator‟s account number should contain a correct account number.

The name/address/place sections are 35 positions large, but will be filled up to a maximum of

28 positions.

The name of the Clieop03 file is free

Name/Address/Place-code is only of concern if you send your Clieop03 directly to Equens

(sending by order in RCM).

When sending Clieop03 directly to Equens (via “orders”) and contains payments or direct

debits for the “Postbank”, then these must be “correct” (NL: ”zuiver”);this means that the

name<>number check (of the beneficiary) must be done in advance (before sending to the

bank)

He who sends in the Clieop-file, will be recognised as the “Initiator”

Time-lines: Batches send to Equens need to be present at Equens before noon of the “desired

processing date”. Only then they will guarantee processing this batch on time under the

condition that the bank (of initiator) gives approval on time (before noon)

Equens requests the bank approval for:

o (non) nett creditor payments

o non-nett direct debits which exceeds pré-defined limitations

When Equens has enough capacity, they will process as much as files, send in on the day of delivery.

If you don‟t want Equens to process your file(„s) on the day of delivery, you have to use the option:

“Desired processing date”; this option can be used to send in files up to 30 calendar days in advance.

7

2.2.5 Structure diagram

Diagram describing the modular structure for Clieop-format.

The structure diagram shows the name of the infos. Between brackets the info code of the infos.

Whether the info is mandatory or optional, you can find below. Between brackets the number of

occurrences at file, batch or transaction level. At the infos at transaction there is also added whether it

is for direct debits of for business payments.

Cient instruction

classification

(Clieop03)

Business

payments or direct

debits

Man. (1-99.999)

Batches with

payments of direct

debits

Man. (1-9.999)

Initiator info

(0030)

Mandatory (1)

Batch close info

(9990)

Mandatory (1)

File header info

(0001)

Mandatory (1)

File close info

(9999)

Mandatory (1)

Address of payer

info (0113)

Optional (0 - 1)

Fixed description

info (0020)

Optional (0 - 4)

Batch header info

(0010)

Mandatory (1)

Transaction info

(0100)

Mandatory (1)

Name of payer info

(0110)

Optional (0 - 1)

Payment reference

info (0150)

Optional (0 - 1)

Description info

(0160)

Optional (0 - 4)

Direct debitDirect debit +

business

payments

Direct debit Direct debit +

business

payments

Direct debit +

business

payments

Name of payee

info (0170)

Optional (0 - 1)

Address of payee

info (0173)

Optional (0 - 1)

Business

payments

Business

payments

8

2.3 CLIEOP03 Info classification

2.3.1 Info classification at file level

File header info

Start

position

Length Type Name Contents

1 4 Numeric Info. code 0001

5 1 Alphanumeric Variant code A

6 6 Numeric File creation date ddmmyy

12 8 Alphanumeric File name CLIEOP03

20 5 Alphanumeric Sender identification

25 4 Alphanumeric File identification

29 1 Numeric Duplicate code

30 21 Alphanumeric Filler

File close info

Start

position





2.3.2 Info classification at batch level

Batch header info

Start

position



5 1 Alphanumeric Variant code B

6 2 Alphanumeric Transaction group

8 10 Numeric Initiator‟s account number

18 4 Numeric Batch serial number

22 3 Alphanumeric Delivery currency EUR


9

Fixed description info

Start

position




6 32 Alphanumeric Fixed description


Initiator info

Start

position




6 1 Numeric NAP (Name/Address/Place)

code

7 6 Numeric Desired processing date ddmmyy

13 35 Alphanumeric Initiator‟s name

48 1 Alphanumeric Test code Capital P


Batch close info

Start

position




6 18 Numeric Total amount

24 10 Numeric Total account numbers

34 7 Numeric Number of transactions


2.3.3 Info classification at transaction level Direct debit

Transaction info

Start

position




6 4 Alphanumeric Transaction type

10 12 Numeric Amount

22 10 Numeric Payer‟s account number

32 10 Numeric Payee‟s account number


Name of payer info

Start

position




10

6 35 Alphanumeric Name of payer


Address of payer info

Start

position




6 35 Alphanumeric Address of payer


Payment reference info

Start

position




6 16 Alphanumeric Payment reference


Description info

Start

position




6 32 Alphanumeric Description


2.3.4 Info classification at transaction level Business payments

Transaction info

Start

position




6 4 Alphanumeric Transaction type

10 12 Numeric Amount

22 10 Numeric Payer‟s account number

32 10 Numeric Payee‟s account number


Payment reference info

Start

position




6 16 Alphanumeric Payment reference


Description info

11

Start

position




6 32 Alphanumeric Description


Name of payee info

Start

position


1 4 Numeric Info code 0170


6 35 Alphanumeric Name of payee


Address of payee info

Start

position


1 4 Numeric Info code 0173


6 35 Alphanumeric Address of payee


12

2.4 CLIEOP03 Fields

2.4.1 Completion instruction for the fields

Alphanumeric fields are written to the left and supplemented to the right with spaces, numeric

fields are written to the right and supplemented to the left with zeros.

Account numbers must have a numeric value, i.e. a giro account must NOT be preceded by a P.

Uncompleted fields and fillers contain spaces if the „Type‟ is alphanumeric (See Info

classifications), or zeros if the „Type‟ is numeric.

If the number of digits of a total exceeds the length of the field, the count will be cut off to the left.

Every field must be completed, unless the description states otherwise.

Fields which allows letters can be completed with upper and/or lower case. Unless otherwise

instructed Equens will convert lower case letters to upper case.

A giro account will be considered „nett‟ if the client has checked whether the name which is noted

for that giro account in this file corresponds with the name which is registered with the Postbank.

„Non-nett‟ payment orders must set out the name and the address of the giro account holder

concerned as you know it.

2.4.2 Field description

Address of payee (Address of payee info)

If completed, contains the address according to the initiator, belongs to the Payee‟s account number.

For business payments orders the first 28 positions of this field will be processed, the remaining

positions will be ignored.

Address of payer (Address of payer info)

If completed, contains the address according to the initiator, belongs to the Payer‟s account number.

For direct debit orders the first 28 positions of this field will be processed; the remaining positions will

be ignored.

Amount (Transaction info)

The amount to be transferred in cents. Subject to further changes, the maximum is EUR

453.780.216,08 or the counter-value thereof in euro‟s per transaction.

If the amount is greater the transaction will be rejected.

Batch serial number (Batch header info)

Serial number increasing by 1 per batch. Numbering may be continued on consecutive information

carriers.

Creation date of file (File header info)

Date on which the file was created.

Delivery currency (Batch header info)

Indicates in what currency the amount will be expressed in the transactions of the batch. Values:

EUR: Euro; amount is in cents

Description (Description info).

Explanation of the transaction, see also “General Features”.

Desired processing date (Initiator info)

If completed, contains the future date on which the batch is to be processed. You can deliver orders up

to a maximum of 30 calendar days before the desired processing date.

Duplicate code (File header info).

Indicates whether a file is a duplicate of a previous file.

Values:

13

1 original

2 duplicate

Comment: original and duplicate only differ in this field.

File identification (File header info).

Identifies the file uniquely (per month).

Contents: position 1 - 2 = position 1 - 2 of Creation date of file (day of the month) position 3 - 4 from

1, sequential number increasing by 1 per day of the month on which delivery took place.

File name (File header info).

Identifies the file. Value CLIEOP03.

Fixed description (Fixed description info).

Contains a description applicable to all the orders of the batch. See also General Features.

Info code (all info).

Identifies the info. For the values see Specification of the info classifications.

Initiator’s account number (Batch header info)

Contains the account number of the initiator of the batch.

Initiator’s name (Initiator info)

Name of the initiator. The first 24 positions of this field will be processed, the remaining positions will

be ignored.

Name of payee (Name of payee info)

Payee‟s name according to the initiator. For business payments orders. The first 24 positions of this

field will be processed, the remaining positions will be ignored.

Name of payer (Name of payer info)

Name of the payer according to the initiator. For direct debit orders. The first 24 positions of this field

will be processed, the remaining positions will be ignored.

14

NAW (Name and Address) code (Initiator info).

Indicates for payments (Transaction group 00) whether the initiator wants to receive the NAW data

used by the Postbank for „non-verified‟ account numbers. To make use of this facility there must be a

contract with Equens.

Values:

1.NAW not desired

2.NAW desired

Direct debit (Transaction group 10) always contains the value 1.

Number of transactions (Batch close info)

The number of Transaction infos between Batch header info and Batch close info.

Maximum of 99,999 transactions per batch.

Payment reference (Payment reference info)

Reference added to the transaction by the client. See also General Features.

Payee’s account number (Transaction info)

The account number of the recipient of the Amount. For Transaction group 10 this number must be the

same as the Initiator‟s account number.

Payer’s account number (Transaction info)

The account number of the payer of the Amount. For Transaction group 00 this number must be the

same as the Initiator‟s account number.

Sender identification (File header info)

Identification that the sender gives to himself.

Test code (Initiator info)

Indicates whether the batch is to be processed as production of test.

Values:

P. production

T. test

Total amount (Batch close info)

The total of the fields Amount in this batch. Subject to further changes, the maximum is EUR

45,378,021,609.01 or the counter-value thereof in euros per batch. If the amount is greater the batch

will be rejected.

Total account numbers (Batch close info)

The calculated amount of the Payer‟s account number and Payee‟s account number per payment per

batch.

Transaction group (Batch header info)

Indicates to what Transaction group the orders of the batch belong.

Values:

00 Payments

10 Direct debits

15

Transaction type (Transaction info)

Further sub-division within Transaction groups 00 and 10 by adding 2 digits.

Values:

0000 – „Non-nett‟ creditor payment to a giro account

0003 – „Non-nett‟ salary payment to a giro account

0005 – „Nett‟ creditor payment to a giro account

– Creditor payment to a bank account

0008 – „Nett‟ salary payment to a giro account

– Salary payment to a bank account

1001 – „Nett‟ direct debit to a giro account

– Direct debit to a bank account

1002 – „Non-nett‟ direct debit to a giro account

Variant code (all infos)

Identifies the versions of the info. A higher letter either contains more fields than the preceding

version, or the last field of the info has been extended.

2.5 CLIEOP03 validations by Rabobank

Rabobank will perform validations to ensure the utmost STP-level. The checks are explicitly and

implicitly described in the Equens documentation.

1. Records must not exceed 50 characters

2. First character of each record must be zero or nine.

3. Fileheader record (0001) must contain „CLIEOP03‟ in field file name.

4. No mix of credit transfers and direct debits (transactiongroup “00” and “10”) in one file.

5. Transactiongroup in batchheader record (0010) must be “00‟ or “10”.

6. Test code in ordering party record (0030) must be “P”

7. The filler after test code must only contain blanks or “S “.

8. Amount, account number payer and account number beneficiary in the transaction record (0100)

must contain digits (0-9) only.

9. Amount must not be zero.

10. Account number payer must be “Elfproef”.

11. For credit transfers the account number ordering party in the batchheader record (0010) must be

equal to the account number payer in the transaction record (0100)

12. For direct debits the account number ordering party in the batchheader record (0010) must be

equal to the account number beneficiary in the transaction record (0100)

13. For credit transfers (transactiongroup “00”) the order type in transaction record (0100) must be

“0000”, “0003”, “0005” or “0008”.

14. For direct debits (transactiongroup “10”) the order type in transaction record (0100) must be

“1001” or “1001”.

15. Number of items of batchtrailer record (9990) must be equal to the counted number of all

transaction records (0100).

16. Total account numbers of batchtrailer record (9990) must be equal to the calculated total of

account number of all transaction records (0100).

17. Total amount of batchtrailer record (9990) must be equal to calculated amount of all transaction

records (0100).

18. Total number of transaction records (0100) must not exceed one hundred thousand.

19. The combination of record code and variant code must be “0001A”, “0001A”, “0010B”, “0020A”,

“0030B”, “0100A”, “0110B”, “0113B”, “0150A”, “0160A”, “0170A”, “0173B”, “9990A” or

“9999A”.

20. Within credit transfers (transactiongroup “00”) record type “0110” or “0113” are not allowed.

21. Within direct debits (transactiongroup “10”) record type “0170” or “0173” are not allowed.

22. Within a payment the number of record type “0150” must be zero or one.

23. Account number beneficiary must not be zero.

24. Account number payer must not be zero.

16

25. The delivery currency in batchheader record (0010) must be “EUR”.

26. The number of description records (0160) must not exceed four per payment.

27. The number of name payer record (0110) and the number of name beneficiary record (0170) must

be zero or one.

28. The number of city payer record (0113) and the number of city beneficiary record (0173) must be

zero or one.

29. Fileheader record (0001) must be the first record in the file.

30. Batchheader record (0010) must be preceded by fileheader record (0001) or batchtrailer record

(9990).

31. Fixed description record (0020) must be preceded by batchheader record (0010).

32. Ordering party record (0030) must be preceded by batchheader record (0010) or by fixed

description record (0020).

33. Filetrailer record (9999) must be preceded by batchtrailer record (9990).

34. Number of batchheader records (0010) must be equal to number of batchtrailer records (9990).

17

3 BTL91 IMPORT FORMAT

3.1 BTL’91 General

3.1.1 Characteristics

Format Variable

Maximum record

length 194

End of record [CR][LF], included in record length

Field separator None

Field identifier None

3.1.2 Record types

1 Leading record

4 Payment records

1 Total record

1 Terminal record

3.1.3 Record layout

1 Leading ecord

n Payment records

n Total record

1 Terminal record

3.2 BTL’91 Record layout

3.2.1 Leading record

No Name Type Start

position

Lengt

h

Dec Contents

11-01 Record code Numerical 1 2 11

11-02 Exchange bank Alphanumeric 3 4 RABO

11-03 Medium code Alphanumeric 7 1

11-04 Version number Numeric 8 2

11-05 File creation date Numeric 10 8 CCYYMMDD

11-06 Batch number Numeric 18 3

11-07 Initiator‟s name Alphanumeric 21 35

11-08 Initiator‟s address Alphanumeric 56 35

11-09 Initiator‟s place Alphanumeric 91 35

11-10 Initiator‟s country Alphanumeric 126 35

11-11 Business sector Numeric 161 4

11-12 Desired processing date Numeric 165 8 CCYYMMDD

11-13 Filler Alphanumeric 173 20

3.2.2 Payment record Part 1

No Name Type Start

position

Lengt

h

Dec Contents

21-01 Record code Numeric 1 2 21

21-02 Payment order no. Numeric 3 4 Unique

21-03 ISO currency code of Initiator‟s

account

Alphanumeric 7 3

18

21-04 Initiator‟s account Numeric 10 10

21-05 ISO currency code of payment order Alphanumeric 20 3

21-06 Payment order amount Numeric 23 12 3 Value>0

21-07 Desired processing date Numeric 38 8 CCYYMMDD

21-08 Domestic costs code Alphanumeric 46 1 1, 2 or 3

21-09 Correspondent costs code Alphanumeric 47 1 1, 2 or 3

21-10 Payment method code Alphanumeric 48 1 0, 1 or 2

21-11 Processing code Alphanumeric 49 1 0 or 2

21-12 Cheque crossing code Alphanumeric 50 1

21-13 Cheque forwarding code Alphanumeric 51 1

21-14 Payment instruction code 1 Alphanumeric 52 2




21-18 Payment category code Alphanumeric 60 1 1, 2, 3, 4 or 5

21-19 Nature of payment code 1 Alphanumeric 61 40

21-20 Nature of payment code 2 Alphanumeric 101 40

21-21 DNB registration no. Alphanumeric 141 8

21-22 Goods code Alphanumeric 149 2

21-23 Article no. Alphanumeric 151 2

21-24 Trader no. Alphanumeric 153 4

21-25 Instructions Alphanumeric 157 35


No Name Type Start

position

Lengt

h

Dec Contents


22-2 Payment order no. Numeric 3 4 Content field 21-

2

22-3 Beneficiary‟s account¹ Alphanumeric 7 34

22-4 Beneficiary‟s name Alphanumeric 41 35

22-5 Beneficiary‟s address Alphanumeric 76 35

22-6 Beneficiary‟s place Alphanumeric 111 35

22-7 Beneficiary‟s ISO country code Alphanumeric 146 2

22-8 Beneficiary‟s country Alphanumeric 148 35


¹ The use of IBAN for beneficiary accountnumbers is obligatory when paying in an EEA currency to

an EEA country.


No Name Type Start

position

Lengt

h

Dec Contents


23-2 Payment order no. Numeric 3 4 Content field 21-

2

23-3 SWIFT address of beneficiary‟s bank Alphanumeric 7 11

23-4 Name of beneficiary‟s bank Alphanumeric 18 35

23-5 Address of beneficiary‟s bank Alphanumeric 53 35

23-6 Place of beneficiary‟s bank Alphanumeric 88 35

23-7 ISO country code of beneficiary‟s bank Alphanumeric 123 2

23-8 Country of beneficiary‟s bank Alphanumeric 125 35

23-9 Instructions Alphanumeric 160 33

19


No Name Type Start

position

Lengt

h

Dec Contents


24-2 Payment order no. Numeric 3 4 content field 21-

2

24-3 Payment reference 1 Alphanumeric 7 35





3.2.6 Total record per currency code

No Name Type Start

position

Lengt

h

Dec Contents


31-2 ISO currency code of totals record Numeric 3 3

31-3 Total amount Numeric 6 12 3

31-4 Number of payment orders Numeric 21 4


Total record In BTL91 it is mandatory to find, check and verify all values in every payment record.

20

3.2.7 Terminal record

No Name Type Start

position

Lengt

h

Dec Contents


41-2 Total number of records Numeric 3 6

41-3 Total number of payment orders Numeric 9 4

41-4 Hash-code Numeric 13 24


Terminal record In BTL91 it is mandatory to find, check and verify all values in every payment

record.

3.3 BTL’91 Field description

3.3.1 GENERAL

The following characters and symbols can be used in alphanumeric fields (marked 'a'):

A through Z (capitals only)

0 through 9

. (full stop)

/ (slash)

? (question mark)

: (colon)

( (opening bracket)

) (closing bracket)

' (accent)

- (minus sign)

+ (plus sign)

, (comma)

(space)

SWIFT recognises the above characters and symbols only. As a colon in SWIFT messages is also

used as field separator, do not enter a colon in the first position of a field.

Empty alphanumeric fields must contain spaces.

Use 0 through 9 in numeric fields (marked 'n').

Empty numeric fields must contain zeros.

If the total amount in field 31-3 exceeds the field length, the digits on the left disappear from the

screen and can be ignored.

3.3.2 LEADING RECORD

11-1 RECORD CODE

Description Code for the type of record. The leading record always contains the value '11'.

Values 11

Validations Mandatory field

21

11-2 EXCHANGE BANK

Description First four letters of the SWIFT address of the exchange bank which receives the

orders for processing.

Values RABO


11-3 MEDIUM CODE

Description One-letter code for the origin of the file received. Customers who create files

themselves must enter an „X‟.

Values "X" – non-Rabobank software


11-4 VERSION NUMBER

Description Version number of the medium software used. Customer should choose and fill in

a permitted value within the range of 01 – 99.

Values 01 –99


11-5 FILE CREATION DATE

Description The date on which the payment order file is created. The date entered is used for

file identification purposes only and does not relate to the date on which orders

included in the file must be processed. The date format is CCYYMMDD: CC =

century; YY = year; MM = month of year; DD = day of month

Values CC = 19-20; YY = 00-99; MM = 01-12; DD = 01-31

Validations Mandatory field; Valid date.

11-6 BATCH NUMBER

Description The number of the batch delivered. Electonic Banking PC Module and the

Payments Diskette allocate a batch number automatically on creation of the file or

preparation of the diskette. Customers who create files themselves can enter any

value between 001 and 999. It is recommended to allocate successive batch

numbers.

Values 001 - 999


11-7 INITIATOR’S NAME

Description Full name of initiator

Values not applicable


11-8 INITIATOR’S ADDRESS

Description Street and house number or P.O. Box



11-9 INITIATOR’S PLACE

Description Postcode and place. Place starts with a postcode, format 4N + space + 2A + space.

Place is max. 27 characters long



11-10 INITIATOR’S COUNTRY

22

Description Name of country where the initiator is established.


Validations Optional field

11-11 BUSINESS SECTOR

Description Code number of the business sector to which the principal's company belongs.

This code is determined by the Chamber of Commerce.



11-12 DESIRED PROCESSING DATE

Description This field contains the date on which the batch is to be processed. The

date format is CCYYMMDD: CC = century; YY = year; MM =

month of year; DD = day of month.

Values CC = 19-20; YY = 00-99; MM = 01-12; DD = 01-31

Validations Optional field; Valid date.

3.3.3 PAYMENT RECORD PART 1

21-1 RECORD CODE

Description Code for the type of record. Each payment order is subdivided into four

interrelated sub records. The record code for the first sub record is 21.

Values 21


21-2 PAYMENT ORDER NO.

Description Serial number of payment order in a batch. Each payment order is subdivided into

four payments sub records. Interrelated sub records have the same number.

Payment orders are numbered from 0001 upwards.

Values 0001-9999

Validations Mandatory field; numbering in ascending order from 0001

21-3 ISO CURRENCY CODE OF INITIATOR’S ACCOUNT

Description ISO code of currency in which the account to be debited is kept.

Values Code included in ISO currency code table


21-4 INITIATOR’S ACCOUNT

Description Ten-digit number of the bank account to be debited.


Validations Mandatory field; leading zero; valid Rabobank account number at positions 2

to 10.

21-5 ISO CURRENCY CODE OF PAYMENT ORDER

Description ISO code of currency in which the payment order is made out.



21-6 PAYMENT ORDER AMOUNT

Description The amount stated in the payment order. Only numeric characters can be entered.

An imaginary decimal point (non-continental European and American) or decimal

comma (continental European) is located between the third and fourth positions

from the right.


23

Validations Mandatory field; greater than zero; smaller than 9 billion (irrespective of

currency); a zero in third decimal place.

21-7 DESIRED PROCESSING DATE

Description This field contains the date on which the order is to be processed. The desired

processing date has to be entered for each order individually. The date format is

CCYYMMDD: CC = century; YY = year; MM = month of year; DD = day of

month.

Values CC = 19-20; YY = 00-99; MM = 01-12; DD = 01-31

Validations Mandatory field; valid date; must be equal of higher then current date.

21-8 DOMESTIC COSTS CODE

Description The code to be entered in this field indicates how costs charged by Rabobank

for the processing of the payment orders such as transfer charge and cheque

clearing charge have to be settled.

Values 1 = costs chargeable to initiator's euro account; 2 = costs chargeable to initiator's

FC account; 3 = costs chargeable to beneficiary details.


21-9 CORRESPONDENT COSTS CODE

Description The code to be entered in this field indicates how costs charged by foreign

correspondent banks have to be settled.

Values 1 = costs chargeable to initiator (OUR); 2 costs chargeable to initiator (OUR); 3 =

domestic costs chargeable to initiator and foreign costs chargeable to beneficiary.

(SHA); 4 = costs chargeable to beneficiary (BEN)

Validations Conditional field. Optional field when 21-10 code 1 (cheque payment).

Option 3 (SHA) is mandatory when paying in EEA currency to an EEA country.

21-10 PAYMENT METHOD CODE

Description The code in this field indicates whether order has to be processed as normal

payment or a cheque payment.

Values 0 = normal payment; 1 = cheque payment


21-11 PROCESSING CODE

Description If funds transfer has been selected as payment method, Rabobank will generally

effect the transfer via the SWIFT network. The code in this field indicates whether

the SWIFT message should be given „normal‟ or „express‟ status.

Values 0 = normal; 2 = express.


21-12 CHEQUE CROSSING CODE

Description The code to be entered in this field indicates whether Rabobank is to cross the

cheque issued. Crossed cheques cannot be paid in cash over the counter. Payment

can only be made directly to the credit of the beneficiary's account.

Values J = cross cheque

Validations Conditional field. Mandatory field when 21-10 code 1 (cheque payment).

21-13 CHEQUE FORWARDING CODE

Description The code in this field indicates the address to which the cheque has to be

forwarded.

24

Values 1 = initiator's branch; 2 = initiator; 3 = beneficiary.


21-14/17 PAYMENT INSTRUCTION CODE (1 to 4)

Description This code can be included in SWIFT messages sent to foreign banks. For an

overview of the codes see Appendix A. Codes other than those listed in the

appendix are not permitted.

Values see appendix A


21-18 PAYMENT CATEGORY CODE

Description This info is as of april 1 2003 no longer in use


Validations not applicable

21-19/20 NATURE OF PAYMENT CODE (1 and 2)




21-21 DNB REGISTRATION NO.




21-22 GOODS CODE




21-23 ARTICLE NO.




21-24 TRADER NO.





22-1 RECORD CODE

Description Code for the type of record.

Values 22



Description Number to identify payment orders within a file (same number as 21-2).

Values 0001-9999


22-3 BENEFICIARY’S ACCOUNT²

Description Bank account number of the beneficiary.

25

Values See appendix d: account numbers with national bank code


22-4 BENEFICIARY’S NAME

Description Name of beneficiary.



22-5 BENEFICIARY’S ADDRESS

Description Address of beneficiary.



² The use of IBAN for beneficiary accountnumbers is obligatory when paying in an EEA currency to an EEA country.

26

22-6 BENEFICIARY’S PLACE

Description Place of beneficiary.



22-7 BENEFICIARY’S ISO COUNTRY CODE

Description ISO code of country where the beneficiary is established.

Values Code included in ISO country code table


22-8 BENEFICIARY'S COUNTRY

Description Name of country where the beneficiary is established.




23-1 RECORD CODE


Values 23




Values 0001-9999


23-3 SWIFT ADDRESS OF BENEFICIARY'S BANK³

Description The SWIFT address of the beneficiary's bank.


Validations Optional field. Optional field when 21-10 code 1 (cheque payment).

Valid SWIFT address consisting of 8 or 11 positions. The first six positions

should contians alphanumeric characters, with positions 5 and 6 giving the

ISO country code (same code as 23-7).

23-4 NAME OF BENEFICIARY'S BANK

Description Name of beneficiary's bank.


Validations Conditional field . Optional field when 21-10 code 1 (cheque payment).

23-5 ADDRESS OF BENEFICIARY'S BANK

Description Address of beneficiary's bank.


Validations Conditional field. Optional field when 21-10 code 1 (cheque payment). 3 The use of SWIFT/BIC is obligatory when paying in an EEA currency to an EEA country.

27

23-6 PLACE OF BENEFICIARY'S BANK

Description Place of beneficiary's bank.


Validations Conditional field . Optional field when 21-10 code 1 (cheque payment).

23-7 ISO COUNTRY CODE OF BENEFICIARY'S BANK

Description ISO code of country where the beneficiary's bank is established.

Values Code included in ISO country code table


23-8 COUNTRY OF BENEFICIARY'S BANK

Description Name of country where the beneficiary's bank is established.




24-1 RECORD CODE


Values 24




Values 0001-9999


24-3/6 PAYMENT REFERENCE (1 to 4)

Description Field in which the principal can enter a payment reference. The reference is

dispatched to the beneficiary simultaneously with the payment order.



3.3.7 TOTAL RECORD

31-1 RECORD CODE


Values 31


31-2 ISO CURRENCY CODE OF TOTALS RECORD

Description ISO code of currency in which the total amount is stated. Batches must also

include totals records for payment orders in the same currency. This record has to

go in the file behind the last payment record and before the terminale record.



31-3 TOTAL AMOUNT

Description Total amount of payment orders in the currency stated in the ISO CURRENCY

CODE OF TOTALS RECORD (31-2). An imaginary decimal point (non-

continental European and American) or decimal comma (continental European) is

located between the third and fourth positions from the right.



28

31-4 NUMBER OF PAYMENT ORDERS

Description Number of payment orders in the currency stated in the ISO CURRENCY CODE

OF TOTALS RECORD (31-2).


Validations Mandatory field; greater than zero.

3.3.8 TERMINAL RECORD

41-1 RECORD CODE


Values 41


41-2 TOTAL NUMBER OF RECORDS

Description This field states the total number of file records, including leading record,

payments sub records, totals records and terminal record.



41-3 TOTAL NUMBER OF PAYMENT ORDERS

Description The total number of payment orders in the file, irrespective of the currency of the

payment orders.


Validations Mandatory field; greater than zero.

41-4 HASH-CODE

Description The DES hash for a payment order file is calculated using the standard DES hash

function of the Equens (Dutch Clearing Institute).



29

3.4 BTL’91 Appendix

3.4.1 Appendix A: PAYMENT INSTRUCTION CODE

These instructions are intended for the beneficiary's bank.

CODE ABBREVIATION IN

SWIFT MESSAGE

TEXT IN TELEX OF

EURO

MEANING

01 /PHONBEN/ ADVISE BENEF. BY

PHONE

Advise beneficiary by phone.

02 /TELEXBEN/ ADVISE BENEF. BY

TELEX

Advise beneficiary by telex.

03 /PHON/ ADVISE BENEF. BANK

BY PHONE

Advise beneficiary‟s bank by phone.

04 /TELEX/ ADVISE BENEF. BANK

BY TELEX

Advise beneficiary‟s bank by telex.

05 ADVISE BEN. BANK

BY CABLE/

CABLE/SWIFT

CHARGES FOR US

ADVISE BEN. BANK BY

SWIFT CHARGES FOR

US

Advise beneficiary‟s bank by

cable/SWIFT, charges for us.

06 ADVISE BEN. BANK

BY CABLE/ SWIFT

WITHOUT CHARGES

FOR US

ADVISE BEN. BANK BY

CABLE/ SWIFT

WITHOUT CHARGES

FOR US

Advise beneficiary‟s bank by

cable/SWIFT, without charges for us.

07 /HOLD/ HOLD DISPOSAL Hold disposal for beneficiary.

12 IF BEN. IS UNKNOWN

OR HAS DECEASED

PLEASE RETURN

AMOUNT

IF BEN. IS UNKNOWN

OR HAS DECEASED

PLEASE RETURN

AMOUNT

If beneficiary is unknown or has

deceased please return amount.

13 THIS PAYMENT IS

IRREVOCABLE

THIS PAYMENT IS

IRREVOCABLE

This payment is irrevocable.

14 INTERCOMPANY

TRANSFER

INTERCOMPANY

TRANSFER

Intercompany transfer.

30

3.4.2 Appendix B: IBAN and BBAN –accountnumbers

The abbreviation IBAN means: International Bank Account Number and BBAN: Basic Bank Account

Number.

If field 23-7 ( ) contains mentioned values, then field 22-3 must be filled with mentioned values:

Field 23-7 Field22-3 Field 22-3* Field 22-3

landcode

bank

beneficiary

Country Accountnumber

beneficiary IBAN

Accountnumber

beneficiary

(BBAN)

Accountnumber

beneficiary

AD Andorra 24 Min 6, Max 20

AT Austria 20 Min 4, Max 11 5 positions +

BBAN

BE Belgium 16 Min en Max 12

BG Bulgaria 22 BG only IBAN

format

CH Switserland 21 Min 1, Max 16 3 tot 6** positions

+ BBAN

CY Cyprus 28 Min 8, Max 24

CZ Czech Republik 24 Min 6, Max 20

DE Germany 22 Min 1, Max 10 8 positions +

BBAN

DK Denmark 18 Min en Max 14

EE Estonia 20 Min 4, Max 14

ES Spain 24 Min en Max 20

FI Finland 18 Min 8, Max 14

FR France 27 Min en Max 23

GB Great-Britain 22 Min 7, Max 8 6 positions +

BBAN

GG Guernsey C.I. 22 Min 7, Max 8 6 positions +

BBAN

IM Isle of Man 22 Min 7, Max 8 6 positions +

BBAN

JE Jersey 22 Min 7, Max 8 6 positions +

BBAN

GI Gibraltar 23 Min en Max 15

GR Greece 27 Min 8, Max 23

HR Croatia 21 Min 1, Max 34

HU Hongary 28 Min 16, Max 24

IE Ireland 22 Min en Max 8 6 positions +

BBAN

IS Iceland 26 Min en Max 12 or

Min en Max 22

IT Italy 27 Min en Max 23

LI Liechtenstein 21 Min 1, Max 16

LT Lithuania 20 LT only IBAN format

LU Luxembourg 20 Min en Max14 or

Min en Max 20

LV Latvia 21 LV only IBAN format

ME Montenegro 22 Min en Max 18

MK Macedonia 19 Min 1, Max 34

MT Malta 31 Min 8, Max 16

MU Mauritius (island

of)

30 Min 1, Max 34

31

NL The Netherlands 18 Min 9, Max 10 or

Min 4 , Max 8

NO Norway 15 Min en Max 11

PL Poland 28 Min 8, Max 32

PT Portugal 25 Min en Max 21

RO Roemania 24 RO only IBAN format

RS Serbia 22 Min en Max 18

SE Sweden 24 Min 2, Max 14

SI Slovenia 19 15

SK Slovakia 24 Min 6, Max 20 or

Min 6, Max 23

TN Tunesia 24 Min en Max 20

TR Turkey 26 Min 1, Max 34

US United States (of

America

N.v.t. 9 positions +

BBAN***

* Accountnumber is no IBAN

** At import always 6 positions

*** At import there should be a FW when the BBAN is 15 posities or more.

3.4.3 Appendix C: Account numbers with national bank code

Extra specifications of bank account numbers in Austria, Germany, Great Britain (including Guernsey,

Jersey and Isle of Man), Ireland and Switzerland 4.

4 It is not possible to insert national bank-codes into Euro (€) payments to EU countries: IBAN is obligated with these payments; the national bankcode is

inserted in the IBAN.

Austria

Austrian bank account numbers are made up of a maximum of 16 characters. The bank code

(Bankleitzahl/BLZ) always consists of five positions; the customer account number (Kontonr.) may be

between 2 and 11 positions. Customer account numbers of less than 11 positions must be preceded by

zeros.

Example of ‘beneficiary's account number’:

12345 0012345678

Bank code account number

Germany

German bank account numbers (Bankleitzahl/BLZ) are made up of a maximum of 18 characters. The

first 8 positions show the bank code, followed by the customer account number (Kontonr.) consisting

of no more than 10 digits. Customer account numbers with less than 10 digits must be preceded by

zeros.


12345678 0012345678


Great Britain (including Guernsey, Jersey and Isle of Man)

A bank account number in Great Britain has a maximum of 16 characters, and consists of a six-digit

bank code (Sort Code) and a customer account number of no more than 10 digits. Banks codes and

32

customer account numbers which do not have the maximum permitted length, must be preceded by

zeros.


123456 0012345678


Ireland

In Ireland the bank account number always consists of 14 characters. It is made up of a six-digit bank

code (Sorting Code/SC) and an eight-digit customer account number.


123456 12345678


Switzerland

In Switzerland bank account numbers have not yet been standardised. Each financial institution uses

its own system. For correct usage in RTE-W the payment order must be structured as follows: six-digit

bank or branch code, followed by a customer account number of no more than 16 alphanumeric

characters (including a check digit). Full stops, commas, spaces, etc. are permitted. If any, please

remember to include these in your payment instructions. If the bank or branch code and the customer

account number do not have the maximum length, they must be preceded by zeros.


123456 000000123456789A

Bank code account number check digit

3.4.4 Appendix 4:PSD & EEA countries and currencies

The Payment Services Directive (PSD) is a European legal framework to harmonise the legal rules in

the field of payment transactions within the European Union.

With respect to (international) credit transfers (within Europe), the entire amount must always be

transferred and no charges may be deducted. The payer and the beneficiary within Europe will each be

required to pay their bank‟s own transfer charges (cost option SHA).

The PSD-conditions only apply, when both the remitter‟s bank and the benificiary‟s bank are located

within the EEA and the currency used is an EEA currency. The EEA consists of the EU & EFTA

countries.5 A list of EEA currencies and countries is available below:

Country ISO code

Austria AT

Belgium BE

Bulgaria BG

Cyprus CY

Czech Republic CZ

Denmark DK

Estonia EE

Finland FI

France FR

Germany DE

Greece GR

Hungary HU

Iceland IS

Ireland IE

Italy IT

Liechtenstein LI

Latvia LV

Lithuania LT

Luxembourg LU

Malta MT

Monaco6 MC

Netherlands NL

Norway NO

Poland PL

Portugal PT

Romania RO

Slovakia SK

Slovenia SI

Spain ES

Sweden SE

Switzerland 5 CH

33

United Kingdom GB

Currency ISO code

Euro EUR

Bulgarian Lev BGN

Czech Koruna CZK

Danish Krone DKK

Estonian Kroon EEK

Hungarian Florint HUF

Iceland Krona ISK

Latvian Lats LVL

Lithuanian Litas LTL

Norwegian Kroner NOK

Polish Zloty PLN

Romanian Leu RON

Swedish Krona SEK

Swiss Franc5 CHF

United Kingdom Pound GBP

5 Switzerland is a member of the EFTA, but formally not of the EEA and does not formally

belong to the PSD area. However the same conditions apply. 6 Monaco is no part of the EEA or the PSD area. However the mentioned conditions do apply.

35

4 Rabo MT940 Extended

4.1 General information.

The SWIFT MT940 format is an international format which is used as sort of account

statement.

Rabo Cash Management provides an option to export account-information (balance,

transaction and specifications) in SWIFT MT940 format. There are 2 kind of the SWIFT-

MT940‟s in RCM possible:

- MT940 standard (RABO-standard)

- MT940 Extended (RABO-standard with several extra configuration-options)

This version of the SWIFT MT940 format description concerns only RCM (Rabo Cash

Management) and no other applications of Rabobank.

4.2 SWIFT MT940 Specifics

SWIFT MT940 contains a start- and closing balance with all payments within. Both balances

are mandatory to create an MT940 (therefore only complete statements can be exported).

Diagram:

36

SWIFT-MT940 record structure (schematicaly)

:940:

Mandatory Optional

:20: Mark + date 1

:28:

Previous account ballance 1

:61: Transaction 1

:86: First description of transaction 1

:86: Second description of transaction 1

:25:

:61: Transaction 2

:86:

Accountnumber 1

:86:

Mandatory if present

:64:

:65:

Available balance 1

Forward available balance 1

:20: Mark + date 2

:25: Account number 1

:28: Repetition of previous items

:20: Mark + date 1

Of the next account.

Note: The

sequence is first

all data for one

account, followed

by other accounts

(if present).

:62F: Current account balance 1

:25: Account number 2

:28:

Fixed value

:60F:

Statement number

First description of transaction 1

Second description of transaction 1

Repetition of previous items

Next

account

Next

account

37

Explanation:

- Each SWIFT-MT940 starts with a header record 940, followed by record 20, 25, 28,

60F, 61 and 0 to 6 records 86; 62F en (optional) record 64 en 65.

- If more then one day is exported, then the information will be shown (in order of the

date) per day.

- If more accounts are exported, then the information will be shown per account (in

order of the date(„s)).

- The standard layout of the filename is:

< AccountnumberCurrency”Underscore”MT940fileYYYYMMDD[Sequence nr].extension >

Example: 300091486EUR_MT940file20070816[1].txt

MT940 were it concerns (SWIFT-) standard MT940 and ME940 where it concerns

(Rabo-) extended MT940.

4.3 SWIFT MT940 file structure

Tag Name (of the tag) Status Length (of the

field)

:940: Header Mandatory (1-1) 5

:20: Transaction Reference Number Mandatory (1-1) 14

:25: Account Number Mandatory (1-1) 39

:28: Statement Number/Sequence Number Mandatory (1-1) 12

:60F: Previous Accounting Balance Mandatory (1-1) 30

:61: Statement Line Optional (0-n) 80

:86: Description Optional (0-n) 69

:62F: Current Accounting Balance Mandatory (1-1) 30

:64: Available Balance at Entry Date Optional (0-1) 29

:65: Forward Available Balance Optional (0-4) 29

The table shows the tag of the record and the name of the tag. The column status shows

whether the field is mandatory in the file and how often the record can appear in the file. The

last column shows the total length of the record.

4.4 SWIFT MT940 File layout

Header

Description Type Length Contents Comment

Header Alphanumeric 5 :940:

Record :20: Transaction Reference Number

Description Type Length Comment

Record code Alphanumeric 4 :20:

Format Alphanumeric 3 940

Usage rule code Alphanumeric 1 A

Entry date Numeric 6 Format: YYMMDD

38

Record :25: Account Number



Account number Alphanumeric 35 Details

Record :28: Statement Number/Sequence Number



Statement number Numeric 5 00000 Details

Separator Alphanumeric 1 /

Sequence number Numeric 2 00

Record :60F: Previous Accounting Balance


Record code Alphanumeric 5 :60F:

Credit / Debit Alphanumeric 1 Value: "C" or "D"


Currency code Alphanumeric 3 Format: ISO-Currency code

Previous accounting

balance

Alphanumeric 15

Record :61: Statement Line



Value date Numeric 6 Format: YYMMDD

Credit / Debit Alphanumeric 1 Value: "C" or "D"

Amount Numeric 15 Details

Transaction type Alphanumeric 4 NMSC

Counter account number Alphanumeric 16 When counter account

number is unknown, the field

gets the value: "NONREF"

Name counter account

number

Alphanumeric 34 If the information is not

available, this field will be

empty.

Record :86: Description



Description Alphanumeric 65 Details

Record :62F: Current Accounting Balance



Credit / Debit Alphanumeric 1 Value: "C" of "D"


Currency code Alphanumeric 3 Format: ISO currency code

Current accounting

balance

Numeric 15

39

Record :64: Available Balance at Entry Date






Available balance Numeric 15

Record :65: Forward Available Balance






Available balance Numeric 15

4.5 Extended options

General information

When exporting SWIFT MT940 within RCM, you will find a screen with several options

witch you can change with checkboxes: . Underneath you will find the explanation of

these options.

Specifics:

- the “standard” options are similar with the settings of our MT940 from the RTE application.

- inserted information will precede on current information

- if a requested option is not available, then nothing will be filled in or inserted; this is to

prevent “empty” lines.

4.5.1 Counterparty Information on transaction

Ref.:86:

Inactive: (default) No address, postal code and city

Active: first description line contains address, postal code and city. Options of display are:

1. Address (space) postal code (space) city [field length variable]

2. Address (fixed length 30 pos.) postal code (fixed length 6 pos.) city (fixed length 29 pos.)

[fixed length, total 65 pos.]

3. Counterparty account number (space) Name counter party

4.5.2 Specifications

Ref.:61: & :86:

Inactive: (default) All transactions will be available in the MT940, including compressed

transactions (without their specifications).

Active: When specifications are available for the compressed transactions, these specifications

will replace the concerning compressed transactions.

40

4.5.3 Transaction Type Code

Ref.:61:

Active: (default) when available, transactions and specifications will be provided with a

numeric transaction type code (N999 where 999 will contain the code). If this code is not

found or available/provided, the type code NMSC will be written.

Inactive: All transactions and specifications will get the transaction type code NMSC

(miscellaneous)

(Note) For Rabobank International (RI) accounts a subset is available at:

https://portalsecure.rabobank.nl/wps/myportal/rfl/rcm

4.5.4 Account Statement Number

Ref.:28:

Inactive: (default) All instances of :28: should contain the value 00000/00 (default)

Active: Each instance of :28: will contain an account statement number

The account statement number consists of two parts; the number before the slash is the

account statement number itself, the part after the slash is the page number of the account

statement. Since the information is provided (counted) electronically and because there is no

link to the „real‟ account statements, the default value for the part after the slash is 00

4.5.5 Transaction Reference Number

Ref.:86:

Active: When available, the next available description line needs to contain the PA, RE, LD,

FX or AC transaction reference number information (default)

Inactive: No transaction reference information

4.5.6 Formatted Account Number (Y/N)

Ref.:25:

Active: (default) Account number in this field will be formatted;

1. 9999.99.999AAA Rabo default mask for 9 digit current account numbers + currency

2. 999999999AAA Alternative mask for 9 digit account numbers, i.e. without separating dots

in the number + currency

3. 0999999999XXX Mask for 9 & 10 digit account numbers, where 9 digit account numbers

are preceded by a 0 (zero), and where currency is only specified when the account is not a

EUR account

4. 99.99.99.999 AAA Alternative mask for 9 digit account numbers

Inactive: No formatting of the account number (default 0999999999 acct. number only)

4.5.7 TAG86 – description line – repeat (Y/N)

Ref.:86:

Active: (default) each description line of the transaction must start with :86: followed by the

description

Inactive: The first description line of the transaction must start with :86:, the next description

lines of the transaction must not start with :86: (Swift standard)

https://portalsecure.rabobank.nl/wps/myportal/rfl/rcm

41

4.5.8 Payment reference (payment identifier code) (Y/N)

Ref.:86:

Inactive: (default) No payment reference

Active: When available, the next available description line must contain the payment reference

information;

1. BETALINGSKENM.: (space) payment reference < Please note the colon after the

dot

2. BETALINGSKENM. (space) payment reference <This option doesn‟t have a colon

after the dot

3. Betalingskenmerk: (space) payment reference

4. BETKENM.: (space) payment reference

5. Payment reference [only the reference, without identifying text]

4.5.9 Amount with or without leading zeros (Select)

Ref. :61:

Active: (default) the amount field must be padded with zeros

:61:060215C000000000050,00NMSC0231902018 SAMPLE COMPANY GMBH

Inactive: The amount field must not be padded with zeros (Swift standard)


:61:051230D0,15NMSC NONREF

Padded means that the numeric field is filled out with zeros from the left of the field, until the

maximum length for the field is reached.

4.5.10 Decimal separator sign for amount (Select)

Ref. :61:

Active: (default) Decimal separator for the amount field is a comma "," (default)


Inactive: Decimal separator for the amount field is a point "."

:61:060215C000000000050.00NMSC0231902018 SAMPLE COMPANY GMBH

4.5.11 Extra:

Regarding lay-out of non-Rabobank accountnumbers; RCM will always use the lay-

out provided by the other bank(s).

Amount: all amounts are 15 positions long (comma included). The place of the

comma depends on the currency code (ISO). The amount will always be preceded by

zeros.

Examples:

EUR123.456,78 - 000000123456,78

USD 0,12 - 000000000000,12

TND 123,456 - 00000000123,456

YPN 123.456.789 - 00000123456789,

42

5 SWIFT MT940 standard

5.1 General information.

The formal name for this report format is “MT 940 Customer Statement Message”, an

international format used as digital equivalent of the official paper account statement.

A statement will be available for each entry date. It becomes available after balancing (closed

off, finalized) the account administration of the entry date. A statement includes the opening

balance and the closing balance of the entry date and detailed information about all entries

booked to the account.

The SWIFT MT940 delivered by RCM is not fully SWIFT compliant. The maximum length

can be more than 2000 characters.

The statement will be empty when no booked entries are available for the reported entry date

(no field-61 and -86 present and field-60F will be equal to field-62F).

5.2 Format structure

A field (label, tag) proceeds each information block in a customer statement message. The

field content can be composed of various items.

The file starts with a fixed value “:940:”. Each message in the file starts with field-20 and ends

at the next field-20 or when the end of the file is reached.

The fields within one message will appear in the sequence as stated below. Within a statement,

the field-61 and field-86 as group can be present multiple times and field 65 can be present

multiple times.

A customer statement can consist of multiple messages due to the SWIFTNET limitations of

2000 characters. When the maximum length will exceed 2000 characters, the first message for

one statement will have field-60F and field-62M, the intermediate messages will have field-

60M and field-62M and the last message will have field-60 M and field-62F. The opening and

closing balances will connect the messages to a chain. In addition, the messages will have an

ascending sequence-number within field-28C. This feature is NOT applicable when

downloading SWIFT MT940 from RCM.

Field Subfield Mandatory/

Optional

Field name Format, Content, Options

[]=optional, !=fixed length,

n=numeric, a=alphabetic,

x=alphanumeric, d=numeric with

decimal separator, c=code list

values

:940: M 5x

Not SWIFT-compliant

:20: M Transaction

Reference

Number

16x

:21: O Transaction 16x

43

Reference

Number Related

Reference

Not used by RCM

:25: M Account

Identification

35x

:28C: M Statement

Number/Sequence

Number

5n[/5n]

As RCM does not make use of

multiple messages for one

statement the sequence number is

not used.

:60F: M Opening Balance 1!a6!n3!a15d

:61: O [0-n] Statement Line 6!n[4!n]2a[1!a]15d1!a3!c16x[//16x]

[34x]

1 M Value Date 6!n

2 O Entry date [4!n]

3 M (Reversed) Debit/

Credit Mark

2a

4 O Funds Code [1!a]

5 M Amount 15d

6 M Transaction Type

Identification

Code

1!a3!c

7 M Reference for the

Account Owner

16x

8 O Account

Servicing

Institution's

Reference

[//16x]

9 O Supplementary

Details

[34x]

:86: O [0-n] Information to

Account Owner

6*65x

:62F: M Closing Balance

(Booked Funds)

1!a6!n3!a15d

:64: O Closing Available

Balance

(Available Funds)

1!a6!n3!a15d

:65: O [0-n] Forward

Available Balance

1!a6!n3!a15d

RCM will provide a maximum of

four Forward Available Balance

:86:

O Information to

Account Owner

6*65x

Not used by RCM.

Each line ends with carriage-return/ line-feed (ASCII-hex 0D0A).

If multiple dates are selected the statements will be downloaded in ascending date-

order (oldest statements first).

If multiple accounts and multiple dates are selected the statements will be downloaded

in ascending account/date-order (lowest accountnumber, oldest statement first).

44

5.3 Content description

5.3.1 Fileheader


Fileheader Alphanumeric 5 :940: Fixed value, will occur only

once in the file.

5.3.2 Field-20: Transaction Reference Number


Record code Alphanumeric 4 :20: Fixed value

Format Alphanumeric 3 940 Fixed value

Usage rule code Alphanumeric 1 A Fixed value. Meaning?


5.3.3 Field-25: Account Number



Account identification Alphanumeric 35 RCM convention for

Rabobank-accounts:

9999.99.999AAA otherwise

35x.

For none Rabobank-accounts

the account is presented as

received from account

servicing banks.

5.3.4 Field-28C: Statement Number/Sequence Number

Separator and Sequence number are only present when multiple messages for one statement is

applicable.


Record code Alphanumeric 5 :28C:

Statement number Numeric 5 No leading zeros.

Separator Alphabetic 1 “/”

Sequence number Numeric 5 No leading zeros.

45

5.3.5 Field-60F: Opening Balance

This field must always be the same as field 62a (closing balance) of the previous customer

statement message for this account.



Debit/ Credit Alphanumeric 1 Value: "D" or "C"


The date will be equal to the

date of the previous

statement. As only one

statement is available per

date the date will be before

the present statement date,

Currency code Alphanumeric 3 Format: ISO-Currency code

Opening balance Alphanumeric 15 Balance will be equal to the

closing balance of the

previous statement

5.3.6 Field-61: Statement Line




Entry date Numeric 4 Format: MMDD

Debit/ Credit Alphanumeric 1-2 Value: "D", "C", “RD” or

“RC”. R=Reversed

Amount Numeric 15


Reference for the

Account Owner

Alphanumeric 16 If present otherwise

“NONREF”

Account Servicing

Institution's Reference

Alphanumeric 16 If present

preceded by

“//”.

Not used by RCM

Supplementary Details Alphanumeric 34 Not used by RCM

46

5.3.7 Field-86: Description.


Field code Alphanumeric 4 :86:

Description Alphanumeric 65 Remittance information. All

available transaction

descriptions

5.3.8 Field-62F: Closing Balance


Field code Alphanumeric 5 :62F:

Debit/ Credit Alphanumeric 1 Value: "D" of "C"



Closing balance Numeric 15 Including all forward dated

entries.

5.3.9 Field-64: Closing Available Balance

This field indicates the funds which are available to the account owner (if credit balance) or

the balance which is subject to interest charges (if debit balance).

The closing available balance excludes all forward valued entries.






Closing available

balance

Numeric 15

5.3.10 Field-65: Forward Available Balance

When there is more than one value date for the items booked to the account (in this or

previous statement periods), this field will indicate the balance which will be available to the

account owner on the date(s) indicated.

This field can occur for as many balances that are available. RCM will standard provide either

none (no forward balances supported for the account) or available balances of the next four

business days.

47






Forward Available

balance

Numeric 15

48

6 SWIFT MT942

6.1 General information

The formal name for this report format is “MT 942 Interim Transaction Report”. It is used to

transmit detailed and/or summary information about entries debited or credited to the account

since:

The last statement (MT940) or balance report (MT941) or

The last interim transaction report (sent in the period since the last statement or

balance report).

The SWIFT MT942 delivered by RCM is not fully SWIFT compliant. The maximum length

can be more than 2000 characters.

As with RFLP-RCM the user can select entries to be reported the incremental reporting is not

applicable. This is subverts the use of statement numbering (field-28C). As the field is

mandatory, the unrealistic value 99999 is used.

6.2 Content

A field (label, tag) proceeds each information block in a customer statement message. The

field content can be composed of various items.

Field Subfield Mandatory/

Optional

Field name Format, Content, Options

[]=optional, !=fixed length,

n=numeric, a=alphabetic,

x=alphanumeric

:942: M 5x

Not SWIFT-compliant

:20: M Transaction

Reference

Number

16x

:21: O Related Reference 16x

Not used by RCM

:25: M Account

Identification

35x

:28C: M Statement

Number/Sequence

Number

5n[/5n]

:34F: M Floor Limit

Indicator

3!a[1!a]15d

Functionality is not supported by

RCM. Filling is default Account

currency and amount zero. No debit

or credit character.

:34F: O Floor Limit

Indicator

3!a[1!a]15d

Not used by RCM

:13D: M Date/Time

Indication

6!n4!n1x4!n

49

:61: O [0-n] Statement Line 6!n[4!n]2a[1!a]15d1!a3!c16x[//16x]

[34x]

1 M Value Date 6!n

2 O Entry date [4!n]

3 M (Reversed) Debit/

Credit Mark

2a

4 O Funds Code [1!a]

5 M Amount 15d

6 M Transaction Type

Identification

Code

1!a3!c

7 M Reference for the

Account Owner

16x

8 O Account

Servicing

Institution's

Reference

[//16x]

9 O Supplementary

Details

[34x]

:86: O [0-n] Information to

Account Owner

6*65x

:90D: O Number and Sum

of Entries

5n3!a15d

:90C: O Number and Sum

of Entries

5n3!a15d

:86:

O Information to

Account Owner

6*65x

Not used by RCM.

6.2.1 Explanation

Each line ends with carriage-return/ line-feed (ASCII-hex 0D0A).

The file start with the value “:942:” on the first line.

Each statement in the file starts with a field-20.

Field-61 and -86 as group are repeated for each booked entry on the account.

If multiple dates are selected the statements will be downloaded in ascending date-

order (oldest statements first).

If multiple accounts and multiple dates are selected the statements will be downloaded

in ascending account/date-order (lowest accountnumber, oldest statement first).

6.3 Detailed description

6.3.1 Fileheader


Fileheader Alphanumeric 5 :940: Fixed value, will occur only

once in the file.

50

6.3.2 Field-20: Transaction Reference Number


Record code Alphanumeric 4 :20: Fixed value

Format Alphanumeric 3 942 Fixed value

Usage rule code Alphanumeric 1 A Fixed value. Meaning?


Time Numeric 6 Format: HHMMSS

6.3.3 Field-25: Account Number



Account identification Alphanumeric 35 RCM convention for

Rabobank-accounts:

9999.99.999AAA otherwise

35x.

For none Rabobank-accounts

the account is presented as

received from account

servicing banks.

6.3.4 Field-28C: Statement Number/Sequence Number



Statement number Numeric 5 99999

6.3.5 Field-34F: Floor Limit Indicator



Currency Alphabetic 3 Account-currency

Amount Numeric 1 0,0

6.3.6 Field-13D: Date/Time Indication


Record code Alphanumeric 5 :13D:

Statement number Numeric 5

51

6.3.7 Field-61: Statement Line




Debit/ Credit Alphanumeric 1-2 Value: "D", "C", “RD” or

“RC”. R=Reversed

Amount Numeric 15d


Counterparty account

number

Alphanumeric 16 When counterparty account

number is unknown, the

field gets the value:

"NONREF"

Name counterparty

account number

Alphanumeric 34 If the information is not

available, this field will be

empty.

6.3.8 Field-86: Description.



Description Alphanumeric 65 Remittance information. All

available transaction

descriptions

6.3.9 Field-90D: Number and sum of entries


Record code Alphanumeric 5 :90D:

Statement number Numeric 5 Number of debit entries in

this report.


Amount Numeric 15d Sum of debit entries in

account-currency

52

6.3.10 Field-90C: Number and sum of entries



Statement number Numeric 5 Number of credit entries in

this report.


Amount Numeric 15d Sum of credit entries in

account-currency

53

7 Comma Separated Values (CSV)

7.1 General information

The CSV ("Comma Separated Value") file format is often used to exchange data between

disparate applications. The file format, as it is used in Microsoft Excel, has become a pseudo

standard throughout the industry, even among non-Microsoft platforms. CSV files have

become somewhat of a legacy format. CSV files had become a de facto industry standard.

Via two options, CSV-download is supported. Either via the “> export to CSV” button or via

the “> download”.

The “> export to CSV”-option will generated a standard CSV-file which contains all

the columns in the sequence as shown on the screen.

The standard CSV used comma as delimiter and heading in the first line.

The “> download”-option enable to select a user-defined conversion.

User-options are: headings or no-headings in the first line, field separator: tab (ASCII-

hex 09), blank “ ”, comma “,”, colon “:” and semicolon “;”, column selection and

column order.

The proprietary conversions are based on one of three scopes: balance, statement or

transaction.

The balance scope informs on the actual balances on accounts with or without intraday

transactions – transactions processed since the last statement. The values can change

continuously based on newly processed data.

The statement scope informs of the static situation of specific statements. The values

reported are fixed and will not change anymore.

The transaction scope informs on the details of a transactions. Either a selection made

by the user or the set of transaction belonging to a statement.

The content enumeration for the CSV-format is identical to the Paper/PDF-format. The one

major difference is that the user can define proprietary conversions to customize details-

reports.

For CSV item-labels will become headers. General information will be repeated for each line.

Paper/ PDF Transaction details

Details EXAMPLE

Account number 123456789

Bank SWIFT BIC RABONL2U

Entry date Value date Amount

24/4/2008 28/4/2008 250,00

25/4/2008 28/4/2008 110,00

25/4/2008 2/5/2008 1250,00

54

CSV equivalent

Account number;Bank SWIFT BIC;Entry date;Value date;Amount

123456789;RABONL2U;24/4/2008;28/4/2008;250,00

123456789;RABONL2U;25/4/2008;28/4/2008;110,00

123456789;RABONL2U;25/4/2008;2/5/2008;1250,00

Documents

Format Description - Rabobank · Our reference Format Description ... 2 Clieop 03 Format 2.1 Clieop03 ... With regard to business payment instructions it is recommend that the creditor