SWIFTRef Bic Dir 2018

Bic Dir 2018 dynamic configuration is populated through ingestion of BIC Directory 2018 file provided by SWIFTRef. The BIC Directory 2018 file will be decommissioned by SWIFT by November 2026 as part of SWIFTRef portfolio evolution initiative. Ingestion of BIC Directory 2018 to enable BIC Validation functionality will be supported on IPF until this time. On evolved SWIFTRef portfolio, BIC validation will be performed using Party Entity Directory with the data sourced from ingestion of Identifiers All file. Refer Identifiers All to Party Entity Directory mapping and BIC Validation

Overview

SwiftRef BIC Plus Directory, loaded via local file ingesters and containing the following file types: BICDIR2018, containing information on institutions behind the BICs and their FIN connectivity status.

File Types Supported

File Name File Types Supported File Formats Supported File Naming Conventions

BIC Directory 2018

FULL

TXT

BICDIR2018_V1_FULL_XXXXXXXX

BIC Directory 2018

DELTA

TXT

BICDIR2018_V1_DELTA_YYYYMMDD
AWS S3 Ingestion identifies this file when the file name starts with "BICDIR2018". The Full file is identified using the text FULL on the file name and the delta file is identified using the text DELTA.
The client implementations should not modify the files names provided by industry sources and ingest the files as received.

Bic Directory 2018 can be used by client implementations for BIC validation purposes.

Bic Dir 2018 Data Structure

Bic Dir 2018 property Description

tag

The type of institution(Usually FI)

modificationFlag

On the FULL file the value of MODIFICATION FLAG is always

“A” (record to add) On the DELTA file the value of MODIFICATION FLAG can be

“A” (record to add) “M” (record to modify) “D” (record to delete) Source file records with a value of "D" will not be loaded.

bicCode

The BIC8 value

branchCode

The 3 character BIC Branch code

BIC CODE concatenated with BRANCH CODE gives a BIC11

institutionName

Name of institution

branchInformation

For information only

Bic Dir 2018 V1 file to Bic Dir 2018 Directory mapping

Bic Dir 2018 V1 property Bic Dir 2018 property Comment

TAG

tag

MODIFICATION FLAG

modificationFlag

On the FULL file is always "A", and for DELTA file it can be "A", "M", or "D"

BIC CODE

bicCode

BRANCH CODE

branchCode

INSTITUTION NAME

institutionName

BRANCH INFORMATION

branchInformation

Example Mapping

Source Record from Industry file

TAG	MODIFICATION FLAG	BIC CODE	BRANCH CODE	INSTITUTION NAME	BRANCH INFORMATION	CITY HEADING	SUBTYPE INDICATION	VALUE ADDED SERVICES	EXTRA INFO	PHYSICAL ADDRESS 1	PHYSICAL ADDRESS 2	PHYSICAL ADDRESS 3	PHYSICAL ADDRESS 4	LOCATION	COUNTRY NAME	POB NUMBER	POB LOCATION	POB COUNTRY NAME
FI	U	AAAARSBG	XXX	MOBI BANKA AD		BEOGRAD	SUPE	FIN	                  CB	OMLADINSKIH BRIGADA 90V				11070 BEOGRAD	SERBIA
FI	U	AAACKWKW	XXX	AL MUZAINI EXCHANGE CO. KSCC		KUWAIT	SUPE	FIN	                  CK	BUILDING 9	BLOCK 4	SAUD BIN ABDULAZIZ ST.		13022 KUWAIT	KUWAIT	POB 2156	13022 KUWAIT	KUWAIT
FI	U	AAADFRP1	XXX	ABN AMRO INVESTMENT SOLUTIONS		PARIS	NSWB		                  NP	3 AVENUE HOCHE	CHEZ NSM	CHEZ NSM		75008 PARIS	FRANCE
FI	U	AAAJBG21	XXX	ARCUS ASSET MANAGEMENT JSC		PLOVDIV	NSWB		                  N2	BUSINESS CENTER LEGIS	6TH OF SEPTEMBER BLVD. 152			4000 PLOVDIV	BULGARIA
FI	U	AAAMFRP1	XXX	NEXAM		PARIS	NSWB		                  NP	20 RUE LE PELETIER				75009 PARIS	FRANCE
FI	U	AAAOFRP1	XXX	ACA  ASSET MANAGEMENT COMPANY AND ASSOCIES		PARIS	NSWB		                  NP	241 BOULEVARD ST GERMAIN				75007 PARIS	FRANCE
FI	U	AAAPBGS1	XXX	ALARIC CAPITAL		SOFIA	NSWB		                  NS	EXARCH YOSIF 7				1301 SOFIA	BULGARIA

Destination Record - BicDir2018

{
  "tag": "FI",
  "modificationFlag": "U",
  "bicCode": "AAAARSBG",
  "branchCode": "XXX",
  "institutionName": "MOBI BANKA AD",
  "branchInformation": ""
}

Setting Type

DPS v2 introduced new attribute of Setting Type. This is used for generation of all API endpoints for a particular setting. It is also used in index-config.<setting type> construct. SETTING_TYPE = "processingentity"

Searchable Fields

Searchable fields for Processing Entity are:

  • tag

  • modificationFlag

  • bicCode

  • branchCode

  • institutionName

  • branchInformation

Indexes

DPS v2 provides an option to configure indexes for each setting. Default indexes for BicDir2018 are:

ipf.dps.mongodb.index-config.bicdir2018 {
    index-1 = ["values.payload.bicCode:ASC"]
    index-2 = ["values.payload.branchCode:ASC"]
    index-3 = ["status:ASC"]
    index-4 = ["source:ASC"]
    index-5 = ["payload.bicCode:ASC"]
    index-6 = ["payload.branchCode:ASC"]
    index-7 = ["processingEntity:ASC"]
    index-8 = ["lastUpdatedAt:ASC"]
}

This can be overridden or updated. Just note that when the field is under payload, you need to provide an index like: index-x = ["values.payload.fieldX:ASC"].

Field processingEntity is added in to the setting search so for better performances is recommended that index for processingEntity is created.

Notifications

DPS v2 can provide notification after certain CRUD operation on a setting is performed. There is an option to enable notifications on setting level. Notifications are disabled by default:

ipf.csm-reachability.should-send-notification.bicdir2018-settings = false

History

There is an option to disable history on setting level. History is enabled by default:

ipf.csm-reachability.should-save-history.bicdir2018-settings = true