Alliance Access 7.1.

40

Release Letter

This document contains release information for Alliance Access 7.1.40.

04 August 2017
Alliance Access 7.1.40
Release Letter Table of Contents

Table of Contents

Practical Information.........................................................................................................................................4

1 Overview...................................................................................................................................................5
1.1 Enhancements.........................................................................................................................................5
1.2 Resolved Problems..................................................................................................................................6
1.3 Software Distribution................................................................................................................................6
1.4 System Requirements............................................................................................................................. 6
1.5 Documentation........................................................................................................................................ 8
1.6 Warnings and Known Issues................................................................................................................... 9
1.7 Obsolete Functionality............................................................................................................................. 9
1.8 Other Information...................................................................................................................................10

2 Installing the Update............................................................................................................................. 11

2.1 Alliance Access on AIX, Linux, or Oracle Solaris.................................................................................. 11
2.2 Alliance Access on Windows................................................................................................................. 12
2.3 Alliance Web Platform Server-Embedded............................................................................................. 13

3 Support...................................................................................................................................................14

A Routing Keyword Extraction and Verifiable Fields.............................................................................15

B Switch-over Planning for Standards MT..............................................................................................28

B.1 Actions to be Taken Now....................................................................................................................... 28
B.2 Actions to be Taken as Soon as Possible.............................................................................................. 28
B.3 Actions to be Taken Before 18th November 2017................................................................................. 28
B.4 Actions to be Taken on 15th, 16th, or 17th November 2017 (Last Business Day of the Week).............28
B.5 Actions to be Taken Before Your First Log In on 19th or 20th November 2017..................................... 29
B.6 Actions to be Taken after the First Login............................................................................................... 29

C Standards Switch-over Planning for InterAct Services..................................................................... 30

C.1 Actions to be Taken When You Are Notified of a Service Change.........................................................30
C.2 Get Ready for Testing............................................................................................................................ 30
C.3 Migrate to the New Standards............................................................................................................... 31
C.4 Wind Down Use of the Old Standards................................................................................................... 31
C.5 Stop Using the Old Standard.................................................................................................................32

04 August 2017 2
Alliance Access 7.1.40
Release Letter Table of Contents

Legal Notices................................................................................................................................................... 33

04 August 2017 3
Alliance Access 7.1.40
Release Letter Practical Information

Practical Information
Installation type Mandatory by November 19, 2017

Customer upgrade path For Alliance Access:

Release 7.1.23 - [7.1.30] - 7.1.40
For Alliance Access GUI packages (on Alliance Web Platform
Server-Embedded):
Release 7.1.23 - [7.1.30] - 7.1.40

Operating system requirements Same as Alliance Access 7.1.2x.

See System Requirements on page 6.

Product dependencies This release has dependencies on other products:

Alliance Web Platform Server-Embedded 7.0.70 or higher
Alliance Gateway 7.0.50 or higher
See also SWIFTNet Requirements on page 7 and Other
Requirements on page 7.

Purpose of this Document

This document contains release information for Alliance Access 7.1.40 (including Alliance Web
Platform 7.1.40 GUI packages). Alliance Access 7.1.40 supports the Standards MT November
2017 release that will be effective as of 19 November 2017, the scheduled release date of FIN. This
document is intended for the system administrators of the Alliance Access systems. It clarifies the
changes in this update, the product dependencies , installation instructions, and last minute
information.
First read this Release Letter, and then use the other documentation provided for more detailed
information.
For a complete list of documents, see section Documentation on page 8.

04 August 2017 4
Alliance Access 7.1.40
Release Letter Overview

1 Overview
Alliance Access 7.1.40 includes all changes introduced since update 7.1.23. It also contains the
following enhancements with no new features or functionalities:
Updates for Standards MT November 2017

1.1 Enhancements

1.1.1 Updates for Standards MT November 2017

Alliance Access 7.1.40 introduces the Standards MT November 2017 and implements all required
changes to support the new Standards. For more information, see the Standards page on
www.swift.com.

SWIFT gpi: on the Standards Release 2017 cut-over date, all banks must be capable of receiving
gpi fields in Block3 of the MT 103
The February 2017 updates of the Standards Release Guide on SWIFT gpi mentions:
MT 103, MT 103 STP, and MT 103 REMIT: Two additional fields may be present in header block 3
to indicate a service type identifier (field 111) or a Unique End-to-end Transaction Reference
(UETR, field 121). Use of these fields has previously been restricted to members of the SWIFT
Global Payment Innovation (SWIFT gpi) Initiative. This service allows banks in the SWIFT gpi
Closed User Group (CUG) to track payments based on the UETR. SWIFT gpi participants will be
allowed to include these header fields in all MTs 103, MTs 103 STP, and MTs 103 REMIT that they
send, including to banks that are not in the CUG, allowing the service to track a payment up to
the first bank outside of the SWIFT gpi CUG. Banks that are not in the CUG must be able to
receive these header fields but will not be allowed to send or forward messages containing fields
111 or 121.
All Alliance interfaces (Access, Entry, AMH, Lite and Lite2) are already capable of receiving the
fields and forwarding them to your back office. Make sure that your payment systems are able to
receive messages with block 3 field 111 and 121. Alliance interfaces will not remove the gpi fields
from incoming MT103 when passing them on to back office systems. If needed SWIFT Consulting
Services can propose custom solutions.
Note If you are using XMLv2, revision 7 must be used to pass the fields.
When used in the scope of a FIN-Copy server, MT096 message syntax will also be
modified. The gpi field tags will also be included in block 4 of MT 096 copy messages
generated by FINCopy and FINInform services.
Non-gpi banks who wish to test receipt of an MT 103 with the gpi fields can download an example
from the Test and Training tank file using an MT 073 Message Sample Request in local test mode
future.

SWIFT gpi: with Standards Release 2017, MT 096 FINCopy/FINInform Message will also contain
gpi fields in block 4
The MT 096 contains all the blocks of the original message, including the user header in block 3.
On an exceptional basis, the gpi fields are currently not copied into MT 096 messages. This

04 August 2017 5
Alliance Access 7.1.40
Release Letter Overview

changes with the 2017 Standards release as of which normal service operation will be restored and
gpi fields present in an MT 103 will be copied into block 4 of the MT 096.
Market Infrastructures and financial institutions that receive MT 096 messages can test receipt of
an MT 096 with the gpi fields by downloading an example from the Test and Training tank file using
an MT 073 Message Sample Request in local test mode future as of 22 July 2017.

SWIFT gpi: Unique End-to-end Transaction Reference format enforced

As of the activation of the Standards 2017, the Unique End-to-end Transaction Reference (UETR)
used in the framework of SWIFT gpi will have to comply with Version 4 of Standard RFC4122.
Instead of being a 36X field, it will now have to be formatted as xxxxxxxx-xxxx-4xxx-yxxx-
xxxxxxxxxxxx where x is a lower case hexadecimal character (0-9,a-f) and y is 8,9,a or b). This will
be validated during manual entry.

1.2 Resolved Problems

See Knowledge Base tip 5021840 for a detailed list of all change requests addressed in this
release.

1.3 Software Distribution

This update of Alliance Access is available on the Download Centre on www.swift.com.
The software package is a .tar or .zip file (Access7140_AIX.tar, Access7140_RHEL.tar,
Access7140_SunOS.tar, Access7140_win32.zip) containing the following:
Alliance Access 7.1.40
Alliance Access/Entry 7.1.40 GUI package

1.4 System Requirements

Requirements have not changed for this update.

1.4.1 Operating System Requirements

1.4.1.1 Alliance Access

Same as Alliance Access 7.1.20.

1.4.1.2 More information

Please consult the following:
System Configuration Recommendations and Guidelines, dated 29th April 2016
OS Levels and Patches Baseline, dated 27th March 2015
Alliance Product Family - Compatibility Matrix

04 August 2017 6
Alliance Access 7.1.40
Release Letter Overview

1.4.2 Memory Requirements

Same as Alliance Access 7.1.20.

On UNIX and Linux, the system should be configured to have at least 8 GB of swap space before
you start an installation or upgrade for Alliance Access 7.1.40.

1.4.3 System Requirements on UNIX and Linux

Same as Alliance Access 7.1.20.

1.4.4 SWIFTNet Requirements

Alliance Access 7.1.40 has the following SWIFTNet requirements:
Alliance Access connects to SWIFTNet through Alliance Gateway 7.0.50 (or higher) using
relaxed mode.

1.4.5 Alliance Requirements

1.4.5.1 Alliance Access

Alliance Access 7.1.40 must be installed on top of Alliance Access 7.1.23 or higher.
Alliance Access 7.1.40 requires the Alliance Access 7.1.40 GUI packages.

Important If you have not yet installed the mandatory Alliance Security Update 2017-05, you can
install it before or after installing 7.1.40.

1.4.5.2 GUI packages on Alliance Web Platform Server-Embedded

The Alliance Access 7.1.40 GUI Packages deployed on Alliance Web Platform Server-Embedded
7.0.70 have been qualified using Alliance Access 7.1.40.
Note Alliance Access GUI packages must not be used with Internet Explorer 11 in
Enterprise mode. For more information on how to tune your Internet Explorer, see
Web Browser Settings in the Installation Guide (AIX, Linux, Oracle Solaris, Windows).
Note SWIFT recommends that you remove unused packages (such as previous versions
when they are no longer required), in order to reduce memory usage of Alliance Web
Platform Server-Embedded.

1.4.6 Other Requirements

04 August 2017 7
Alliance Access 7.1.40
Release Letter Overview

1.4.6.1 Network Time Protocol Server

Usage of an NTP (Network Time Protocol) server is recommended when using time-based one-
time passwords. This allows a minimal time drift between the server and the client authenticator
applications.
When using an NTP server, it must be configured in slew mode to ensure that the time stays
monotonic.

1.4.6.2 NTFS Compression and Encryption (Windows only)

Alliance Access cannot be installed in a folder or drive with NTFS compression or encryption
enabled.

1.4.6.3 File System Type for High-throughput Systems (AIX only)

On the AIX platform, the file system(s) for Alliance Access must be jfs2 (and not jfs with large file
option) on high-throughput systems.

1.4.6.4 Software from Oracle for Hosted Database Option

Same as Alliance Access 7.1.20.

1.4.6.5 IBM MQ
Same as Alliance Access 7.1.20.

1.4.6.6 LDAP Packages

Client LDAP packages are required if you want to use the LDAP functionality.
Please refer to the OS Levels and Patches Baseline document, dated 27 March 2015, for the list of
necessary packages.

1.4.6.7 Alliance Access and Network Drives

SWIFT has not qualified Alliance Access/Gateway/Web Platform Server-Embedded whereby
software or database files reside on an NFS-mounted or mapped network drive.
See Knowledge Base tip 5020267 for for more detail.

1.5 Documentation
The following documents are available for Alliance Access 7.1.40:
Alliance Access Administration Guide - AIX
Alliance Access Administration Guide - Linux
Alliance Access Administration Guide - Oracle Solaris

04 August 2017 8
Alliance Access 7.1.40
Release Letter Overview

Alliance Access Administration Guide - Windows

Alliance Access Configuration Guide
Alliance Access Installation Guide - AIX
Alliance Access Installation Guide - Linux
Alliance Access Installation Guide - Oracle Solaris
Alliance Access Installation Guide - Windows
Alliance Access Message Management Guide
Alliance Access Monitoring Guide
Alliance Access Relationship Management Guide
Alliance Access Security Guide
Alliance Security Guidance
IBM PowerHA SystemMirror Standard Edition Installation and User Guide
This document is licence restricted and can be requested from customer support by customers
who have the 11:DUAL HARDWARE option in their licence sheet.

Documentation for CREST over SWIFTNet Users

The following guides are specifically for CREST over SWIFTNet users:
CREST over SWIFTNet Customer Application Integration Guide - UNIX and Linux
CREST over SWIFTNet Customer Application Integration Guide - Windows

1.6 Warnings and Known Issues

See Knowledge Base tip 5021841 for the latest detailed list of all warnings and known issues with
Release 7.1.40.

1.7 Obsolete Functionality

1.7.1 End of Support for Alliance Workstation

As announced in early March 2015, Alliance Workstation is no longer supported as of the end of
March 2017.
Alliance Access 7.1.40 is incompatible with Alliance Workstation.

Consequences of the Retirement of Alliance Workstation

The retirement of Alliance Workstation has the following impact:
customers who used the Alliance Workstation GUI on the server to perform message
processing or system administration must now use the Alliance Web Platform Server Embedded
based GUIs.

04 August 2017 9
Alliance Access 7.1.40
Release Letter Overview

1.8 Other Information

1.8.1 Release 7.2

SWIFT announced at the end of September 2015 that it is planning a mandatory release 7.2.
Release 7.2 will be released in 2017, and will have a mandatory migration window of 15 months.
For more information see the Alliance 7.2 Final Release Overview.

04 August 2017 10
Alliance Access 7.1.40
Release Letter Installing the Update

2 Installing the Update

Alliance Access 7.1.23 or higher must be installed before installing Alliance Access 7.1.40.

2.1 Alliance Access on AIX, Linux, or Oracle Solaris

Alliance Access 7.1.40 must be installed by either the Alliance Access owner account or by root.

Prerequisites
1. Before installing the update, make sure that the Alliance Access server is stopped
(saa_system stop command and saa_bootstrap stop commands) and that all Alliance
Access applications (including the System Administration window) are closed.
2. Take a system backup, with the database stopped.

Procedure
1. Download the installation media to a temporary folder (for example, /tmp).
2. Extract the software from the downloaded tar file and navigate to the folder (AIX, RHEL, or
SunOS) of the platform on which you are installing.
3. If you are working remotely, export the display to your local machine. Type the following
command: export DISPLAY=<IPaddressComputer>:0.0, where <IPaddressComputer>
is the IP address of the computer where the installation windows are displayed.
4. If the disk space requirements for the temporary files for the install program cannot be satisfied,
the installer option -tempdir <TMPDIR> can be used to specify an alternate temporary
directory.
5. Run the executable ./saa-patch-install
If you run the installation in silent mode, execute the command as follows:
./saa-patch-install -silent <path to file
silent.properties.install.patch>
Note The <path to file silent.properties.install.patch> can be found
under the installation software on the temporary folder, where it was copied (/
tmp). The following lines in the file must be edited before launching the installation:
## Licensing terms agreement (mandatory)
## Uncomment to specify your agreement with licensing terms
Mandatory.Accept.LicensingTerms=Agree
## Backup confirmation (mandatory)
## Uncomment to confirm you have taken the necessary Alliance
Access backups

Mandatory.Backup=I confirm

## Installation root directory (mandatory)

## Used to identify the instance being patched
## Modify the value if not using the default value
application.installLocation=/Alliance/Access

04 August 2017 11
Alliance Access 7.1.40
Release Letter Installing the Update

Note After installing update 7.1.40, you will need to install the latest mandatory Security
Update(s) if you have not already done so.

2.2 Alliance Access on Windows

Alliance Access 7.1.40 must be installed by the Alliance Access owner account.

Prerequisites
1. Before installing the update, make sure that the Alliance Access server is stopped
(saa_system stop command and saa_bootstrap stop commands) and that all Alliance
Access applications (including the System Administration window) are closed.
2. Take a system backup, with the database stopped.

Procedure
1. Download the installation media to a temporary folder (for example, C:\Temp).
2. Log in with the Alliance Access owner account.
3. Extract the software from the downloaded zip file and navigate to the win32 folder.
4. Double-click saa-patch-install.exe to launch the installation.
If you run the installation in silent mode, execute the command as follows:
saa-patch-install -silent <path to file
silent.properties.install.patch>
Note The <path to file silent.properties.install.patch> can be found
under the installation software on the temporary folder, where it was copied (C:
\TEMP). The following lines in the file must be edited before launching the
installation:
## Licensing terms agreement (mandatory)
## Uncomment to specify your agreement with licensing terms
Mandatory.Accept.LicensingTerms=Agree
## Backup confirmation (mandatory)
## Uncomment to confirm you have taken the necessary Alliance
Access backups
Mandatory.Backup=I confirm
## Installation root directory (mandatory)
## Used to identify the instance being patched
## Modify the value if not using the default value
application.installLocation=C\:\\Alliance\Access
## Product key (mandatory)
## Specify the product being patched:
application.key=saa

Note After installing update 7.1.40, you will need to install the latest mandatory Security
Update(s) if you have not already done so.

04 August 2017 12
Alliance Access 7.1.40
Release Letter Installing the Update

2.3 Alliance Web Platform Server-Embedded

2.3.1 Overview
See the Alliance Web Platform Server-Embedded Installation Guide (AIX, Linux, Oracle Solaris,
Windows) for information about the installation and configuration of the GUI packages.
To locate the packages in the downloaded file, navigate to the GUIPackages directory. The
packages are locate in a single .ear file: access_7_1_40.ear.
Note To preserve user preferences, ensure that you install the 7.1.40 GUI packages before
removing the 7.1.2x package.

2.3.2 Installation procedure

1. Copy the content of the downloaded file to a local path.
2. Deploy release 7.1.40 (access_7_1_40.ear), which is cumulative, by running the swp_config
-packages -install command. The configuration from any previous GUI packages will be
migrated.
3. If you have created any custom application groups, update them with the new version of the
application(s) or create new specific custom groups with the new version of the application(s).
4. To minimise resource consumption, if the previous GUI packages have already been installed
and are no longer needed, SWIFT recommends that you remove them by using the
swp_config -packages -uninstall command.

04 August 2017 13
Alliance Access 7.1.40
Release Letter Support

3 Support
Support for SWIFT customers
By default, SWIFT Support is the single point of contact to report all problems and queries that
relate to SWIFT services and products. Support is available to all SWIFT customers.
Individuals within a customer organisation must register to use the Support service.
For more information about the different services that SWIFT offers as part of the support
packages and the procedure to order support, see Comparison of support packages on swift.com.

Related information

For more information about Support services, see the service description related to the applicable
support package:
Support documentation

04 August 2017 14
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

A Routing Keyword Extraction and Verifiable

Fields
The following table lists the Standards MT November 2017 routing keywords and verifiable fields for
each message in this Deployment Package.
The first set of columns, entitled "Keyword", lists per Message Type (MT) the fields that are
extracted for the default keywords, Currency/Amount, and Date. These keywords, which are verified
against operator permission, are used to facilitate search criteria and sorting functions in GUI
applications, such as the Message Approval application.
Note For repetitive fields, and unless specified otherwise, keywords are always extracted
from their first occurrence, and in the case of repetitive sub sequences, only the first
instance is considered.
A message is scanned top-down and the first field that matches the table is extracted.
The second set of columns, entitled "Verifiable", lists those fields that need to be re-entered by an
operator for message approval. Unless specified otherwise, all occurrences of repetitive fields are
verified.

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

101 Seq A.F20 Seq B.F32B Seq B.F32B F32B,F33B F32B,F33B

F32A,F32B, F19,F32A,F
102 Seq A.F20 Seq C.F32A Seq C.F32A Seq C.F32A F33B,F71F,F 32B,F33B,F F32A
71G 71F,F71G

F32A,F32B, F19,F32A,F
102.
Seq A.F20 Seq C.F32A Seq C.F32A Seq C.F32A F33B,F71F,F 32B,F33B,F F32A
STP
71G 71F,F71G

F32A,F33B, F32A,F33B,
103 F20 F32A F32A F32A F32A
F71F,F71G F71F,F71G

103.
F32A,F33B, F32A,F33B,
REMI F20 F32A F32A F32A F32A
F71F,F71G F71F,F71G
T

103. F32A,F33B, F32A,F33B,

F20 F32A F32A F32A F32A
STP F71F,F71G F71F,F71G

F19,F32B,F3
F32B,F33B,
104 Seq A.F20 Seq C.F32B Seq C.F19 F30 3B,F71F,F71 F30
F71F,F71G
G

105 F20

04 August 2017 15
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

F19,F32B,F3
F32B,F33B,
107 Seq A.F20 Seq B.F32B Seq C.F19 F30 3B,F71F,F71 F30
F71F,F71G
G

110 F20 F32A,F32B F32A,F32B F32A F32A,F32B F32A,F32B F32A

111 F20 F32A,F32B F32A,F32B F32A F32A,F32B F32A,F32B F32A

112 F20 F32A,F32B F32A,F32B F32A F32A,F32B F32A,F32B F32A

190 F20 F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D

191 F20 F32B F32B F32B F32B

192 F20

195 F20

196 F20

198 F20

199 F20

200 F20 F32A F32A F32A F32A F32A F32A

201 F20 F32B F19 F30 F32B F19,F32B F30

202 F20 F32A F32A F32A F32A F32A F32A

202.
F20 F32A F32A F32A F32A,F33B F32A,F33B F32A
COV

203 F20 F32B F19 F30 F32B F19,F32B F30

204 Seq A.F20 Seq B.F32B Seq A.F19 Seq A.F30 F32B F19,F32B F30

205 F20 F32A F32A F32A F32A F32A F32A

205.
F20 F32A F32A F32A F32A,F33B F32A,F33B F32A
COV

210 F20 F32B F32B F30 F32B F32B F30

290 F20 F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D

291 F20 F32B F32B F32B F32B

292 F20

04 August 2017 16
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

295 F20

296 F20

298 F20

299 F20

Seq Seq F32B,F33B, F32B,F33B,

300 Seq A.F20 Seq B.F30V Seq B.F30V
B1.F32B B1.F32B F71F F71F

Seq Seq F32B,F32G, F32B,F32G,

304 Seq A.F20 Seq B.F30V Seq B.F30V
B1.F32B B1.F32B F33B F33B

F32B,F33B, F32B,F33B,
305 F20 F32B F32B F34P,F34R
F34P,F34R F34P,F34R

F32B,F33B, F32B,F33B,
Seq Seq
306 Seq A.F20 Seq B.F30X F33E,F34B, F33E,F34B, Seq B.F30X
B1.F34B B1.F34B
F71F,F32H F71F,F32H

F32B,F32H, F32B,F32H,
320 Seq A.F20 Seq B.F32B Seq B.F32B Seq B.F30V F33B,F33E, F33B,F33E, Seq B.F30V
F34E,F71F F34E,F71F

Seq Seq Seq Seq

Seq B.F19A:PRI B.F19A:PRI Seq B.F19A:PRI B.F19A:PRI Seq
321 A.F20C:SE N, Seq N, Seq B.F98A:VAL N,Seq N, Seq B.F98A:VAL
ME B.F19A:NIN B.F19A:NIN U B.F19A:NIN B.F19A:NIN U
T T T T

F32B,F32H, F32B,F32H,
Seq B.F32B, Seq B.F32B,
330 Seq A.F20 Seq B.F30V F33B,F33E, F33B,F33E, Seq B.F30V
Seq B.F32H Seq B.F32H
F34E F34E

Seq
F32B,F71F,F F32B,F71F,F
340 Seq A.F20 Seq B.F32B Seq B.F32B Seq B.F30F B.F30F,Seq
32H 32H
F.F30F

341 Seq A.F20 Seq B.F32B Seq B.F32B Seq B.F30F F32B,F34E F32B,F34E Seq B.F30F

F32B,F33B, F32B,F33B,
350 Seq A.F20 Seq B.F32B Seq B.F32B Seq B.F30V F33E,F34B, F33E,F34B, Seq B.F30V
F71F F71F

F32B,F32M, F32B,F32M,
360 Seq A.F20 Seq A.F32B Seq A.F32B Seq A.F30V Seq A.F30V
F32U,F71F F32U,F71F

04 August 2017 17
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

F32B,F32M, F32B,F32M,
361 Seq A.F20 Seq A.F32B Seq A.F32B Seq A.F30V F32U,F33B, F32U,F33B, Seq A.F30V
F71F F71F

F32H,F32M, F32H,F32M,
362 Seq A.F20 Seq B.F33F Seq B.F33F Seq A.F30V Seq A.F30V
F33E,F33F F33E,F33F

F32B,F32G, F32B,F32G,
364 Seq A.F20 Seq A.F32B Seq A.F32B Seq A.F30V Seq A.F30V
F32M F32M

F32B,F32G, F32B,F32G,
365 Seq A.F20 Seq A.F32B Seq A.F32B Seq A.F30V F32M,F33B, F32M,F33B, Seq A.F30V
F33E F33E

370 Seq A.F20C Seq B.F19A Seq B.F19A Seq B.F98A Seq B.F19A Seq B.F19A Seq B.F98A

Seq Seq Seq

380 A.F20C:SE Seq B.F19B Seq B.F19B B.F98A:RVA B.F98A:RVA
ME L L

Seq Seq
381 Seq A.F20C Seq B.F19B Seq B.F19B B.F98A:VAL B.F98A:VAL
U U

390 F20 F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D

391 F20 F32B F32B F32B F32B

392 F20

395 F20

396 F20

398 F20

399 F20

F32A,F32B, F32A,F32B, F32A,F32B, F32A,F32B,

400 F20 F32A F32A,F33A
F32K F32K F32K,F33A F32K,F33A

F32A,F32B, F32A,F32B, F32A,F32B, F32A,F32B,

410 F20 F32A F32A
F32K F32K F32K F32K

412 F20 F32A F32A F32A F32A F32A F32A

Seq B.F32A, Seq B.F32A,

F32A,F32B, F32A,F32B,
416 Seq A.F20 Seq B.F32B, Seq B.F32B, Seq B.F32A F32A
F32K,F71F F32K,F71F
Seq B.F32K Seq B.F32K

04 August 2017 18
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

F32A,F32B, F32A,F32B, F32A,F32B, F32A,F32B,

420 F20 F32A F32A
F32K F32K F32K F32K

F32A,F32B, F32A,F32B, F32A,F32B, F32A,F32B,

422 F20 F32A F32A
F32K F32K F32K F32K

Seq A.F32A, Seq A.F32A,

Seq A.F32K, Seq A.F32K, F32A,F32K, F32A,F32K,
430 Seq A.F20 Seq A.F32A F32A,F33A
Seq A.F33A, Seq A.F33A, F33A,F33K F33A,F33K
Seq A.F33K Seq A.F33K

450 F20 F32A F32A F32A F32A F32A F32A

F32A,F33C, F32A,F33C, F32A,F33C,

455 F20 F32A F32A F32A
F33D F33D F33D

F32A,F32B, F32A,F32B,
456 F20 F32A,F32B F32A,F32B F32A F32A,F33D
F33D F33D

490 F20 F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D

491 F20 F32B F32B F32B F32B

492 F20

495 F20

496 F20

498 F20

499 F20

Seq B.F98A,
500 Seq A.F20C
Seq B.F98C

Seq B.F98A,
501 Seq A.F20C
Seq B.F98C

Seq Seq
B.F19A:ORD B.F19A:ORD
502 Seq A.F20C R, Seq R, Seq
B.F19A:CAN B.F19A:CAN
C(1) C(1)

Seq Seq Seq

503 A.F20C:SE B.F19B:COV B.F19B:COV
ME A A

04 August 2017 19
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

Seq Seq Seq

504 A.F20C:SE B.F19B:COV B.F19B:COV
ME A A

Seq
505 A.F20C:SE
ME

Seq
506 A.F20C:SE
ME

Seq
507 A.F20C:SE
ME

Seq
508 A.F20C:SE
ME

509 Seq A.F20C

Seq
B.F98A:RRE
510 Seq A.F20C G, Seq
B.F98C:RRE
G

Seq
C.F98A:TRA
Seq C.F19A, Seq C.F19A,
D, Seq
Seq Seq
513 Seq A.F20C C.F98C:TRA
D3.F19A:SE D3.F19A:SE
D, Seq
TT TT
C.F98E:TRA
D

Seq
Seq Seq B.F98A:TRA
B.F19A:SET B.F19A:SET D, Seq
514 Seq A.F20C T, Seq T, Seq B.F98C:TRA
C3.F19A:SE C3.F19A:SE D, Seq
TT TT B.F98E:TRA
D

Seq
Seq C.F19A, Seq C.F19A,
C.F98A:SET
Seq Seq
515 Seq A.F20C T, Seq
D3.F19A:SE D3.F19A:SE
C.F98C:SET
TT TT
T

04 August 2017 20
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

Seq B.F32A, Seq B.F32A,

516 Seq A.F20 Seq B.F32A F32A,F32B F32A,F32B F32A
Seq B.F32B Seq B.F32B

517 Seq A.F20C

Seq
Seq B.F19A, Seq B.F19A,
B.F98A:SET
Seq Seq
518 Seq A.F20C T, Seq
C3.F19A:SE C3.F19A:SE
B.F98C:SET
TT TT
T

Seq B.F98A,
519 Seq A.F20C
Seq B.F98C

Seq B.F98A,
524 Seq A.F20C
Seq B.F98C

526 Seq A.F20

Seq
Seq Seq Seq A.F98A:EXR
527 A.F20C:SE B.F19A:TRA B.F19A:TRA Q, Seq
ME A A A.F98C:EXR
Q

530 Seq A.F20C

535 Seq A.F20C

536 Seq A.F20C

537 Seq A.F20C

538 Seq A.F20C

Seq
B.F98A:SET
540 Seq A.F20C T, Seq
B.F98C:SET
T

Seq
Seq Seq B.F98A:SET Seq Seq
541 Seq A.F20C E3.F19A:SE E3.F19A:SE T, Seq E3.F19A:SE E3.F19A:SE
TT TT B.F98C:SET TT TT
T

04 August 2017 21
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

Seq
B.F98A:SET
542 Seq A.F20C T, Seq
B.F98C:SET
T

Seq
Seq Seq B.F98A:SET Seq Seq
543 Seq A.F20C E3.F19A:SE E3.F19A:SE T, Seq E3.F19A:SE E3.F19A:SE
TT TT B.F98C:SET TT TT
T

Seq
B.F98A:ESE
544 Seq A.F20C T, Seq
B.F98C:ESE
T

Seq
Seq Seq B.F98A:ESE
545 Seq A.F20C E3.F19A:ES E3.F19A:ES T, Seq
TT TT B.F98C:ESE
T

Seq
B.F98A:ESE
546 Seq A.F20C T, Seq
B.F98C:ESE
T

Seq
Seq Seq B.F98A:ESE
547 Seq A.F20C E3.F19A:ES E3.F19A:ES T, Seq
TT TT B.F98C:ESE
T

Seq
Seq Seq B.F98A:SET
548 Seq A.F20C B.F19A:SET B.F19A:SET T, Seq
T T B.F98C:SET
T

549 Seq A.F20C

04 August 2017 22
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

Seq
Seq Seq Seq A.F98A:EXR
558 A.F20C:SE B.F19A:TRA B.F19A:TRA Q, Seq
ME A A A.F98C:EXR
Q

F32G,F32M, F19,F32G,F
559 F20 F34A F19 F34A
F34A 32M,F34A

Seq
564 A.F20C:SE
ME

Seq
Seq D.F98A,
565 A.F20C:SE
Seq D.F98C
ME

Seq
Seq Seq Seq D1.F98A:PO
566 A.F20C:SE D2.F19B:PS D2.F19B:PS ST, Seq
ME TA TA D1.F98C:PO
ST

Seq
567 A.F20C:SE
ME

Seq
568 A.F20C:SE
ME

569 Seq A.F20C

575 Seq A.F20C

576 Seq A.F20C

Seq
Seq Seq B.F98A:SET Seq Seq
578 Seq A.F20C E3.F19A:SE E3.F19A:SE T, Seq E3.F19A:SE E3.F19A:SE
TT TT B.F98C:SET TT TT
T

581 F20 F34B F34B

586 Seq A.F20C

590 F20 F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D

04 August 2017 23
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

591 F20 F32B F32B F32B F32B

592 F20

595 F20

596 F20

598 F20

599 F20

F33G,F34P,
600 Seq A.F20 F33G F33G Seq B.F34P F34P,F34R F34P,F34R
F34R

F32B,F33B, F32B,F33B, F34P,F34R,

601 F20 F32B F32F F31G
F34P,F34R F34P,F34R F31G

604 F20 F30

605 F20 F30

606 F20 F30

607 F20 F30

F60F,F60M, F60F,F60M, F60F,F60M,

F62F, F62F, F62F,
608 F20
F62M,F64,F F62M,F64,F F62M,F64,F
65 65 65

F32B,F32H, F32B,F32H,
F34E, F34E,
620 F20 F32B F32B F30V F30V
F33B,F33E, F33B,F33E,
F71F F71F

670 Seq A.F20C

671 Seq A.F20C

690 F20 F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D

691 F20 F32B F32B F32B F32B

692 F20

695 F20

696 F20

04 August 2017 24
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

698 F20

699 F20

700 F20 F32B F32B F32B F32B

701 F20

705 F20 F32B F32B F32B F32B

F32B,F33B, F32B,F33B, F32B,F33B, F32B,F33B,

707 F20
F34B F34B F34B F34B

710 F20 F32B F32B F32B F32B

711 F20

720 F20 F32B F32B F32B F32B

721 F20

730 F20 F32B,F32D F32B,F32D F32D

732 F20 F32B F32B F32B F32B

F32A,F33A, F32A,F33A,
734 F20 F32A F32A F32A F32A,F33A
F33B F33B

740 F20 F32B F32B F32B F32B

F32B,F33B, F32B,F33B,
742 F20 F32B F32B F34A
F34A,F34B F34A,F34B

F32B,F33B, F32B,F33B, F32B,F33B, F32B,F33B,

747 F20
F34B F34B F34B F34B

F32B,F33B, F32B,F33B,
750 F20 F32B F32B
F34B F34B

F32B,F33A, F32B,F33A, F32B,F33A, F32B,F33A,

752 F20 F33A
F33B F33B F33B F33B

F32A,F32B, F32A,F32B,
754 F20 F32A,F32B F32A,F32B F32A F33B,F34A, F33B,F34A, F32A,F34A
F34B F34B

756 F20 F32B F32B F32B,F33A F32B,F33A F33A

760 F20

04 August 2017 25
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

767 F20

768 F20 F32B,F32D F32B,F32D F32D

F32B,F32D, F32B,F32D,
769 F20 F32D
F33B,F34B F33B,F34B

790 F20 F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D

791 F20 F32B F32B F32B F32B

792 F20

795 F20

796 F20

798 F20

799 F20

F32A,F33B, F32A,F33B,
800 F20 Seq B.F32A Seq B.F32A Seq B.F32A F32A
F34B F34B

801 F20 F33B F33B F33B,F34B F33B,F34B

802 F20 F32A F32A F32A F32A F32A F32A

824 F20 F68A F19 F68A F19,F68A

890 F20 F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D

891 F20 F32B F32B F32B F32B

892 F20

895 F20

896 F20

898 F20

899 F20

900 F20 F32A F32A F32A F32A F32A F32A

910 F20 F32A F32A F32A F32A F32A F32A

920 F20 F34F F34F

04 August 2017 26
Alliance Access 7.1.40
Release Letter Routing Keyword Extraction and Verifiable Fields

Keyword Verifiable field

MT
TRN Currency Amount Value Date Currency Amount Date

935 F20 F37H F30 F37H F30

F60F,F60M, F60F,F60M, F60F,F60M,

940 F20 F62F,F62M F62F,F62M F62F,F62M F62F,F62M, F62F,F62M, F62F,F62M,
F64,F65 F64,F65 F64,F65

F60F,F62F,F F60F,F62F,F
F60F,F62F,F
941 F20 F62F F62F F62F 64,F65,F90 64,F65,F90
64,F65
C,F90D C,F90D

F34F,F90C,F F34F,F90C,F
942 F20 F34F F34F
90D 90D

F60F,F60M, F60F,F60M, F60F,F60M,

950 F20 F62F,F62M F62F,F62M F62F,F62M F62F,F62M, F62F,F62M, F62F,F62M,
F64 F64 F64

F60F,F60M, F60F,F60M, F60F,F60M,

970 F20 F62F,F62M F62F,F62M F62F,F62M F62F,F62M, F62F,F62M, F62F,F62M,
F64 F64 F64

971 F20 F62F F62F F62F F62F F62F F62F

F60F,F60M, F60F,F60M, F60F,F60M,

972 F20 F62F,F62M F62F,F62M F62F,F62M F62F,F62M, F62F,F62M, F62F,F62M,
F64 F64 F64

973 F20

985 F20

986 F20

990 F20 F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D F32C,F32D

991 F20 F32B F32B F32B F32B

992 F20

995 F20

996 F20

998 F20

999 F20

(1) The value with the CANC qualifier will be extracted only if the function of the message (F23G) is equal to CANC.

04 August 2017 27
Alliance Access 7.1.40
Release Letter Switch-over Planning for Standards MT

B Switch-over Planning for Standards MT

The information contained in this appendix will help you in your planning for the switch-over to the
Standards MT November 2017. It lists in chronological order the actions that need to be taken.

B.1 Actions to be Taken Now

Assess the impact of the changed standards for your company (for example: Check whether you
either use any of the changed messages or will use any of the new messages. Check whether
back-office systems need an upgrade (for example).

B.2 Actions to be Taken as Soon as Possible

Complete these actions:
Update your Alliance Access server to release 7.1.40.
Install the relevant Web Platform Server-Embedded GUI packages and deployment packages.
Note Customers must install the Standards Release 2017 Message Management
Deployment Package at the latest on 19th November 2017.
If relevant, inform the Web Platform GUI packages users that they must use the new URL.
Assign the Standards MT November 2017 to your Test and Training logical terminals.
Upgrade back-office systems where required.

B.3 Actions to be Taken Before 18th November 2017

For the new/changed messages, train your staff and test your back-office systems by sending
messages to the Test and Training network.

B.4 Actions to be Taken on 15th, 16th, or 17th

November 2017 (Last Business Day of the Week)
Complete these actions:
Send your business messages as soon as possible.
At the end of your business week, make sure that all your pending messages are transmitted.
When your business week is finished, log out from the SWIFT network and log back in for
reception only. In this way, you can still receive and correctly process messages from other
correspondents.
Close all your "from" message partners and open all your "to" message partners. In this way, all
received messages can still follow automatic processing.
Note On 18th November 2017 at 16:00 GMT, SWIFT will disconnect all users and
activate the new Standards MT November 2017.

04 August 2017 28
Alliance Access 7.1.40
Release Letter Switch-over Planning for Standards MT

B.5 Actions to be Taken Before Your First Log In on

19th or 20th November 2017
Complete these actions:
Make sure that as many messages as possible have been processed by Alliance Access. This
means that only a few or even no live messages must be left in the system.
Assign the Standards MT November 2017 to all your live logical terminals.
Log in to SWIFT and activate all the message partners that you use normally.
Monitor your Alliance Access and back-office systems for correct behaviour (for example, check
all your templates for correct resolution).

B.6 Actions to be Taken after the First Login

Most of your FIN message templates will still be linked to the old Message Standards. Upon usage,
these templates will have to be resolved to be associated with the new standards, and might need
further changes before they are saved as templates again.

04 August 2017 29
Alliance Access 7.1.40
Release Letter Standards Switch-over Planning for InterAct Services

C Standards Switch-over Planning for InterAct

Services
The information contained in this appendix will help you in your planning for the switch-over to a
new version of ISO 20022 standards used by a specific InterAct service. It lists in chronological
order the actions that need to be taken.
Contrary to the FIN annual message standards cut-over, the introduction of new versions of ISO
20022 messages is not a big bang event, but provides a relatively long migration period, a period
which does not have the same length for every ISO 20022 InterAct service and is determined and
communicated by the service administrator.
To cater for this, ISO 20022 InterAct services typically support two versions of the standards in
parallel for a period of time.
The high level guidelines below can help you plan adoption of new versions for the ISO 20022
InterAct services, of which you are a member.

C.1 Actions to be Taken When You Are Notified of a

Service Change
If you are a member of an InterAct service that will adopt new ISO 20022 message standards, you
want to make an initial assessment of how this will impact your infrastructure. You should look into
the following areas, among others:
Understand what messages or message versions are added/removed from the service, and how
you use them
Establish if Alliance Access is used for manual processing of these messages (create, modify,
verify, authorise)
Establish if your Alliance Access routes messages based on message types or message
keywords
Validate the readiness of the impacted back office systems.

C.2 Get Ready for Testing

Normal practice on InterAct is to allow both the current version and the next version of a particular
message type for a particular service at the same moment in time.
It is important to understand that once a service is provisioned for a new version of a message
type, the service will accept from your correspondents both the new version of that message type
added to the service and the previous version of that message type allowed in the service, and will
send them to you. You cannot choose to not receive the new version of a message at the technical
level. In most cases however there will be a bilateral agreement or group guideline, about the date
as of which it is allowed to use the new version of the message, first for the pilot service and later
for the production service.
For message flows to or from your back-office, make sure that you have a clear view of when your
back-office will be capable of supporting the changes in message standards. By default Alliance
Access does not distinguish a new version of a message type from an old version and will process

04 August 2017 30
Alliance Access 7.1.40
Release Letter Standards Switch-over Planning for InterAct Services

all messages through the routing you set up to distribute the messages to your back office. So it is
important that you know how your back office will behave when receiving new message versions for
the pilot service.
In order to allow manual processing (create, modify, verify, authorise), and printing in human
readable format, you need to download the appropriate message standards Deployment Package
from the download centre on www.swift.com or from mystandards.swift.com. If you are using
specific usage guidelines for the service, also download the usage guideline specific deployment
package from mystandards.swift.com.
From the Alliance Access Configuration GUI package, install the new deployment packages. If a
previous version of the deployment package was installed, the installation process will mark all
messages types for that service as obsolete, and merge the message types from the new
deployment package with this. As a result of this process, all message types already loaded, and
no longer occuring in the latest deployment package will still be there and marked as obsolete,
while all messages in the latest deployment package will be marked as not obsolete and will be
available to the users. If there were some messages that should not be used by your users, you
can mark these manually as obsolete to prevent message creation. The release letters of the
deployment packages provide the details of what message versions are included in the deployment
package.
If you have usage guidelines installed, you need to do the same for each usage guideline linked to
the same service. It is possible that a specific usage guideline does not yet support the new
message standards version, and will not have an updated deployment package. For more
information, contact the publisher of the usage guideline.
In case you have created manually defined verifiable fields for a message in this service that got a
new version, you will need to configure the new version of the message to also have the
appropriate verifiable fields.
Once the deployment package is installed, the new message standard can be used both for the
production and all pilot/test versions of the service. If one of your users would create a message
using the new version before it has been activated on the SWIFT network a NACK will be returned.
If you try to create a message using a template that is linked to an obsolete message version,
Alliance Access will automatically try to convert it to the latest version available.
When no manual processing or human readable printing is required, the deployment package
installation is not necessary.

C.3 Migrate to the New Standards

Once the new message standards have been activated for the service you will typically be able to
use both the previously allowed version and the new version for a period of time. Keep in mind
however that while you can choose which versions you send (in agreement with your
correspondent), you may receive new versions of the messages on the production service.
You will need to inform your users who manually process messages about which message to use
and when.

C.4 Wind Down Use of the Old Standards

Once the new message version is in use you have entered a migration period where both versions
are available. When the end-of-support of an older message version is announced, you can start

04 August 2017 31
Alliance Access 7.1.40
Release Letter Standards Switch-over Planning for InterAct Services

monitoring usage to make sure that you have no business need for the old version by the time that
the message version reaches end-of-support.
In order to enforce the usage of the latest message version during manual processing you can use
the Alliance Access Configuration GUI package to configure the message version as obsolete.
During this period, however, your back-office systems are expected to still be capable of processing
older message versions until they are removed from the service.

C.5 Stop Using the Old Standard

Old versions of messages standards would typically be removed during a subsequent update of the
service, which would bring you back to Actions to be Taken When You Are Notified of a Service
Change on page 30.
As long as you add new deployment packages for a specific service, you will keep track of
obsoleted message versions which means you will still be able to see messages using that old
message version in a human readable form. If you remove the old deployment package before
adding the new one, you will lose the information on obsolete messages and an attempt to display/
print them would result in a printout that is in an XML style format.

04 August 2017 32
Alliance Access 7.1.40
Release Letter Legal Notices

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

04 August 2017 33