Differences BTL91and Generic Payment File. RCM, RIB Pro, RDC and SWIFT FileAct

Transcription

1 Differences BTL91and Generic Payment File RCM, RIB Pro, RDC and SWIFT FileAct

2 Contents 1 GENERAL INFORMATION 3 2 INTRODUCTION 3 3 GENERAL DIFFERENCES 4 4 DESCRIPTION OF THE DIFFERENCES 6 APPENDIX: CHANGE LOG 16 Rabobank Description differences BTL91 (RCM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) Janary 2018 Versie 1.0 2

3 1 General information The purpose of this document is to provide information about the differences between the BTL91-format and Generic Payment File (pain ) for Rabo Internetbankieren Professional (RIB Pro), Rabo Direct Connect (RDC) and SWIFT FileAct. The format description is available on: Introduction The BTL91 format was introduced in 1991 mainly for foreign payments and has been kept unchanged ever since. In the past years a lot has happened in the payments area, for example: The implementation of the Single European Payment Area (SEPA) Introduction of Euro currency Stopped supporting cheque payments Introduction of IBAN For processing payments in the SEPA area it is mandatory to use Sepa Credit Transfers according to the ISO20022 Payment Initation standard pain This standard is also applicable for World payments (payments outside the SEPA area), Urgent Euro payments, Urgent Domestic Europayments, Multibank*- and Rabo Networkbanking-payments**. Due to this new development the old BTL91 standard needs to be replaced. From 1 st of May 2019 Rabobank will stop accepting payments provided in the BTL91 format. * Multibank is expected to be available in Q ** Rabo Networkbanking payments are not yet supported Rabobank Description differences BTL91 (RCM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) Janary 2018 Versie 1.0 3

4 3 General differences Feature BTL91 Generic Payment File via RIB Pro and RDC Multiple batches in one file N/A Yes Support PAIN.002 statusfeedback No Yes Used standard Old standard, non-xml XML ISO20022, CGI compliant Multiple debtor accounts with different currencies in one file Allowed Only one currency of the debet account per batch File check Total amount per currency Total amount of transactions per currency Total amount of records in file Total amount of transactions Hash value Total amount of transactions per batch Total amount per batch BBAN/IBAN BBAN (debtor) BBAN/IBAN (beneficiary) IBAN/BBAN (debtor and beneficiary) Character encoding ASCII UTF-8 Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version 1.0 4

5 Feature BTL91 Generic Payment File via RIB Pro and RDC Supported type of payments World payments Urgent Euro payments. SEPA Credit Transfers are not allowed. World payments SEPA Credit Transfers Urgent Domestic Europayments Urgent Europayments Multibank- and Rabo Networkbanking-payments Each supported type of payments needs to be placed in a seperate batch Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version 1.0 5

6 4 Description of the differences In this chapter an example of the BTL91 is shown in which, several fields are marked in a color. These marked fields are important in order to generate a World payments. For these fields a comparison had been made between the BTL91 and the fields of the Generic Payment File. Note: The Dutch Payments Association has published a complete conversion table between BTL91 fields and XML fields. The conversiontable is available at: Rabobank Description differences BTL91 (RCM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) Janary 2018 Versie 1.0 6

7 Example file BTL91 with one SEPA Credit Transfer and one World payment 11RABOX RABOBANK NEDERLAND POSTBUS HG UTRECHT NEDERLAND EUR EUR NL44RABO TESTREK POSTBUS UTRECHT NLNEDERLAND RABONL2U RABOBANK POSTBUS Amsterdam NLNEDERLAND Batch containing one Sepa Credit Transfer (SCT) EUR USD WORLDBASE PAYMENT WITH SWIFT ADDRESS SANTA MONICA CA USVERENIGDE STATEN CHASUS33XXXJPMORGAN CHASE BANK 4 NEW YORK PLAZA, FLOOR 15 NEW YORK NY USVERENIGDE STATEN Batch containing one Urgent Europayment (UWP) 31EUR USD Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version 1.0 7

8 Example file Generic Payment File (RIB Pro, RDC and SWIFT FileAct) with one World payment and one SEPA Credit Transfer <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" <CstmrCdtTrfInitn> <GrpHdr> <MsgId>Voorbeeld-GPF-01</MsgId> <CreDtTm> T11:30:00</CreDtTm> <NbOfTxs>2</NbOfTxs> <CtrlSum>5.50</CtrlSum> <InitgPty> <Nm>Rabobank</Nm> </InitgPty> </GrpHdr> <PmtInf> <PmtInfId>EXAMPLE-BATCH-SCT-01</PmtInfId> <PmtMtd>TRF</PmtMtd> <NbOfTxs>1</NbOfTxs> <CtrlSum>2.00</CtrlSum> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>Initiating Party Name</Nm> <PstlAdr> <Ctry>NL</Ctry> <AdrLine>Dbtr Streetname Housenumber 123</AdrLine> <AdrLine>Dbtr Postal Code and City</AdrLine> </PstlAdr> </Dbtr> <DbtrAcct> <Id> <IBAN>NL10RABO </IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>RABONL2U</BIC> </FinInstnId> Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version 1.0 8

9 </DbtrAgt> <ChrgBr>SLEV</ChrgBr> <CdtTrfTxInf> <PmtId> <InstrId>InstrId-SCT-01</InstrId> <EndToEndId>End2EndId-SCT-01</EndToEndId> </PmtId> <PmtTpInf> <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> </PmtTpInf> <Amt> <InstdAmt Ccy="EUR">2.00</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>RABONL2U</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>TESTREK</Nm> <PstlAdr> <Ctry>NL</Ctry> <AdrLine>Cdtr Streetname Housenumber 123</AdrLine> <AdrLine>POSTBUS UTRECHT</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>NL44RABO </IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd>Batch containing one Sepa Credit Transfer (SCT)</Ustrd> </RmtInf> </CdtTrfTxInf> Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version 1.0 9

10 </PmtInf> <PmtInf> <PmtInfId>EXAMPLE-BATCH-WP-01</PmtInfId> <PmtMtd>TRF</PmtMtd> <NbOfTxs>1</NbOfTxs> <CtrlSum>3.50</CtrlSum> <PmtTpInf> <SvcLvl> <Cd>URGP</Cd> </SvcLvl> </PmtTpInf> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>Initiating Account</Nm> </Dbtr> <DbtrAcct> <Id> <IBAN>NL10RABO </IBAN> </Id> <Ccy>EUR</Ccy> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>RABONL2U</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>SHAR</ChrgBr> <CdtTrfTxInf> <PmtId> <InstrId>InstrId-WP-01</InstrId> <EndToEndId>End2EndId-WP-01</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="USD">3.50</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version

11 <BIC>CHASUS33XXX</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>WORLDBASE</Nm> <PstlAdr> <PstCd>90406</PstCd> <TwnNm>SANTA MONICA</TwnNm> <Ctry>US</Ctry> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <Othr> <Id> </Id> </Othr> </Id> </CdtrAcct> <RmtInf> <Ustrd>Batch containing one Urgent Europayment (UWP)</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version

12 Field from example BTL91 Field Generic Payment File (RIB Pro, RDC, SWIFT FileAct) Note Currency of the EUR <Ccy>EUR</Ccy> No difference. debtor account Field 21-03: ISO currency code of Initiator s account Tag 2.20 <DbtrAcct><Ccy> Code included in ISO currency code table. Code included in ISO currency code table. Debtor s account Field 21-04: Initiator s account Max. length of this field is 10 numeric. <IBAN>NL10RABO </IBAN> Tag 2.20 <DbtrAcct><Id><IBAN> Letters used in IBAN must be in capitals. Usage of spaces is not allowed. Difference. For debtor s account the Generic Payment File only supports IBAN. Note: for Multibank payments BBAN may only be if there is no IBAN. Amount and USD <InstdAmt Ccy="USD">3.50</InstdAmt> There are differences. currency of the The amount of the Generic Payment payment order Field 21-05: ISO currency code of the payment order Tag 2.43 <InstdAmt> File has: Code included in ISO currency code table The currency of the amount must be provided within the tag: 1) Different notation. <InstdAmt Ccy= XXX > where XXX must be a valid ISO currency 2) The amount provided must be a Field 21-06: Payment order amount code (f.e. EUR, USD, GBP, JPY, etc.). value between 0.01 and Only numerical characters are allowed. An imaginary 999,999, decimal point (non-continental European and Amount of the payment. Decimals are separated with a point.. The 3) Decimals are separated with a American) or decimal comma (continental European) amount provided must be a value between 0.01 and 999,999, point. is located between the third and fourth position from 4) Variable length in the Generic the right. Payment File. Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version

13 Field from example BTL91 Field Generic Payment File (RIB Pro, RDC, SWIFT FileAct) Note Requested <ReqdExctnDt> </ReqdExctnDt> There is a difference. processing date The date in the Generic Payment File Field 21-7 Requested processing date Tag 2.17 <ReqdExctnDt> includes -. Notation CCYYMMDD Notation CCYY-MM-DD Charges 4 Field 21-9: Correspondent costs code 1 = costs chargeable to initiator (OUR) 3 = domestic costs chargeable to initiator and foreign costs chargeable to beneficiary. (SHA); 4 = costs chargeable to beneficiary (BEN) <ChrgBr>SHAR</ChrgBr> Tag 2.24/2.51 <ChrgBr> For SEPA Credit Transfers only the value SLEV is allowed. For Urgent Domestic Europayments only SHAR is allowed. For World payments, Multibank payments and Urgent Europayments the following values are allowed: CRED - all costs for the beneficiary (BEN) DEBT - all costs for the initiating party (OUR) SHAR - costs are shared between the initiating party and the beneficiary (SHA). For World payments the definition of the codes are the same OUR, SHA and BEN but the codes are different. Value 1, 2 and 3 towards CRED, DEBT and SHAR. Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version

14 Field from example BTL91 Field Generic Payment File (RIB Pro, RDC, SWIFT FileAct) Note Way of 0 <Cd>URGP</Cd> There is a difference in the used processing codes. Field 21-11: Processing code Tag 2.8/2.9 <SvcLvl><Cd> Options are extended towards the 0 = Normal The Rabobank only accepts one of the following values: NURG, BTL91. 2 = Urgent URGP, SDVA, SEPA. - SEPA or Empty for SEPA Credit Transfers - URGP for Urgent Domestic Europayments - SDVA, NURG and URGP for World payments, Urgent Domestic Europayments and Multibank payments. Total amount Field 31-03: Total amount Total amount of payment orders in the currency stated in record 31-2 ISO Currency Code of total records. An imaginary decimal point (noncontinental European and American) or decimal comma (continental Europe-an) is located between the third and fourth position from the right. Total number of 0001 transactions Field 31-04: Number of payment orders Number of payment orders for each currency. <CtrlSum>3.50</CtrlSum> Tag 2.5 <CtrlSum> Total sum of all the individual payments in the batch Decimals are separated by a point.. <NbOfTxs>1</NbOfTxs> Tag 2.4 <NbOfTxs> Total number of transactions in a batch. There are differences: 1) The notation of the amount in the Generic Payment File must have a value between 0.01 and 999,999, ) The CtrlSum is the total amount of all individual payments per batch, regardless of the currency. 3) Variable length in the Generic Payment File. There is a difference. BTL91 shows total number of transactions divided for each currency separately. The Generic Payment File Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version

15 Field from example BTL91 Field Generic Payment File (RIB Pro, RDC, SWIFT FileAct) Note shows total number of transactions for each batch and not for each currency of the transaction. Description lines Batch containing one Urgent Europayment (UWP) <Ustrd>Batch containing one Urgent Europayment (UWP)</Ustrd> There is a difference. For World payments only 98 positions will be Fields 24-3/6 (1, 2, 3 and 4): Reason of payment Tag 2.99 <Ustrd> processed and passed through Field in which a payment reference can be provided. For SEPA Credit Transfers all 140 positions will be processed and instead of 140 poistions. The reference is dispatched to the beneficiary passed through. simultaneously with the payment order. For Urgent Domestic Europayments only the first 96 positions will processed and passed through. For World payments, Multibank payments and Urgent Europayments only the first 98 positions will be processed and passed through. Please note!: For all payment types there is a maximum of one (1) Unstructured remittance line. Rabobank Description differences between BTL91 (RM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) January 2018 Version

16 Appendix: Change Log Title: Description differences between BTL91 (RCM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) Version: 1.0 Date: On behalf of: Transactiebankieren & Cash Management Operations Contact: Date Version Type Change Reason change Initial document - Rabobank Description differences BTL91 (RCM/RDC) and Generic Payment File (RIB/RDC/SWIFT FileAct) Janary 2018 Versie