IBAN Plus Directory

IBANPlus dynamic configuration is populated through ingestion of IBAN Plus file provided by SWIFTRef. The IBAN Plus file will be decommissioned by SWIFT by November 2026 as part of SWIFTRef portfolio evolution initiative. Ingestion of IBAN Plus to enable IBAN deconstruct functionality will be supported on IPF until this time. On evolved SWIFTRef portfolio, IBAN deconstruction 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 IBAN deconstruct for more details.

Overview

SwiftRef IBAN Plus Directory, loaded via local file ingesters and containing the following file types: IBAN Plus, containing IBAN-related data for financial institutions in SEPA and non-SEPA countries that have adopted IBAN. Supports both FULL and DIFF imports in both XML and TXT.

Iban Plus Directory Structure

DPS SETTING_TYPE = "ibanplus"

Iban Plus property Comment

modificationFlag

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

ibanBic

The BIC of the Institution. Loaded from IBAN BIC field of SWIFTRef published IBANPLUS file (part of IBANPlus Directory)

ibanIsoCountryCode

Country where the bank is located. Loaded from IBAN ISO COUNTRY CODE field of IBANPLUS file

isoCountryCode

Country where the bank is located.

ibanNationalId

Used along with IBAN ISO COUNTRY CODE to look up this table when deconstructing or validating an IBAN to retrieve the related IBAN BIC and ROUTING BIC Loaded from the IBAN NATIONAL ID field of IBANPLUS file

institutionName

Name of the Institution. Loaded from the INSTITUTION NAME field of IBANPLUS file

routingBic

Loaded from the ROUTING BIC field of IBANPLUS file From SWIFT IBAN Plus FAQ document - The ROUTING BIC is NOT related to SEPA (ISO 20022 XML) payments. The ROUTING BIC can be applied to non-SEPA IBAN payments to find the following information: • the SWIFT-connected correspondent of an unconnected bank • the central payments processing address of a bank with many unconnected branch BICs or with multiple BICs due to take-overs and mergers

serviceContext

Loaded from the SERVICE CONTEXT field of IBANPLUS file

File Types Supported

File Name File Types Supported File Formats Supported File Naming Conventions

IBAN Plus

FULL

TXT, XML

IBANPLUS_V3_FULL_YYYYMMDD

IBAN Plus

DELTA

TXT, XML

IBANPLUS_V3_DELTA_YYYYMMDD
AWS S3 Ingestion identifies this file when the file name starts with "IBANPLUS". 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.

Mapping Definition

Iban Plus Directory Mappings

Iban Structure V2 property Iban Structure property Comment

modification_flag

modificationFlag

iban_bic

ibanBic

iban_iso_country_code

ibanIsoCountryCode

iso_country_code

isoCountryCode

iban_national_id

ibanNationalId

institution_name

institutionName

routing_bic

routingBic

service_context

serviceContext

Example Mappings

Source Record from Industry file

MODIFICATION FLAG	RECORD KEY	INSTITUTION NAME	COUNTRY NAME	ISO COUNTRY CODE	IBAN ISO COUNTRY CODE	IBAN BIC	ROUTING BIC	IBAN NATIONAL ID	SERVICE CONTEXT	FIELD A	FIELD B
A	IB0000000001	MoraBanc	ANDORRA	AD	AD	BINAADADXXX	BINAADADXXX	00070014	SEPA

Destination Record IBANPLus

{
  "modificationFlag": "A",
  "ibanBic": "BINAADADXXX",
  "ibanIsoCountryCode": "AD",
  "isoCountryCode": "AD",
  "ibanNationalId": "00070014",
  "institutionName": "MoraBanc",
  "routingBic": "BINAADADXXX",
  "serviceContext": null
}

Searchable Fields

Searchable fields for IBAN Plus Settings are:

  • ibanBic

  • institutionName

  • ibanIsoCountryCode

  • isoCountryCode

  • ibanNationalId

  • routingBic

  • serviceContext

Indexes

DPS v2 provides an option to configure indexes for each setting. Default indexes for IBAN Plus Settings are:

ipf.dps.mongodb.index-config.ibanplus {
    index-1 = ["status:ASC"]
    index-2 = ["processingEntity:ASC"]
    index-3 = ["values.payload.ibanIsoCountryCode:ASC"]
    index-4 = ["values.payload.isoCountryCode:ASC"]
    index-5 = ["values.payload.ibanNationalId:ASC"]
    index-6 = ["payload.ibanIsoCountryCode:ASC"]
    index-7 = ["payload.isoCountryCode:ASC"]
    index-8 = ["payload.ibanNationalId:ASC"]
    index-9 = ["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.iban-plus-settings = false

History

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

ipf.csm-reachability.should-save-history.iban-plus-settings = true