officenet direct data import formats - abn amro importing, we mean integrating a file with payments...

OfficeNet Direct data import formats

CLIEOP 03

ABN AMRO BTL91

Version 1.12 January 2008

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________

OfficeNet Direct Format Book

2

ABN AMRO Bank N.V. 2008 All rights reserved. With the exception of the conditions specified in or based on the 1912 Copyright Act, no part of this publication may be reproduced and/or made public by print, photocopy, microfilm, or any other means whatsoever, nor may the document be stored in a data storage system without the express written permission of ABN AMRO Bank N.V.

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


3

Getting started with OfficeNet Direct formats This document is written for people who define specifications for importing data to the ABN AMRO OfficeNet Direct electronic banking product. OfficeNet Direct is a stand-alone product. It can be used as a communication module for the OfficeNet Extra modules Domestic payments, Foreign payments and Direct debits. OfficeNet Direct can also be used as a communication module with other financial packages, allowing you to send Payments to ABN AMRO Bank and retrieve reporting information from ABN AMRO Bank. Should you have questions and/or remarks regarding this document, please contact the Electronic Banking Service Desk. You can also address questions to the following department: ABN AMRO Bank N.V. Functional Management & Support Interactive Banking T.a.v. Beheer formaten P.O. Box 283 1000 EA Amsterdam PAC AA2444 e-mail: [email protected] Although the information in this document has been compiled with the utmost care, we can accept no liability for any errors or inaccuracies. We reserve the right to modify the (technical) data of the products mentioned in this document at any time without prior notification. We accept no liability from any third parties who may use the information presented in this document.

ABN AMRO Bank N.V.

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


4

Contents

1. A BRIEF REVIEW........................................................................................................................5

2. PROCESSING PAYMENTS IN OFFICENET DIRECT ..........................................................6

3. CLIEOP03......................................................................................................................................7

3.1 GENERAL .................................................................................................................................7 3.2 ORDER TYPES...........................................................................................................................7 3.3 RECORDS CLIEOP03-FORMAT ..................................................................................................8 3.4 EXPLANATION OF THE RECORDS FROM THE CLIEOP03-FORMAT ............................................10 3.5 ELEVEN CHECK BANK ACCOUNT NUMBERS............................................................................12 3.6 SUPPORTED CHARACTERS ......................................................................................................13 3.7 DEVIATIONS IN ADMINISTRATIVE PROCESSING ......................................................................13

4. ABN AMRO BTL91 ....................................................................................................................14

4.1 GENERAL ...............................................................................................................................14 4.2 ORDER TYPES.........................................................................................................................14 4.3 FILESTRUCTURE.....................................................................................................................14 4.4 RECORD LAYOUT...................................................................................................................14 4.4.1 LEADING RECORD LAYOUT........................................................................................................15 4.4.2. PAYMENT RECORD LAYOUT – SUB RECORD 1 OF 4.............................................................16 4.4.3. PAYMENT RECORD LAYOUT – SUB RECORD 2 OF 4.............................................................18 4.4.4. PAYMENT RECORD LAYOUT – SUB RECORD 3 OF 4.............................................................18 4.4.5. PAYMENT RECORD LAYOUT – SUB RECORD 4 OF 4.............................................................18 4.4.6. TOTALS RECORD LAYOUT..................................................................................................19 4.4.7. TERMINAL RECORD LAYOUT..............................................................................................19 4.5 RELATION CHECKS.................................................................................................................20 4.6 CRITERIA EU-PAYMENT (IBAN/BIC)....................................................................................21 4.7 THE USE OF DES-HASH IN COMBINATION WITH BTL91 FILES................................................21 APPENDIX A: PAYMENT INSTRUCTION CODES .........................................................................22

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


5

1. A brief review

OfficeNet Direct supports the ClieOp03, ABN AMRO BTL91, SWIFT MT940 and SWIFT MT942 formats. The format descriptions in this document enable the import of data in OfficeNet Direct from other software-programs with the use of the CLIEOP03- or BTL91-format. This document contains the data characteristics that must be considered in these data. The deviations from official format descriptions issued by the suppliers of data in the various formats are also handled in this document. By importing, we mean integrating a file with Payments in OfficeNet Direct created by another program. The formats supported by OfficeNet Direct are: For importing data in OfficeNet Direct: - ClieOp03

- ABN AMRO BTL91 For exporting data from OfficeNet Direct - SWIFT MT940

- SWIFT MT942 The formats were developed to facilitate electronic data processing (payments or account statements). ClieOp03 is an Equens format for submitting domestic payment and direct debits orders. The BTL91 format is an ABN AMRO format that supports the electronic delivery of foreign payment orders. The SWIFT (Society for Worldwide Interbank Financial Telecommunication) formats MT940 and MT942 make it possible to export account data. The formats in OfficeNet Direct differ from the official format descriptions while in some cases other validations apply. This is necessary to support administrative processing in the ABN AMRO systems. This document describes the specific characteristics for correct data delivery via OfficeNet Direct using ClieOp03 and ABN AMRO BTL91. The file layout for the SWIFT MT940 and MT 942 formats as used for the presentation of account information is not explained in this document.

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


6

2. Processing payments in OfficeNet Direct

This section contains a brief explanation of how payments, which comply with the ClieOp03 and ABN AMRO BTL91, are processed in OfficeNet Direct. For a detailed description, please see the help texts supplied with the OfficeNet Direct package. To view help texts, press function key F1. Payments in ClieOp03 and ABN AMRO BTL91 format can be created in a financial package or one of the OfficeNet Extra modules. Once created, the payments must be stored in a file. OfficeNet Direct can automatically process this file if: - the file complies with the format descriptions - the file is placed in the directory specified in the OfficeNet Direct settings. The locations of the directories are specified in the OfficeNet Direct settings, which can be opened via 'Settings\Conversions\OfficeNet Direct '. Once the order files have been placed in these directories, these files will be processed in OfficeNet Direct, from which they can be signed and sent to the bank. The process is shown in the figure below. Figure 1. Creating and processing payments using OfficeNet Direct Note The extension given to the file is of no importance. As long as the files comply with the format descriptions, OfficeNet Direct can automatically process them. During processing, the payments in the file are checked to determine whether they can be processed by ABN AMRO Bank. OfficeNet Direct may discover that payments cannot be signed and sent to the bank because they do not comply with certain requirements. This is indicated via the file status in the screen 'Orders\Imported' in OfficeNet Direct. Payments that cannot be imported are displayed in the screen 'Orders\Rejected by import'. Additional information on the status of payments and rejected order files can be found in the help texts for this screen. The information on the ClieOp03 and ABN AMRO BTL91 formats in this document is based on the standard installation of OfficeNet Direct. This assumption plays a role in determining the settings for the directories in which the order files are placed.

Create payments in financial package or module

Save file in specified directory

Start OfficeNet Direct and select Payments, Imported

Sign the payments and send them to ABN AMRO Bank

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


7

3. ClieOp03

The peculiarities described in this chapter regarding use of the ClieOp03 format with OfficeNet Direct are based on the official ClieOp03 format description issued by Equens (formerly Interpay) . The ClieOp03-format description can be downloaded from www.equens.com. Under “File Layout” you’ll find a link to the PDF-files Clieop and Clieop NL.

3.1 General

Batch payments: pure/impure Postbank payments A Postbank order (transfer to or direct debit from a Postbank account) is pure if the customer has verified that the Postbank account holder’s name and address correspond to the account data as registered with the Postbank. If so, these files can be imported without name and address data. The Postbank performs no further name/number check on ‘pure’ payments. To enable the import of pure payments in OfficeNet Direct, you must specify in the transaction type field of the ClieOp03 file that the order must be processed as pure.

3.2 Order types

The checks performed by OfficeNet Direct and the manner in which the payments must be delivered for processing are determined by: � the directory in which the payments are placed; � the individual order and batch settings in OfficeNet Direct; � any specifications included in the order file. These items are explained below. Urgent payments and non-urgent payments Whether a payment is processed as urgent or non-urgent depends on the directory in which the Clieop-File is placed in OfficeNet Direct. Domestic payments to be processed as urgent payment have to be placed in the directory 'installation directory'\ClieOp\Spoed Non-urgent payments have to be placed in the directory 'installation directory'\ClieOp\ . Individual or batch When importing into OfficeNet Direct, you can specify whether the payments in the import file must be processed collectively (batch processing) or individually. To do this, select ‘Settings’, followed by ‘General’. To process imported payments as a batch, activate the ‘Treat orders as batch’ checkbox. The total amount of payments processed as a batch is reported on the account statement. To process the imported payments individually, do not activate the checkbox.

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


8

Note! - This setting only applies when OfficeNet Direct is used with a financial package. If

the Domestic Payments module of OfficeNet Extra is used to create payments, the type of processing (batch, urgent, non-urgent or acceptgiro collection form) determines how the payments are processed in OfficeNet Direct.

- Direct debits are always processed in batches. Acceptgiro The settings described above can be used to make a distinction between urgent payments and non-urgent payments and between individual and batch payments. The distinction between normal (bankgiro) and acceptgiro collection form payments is indicated by specifying the payment reference and the form code of the acceptgiro collection form in the ClieOp03 file. This approach makes it possible to retain the reference of the acceptgiro collection form in the payment process. Form code To have OfficeNet Direct process an order as an acceptgiro collection form, place the two-digit form code at the end of the filler of info code 100, in the first position following the account number. The form code is specified in the white bar in the lower right-hand corner of the acceptgiro collection form (possible values are 12, 13, 14 and 15). If applicable, the payment reference for an acceptgiro collection form can be placed in info code 0150. Direct debit payments Direct debit payments can be identified by transaction type (1001 or 1002). These payments must always be delivered in a separate batch.

3.3 Records Clieop03-format

Legend 9(n) the field is numeric and n digits long X(n) the field is alphanumeric and n characters long

Name Form Mandatory

Value Remark/description

Fileheader record Record code Variant code File creation date File name Sender identification File identification Duplicate code Filler

9(4) X(1) 9(6) X(8) X(5) X(4) 9(1) X(21)

0001 A CLIEOP03 1

format ddmmyy not mandatory in OfficeNet mandatory value in OfficeNet

Filetrailer record Record code Variant code Filler

9(4) X(1) X(45)

9999 A

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


9

Name Form Mandatory


Batchheader record Record code Variant code Transactiongroup Account number ordering party Batch sequence number Delivery currency Filler

9(4) X(1) X(2) 9(10) 9(4) X(3) X(26)

0010 B EUR

In case of importing a single batch value “0000” is valid

Fixed description record Record code Variant code Fixed description Filler

9(4) X(1) X(32) X(13)

0020 A

This record is not mandatory in a file but if used the record must contain data

Ordering party record Record code Variant code Name code Desired processing date Name ordering party Test code Filler

9(4) X(1) 9(1) 9(6) X(35) X(1) X(2)

0030 B 1 P

mandatory value in OfficeNet format ddmmyy mandatory value in OfficeNet

Batchtrailer record Record code Variant code Total amount Total account numbers Number of items Filler

9(4) X(1) 9(18) 9(10) 9(7) X(10)

9990 A

Transaction record Record code Variant code Transactiontype Amount Account number payer Account number beneficiary Filler In case of an acceptgiro filler is replaced by: Form code Filler

9(4) X(1) X(4) 9(12) 9(10) 9(10) X(9) 9(2) X(7)

0100 A

value 12, 13, 14 or 15

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


10

Name Form Mandatory


Name payer record Record code Variant code Name payer Filler

9(4) X(1) X(35) X(10)

0110 B

Only in combination with direct debit transactiontype 1001 or 1002

City payer record Record code Variant code City payer Filler

9(4) X(1) X(35) X(10)

0113 B

This records is optional since 2005. Only in combination with Recordcode 0110 (see above)

Payment reference record Record code Variant code Payment reference Filler

9(4) X(1) X(16) X(29)

0150 A

Mandatory in combination with an acceptgiro with form code 13 or 15

Description record Record code Variant code Description Filler

9(4) X(1) X(32) X(13)

0160 A

This record is not mandatory in a file but if used the record must contain data

Name beneficiary record Record code Variant code Name beneficiary Filler

9(4) X(1) X(35) X(10)

0170 B

This record is not mandatory in case of batch processing

City beneficiary record Record code Variant code Filler

9(4) X(1) X(45)

0173 B

This record is optional since 2005.

3.4 Explanation of the records from the Clieop03-format

Unless otherwise stated in the description of a field, the following applies: • alphanumeric fields are left justified and padded with trailing spaces; • numeric fields are right justified and padded with leading zeros; • empty alphanumeric fields and Fillers contain spaces; • empty numeric fields contain zeros; • the field has to be filled.

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


11

Account number beneficiary (Transaction record) The account number of the recipient of Amount. Postbank account numbers are not preceded by a P, but by leading zeros. Bank account numbers satisfy the eleven check. With direct debit this number is the same as Account number ordering party. Account number ordering party (Batchheader record) The bankaccount number of the ordering party of the batch. Bank account numbers satisfy the eleven check. Account number payer (Transaction record) The account number of the payer of Amount. With business payments this number is the same as Account number ordering party. Postbank account numbers are not preceded by a P, but by leading zeros. Bank account numbers satisfy the eleven check. Amount (Transaction record) The amount of the item in cents. The maximum is EUR 453.780.216,08. Batch sequence number (Batchheader record) Number incremented with one per batch. Numbering may continue through subsequent files. Description (Description record) Text explaining the transaction (invoicenumbers, referencenumbers etc.) Duplicate code (Fileheader record) Mandatory value for OfficeNet is 1 (unicate) File identification (Fileheader record) Identifies the file uniquely per month. Content: position 1 – 2 position 1 – 2 of File creation date (day of the month) position 3 – 4 sequence number, incremented from one by one per delivery day Fixed description (Fixed description record) Contains a description that applies to all items in the batch. Name beneficiary (Name beneficiary record) The beneficiary’s name according to the ordering party. Only the first 24 characters of the field are processed, the rest is ignored. Name code (Ordering party record) Mandatory value for OfficeNet is 1. Name payer (Name payer record) The payer’s name according to the ordering party. Only the first 24 characters of the field are processed, the rest is ignored. Number of items (Batchtrailer record) The number of Transaction records between Batchheader record en Batchtrailer record. The maximum is 100.000. Payment reference (Payment reference record) Reference assigned to the item by the ordering party. With business payments, the payment reference will usually suffice to inform your

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


12

beneficiary. With direct debit, the payment reference is intended primarily for you; you use a description to inform the payer. In revocations the payment reference of the original direct debit is returned to you. If you make sure the payment reference is unique, you can easily see which direct debit is being revoked. This record is mandatory in combination with an acceptgiro with form code 13 or 15. Test code (Ordering party record) Indicates whether the batch is to be processed as production or as test. For OfficeNet the value must be “P”. Total account numbers (Batchtrailer record) The sum of the fields Account number payer and Account number beneficiary in the batch. If this sum exceeds the length of the field, the field is filled with the rightmost ten digits.If this sum differs from Interpay's count, the batch is rejected. Total amount (Batchtrailer record) The sum of the fields Amount in the batch. The maximum is EUR 45.378.021.609,01. Transactiongroup (Batchheader record) Indicates the kind of transaction the batch contains. Values: 00 business payments 10 direct debits Transactiontype (Transaction record) Indicates a further distinction within the Transactiongroup. See further Postbank accounts. Values: 0000 unchecked creditor payment to a Postbank account 0003 unchecked salary payment to a Postbank account 0005 creditor payment to a bank account, or:

checked creditor payment to a Postbank account 0008 salary payment to a bank account, or:

checked salary payment to a Postbank account 1001 direct debit off a bank account, or:

checked direct debit off a Postbank account 1002 unchecked direct debit off a Postbank account

3.5 Eleven check bank account numbers

When creating the file you check whether bank account numbers satisfy the eleven check:

� multiply the leftmost digit of the account number by 10; � multiply the next digit by 9, the digit next to that by 8, and so on, until

you have multiplied the tenth digit by 1; � sum the results of the multiplications; � divide this sum by 11.

If the result of this division is a whole number, the bank account number satisfies the eleven check. As an example we take account number 012.34.56.789: 0 1 2 3 4 5 6 7 8 9 x x x x x x x x x x 10 9 8 7 6 5 4 3 2 1 0 + 9 + 16 + 21 + 24 + 25 + 24 + 21 + 16 + 9 = 165 : 11 = 15

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


13

3.6 Supported characters

When importing a ClieOp03 file, OfficeNet Direct checks whether the characters in the file being delivered can be processed by the ABN AMRO systems. The following characters are supported: - capital letters; - digits; - the punctuation marks space ( ), period (.), asterisk (*), slash (/), at (@), minus

sign/hyphen (-), percentage (%), ampersand (&) and equal sign (=). OfficeNet Direct replaces all other characters with spaces. We therefore recommend that you use supported characters only.

3.7 Deviations in administrative processing

In ClieOp03, a limited number of positions is available for each field. In OfficeNet Direct too, the number of available positions per field is subject to a maximum. The number of available positions in OfficeNet Direct can deviate from the number specified in the ClieOp03 format description. This is due to the file handling method in the ABN AMRO systems. OfficeNet Direct checks the number of positions in the fields when it imports the ClieOp03 file. Any changes that may be made in these fields are indicated in the status assigned to the imported file. OfficeNet Direct also indicates what changes are made. The following table gives the number of positions permitted for each field, split out into order type where applicable. If the field is included in a multi-field data layout, we also specify the data layout to which the field belongs. Number of available positions in OfficeNet Direct

ClieOp03 field OfficeNet Direct

Beneficiary’s name (35 positions) 24 positions (name) Principal’s name (35 positions) 24 positions (name)

Beneficiary’s town (35 positions) 20 positions (town) 18 positions (town) for urgent payments

Principal’s town (35 positions) 20 positions (town)

Payment reference (16 positions) Fixed description (4 * 32 positions) Description (4 * 32 positions)

3 * 32 positions (description, see explanation below)

When the ClieOp03 file is imported in OfficeNet Direct, the fields ‘Payment reference’, ‘Fixed description’ and ‘Description’ are entered in the ‘Description’ field insofar as the number of positions permits. This field contains 3 lines of 32 positions each, with the fields ‘Payment reference’, ‘Fixed description’ and ‘Description’ being entered in that order. A space is inserted between the fields within the available number of positions in OfficeNet Direct. Any characters in excess of the maximum number of positions are dropped.

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


14

4. ABN AMRO BTL91

The details described in this chapter regarding the use of the ABN AMRO BTL91 format in combination with OfficeNet Direct are based on the official Foreign Payments ABN AMRO BTL91 format description (abbreviated as BTL91). Nowadays this format, developed by ABN AMRO itself, is used only for importing foreign payments in OfficeNet Direct

4.1 General

Foreign payments for import in OfficeNet Direct are to be placed in the directory 'installation directory'\BTL91, regardless of the order type.

4.2 Order types

The following foreign order 'types' can be imported in OfficeNet Direct in BTL91 format:

♦ ABN AMRO Foreign payment Normal

♦ ABN AMRO Foreign payment Urgent

♦ ABN AMRO Cheque

♦ ABN AMRO EU-payment (IBAN/BIC) The codes required to define Foreign payments or Cheque payments are available in the BTL91 format description. There is no specific code available for an EU-payment (IBAN/BIC). For composing an EU-payment(IBAN/BIC) see paragraph 4.6.

4.3 Filestructure

A file consists of 1 leading record, 1 batch and 1 terminal record. Each payment order is subdivided into four payments subrecords (1 to 4). Each payment order has a unique number in ascending order. A batch consists of no more than 9999 payment orders followed by one or more totalrecords sorted by the ISO currency code of the orders. These totals records are included after the last payment record and before the terminal record.

4.4 Record Layout

Record length 192 followed by an end-of-record indicator

(ASCII 'CRLF', HEX '0D0A'). Alphabet ASCII Abbreviations used : a = alphanumeric n = numeric d = decimals

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


15

In alphanumeric fields (marked 'a') the following characters are allowed: When importing a BTL91 file, OfficeNet checks whether the characters in the file being delivered can be processed by the ABN AMRO systems. The following characters are supported: - letters A through Z (capitals only) - digits 0 through 9 - the punctuation marks space ( ), period (.), asterisk (*), slash (/), at (@), minus

sign/hyphen (-), percentage (%), ampersand (&) and equal sign (=).

OfficeNet Direct replaces all other characters with spaces. We therefore recommend that you use supported characters only. Empty alphanumeric fields must contain spaces. In numeric fields (marked 'n') the digits 0 through 9 are allowed Empty numeric fields must contain zeros.

4.4.1 Leading Record Layout

Nr. Name Start position

Form Mandatory Value

Remark/description

11-1 11-2 11-3 11-4 11-5 11-6 11-7 11-8 11-9 11-10 11-11 11-12

Record code Exchange bank Medium code Version number File creation date Batch number Payer’s name Payer’s address Payer’s town Payer’s country Business sector Processing date Filler

1 3 7 8 10 18 21 56 91 126 161 165

173

2n 4a 1a 2n 8n 3n 35a 35a 35a 35a 4n 8n

20a

11 ABNA X 01 0000 spaces

* * format YYYYMMDD see below * not mandatory format YYYYMMDD

* Mediumcode, Versionnumber and Business sector are no longer in use, use the fixed values instead.

11-6 Batchnumber Any value between 001 and 999. It is recommended to allocate successive batch numbers.

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


16

4.4.2. Payment record layout – sub record 1 of 4

Nr. Name Start

position Form Mandatory


21-1 21-2 21-3 21-4 21-5 21-6 21-7 21-8 21-9 21-10 21-11 21-12 21-13 21-14 21-15 21-16 21-17

Record code Order number ISO currency code of payer’s account Payer’s account no. ISO currency code of payment Transaction amount Desired processing date Domestic costs code Corr. costs code Payment method code Processing code Cheque crossing code Cheque forwarding code Payment instr. code 1 Payment instr. code 2 Payment instr. code 3 Payment instr. code 4 Filler

1 3 7

10 20

23 38 46 47 48 49 50 51 52 54 56 58 60

2n 4n 3a 10n 3a 15n 3d 8n 1n 1n 1n 1n 1a 1a 2a 2a 2a 2a 133a

21 spaces

see explanation 1st position = 0 format YYYYMMDD

21-2 Ordernumber Serial number of payment order in a batch. Each payment order is subdivided into four payments subrecords. Interrelated subrecords have the same number. Orders are numbered from 0001 upwards. (Values 0001 through 9999) 21-3 ISO currency code of payer’s account ISO currency code of payers accountnumber(ordering party). In case of transactions in debit of the foreign currency (FC) account of payer (currency-code unequal EUR) the currency-code of the payment (21-5) must equal the currency-code of payer’s account (21-3). 21-5 ISO currency code of payment Currency code of transaction amount 21-6 Transaction amount Only numeric characters can be entered. An imaginary decimal point or decimal comma is located between the third and fourth positions from the right. The third decimal must be zero, in case of transfer in JPY or ISK all decimals must be zero. Transaction amount must be between zero and below 90 billion (irrespective of currency). 21-8 Domestic costs code Method of settlement of charges and commissions as charged by ABN AMRO Values: 1 = Costs chargeable to payer’s EUR-account 2 = Costs chargeable to payer’s FC-account (only if record 21-3 is unequal to EUR) 3 = Costs chargeable to beneficiary Relation checks: 6,7,8 see page 20

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


17

21-9 Correspondent costs code Method of settlement of charges and commissions as charged by the foreign (correspondent) bank Values 1 = Costs chargeable to payer’s EUR-account 2 = Costs chargeable to payer’s FC-account 3 = Costs chargeable to beneficiary Relation checks: 6, 7, 8, 9 see page 20 21-10 Payment-method code Indicates whether the payment is to be executed as a transfer or a banker’s cheque issued by ABN AMRO settles payment. Values 0 = Transfer 1 = Cheque Relation checks: 1, 2, 3, 4, 9, 10 see page 20 21-11 Processing code ABN AMRO processes foreign transfers through the SWIFT-network. This code indicated whether transfer has to be processed as “normal” or “urgent” transfer. Values 0 = Normal 1 = Urgent Relation checks: 1, 9 see page 20 21-12 Cheque crossing code Cheques issued by ABN AMRO are always “crossed” indicating that the cheque can only be settled through a bank account and not in cash. Values “J” if payment-method code (record 21-10) = 1 (cheque) “SPACE” in all other cases. Relation checks: 1, 9 see page 21-13 Cheque forwarding code Indicates the addressing of the cheque Values 2 = Send cheque to ordering party 3 = Send cheque to beneficiary Relation checks: 1, 9, 10 see page 20 21-14/17 Payment instruction code Payment instructions addressed to the foreign (correspondent) bank. ATTENTION: Payment instructions can lead to extra handling charges charged by

the foreign (correspondent) bank. These charges are not always transparent.

Values See Appendix A Relation checks: 3, 9 see page 20

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


18




Remark/description

22-1 22-2 22-3 22-4 22-5 22-6 22-7 22-8

Record code Order number Beneficiary’s accountnr. Beneficiary’s name Beneficiary’s address Beneficiary’s town Beneficiary’s countrycode Beneficiary’s country Filler

1 3 7 41 76 111 146 148 183

2n 4n 34a 35a 35a 35a 2a 35a 10a

22 content 21-2 spaces

Relation check 3, 10 ISO-country-code Relation check 10

22-3 Beneficiary’s account number Only digits (0 through 9) and letters (A through Z capitals only) are allowed in this field. The use of punctuation marks can lead to incorrect accountnumbers during import. Relation checks: 3, 5, 9 see page 20




Remark/description

23-1 23-2 23-3 23-4 23-5 23-6 23-7 23-8

Record code Order number Benef.Bank BIC Benef.Bank name Benef.Bank address Benef.Bank town Benef.Bank country code Benef.Bank country Filler

1 3 7 18 53 88 123 125 160

2n 4n 11a 35a 35a 35a 2a 35a 33a


Rel. checks 1,2,4,9 Rel. check 9 Rel. checks 1,2,4,9 Rel. checks 1,4,5,9 Rel. check 9

23-3 Beneficiary’s Bank BIC The BIC-code (SWIFT-address) of beneficiary’s bank. A valid BIC-code consists of 8 or 11 positions without spaces. Position 1 to 6 contain only letters (A through Z capitals only). Position 5 and 6 contain ISO-country code of the beneficiary’s bank and must equal the content of record 23-7. Relation checks: 2, 4, 9 see page 20




Remark/description

24-1 24-2 24-3 24-4 24-5 24-6

Record code Order number Payment reference 1 Payment reference 2 Payment reference 3 Payment reference 4 Filler

1 3 7 42 77 112 147

2n 4n 35a 35a 35a 35a 46a


___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


19

4.4.6. Totals record layout



Remark/description

31-1 31-2 31-3 31-4

Record code Total ISO-currency code Total amount Number of payment orders Filler

1 3 6

21 25

2n 3a 15n 3d 4n 168a

31 spaces

figure > 0

General This type of record totals payment orders with equal currency code of payments (21-5). For each separate currency code as used in the file a totals record must be included. 31-3 Total amount The total amount of payment orders in the currency of the total record (31-2). An imaginary decimal point or decimal comma is located between the third and fourth positions from the right. If the total amount exceeds the 15-digit limit the most left positions are deleted 31-4 Number of payment orders The number of payment orders in the currency of the total record (31-2).

4.4.7. Terminal record layout



Remark/description

41-1 41-2 41-3

Record code Total number of records Total number of payment orders Filler

1 3 9

13

2n 6n 4n 180a

41 spaces

figure > 0

41-2 Total number of records Total number of records in the file including leading record, payments (sub)records, total record(s) and terminal record.

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


20

4.5 Relation checks

NR FIELD 1 FIELD 2

1 IF PAYMENT METHOD CODE is (0) funds transfer

THEN PROCESSING CODE is a required entry, BENEF. BANK NAME is a required entry, BENEF. BANK TOWN is a required entry, CHEQUE FORWARDING CODE cannot be entered, CHEQUE CROSSING CODE cannot be entered and CORRESPONDENT COSTS CODE is a required entry

2 IF BENEFICIARY'S BANK COUNTRY CODE has not been entered and PAYMENT METHOD CODE is (0) funds transfer

THEN BENEFICIARY’S BANK BIC is a required entry BENEF. BANK NAME is a required entry, BENEF.BANK TOWN is a required entry,

3 IF PAYMENT METHOD CODE is (0) funds transfer, BENEFICIARY'S ACCOUNT NUMBER has not been entered and PAYMENT INSTRUCTION CODE is not (07)

THEN BENEFICIARY'S ADDRESS is a required entry

4 IF BENEFICIARY'S BANK COUNTRY CODE is NL and PAYMENT METHOD CODE is (0) funds transfer

THEN BENEFICIARY'S BANK BIC is a required entry NAME OF BENEFICIARY’S BANK is a required entry, TOWN OF BENEFICIARY’S BANK is a required entry,

5 IF BENEFICIARY'S BANK COUNTRY CODE is NL

THEN BENEFICIARY'S ACCOUNT NUMBER is a required entry

6 IF DOMESTIC COSTS CODE is 1 THEN CORRESPONDENT COSTS CODE must be 1 or 3

7 IF DOMESTIC COSTS CODE is 2 THEN CORRESPONDENT COSTS CODE must be 2 or 3

8 IF DOMESTIC COSTS CODE is 3 THEN CORRESPONDENT COSTS CODE must be 3

9 IF PAYMENT METHOD CODE is (1) cheque

THEN CORRESPONDENT COSTS CODE cannot be entered PROCESSING CODE cannot be entered CHEQUE CROSSING CODE is a required entry CHEQUE FORWARDING CODE is a required entry PAYMENT INSTRUCTION CODE 1 TO 4 cannot be entered BENEFICIARY'S ACCOUNT NUMBER cannot be entered BENEFICIARY'S BANK NAME cannot be entered BENEFICIARY'S BANK BIC cannot be entered BENEFICIARY'S BANK TOWN cannot be entered BENEFICIARY'S BANK COUNTRY CODE cannot be entered BENEFICIARY'S BANK COUNTRY cannot be entered

10 IF PAYMENT METHOD CODE is (1) cheque and CHEQUE FORWARDING CODE is (3) beneficiary

THEN BENEFICIARY'S ADDRESS and BENEFICIARY'S COUNTRY are required entries

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


21

4.6 Criteria EU-payment (IBAN/BIC)

With BTL91 is is possible to import an EU-payment (IBAN/BIC) in OfficeNet. An EU-payment (IBAN/BIC) has to comply with the following conditions to be processed against domestic charges:

• The currency of the amount is in euro's;

• The amount of EU-payment is maximum 50.000 euro;

• The charges for processing the payment will be shared between principal and beneficiary;

• The correct and complete accountnumber of the beneficiary in IBAN-format;

• The correct and complete BIC (SWIFT-address) of the bank of the beneficiary;

• The country of the beneficiary bank is one of the EU-countries;

• No supplementary payment instructions

For the BTL91-payments record layout, which does not change, this leads to the corresponding heading description:

Heading Name Startposition Alfa/ numeric

Contents

21-5 ISO CURRENCY CODE OF THE PAYMENT

20 3a EUR

21-6 AMOUNT OF THE PAYMENT 23 15n 3d <=000000050000000 21-8 CODE-COSTS-DOMESTIC BANK 46 1n 1 21-9 CODE-COSTS-CORRESPONDENT 47 1n 3 22-3 BENEFICIARY-ACCOUNTNUMBR 7 34a ‘International Bank

Account Number (IBAN)’

23-3 BENEFICIARY’S BANK BIC 7 11a Complete and correct BIC’

23-7 BENEFICIARY’S BANK COUNTRY CODE 123 2a ‘EU-country code’

4.7 The use of DES-hash in combination with BTL91 files

If payments are created using the Foreign Payments module of OfficeNet Extra, a Des Hash code is added to the file in the filler of the terminal record when the file is prepared for dispatch. A Des Hash code is a number used for verification purposes and is the result of a calculation that includes a number of variables from the file. In order to import BTL91-files without a DES-hash created by other financial packages the option ‘Accept foreign payments without hash’ under ‘Settings/Advanced’ has to be activated in OfficeNet Direct. Only the main user is authorised to activate this option.

___________________________________________________________________ABN AMRO Bank N.V.

__________________________________________________________________________


22

Appendix A: PAYMENT INSTRUCTION CODES

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 /REC/ADVISE BEN. BANK BY ADVISE BEN. BANK BY CABLE/ CABLE/SWIFT CHARGES FOR US SWIFT CHARGES FOR US 06 /REC/ADVISE BEN. BANK BY ADVISE BEN. BANK BY CABLE/

CABLE/SWIFT WITHOUT CHARGES SWIFT WITHOUT CHARGES FOR FOR US US

07 /HOLD/ HOLD DISPOSAL 12 /ACC/IF BEN. IS UNKNOWN OR HAS IF BEN. IS UNKNOWN OR HAS DECEASED PLEASE RETURN DECEASED PLEASE RETURN AMOUNT AMOUNT 13 /REC/THIS PAYMENT IS THIS PAYMENT IS IRREVOCABLE IRREVOCABLE 14 /REC/INTERCOMPANY TRANSFER INTERCOMPANY TRANSFER

officenet direct data import formats - abn amro importing, we mean integrating a file with payments...

Documents