Information About Transfer Orders with Missing Or Incorrect Data

Total Page:16

File Type:pdf, Size:1020Kb

Information About Transfer Orders with Missing Or Incorrect Data INFORMATION about transfer orders incurring “Extra transfer fees for transfer orders with missing or incorrect data” Incorrect SWIFT / BIC Cause of error: - The SWIFT/BIC code is missing, and the name and address of the bank is indicated only in words - The SWIFT/BIC code is indicated but not in the appropriate field but in the rows left for the bank’s name and address, or the rows of the sender’s message to the beneficiary, which are free-format rows and hence cannot be interpreted by the systems automatically. - The SWIFT/BIC code is indicated but incorrectly. How can you avoid this error? - This information has to be indicated on the invoices incoming from partners more and more often, since it is vital information in international money transfers. Thus, it is in the interest of your partners as well to indicate this on the invoices or other documents in which they ask for transfers from their clients. - Should there be no such information on the invoice, please ask from your partners for their bank’s SWIFT/BIC code. Every bank has to specify their SWIFT/BIC code on their bank account statements or announce it to their clients upon request, so your partners have to be able to provide you with this information. - SWIFT/BIC codes may only consist of 8 or 11 characters, and any length other than these are incorrect. - SWIFT/BIC codes may be searched by the name of the bank on the http://www.swift.com/bsl webpage. - Please enter the correct SWIFT code you have been provided with only in the field where the SWIFT/BIC code has to be indicated. Incorrect IBAN – in the “Beneficiary’s bank account number” field an incorrect International Bank Account Number (IBAN) has been entered. Cause of error: - It was not the IBAN that was indicated as the bank account number of the beneficiary when making a transfer to a country using IBAN - IBAN was entered in another field (Bank ID or Bank’s name, address or the rows of the sender’s message to the beneficiary, which are free-format rows and hence cannot be interpreted by the beneficiary’s bank automatically) - The IBAN was indicated, but some unnecessary information or characters were also added (e.g. “IBAN”, “BIZ”, etc. is added before it) - The IBAN was entered but incorrectly (numbers might be left out, added or mistyped) How can you avoid this error? - The IBAN has to be indicated on the invoices incoming from partners, since it is vital information in international money transfers (especially in Europe). Thus, it is in the interest of your partners as well to indicate this on the invoices or other documents in which they ask for transfers from their clients. - Should there be no such information on the invoice, please ask from your partners for the IBAN of their account where they would like the money to be sent. The IBAN numbers are used in every EU country and in several other countries, and every bank has to specify the IBAN on their bank account statements, so your partners have to be able to provide you with this information. - The IBAN format and the number of characters contained are defined by each country, and it also has a 2-digit verification number by which the banks verify them. This information package contains a list about countries using IBAN at present, and the format of such numbers. If you compare there with the information entered in the transaction orders, the differences will be apparent immediately. - We suggest that you check the IBAN format using our IBAN verifier located at our webpage www.unicreditbank.hu . - Please enter the correct IBAN you have been provided with only in the field where the IBAN has to be indicated. Every electronic system we have will tell you immediately if the IBAN entered is correct or not. Incorrect Bank ID Cause of error: - Unnecessary specification of Bank ID in cases when the IBAN would be sufficient. - The Bank ID is entered with the incorrect prefix (e.g. BIZ instead of BL). - The IBAN is incorrectly entered in the Bank ID field instead of the “Beneficiary’s bank account number” field. How can you avoid this error? - Nearly 70-80% of our clients’ transactions are directed at countries where the IBAN is used. Hence, indicating the SWIFT/BIC codes and the Beneficiary’s IBAN is necessary and sufficient to perform orders. If the transfer is directed into a country which uses the IBAN, please always give the SWIFT/BIC code and the IBAN, and leave he Bank ID field empty. - Bank IDs are defined only for certain countries, and their form is strictly defined and should be adhered to according to the table attached here. Please find a summary of the correct IDs and their format in the table below. On the pages that follow we would like to offer more help to you on how to fill out accurately our foreign currency transfer screens of our electronic banking software. Yours sincerely, UniCredit Bank Hungary Zrt. Spectra, Spectra Light In the Spectra and SpectraLight systems the programs fill out the IBAN field automatically if you enter a correct IBAN in the bank account field. (You may use spaces between 4-digit groups) SpectraNet Light and SpectraNet Plusz In the SpectraNet Light and the SpectraNet Plus systems, when an existing and correct IBAN is entered in the bank account field the program will indicate, above the bank account number, if the account number entered is an “IBAN account number” or “Not an IBAN account no.” MultiCash – when using the HUA module: Please leave the Beneficiary account number field empty, and after selecting “IBAN” enter the IBAN number (continuously, without spaces or the IBAN prefix). You may only store and close the Beneficiary info if the IBAN meets the requirements. MultiCash – when using the MT100 module: Please enter the IBAN account number (continuously, without spaces or the IBAN prefix) in the PARTNER account number field, then choose the “IBAN” option. You may only store and close the Partner info if the IBAN meets the requirements. Countries using IBAN and their IBAN formats Country Electronic account no. format No. of (examples) characters Albania AL47212110090000000235698741 28 Andorra AD1200012030200359100100 24 Austria AT611904300234573201 20 Republic of Azerbaijan AZ21NABZ00000000137010001944 28 Bahrein BH67BMAG00001299123456 22 Belgium BE62510007547061 16 Bosnia-Herzegovina BA391290079401028494 20 Brazil BR9700360305000010009795493P1 29 Bulgária BG80BNBG96611020345678 22 Costa Rica CR0515202001026284066 21 Croatia HR1210010051863000160 21 Cyprus CY17002001280000001200527600 28 Czech Republic CZ6508000000192000145399 24 Denmark DK5000400440116243 18 Dominican Republic DO28BAGR00000001212453611324 28 United Arab Emirates AE070331234567890123456 23 Estonia EE382200221020145685 20 Faroe Islands FO6264600001631634 18 Finland FI2112345600000785 18 France FR1420041010050500013M02606 27 Georgia GE29NB0000000101904917 22 Germany DE89370400440532013000 22 Gibraltar GI75NWBK000000007099453 23 Great Britain GB29NWBK60161331926819 22 Greece GR1601101250000000012300695 27 Greenland GL8964710001000206 18 Guatemala GT82TRAJ01020000001210029690 28 Hungary HU42117730161111101800000000 28 Iceland IS140159260076545510730339 26 Ireland IE29AIBK93115212345678 22 Israel IL620108000000099999999 23 Italy IT40S0542811101000000123456 27 Jordan JO94CBJO0010000000000131000302 30 Kazakhstan KZ86125KZT5004100100 20 Kuwait KW81CBKU0000000000001234560101 30 Latvia LV80BANK0000435195001 21 Lebanon LB62099900000001001901229114 28 Lichtenstein LI21088100002324013AA 21 Lithuania LT121000011101001000 20 Luxemburg LU280019400644750000 20 Macedonia MK07300000000042425 19 Malta MT84MALT011000012345MTLCAST001S 31 Mauritania MR1300020001010000123456753 27 Mauritius MU17BOMM0101101030300200000MUR 30 Republic of Moldova MD24AG000225100013104168 24 Monaco MC1112739000700011111000h79 27 Montenegro ME25505000012345678951 22 Electronic account no. format No. of Country (examples) characters The Netherlands NL39RABO0300065264 18 Norway NO9386011117947 15 Pakistan PK36SCBL0000001123456702 24 Palestine, State of. PS92PALS000000000400123456702 29 Poland PL27114020040000300201355387 28 Portugal PT50000201231234567890154 25 Romania RO49AAAA1B31007593840000 24 Qatar QA58DOHB00001234567890ABCDEFG 29 San Marino SM86U0322509800000000270100 27 Saudi Arabia SA0380000000608010167519 24 Serbia RS35260005601001611379 22 Slovakia SK3112000000198742637541 24 Slovenia SI56191000000123438 19 Spain ES0700120345030000067890 24 Sweden SE3550000000054910000003 24 Switzerland CH9300762011623852957 21 Tunisia TN5914207207100707129648 24 Turkey TR330006100519786457841326 26 Virgin Islands, British VG96VPVG0000012345678901 24 Correct Bank IDs and their formats Code Identifier Country using it Does country use IBAN? Example of format AT 5 numbers Austrian Bankleitzahl Yes Need not be used; please give beneficiary’s account number with IBAN instead AU 6 numbers Australian Bank State Branch (BSB) Code No AU123456 BL 8 numbers German Bankleitzahl Yes Need not be used; please give beneficiary’s account number with IBAN instead CC 9 numbers Canadian Payments Association Payment No CC123456789 Routing Number CH 6 numbers CHIPS Universal Identifier n/a CH123456 CP 4 numbers CHIPS Participant Identifier n/a CP1234 ES 8 or 9 numbers Spanish Domestic Interbanking Code Yes Need not be used; please give beneficiary’s account number with IBAN instead FW 9 numbers Fedwire Routing Number (USA) No FW123456789 GR 7 numbers HEBIC (Hellenic Bank Identification Code) Yes Need not be used; please give beneficiary’s account number with IBAN instead HK 3 numbers Bank Code of Hong Kong
Recommended publications
  • Oracle Financial Services Regulatory Reporting 2.1 Web Service Guide
    Oracle Financial Services Compliance Regulatory Reporting Web Service Guide Release 2.5.6 May 2016 Oracle Financial Services Compliance Regulatory Reporting Web Service Guide Release 2.5.6 December 2016 Part Number: E70640-01 Oracle Financial Services Software, Inc. 1900 Oracle Way Reston, VA 20190 Part Number: E70640-01 First Edition (May 2016) Copyright © 2016 Oracle and/or its affiliates. All rights reserved. Printed in U.S.A. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise without the prior written permission. Trademarks Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Oracle Financial Services Software, Inc. 1900 Oracle Way Reston, VA 20190 Phone: 703-478-9000 Fax: 703-318-6340 Internet: www.oracle.com/financialservices Contents Contents About This Guide ............................................................................................................ III Who Should Use this Guide .............................................................................................................................................III Scope of this Guide............................................................................................................................................................III How this Guide is Organized...........................................................................................................................................III
    [Show full text]
  • PAYMENT FORMATS STP Rules
    PAYMENT FORMATS STP Rules © VTB Bank (Europe) SE – Payment Formats – STP Rules Page 1 / 10 List of Contents General Information ............................................................................................................... 3 Requirements of the regulations of the Anti Money Laundering Act ....................................... 3 Transaction quality and price ................................................................................................. 3 Account number format ......................................................................................................... 4 BIC (SWIFT address) ............................................................................................................ 4 Customer payment order MT 103 .......................................................................................... 4 Customer payment order MT 103+ ........................................................................................ 8 Bank-to-Bank payments MT 200/202/202Cov ....................................................................... 8 Appendix I ........................................................................................................................... 10 © VTB Bank (Europe) SE – Payment Formats – STP Rules Page 2 / 10 General Information The costs of international payment transactions can be considerably reduced by the observation of prevailing standard rules. The term „Straight Through Processing“ (STP) refers to the highly automated and standardised processing of payment
    [Show full text]
  • Payment Formatting Guidelines
    PAYMENT FORMATTING GUIDELINES May 2019 Version 2019.1 PAYMENT FORMATTING GUIDELINES Welcome the the First Quarter 2019 Edition of the Payment Formatting Guidelines (PFG). • Address: Beneficiary address requests should be a physical • NOK: ADDITIONAL CONSIDERATIONS: Draft capability is address, PO Boxes are not recommended no longer available. • AED/ANY CURRENCY: Purpose Of Payment Code is • NZD: ADDITIONAL CONSIDERATIONS: NZD Payments to required regardless of currency. Thailand require a Purpose Of Payment. • AUD: High Value Account Number: 6 - 9 digits • PAB: Panamanian balboa (PAB) to Banco General S.A. • CLP: Registro Unico Tributario (RUT) Number: 9-digit Tax Suspended. Customers may send U.S. dollars in place of ID # in ‘SWIFT Branch Details’ field, (Without the word local currency. RUT). A valid RUT less than 9 digits, must be added with • PHP: ADDITIONAL CONSIDERATIONS: Payments to Bank preceding zeros. of the Philippine Island (BOPIPHMM) should now use the • CRC: IBAN should have 22: CRkk BBBC CCCC CCCCCCCC following SWIFT Code: BOPIPHMMTRY CC: Additional Tax ID instructions • RUB/ANY CURRENCY: Purpose Of Payment is highly • DKK: ADDITIONAL CONSIDERATIONS: Draft capability is recommended for all payments to Russia regardless of no longer available. currency. • JMD: Branch Routing Code - 8 • SCR: RECOMMENDED: Beneficiary IBAN: 31 Alpha Numerical Digits digits (3 digit bank code, 5 digit transit code) • SGD: ADDITIONAL CONSIDERATIONS: SGD-ACH • JPY: ADDITIONAL CONSIDERATIONS: JPY cannot be sent to Japan Post Bank (JPPSJPJ1) but USD and EUR are payments are only available for beneficiaries located in Singapore. accepted. • SGD: ADDITIONAL CONSIDERATIONS: Payments to • KES: RECOMMENDED: When making tax payment the remitter needs to include a 17 digit Payment Registration HSBC Singapore should use the following SWIFT Codes: Number (PRN) in filed 70 “RETAIL/PERSONAL” accounts use SWIFT HSBCSGS2.
    [Show full text]
  • Payments Standards - Exceptions and Investigations
    UNIFI (ISO 20022) Message Definition Report Payments Standards - Exceptions and Investigations Approved by UNIFI Payments SEG on 25 July 2006 Edition August 2006 Table Of Contents Overview .................................................................................................................................................................... 1 What does this document contain? ......................................................................................................................... 1 Exceptions and Investigations messages ................................................................................................................ 1 Business rationale for the Exceptions and Investigations messages ...................................................................... 1 How to read ............................................................................................................................................................ 2 How to use the exceptions and investigations messages ........................................................................................ 3 Introduction ............................................................................................................................................................ 3 Concepts ................................................................................................................................................................. 3 Rules ......................................................................................................................................................................
    [Show full text]
  • Mt 200 Mip Vtb Europe Format Specifications
    VTB Bank (Europe) SE Rüsterstraße 7–9 60325 Frankfurt Germany MT 200 MIP VTB EUROPE SE FORMAT SPECIFICATIONS © VTB Bank (Europe) SE – MIP formats – MT200 Page 1 / 7 VTB Bank (Europe) SE Rüsterstraße 7–9 60325 Frankfurt Germany MT 200 Financial Institution Transfer for its Own Account Status Tag Field Name Content/Options M 20 Transaction Reference Number 16x M 32A Value Date, Currency Code, 6!n3!a15d Amount O 53B Sender's Correspondent /D/10 digits your account number O 56a Intermediary A or D M 57a Account With Institution A, B or D O 72 Sender to Receiver Information 6*35x M = Mandatory O = Optional MT 200 Usage Rules The beneficiary of this transfer is always the Sender. MT 200 Field Specifications Field 20: Transaction Reference Number FORMAT 16x DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message. MIP VTB EUROPE VALIDATED RULES This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' © VTB Bank (Europe) SE – MIP formats – MT200 Page 2 / 7 VTB Bank (Europe) SE Rüsterstraße 7–9 60325 Frankfurt Germany Field 32A: Value Date, Currency Code, Amount FORMAT Option A 6!n3!a15d (Date)(Currency)(Amount) DEFINITION This field specifies the value date, currency and amount to be transferred. MIP VTB EUROPE VALIDATED RULES Date must be a valid date expressed as YYMMDD Field 53B: Sender's Correspondent Account DEFINITION This field specifies the ordering institution when other than the Sender of the message. Option B [/1!a][/34x] (Party Identifier) [35x] (Location) Example: 53B:/D/1234567890 Field 56a: Intermediary Option A [/1!a][/34x] (Party Identifier) 4!a2!a2!c[3!c] (Identifier Code) Option C /34x (Party Identifier) Option D [/1!a][/34x] (Party Identifier) 4*35x (Name & Address) DEFINITION This field specifies the financial institution through which the transaction must pass to reach the account with institution.
    [Show full text]
  • Documento Ayuda
    TRANSFERENCIAS AL EXTERIOR Beneficios Realiza transferencias al exterior desde nuestras más de 450 Agencias BCP a nivel nacional o desde la comodidad de tu casa a través de nuestra Banca por Internet. @ Recibe la confirmación de tus transferencias y el SWIFT automáticamente vía correo electrónico. Para ello deberás indicar tu correo electrónico en la solicitud. Seguridad: Las transferencias se trasmiten con claves encriptadas (vía sistema SWIFT). Características El importe mínimo a transferir es de USD 100.00 o su equivalente en otras monedas. Las transferencias al exterior están afectas al cobro del ITF. Tiempo de llegada de una transferencia al banco corresponsal de destino según horario de recepción de solicitud: TIEMPO DE LLEGADA AL BANCO CORRESPONSAL DE DESTINO PARA TRANSFERENCIAS AL EXTERIOR EN DÓLARES AMERICANOS MISMO DÍA SIGUIENTE DÍA ÚTIL (T+1) DOS DÍAS ÚTILES (T+2) RECIBIDA HASTA LAS RECIBIDA ENTRE LAS U.S.A. Y AMÉRICA LATINA 12:00 PM (MEDIO DÍA) 12:01 PM Y 04:00 PM RECIBIDA HASTA LAS RECIBIDA ENTRE LAS EUROPA 12:00 PM (MEDIO DÍA) 12:00 PM Y 04:00 PM RECIBIDA ENTRE LAS ASIA 8:00 AM Y 04:00 PM TIEMPO DE LLEGADA AL BANCO CORRESPONSAL DE DESTINO PARA TRANSFERENCIAS AL EXTERIOR EN OTRAS MONEDAS DISTINTAS AL DÓLAR MISMO DÍA SIGUIENTE DÍA ÚTIL (T+1) DOS DÍAS ÚTILES (T+2) RECIBIDA HASTA LAS U.S.A. Y AMÉRICA LATINA 12:00 PM (MEDIO DÍA) RECIBIDA HASTA LAS EUROPA 12:00 PM (MEDIO DÍA) RECIBIDA HASTA LAS ASIA 12:00 PM (MEDIO DÍA) 1 ANEXO 1: ¿CÓMO IDENTIFICAR LA CUENTA DE ABONO DEL BENEFICIARIO EN UNA TRANSFERENCIA AL EXTERIOR? Las cuentas de abono de los beneficiarios dentro de otros bancos en el exterior se identifican según tipos de códigos y dependiendo de la región donde se ubiquen pueden ser: 1.
    [Show full text]
  • Pain.002.001.03-CH-SIX-1.1.1-CS-ST Customer Payment Status Report
    Credit Suisse Version 1.0 Issue date: January 2020 pain.002.001.03-CH-SIX-1.1.1-CS-ST Customer Payment Status Report Message implementation guidelines Table of contents 1. Message overview 3 2. Message details 6 3. Components 23 4. Legend – description of cardinality 71 5. Disclaimer 72 pain.002.001.03-CH-SIX-1.1.1-CS-ST 2 1. Message overview Index XML Name ISO Name Cardinality Document 1 CstmrPmtStsRpt Customer Payment Status Report V03 1..1 1.1 GrpHdr Group Header 1..1 1.1.1 MsgId Message Identification 1..1 1.1.2 CreDtTm Creation Date Time 1..1 1.1.3 InitgPty Initiating Party 0..1 1.1.3.1 Nm Name 0..1 1.1.3.3 Id Identification 0..1 xs:choice 1..1 1.1.3.3.1 OrgId Organisation Identification 1..1 1.1.3.3.1.1 BICOrBEI BICOr BEI 0..1 1.1.3.3.1.2 Othr Other 0..n 1.1.3.3.1.2.1 Id Identification 1..1 1.1.3.3.1.2.2 SchmeNm Scheme Name 0..1 xs:choice 1..1 1.1.3.3.1.2.2.1 Cd Code 1..1 1.1.3.3.1.2.2.2 Prtry Proprietary 1..1 1.1.3.3.1.2.3 Issr Issuer 0..1 1.2 OrgnlGrpInfAndSts Original Group Information And Status 1..1 1.2.1 OrgnlMsgId Original Message Identification 1..1 1.2.6 GrpSts Group Status 0..1 1.2.7 StsRsnInf Status Reason Information 0..n 1.2.7.1 Orgtr Originator 0..1 1.2.7.1.1 Nm Name 0..1 1.2.7.1.3 Id Identification 0..1 xs:choice 1..1 1.2.7.1.3.1 OrgId Organisation Identification 1..1 1.2.7.1.3.1.1 BICOrBEI BICOr BEI 1..1 1.2.7.2 Rsn Reason 1..1 xs:choice 1..1 1.2.7.2.1 Cd Code 1..1 1.2.7.2.2 Prtry Proprietary 1..1 1.2.7.3 AddtlInf Additional Information 0..n 1.3 OrgnlPmtInfAndSts Original Payment Information And Status 0..n 1.3.1
    [Show full text]
  • Payment Formatting Guidelines
    PAYMENT FORMATTING GUIDELINES 03.2014 Version 2.7 business.westernunion.com Page 1 of 77 business.westernunion.com TABLE OF CONTENTS CURRENCY GUIDELINES ................................................................................. 3 MAXIMIZING THE USE OF THE GUIDELINES .................................................. 3 BBAN / BASIC ACCOUNT NUMBER .................................................................. 3 IBAN / ACCOUNT NUMBER ............................................................................... 3 SWIFT / BIC CODE ............................................................................................. 4 BANK CODE ....................................................................................................... 4 NON-SWIFT BIC ................................................................................................. 5 ADDITIONAL REQUIREMENTS ........................................................................ 5 IBAN & SWIFT CODE COUNTRIES ................................................................... 6 COUNTRY CURRENCIES (BY CURRENCY CODE) CURRENCIES A - E ............................................................................................ 7 EURO IBAN REQUIREMENTS ......................................................................... 21 CURRENCIES F - J .......................................................................................... 29 CURRENCIES K - O ......................................................................................... 35 CURRENCIES P - T .........................................................................................
    [Show full text]
  • Completion Instruction for the Other Currency Payment Form ______
    Completion Instruction for the Other Currency Payment Form _______________________________________________________________________________________________________________________________________ This Form is meant for transfers in foreign currency from own account to other banks in Lithuania or foreign banks. Please complete the Form using a computer or by hand – in capital letters without corrections. Date* Please indicate or the system will automatically assign it when the payment is entered. Document no. A year, month and day of submitting a payment order to the bank. Payment urgency / Remittance* Normal – payment is sent from DNB bank after 2 bank working days (D+2); Urgent – payment is sent from DNB bank on the next working day (D+1); Extra urgent – payment is sent from DNB bank on the same working day (D+0). Payer: Account No.* Your account in IBAN format. Name, surname / Company name* Your name, surname (natural persons) or company name (legal persons). Beneficiary: Account No.* Please indicate the beneficiary’s account in IBAN format – an international standard for identifying bank accounts (International Bank Account Number). To check whether an IBAN is correct click here (just choose the country and enter the IBAN you want to check). If the beneficiary’s account is in non-IBAN format you must together with SWIFT (BIC) code indicate the beneficiary’s bank code. It is recommended to find out the IBAN account number as that allows sending an international payment to the beneficiary in a cheaper and faster way without any additional charges. Name, surname / Company name* Beneficiary’s name, surname (natural persons) or company name (legal persons). Bank’s SWIFT code (BIC)/Code Please always indicate the beneficiary’s bank SWIFT code (BIC) consisting of either 8 or 11 characters.
    [Show full text]
  • IBAN REGISTRY This Registry Provides Detailed Information About All ISO 13616-Compliant National IBAN Formats
    Registration Authority for ISO 13616 The Society for Worldwide Interbank Financial Telecommunication SCRL, SWIFT, has been designated by the ISO Technical Management Board to act as the Registration Authority for ISO 13616. IBAN REGISTRY This registry provides detailed information about all ISO 13616-compliant national IBAN formats. Release 62 – January 2016 1 Table of Contents Table of Contents 1 About IBAN ........................................................................................................................ 14 1.1 General IBAN Information ......................................................................................... 14 1.2 The ISO 13616 IBAN Standard................................................................................. 14 2 ISO 13616-Compliant IBAN Formats ............................................................................... 14 2.1 Albania ...................................................................................................................... 15 2.2 Andorra ..................................................................................................................... 16 2.3 Austria ....................................................................................................................... 17 2.4 Republic of Azerbaijan .............................................................................................. 18 2.5 Bahrain ...................................................................................................................... 19 2.6 Belgium
    [Show full text]
  • RTGS) Payments User Guide Oracle Banking Payments Release 14.0.0.0.0
    High Value (RTGS) Payments User Guide Oracle Banking Payments Release 14.0.0.0.0 Part No. E93631-01 Feb 2018 High Value (RTGS) Payments User Guide Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon (East) Mumbai, Maharashtra 400 063 India Worldwide Inquiries: Phone: +91 22 6718 3000 Fax: +91 22 6718 3001 www.oracle.com/financialservices/ Copyright © 2017 - 2018, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety ofinformation management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
    [Show full text]
  • Payment Formatting Guidelines
    PAYMENT FORMATTING GUIDELINES 09.2018 Version 6.1 PAYMENT FORMATTING GUIDELINES Welcome to the September 2018 edition of the Payment Formatting Guidelines (PFG). In response to newly implemented payment requirements, we will be updating the following: • BRL (Brazilian Real) Removed BRL local provider. TABLE OF CONTENTS CURRENCY GUIDELINES �����������������������������������������������������������������������������������������������������������������������������������������������������3 MAXIMIZING THE USE OF THIS DOCUMENT . .3 BBAN/BASIC BANK ACCOUNT NUMBER . .3 IBAN/INTERNATIONAL BANK ACCOUNT NUMBER . .3 SWIFT/BIC CODE . .4 BANK CODE . .4 NON-SWIFT BIC . .5 BENEFICIARY ADDRESS . .5 ADDITIONAL REQUIREMENTS . .5 IBAN & SWIFT/BIC CODE �����������������������������������������������������������������������������������������������������������������������������������������������������6 COUNTRY CURRENCIES (BY CURRENCY CODE) CURRENCIES A–E . .8 EURO IBAN REQUIREMENTS . .22 CURRENCIES F–J ���������������������������������������������������������������������������������������������������������������������������������������������������������������30 CURRENCIES K–O �������������������������������������������������������������������������������������������������������������������������������������������������������������37 CURRENCIES P–S . .47 CURRENCIES T–Z ���������������������������������������������������������������������������������������������������������������������������������������������������������������54 ADDENDUMS ADDENDUM 1.1 . .61 ADDENDUM
    [Show full text]