Reference Data. IBAN Plus. Questions & Answers. This document contains the most frequently asked questions and answers.



Similar documents
Frequently Asked Questions

Frequently Asked Questions

SWIFTReady for Corporates Cash Management

SWIFT Certified Application - Exceptions and Investigations

SWIFT Certified Specialist - Consultancy for Trade and Supply Chain Finance Track Criteria

Technical Specifications

SWIFT Certified Application Payments

Personal Token Software Installation Guide

SWIFT Certified Application for Corporates - Trade and Supply Chain Finance

365 Phone, Online and Mobile Banking Terms and Conditions - Republic of Ireland Effective from 25 th November 2013

Bank Wizard. Comprehensive payment data validation and verification

Connectivity. Alliance 7.0. Alliance Interfaces. FileAct support in SWIFTNet Release 7.0

Regulation on Bank Account Standard Numbering System

How does migration to IBAN format impact payments integrity? An Experian White Paper

Customer Testing Policy

INTERNATIONAL BANK ACCOUNT NUMBER (IBAN) AND BANK IDENTIFIER CODE (BIC) IN PAYMENTS

Electronic Bank Account Management - EBAM

Implementing SEPA in Belgiu m

Interface Certification for a RMA Interface

Release Letter. SWIFTRef. Reference Data

INTERNATIONAL BANK ACCOUNT NUMBER (IBAN) AND BANK IDENTIFIER CODE (BIC) IN PAYMENTS

Connectivity. SWIFTNet Link 7.0. Functional Overview

SEPA in SAP CRM. Application Innovation, CRM & Service Industries. Customer

CONDITIONS FOR MAKING PAYMENT TRANSACTIONS

Background. IBAN Overview

WHAT S NEW EXPENSE MANAGEMENT SERVICE. US Administrator s Guide IN YOUR. Release 3.1

SWIFTNet Online Operations Manager

Format Validation Tool ING Commercial Banking

x x Accuity IBAN Complete Validation Messages Explanations Message Code IBAN Message Additional Explanation VALID INVALID WARNING

Entering payment order abroad and payment order in a foreign currency in the Czech Republic via electronic banking service ČSOB InternetBanking 24

Switching your personal current account made easy

SEPA Country-Specific Information Austria

BUSINESS JUSTIFICATION

Interface Certification for a Store-andforward InterAct Messaging Interface

SEPA - Frequently Asked Questions

STANDARD 48 FORMAT OF THE IBAN ISSUED IN THE UK (International Bank Account Number) June 2007

SEPA Mandate Guide. Contents. 1.0 The purpose of this document Why mandates are required When a new mandate is required 2

Questions About SEPA

SEPA DATA MODEL. Reason for Issue Approved by the EPC Plenary on 13 December 2006

SafeNet Cisco AnyConnect Client. Configuration Guide

CyberSource Global Payment Service

SEPA Country Guide Italy. Introduction

SEPA Country-Specific Information Hungary

Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers

Online RESTful API documentation. V-Series 5.1

Information paper. Best Practice for Successful Implementation of ISO for Financial Institutions

Offshore CNY Guidelines. for. SWIFT MT and ISO Messages

SEPA in Netherlands. Quick facts. International Bank Account Number (IBAN) IBAN structure. 66 SEPA Country Sheets - Netherlands

FAQ on the International Bank Account Number (IBAN) 2. Question: Can you explain briefly the IBAN for Bahrain?

Format Description. SWIFT MT103 Single Customer Credit Transfer

SEPA Credit Transfer Terms and Conditions

Oracle FLEXCUBE Direct Banking Release Retail Transfer and Payments User Manual. Part No. E

Intra-day payment Frequently asked questions

Format description XML SEPA Credit Transfer. Format Description

FREQUENTLY ASKED QUESTIONS ABOUT SEPA

ICEPAY & SEPA Direct Debit

EBS204 Version 1 Published November EBS204 Version 2 Published July EBS204 Version 3 Published February 2001

ERP SEPA readiness checklist

Building a Better SAP Payment Process Identifying the right tools for payment success

EPC Report on the results of the IBAN+BIC Survey Joint EPC and EUC Task Force on IBAN+BIC 2

HSBC Your Guide to SEPA. Capitalising on the opportunities

INTERNATIONAL PAYMENTS - PERSONAL

Streamline End-to-End Payment Processes on a Central Platform

TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK

GENERAL TERMS AND CONDITIONS FOR EURO-DENOMINATED PAYMENTS WITHIN SEPA

SEPA Reason Codes. Direct Debit Customer to Bank Implementation Guidelines

Service Description. 3SKey. Connectivity

Interface Certification for a FIN Interface

INTERNATIONAL MONEYMOVER. Terms and Conditions

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.3 Final Page 1 of 38

More information on completing payment details

Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL

1.0 Getting Started Guide

Rules for international payments

Alliance Access Integration Automated File Transfer

State Bank of Pakistan. Guidelines: IBAN Implementation in Pakistan

ENTERPRISE PAYMENTS SOLUTIONS

CONDITIONS FOR ELECTRONIC DATA EXCHANGE VIA ČSOB MULTICASH 24 SERVICE

in Fr a nce Introduction

INTERNATIONAL BANK ACCOUNT NUMBER

Integrated Accounting System for Mac OS X

Credit transfer to Customer account with AS "Meridian Trade Bank" EUR, USD free of charge * Other countries currency information in the Bank

XML message for Payment Initiation Implementation Guideline. Version 1.02

Single Euro Payments Area

Single Euro Payments Area (SEPA) with Oracle E-Business Suite for German Banks

SEPA What should you be thinking about?

for CONSUMERS Information on the SINGLE EURO PAYMENTS AREA

and transfers in foreign currency in Denmark Corporate Effective from 17 June 2016

International Payments

NATIONAL BANK OF ROMANIA

INFORMATION AND CONDITIONS CONCERNING THE USE OF PAYMENT SERVICES ACCORDING TO THE PAYMENT SERVICES LAW OF 2009 (L.128(I)/2009)

Alliance Access Integration SOAP Host Adaptor

User Guide bintec R230a / R230aw / R232b/ R232bw ADSL. Copyright April 18, 2006 Funkwerk Enterprise Communications GmbH Version 2.

RULES. MultiCash Electronic Customer Service System

Transcription:

Reference Data IBAN Plus Questions & Answers This document contains the most frequently asked questions and answers. Update date: 16 June 2013

Table of Contents Table of Contents... 2 Questions about the product IBAN Plus... 3 Which files does the IBAN Plus product contain?... 3 Which other products contain the IBAN Plus product?... 3 What is the purpose of the IBANPLUS file?... 3 Which countries are represented in the IBANPLUS file?... 3 Is the IBAN BIC in IBANPLUS file different from the ordinary BIC?... 3 Why are the BIC in BANKDIRECTORYPLUS and the IBAN BIC in IBANPLUS different for one and the same bank code?... 4 Is the IBAN NATIONAL ID in IBANPLUS file different from the ordinary NATIONAL ID (bank code)?... 4 What is the purpose of the IBANSTRUCTURE file?... 5 Which countries are represented in the IBANSTRUCTURE file?... 5 What is the purpose of the EXCLUSIONLIST file?... 5 Which countries are represented in the EXCLUSIONLIST file?... 5 What does the BIC in the EXCLUSIONLIST represent?... 5 How is the EXCLUSIONLIST populated by SWIFT?... 5 Questions about the usage of IBAN Plus... 6 How should I use the IBAN Plus files to validate IBANs and derive the BIC?... 6 Why is the absence of a bank code in IBANPLUS file not sufficient to declare it invalid?... 6 How should I use the EXCLUSIONLIST?... 6 Which SWIFTRef directories should I use to construct IBANs?... 6 Why would financial institutions validate IBANs in payments submitted by corporates?... 7 Questions about the quality of data... 7 How is the data quality of IBAN Plus files achieved?... 7 What is the data quality of IBAN Plus today?... 7 Is SWIFT liable for the data quality?... 8 Questions about IBAN regulations and standards... 8 Where can I find the list of registered IBAN formats?... 8 How can I calculate or validate IBAN s check digits?... 8 What is IBAN Only?... 8 What are SEPA payments and IBAN payments?... 8 Where can I find information on how the IBANs are used in their countries?... 9 The EPC (European Payments Council) is defining requirements for IBAN to BIC translation data bases. How does your IBAN Plus directory relate to this?... 9 We are a financial institution outside of SEPA. Does the EU 260/2012 regulation apply to us?... 9 Which countries use IBANs, which are in SEPA and which ones are EURO countries?... 9 Legal Notices... 10 2

Questions about the product IBAN Plus Which files does the IBAN Plus product contain? The IBAN Plus product contains three files (and for some of them various versions): IBANPLUS IBANSTRUCTURE EXCLUSIONLIST Which other products contain the IBAN Plus product? IBAN Plus is a product containing the three files listed above, however these files are also included in the following products: SEPA Plus Payments Plus Corporate Pack One Corporate Pack Two Corporate Pack Three What is the purpose of the IBANPLUS file? The IBANPLUS file contains data that allow to: Validate the bank code in an IBAN. Derive the BIC from the IBAN. This supports the EU regulation 260/2012. Which countries are represented in the IBANPLUS file? Data related to all IBAN countries (at the present more than 60) are present in the IBANPLUS file. Is the IBAN BIC in IBANPLUS file different from the ordinary BIC? From all BICs financial institutions have often one or multiple specific BICs have been selected to use in SEPA/IBAN payments. Only these specific BICs are listed in the IBANPLUS file. Special rules might apply per financial institution, for example co-operatives often use BICs with the branch codes to identify their legal entities, while large financial institutions often only use their main BIC without a branch code. Example 1: Societe Generale, France, owns the BICs SOGEFRPPADI, SOGEFRPPAED, SOGEFRPPAFI, SOGEFRPPAFS etc. However, only SOGEFRPP is to be used with IBANs. 3

Example 2: Credit Agricole, France, owns the BICs AGRIFRPP802, AGRIFRPP810, AGRIFRPP812, AGRIFRPP813 etc. They all are to be used with the IBANs in correspondence to their bank codes within the IBANs. Why are the BIC in BANKDIRECTORYPLUS and the IBAN BIC in IBANPLUS different for one and the same bank code? The answer is much related to the previous question. For SEPA IBAN payments: The IBAN Plus is used to derive the BIC for both national and international SEPA payments. The BIC in BDP can be different from the one in IBAN Plus because it is the identifier of the bank/branch equivalent to the bank code (NATIONAL ID). It is not the BIC to be used in SEPA payments. Example: the German BLZ 70010080 represents a bank/branch that has its own BIC11 code PBNKDEFF700 (Deutsche Postbank AG, Muenchen branch). This one-on-one link between the NATIONAL ID (BLZ) and the BIC is represented it the BANKDIRECTORYPLUS. However for IBAN/SEPA payments for this branch the IBAN BIC PBNKDEFFXXX (i.e. PBNKDEFF) is to be used. This is represented in IBANPLUS. For non-sepa (IBAN or non-iban) payments: The IBAN Only regulation EU260/2012 does not apply to non-sepa payments, such as interbank transfers, FX/MM transactions etc. So for these the BIC must be provided by the payer and does not need to be derived from the IBAN. If needed, these BICs can be found or validated against the BANKDIRECTORYPLUS. Is the IBAN NATIONAL ID in IBANPLUS file different from the ordinary NATIONAL ID (bank code)? In many cases the existing NATIONAL IDs are used in IBANs unchanged. However, some NATIONAL IDs might not be used in IBANs, while some others change (structure or value) when they are embedded in IBANs. These special cases and exceptions exist per bank and are configured in the IBANPLUS file. Example 1: The Swedish BBAN 4042 1303405 will be converted into the IBAN SE27 3000 0000 0404 2130 3405. The underlined numbers are the bank identifiers within the BBAN and the IBAN. They are different. Example 2: The German BBAN: 5085 0049 (BLZ) and 5000002096 (account) will become the IBAN DE95 5005 0000 5000 0020 96. The bank code changes. 4

What is the purpose of the IBANSTRUCTURE file? The IBANSTRUCTURE file contains data that allow de-constructing an IBAN into its parts in line with the ISO standard 13616. The de-construction is required prior to validating an IBAN and looking-up the BIC. The IBAN s country pre-fix and the length can be validated against the IBANSTRUCTURE file. Which countries are represented in the IBANSTRUCTURE file? All countries that have registered an ISO 13616 IBAN format with ISO (at the present more than 60) are represented in the IBANSTRUCTURE file. Note that SWIFT is the ISO 13616 registration authority. What is the purpose of the EXCLUSIONLIST file? The EXCLUSIONLIST file contains bank codes that are not allowed in IBANs. Any IBAN that contains a bank code listed in the EXCLUSIONLIST is an invalid IBAN. This is a useful validation as corporates are constructing many invalid IBANs using legacy bank codes configured in their ERP systems. Which countries are represented in the EXCLUSIONLIST file? Bank codes of any IBAN country can be present in the EXCLUSIONLIST file. What does the BIC in the EXCLUSIONLIST represent? The BIC code in the EXCLUSIONLIST is only occasionally provided. It identifies the financial institution that owns/used to own the (invalid) bank code. The BIC itself is NOT an invalid BIC or a BIC that should not be used with IBANs. How is the EXCLUSIONLIST populated by SWIFT? SWIFT populates the EXCLUSIONLIST with: Bank codes declared obsolete or invalid by central authorities or financial institutions that own(ed) them. Bank codes that are not allowed to hold payment accounts. Bank codes of banks that have lost their banking license. Fictious bank codes embedded by corporates in self-made IBANs. 5

Questions about the usage of IBAN Plus How should I use the IBAN Plus files to validate IBANs and derive the BIC? The various steps to perform are described in the IBAN Plus Technical Specification, Appendix G. The document can be downloaded from www.swift.com/swiftref > Documentation > Technical Specifications. The steps include: Validate the Country Code Validate the IBAN length Validate the IBAN check digits Validate the Bank Code Derive the BIC Why is the absence of a bank code in IBANPLUS file not sufficient to declare it invalid? In some cases the central authorities and the financial institutions that are providing the bank codes to SWIFT do not provide a complete list. Therefore absence in IBANPLUS file does not necessarily mean the bank code is invalid. Its presence in the EXCLUSIONLIST however does. How should I use the EXCLUSIONLIST? If you need to validate the Bank Code in an IBAN or to derive the BIC from an IBAN and you do not find the Bank Code (IBAN NATIONAL ID) in the IBANPLUS file then check whether it is listed in the EXCLUSIONLIST. If it is then the Bank Code must not be used in an IBAN and the IBAN is invalid. Which SWIFTRef directories should I use to construct IBANs? Constructing IBANs from BBANs is an error-prone activity as many exceptions and irregularities exist in the process and should be only done if no other alternatives exist. Note that SWIFT provides and IBAN construction service (for more information please ask swiftref@swift.com). In order to construct IBANs as best as possible use the following files: If you are a financial institution, use BANKDIRECTORYPLUS file (in the Bank Directory Plus product) to look-up the BBAN s bank code, and use the IBANPLUS file to find the corresponding IBAN bank code (which can be different) and the associated BIC. The BANKDIRECTORYPLUS is linked via record keys to the IBANPLUS file. If you are a corporate use the BANKDIRECTORYSAP to find the BBAN bank code, related IBAN bank code and the associated BIC, all listed on one and the same line in the file. 6

Then use the IBANSTRUCTURE file to prepare the various components of the IBAN, before calculating the check digit and concatenating the components into the IBAN. Why would financial institutions validate IBANs in payments submitted by corporates? There are tens of thousands corporates out there that are constructing their clients and suppliers IBANs themselves. In most cases they are not being aware of the special rules and exceptions to be applied during IBAN construction. This leads to many invalid IBANs used in payments. Financial institutions that want to reach a high SEPA payments STP should validate the IBANs using the IBAN Plus files. Questions about the quality of data How is the data quality of IBAN Plus files achieved? SWIFT applies the following processes to ensure the highest possible data quality: Per country, the central authorities (central banks and banking associations) provide the list of bank codes and sometimes the BIC codes. This data is then reviewed, completed or corrected by the owning financial institutions via online tools. SWIFT also includes the published exceptions, such as the German IBAN Regeln, if they affect the bank codes and BICs. If IBAN Plus users find omissions or mistakes they report them to the SWIFT data team. The team investigates with the owners and corrects if needed. In the near future SWIFT will also extract the IBAN/BIC combinations from valid SEPA payment messages on the SWIFT network and will use the data to further challenge the IBAN Plus data base, and where needed to correct it after data owner s approval. What is the data quality of IBAN Plus today? The IBAN Plus data quality consists of two components: The completeness of the bank codes (IBAN NATIONAL IDs) if a bank code is missing the BIC cannot be derived. The accuracy of the BIC codes (IBAN BICs) if the BIC is incorrect the payment might be mis-routed or returned. The bank code completeness has been measured against live SEPA payments provided by financial institutions to SWIFT and currently is assumed to be 99.4% and higher. The uncertainty in the measurement is due to the lack of a 100% correct reference. Most missing bank codes reported by users appear to be invalid bank codes after investigation and are added to the EXCLUSIONLIST file. The comparison of IBAN Plus data against IBAN/BIC extracted from SWIFT payments should lead to near 100% completeness early 2014. 7

The BIC accuracy is also measured against valid live SEPA payments and is between 99.1% and higher. Again, the uncertainty is due to the lack of a correct reference and near 100% accuracy is expected early 2014 with the data comparison against IBAN/BIC data extracted from SEPA payments on SWIFT network. Note that the BIC in this context is the BIC that a financial institution has chosen to be used with SEPA payments. Is SWIFT liable for the data quality? The data is provided and validated by central authorities and by financial institutions that own the data. If they make a mistake SWIFT might not be able to detect it. Therefore SWIFT does not take liability for the accuracy of data. SWIFT is though liable for not applying its data management processes correctly. Please refer to the SWIFTRef license agreement http://www.swift.com/about_swift/legal/swiftref_services_licence_agreement. Questions about IBAN regulations and standards Where can I find the list of registered IBAN formats? The IBAN formats are published in the IBAN Registry document which can be downloaded from SWIFT s web site: http://www.swift.com/products_services/by_type/reference_data/iban_registry_iso13616. How can I calculate or validate IBAN s check digits? The algorithm MOD-97-10 for calculating the check digits in an IBAN (position 3 and 4 of the IBAN) is defined in the ISO 7064 standard. What is IBAN Only? IBAN Only is an alternative name for the situation in which a paying financial institution (a Payment Service Provider, PSP) will only receive the IBAN in a payment (from a Payment Service User, PSU) and will have to derive the BIC in line with the EU regulation 260/2012. What are SEPA payments and IBAN payments? SEPA payments are credit transfers and direct debits sent between payment service users (PSUs) within the SEPA area. These payments are using IBANs, and for the time being also BICs. IBAN payments include all SEPA payments and non-sepa payments, such as correspondent banking transfers, inter-bank transfers, FX and MM transactions etc, as long as these use IBANs. IBAN payments are also used outside of the SEPA area as many non-sepa countries have adopted the IBAN standard. 8

Where can I find information on how the IBANs are used in their countries? SWIFT is currently building a data base that contains the dates and conditions for IBAN usage in the IBAN countries. This data base is not yet ready for publication. The EPC (European Payments Council) is defining requirements for IBAN to BIC translation data bases. How does your IBAN Plus directory relate to this? The EPC IBAN Only WB is facilitating the definition of requirements for data bases supporting IBAN to BIC translation. These requirements are under construction with target data February 2016. Because many financial institutions are already in the process of implementing IBAN Only, SWIFT s IBAN Plus is a solution available today. If needed, IBAN Plus will be extended in the future to be compliant with the final rules. We are a financial institution outside of SEPA. Does the EU 260/2012 regulation apply to us? If you are a financial institution operating from outside of SEPA and you have a foreign branch or subsidiary in SEPA, this branch will have to comply with SEPA. All payments coming in via this branch will have to comply. If you have no presence in SEPA then strictly speaking the EU cannot mandate you to comply. However, you will be sending payments towards SEPA countries. This means that your clients will provide you with payment instructions containing IBANs only and you will have to figure out to which BIC to send the payment anyway. Therefore you will have an almost identical problem to resolve and IBAN Plus will be the best solution. Which countries use IBANs, which are in SEPA and which ones are EURO countries? A list of IBAN countries: http://www.swift.com/products_services/by_type/reference_data/iban_registry_iso13616. A list of SEPA countries: http://www.europeanpaymentscouncil.eu/knowledge_bank_detail.cfm?documents_id=328 A list of EURO countries: http://www.ecb.int/euro/intro/html/map.en.html. 9

Legal Notices Copyright SWIFT 2013. All rights reserved. You may copy this publication within your organisation. Any such copy must include these legal notices. Confidentiality This publication contains SWIFT or third-party confidential information. Do not disclose this publication outside your organisation without the prior written consent of SWIFT. Disclaimer The information in this publication may change from time to time. You must always refer to the latest available version on www.swift.com. Translations The English version of SWIFT documentation is the only official and binding version. Trademarks SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT: SWIFT, the SWIFT logo, the Standards Forum logo, 3SKey, Innotribe, Sibos, SWIFTNet, SWIFTReady, and Accord. Other product, service, or company names in this publication are trade names, trademarks, or registered trademarks of their respective owners. 10