Format Description. Version, date Project. 6, March 10, 2011 Rabo Cash Management

Transcription

1 Format Description Version, date Project 6, March 10, 2011 Rabo Cash Management 1

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 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. 2

3 Contents 1 General information 4 2 Clieop 03 Format Clieop03 Description Structure of CLIEOP CLIEOP03 Info classification CLIEOP03 Fields CLIEOP03 validations by Rabobank 15 3 BTL91 IMPORT FORMAT BTL 91 General BTL 91 Record layout BTL 91 Field description BTL 91 Appendix 29 4 Rabo MT940 Extended General information SWIFT MT940 Specifics SWIFT MT940 file structure SWIFT MT940 File layout Extended options 39 Examples: 41 5 SWIFT MT940 standard General information Format structure Content description 44 6 SWIFT MT General information Content Detailed description 49 7 Comma Separated Values (CSV) General information 53 3

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

5 2 Clieop 03 Format 2.1 Clieop03 Description 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 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 CLIEOP Structure These specifications of the CLIEOP 03 are according to Equens (Dutch clearing institute) standards Version CLIEOP 03 can be used for: (non) nett creditor and salary payments nett direct debits non-nett direct debits 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 Lay-out The following lay-out is also used by the Dutch clearing institute. 5

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. 6

7 2.2.5 Structure diagram Diagram describing the modular structure for Clieop-format. Cient instruction classification (Clieop03) File header info (0001) Mandatory (1) Batches with payments of direct debits Man. ( ) File close info (9999) Mandatory (1) Batch header info (0010) Mandatory (1) Fixed description info (0020) Optional (0-4) Initiator info (0030) Mandatory (1) Business payments or direct debits Man. ( ) Batch close info (9990) Mandatory (1) Transaction info (0100) Name of payer info (0110) Address of payer info (0113) Payment reference info (0150) Description info (0160) Name of payee info (0170) Address of payee info (0173) Mandatory (1) Optional (0-1) Optional (0-1) Optional (0-1) Optional (0-4) Optional (0-1) Optional (0-1) Direct debit + business payments Direct debit Direct debit Direct debit + business payments Direct debit + business payments Business payments Business payments 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. 7

8 2.3 CLIEOP03 Info classification Info classification at file level File header info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 6 Numeric File creation date ddmmyy 12 8 Alphanumeric File name CLIEOP Alphanumeric Sender identification 25 4 Alphanumeric File identification 29 1 Numeric Duplicate code Alphanumeric Filler File close info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 45 Alphanumeric Filler Info classification at batch level Batch header info Start Length Type Name Contents position 1 4 Numeric Info. code 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 Alphanumeric Filler 8

9 Fixed description info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 32 Alphanumeric Fixed description Alphanumeric Filler Initiator info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code B 6 1 Numeric NAP (Name/Address/Place) code 7 6 Numeric Desired processing date ddmmyy Alphanumeric Initiator s name 48 1 Alphanumeric Test code Capital P 49 2 Alphanumeric Filler Batch close info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 18 Numeric Total amount Numeric Total account numbers 34 7 Numeric Number of transactions Alphanumeric Filler Info classification at transaction level Direct debit Transaction info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 4 Alphanumeric Transaction type Numeric Amount Numeric Payer s account number Numeric Payee s account number 42 9 Alphanumeric Filler Name of payer info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code B 9

10 6 35 Alphanumeric Name of payer Alphanumeric Filler Address of payer info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code B 6 35 Alphanumeric Address of payer Alphanumeric Filler Payment reference info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 16 Alphanumeric Payment reference Alphanumeric Filler Description info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 32 Alphanumeric Description Alphanumeric Filler Info classification at transaction level Business payments Transaction info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 4 Alphanumeric Transaction type Numeric Amount Numeric Payer s account number Numeric Payee s account number 42 9 Alphanumeric Filler Payment reference info Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 16 Alphanumeric Payment reference Alphanumeric Filler Description info 10

11 Start Length Type Name Contents position 1 4 Numeric Info. code Alphanumeric Variant code A 6 32 Alphanumeric Description Alphanumeric Filler Name of payee info Start Length Type Name Contents position 1 4 Numeric Info code Alphanumeric Variant code B 6 35 Alphanumeric Name of payee Alphanumeric Filler Address of payee info Start Length Type Name Contents position 1 4 Numeric Info code Alphanumeric Variant code B 6 35 Alphanumeric Address of payee Alphanumeric Filler 11

12 2.4 CLIEOP03 Fields 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 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 ,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: 12

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. 13

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, 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 14

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 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 For direct debits (transactiongroup 10 ) the order type in transaction record (0100) must be 1001 or 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. 15

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). 16

17 3 BTL91 IMPORT FORMAT 3.1 BTL 91 General Characteristics Format Maximum record length End of record Field separator Field identifier Variable 194 [CR][LF], included in record length None None Record types 1 Leading record 4 Payment records 1 Total record 1 Terminal record Record layout 1 Leading ecord n Payment records n Total record 1 Terminal record 3.2 BTL 91 Record layout Leading record No Name Type Start LengtDec Contents position h Record code Numerical Exchange bank Alphanumeric 3 4 RABO Medium code Alphanumeric Version number Numeric File creation date Numeric 10 8 CCYYMMDD Batch number Numeric Initiator s name Alphanumeric Initiator s address Alphanumeric Initiator s place Alphanumeric Initiator s country Alphanumeric Business sector Numeric Desired processing date Numeric CCYYMMDD Filler Alphanumeric Payment record Part 1 No Name Type Start LengtDec Contents position h Record code Numeric Payment order no. Numeric 3 4 Unique ISO currency code of Initiator s account Alphanumeric

18 21-04 Initiator s account Numeric ISO currency code of payment order Alphanumeric Payment order amount Numeric Value> Desired processing date Numeric 38 8 CCYYMMDD Domestic costs code Alphanumeric , 2 or Correspondent costs code Alphanumeric , 2 or Payment method code Alphanumeric , 1 or Processing code Alphanumeric or Cheque crossing code Alphanumeric Cheque forwarding code Alphanumeric Payment instruction code 1 Alphanumeric Payment instruction code 2 Alphanumeric Payment instruction code 3 Alphanumeric Payment instruction code 4 Alphanumeric Payment category code Alphanumeric , 2, 3, 4 or Nature of payment code 1 Alphanumeric Nature of payment code 2 Alphanumeric DNB registration no. Alphanumeric Goods code Alphanumeric Article no. Alphanumeric Trader no. Alphanumeric Instructions Alphanumeric Payment record Part 2 No Name Type Start LengtDec Contents position h 22-1 Record code Numeric Payment order no. Numeric 3 4 Content field Beneficiary s account¹ Alphanumeric Beneficiary s name Alphanumeric Beneficiary s address Alphanumeric Beneficiary s place Alphanumeric Beneficiary s ISO country code Alphanumeric Beneficiary s country Alphanumeric Filler Alphanumeric ¹ The use of IBAN for beneficiary accountnumbers is obligatory when paying in an EEA currency to an EEA country Payment record Part 3 No Name Type Start LengtDec Contents position h 23-1 Record code Numeric Payment order no. Numeric 3 4 Content field SWIFT address of beneficiary s bank Alphanumeric Name of beneficiary s bank Alphanumeric Address of beneficiary s bank Alphanumeric Place of beneficiary s bank Alphanumeric ISO country code of beneficiary s bank Alphanumeric Country of beneficiary s bank Alphanumeric Instructions Alphanumeric

19 3.2.5 Payment record Part 4 No Name Type Start LengtDec Contents position h 24-1 Record code Numeric Payment order no. Numeric 3 4 content field Payment reference 1 Alphanumeric Payment reference 2 Alphanumeric Payment reference 3 Alphanumeric Payment reference 4 Alphanumeric Filler Alphanumeric Total record per currency code No Name Type Start LengtDec Contents position h 31-1 Record code Numeric ISO currency code of totals record Numeric Total amount Numeric Number of payment orders Numeric Filler Alphanumeric Total record In BTL91 it is mandatory to find, check and verify all values in every payment record. 19

20 3.2.7 Terminal record No Name Type Start LengtDec Contents position h 41-1 Record code Numeric Total number of records Numeric Total number of payment orders Numeric Hash-code Numeric Filler Alphanumeric Terminal record In BTL91 it is mandatory to find, check and verify all values in every payment record. 3.3 BTL 91 Field description 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 LEADING RECORD 11-1 RECORD CODE Description Code for the type of record. The leading record always contains the value '11'. Values 11 20

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 Values Version number of the medium software used. Customer should choose and fill in a permitted value within the range of 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 = ; Valid date BATCH NUMBER Description Values 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 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 Values not applicable 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 Values not applicable INITIATOR S COUNTRY 21

22 Description Values Validations Name of country where the initiator is established. not applicable Optional field 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. Values not applicable Validations Optional field 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 = Validations Optional field; Valid date PAYMENT RECORD PART RECORD CODE Description Values 21 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 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 ; numbering in ascending order from 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. Values not applicable ; leading zero; valid Rabobank account number at positions 2 to ISO CURRENCY CODE OF PAYMENT ORDER Description ISO code of currency in which the payment order is made out. Values Code included in ISO currency code table 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. Values not applicable 22

23 Validations Mandatory field; greater than zero; smaller than 9 billion (irrespective of currency); a zero in third decimal place 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 = ; valid date; must be equal of higher then current date 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 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 code 1 (cheque payment). Option 3 (SHA) is mandatory when paying in EEA currency to an EEA country 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 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. Validations Conditional field. Optional field when code 1 (cheque payment) 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 code 1 (cheque payment) CHEQUE FORWARDING CODE Description The code in this field indicates the address to which the cheque has to be forwarded. 23

24 Values Validations 1 = initiator's branch; 2 = initiator; 3 = beneficiary. Conditional field. Optional field when code 1 (cheque payment) /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 Validations Optional field PAYMENT CATEGORY CODE Description This info is as of april no longer in use Values not applicable Validations not applicable 21-19/20 NATURE OF PAYMENT CODE (1 and 2) Description This info is as of april no longer in use Values not applicable Validations not applicable DNB REGISTRATION NO. Description This info is as of april no longer in use Values not applicable Validations not applicable GOODS CODE Description This info is as of april no longer in use Values not applicable Validations not applicable ARTICLE NO. Description This info is as of april no longer in use Values not applicable Validations not applicable TRADER NO. Description This info is as of april no longer in use Values not applicable Validations not applicable PAYMENT RECORD PART RECORD CODE Description Code for the type of record. Values PAYMENT ORDER NO. Description Number to identify payment orders within a file (same number as 21-2). Values BENEFICIARY S ACCOUNT² Description Bank account number of the beneficiary. 24

25 Values Validations See appendix d: account numbers with national bank code Conditional field. Optional field when code 1 (cheque payment) BENEFICIARY S NAME Description Name of beneficiary. Values not applicable 22-5 BENEFICIARY S ADDRESS Description Address of beneficiary. Values not applicable ² The use of IBAN for beneficiary accountnumbers is obligatory when paying in an EEA currency to an EEA country. 25

26 22-6 BENEFICIARY S PLACE Description Place of beneficiary. Values not applicable 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. Values not applicable Validations Optional field PAYMENT RECORD PART RECORD CODE Description Code for the type of record. Values PAYMENT ORDER NO. Description Number to identify payment orders within a file (same number as 21-2). Values SWIFT ADDRESS OF BENEFICIARY'S BANK³ Description The SWIFT address of the beneficiary's bank. Values not applicable Validations Optional field. Optional field when 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) NAME OF BENEFICIARY'S BANK Description Name of beneficiary's bank. Values not applicable Validations Conditional field. Optional field when code 1 (cheque payment) ADDRESS OF BENEFICIARY'S BANK Description Address of beneficiary's bank. Values not applicable Validations Conditional field. Optional field when code 1 (cheque payment). 3 The use of SWIFT/BIC is obligatory when paying in an EEA currency to an EEA country. 26

27 23-6 PLACE OF BENEFICIARY'S BANK Description Place of beneficiary's bank. Values not applicable Validations Conditional field. Optional field when code 1 (cheque payment) 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. Values not applicable Validations Optional field PAYMENT RECORD PART RECORD CODE Description Code for the type of record. Values PAYMENT ORDER NO. Description Number to identify payment orders within a file (same number as 21-2). Values /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. Values not applicable Validations Optional field TOTAL RECORD 31-1 RECORD CODE Description Code for the type of record. Values 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. Values Code included in ISO currency code table 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 (noncontinental European and American) or decimal comma (continental European) is located between the third and fourth positions from the right. Values not applicable 27

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). Values not applicable ; greater than zero TERMINAL RECORD 41-1 RECORD CODE Description Code for the type of record. Values 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. Values not applicable 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. Values not applicable ; greater than zero 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). Values not applicable Validations Optional field 28

29 3.4 BTL 91 Appendix Appendix A: PAYMENT INSTRUCTION CODE These instructions are intended for the beneficiary's bank. CODE ABBREVIATION IN SWIFT MESSAGE TEXT IN TELEX OF EURO 01 /PHONBEN/ ADVISE BENEF. BY PHONE 02 /TELEXBEN/ ADVISE BENEF. BY TELEX 03 /PHON/ ADVISE BENEF. BANK BY PHONE 04 /TELEX/ ADVISE BENEF. BANK BY TELEX 05 ADVISE BEN. BANK ADVISE BEN. BANK BY BY CABLE/ SWIFT CHARGES FOR CABLE/SWIFT US CHARGES FOR US 06 ADVISE BEN. BANK BY CABLE/ SWIFT WITHOUT CHARGES FOR US ADVISE BEN. BANK BY CABLE/ SWIFT WITHOUT CHARGES FOR US MEANING Advise beneficiary by phone. Advise beneficiary by telex. Advise beneficiary s bank by phone. Advise beneficiary s bank by telex. Advise beneficiary s bank by cable/swift, 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 IF BEN. IS UNKNOWN If beneficiary is unknown or has OR HAS DECEASED PLEASE RETURN AMOUNT OR HAS DECEASED PLEASE RETURN AMOUNT deceased please return amount. 13 THIS PAYMENT IS IRREVOCABLE 14 INTERCOMPANY TRANSFER THIS PAYMENT IS IRREVOCABLE INTERCOMPANY TRANSFER This payment is irrevocable. Intercompany transfer. 29

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 30

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 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 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 : 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. Example of beneficiary's account number : Bank code account number 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 31

32 customer account numbers which do not have the maximum permitted length, must be preceded by zeros. Example of beneficiary's account number : Bank code account number 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. Example of beneficiary's account number : Bank code account number 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. Example of beneficiary's account number : A Bank code account number check digit 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 Austria Belgium Bulgaria Cyprus Czech Republic Denmark Estonia Finland France Germany Greece Hungary Iceland Ireland Italy ISO code AT BE BG CY CZ DK EE FI FR DE GR HU IS IE IT Liechtenstein Latvia Lithuania Luxembourg Malta Monaco 6 Netherlands Norway Poland Portugal Romania Slovakia Slovenia Spain Sweden Switzerland 5 LI LV LT LU MT MC NL NO PL PT RO SK SI ES SE CH 32

33 United Kingdom Currency Euro Bulgarian Lev Czech Koruna Danish Krone Estonian Kroon Hungarian Florint Iceland Krona Latvian Lats Lithuanian Litas Norwegian Kroner Polish Zloty Romanian Leu Swedish Krona Swiss Franc 5 United Kingdom Pound GB ISO code EUR BGN CZK DKK EEK HUF ISK LVL LTL NOK PLN RON SEK CHF GBP 33

34 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: 35

36 SWIFT-MT940 record structure (schematicaly) :940: Fixed value :20: Mark + date 1 :25: :28: :60F: Accountnumber 1 Statement number Previous account ballance 1 Next account :61: Transaction 1 :86: First description of transaction 1 :86: Second description of transaction 1 :61: Transaction 2 :86: First description of transaction 1 Note: The sequence is first all data for one account, followed by other accounts (if present). :86: Second description of transaction 1 :62F: Current account balance 1 :64: :65: Available balance 1 Forward available balance 1 Next account :20: Mark + date 2 :25: Account number 1 :28: Repetition of previous items :20: Mark + date 1 :25: Account number 2 Of the next account. :28: Repetition of previous items Mandatory Mandatory if present Optional 36

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 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: EUR_MT940file [1].txt MT940 were it concerns (SWIFT-) standard MT940 and ME940 where it concerns (Rabo-) extended MT 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 Usage rule code Alphanumeric 1 A Entry date Numeric 6 Format: YYMMDD 37

38 Record :25: Account Number Description Type Length Contents Comment Record code Alphanumeric 4 :25: Account number Alphanumeric 35 Details Record :28: Statement Number/Sequence Number Description Type Length Contents Comment Record code Alphanumeric 4 :28: Statement number Numeric Details Separator Alphanumeric 1 / Sequence number Numeric 2 00 Record :60F: Previous Accounting Balance Description Type Length Contents Comment Record code Alphanumeric 5 :60F: Credit / Debit Alphanumeric 1 Value: "C" or "D" Entry date Numeric 6 Format: YYMMDD Currency code Alphanumeric 3 Format: ISO-Currency code Previous accounting balance Alphanumeric 15 Record :61: Statement Line Description Type Length Contents Comment Record code Alphanumeric 4 :61: 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 Type Length Contents Comment Record code Alphanumeric 4 :86: Description Alphanumeric 65 Details Record :62F: Current Accounting Balance Description Type Length Contents Comment Record code Alphanumeric 5 :62F: Credit / Debit Alphanumeric 1 Value: "C" of "D" Entry date Numeric 6 Format: YYMMDD Currency code Alphanumeric 3 Format: ISO currency code Current accounting balance Numeric 15 38

39 Record :64: Available Balance at Entry Date Description Type Length Contents Comment Record code Alphanumeric 4 :64: Credit / Debit Alphanumeric 1 Value: "C" of "D" Entry date Numeric 6 Format: YYMMDD Currency code Alphanumeric 3 Format: ISO currency code Available balance Numeric 15 Record :65: Forward Available Balance Description Type Length Contents Comment Record code Alphanumeric 4 :65: Credit / Debit Alphanumeric 1 Value: "C" of "D" Entry date Numeric 6 Format: YYMMDD Currency code Alphanumeric 3 Format: ISO currency code Available balance Numeric Extended options General information When exporting SWIFT MT940 within RCM, you will find a screen with several options witch you can change with checkboxes: these options.. Underneath you will find the explanation of 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 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 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. 39