Upload
e2358927
View
469
Download
37
Tags:
Embed Size (px)
Citation preview
BIC Directory
Technical SpecificationsThese technical specifications provide detailed information about the BIC Directory. The information includes descriptionsof files, records, fields, and flags. This document is intended for anyone who installs and administers the BIC Directory.
August 2009
Messaging
Table of Contents
1 About BIC Directory ....................................................................................................................................... 3
2 Files ....................................................................................................................................................................... 42.1 File Types in the Download Packages ................................................................................................... 42.2 File Names ................................................................................................................................................. 52.3 File Formats ............................................................................................................................................... 62.4 Record Length per File ............................................................................................................................. 6
3 Records ............................................................................................................................................................... 83.1 AM Records ................................................................................................................................................ 83.2 CT Records ................................................................................................................................................ 93.3 CU Records .............................................................................................................................................. 103.4 FI Records (BIC Update Files) .............................................................................................................. 113.5 FI Records (BIC Bank Files) .................................................................................................................. 153.6 HD Records (BIC Update, Currencies, Countries, Holidays Files) ................................................. 163.7 HD Records (BIC Bank Files) ................................................................................................................ 183.8 HF Records .............................................................................................................................................. 183.9 HS Records .............................................................................................................................................. 203.10 TZ Records ............................................................................................................................................... 21
4 Fields and Flags ............................................................................................................................................ 234.1 Common Fields ........................................................................................................................................ 234.2 Filler Fields ............................................................................................................................................... 234.3 Key Fields ................................................................................................................................................. 254.4 Modification Flag ..................................................................................................................................... 264.5 Text Fields ................................................................................................................................................ 26
.Legal Notices ...............................................................................................................................................................28
BIC Directory
2 Technical Specifications
1 About BIC DirectoryBIC Directory
The BIC Directory, published by SWIFT, contains the list of bank identifier codes registeredaccording to the ISO 9362 standard. The BIC Directory includes the registered BICs, the namesand addresses of the corresponding entities, and additional information such as MarketInfrastructures in which the entity participates. The scope of the additional information variesaccording to the version.
BIC Directory DownloadYou can download the BIC Directory:
from swift.com, over the InternetBrowse to the Directory downloads section in Solutions > Messaging > Directories, Directorydownloads.
from SWIFTNet Portal, over SWIFTNet (using Browse, and Alliance WebStation or StarterSet)For more information about SWIFTNet Portal, see the SWIFTNet Portal User Guide, availableon swift.com > Support > Documentation.
Downloadable TXT files (FI records) are also available as delta files, which contain only thechanges as compared to the previous release.
Because of the different publication cycles, you can only switch from CD to download byperforming a FULL LOAD.
About BIC Directory
August 2009 3
2 FilesAbout this section
This section focuses on the files located in the download package. It gives information about filetypes, names and extensions, formats, and the length of records each file type can contain.
ContentsIn this section, you will find more information about these topics.
2.1 File Types in the Download PackagesIntroduction
On swift.com, in the Directory downloads section, you will find different file types, assembled inpackages. Here is a brief explanation.
File characteristicsHere is an explanation of terms and options used on the download page, related to files:
Full files: these files contain all data, not only what has changed as compared to the previousrelease.
Delta files: most packages containing TXT format files are available as full files, and as deltafiles, which contain only the changes as compared to the previous release. Delta files are onlyoffered in the TXT format.
Download package characteristicsHere is an explanation of terms and options used on the download page, related to packages:
ZIP / tar.Z: ZIP files are available for Windows, BIC Directory for Alliance packages are alsoavailable as tar.Z for UNIX. Tar.Z files will take longer to download.
Publication date: a package is available on the Friday preceding the last Saturday of the monthbefore it is activated. On the publication date, the files are published at 02 am GMT.
Activation date: a release is activated on the first Saturday of the month.
Note Both the new (published, but not yet activated) and the activated (published andactivated) packages are available.
Recommended file typeSWIFT recommends that the tab delimited file format:
File type Full name Files
BICDB BIC Directory tab delimitedfiles
The FI file in this package contains all BICs with the fullrange of data attributes. Amendment, Currency, Country,and Holiday files are also part of this package. All files arein tab delimited format.Example: FI_20080906.TXT
BIC Directory
4 Technical Specifications
Other file typesHere is a description of the other available file types:
File type Full name Files
Bankfile BIC bank files The bank files include all BICs, and for each BIC, a limitednumber of data attributes (for example, institution name,but not BIC modification flag or service code). The filesare available in different formats.Example: BANKFILE_20080906.DAT
BICDU BIC update files The FI file in this package contains all BICs with the fullrange of data attributes. Amendment, Currency, andCountry files are also part of the package.Example: BICDUFI_YYYYMMDD.DOS
CCH Currencies, Countries,Holidays files
The files in this package provide information about ISOcurrencies, ISO countries, and financial institutionsholidays for SWIFT operational countries.Example: CCH_20080906.TXT
Readme files
Full name Files
BIC Directory business codes Example: BIC_DIR_BC_20080906.pdf
Description of the different file types andrecords
Example: BIC_DIR_20080906.pdf
General information about countries This file contains, for example, cut-off times andcancellation instructions.Example: BIC_GF_20080906.pdf
2.2 File NamesFile name structures
BIC files are of one of these structures:
Type Example
_. BANKFILE_20080906.DAT
_. AM_20080906.TXT
. BICDUAM_YYYYMMDD.DOS
Variables in file namesIn the BIC file names, you will find a combination of these variables:File typeThe file type indicates whether this is a BIC bank file (BANKFILE), a BIC update file (BICDU), ora currency/country/holiday file (CCH).Activation dateThe activation date of the BIC Directory, in YYYYMMDD format. The activation date is also used inthe readme file names (PDF).
Files
August 2009 5
Data typeThe data type shows the type of record the file contains:
BIC database tab delimited files: AM, CT, CU, FI, HD, HF, HS, or TZ
BIC update files: AM, CT, CU, FI, HDExtensionPossible file extensions are: DOS, EBC, DAT and TXT.
2.3 File FormatsAvailable formats
The different file formats have these characteristics:
Extension Type of file Record format Character set
DOS stream file fixed length ASCII
EBC stream file fixed length EBCDIC
DAT text file with CR/LFseparator
fixed length ASCII
TXT text file with CR/LFseparator
tab delimited ASCII
Note There is no empty record at the end of these files.
Type of file
stream file: DOS and EBC files are stream files for backward compatibility usage only
text file with CR/LF separator
Record format
fixed length
tab delimited: variable length records separated by CR/LF (0D Hex/0A Hex) fields within arecord are delimited by the Tab (09 Hex) character.
2.4 Record Length per FileBIC bank file records
File Record length
BANKFILE_yyyymmdd.DOSBANKFILE_yyyymmdd.EBCBANKFILE_yyyymmdd.DAT
221
BANKFILE_yyyymmdd.TXT Not applicable (tab delimited)
BIC Directory
6 Technical Specifications
BIC database tab delimited file recordsRecord length is not applicable (tab delimited).
BIC update file records (all record types in 1 file)File Record length
BICDU_yyyymmdd.DOSBICDU_yyyymmdd.EBCBICDU_yyyymmdd.DAT
855
BICDU_yyyymmdd.TXT Not applicable (tab delimited)
BIC update file records (separate files)File Record length
BICDUamn.DOSBICDUamn.DAT
24
BICDUctn.DOSBICDUctn.DAT
75
BICDUcun.DOSBICDUcun.DAT
149
BICDUfin.DOSBICDUfin.DAT
848
BICDUhdn.DOSBICDUhdn.DAT
22
BICDUamn.TXTBICDUctn.TXTBICDUcun.TXTBICDUfin.TXTBICDUhdn.TXT
Not applicable (tab delimited)
Countries, Currencies, Holidays file records
File Record length
CCH_yyyymmdd.DOSCCH_yyyymmdd.DAT
855
CCH_yyyymmdd.TXT Not applicable (tab delimited)
Files
August 2009 7
3 RecordsAbout this section
The descriptions that follow detail each record type that can be found in the various files.Depending on the data type, not all record types are necessarily present in the file.
ContentsIn this section, you will find more information about these topics:
3.1 AM RecordsAbout these records
These records give information about amendments made to SWIFT and non-SWIFT BICs. Itcontains all changes made to the BIC codes (including BIC codes involved in mergers) since theprevious issue of the BIC Directory.
StructureThe length of this record is 24, without filler field:
D088
0003
AM RECORDS
tag identifier1
2
3
old BIC
new BIC
Field description
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 1 tag identifier TAG alphabetic yes 2 char : AM
2 3 old BIC OLD BIC alphanumeric yes 11 char : old BIC
3 14 new BIC NEW BIC alphanumeric yes 11 char : new BIC
Case 1A certain BIC appears in only one record (NEW BIC field). The record indicates a change in theBIC.
BIC Directory
8 Technical Specifications
An example:TAG = AM OLD BIC = AAAACH2CXXXNEW BIC = BBBBCH2CXXXThis example indicates that the bank code field for AAAACH2CXXX has changed from AAAA toBBBB.
Case 2A certain BIC appears in more than one record (NEW BIC field). Those records taken togetherindicate a merger. All BICs in the field OLD BIC for records with the same BIC in the field NEWBIC, are merged together into the BIC specified in the NEW BIC field.An example record:TAG = AMOLD BIC = AAAACH2CXXX NEW BIC = CCCCCHBZXXXAnd a second example record:TAG = AMOLD BIC = BBBBCHEDXXXNEW BIC = CCCCCHBZXXXThis example indicates that AAAACH2CXXX and BBBBCHEDXXX have merged to CCCCCHBZXXX.
3.2 CT RecordsAbout these records
These records give information about ISO countries.
StructureThe length of this record is 75, without filler field:
D088
0004
CT RECORDS
tag identifier1
2
3
modification flag
country code
4 --- 5 country name
Records
August 2009 9
Field description
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 1 tag identifier TAG alphabetic yes 2 char : CT
2 3 modificationflag
MODIFICATIONFLAG
alphabetic yes 1 char : A (addition),M (modification), D(deletion), or U(unchanged)
3 4 country code COUNTRYCODE
alphabetic yes 2 char: ISO countrycode
4 6 country name COUNTRYNAME
any type yes 35 char: countryname (part 1)
5 41 country name any type no 35 char: countryname (part 2)
3.3 CU RecordsAbout these records
These records give information about ISO currencies.
StructureThe length of this record is 149, without filler field:
D088
0005
CU RECORDS
tag identifier1
2
3
modification flag
currency mode
4 --- 5 currency name
6
7
8 --- 9
fractional digit
country code
country name
Field description
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 1 tag identifier TAG alphabetic yes 2 char: CU
2 3 modificationflag
MODIFICATIONFLAG
alphabetic yes 1 char: A (addition),M (modification), D(deletion), or U(unchanged)
BIC Directory
10 Technical Specifications
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
3 4 currencycode
CURRENCYCODE
alphabetic yes 3 char: ISOcurrency code
4 7 currencyname
CURRENCYNAME
any type yes 35 char: ISOcurrency name (part1)
5 42 currencyname
any type no 35 char: ISOcurrency name (part2)
6 77 fractionaldigit
FRACTIONALDIGIT
numeric yes 1 char: fractionaldigit for thecurrency, that is, thenumber of decimalsto be used
7 78 country code COUNTRYCODE
alphabetic no 2 char: ISO countrycode
8 80 country name COUNTRYNAME
any type no 35 char: countryname (part 1)
9 115 country name any type no 35 char: countryname (part 2)
3.4 FI Records (BIC Update Files)About these records
These records gives information about financial institutions, here for BIC update (BICDU) files.
Records
August 2009 11
High-level structureThis is a high-level overview of the record. You will find more detailed information after this. Thelength of this record is 848, over 28 fields, the filler field not included:
D088
0006
FI (BICDU) RECORDS
tag identifier1
2
3
modification flag
BIC (bank, country and location code)
5 --- 7
BIC (branch code)4
8 --- 9
institution name
branch information
city heading10
11
12
13
14 --- 17
18 --- 20
21 --- 22
23 --- 28
subtype indication
value added services
extra information
physical address
location
country name
post office box
Tag identifier, modification flag, and BIC fields
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 1 tag identifier TAG alphabetic yes 2 char: FI
2 3 modificationflag
MODIFICATIONFLAG
alphabetic yes 1 char: A (addition),M (modification), D(deletion), or U(unchanged)
3 4 BIC (bank,country andlocationcode)
BIC CODE alphanumeric yes 8 char: bank code (4char), country code(2 char), locationcode (2 char)
4 12 BIC (branchcode)
BRANCH CODE alphanumeric yes 3 char: branch code(XXX if no branchcode exists)
BIC Directory
12 Technical Specifications
Institution name fields (mandatory/optional)Field Position Description Field Name
(tab delim. file)Data Entry Mandatory Max. Length + Data
5 15 institutionname
INSTITUTIONNAME
any type yes 35 char: name(part 1)
6 50 institutionname
any type no 35 char: name(part 2)
7 85 institutionname
any type no 35 char: name(part 3)
Branch information fields
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
8 120 branchinformation
BRANCHINFORMATION
any type no 35 char: branchspecification (part 1)
9 155 branchinformation
any type no 35 char: branchspecification (part 2)
City heading field
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
10 190 city heading CITY HEADING any type yes 35 char: city name
Subtype indication fieldHere is a description of the subtype indicator field (see the BIC Directory Business Code for acomplete list of subtype indicators and their definitions), which contains the precise type of financialinstitution, for example, a bank or a broker:
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
11 225 subtypeindication
SUBTYPEINDICATION
any type no 4 char: type offinancial institution
Value-added services fieldHere is a description of the value-added services field, which contains the value-added servicesthat the financial institution has subscribed to:
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
12 229 Value-addedservices
Value addedSERVICES
any type no 20 x 3 char: valueadded services
Records
August 2009 13
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
Moreinformation:
Positions:
1-48: can contain up to 16 three-character service codes in alphabetical order.
49-51: can contain the preferred service code. If not used, they are left blank.
52-60: are reserved for future use.
Do not put spaces between the codes. A plus sign (+) as the third character indicatesanother participant of this service. See the BIC Directory Business Code for a completelist of service codes.
Extra Information fieldHere is a detailed description of the extra Information field, containing the BIC branch qualifiers(see the BIC Directory Business Code for a complete list of the branch qualifiers and theirdefinitions), which have been implemented as of the March 2001 release:Field Position Description Field Name
(tab delim. file)Data Entry Mandatory Max. Length + Data
13 289 extrainformation
EXTRAINFORMATION
any type no 35 char: BIC branchqualifiers
Moreinformation:
Positions:
1-18: can contain up to 6 three-character branch qualifiers in alphabetic order. Donot put spaces between the codes.
19-35: are unused and left empty.
Physical address fieldsIn the physical address field, four subfields give the building name, detailed building information,street name, and number (see "Text Fields" on page 26). The order of the information in thesefour fields depends on accepted practice for the individual country:
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
14 324 physicaladdress
PHYSICALADDRESS 1
any type no 35 char: physicaladdress (part 1)
15 359 physicaladdress
PHYSICALADDRESS 2
any type no 35 char: physicaladdress (part 2)
16 394 physicaladdress
PHYSICALADDRESS 3
any type no 35 char: physicaladdress (part 3)
17 429 physicaladdress
PHYSICALADDRESS 4
any type no 35 char: physicaladdress (part 4)
BIC Directory
14 Technical Specifications
Location fieldsThe location fields contain three logical groups of information: the postal code, the location name,and the location suffix. The order of the information depends on accepted practice for the individualcountry:
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
18 464 location LOCATION any type no 35 char: location(part 1)
19 499 location any type no 35 char: location(part 2)
20 534 location any type no 35 char: location(part 3)
Country name fields
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
21 569 country name COUNTRYNAME
any type no 35 char: countryname (part 1)
22 604 country name any type no 35 char: countryname (part 2)
Post office box (POB) fieldsThe post office box field contains four logical groups of information: the POB number, POBlocation, POB postal code, POB location name, and location suffix. The order of the informationdepends on accepted practice for the individual country:
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
23 639 POB number POB NUMBER any type no 35 char: POBnumber
24 674 POB location POB LOCATION any type no 35 char: POBlocation (part 1)
25 709 POB location any type no 35 char: POBlocation (part 2)
26 744 POB location any type no 35 char: POBlocation (part 3)
27 779 POB countryname
POB COUNTRYNAME
any type no 35 char: POBcountry name (part1)
28 814 POB countryname
any type no 35 char: POBcountry name (part2)
3.5 FI Records (BIC Bank Files)About these records
These records give information about financial institutions, here for BIC bank files (BANKFILE).
Records
August 2009 15
StructureThe length of this record is 211:
D088
0007
FI (BANKFILE) RECORDS
BIC (bank, country and location code)1
2
6
BIC (branch code)
financial institution3 --- 5
city heading
7 --- 8 branch information
Field description
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 1 BIC (Bank,Country &LocationCode)
BIC CODE alphanumeric yes 8 char: bank code (4char), country code(2 char), locationcode (2 char)
2 9 BIC (Branchcode)
BRANCH CODE alphanumeric yes 3 char: branch code(XXX if no branchcode exists)
3 12 financialinstitution
INSTITUTIONNAME
any type yes 35 char: name(part 1)
4 47 financialinstitution
any type no 35 char: name(part 2)
5 82 financialinstitution
any type no 35 char: name(part 3)
6 117 city heading CITY HEADING any type yes 35 char: city name
7 152 branchinformation
BRANCHINFORMATION
any type no 35 char: branchspecification (part 1)
8 187 branchinformation
any type no 35 char: branchspecification (part 2)
3.6 HD Records (BIC Update, Currencies, Countries,Holidays Files)
About these recordsThese records identify the rebuild date for BIC update and Currencies, Countries, Holidays files(BICDU and CCH), which is the date on which the updates are applicable for SWIFT FIN.
BIC Directory
16 Technical Specifications
StructureThe length of this record is 22:
D088
0010
HD (BICDU+CCH) RECORDS
tag identifier1
2
3
text
date
StructureThe length of this record is 22:
D088
0015
HD RECORDS
tag identifier1
2
3
text
date
Field description
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 1 tag identifier TAG alphabetic yes 2 char: HD
2 3 text TEXT any type yes 12 char: REBUILDDATE
3 15 date DATE numeric yes 8 char: date ofrebuild(YYYYMMDD)
Records
August 2009 17
3.7 HD Records (BIC Bank Files)About these records
These records identify the rebuild date for BIC bank files (BANKFILE), which is the date on whichthe updates are applicable for SWIFT FIN.
StructureThe length of this record is 20:
D088
0011
HD (BANKFILE) RECORDS
text1
2 date
Field description
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 1 text TEXT any type yes 12 char: REBUILDDATE
2 13 date DATE numeric yes 8 char: date ofrebuild(YYYYMMDD)
3.8 HF RecordsAbout these records
These records contain information about financial institution holidays in the SWIFT-connectedcountries.
BIC Directory
18 Technical Specifications
StructureThe length of this record is 404, without filler field:
D088
0012
HF RECORDS
tag identifier1
2
3
modification flag
holiday type
4 --- 5
special holiday info
6
7
date
country code
country name
8
Field description
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 1 tag identifier TAG alphabetic yes 2 char: HF
2 3 modificationflag
MODIFICATIONFLAG
alphabetic yes 1 char: A (addition),M (modification), D(deletion), or U(unchanged)
3 4 country code COUNTRYCODE
alphabetic yes 2 char: ISO countrycode
4 6 country name COUNTRYNAME
any type yes 35 char: countryname(part 1)
5 41 country name any type no 35 char: countryname(part 2)
6 76 date DATE numeric yes 8 char: date of aholiday(YYYYMMDD)
7 84 holiday type HOLIDAY TYPE any type yes 1 char: codeindicating type ofholiday
8 85 specialholiday info
SPECIALHOLIDAY INFO
any type no 320 char:restrictionsapplicable if aholiday is notapplicablecountrywide, or isnot a full day, oradditional text for allholiday types
Records
August 2009 19
More info about field 7, holiday typeThe holiday type field can contain the following values:
Value Description
A morning weekend holiday (occurring every week)D special exchange holiday in country
E exchange holidays
F morning exchange holidays
G afternoon exchange holidays
H normal holiday
P afternoon weekend holiday (occurring every week)S special holiday
W weekend holiday
X morning holiday (occurring only once)Y afternoon holiday (occurring only once)
3.9 HS RecordsAbout these records
These records contain information about holidays related to a particular service, such as financialinstitution holidays.
StructureThe length of this record is 335, without the filler field:
D088
0013
HS RECORDS
tag identifier1
2
4
modification flag
service code
date
holiday type
3
5
6 special holiday info
BIC Directory
20 Technical Specifications
Field description
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 1 tag identifier TAG alphabetic yes 2 char: HS
2 3 modificationflag
MODIFICATIONFLAG
alphabetic yes 1 char: A (addition),M (modification), D(deletion), or U(unchanged)
3 4 service code SERVICECODE
any type yes 3 char: value-addedservice code
4 7 date DATE numeric yes 8 char: date of aholiday(YYYYMMDD)
5 15 holiday type HOLIDAY TYPE any type yes 1 char: codeindicating type ofholidaySee "More infoabout field 7,holiday type" onpage 20.
6 16 specialholiday info
SPECIALHOLIDAY INFO
any type no 320 char:restrictionsapplicable if aholiday is notapplicablecountrywide, or isnot a full day, oradditional text for allholiday types
3.10 TZ RecordsAbout these records
These records contain information about the local time difference in relation to GMT, and on thestart and end dates for standard time and daylight saving time (if applicable). Only tab delimitedformat is available for this record type. There is no filler field.
Records
August 2009 21
Structure
D088
0014
TZ RECORDS
tag identifier1
2
3
modification flag
starting date
ending date
5
6
region code
country name
country code
7
4
8 hours difference
Field description
Field Position Description Field Name(tab delim. file)
Data Entry Mandatory Max. Length + Data
1 - tag identifier TAG alphabetic yes 2 char: TZ
2 - modificationflag
MODIFICATIONFLAG
alphabetic yes 1 char: A (addition),M (modification), D(deletion), or U(unchanged)
3 - country code COUNTRYCODE
alphabetic yes 2 char: ISO countrycode
4 - country name COUNTRYNAME
any type yes 35 char: countryname (part 1)
5 - region code REGION CODE any type yes 1 char: firstcharacter of thelocation code (* forentire country)
6 - starting date STARTINGDATE
numeric yes 8 char: starting date(YYYYMMDD)
7 - ending date ENDING DATE numeric yes 8 char: ending date(YYYYMMDD)
8 - hoursdifference
HOURSDIFFERENCE
numeric no 5 char: number ofhours and minutesdifference (-)HHMM
BIC Directory
22 Technical Specifications
4 Fields and FlagsAbout this section
This section groups all generic fields and flags descriptions, as found in the different files andrecords.
ISO namesSome of the fields in certain records list information defined by ISO. However, the names in thoserecords are the ones used to print the BIC Directory and may be abbreviated.
Other fieldsIn this section you will find more detailed information about the remaining fields:
4.1 Common FieldsDate fields
Date fields have 8 characters, structured in this format:YYYYMMDD
Mandatory/optional flagThis flag indicates whether the field must contain information (mandatory, indicated by "yes" in therecords section), or can be empty (optional, indicated by "no" in the records section). If the fieldhas no information, it is filled with blanks.
4.2 Filler FieldsAbout the filler fields
Fixed length records can contain a filler field after all data fields. They are filled with blankcharacters. Records in tab delimited files retain the filler field when present in other equivalentformats.
BIC bank file recordsFor BANKFILE_yyyymmdd files the filler field is as follows:
HD records (DOS, EBC, DAT files)Field Position Description Data Entry Mandatory Max. Length + Data
3 21 Filler any type yes 201 char: (blanks)
HD records (TXT files) have a filler field header, but the field is empty.
Note There are no filler fields in the FI records.
BIC database tab delimited file recordsThese files have no filler field.
Fields and Flags
August 2009 23
BIC update file records (DOS, EBC, DAT files)For BICDU_yyyymmdd files the filler field is as follows:
FI records
Field Position Description Data Entry Mandatory Max. Length + Data
29 849 Filler any type yes 7 char: (blanks)
CU records
Field Position Description Data Entry Mandatory Max. Length + Data
10 150 Filler any type yes 150 char: (blanks)
CT records
Field Position Description Data Entry Mandatory Max. Length + Data
6 76 Filler any type yes 780 char: (blanks)
AM records
Field Position Description Data Entry Mandatory Max. Length + Data
4 25 Filler any type yes 831 char: (blanks)
Note BICDUxxn.* files have no filler field.
Currencies, Countries, Holidays file records (DOS, EBC, DAT files)For CCH_yyyymmdd files the filler field is as follows:
HD records
Field Position Description Data Entry Mandatory Max. Length + Data
4 23 Filler any type yes 833 char: (blanks)
HS records
Field Position Description Data Entry Mandatory Max. Length + Data
7 336 Filler any type yes 520 char: (blanks)
HF records
Field Position Description Data Entry Mandatory Max. Length + Data
9 415 Filler any type yes 451 char: (blanks)
CU records
Field Position Description Data Entry Mandatory Max. Length + Data
10 160 Filler any type yes 706 char: (blanks)
BIC Directory
24 Technical Specifications
CT records
Field Position Description Data Entry Mandatory Max. Length + Data
6 76 Filler any type yes 780 char: (blanks)
4.3 Key FieldsAbout key fields
A key field contains the value of a unique identifier for a particular record type (for example, BICfor FI records, CT code for country records, CU code for currency records).
Key field changeIf a key field changes, then the record in the next BIC Directory file will not have a modificationflag M. The record appears twice: once with the old information (modification flag = D), and oncewith the new information (modification flag = A).
Note If other information in a record has changed, and not a key field, then the recordappears only once with modification flag M.
Key fields list
Record Field Description Field Number
CT country code 3
CU currency code 3
FI BIC (bank, country & location code) BICDU: 3, BANKFILE: 1BIC (branch code) BICDU: 4, BANKFILE: 2
HF country code 3
date 6
HS service code 3
date 4
TZ country code 3
region code 6
starting date 7
ending date 8
Key fields list
Record Field Description Field Number
HF country code 3
date 6
HS service code 3
date 4
TZ country code 3
Fields and Flags
August 2009 25
Record Field Description Field Number
region code 6
starting date 7
ending date 8
4.4 Modification FlagAbout the modification flag
This field reflects the update status for that specific record compared to the previous BIC Directoryissue. All records (except the single HD record and all the Bank File records) bear a modificationflag in the third position.
Possible flagsThese modification flags are used in the records:
Modification Flag Meaning
A Added since last BIC DirectoryThe record was not present in the previous BIC Directory file, and is therefore new inthe current issue.
D Deleted since last BIC DirectoryThe record has been removed since the previous issue of the BIC Directory. The BICstill appears in this particular issue to provide the deletion information, but will notappear in future issues of the BIC Directory.
U Unchanged since last BIC DirectoryThe record has not been changed since the previous BIC Directory. In the currentissue it is still present and unchanged.
M Modified since last BIC DirectoryThe record still exists in the current issue of the BIC directory, but does not containthe same information as the previous issue. For example, when the name of theinstitution has changed since the last issue of the BIC Directory, that BIC will have Mas its modification flag.
4.5 Text FieldsTypes of text fields
There are two types of text fields:
Type Description
General text fields General text fields contain narrative information such as financialinstitution names or branch information.
Physical address text fields The physical address field is a special type of text field. The data arespread over several sub-fields instead of using just one large field.Subfields can be used to print labels or letter headings, without worryingabout where to split the field before going to the next line. With thisapproach, you can put sub-fields beneath each other.
BIC Directory
26 Technical Specifications
Sub-fields in a physical address text fieldSeveral sub-fields link together if the information has to fit on only a few lines. Sub-fields areformatted in the following way:
First sub-fieldThe information starts at position 1 of the field.
Next subfields (if not empty)Is the first position of the sub-field a blank, followed by characters?
If yes, the next characters make a new, separate word, whether the first sub-field ended ina blank or not.
If no, the next characters are joined to those ending the previous sub-field. However, a wordis never cut.
Note Tab delimited text files do not contain consecutive blanks at the end of a sub-field,they do not contain filler fields. For physical address fields, filler blanks in these fieldsare reduced to one blank.This definition is derived from the BIC Directory. Due to the different input filedefinition, the organisation into sub-fields is not always respected in BIC DatabasePlus.
Fields and Flags
August 2009 27
Legal NoticesCopyrightSWIFT 2009. All rights reserved.You may copy this publication within your organisation. Any such copy must include these legal notices.
ConfidentialityThis publication may contain SWIFT or third-party confidential information. Do not disclose this publicationoutside your organisation without the prior written consent of SWIFT.
DisclaimerSWIFT supplies this publication for information purposes only. The information in this publication may changefrom time to time. You must always refer to the latest available version on www.swift.com.
TranslationsThe English version of SWIFT documentation is the only official version.
TrademarksSWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT: SWIFT, theSWIFT logo, Sibos, SWIFTNet, SWIFTReady, and Accord. Other product, service, or company names in thispublication are trade names, trademarks, or registered trademarks of their respective owners.
BIC Directory
28 Technical Specifications
Title PageTable of Contents1 About BIC Directory2 Files2.1 File Types in the Download Packages2.2 File Names2.3 File Formats2.4 Record Length per File
3 Records3.1 AM Records3.2 CT Records3.3 CU Records3.4 FI Records (BIC Update Files)3.5 FI Records (BIC Bank Files)3.6 HD Records (BIC Update, Currencies, Countries, Holidays Files)3.7 HD Records (BIC Bank Files)3.8 HF Records3.9 HS Records3.10 TZ Records
4 Fields and Flags4.1 Common Fields4.2 Filler Fields4.3 Key Fields4.4 Modification Flag4.5 Text Fields
Legal Notices