Reference Data
Bank Directory for SAPTM TXT file – Version 1
Technical Specifications
This document describes the technical matters of the TXT files included in the Bank Directory for SAPTM
TM
product. The files are suited for upload into SAP systems and other ERP systems in order to build a
complete bank master data table. The files are in particular useful in making the client and vendor
account data compliant with the SEPA direct debit and credit transfer regulation.
Update date: 30 January 2013
Note that corrections relative to previous update date are marked in red font.
Bank Directory for SAP – Technical Specifications
Table of Contents
Table of Contents ...............................................................................................................................2
Preface .................................................................................................................................................3
1
General product information ...................................................................................................4
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
2
BANKDIRECTORYSAP file ......................................................................................................7
2.1
3
Field definitions .......................................................................................................................9
CURRENCY CODE File...........................................................................................................10
4.1
5
Field definitions .......................................................................................................................7
COUNTRY CODE File ...............................................................................................................9
3.1
4
TM
Bank Directory for SAP ........................................................................................................4
File format ...............................................................................................................................4
File names ...............................................................................................................................4
Previous file versions ..............................................................................................................4
Downloading the files ..............................................................................................................5
Uploading the files ...................................................................................................................5
Future file changes ..................................................................................................................5
Release notes .........................................................................................................................5
Support ....................................................................................................................................5
Terminology ............................................................................................................................5
Field definitions .....................................................................................................................10
IBAN STRUCTURE File ..........................................................................................................11
5.1
Field definitions .....................................................................................................................11
Appendix A - Character Set .............................................................................................................13
Appendix B – Fields and Flags .......................................................................................................14
B.1
B.2
B.3
Modification Flag ...................................................................................................................14
Record keys ..........................................................................................................................14
Date fields .............................................................................................................................14
Appendix C – Office Type ................................................................................................................15
Appendix D – List of countries .......................................................................................................16
D.1
D.2
D.3
List of countries with BIC codes ............................................................................................16
List of countries with National IDs (Bank Numbers) .............................................................16
Country specific notes ...........................................................................................................19
Appendix E – File upload guidelines .............................................................................................20
E.1
E.2
E.3
E.4
E.5
File content ............................................................................................................................20
Upload options ......................................................................................................................20
Choosing the Bank Keys .......................................................................................................21
Cleaning-up the Bank Keys ..................................................................................................22
BICPlusIBAN users ...............................................................................................................23
Legal Notices ....................................................................................................................................24
2
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
Preface
Purpose
The Bank Directory for SAPTM (BDS) is a product that includes a file that can be uploaded by corporations into their
SAP or other ERP system. The purpose of the file is two-fold: a) to build a complete Bank Master table and keep it
up-to-date almost effortlessly; b) to make the client and vendor account data compliant with the SEPA direct debit
and credit transfer regulation.
Manually entering bank details into the Bank Master (BNKA) table each time a new client or vendors is being added
is cumbersome and error prone. A much easier and correct solution is to have the Bank Master table populated with
bank details for all banks world-wide from the BDS file, and just link these bank details to the client and vendors in
KNBK and LFBK tables through well-chosen Bank Keys. Once the SAP user has uploaded the BDS file, monthly
updates are automated through the upload of the delta files, and manual maintenance becomes unnecessary.
The EU regulation 260/2012 mandates payment service users, such as corporations, to provide the IBANs and the
SWIFT BIC codes in payments to the EURO countries within SEPA. Although the obligation to provide the BIC will
disappear in 2016, corporations that are making credit transfer and direct debit payments to SEPA countries must
make their client and vendor (supplier) bank data SEPA compliant urgently. In particular the direct debits are painful
since in general they have been configured in the SAP systems many years ago using the traditional bank codes
(clearing codes) and account numbers, and IBANs and BICs are missing. For most corporations going out and
asking the IBANs and BICs to their clients is not an option and they have to find other ways to populate these. The
BDS file has been designed to complete the Bank Numbers in their IBAN format and to complete the BICs used in
SEPA payments.
The BDS file contains basic bank details (name & address), bank codes, BICs and IBAN-specific bank codes. The
file has a generic format and content and can be uploaded into ERP systems and into proprietary payment
applications. It also can be imported into Microsoft Excel or Access for manual data analysis and repair of bank and
account details.
The BDS file does not directly support the generation of IBANs from BBANs (traditional account numbers). Although
it contains all data needed to generate an IBAN from BBAN, the generation requires country and bank-specific rules
in order to cope for the many exceptions and special cases. SWIFT Consultancy Services provide an IBAN
generation service on project basis. For more information contact SWIFT at consultancy@swift.com.
SAP users that do not start with a clean system but that already have bank entries configured in the BNKA, KNBK,
LFBK tables, should read Appendix E in order to better control the initial upload of the BDS file into the SAP system.
Distribution
The Bank Directory for SAPTM product is available within the corporate Pack Two and corporate Pack Three product
packages of SWIFT’s SWIFTRef product portfolio. For more information please consult www.swift.com/swiftref.
Data sources
The directory data is obtained from, cross-referenced with and validated against the following sources:
 ISO 9362 BIC Directory – data provided by financial institutions and corporates.
 ISO 13616 IBAN Registry for the IBANSTRUCTURE file.
 ISO 3166 Country Codes.
 ISO 4217 Currency Codes.
 National codes from the issuing authorities such as central banks and banking associations.
 Financial Institutions – via the online data management interface (“PAK”) - in particular for the IBAN BICs
and IBAN NATIONAL IDs.
 Standards bodies in IBAN countries for the dates when IBANs become used.
3
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
1
General product information
1.1
Bank Directory for SAPTM
Bank Directory for SAPTM is one of the TXT file-based products in the SWIFTRef portfolio. The product consists of a
set of TXT files that are compressed in a .zip package. The zip package is updated and published monthly.
1.2
File format
The files are structured TXT files, with:

Line separator: CR/LF

Field separator: Tab character

File extension: .txt
The files are encoded in the UFD8 format. The characters used within the files belong to the SWIFT X character set
(see Appendix A).
1.3
File names
The downloadable zip package contains the following files:
Latest version files
Available
BANKDIRECTORYSAP_V1_FULL_YYYYMMDD.txt
Jan 2013
BANKDIRECTORYSAP_V1_DELTA_YYYYMMDD.txt
Feb 2013
COUNTRY_CODE_YYYYMMDD.txt
Jan 2013
CURRENCY_CODE_YYYYMMDD.txt
Jan 2013
IBANSTRUCTURE_FULL_YYYYMMDD.txt
Jan 2013
The FULL file contains the full set of data. It can be used to re-initialise, re-build the target data base.
The DELTA file only contains the changes (additions, deletions and modifications) relative to the previous release. It
is used to update the target data base.
NB: there is no DELTA file for the IBANSTRUCTURE file due to the infrequent changes, therefore the full file is only
ever available.
The structure and content of the files are explained in further sections in this document.
The md5sum file (not shown in table above) contains the digest for file integrity verification.
The Release Notes file (optional, not shown in table above) contains a brief description of the latest changes (see
section Release Notes).
1.4
Previous file versions
The structure of the data files can evolve with time, for example, because new data is being added in the form of
new columns. The files listed in the previous section are the latest version files included in the zip package. If
previous versions of files exist, they also might be included in the downloadable zip package.
Currently there are no previous versions of the files included in the Bank Directory for SAPTM downloadable package.
4
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
Downloading the files
1.5
TM
The Bank Directory for SAP zip package can be downloaded manually from www.swiftref.com by authorised
users only using a supplied access key. The user access will be configured at ordering time. For questions contact
us at swiftref@swift.com.
The package can also be received automatically. Please read the SWIFTRef Automated Download Service
Technical Specification, available on www.swift.com/swiftref, for more information. Contact us at swiftref@swift.com
to order the download automation option.
Customers connected to the SWIFT Network also can obtain the files securely and automatically via FileAct. Please
read the Implementation Guidelines for Directories Distribution over FileAct, available on www.swift.com/swiftref, for
more information. Contact us at swiftref@swift.com to order the FileAct delivery option.
Uploading the files
1.6
The BANKDIRECTORYSAP (FULL or DELTA) can be uploaded into:

SAP systems. SAP version 4.7 or later is required. Please read SAP note 1737484 for detailed upload
options.

Other ERP system or payments application. The user will have to implement its own integration software.

Microsoft Excel or Microsoft Access – for desktop consultation. Please make sure to format the Excel sheet
as text before uploading the file in order to preserve leading zeros (“0”).
Note that COUNTRY, CURRENCY and IBANSTRUCTURE files cannot be uploaded into SAP through the upload
utility, but can be consulted outside of the system.
1.7
Future file changes
The structure of the data files can exceptionally evolve with time, for example because new data must be added in
the form of new columns in order to support a new regulation. SWIFT will take care to limit the number of changes to
a minimum. In case SWIFT changes a file it will keep providing the old file for 18 months. The files and the relevant
technical specifications will be identified by a version number.
1.8
Release notes
Customers are notified of important changes to the files in the zip packages through the Release Notes. Release
Notes are simple TXT files included in the downloadable zip packages and contain a brief description of a change.
Examples are: a new version of a file due to a structure change, change to the meaning of the data in a file, phaseout of an old version of a file. If a Release Note is present in the zip package please read it carefully and take any
actions if required.
1.9
Support
TM
Customers using the Bank Directory for SAP can receive support on the data content by sending an email to the
SWIFTRef data team at swiftrefdata@swift.com. Support can also be requested via support@swift.com.
For information on all SWIFTRef products please visit www.swift.com/swiftref/.
Support related to SAP, the SAP notes and the upload utility must be requested via SAP support.
1.10
Terminology
For the definitions of the fields (columns) in the files see section 2.1.
Bank Key
The unique identifier of a bank or branch in the BNKA, LFBK and KNBK tables. The Bank
Key can be composed in different ways as described in section E.4.
5
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
Bank Number
The unique identifier of a bank or branch in the BNKA table. The Bank Number contains
the NATIONAL ID or IBAN NATIONAL ID (for an IBAN country) from the Bank Directory
TM
for SAP (BDS) file. Synonyms of Bank Number are: bank/branch code, clearing code,
sorting code, routing number.
SWIFT Code
BIC (Business Identifier Code). BICs that identify a financial institution or a large
corporation consist of 8 characters, sometimes padded with “XXX”. Example:
GEBABEBB or GEBABEBBXXX, are equivalent. BICs that identify a branch or a line of
business consist of 11 characters. Example: BNPAFRPPLYO (Lyon branch), or
BISSIE2DFEX (Foreign Exchange department).
6
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
2
BANKDIRECTORYSAP file
The BANKDIRECTORYSAP file contains both the bank and branch related attributes and identifiers as well as the
IBAN related identifiers, combined in one file.
2.1
Field definitions
The table below contains the definitions of the fields (columns) in the BANKDIRECTORYSAP file – both the full and
the delta file.
Field name
Data
type
Max
length
Always Description
present
MODIFICATION FLAG
alphabetic
1
yes
Modification flag, in delta files:
 A (addition)
 M (modification)
 D (deletion)
In full files:
 A (addition)
See Appendix B.1 for more about Modification Flags
RECORD KEY
alphanumeric
12
yes
The unique key of the record in the file.
See Appendix B.2 for further details about Record keys
ISO COUNTRY CODE
alphabetic
2
yes
The ISO 3166-1 alpha-2 code of the country of the
institution/branch.
NATIONAL ID
alphanumeric
15
no
The national identifier of the institution/branch. The National
ID consists of the bank code and the branch code
(optional).
Synonyms for the National ID are bank code, clearing code,
sort code, sorting code, routing number.
See Appendix D for a list of National IDs with description
and source.
BIC
alphanumeric
11
no
The BIC (“SWIFT code”) of the institution/branch.
In case a BIC8 was issued it is padded with “XXX”.
ISO IBAN COUNTRY
CODE
alphabetic
2
no
The ISO 13616 prefix of the IBAN format applied to the
IBANs issued by the institution.
When a country or territory adopts an IBAN format of
another country, this can be different from the ISO
COUNTRY CODE.
IBAN NATIONAL ID
alphanumeric
15
no
The national identifier of the institution/branch in the format
as included in the IBANs.
In special cases the format/value can be different from the
NATIONAL ID.
IBAN BIC
alphanumeric
11
no
The BIC issued together with the IBANs to the institution’s
account holders.
In special cases it can be different from the value in the
field BIC.
In case a BIC8 was issued it is padded with “XXX”. In
practice, a BIC with branch code “XXX” (length 11) is
equivalent to a BIC without branch code (length 8).
IBAN CONTEXT
alphabetic
1
no
Indicates in which context the IBANs are used in the
country:
7
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
UNIQUE ID
alphabetic
1
no

S for a SEPA country,

I for any other country using IBANs,

empty for all other countries.
Flags the record to select in case duplicate combinations of
ISO COUNTRY CODE, NATIONAL ID and BIC exist:

U for unique combinations,

D for duplicates.
Note: This data is designed for ERP systems other than
SAP. The SAP system automatically selects ’unique’ Bank
Keys and ignores duplicates.
INSTITUTION NAME
any
105
yes
Institution name.
BRANCH
INFORMATION
any
70
no
Description of the institution/branch as provided by the
financial institution to which it belongs. Only provided for
records that contain a BIC code. The information is sourced
from the BIC Directory.
OFFICE TYPE
alphabetic
2
yes
The type of the institution/branch in the office hierarchy:
HO - Head Office
MP - Main Payments Office
DB - Domestic Branch or dept.
SB - Sub Domestic Branch
FB - Foreign Branch
SF - Sub Foreign Branch
UC – Unclassified
See Appendix C for more details.
STREET ADDRESS 1
any
35
no
Street name.
STREET ADDRESS 2
any
35
no
Street number.
STREET ADDRESS 3
any
35
no
Building, building name, floor.
STREET ADDRESS 4
any
35
no
Area.
CITY
any
35
no
City name of the institution/branch.
ZIP CODE
any
15
no
The ZIP/postal code of the institution/branch.
CPS
any
90
no
The county, province, state of the institution/branch.
POB NUMBER
any
35
no
The post box number of the institution/branch.
COUNTRY NAME
any
70
yes
The country name of the institution/branch.
8
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
COUNTRY CODE File
3
This file contains information about ISO countries.
3.1
Field definitions
Field name
Data
type
Max
length
Always
present
TAG
alphabetic
2
yes
MODIFICATION
FLAG
alphabetic
1
yes
Description
Record tag identifier: CT

A (addition),

M (modification),

D (deletion),

U (unchanged).
Note that these values are included in the full
file as there is no delta file for Country Codes.
See Appendix B.1 for more about Modification
Flags
COUNTRY CODE
alphabetic
2
yes
The ISO 3166-1 alpha-2 country code
COUNTRY NAME
alphabetic
70
yes
The ISO 3166-1 alpha-2 Country name
9
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
CURRENCY CODE File
4
This file contains information about all ISO currencies.
4.1
Field definitions
Field name
Data
type
Max
Always
Description
length present
TAG
alphabetic
2
yes
MODIFICATION
FLAG
alphabetic
1
yes
Record tag identifier: CU

A (addition),

M (modification),

D (deletion), or

U (unchanged).
Note that these values are included in the full file
as there is no delta file for Country Codes.
See Appendix B.1 for more about Modification
Flags
CURRENCY CODE
alphabetic
3
yes
The ISO 4217 code of the currency
CURRENCY NAME
any
70
yes
The ISO 4217 currency name
FRACTIONAL DIGIT
numeric
1
yes
Fractional digit for the currency, that is, the
number of digits after the decimal to be used
COUNTRY CODE
alphabetic
2
yes
The ISO 3166-1 alpha-2 country code
COUNTRY NAME
any
70
yes
The ISO 3166-1 country name
10
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
IBAN STRUCTURE File
5
This file contains information about all ISO IBAN formats registered by countries that have adopted
IBAN or are in the process of adopting IBAN.
5.1
Field definitions
Data
type
Max
length
Always
present
Description
TAG
alphabetic
2
yes
Record Identifier: IS
MODIFICATION FLAG
alphabetic
1
yes
Modification flag:
 A (addition)
See Appendix B.1 for more about Modification Flags
IBAN COUNTRY CODE
alphanumeric
2
yes
The ISO 3166-1 alpha-2 code prefix in the IBAN.
IBAN COUNTRY CODE
POSITION
numeric
2
yes
Start position of the country code in IBAN.
IBAN COUNTRY CODE
LENGTH
numeric
1
yes
Number of characters of the country code in the
IBAN.
IBAN CHECK DIGITS
POSITION
numeric
2
yes
Start position of check digits in the IBAN.
IBAN CHECK DIGITS
LENGTH
numeric
2
yes
Number of check digits in the IBAN.
BANK IDENTIFIER
POSITION
numeric
2
yes
Start position of bank identifier in the IBAN.
BANK IDENTIFIER
LENGTH
numeric
2
yes
Number of characters of bank identifier in the IBAN.
BRANCH IDENTIFIER
POSITION
numeric
2
no
Start position of the branch identifier in the IBAN
(value is empty if the branch identifier is not applied
in the country's IBAN format).
BRANCH IDENTIFIER
LENGTH
numeric
2
yes
Number of characters of the branch identifier in the
IBAN (value is 0 if the branch identifier is not applied
in the country's IBAN format).
Field name
11
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
Data
type
Max
length
Always
present
IBAN NATIONAL ID
LENGTH
numeric
2
yes
Number of significant characters of the National ID
value that are used by SWIFT to populate the IBAN
NATIONAL ID, and that are sufficient to derive the
IBAN BIC correctly.
This number can be different from (that is, smaller
than) the length of the national bank/branch identifier
defined in the IBAN Registry.
As SWIFT refines its IBAN to BIC translation
algorithms, this number may change from release to
release.
ACCOUNT NUMBER
POSITION
numeric
2
yes
Start position of the account number in IBAN.
ACCOUNT NUMBER
LENGTH
numeric
2
yes
Number of characters of account number in IBAN.
IBAN TOTAL LENGTH
numeric
2
yes
The total number of characters of the IBAN.
SEPA
alphabetic
1
yes
This flag indicates if the IBAN is used in a SEPA
country:
 Y if it does
 N if it does not
OPTIONAL COMMENCE
date
DATE
YYYYM
MDD
8
no
The date from which IBANs can be used in
payments in the country. The data in this field will be
populated gradually.
MANDATORY
COMMENCE DATE
8
no
The date from which IBANs is obligatory for
payments in the country. The data in this field will be
populated gradually.
Field name
date
YYYYM
MDD
12
Description
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
Appendix A - Character Set
The files only contain characters from the SWIFT X character set. The character set allows using parts of the data in
the files, such as institution names and addresses, in SWIFT messages.
SWIFT X character set
Type
Allowed characters
Alphabetic characters
A to Z (upper case)
a to z (lower case)
Numeric characters
0 to 9
Special characters
/ - ? : ( ) . , ' + CrLf SPACE
Transliteration of special characters that do not fit within the SWIFT X character set:
@
“ (double quote)
13
(AT)
‘ (single quote)
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
Appendix B – Fields and Flags
B.1
Modification Flag
The MODIFICATION FLAG field reflects the update status of a specific record compared to the previous issue.
B.2
Value
MODIFICATION FLAG description
A
Added since last issue.
The record was not present in the previous issue and is therefore new in the current issue.
In the FULL file all records have the MODIFICATION FLAG set to A. This is because when
a FULL file is being uploaded all records need to be added to the target data base.
In the DELTA file the new records are marked with A.
D
Deleted since last issue.
In the FULL file the record has been removed.
In the DELTA file the record is still present but marked with D. It will not appear in the next
issue of the DELTA file.
M
Modified since last issue.
The record does not contain the same information as in the previous issue.
In the FULL file the modified records have the MODIFICATION FLAG set to A. This is
because when a FULL file is being uploaded all records need to be added to the target data
base.
In the DELTA file the modified records have the MODIFICATION FLAG set to M.
Record keys
The RECORD KEY field contains the unique identifier of a particular record. The RECORD KEYs are unique.
If information in a record has changed then the record appears with modification flag M.
If the RECORD KEY itself changes, then the record in the next DELTA file will not have a modification flag M.
Instead, the record will appear twice: once with the old information (MODIFICATION FLAG set to D), and once with
the new information (MODIFICATION FLAG set to A). The two records will have different RECORD KEYs.
B.3
Date fields
Date fields have a length of 8 characters, structured in the format YYYYMMDD, where:

YYYY = 4 digits year


MM = 2 digits month
DD = 2 digits day
14
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
Appendix C – Office Type
Where possible, within the BANKDIRECTORYSAP file, each bank/branch is flagged in field OFFICE TYPE with the
following values:
Head Office
HO - This is the head office of the institution. In the case that the institution has a BIC ending in xxx, this BIC is
shown as the head office and is usually the BIC to which cross-border payments should be sent.
It should be noted that not all HOs are Legal Entities (for example, separate banking divisions may retain the names,
operational and code structures of banks that have been absorbed into larger organisations).
Main Payments Office
MP - This is the main domestic payments office for the financial institution concerned. This is used by banks that do
not wish to receive cross-border payments via their head office. Where no Main Payments Office is indicated,
therefore, payments should be sent to the Head Office.
Domestic Branches & Departments
DB - These are branches and departments with their own BIC and/or National ID in the same territory as the Main
Payments Office to which they are linked.
SB - The status of Sub-Domestic Branch\Department will be flagged if this is indicated by the source National ID file
or the BIC Directory.
Foreign Branches and Departments
FB - These are branches and departments with their own BIC and/or National ID in a different territory to the Main
Payments Office.
SF - The status of Foreign Sub-Domestic Branch\Department will be flagged if this is indicated by the source
National ID file or the BIC Directory.
Unclassified
UC - Offices that are not classified.
15
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
Appendix D – List of countries
D.1
List of countries with BIC codes
In Bank Directory for SAPTM all 230 countries and territories in which financial institutions are located are
represented. The financial institutions in these countries have at least the BIC code as identifier. For most of the
countries the financial institutions also have a bank code, here called the National ID (see next section).
D.2
List of countries with National IDs (Bank Numbers)
The table below shows the list of countries for which the National IDs (also called Bank Numbers, bank and branch
codes, bank codes, clearing codes, sort codes, sorting codes, routing numbers or clearing codes) and IBAN National
IDs (Bank Numbers in IBAN format) are included in the Bank Directory for SAPTM. New countries are being added to
the file over time.
COUNTRY NAME
ISO
CTRY NATIONAL ID name
CODE
IBAN SEPA
CTRY CTRY
ALBANIA
ALGERIA
AMERICAN SAMOA
ANDORRA
ARGENTINA
ARMENIA
ARUBA
AUSTRALIA
AUSTRIA
BAHRAIN
BELGIUM
BENIN
BERMUDA
BOSNIA AND
HERZEGOVINA
BRAZIL
BULGARIA
BURKINA FASO
CAMBODIA
CAMEROON
AL
DZ
AS
AD
AR
AM
AW
AU
AT
BH
BE
BJ
BM
KIB
Code Etablissement
ABA Code
Codificació de les oficines bancàries
N.banco/codigo
RT Number (Routing number)
BSB Number (Bank State Branch)
Bankleitzahl (BLZ )
BIC 4
Bank identification codes
Code
Clearing code
yes
yes
yes
BA
Bank Code (Šifra Banke)
yes
BR
BG
BF
KH
CM
CANADA
CA
CAPE VERDE
CENTRAL AFRICAN
REPUBLIC
CHAD
CHILE
COLOMBIA
CONGO
COSTA RICA
COTE D'IVOIRE
CROATIA
CYPRUS
CZECH REPUBLIC
DENMARK
ECUADOR
EL SALVADOR
EQUATORIAL GUINEA
ESTONIA
CV
Cod Compensação
BAE codes - Banking Addressable Entity
Code
Bank Identification Number
Code et code agence
Canadian Transit Number / Routing
Numbers
Código de instituição
CF
Code et code agence
10 = 5 + 5
TD
CL
CO
CG
CR
CI
HR
CY
CZ
DK
EC
SV
GQ
EE
Code et code agence
Codigo de Identificacion
Código de Compensacion
Code et code agence
Código de Participantes Asociados
Code
Vodeći Broj Banke
Cyprus Bank Identification Code (CYRN)
Identity code
Registreringsnr.
Código Institución
Código de Institución
Code et code agence
EERN/Pangakood
10 = 5 + 5
3
2
10 = 5 + 5
3
5
7
8
4
4
2
4
10 = 5 + 5
2
16
yes
IBAN
IBAN NATIONAL ID
NATIONAL ID
pre- length &
length &
fix structure
structure
AL 8 = 3 + 4 + 1
8=3+4+1
3
9
AD 8 = 4 + 4
8=4+4
5
5
9
6=3+3
6=3+3
AT 5 = 2 + 3
5=2+3
BH 4
4
BE 3
3
5
2
yes
yes
yes
yes
BA
yes
BG
3
3
7=3+4
8=4+4
5
6=3+3
10 = 5 + 5
8=4+4
9=5+4
2
yes
CR
yes
yes
yes
yes
yes
yes
yes
HR
CY
CZ
DK
yes
yes
EE
3
7
8
4
4
2
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
COUNTRY NAME
FAROE ISLANDS
FINLAND
FRANCE
FRENCH GUIANA
FRENCH POLYNESIA
GEORGIA
GERMANY
GHANA
GIBRALTAR
GREECE
GREENLAND
GUADELOUPE
GUAM
GUATEMALA
GUERNSEY, C.I.
GUINEA
GUINEA-BISSAU
GUYANA
HAITI
HOLY SEE (VATICAN
CITY STATE)
HONDURAS
HONG KONG
HUNGARY
ICELAND
INDIA
INDONESIA
IRELAND
ISLE OF MAN
ISRAEL
ITALY
JERSEY, C.I.
JORDAN
KAZAKHSTAN
KENYA
KYRGYZSTAN
LATVIA
LEBANON
LESOTHO
LIECHTENSTEIN
LITHUANIA
LUXEMBOURG
MACAO
MACEDONIA,THE
FORMER YUGOSLAV
REPUBL. OF
MADAGASCAR
MALAYSIA
MALI
MALTA
MARTINIQUE
MAURITANIA
MAURITIUS
MAYOTTE
MOLDOVA, REP. OF
MONACO
MONGOLIA
ISO
CTRY NATIONAL ID name
CODE
IBAN SEPA
CTRY CTRY
FO
FI
FR
GF
PF
GE
DE
GH
GI
GR
GL
GP
GU
GT
GG
GN
GW
GY
HT
Registreringsnr.
Konttori- numero
Code Bancaire/code guichet – RIB
Code Bancaire/code guichet – RIB
Code Bancaire/code guichet – RIB
Bank Code
Bankleitzahl (BLZ)
Sort Code
Sort Code
HEBIC – Hellenic Bank Identification Code
Registreringsnr.
Code Bancaire/code guichet – RIB
ABA Code
Codigos Bancarios
Sort Code
VA
ABI CAB
HN
HK
HU
IS
IN
ID
IE
IM
IL
IT
JE
JO
KZ
KE
KG
LV
LB
LS
LI
LT
LU
MO
Código CNBS
Bank Clearing Code
Bankfiók-kód
Bank identifier
IFSC Code
Clearing Codes
National Sort Code
Sort Code
Bank Code
ABI CAB
Sort Code
Bank Code
Bank Code
Bank and branch code
Bank Identification Code
BIC4
Banque du Liban Bank List No.
Code
BC number
Codes
Code IBAN Luxembourg /Bank Code
Bank Code
MK
Bank Code
MG
MY
ML
MT
MQ
MR
MU
YT
MD
MC
MN
Code Banque and Code Agence
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
Code
Routing number
Routing number
IBAN
IBAN NATIONAL ID
NATIONAL ID
pre- length &
length &
fix structure
structure
FO 4
4
FI 3
3
FR 10 = 5 + 5
10
FR 10 = 5 + 5
FR 10 = 5 + 5
GE 9
2
DE 8
8
6
GI 6 = 2 + 4
4 = BIC4
GR 7 = 3 + 4
7=3+4
GL 4
4
FR 10 = 5 + 5
10 = 5 + 5
9
2
GB 6 = 2 + 4
10 =BIC4+2+4
6
5
8=3+5
9
yes
10 = 5 + 5
yes
yes
yes
yes
HU
IS
yes
yes
yes
yes
yes
yes
IE
yes
IL
IT
KZ
yes
yes
yes
LV
LB
yes
yes
yes
yes
yes
yes
LI
LT
LU
yes
MK
National banking code
Code
National Id
Code Bancaire/code guichet – RIB
Code Banque
Bank Code
Code Bancaire/code guichet – RIB
Participant Code
Code Bancaire/code guichet – RIB
Bank code
17
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
MT
FR
MR
MU
FR
MD
MC
6=2+4
6=3+3
8=3+4+1
4
11 = 4 + 1 + 6
7=3+4
6=2+4
6=2+4
6
10 = 5 + 5
6=2+4
2
3
5=2+3
6=3+3
4 = BIC4
4
6=3+3
5
5=2+3
3
3
3
8=3+4+1
4
10 =BIC4+2+4
10 =BIC4+2+4
6
10 = 5 + 5
10 =BIC4+2+4
3
4 = BIC4
4
5
5=2+3
3
3
10 = 5 + 5
4
5
5
10 = 5 + 5
10 = 5 + 5
4=2+2
10 = 5 + 5
11 = BIC11
10 = 5 + 5
5 or 6
9 = BIC4 + 5
10 = 5 + 5
10 = 5 + 5
8 = BIC4+2+2
10 = 5 + 5
2 = BIC2
10 = 5 + 5
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
COUNTRY NAME
ISO
CTRY NATIONAL ID name
CODE
IBAN SEPA
CTRY CTRY
IBAN
IBAN NATIONAL ID
NATIONAL ID
pre- length &
length &
fix structure
structure
MONTENEGRO,
REPUBLIC OF
ME
Fiksni broj (Bank Code)
yes
ME
MOROCCO
MA
Code Banque
MOZAMBIQUE
NAMIBIA
NEPAL
NETHERLANDS
NEW CALEDONIA
NEW ZEALAND
NICARAGUA
NIGER
NIGERIA
NORTHERN
MARIANA ISLANDS
NORWAY
PAKISTAN
PALESTINIAN
TERRITORY,
OCCUPIED
PANAMA
PARAGUAY
PERU
POLAND
PORTUGAL
PUERTO RICO
QATAR
REUNION
ROMANIA
RUSSIAN
FEDERATION
SAINT PIERRE AND
MIQUELON
SAN MARINO
SAUDI ARABIA
SENEGAL
SERBIA, REPUBLIC OF
SINGAPORE
SLOVAKIA
SLOVENIA
SOUTH AFRICA
SPAIN
SRI LANKA
SWAZILAND
SWEDEN
SWITZERLAND
TAIWAN
TAJIKISTAN
TANZANIA, UNITED
REPUBLIC OF
THAILAND
TIMOR-LESTE
TOGO
TUNISIA
TURKEY
UNITED ARAB
MZ
NA
NP
NL
NC
NZ
NI
NE
NG
Códigos das Instituições de Crédito
Branch Code
Bank Code
BIC4
Code Bancaire/code guichet – RIB
Bank Number and branch number
Bank Code
Code
Bank Code
MP
ABA Code
NO
PK
Registernummer
PS
Clearing code
2
PA
PY
PE
PL
PT
PR
QA
RE
RO
No. de Ruta
3
4
3
8
8=4+4
9
2
10 = 5 + 5
4
RU
RCBIC - Russian Central Bank Id. code
PM
Code Bancaire/code guichet – RIB
yes
SM
SA
SN
RS
SG
SK
SI
ZA
ES
LK
SZ
SE
CH
TW
TJ
ABI CAB
Clearing code
Code
Bank Code
ACH Bank Code
Kód banky
Identifi kacija
Brach number
Oficinas Entidades Financieras - OEF
ASYCUDA Codes
Sort code
Clearing nummer
BC number
Bank Code
Bank Identification Code number
TZ
Sort Code
6=2+4
TH
TL
TG
TN
TR
AE
Financial Institution Code
Bank Routing Number (BNR)
Code
Code de Banque
Banka Kodu
Bank Code
7=3+4
4=2+2
5
2
4
3
yes
yes
yes
NL
FR
3
3
9=3+3+3
or 10 = 3 + 3 +
3+4
2
5 or 6
8=5+3
4 = BIC4
4 = BIC4
10 = 5 + 5
10 = 5 + 5
6=2+4
2
5
3
9
yes
Código
Numer Rozliczliczeniowy Oddzialu-banku
Numero de Identificaçao Bancaria
ABA Code
Bank Code
Code Bancaire/code guichet – RIB
BIC4
NO
yes
yes
yes
yes
PL
PT
yes
yes
yes
yes
FR
RO
4
4
8
8=4+4
10 = 5 + 5
4
9
FR
10 = 5 + 5
10 = 5 + 5
yes
yes
SM
SA
10 = 5 + 5
2
yes
RS
10 = 5 + 5
2
5
3
7=4+3
4
2
6
9=4+4+1
7=4+3
6=2+1+3
4
5
7
9
yes
yes
yes
yes
yes
SK
SI
yes
yes
ES
yes
yes
yes
yes
SE
CH
yes
yes
yes
18
yes
TN
TR
AE
3
4
2
8=4+4
3
5
2
5
3
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
COUNTRY NAME
EMIRATES
UNITED KINGDOM
UNITED STATES
VENEZUELA,
BOLIVARIAN
REPUBLIC OF
VIRGIN ISLANDS, U.S.
WALLIS AND FUTUNA
ISLANDS
ZAMBIA
ZIMBABWE
D.3
ISO
CTRY NATIONAL ID name
CODE
IBAN SEPA
CTRY CTRY
IBAN
IBAN NATIONAL ID
NATIONAL ID
pre- length &
length &
fix structure
structure
yes
GB
GB
US
Sort Code
ABA Code
VE
Codigos de Bancos
4
VI
ABA Code
9
WF
Code Bancaire/code guichet – RIB
ZM
Sort Code
ZW
Bank Sort Codes
yes
yes
FR
6=2+4
9
10 = 5 + 5
10 =BIC4+2+4
10 = 5 + 5
6=2+2+2
4 = 1 + 3 or
5=2+3
Country specific notes
The following country-specific rules apply to the National IDs and IBAN National IDs:
Country
Comment
SI, BA, TN, FI
For these countries the NATIONAL IDs and IBAN NATIONAL IDs only include the bank
code, and do not include the branch code, and therefore are shorter than the full bank and
branch code. The bank code only is sufficient in order to accurately identify the bank in the
country. Note that in these countries the branch code, included in an account holder’s
account details, is not an accurate identifier due to the account holder’s right to keep his
account details when changing branch.
ES
According to the ISO IBAN registry the IBAN NATIONAL IDs are 4+4=8 long (i.e. the check
digit is omitted). However, in this file the Spanish NATIONAL IDs are 4+4+1 (check digit) =
9 long as required by SAP.
HU
According to the ISO IBAN registry the IBAN NATIONAL IDs for HU are 3+4=7 long (i.e. the
check digit is omitted). However, in this file the Hungarian NATIONAL IDs are 3+4+1 (check
digit) =8 long as required by SAP.
19
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
Appendix E – File upload guidelines
E.1
File content
The Bank Directory for SAPTM (BDS) file contains an exhaustive list of banks and their branches. The file contains
data for all SEPA and non-SEPA countries. Of the non-SEPA countries (today) 28 countries have adopted the IBANs
as well (see the IBAN structure file). For all countries that adopted the IBAN format the SAP user can choose to
upload the IBAN-related Bank Numbers and associated SEPA BICs or the traditional Bank Numbers and BICs. The
BDS file contains:

All existing SWIFT codes (BICs) for all 230 countries and territories. The BDS file is synchronised with the
ISO BIC directory also produced and published by SWIFT at the same date as the BDS file. New banks will
be added, and de-activated banks will be removed from the BDS file at the same time as from the ISO BIC
Directory.

All existing Bank and branch Numbers (NATIONAL IDs) for 144 countries (situation in Jan 2013, see
Appendix D.2). Bank Numbers of new countries are being added regularly. Where applicable, these Bank
Numbers are linked to the BIC codes. The NATIONAL IDs are being sourced from central banks, banking
associations, and other authorised sources. Where necessary, they are being corrected/completed by input
from the banks that own these identifiers on request of SWIFT’s data collection team.

Bank Numbers as used in IBANs (IBAN NATIONAL IDs) for 58 countries that have adopted the IBANs,
including all SEPA countries.

BIC codes associated to the IBANs (IBAN BICs) for all countries that have adopted the IBANs.

Banks’ names and addresses.

Office type indicator, specifying whether the bank/branch is a head-office, a branch, and which type of
branch. This is useful if in an initial bank details clean-up process a BIC code needs to be translated into a
Bank Number and from multiple alternatives one has to be chosen.
E.2
Upload options
SAP provides the many upload options to be selected before the upload of the full BDS file or the monthly updates in
the delta file. The most important upload options are:
Country Selection
Allows the user to upload one country or a range of countries at a time instead of the
entire file with 230 countries and territories.
Countries with Bank Key
Selects countries for upload that have the specified Bank Key Type applied only. For
example, selects countries that use the country code + Bank Number as Bank Key.
Test Run
Simulates the changes that the upload will cause. If for example the number of deletions
is too high, user might want to clean-up the Bank Keys first before applying the upload in
live mode (see next section).
Delta Upload
Selects either the full BDS file or the monthly update file for upload. Initially the user will
have to upload the full file and then after the delta files.
SEPA mode
For countries that have adopted the IBAN user can select the SEPA mode. In this case
the Bank Numbers as they are used in IBANs and the associated BICs will be uploaded.
Only banks with BIC
This will filter out all banks that do not have bank codes, i.e. in general banks that are
very small and do virtually no international payments.
Only BICs connected to SWIFT Network – These are medium to large banks doing their international payments
through the SWIFT network.
Use IBAN country code
Some territories do not have their own IBAN formats but are using those of the main
country, for example MT Martinique uses the FR French IBAN format. Although the
country code of a bank in Martinique is MT, this option will replace it by FR.
Use the BIC record key
Use the RECORD KEY from the BDS file as the Bank Key, rather than using the country
code + Bank Number or any other Type 4 key. An advantage of this approach is that
banks with a Bank Number but no BIC and banks with a BIC but no Bank Number will be
20
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
uploaded and will have same type of Bank Key. The disadvantage is that this key is not
“natural”, i.e. does not contain the Bank Number nor BIC.
For more information please contact SAP support and read the SAP Note 1737484.
E.3
Choosing the Bank Keys
Choosing the right Bank Key format is important as it has long term consequences for maintenance. The Bank Key
is used in the Bank Master table (BNKA) to identify a bank uniquely, and in the KNBK and LFBK tables to link the
BNKA data to client’s or supplier’s bank details. Changing a Bank Key in BNKA therefore can affect KNBK and LFBK
tables. Different Bank Key formats can be chosen to upload the BDS file:

Country code + Bank Number (Type 1) – During the BDS file upload this will create Bank Keys for all banks
(records) in the file that contain a bank code (NATIONAL ID or IBAN NATIONAL ID). Records with a BIC
code but no bank code will be ignored. For countries where both bank codes and BICs are provided in the
file this is not a big problem because this excludes a minority of records and the excluded BIC codes mainly
represent financial institutions active in the securities business or loans and not in commercial payments.
This key type should not be selected for countries for which the BDS file only provides BIC codes and no
bank codes (see table in Appendix D.2).

Country code + BIC code (Type 4) – The BDS file upload will create Bank Keys for all banks with a BIC
code (and bank code if available). This is a good approach for countries in the BDS file that only contain
21
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
BIC codes and no bank codes, but for countries with bank codes the upload will ignore the banks with bank
code alone, i.e. the very small banks.

Country code + record key (Type 4) – The BDS upload will create a Bank Key for each record in the BDS
file. This is a good approach for each country for SAP systems but it will delete all existing Bank Keys from
the BNKA table as they all have a different format. The BDS file record key is a stable identifier as it is
expected to last for many years to come and its value is not going to change as long as the bank exists.
The SAP user should run the initial upload in Test mode to assess the impact first and take measures if needed.
For a new SAP system the choice is free as there is no impact on legacy bank data. For SAP systems that already
contain bank entries in the BNKA table and Bank Keys in the KNBK and LFBK tables, the best is to choose a Bank
Key of a format that best matches the Bank Keys already present. This decision should be made country-by-country.
If the Bank Key formats have been applied consistently in the BNKA table, and the same Bank key format is chosen
during the upload, the upload will do a limited number of modifications and deletions. If the Bank Key formats have
not been applied consistently, a clean-up of the Bank Keys is recommended before doing the upload.
E.4
Cleaning-up the Bank Keys
Prior the initial upload of the BDS file, the Bank Keys of inconsistent format will have to be made consistent. The
conversion has to be applied to all of the BNKA, KNBK and LFBK tables at the same time in order to preserve the
existing links to the client and vendor data.
In the illustration below the two Canadian (CA) Bank Keys are of different type and the same holds for the pair of
Czech (CZ) Bank Keys. They can be made consistent (both become Bank Numbers) as show in the table:
Ctr
Bank Key
before
Bank Key
after
Note
Bank name
CA
00300002
000300002
(1)
ROYAL BANK OF
CANADA
CA
BOFM
000137691
(2)
BANK OF MONTREAL
CZ
0300
0300
(3)
CESKOSLOVENSKA
OBCHODNI BANKA
CZ
CEKO
0300
(4)
CESKOSLOVENSKA
OBCHODNI BANKA
Notes:
(1) The length of the Bank code has been corrected to 9 digits by looking-up the length in Appendix D.2 and by
looking up the value in the BDS file.
st
(2) BOFM, which are the 1 4 characters of the BIC, has been converted to the Bank Number. As there are
many Bank Numbers for this bank in the BDS file, the Bank Number of type “head-office” (see column
OFFICE TYPE in the BDS file) has been chosen. In the column BRANCH INFORMATION this Bank
Number is described as “international payments department”. Alternatively, if a Bank Number were
provided in the BNKA table, this Bank Number would be chosen.
(3) The Bank Number is correct, no action.
st
(4) CEKO, which are the 1 4 characters of the BIC, has been converted to the Bank Number with type headoffice. The Bank Number is 0300, which shows that now the two CZ Bank Keys are duplicate and therefore
one of the two can be replaced by the other in all tables.
22
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
These manipulations can be made easier by exporting the BDS file and the BNKA, KNBK and LFBK tables into
Microsoft Excel, sorting the data conveniently and doing VLOOKUPs and Find/Replace operations in bulk. Make
sure to format the entire Excel sheet as Text before importing the files in order to preserve any leading zeros.
After the clean-up the tables need to be imported back into SAP. The BDS file upload will now have no or limited
impact on the existing BNKA, KNBK and LFBK tables due to a different Bank Key format.
E.5
BICPlusIBAN users
Many SAP systems are using SWIFT’s BICPlusIBAN directory, which is the predecessor of the BDS. As the
BICPlusIBAN directory will be phased out by December 2013, SAP users will have to migrate to the BDS file in
2013.
If the Bank Keys used with BICPlusIBAN consist of the BICPlusIBAN record key, then all Bank Keys will have to be
replaced by new Bank Keys, for example by the RECORD KEY of the BDS file (recommended), or any other type of
Bank Key. In order to facilitate this translation SWIFT will deliver a cross-reference file with the old record keys and
the new record keys. This file will be provided in the downloadable package that contains the BDS file in each
monthly publication between June 2013 and December 2013. SWIFT suggests to:
1)
export the content of the BNKA, KNBK and LFBK tables into Microsoft Excel
2)
import the cross-reference file into Microsoft Excel
3)
replace the Bank Keys based on the BICPlusIBAN record keys by the new Bank Keys
4)
import the BNKA, KNBK and LFBK tables into SAP and validate result
5)
upload the BDS file for the first time in Test mode, and if all is ok
6)
upload the BDS file in live mode
23
Copyright SWIFT © 2013
Bank Directory for SAP – Technical Specifications
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.
SAPTM is a registered trademark of SAP AG, Germany.
24
Copyright SWIFT © 2013