SWIFTRef File Support
Background
IPF supports ingestion of files from SWIFT (provided through subscriptions to SWIFTRef by client implementations). SWIFT API products for reference data are not supported. Client implementations must subscribe to relevant SWIFTRef products to secure the files required for relevant IPF functionality and ingest the files using supported ingestion mechanisms. (Refer File Ingestion)
SWIFT have announced that the legacy SWIFTRef portfolio of file products it offers will be decommissioned by November 2026. The legacy portfolio will be replaced by new file products from SWIFT. Below are relevant files that are applicable for IPF CSM Reachability.
Legacy SWIFTRef Portfolio |
Legacy SWIFTRef Portfolio |
Bank Directory Plus IBAN Plus IBAN Structure Exclusion List BIC Directory 2018 |
Identifiers All FORMATS-ALL FORMATS-CTRY |
IPF will support ingestion of legacy SWIFTRef portfolio files and their use on CSM Reachability functions until November 2026 (SWIFT mandated deadline). While retaining the support to the legacy portfolio, support for evolved SWIFTRef portfolio has been introduced on IPF. While files from legacy and evolved portfolio can be ingested independently of each other, the use of the data ingested through respective portfolio for functions on CSM Reachability is driven by a new configuration introduced on IPF (swift-ref-version).
Config Driven Functionality
The config swift-ref-version will have the default value of "legacyPortfolio" so the existing clients that use these features can continue using the data populated through ingestion of legacy files. Any clients that want to move to use the evolved portfolio can change the config value to "evolvedPortfolio" so the data populated from evolved portfolio files can be used for the functions.
The features that are dependent on the config value are (Refer the configuration on application.conf):
-
- NOTE
-
IBAN deconstruct is used internally by other CSM reachability functions that support the use of IBANs on input request.
Legacy Portfolio Support
Below files from the legacy portfolio are supported on IPF to provide reachability specific functions.
| File | Destination Dynamic Configuration | Function | Comments |
|---|---|---|---|
Bank Directory Plus |
Party Entity Directory |
Other CSM Reachability functions use party entity look up internally to provide industry data look up capability |
|
IBAN Plus |
IBAN Plus |
Other CSM Reachability functions use IBAN deconstruct to provide IBAN deconstruction capability |
|
IBAN Structure |
IBAN Structure |
Other CSM Reachability functions use IBAN deconstruct to provide IBAN deconstruction capability |
|
Exclusion List |
Exclusion List |
Other CSM Reachability functions use IBAN deconstruct to provide IBAN deconstruction capability |
|
BIC Directory 2018 |
BicDir2018 |
Evolved SWIFTRef Portfolio Support
Below files from the evolved portfolio are supported on IPF to provide reachability specific functions.
| File | Destination Dynamic Configuration | Function | Comments |
|---|---|---|---|
Identifiers All |
Party Entity Directory |
Other CSM Reachability functions use party entity look up and IBAN deconstruct internally to provide industry data look up capability |
|
FORMATS-CTRY |
IBAN Structure |
Other CSM Reachability functions use IBAN deconstruct to provide IBAN deconstruction capability. |
|
FORMATS-ALL |
IBAN Structure |
Other CSM Reachability functions use IBAN deconstruct to provide IBAN deconstruction capability. |
- NOTE
-
FORMATS-ALL is provided through "Payments Directory" and FORMATS-CTRY is provided through "Identifiers Directory". Based on the SWIFTRef subscriptions, any one of these files can be used to achieve the required functionality.
Client Recommendations
Below are some key recommendations for client implementations who wish to use the SWIFTRef portfolio files on IPF.
| # | Recommendation | Comment |
|---|---|---|
1 |
Client implementations must plan ahead and move to use the evolved SWIFTRef portfolio on their LIVE implementation ahead of the legacy portfolio decommissioning date of November 2026 |
|
2 |
It is highly recommended that client implementations carry out thorough testing of CSM Reachability functions using full versions of the evolved portfolio files on the test systems. |
The feature development has been done using the sample files and the specifications provide by SWIFT. Though the confidence levels on the solution are high, it is possible that full files may provide data variability not captured through sample files and some minor adjustments may be needed to the functionality. |
3 |
Client implementations must ingest full versions of the evolved portfolio files before enabling the configurations to use the data on CSM Reachability functions through configurations. |
|
4 |
Client implementations must ingest the ZIP version of the Identifiers All file when ingesting the full file. (Full file can be significantly large and ingesting unzipped xml can lead to failures). |
FORMATS files and the identifiers-All delta files can be unzipped xml files. But client implementations may want to use the ZIP versions on all files for consistency purposes. |
5 |
Client implementations can subscribe to daily delta or monthly delta frequencies of the files. The files should be ingested as per the frequency subscribed (daily delta and monthly delta should not be mixed and matched). |
A change from daily to monthly (or vise versa) must be separated by a full file ingestion. |
6 |
After switching to use the evolved portfolio, client implementations can clear data from below dynamic configuration collections (provided they don’t intend to switch back to legacy portfolio). a) IBAN Plus b) Exclusion List c) BIC Dir 2018 d) Party Entity Directory (Bank Directory Plus only) |
|
7 |
Client implementations must not modify the file names before ingesting them on IPF. |
|
8 |
IPF does not scan the ingested files for threats. It is recommended that client implementations carry out required threat / virus scanning of the files when received from the industry source. |