Format Description SWIFT FIN MT101 Rabobank
COLOPHON Title Format Description SWIFT FIN MT101 Version, date 1.25, September 2015 On behalf of Contact address Corporate Client Channels Rabobank Nederland, Croeselaan 18, Postbus 2626 3500 HG Utrecht. @ Rabobank, 2015 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.
Content SWIFT FIN MT101: Request for transfer 3 1 Introduction 3 2 General information 3 3 Specific field descriptions within format structure 4 Appendix 1: Change log 7 2
SWIFT FIN MT101: Request for transfer 1 Introduction This document indicates the Rabobank specific requirements for fields within the MT101 standard format structure. If the field is not mentioned in the underlying document, the standard SWIFT description is leading, as indicated in the user handbook on www.swift.com. 2 General information The MT101 is a Request For Transfer and is sent by the corporate to the financial institution. It is used to move funds from the ordering customer s account, serviced at the receiving financial institution. The MT101 can be used to initiate: Euro Payments, payments in Euro within the E.E.A. Foreign payments, payments in a foreign currency and/or outside the E.E.A. A MT101 can contain one or more payment transactions (with a maximum of 60 transactions per MT101). Rabobank accepts both single and multiple MT101-messages, as long as only one debit account is present in sequence A of the MT101.. 3
3 Specific field descriptions within format structure The MT101 message can be send to Rabobank, and should be formatted as indicated in the user handbook on www.swift.com. However, all MT101 messages must also comply with the Rabobank specific rules, as indicated below. Sequence A (Common File Elements) Field Format, Content, Options []=optional!=fixed length a=text x=alphanumeric d=numeric with decimal separator n=numeric Mandatory / Optional Field name Comments/Rabobank Specific 20 16x M Sender s Reference Must be unique per message, duplicates are rejected. 21R 16x O Customer Specified This reference is ignored. Reference 28D 5n/5n M Message index/total Must contain (nnnn) 1/ (nnnn) 1. Chained messages are not processed and are rejected. 50a C or L O Instructing party Option C is rejected, option L is ignored. 50a F, G or H O Ordering Customer Options F and G are rejected. Option H: accountnumber (IBAN) /name is mandatory and must be FATF VII compliant. 52a A en C O Account Servicing institution 51A [/1!a][/34x] 4!a2!a2!c[3!c] O Sending Institution If used, must contain a valid BIC. 30 6!n M Requested Execution Date This date may be future dated at a maximum of 30 calendar days ahead from the message date. Please note: Future dated requests for transfer cannot be cancelled! Messages with a requested execution date more than 5 days in the past are rejected. 25 35x O Authorization This field is ignored. 4
Field Sequence B (Transaction details) Format, Content, Options []=optional!=fixed length a=text x=alphanumeric d=numeric with decimal separator n=numeric Mandatory / Optional Field name Comments/Rabobank Specific 21 16x M Transaction reference Must be unique within the message. 21F 16x O F/X Deal reference This reference is ignored. 23E 4!c[/30x] O Instruction code The following codes are supported: PHON, URGP, RTGS (payment order is handled as urgent payment) INTC (requires a bilateral agreement. Without an agreement, this code results in rejection). OTHR/DMST and OTHR/INTL are processed. CHQB, CMSW, CMTO, CMZB and REPA are ignored. All other code words result in a rejection of the request 1. 32B 3!a15d M Currency/Transaction amount Max amount: 999.999.999,99 Restriction: for accounts held at Local Member Banks of Rabobank, currency conversion is allowed for transactions up to EUR 500.000 or its foreign currency equivalent. Currency conversion is not allowed for transactions with a value over EUR 500.000 or its foreign currency equivalent (Currency of ordering customer account must be equal to the currency of the transaction). 50a C or L O Instructing party Option C is rejected, option L is ignored. 50a F, G or H O Ordering Customer Option F and G will be rejected. Option H: account number (IBAN)/name is mandatory and must be FATF VII compliant. 52a A or C O Account Servicing Field 52a option A and C are ignored. institution 56a A, C or D O Intermediary Field 56a option A, C and D are ignored. 57a A, C or D M Account with institution Only option A is supported. Must be present for both Euro and foreign payments. 1 If field 23E is empty, the payment order will be considered non urgent SCT or non urgent crossborder, depending on currency, beneficiary and beneficiary bank details (57a). 5
Field Format, Content, Options []=optional!=fixed length a=text x=alphanumeric d=numeric with decimal separator n=numeric Mandatory / Optional Field name Comments/Rabobank Specific 59a No letter option or A M Beneficiary Option A is rejected. Beneficiary s account number is mandatory for both domestic and cross border payments. IBAN is mandatory for payments in EUR to accounts within EU/EEA (incl NL). It s mandatory to provide at least 3 lines filled with name and address. At the end of the last line (3 or 4) filled, the country ISO code must be provided, preceded with a single space. 70 4*35x O Remittance information 77B 3*35x O Regulatory reporting Is ignored. 33B 3!a15d O Currency/original Is ignored. ordered amount 71A 3!a M Details of charges Is ignored for Euro Payments. Rabobank only accepts SHA for any cross border payment in a PSD currency to a PSD country. Non-compliant orders are rejected. 25A /34x O Charges account Is ignored. 36 12d O Exchange rate Is ignored. 6
Appendix 1: Change log Title: Format Description SWIFT FIN MT101 Version: 1.25 Date: 01-09-2015 By: Corporate Client Channels Address: Rabobank Nederland, Zakelijke Klantkanalen Leidseveer 35, 3511 SB Utrecht P.O. box 17100 3500 HG Utrecht Date Version Change Change reason 31-03-2015 1.23 Field 59a, it is mandatory to provide the ISO Country Code. Clarification 31-3-2015 1.23 Field 57 changed into manditory Correction 31-3-2015 1.23 Field 32B changed into manditory. Correction 01-06-2015 1.24 Change log added to this document Improvement 01-06-2015 1.24 Layout changes Improvement 01-06-2015 1.24 Field 32B, max. amount. There is no difference anymore between RI and local bank accounts. Improvement 01-09-2015 1.25 Clarification 01-09-2015 1.25 Clarification 7