SWIFTRef Reach Plus

Technical Specifications

These technical specifications describe the SWIFTRef Reach Plus files. Financial institutions use these files to look up
information related to clearing and settlement systems and SWIFTNet and FIN services, and to decide on payment
routing options when sending payments to the counterparties. This document is intended for anyone who installs and
administers the SWIFTRef Reach Plus files.

28 February 2020

Link to this document: https://www2.swift.com/go/book/book156411

SWIFTRef Reach Plus Table of Contents
Technical Specifications

Table of Contents

Preface............................................................................................................................................................... 4

1 About SWIFTRef Reach Plus..................................................................................................................5

1.1 Purpose of SWIFTRef Reach Plus.......................................................................................................... 5
1.2 Files in SWIFTRef Reach Plus................................................................................................................ 5

2 About the SWIFTRef Reach Plus Files.................................................................................................. 7

2.1 SWIFTRef Reach Plus File Formats........................................................................................................7
2.2 Daily and Monthly File Distribution.......................................................................................................... 7
2.3 SWIFTRef Reach Plus File Naming Convention..................................................................................... 9
2.4 SWIFTRef Reach Plus File Names........................................................................................................11
2.5 Downloading and Importing SWIFTRef Files.........................................................................................13
2.6 SWIFTRef Release Letter and Support................................................................................................. 14

3 PMI_V1 File.............................................................................................................................................16
3.1 Overview of the PMI Data File............................................................................................................... 16
3.2 PMI Data File Field Definitions.............................................................................................................. 16
3.3 PMI Sample File.................................................................................................................................... 20

4 REACHPLUS_V1 File.............................................................................................................................21
4.1 Overview of REACHPLUS Data File..................................................................................................... 21
4.2 REACHPLUS Data File Field Definitions...............................................................................................21
4.3 REACHPLUS Sample Files................................................................................................................... 23

5 REACHPLUSSTRUCTURE_V1 File...................................................................................................... 24
5.1 Overview of the REACHPLUSSTRUCTURE File..................................................................................24
5.2 REACHPLUSSTRUCTURE File Field Definitions................................................................................. 24
5.3 REACHPLUSSTRUCTURE Sample Files.............................................................................................25

Appendix A Fields and Flags for SWIFTRef Files....................................................................................... 26

A.1 MODIFICATION FLAG Field in SWIFTRef Files..............................................................................................26

Appendix B Publication Date and Validity Date for SWIFTRef Files......................................................... 27

B.1 Applicable Dates for SWIFTRef Reach Plus Data........................................................................................... 27

Appendix C Services......................................................................................................................................28
C.1 Payment Services and Market Infrastructures................................................................................................. 28

28 February 2020 2
SWIFTRef Reach Plus Table of Contents
Technical Specifications

C.2 SWIFTNet Services......................................................................................................................................... 28

C.3 SWIFT FINCopy Services................................................................................................................................29
C.4 SWIFTgpi Service............................................................................................................................................29

Appendix D Guidelines to Use the Reach Plus Files.................................................................................. 30

D.1 The Files.......................................................................................................................................................... 30
D.2 Links Between the Files...................................................................................................................................30
D.3 Importing Data into Your Application................................................................................................................32
D.4 Standardised Field Names...............................................................................................................................32
D.5 Restricted List of Attributes..............................................................................................................................35

Legal Notices................................................................................................................................................... 36

28 February 2020 3
SWIFTRef Reach Plus Preface
Technical Specifications

Preface
Purpose of the document
These technical specifications describe the SWIFTRef Reach Plus files. Financial institutions use
these files to look up information related to clearing and settlement systems and SWIFTNet and
FIN services, and to decide on payment routing options when sending payments to the
counterparties.
Note In this document, the SWIFTRef Reach Plus product name is occasionally shortened
to Reach Plus.

Audience
This document is intended for anyone who installs and administers the SWIFTRef Reach Plus files.

Significant changes
These tables list all significant changes to the content of the SWIFTRef Reach Plus Technical
Specifications since the following previous editions. These tables do not include editorial changes
that SWIFT makes to improve the usability and comprehension of the document.

Updated information since the 10 January 2020 Location

edition

ALTERNATIVE SERVICE IDs description PMI Data File Field Definitions on page 16

New information since the 06 December 2019 Location

edition

Guidelines to use the Reach Plus files The Files on page 30

Links Between the Files on page 30
Importing Data into Your Application on page 32
Standardised Field Names on page 32
Restricted List of Attributes on page 35

Updated information since the 25 October 2019 Location

edition

Information about the PMI_V1 file field definitions has PMI Data File Field Definitions on page 16
been updated.
Overview of the PMI Data File on page 16

Related documentation
• Directories over FileAct Implementation Guidelines
• Frequently Asked Questions for SWIFTRef Users
• Publication Schedule and Distribution Information
• SWIFTRef Automated Download Service Technical Specifications
• SWIFTRef Release Letter (sent by e-mail every month to all SWIFTRef data file subscribers,
including SWIFTRef Reach Plus subscribers)

28 February 2020 4
SWIFTRef Reach Plus About SWIFTRef Reach Plus
Technical Specifications

1 About SWIFTRef Reach Plus

1.1 Purpose of SWIFTRef Reach Plus

Financial institutions use the data in the SWIFTRef Reach Plus files to do the following:
• get an overview of payment services throughout the world
• look up the participants of a payment service
• look up the necessary parameters such as identifiers and participant roles to send payments to
participants through the services
The Reach Plus files also contain financial institutions' participation in SWIFTNet services and
SWIFT FIN services.
The services covered in the Reach Plus files are related to payments. They include RTGS
systems, ACHes, cheque clearing systems, and real-time instant payment systems. Services for
other types of business such as loans, remittances, money markets, derivatives, and systems that
are based on mobile phones and ATMs as end points are not included.
The number of services covered in Reach Plus will grow over time. SWIFTRef Reach Plus has
superseded the legacy Service Directory file, which is a part of the Bank Directory Plus product.
SWIFTRef Reach Plus is a stand-alone product and is not a part of the Bank Directory Plus
product. SWIFTRef Reach Plus files are also included in the Payments Plus product and in the
Corporate Pack Three.

1.2 Files in SWIFTRef Reach Plus

The SWIFTRef Reach Plus product contains three related files: the PMI file, the REACHPLUS file,
and the REACHPLUSSTRUCTURE file.
• PMI file
This file contains the list of Payment Services and their basic attributes, such as the service
name, transaction value (low/high), execution time (real-time, same day, deferred, and others),
the currency cleared, and the type of settlement (net or gross). One record in the PMI file
represents one Payment Service. New records are added monthly.
• REACHPLUS file
This file contains, per Payment Service, the list of participants. For each participant, the file
displays the participant name, its identifier used in the system, any particular role the participant
has in the system, and additional attributes. The link between the PMI file and the REACHPLUS
file is the SERVICE ID field.
• REACHPLUSSTRUCTURE file
Because the data attributes in the REACHPLUS file can be different per Payment Service, this
file contains the data definitions of the attributes (metadata file). The link between the
REACHPLUS file and its data definitions is the PLATFORM field. This is the identifier of the
single data definition set of records in the REACHPLUSSTRUCTURE file.

28 February 2020 5
SWIFTRef Reach Plus About SWIFTRef Reach Plus
Technical Specifications

Payment Services
(PMI file)

SERVICE ID

Payment Service Participants Link to Bank

(REACHPLUS file) Directory Plus

PLATFORM

Payment Service Participants

D1990001
Data Definitions
(REACHPLUSSTRUCTURE file)

28 February 2020 6
SWIFTRef Reach Plus About the SWIFTRef Reach Plus Files
Technical Specifications

2 About the SWIFTRef Reach Plus Files

2.1 SWIFTRef Reach Plus File Formats

UTF-8 format
The files are encoded in the UTF-8 format.

TXT files
The text files are structured as follows:
• Line separator: CR/LF
• Field separator: Tab character
• File extension: .txt

XML files
The root node of the XML is <dataexport> which contains three mandatory attributes:
• product
the name of the product and the row node
• filetype
whether it is a full file or a delta file
• filedate
date of the file in the format <YYYYMMDD>
For example, <dataexport product="reachplus_v1" filetype="full"
filedate="20160325">.

Inside the root node, rows are enclosed in the product node, for example,
reachplusdirectory_v1. Each product node contains one TAG for each available column. Empty
TAGs are not included.
The following rules apply to the TAG names:
• underscore ("_") replaces blanks (" ")
• uppercase characters are converted lowercase
For example, "ISO COUNTRY CODE" becomes <iso_country_code>.
An XSD (XML Schema Definition) included as a separate xsd file, formally describes the elements
in the XML document. Use this file to verify that each item in the content adheres to its description.

2.2 Daily and Monthly File Distribution

Overview
SWIFTRef products consist of a set of files that are compressed in a zip package.
Users can receive the files on a daily or a monthly basis. The distribution mechanisms are identical.
You can find more information about the daily download service on www.swift.com/swiftref >
About SWIFTRef > Distribution channels.

28 February 2020 7
SWIFTRef Reach Plus About the SWIFTRef Reach Plus Files
Technical Specifications

An additional subscription, access, and fee for the daily files apply.
The daily and the monthly cycle files are not interchangeable. Users must select and continue to
use the same update frequency. Switching from one frequency to the other can only be done
exceptionally by loading the full file of the new frequency.

Differences in RECORD KEYs in daily and monthly files

For more information about the differences in RECORD KEYS in daily and monthly files, see the
Publication Schedule and Distribution Information.

Daily cycle files

To keep data consistent, all daily files must be applied in the correct order (by date in the file
name). SWIFT suggests the customer implements a daily delta file counter, using dates, so that the
counter automatically detects if a file has been missed out or applied in an incorrect sequence. The
counter must also count empty daily delta files.
The daily files do not necessarily need to be applied once per day. They can be accumulated and
then applied in a single batch in the correct order. For example, if you want to apply the daily files
on a weekly basis, then on 15 June you apply the files of 8, 9, 10, 11, 12, 13 and 14 June in this
order.
Alternatively, if you prefer to keep your monthly update process, then you can apply 30 or 31 daily
updates at the end of each month in one go. The benefit of this, in comparison to applying one
monthly delta file, is that if there is an urgent data fix made throughout the month, you already have
the related update in one of the daily deltas. You only need to apply all outstanding daily deltas
immediately to have the data fixed. Subscribers to the monthly updates do not have such fixes
available on time.
Note If you have access to the daily files, then you can also keep access to the monthly
files. Some back-office systems may use daily data and other systems may use
monthly data.

Type of file Description Frequency Availability

Daily full file The daily full file is only required for Published once a month For daily publications, the
an optional data resynchronisation. deliveries of all SWIFTRef
directories are available at
The daily full file is published as a
02:00 GMT. Deliveries over
separate file along with the daily
FileAct will take longer, but
delta. The daily full and daily delta
will be delivered no later than
files are published one day after the
07:00 GMT.
date mentioned in the file name.
Note The daily full
file is published
once a month.
Even if the file
name is defined
with "daily", it is
a monthly
publication.

28 February 2020 8
SWIFTRef Reach Plus About the SWIFTRef Reach Plus Files
Technical Specifications

Type of file Description Frequency Availability

Daily delta file This file contains only the changes of Published every day, For daily publications, the
the previous day. For example, on 04 including the weekends deliveries of all SWIFTRef
November 2015 beginning at 02:00 directories are available at
GMT, SWIFTRef provides the daily 02:00 GMT. Deliveries over
files with file date 20151103. To FileAct will take longer, but
download this file, select 03 Nov will be delivered no later than
2015 in the Date Selector. 05:00 GMT.
For more information, see Frequently
Asked Questions for SWIFTRef
Users.

The daily files contain updates for immediate use and not for future use.

Monthly cycle files

Type of file Description Frequency Availability

Monthly full file One delta file and one full file, Published once a month For daily publications, the
published on the same day. (That is, deliveries of all SWIFTRef
Monthly delta file
on the date mentioned in the file directories are available at
name.) 02:00 GMT. Deliveries over
FileAct will take longer, but
Users can apply the delta files only,
will be delivered no later than
the full files only, or a mix of the two
07:00 GMT.
(but not in the same month).

Related information
SWIFTRef Reach Plus File Naming Convention on page 9
SWIFTRef Reach Plus File Names on page 11
Publication Schedule and Distribution Information

2.3 SWIFTRef Reach Plus File Naming Convention

2.3.1 Monthly Update File Naming Convention

This section describes the file naming convention for SWIFTRef monthly files.
<directory_filename>_<version>_<filetype>_<date>.<format>

Variable Description

<directory_filename> The name of the directory file

<version> The version of the file

28 February 2020 9
SWIFTRef Reach Plus About the SWIFTRef Reach Plus Files
Technical Specifications

Variable Description

<filetype> • FULL
The file is published once a month and contains all data, whether the data has changed
or not. It is compatible with the DELTA files and serves the purpose of resynchronising
your database with SWIFT's database.
• DELTA
The file is published once a month and only contains the data modified, added, or
deleted relative to the previous month.

<date> <YYYYMMDD> format

The publication date and the activation date of the file

<format> .txt or .xml (see SWIFTRef Reach Plus File Formats on page 7)

Related information
Monthly File Names on page 11

2.3.2 Daily Update File Naming Convention

This section describes the file naming convention for SWIFTRef daily files.
<directory_filename>_<version>_<filetype>_<date>.<format>

Variable Description

<directory_filename> The name of the directory file

<version> The version of the file

<filetype> • FULL
This file is published once a month and contains all data, whether the data has changed
or not. It is compatible with the daily DELTA files and serves the purpose of
resynchronising your data base with SWIFT's database. It is different from, and not
compatible with the monthly cycle FULL and DELTA files.
• DELTA
This file is published once a day and contains the changes of the day specified in the file
name. It also includes any emergency changes, therefore correction files are not
needed. It is published each single day, including the week-ends. It may be empty if no
change occurred.

<date> <YYYYMMDD> format

The publication date and the activation date of the file
The daily files contain updates for immediate use and not for future use.

<format> .txt or .xml (see SWIFTRef Reach Plus File Formats on page 7)

Note FIX and UNDO files do not exist in a daily update cycle.

28 February 2020 10
SWIFTRef Reach Plus About the SWIFTRef Reach Plus Files
Technical Specifications

2.4 SWIFTRef Reach Plus File Names

2.4.1 Monthly File Names

This section lists the data files included in the SWIFTRef Reach Plus zip archive file, related to the
monthly update cycle. All files are produced once per month.

.txt files .xml files

PMI_V1_MONTHLY_FULL_<YYYYMMDD>.txt PMI_V1_MONTHLY_FULL_<YYYYMMDD>.xml

PMI_V1_MONTHLY_DELTA_<YYYYMMDD>.txt PMI_V1_MONTHLY_DELTA_<YYYYMMDD>.xml

REACHPLUS_V1_DELTA_<YYYYMMDD>.txt REACHPLUS_V1_DELTA_<YYYYMMDD>.xml

REACHPLUS_V1_FULL_<YYYYMMDD>.txt REACHPLUS_V1_FULL_<YYYYMMDD>.xml

REACHPLUSSTRUCTURE_V1_DELTA_<YYYYMMDD>.txt REACHPLUSSTRUCTURE_V1_DELTA_<YYYYMMDD>.xml

REACHPLUSSTRUCTURE_V1_FULL_<YYYYMMDD>.txt REACHPLUSSTRUCTURE_V1_FULL_<YYYYMMDD>.xml

EULA.txt EULA.txt

sha256sum.txt sha256sum.txt

• EULA.txt
This file is included in all downloadable file packages. This file provides information about
SWIFTRef Terms and Conditions. For more information, see the SWIFTRef Products Terms and
Conditions.
• sha256sum.txt
The Secure Hash Algorithm (SHA) validates the integrity of SWIFTRef files. The SHA256
algorithm generates an almost-unique, fixed size 256-bit (64-byte) hash.

2.4.2 Monthly File Zip Archives

The monthly data files are downloadable (manually or automatically) as one set of files from
www.swiftrefdata.com > Download Area within the following zip archive:

.txt files .xml files

REACHPLUS_<YYYYMMDD>_TXT.zip REACHPLUS_<YYYYMMDD>_XML.zip

You can also download the data files individually in their own dedicated zip archive files. The zip
archive file names are not displayed in these technical specifications.
Note The Automated Download Service is a payable service.
The data files can also be received as a single set of files through the Directories Over FileAct
(DOFA) service in the following archive file:

28 February 2020 11
SWIFTRef Reach Plus About the SWIFTRef Reach Plus Files
Technical Specifications

.txt files .xml files

REACHPLUS_<YYYYMMDD>_TXT.zip REACHPLUS_<YYYYMMDD>_XML.zip

You can also receive the data files through DOFA individually in their own dedicated zip archive
files. The zip archive file names are not displayed in these technical specifications. To receive the
files individually through DOFA, select them in the e-order form. By default, the reception of the
entire data file set zip archive is configured.
Note Receiving files through DOFA is a payable service.

2.4.3 Daily File Names

This section lists the data files included in the SWIFTRef Reach Plus zip archive file, related to the
daily update cycle. The zip archives are produced daily. Inside the zip files, the data files that
contain "DELTA" in the file name are included daily. The files that contain "FULL" or without any
indication of "FULL" or "DELTA" in the file name are included only once per month. The files
contain updates for immediate use and not for future use.
The DAILY_FULL file is provided as a separate file once a month, one day after the monthly
publication date.

.txt files .xml files

PMI_V1_DAILY_FULL_<YYYYMMDD>.txt PMI_V1_DAILY_FULL_<YYYYMMDD>.xml

PMI_V1_DAILY_DELTA_<YYYYMMDD>.txt PMI_V1_DAILY_DELTA_<YYYYMMDD>.xml

REACHPLUS_V1_DAILY_DELTA_<YYYYMMDD>.txt REACHPLUS_V1_DAILY_DELTA_<YYYYMMDD>.xml

REACHPLUS_V1_DAILY_FULL_<YYYYMMDD>.txt REACHPLUS_V1_DAILY_FULL_<YYYYMMDD>.xml

REACHPLUSSTRUCTURE_V1_DAILY_DELTA_<YYYYMMD REACHPLUSSTRUCTURE_V1_DAILY_DELTA_<YYYYMMD
D>.txt D>.xml

REACHPLUSSTRUCTURE_V1_DAILY_FULL_<YYYYMMDD REACHPLUSSTRUCTURE_V1_DAILY_FULL_<YYYYMMDD
>.txt >.xml

EULA.txt EULA.txt

sha256sum.txt sha256sum.txt

• EULA.txt
This file is included in all downloadable file packages. This file provides information about
SWIFTRef Terms and Conditions. For more information, see the SWIFTRef Products Terms and
Conditions.
• sha256sum.txt
The Secure Hash Algorithm (SHA) validates the integrity of SWIFTRef files. The SHA256
algorithm generates an almost-unique, fixed size 256-bit (64-byte) hash.

28 February 2020 12
SWIFTRef Reach Plus About the SWIFTRef Reach Plus Files
Technical Specifications

2.4.4 Daily File Zip Archives

The daily data files are downloadable (manually or automatically) as one set of files from
www.swiftrefdata.com > Download Area within the following zip archive:

.txt files .xml files

REACHPLUS_DAILY_<YYYYMMDD>_TXT.zip REACHPLUS_DAILY_<YYYYMMDD>_XML.zip

You can also download the data files individually in their own dedicated zip archive files. The zip
archive file names are not displayed in these technical specifications.
Note The Automated Download Service is a payable service.
The data files can also be received as a single set of files through the Directories Over FileAct
(DOFA) service in the following archive file:

.txt files .xml files

REACHPLUS_DAILY_<YYYYMMDD>_TXT.zip REACHPLUS_DAILY_<YYYYMMDD>_XML.zip

You can also receive the data files through DOFA individually in their own dedicated zip archive
files. The zip archive file names are not displayed in these technical specifications. To receive the
files individually through DOFA, select them in the e-order form. By default, the reception of the
entire data file set zip archive is configured.
Note Receiving files through DOFA is a payable service.

2.5 Downloading and Importing SWIFTRef Files

Downloading files
File download option More information How to order

Manual download from Frequently Asked Questions - For 1. Go to the ordering pages on www.swift.com.
www.swiftrefdata.com by SWIFTRef Users
2. Click Place orders , then select the desired
authorised users
product. Complete the order form (login to
swift.com required).
3. Under Files products types, select the product
from the drop-down list. Under Distribution
options, select Manual download from the
drop-down list.

Automated Download Service SWIFTRef Automated Download 1. Go to the ordering pages on www.swift.com.
Service Technical Specifications
2. Click Place orders , then select the desired
product. Complete the order form (login to
swift.com required).
3. Under Files products types, select the product
from the drop-down list. Under Distribution
options, select Download automation from the
drop-down list.

28 February 2020 13
SWIFTRef Reach Plus About the SWIFTRef Reach Plus Files
Technical Specifications

File download option More information How to order

Directories Over FileAct Directories Over FileAct 1. Go to the ordering pages on www.swift.com.
Implementation Guidelines
2. Click Place orders , then select Subscribe (Test)
or Subscribe (Live) .
3. Complete the subscription/change form as
appropriate (login to swift.com required).

Principles for importing data into a target database

There are two ways to import data:

Situation Solution

File and destination table are both UTF-8 Directly import the file without changing parameters

File is UTF-8 and destination table is not UTF-8 Specify during the import that the encoding of the file
is UTF8. That way the system knows that the
characters must be read in UTF-8.
If you do not specify the encoding of the file, then the
system will try to import the file using the destination
table encoding. The characters will be read in the
wrong way and will be replaced by incorrect
characters.

Importing files
The files can be imported into:
• Your target application and databases. The TXT files must be translated into the EBCDIC format
for import into IBM systems.
• Microsoft Excel (if size allows) or Microsoft Access - for desktop consultation. Format the Excel
sheet as text before importing the file to preserve leading zeros ("0").
To import into Microsoft Excel, do the following:
1. Select the entire sheet.
2. Format it as text.
3. Import the data with: Data > From text.
4. Select TAB-delimited Unicode (UTF-8) format for all columns.

2.6 SWIFTRef Release Letter and Support

Release Letter
For the users of the SWIFTRef files, SWIFT publishes the monthly SWIFTRef Release Letter that
describes all significant additions, changes, and corrections to the SWIFTRef files. The SWIFTRef
Release Letter is e-mailed automatically to all users with a subscription to file download. The
SWIFTRef Release Letter is published approximately one week before the file publication date.
If you want to receive the monthly SWIFTRef Release Letter through e-mail, then register on
mySWIFT.

28 February 2020 14
SWIFTRef Reach Plus About the SWIFTRef Reach Plus Files
Technical Specifications

Support
SWIFT Customer Support provides documentation and the Knowledge Base to help customers find
information.
If you do not find the information that you are looking for, then contact Support:
• You are registered for SWIFT Support
Create a support case: Log in to the Case Manager.
• You are not registered for SWIFT Support
If you have a BIC, then log in to www.swift.com. Under Profiles, click Request Accesses >
Support applications. If you do not have a BIC or you do not know your BIC, then contact the
SWIFTRef administrator of your institution.

Type of support Contact information

SWIFTRef data content and operational Log in to Ordering & Support.

issues:
• Documentation (User Handbook)
• data issues
• How-to videos
• directory publication issues
• Knowledge base
• directory file queries
• Case Manager
• website application errors
• identity and access management

SWIFTRef sales enquiries Send an e-mail to [email protected]

Customers can find more information about Reference Data products on www.swift.com/swiftref.

28 February 2020 15
SWIFTRef Reach Plus PMI_V1 File
Technical Specifications

3 PMI_V1 File

3.1 Overview of the PMI Data File

The PMI file contains a list of domestic and international clearing and settlement services (also
called payment services, payment systems, or payment market infrastructures) such as ACH,
cheque clearing systems, real-time retail payment systems, and RTGS systems. Eventually, the list
will be global. The PMI file does not contain the list of services that are listed in the REACHPLUS
file under PLATFORM as "SNET" and "SNETFIN", as these are not single PMIs, but include entire
groups of PMIs. They have a common PLATFORM because, as they are not hosted on SWIFTNet
and SWIFTNet FIN, their parameters are similar. However, some of these services can be listed
individually under their own SERVICE ID in the PMI, the REACHPLUS, and the
REACHPLUSSTRUCTURE files.
The PMI file does not contain person-to-person mobile phone number-based services, services
using ATMs for the payout, remittance services, or services in the area of money markets and
securities.
For an increasing number of these services, the REACHPLUS file contains the list of the
participants. The data element that links the payment services in the PMI file and the participant list
in the REACHPLUS file is the SERVICE ID.

3.2 PMI Data File Field Definitions

Field name Data Type Maximum Always Description
length present

MODIFICATION FLAG Alphabetic 1 Yes Modification flag, in delta files:

• A (addition)
• M (modification)
• D (deletion)
In full files:
• A (addition)
For more information, see Fields and Flags
for SWIFTRef Files on page 26.

SERVICE ID Character 20 Yes The acronym of the clearing and settlement

service, or the SWIFTNet service. It is
usually prefixed with the ISO country code or
the AREA code, which represents the land/
area where the service is offered.
Example: "CN CIPS" or "SADC SIRESS"
The same SERVICE ID is also used in the
REACHPLUS file to identify all participants of
the service.

SERVICE NAME Character 105 Yes The name of the payment service.

28 February 2020 16
SWIFTRef Reach Plus PMI_V1 File
Technical Specifications

Field name Data Type Maximum Always Description

length present

ALTERNATIVE SERVICE IDS Character 200 No The various alternative IDs are prefixed as
follows:
• ISO3: the 3-digit ISO clearing and
settlement service code
• ISO5: the 5-digit ISO clearing and
settlement service code
• FIN: the FIN service (VAS) code
The prefix and the alternative ID are
separated by ":". The prefix/alternative ID
pairs are comma-separated (if multiple).

CURRENCY CODES Character 80 No (for The comma-separated list of currency codes

SNET cleared or settled on the service.
platform)
Yes (for
others)

SERVICE TYPE Character 50 No If applicable, one of the following:

• ACH - automated clearing house
• CHQ - cheque clearing system
• RTGS - real-time gross settlement
• RT-RPS - real-time retail payments
service
Other services that are not in these
categories have this field empty.

AREA Character 200 No One country code, or a list of countries, at

times defining an official group of countries in
which the service is made available.

COVERAGE Character 13 No The reach/coverage the service provides.

One of the following:
• domestic
• regional
• international

HIGH LOW VALUE Character 5 No The value of the transactions. One of the
following:
• HV - high value
• LV - low value
• HV/LV - high and low value

28 February 2020 17
SWIFTRef Reach Plus PMI_V1 File
Technical Specifications

Field name Data Type Maximum Always Description

length present

GROSS NET SETTLEMENT Character 2 No The type of settlement. One of the following:
• GS - gross settlement. Each transaction
is settled individually.
• NS - net settlement. The transactions are
aggregated and settled in batch as net
differences in amounts.

EXECUTION DELAY Character 2 No The maximum period necessary to execute

the transaction. One of the following:
• RT - real-time or instant
• nH - a number of hours (for example, 2H)
• n min - a number of minutes
• n sec - a number of seconds
• SD - same day
• DF - deferred, can take one or several
days

TRANSACTION TYPE Character 150 No The type of transaction. One or a comma-

separated combination of the following:
• CQ - cheque transfer
• CT - credit transfer
• DT - debit transfer
• DD - direct debit
• IB - inter-bank transfer
Additional types may be added in the future.

PARTICIPANT ID TYPE Character 50 No The type of identifier of the participant of the

service. In most cases, it will either be a
SWIFT BIC or a domestic routing/clearing
number (with or without the branch code).
These have a dedicated name in the related
Bank Directory Plus file called the NATIONAL
ID TYPE.
Examples: "ABA", "CNAPS", "BLZ"

ISO MESSAGE FORMAT an 50 No The ISO standards ID(s) for the type of
messages used by the service.
Examples: ISO15022 (as used in the FIN
MTs), ISO20022, ISO8583.

SERVICE LOCAL START HH:MM+HH:MM 11 No The local time + UCT offset of the start of the
TIME daily operations of the service.
Example: 08:30+03:00

SERVICE LOCAL CUT-OFF HH:MM+HH:MM 11 No The local time + UCT offset of the
TIME acceptance of the last transaction by the
service.

28 February 2020 18
SWIFTRef Reach Plus PMI_V1 File
Technical Specifications

Field name Data Type Maximum Always Description

length present

OPERATING DAYS Character 27 No A range of days (in acronyms) during which

the service is operational.
Example: MON-FRI

TECHNICAL NAME Character 150 No A technical name of the service. This is

mainly used for services on SWIFTNet
(SNET).
Example: swift.bulkp.generic.rt

NETWORKS Character 150 No The network(s) through which the service is

provided.
Example: “SWIFT FIN” is the network that
enables the BISS RTGS system of
Botswana.

SETTLEMENT SERVICE ID Character 20 No The Service ID of the service that provides

the settlement for this clearing service.
Example: “BW BLISS” is the RTGS service in
Botswana that provides settlement services
to the “BW BACH” ACH service.

PLATFORM Character 20 No The identifier of the data structure (field

definition) of the service participant records,
which are available in the REACHPLUS file.
The data structure is defined in the
REACHPLUSSTRUCTURE file and defines
the meaning and size of the columns that
contain the participant data in the
REACHPLUS file.
Filtering the REACHPLUSSTRUCTURE
records on PLATFORM will return the data
specification for a service.
Example: Filtering the
REACHPLUSSTRUCTURE records on
PLATFORM = “FEDWIRE” will list the data
definition of the FedWire participant records
in the REACHPLUS file.

OPERATOR COMPANY Character 150 No The legal name of the company that operates
the service.
Example: Transfond S.A.

OPERATOR COUNTRY Character 2 No The ISO country code of the operator.

CODE
It remains blank if the operator operates from
multiple countries. This is not to be confused
with AREA, which specifies the countries
where the service is provided.

NOTES Character 255 Additional notes to the service.

28 February 2020 19
SWIFTRef Reach Plus PMI_V1 File
Technical Specifications

Field name Data Type Maximum Always Description

length present

FIELD A Character 1 No Spare field, not used. In the future, data may
be added to this column.

FIELD B Character 8 No Spare field, not used. In the future, data may
be added to this column.

FIELD C Character 11 No Spare field, not used. In the future, data may
be added to this column.

FIELD D Character 100 No Spare field, not used. In the future, data may
be added to this column.

FIELD E Character 255 No Spare field, not used. In the future, data may
be added to this column.

FIELD F Character 600 No Spare field, not used. In the future, data may
be added to this column.

3.3 PMI Sample File

The sample file includes records that illustrate the PMI Service data and is structured in the PMI
file. The PMI_V1_SAMPLE.TXT Sample File is available on the SWIFT Knowledge Centre.
You can import the files into Microsoft Excel.

28 February 2020 20
SWIFTRef Reach Plus REACHPLUS_V1 File
Technical Specifications

4 REACHPLUS_V1 File

4.1 Overview of REACHPLUS Data File

The REACHPLUS data file contains the participation and the routing data for payment services
provided by national and international payment infrastructures and by SWIFT. For a list of payment
services, see Services on page 28.

4.2 REACHPLUS Data File Field Definitions

Field name Data Type Maximum Always Description
length present

MODIFICATION FLAG Alphabetic 1 Yes Modification flag, in delta files:

• A (addition)
• M (modification)
• D (deletion)
In full files:
• A (addition)
For more information, see Fields and Flags
for SWIFTRef Files on page 26.

RECORD KEY Alphanumeric 12 Yes The unique key of the record in the file.
The RECORD KEYs in the REACHPLUS file
always start with "RP".
For more information, see "Record Keys" on
page 18.

BDP RECORD KEY Alphanumeric 12 No The record key of the corresponding record
in the BANKDIRECTORYPLUS file.

PLATFORM Alphanumeric 12 Yes The acronym for the platform or infrastructure

that operates one or multiple services. For
example, SWIFTNet is a platform operating
services such as Investment Funds, Cash
Reporting end Generic FileAct. All services
on a platform have a common data structure.
Therefore, there is only one set of field
definitions in the REACHPLUSSTRUCTURE
file.

SERVICE ID Character 20 Yes The acronym of the payments service on the

platform.

SERVICE NAME Character 105 Yes The name or short description of the service.

PARTICIPANT ID Character 255 Yes The ID of the direct/indirect service

participant. The ID format is specific to the
service.

28 February 2020 21
SWIFTRef Reach Plus REACHPLUS_V1 File
Technical Specifications

Field name Data Type Maximum Always Description

length present

ATTRIBUTE 1 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 2 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 3 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 4 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 5 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 6 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 7 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 8 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 9 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 10 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 11 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 12 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 13 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 14 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 15 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 16 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 17 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 18 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

28 February 2020 22
SWIFTRef Reach Plus REACHPLUS_V1 File
Technical Specifications

Field name Data Type Maximum Always Description

length present

ATTRIBUTE 19 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ATTRIBUTE 20 Character 255 No A generic attribute column containing a

service-specific parameter.(1)

ACTIVATION DATE Alphanumeric 8 No The date of activation of an added record in

case it is different from the monthly
publication date.
Format YYYYMMDD

FIELD A Alphanumeric 1 No Reserved for future use

FIELD B Alphanumeric 8 No Reserved for future use

FIELD C Character 35 No Reserved for future use

(1) For information about the specification of the parameter, see the REACHPLUSSTRUCTURE File Field Definitions on page 24 .

4.3 REACHPLUS Sample Files

The use of metadata files provides flexibility. As these files are complex, SWIFTRef provides
samples files to help customers understand how the metadata works. The
REACHPLUSSTRUCTURE_V1_SAMPLE.TXT and the REACHPLUS_V1_SAMPLE.TXT files are
available on www.swift.com/swiftref > Documentation > Products. For ease of use, you can import
these files into Microsoft Excel.

28 February 2020 23
SWIFTRef Reach Plus REACHPLUSSTRUCTURE_V1 File
Technical Specifications

5 REACHPLUSSTRUCTURE_V1 File

5.1 Overview of the REACHPLUSSTRUCTURE File

Each payment system or market infrastructure has its own variation of participation and routing
data format and structure. Fitting these different structures into one data file is a challenge. For this
purpose, the data file is complemented with a metadata file. The REACHPLUS data file contains
the participation and the routing data. The REACHPLUSSTRUCTURE file contains metadata
related to the service platform-specific structure of the data in the REACHPLUS file.
In brief, the REACHPLUSSTRUCTURE file renames the generic column names and field formats
by service-specific column names and formats.
REACHPLUSSTRUCTURE file should be used to:
• Understand the structure of the service data in the main REACHPLUS file. All data in the
REACHPLUS file is contained in standard data fields. The type, format, and meaning of the
data in the same data field can be different for each platform operating the services.
• Configure the user's database into which REACHPLUS data is imported.
• Configure the user interface of front-desk operators in which the REACHPLUS data is
displayed. This includes displaying the service platform-specific data field names.

5.2 REACHPLUSSTRUCTURE File Field Definitions

The following table contains the definitions of the fields (columns) in the
REACHPLUSSTRUCTURE file, both the full and the delta file.

Field name Data Type Maximum Always Description

length present

MODIFICATION FLAG Alphabetic 1 Yes Modification flag, in delta files::

• A (addition)
• M (modification)
• D (deletion)
In full files:
• A (addition)
For more information, see Fields and Flags
for SWIFTRef Files on page 26.

RECORD KEY Alphanumeric 12 Yes The unique key of the record in the file.
All REACHPLUSSTRUCTURE file records
start with "RS".
For more information, see "Record Keys" on
page 18.

28 February 2020 24
SWIFTRef Reach Plus REACHPLUSSTRUCTURE_V1 File
Technical Specifications

Field name Data Type Maximum Always Description

length present

PLATFORM Alphanumeric 12 Yes The acronym for the service platform that
operates one or multiple services. For
example, SWIFTNet is a platform operating
services such as Investment Funds, Cash
Reporting end Generic FileAct. All services on
SWIFTNet have a common data structure.

GENERIC FIELD NAME Alphanumeric 20 Yes The title of the data field in the REACHPLUS
data file.

SPECIFIC FIELD NAME Alphanumeric 25 No The platform-specific title of the data field in
the REACHPLUS file. Not present if the
column in the REACHPLUS data file is not
used for the platform.

SPECIFIC FIELD Character 600 No The platform-specific meaning of the data

DESCRIPTION field in the REACHPLUS file.

SPECIFIC FORMAT Alphanumeric 8 No The platform-specific meaning of the data

field in the REACHPLUS file.

ALWAYS PRESENT Alphabetic 3 Yes The mandatory or optional presence of the

data in the platform-specific data field in the
REACHPLUS file.
Possible values in the REACHPLUS file:
• YES
• NO

ALLOWED VALUES Character 255 No If the data in the platform-specific data field
contains a fixed value or a range of fixed
values for all records of the platform, then this
field contains that fixed value (or the range of
fixed values).

FIELD A Alphanumeric 1 No Reserved for future use

FIELD B Alphanumeric 8 No Reserved for future use

5.3 REACHPLUSSTRUCTURE Sample Files

The use of metadata files provides flexibility. As these files are complex, SWIFTRef provides
samples files to help customers understand how the metadata works. The
REACHPLUSSTRUCTURE_V1_SAMPLE.TXT and the REACHPLUS_V1_SAMPLE.TXT files are
available on www.swift.com/swiftref > Documentation > Products. For ease of use, users can
import these files into Microsoft Excel.

28 February 2020 25
SWIFTRef Reach Plus Fields and Flags for SWIFTRef Files
Technical Specifications

Appendix A Fields and Flags for SWIFTRef Files

A.1 MODIFICATION FLAG Field in SWIFTRef Files

Overview
The MODIFICATION FLAG field reflects the update status of a specific record compared to the
previous (monthly or daily) publication.
ADM flags are used in the SWIFTRef Reach Plus files.

ADM flags
FIELD DESCRIPTION DESCRIPTION

MODIFICATION FLAG A (Added)

In a full file: this record must be added to the target database. (All records in the target
database should be deleted before importing the full file so all records in the full file have the
"A" flag, as they all must be added.)
In a delta file: this new record must be added to the target database.(1)

D (Deleted)
In a full file: not applicable. The deleted records are omitted from the full file and therefore will
not be added to the emptied target database.
In a delta file: this record must be deleted from the target database.

M (Modified)
In a full file: not applicable. The modified records have the "A" value.
In a delta file: the existing record must be modified in the target database.

(1) The target database is the database to which you import the full or delta file.

28 February 2020 26
SWIFTRef Reach Plus Publication Date and Validity Date for SWIFTRef Files
Technical Specifications

Appendix B Publication Date and Validity Date for

SWIFTRef Files

B.1 Applicable Dates for SWIFTRef Reach Plus Data

The SWIFTRef Reach Plus files are published on the same date as the BIC Directory 2018. For the
scheduled publication dates, see the Publication Schedule and Distribution Information.
In general, the data records inside the SWIFTRef Reach Plus data files (that is, files included in the
zip archive) are valid at publication date. For the full list of files, see the table in Monthly File
Names on page 11.
The publication date is specified in the file name, for example:
• REACHPLUS_V1_FULL_20160325.TXT
Note The BIC Directory 2018 uses the BIC activation date concept, where the entire file
becomes valid at the activation date, rather than at the publication date. This concept
is not applied to SWIFTRef Reach Plus files.

28 February 2020 27
SWIFTRef Reach Plus Services
Technical Specifications

Appendix C Services

C.1 Payment Services and Market Infrastructures

The number of PMI Services in SWIFTRef Reach Plus continuously increases. For more
information, see the SWIFTRef Release Letter for details about added PMI Services and the
participant lists.

C.2 SWIFTNet Services

The following SWIFTNet services that operate on InterAct or FileAct are included in SWIFTRef
Reach Plus:
• Bulk Payments Generic
• Bulk Payments Generic in store-and-forward transfer mode
• Bulk Payments for Bilateral Clearing (Live)
• Bulk Payments for Bilateral Clearing (Test)
• Cash Reporting
• Cash Reporting Hosted Model File Transfer (Live)
• Cash Reporting Hosted Model File Transfer (Test)
• Data Distribution SMD (Live)
• Data Distribution SMD (Test)
• eStatements
• Exceptions and Investigations (Live)
• Exceptions and Investigations (Test)
• FileAct in real-time file transfer mode (Live)
• FileAct in real-time file transfer mode (Test)
• FileAct in store-and-forward transfer mode (Live)
• FileAct in store-and-forward transfer mode (Test)
• FpML
• FpML (Test)
• SWIFTNet Funds (Live)
• SWIFTNet Funds (Test)
• Proxy Voting (Test)
• SWIFTRemit (Workers' Remittances)
• SWIFTRemit Flash (Workers' Remittances)
• Trade Services Utility Bank to TSU (Live)
• Trade Services Utility Bank to TSU (Test)
• Trade Services Utility TSU to Bank (Live)
• Trade Services Utility TSU to Bank (Test)
• Transaction Reporting (Live)

28 February 2020 28
SWIFTRef Reach Plus Services
Technical Specifications

• Transaction Reporting (Test)

C.3 SWIFT FINCopy Services

The PMI_V1 and REACHPLUS files include all FINCopy services. In most cases, these services
are RTGS services operated by central banks. For more information about the FIN service codes,
see the BIC Directory Business Codes, available on Knowledge Centre (User Handbook) and on
www.swiftrefdata.com > Download Area. These services have a FIN service code (also called a
FINCopy code or a VAS code).
An overview of these services an be obtained in the following ways:
• Filter the PMI_V1 file on ALTERNATIVE SERVICE IDS with the keyword "FIN". This keyword is
followed by the FIN service code.
• Filter the REACHPLUS file on PLATFORM = "SNETFIN". This will list all FIN service codes in
the column SERVICE ID, as well as the individual participants (that have voluntarily registered
at SWIFT) in the resulting records.

C.4 SWIFTgpi Service

The gpi service has its own directory available to gpi participants only. gpi participant data are not
included in SWIFTRef Reach Plus.

28 February 2020 29
SWIFTRef Reach Plus Guidelines to Use the Reach Plus Files
Technical Specifications

Appendix D Guidelines to Use the Reach Plus Files

D.1 The Files

If you are subscribed to Reach Plus, Corporate Pack Three, or Payments Plus, then you have
access to the following three files:
• PMI_V1_XXXXX.YYY
• REACHPLUS_V1_XXXXX.YYY
• REACHPLUSSTRUCTURE_V1_XXXXX.YYY
XXXXX stands for the publication frequency of the file (DAILY, MONTHLY), content (FULL or
DELTA), and the publication date (in the format YYYYMMDD). YYY stands for the format of the file
(either .TXT or .XML).
The PMI file contains a worldwide list of payment services such as ACHes, RTGSes, cheque
clearing systems, and real-time retail payment services (often referred to as instant payment
services). Each payment service is represented by a single record.
The REACHPLUS file contains the list of participants of the payment services. Not all payment
services in the PMI file have a list of participants in the REACHPLUS file yet. Over time, the
number of participant lists increases.
The REACHPLUSSTRUCTURE file is a metadata file. It contains the data structure of each single
participant list of a payment service. This is needed, because most payment services have
attributes of their own, but are different from the attributes of other payment services. For more
information about the purpose of the REACHPLUSSTRUCTURE file, see Overview of the
REACHPLUSSTRUCTURE File on page 24.

D.2 Links Between the Files

A payment service in the PMI file is uniquely identified by the SERVICE ID, the natural identifier of
the payment service record. The SERVICE ID will not change over time unless a mistake must be
corrected, in which case users will be notified several months prior through the Release Letter. This
allows users to adapt their applications if needed. In addition, the RECORD KEY is the unique
technical identifier of a record in any file. Generally, a payment service record will also preserve its
RECORD KEY over time.
The REACHPLUS file contains the participants of the payment services. A SERVICE ID identifies
the list of participants of a payment service. The list consists of a subset of records. In addition to
the SERVICE ID, each participant in the list has its own PARTICIPANT ID. Therefore, the
combination of the SERVICE ID and the PARTICIPANT ID is the unique natural record key. In
addition, the RECORD KEY is the unique technical record identifier.
The link between the PMI file and the REACHPLUS file is the SERVICE ID. One record in the PMI
file may have many corresponding records in the REACHPLUS file (as many as there are service
participants) or none, in case there is no list of service participants yet available.
The REACHPLUSSTRUCTURE file contains data definitions for a single participant list in the
REACHPLUS file, or a set of multiple participant lists if the data definition is “shared” by multiple
participant lists. A shared data definition is, for example, applied to the multiple SEPA payment
services where the data structures of the participant lists are identical due to the standardisation by
the EU regulator.
A data definition of a payment service is called a PLATFORM and consists of 31 records, which all
share the same PLATFORM value. These 31 records define the 31 data attributes (columns) in the

28 February 2020 30
SWIFTRef Reach Plus Guidelines to Use the Reach Plus Files
Technical Specifications

REACHPLUS file that are specific to the payment service. Each record defines the name, format,
and other characteristics of the attribute. The unique (natural) key in the
REACHPLUSSTRUCTURE file is the combination of the PLATFORM and the GENERIC FIELD
NAME. This combination is unique. The RECORD KEY is the unique technical record key and is
stable over time. However, generally there is no guarantee that the records in the three files will
always preserve their RECORD KEYs. The RECORD KEY should only be used to identify the
records imported into your application, which must be deleted or updated during the import of a
delta file.
The link between the REACHPLUS file and the REACHPLUSSTRUCTURE file is the PLATFORM.
Each REACHPLUS record contains the PLATFORM attribute. This is a many-to-many relationship,
as a single record in the REACHPLUS file is linked through the PLATFORM to 31
RECHPLUSSTRUCTURE records that define the attributes (columns) of the record. One
PLATFORM (that is, a set of 31 REACHPLUSSTRUCTURE records) can be applied to multiple
participant lists in the REACHPLUS file each with a different SERVICE ID.
There also is a relationship between the PMI file and the REACHPLUSSTRUCTURE file, because
a PMI record has a PLATFORM attribute but is populated only if the PMI has the associated
participant list records in the REACHPLUS file. The relationships are as follows:

Unique: 1...N
SERVICE ID
PMI

PLATFORM
1

SERVICE ID

0,1
0...N

Unique*: Unique:
SERVICE ID+ PLATFORM REACHPLUS
REACHPLUS PLATFORM+
PARTICIPANT ID 1...M 31 STRUCTURE GENERIC FIELD NAME

D1990002
* This is the natural key, and it is unique in most cases. However, if the PARTICIPANT ID is
unknown, then it contains the keyword "UNKNOWN". If there are multiple unknown IDs, then the
key is not unique. For services that have the PLATFORM "SEPA", the SERVICE ID+PARTICIPANT
ID is repeated per SEPA Scheme. The true unique key is the RECORD KEY.
In the PMI file, the SERVICE ID is a true unique key. In the REACHPLUSSTRUCTURE file, the
combination of PLATFORM+GENERIC FIELD NAME is a true unique key.

Summary
• One payment service (a single record in the PMI file) has zero or one list of participants (a set of
records that share an identical SERVICE ID) in the REACHPLUS file.
• One list of participants (a set of records that share an identical SERVICE ID) in the
REACHPLUS file has one data definition (a set of 31 records that share an identical
PLATFORM) in the REACHPLUS file.
• One list of participants in the REACHPLUS file (a set of records that share an identical
SERVICE ID) has one data definition (a set of 31 records that share an identical PLATFORM) in
the REACHPLUSSTRUCTURE file.

28 February 2020 31
SWIFTRef Reach Plus Guidelines to Use the Reach Plus Files
Technical Specifications

• One data definition (a set of 31 records that share an identical PLATFORM) in the
REACHPLUSSTRUCTURE file is related to one or multiple participant lists (a set of records that
have an identical SERVICE ID) in the REACHPLUS file.
• One payment service (a single record in the PMI file) has zero or one data definition (a set of 31
records that share an identical PLATFORM) in the REACHPLUSSTRUCTURE file.

D.3 Importing Data into Your Application

There are several options to import the data from the three files into your application:
• preserving the dynamic structure of the REACHPLUS data (recommended) by using the
REACHPLUSSTRUCTURE file for configuration
• mapping the variable REACHPLUS data structure on your own fixed structure, while preserving
all data attributes of all payment services
• mapping the variable REACHPLUS data structure on your own fixed structure, while only
including a restricted set of data attributes
In the first option, you must define a database table with a structure similar to the table of the
REACHPLUS file, where the fields ATTRIBUTE 1 to ATTRIBUTE 20 are dynamically assigned to
contain a variety of data attributes that are different per SERVICE ID. If you build a user interface, a
list of payment service participants table will show the number of columns that correspond to the
number of SPECIFIC FIELD NAMES for that service, and the column names will be the SPECIFIC
FIELD NAMES of that service. The columns displayed are different per payment service, and the
column header must be changed per payment service displayed to the end-user. Developing such
an interface is more complex than a fixed-column interface, but it can show all applicable attributes
in less than 20 columns and is flexible so that it can show any payment services added at a later
stage.
In the second option, you will need as many data fields (columns) in your table as there are data
attributes in all payment services worldwide together. Due to a standardisation of the attribute
names in the REACHPLUS file, the total number of columns for all services worldwide is between
200 and 300, from multiple hundreds more if the original attribute names are preserved. Although a
table with 200 or 300 columns is technically feasible, it is not end-user-friendly (with many empty
fields) and mapping the attribute names of the REACHPLUS file on your table with 200 or 300
columns will be cumbersome.
You may opt for the third option, where users map the REACHPLUS data on a restricted number of
fixed columns in the table. With this option, it is possible that you could exclude some service
attributes needed by the end-user. If you opt for this approach, then see Restricted List of Attributes
on page 35 for more information.

D.4 Standardised Field Names

Each payment service uses data field names of its own choosing. Generally, they will not be
standardised. In order to simplify them for the end-users, SWIFTRef has standardised most of the
namesa.
Examples of standardised attribute names

Payment Service Original name Standardised name

US FedACH Routing number PARTICIPANT ID

28 February 2020 32
SWIFTRef Reach Plus Guidelines to Use the Reach Plus Files
Technical Specifications

Payment Service Original name Standardised name

CH SIC Interbank Clearing BC No PARTICIPANT ID

IN National Electronic Funds IFSC PARTICIPANT ID

Transfer

US FedACH Institution name PARTICIPANT NAME

CH SIC Interbank Clearing Bank/Institution PARTICIPANT NAME

IN National Electronic Funds Bank PARTICIPANT NAME

Transfer

The original names of several hundreds of attributes have been standardised into 22 standard
names (in the following list). The remainder of the field names that appear infrequently have been
preserved in their original forms. Although the names have been standardised, the descriptions of
the attributes remain service-specific, as the meaning of the data element may differ per payment
service. The descriptions are listed in the REACHPLUSSTRUCTURE file, field SPECIFIC FIELD
DESCRIPTION.

Standardised field name Meaning E

PARTICIPANT ID The identifier of the participant in the payment service E

PARTICIPANT NAME The name of the participant institution E

PARTICIPANT ID TYPE The type of the participant identifier (not the type of
participant). For example, in case of a clearing code in India:
IFSC, MICR.

PARTICIPANT NAME LL The name of the participant institution in the local language

PARTICIPANT ALTERN ID A second identifier of the participant, additional to the

PARTICIPANT ID

PARTICIPANT BRANCH The branch name of the participant institution

NAME

PARTICIPANT BRNCH NAME The branch name of the participant institution in the local
LL language

PARTICIPANT ALTERN The synonym name, short name, acronym, or abbreviation of

NAME the participant name

ADDRESS The (concatenated) address of the participant or its branch

ADDRESS LL The (concatenated) address of the participant in the local

language

PARTICIPANT TYPE The type of participant E

28 February 2020 33
SWIFTRef Reach Plus Guidelines to Use the Reach Plus Files
Technical Specifications

Standardised field name Meaning E

OFFICE TYPE Can be the following:

• head-office (HO)
• branch (BR)
• domestic branch (DB)
• foreign branch (FB)

DIRECT INDIRECT Can be the following: E

• D - direct participant
• I - indirect participant, reachable through an intermediary
(not related to whether the participant can do the
settlement or cannot)

INTERMEDIARY ID The Identifier of the direct participant through which the E

indirect institution can be reached

SETTLEMENT Can be the following:

• Y - the participant can do the settlement
• N - the participant cannot do the settlement

SETTLEMENT PARTICIPANT The Identifier of the participant that can do settlement for the
ID participant that cannot

PARTICIPANT ROLE The role or the capability of the participant E

TRANSACTION TYPE The transaction type(s) that the participant supports, if they
vary per participant. This is a comma-separated list in case
of multiple types.

COUNTRY CODE The 2-digit ISO country code of the participant E

CURRENCY CODE The 3-digit ISO currency code of the currency serviced by E
the participant

BIC The BIC of the participant. Only provided when the BIC is an
additional identifier, different from the main identifier in
PARTICIPANT ID.

ACCOUNT NUMBER The account number of the participant

CONTACT DETAILS The contact details of the participant

OPERATIONAL STATUS The operational status of the participant. Can be one of the E(1)
following:
• live
• pilot
• active
• inactive
• suspended

28 February 2020 34
SWIFTRef Reach Plus Guidelines to Use the Reach Plus Files
Technical Specifications

Standardised field name Meaning E

START DATE The date when the participant becomes active in the
payment service

STOP DATE The date when the participant leaves the payment service

UPDATE DATE The date when the record is updated

(1) Instead of importing the OPERATIONAL STATUS attribute, filter the records on this and only include those that have the “Live”
or “Active” status.

D.5 Restricted List of Attributes

If you consider not to import all attributes but only an essential subset (third option), then you might
choose to import the 22 standardised attributes listed in Standardised Field Names on page 32. A
further restricted subset, the essential subset, is also provided in the table where the essential
fields are marked with “E” in the right-most column.

a Some field names in some payment services are not yet standardised. When the names will be changed will be announced in the Release Letter.

28 February 2020 35
SWIFTRef Reach Plus Legal Notices
Technical Specifications

Legal Notices
Copyright
SWIFT © 2020. All rights reserved.

Restricted Distribution
Do not distribute this publication outside your organisation unless your subscription or order
expressly grants you that right, in which case ensure you comply with any other applicable
conditions.

Disclaimer
The information in this publication may change from time to time. You must always refer to the
latest available version.

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. SC. The following are registered trademarks of SWIFT:
3SKey, Innotribe, MyStandards, Sibos, SWIFT, SWIFTNet, SWIFT Institute, the Standards Forum
logo, the SWIFT logo and UETR. Other product, service, or company names in this publication are
trade names, trademarks, or registered trademarks of their respective owners.

28 February 2020 36