SWIFT 2019 Installation Notes (Treasury)

Version 1.0

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.

© 2019 Temenos Headquarters SA - all rights reserved.

Table of Contents

Table of Contents .................................................................................................................................... 2

Document History .................................................................................................................................... 3
1. Introduction ...................................................................................................................................... 4
2. Update Details ................................................................................................................................. 4
3. Installation Process .......................................................................................................................... 4
3.1 Updates ...................................................................................................................................... 4
3.2 Installation of SWFT19 Module ............................................................................................... 5
3.3 SPF ............................................................................................................................................. 5
3.4 SWIFT.PARAMETER table ......................................................................................................... 6
3.5 Post installation of Updates ......................................................................................................... 7
4. New Functionality ............................................................................................................................. 7
4.1 Overview of Swift 2019 changes for Treasury............................................................................... 7
4.2 Local Reference configuration ....................................................................................................... 8
4.3 DE.TRANSLATION ..................................................................................................................... 14
4.4 DE.MESSAGE ............................................................................................................................. 16
4.4 DE.MAPPING .............................................................................................................................. 18
4.5 DE.FORMAT.SWIFT of 300.1.1 ............................................................................................ 19
4.7 EB.ERROR .................................................................................................................................. 23
4.8 SWIFT.CODE.WORDS ............................................................................................................... 24
5 MT 300 generated on various events ............................................................................................. 29
5.1.1 New deal input-FX ................................................................................................................ 29
5.2.1 Amendment-FX ..................................................................................................................... 34
5.2.2 Rate fixing-ND....................................................................................................................... 36
6. Contact Details ........................................................................................................................... 37
Document History

Author Version Date

Temenos 0.1 22/08/19

Comments:

Initial Version
1. Introduction
This document explains the installation process for Swift 2019 changes for MT 300
message for Treasury module.

2. Update Details
The following table contains details of the updates that are required to be installed for the
Swift 2019 changes.

Release Module Updates

R17_DE_Outward_17
R17 DE R17_DE_Config_17
R17_DE_API_10

R17 FX R17_FX_Delivery_7

201603 DE 201603_DE_Outward_17
201603_DE_Config_20
201603_DE_API_7

201603 FX 201603_FX_Delivery_2

201507 DE 201507_DE_Outward_11
201507_DE_Config_9
201507_DE_API_2

201507 FX 201507_FX_Delivery_4

201608 DE 201608_DE_Outward_3
201608_DE_Config_6
201608_DE_API_2

201608 FX 201608_FX_Delivery_6

Note: DE changes are pre-requisite to FX changes, so the functionality is enabled only when both the
updates are available.
In addition to the above updates, the activation of the changes will also be dependent on the
installation of the SWFT19 Module; please contact your account manager.
Releases prior to R19 are subject to a fixed price charge; please contact your account manager for
further details

3. Installation Process
The following process should be followed to install the Swift 2019 changes.

3.1 Updates
Please refer to the table above which contains details of the updates that are required per
release. The standard updates installation process should be followed.
3.2 Installation of SWFT19 Module
Since SWFT19 is a new module and standard instructions for installing a new module should be
followed which includes adding the module in T24 SPF application. Please follow the below steps
one by one before downloading the updates from TCSP portal.

Figure 1 – EB.PRODUCT screenshot

Once the updates have been installed into the system, the SWFT19 module is required to be
installed. The standard instructions for installing a new module should be followed. These are detailed
below for quick reference.
Note: For R19 release SWFT19 Installation is not required and the other configuration remains the
same.

3.3 SPF
Add the new product to the PRODUCTS field on the SPF (System Parameter File). In the
following field, PRODUCT.CODES, enter the product code you have been given. Authorise the
record.
 Figure 2 – SPF screenshot

3.4 SWIFT.PARAMETER table

A record needs to be created in the new table SWIFT.PARAMETER with a record id as “SYSTEM” with
the field CURR.SWIFT.REL as “2019”. Once this has been authorised the Swift 2019 change will be
active. Please note that 2019 is dependent on 2018. If 2018 is not configured earlier, configure 2018
and then configure 2019.

Figure 3 – SWIFT.PARAMETER screen shot

Note: In the live environment this should be done on the date that you require these changes to be
live

3.5 Post installation of Updates

The exception records released in EB.ERROR need to be authorized.
Note: Please do the below setup initially in the test environment and then in the live environment after
confirmation of test results.

4. New Functionality
4.1 Overview of Swift 2019 changes for Treasury
The following changes have been made for MT 300 message type for FX and ND.
Please note the confirmation messages for ND is supported from 201411 onwards.
• SWIFT 2019 changes mandate the removal of usage of Option D and enable the usage of Option
J in the following tags and sequences in MT300:
• However, the tags 53A on B1 sequences and 58a on B2 sequences are not supported in FX
whereas 58a on B2 sequence is not supported in ND.
• Currently, system doesn’t support the usage of option J for any of the following tags.

MT300 Foreign Exchange Confirmation

Status Tag Field Name Content/Options No.
Mandatory Sequence A General Information
M 82a Party A A, D, or J 10
M 87a Party B A, D, or J 11
O 83a Fund or Beneficiary Customer A, D, or J 12
Mandatory Subsequence B1 Amount Bought
O 53a Delivery Agent A, D, or J 29
O 56a Intermediary A, D, or J 30
M 57a Receiving Agent A, D, or J 31
Mandatory Subsequence B2 Amount Sold
O 53a Delivery Agent A, D, or J 33
O 56a Intermediary A, D, or J 34
M 57a Receiving Agent A, D, or J 35
O 58a Beneficiary Institution A, D, or J 36
As per the 2019 mandate, the option J should be enabled and option D should be removed for the
below tags for MT 300 confirmation message.

MT300 Foreign Exchange Confirmation

Status Tag Field Name Content/Options No.
Mandatory Sequence A General Information
M 82a Party A A or J 10
M 87a Party B A or J 11
 Mandatory Subsequence B1 Amount Bought
O 56a Intermediary A or J 30
M 57a Receiving Agent A or J 31
Mandatory Subsequence B2 Amount Sold
O 53a Delivery Agent A or J 33
O 56a Intermediary A or J 34
M 57a Receiving Agent A or J 35

4.2 Local Reference configuration

4.2.1 Additional information for option J
A new field in FX.PARAMETERS and ND.PARAMETER should be added as local reference fields to
support the option J with additional information like BIC, LEI as described below:

Field Name

DEFAULT.OPTIONJ

When set to “YES”, the following codes will be auto populated in the swift message as applicable.
▪ ABIC – BIC.CODE from DE.BIC application.
▪ ACCT – The account number
▪ LEIC – LEGAL.ENTITY.ID from OC.CUSTOMER application.
▪ TXID – First value of the multi-value field TAX.ID from CUSTOMER
application
▪ CLRC – The clearing code if available in the CLEAR.CODE field in the
AGENCY record

Figure 4 – LOCAL.TABLE for DEFAULT.OPTIONJ screen shot

 Figure 5 – LOCAL.REF.TABLE for FX.PARAMETERS screen shot

Figure 6 – LOCAL.REF.TABLE for ND.PARAMETER screen shot

4.2.2 Mapping for Correspondence and Intermediary Name/City

The value for TAG 56J and 57J is mapped through LRF field, hence it must be configured as
shown below:
New fields should be added as local reference fields in ND.DEAL and FOREX template.

T24 Field
CPY.COR.NAME
CPY.COR.CITY
INTERMD.NAME
INTERMD.CITY
Figure 7 – LOCAL.TABLE for CPY.COR.NAME screen shot

Figure 8 – LOCAL.TABLE for CPY.COR.NAME screen shot

Figure 9 – LOCAL.TABLE for CPY.COR.NAME screen shot

Figure 10 – LOCAL.TABLE for CPY.COR.NAME screen shot

Figure 11 – LOCAL.REF.TABLE for FOREX screen shot

Figure 12 – LOCAL.REF.TABLE for ND.DEAL screen shot

The validation for the LRF field must be configured by the clients. A sample validation routine and
steps are as below:
1. A sample validation routine for LRF

ND.VALIDATE.SWIFT.FIELDS.b FX.VALIDATE.SWIFT.FIELDS.b

2. Create EB.API record

The client must be configured the EB.API record. The Source type should be “Basic”
for the validation routines.

Figure 13 – EB.API for ND.VALIDATE.SWIFT.FIELDS screen shot

Figure 14 – EB.API for FX.VALIDATE.SWIFT.FIELDS screen shot

3. Attach the routine as validation routine to either newly created version or already existing
version provided that above mentioned new fields is being added.
4.3 DE.TRANSLATION
To define the tags with option J in DFS, the tags should be defined in DE.TRANSLATION

Figure 15 - DE.TRANSALTION for SW87J

Figure 16 - DE.TRANSALTION for SW82J

Figure 17 - DE.TRANSALTION for SW56J

Figure 18 - DE.TRANSALTION for SW53J

 Figure 16 - DE.TRANSALTION for SW57J

4.4 DE.MESSAGE

1. In DE.MESSAGE of 300, a new field SELL and BUY to be introduced.

2. A new field INTERM SELL ACC has a length of 35, Single Multi as “M” and Mandatory as
“No”.
3. A new field INTERM BUY ACC has a length of 35, Single Multi as “M” and Mandatory as
“No”.
4. A new field INTERM BUY CUS has a length of 35, Single Multi as “M” and Mandatory as
“No”.

Figure 17.1 - DE.MESSAGE for 300

5. We have to change the Single Multi field as “M” for the below fields.

▪ ACCT WITH BANK ACC .

Figure 17.2 - DE.MESSAGE for 300

• SENDER BANK ACC.

Figure 17.3 - DE.MESSAGE for 300

• ACCT SELL ACC.

Figure 17.4 - DE.MESSAGE for 300

• BUYER BANK ACC.

Figure 17.5 - DE.MESSAGE for 300

6. We have to change the Mandatory field as “NO” for the below fields.
 • ACCT WITH BANK CUS.

Figure 17.6 - DE.MESSAGE for 300

• ACCT SELL ACC.

Figure 17.7 - DE.MESSAGE for 300

• INTERM BUY CUS

Figure 17.8 - DE.MESSAGE for 300

4.4 DE.MAPPING

In DE.MAPPING of 300.FX.1, the new field INTERM BUY CUS should be mapped to 2.34.2
and INTERM BUY ACC should be mapped to 2.34.3.

Figure 18 - DE.MAPPING for 300.FX.1

 In DE.MAPPING of 300.ND.1, the field INTERM BUY CUS should be mapped to 5.26.3 and
INTERM BUY ACC should be mapped to 5.26.2.

Figure 19.1 - DE.MAPPING FOR 300.ND.1

1. The new field INTERM SELL ACC should be mapped to 5.33.2.

2. The existing field INTERMEDIARY SELL should be mapped to 5.33.3.

Figure 1921 - DE.MAPPING FOR 300.ND.1

3. The existing field INTERMEDIARY BUY should be mapped to 5.26.1.

Figure 19.3 - DE.MAPPING FOR 300.ND.1

4.5 DE.FORMAT.SWIFT of 300.1.1

1. The existing tags with option A as mentioned below should be replaced as tags with option J.
2. The formatting logic of the tags should be modified. The ACC and C/D conversion should be
removed.
3. The new tag should be defined with the field name meant for customer which also includes
CUS *J conversion.

TAG-82
1. Change the Tag 82 A to 82J.
2. Remove the Party A C/D and PARTY A ACC fields.
3. The Tag 82J to be expanded to include both PARTY A ACC and PARTY A CUS for the same
tag.
4. Change the PARTY A CUS field conversion as CUS*J.
 Figure 20.1 - DE.FORMAT.SWIFT for 300.1.1

TAG-87
1. Change the Tag 87 A to 87J.
2. Remove the Party B C/D and PARTY B ACC fields.
3. The Tag 87J to be expanded to include both PARTY A ACC and PARTY A CUS for the same
tag.
4. Change the PARTY B CUS field conversion as CUS*J.

Figure 20.2 - DE.FORMAT.SWIFT for 300.1.1

TAG-53 On B1
1. Change the Tag 53A to 53J.
2. Remove the BUYER C/D and BUYER BANK ACC fields.
3. The Tag 53J to be expanded to include both BUYER BANK ACC and BUYER BANK CUS for
the same tag.
4. Change the BUYER BANK CUS field conversion as CUS*J.
 Figure 20.3 - DE.FORMAT.SWIFT for 300.1.1

TAG-56 On B1
1. Change the Tag 56A to 56J.
2. Remove the INTERM BUY C/D and INTERM BUY ACC fields.
3. The Tag 56J to be expanded to include both INTERM BUY ACC and INTERM BUY CUS for
the same tag.
4. Change the INTERM BUY CUS field conversion as CUS*J.

Figure 20.4 - DE.FORMAT.SWIFT for 300.1.1

TAG-57 On B1
1. Change the Tag 57A to 57J.
2. Remove the ACCT WITH C/D and ACCT WITH BANK ACC fields.
3. The Tag 57J to be expanded to include both ACCT WITH BANK ACC and ACCT WITH
BANK CUS for the same tag.
4. Change the ACCT WITH BANK CUS field conversion as CUS*J.
 Figure 20.5 - DE.FORMAT.SWIFT for 300.1.1

TAG-53 On B2
1. Change the Tag 53A to 53J.
2. Remove the SENDERS C/D and SENDER BANK ACC fields.
3. The Tag 53J to be expanded to include both SENDER BANK ACC and SENDER BANK CUS
for the same tag.
4. SENDER BANK CUS field includes CUS*J conversion.

Figure 20.6 - DE.FORMAT.SWIFT for 300.1.1

TAG-56 On B2
1. Change the Tag 56A to 56J.
2. Remove the INTERMEDIARY SELL.
3. The Tag 56J to be expanded to include both INTERM SELL ACC and INTERMEDIARY SELL
for the same tag.
4. Change the INTERMEDIARY SELL field conversion as CUS*J.
 Figure 20.7 - DE.FORMAT.SWIFT for 300.1.1

TAG-57 On B2
1. Change the Tag 57A to 57J.
2. Remove the ACCT SELL C/D and ACCT SELL ACC.
3. The Tag 57J to be expanded to include both ACCT SELL ACC and ACCT SELL CUS for the
same tag.
4. Change the ACCT SELL CUS field conversion as CUS*J.

Figure 20.8 - DE.FORMAT.SWIFT for 300.1.1

4.7 EB.ERROR
The below records are introduced to ensure that all the required updates are available in the system
thereby the functionality of SWIFT 2019 changes are enabled.
 Figure 21 – EB.ERROR for FX-SWIFT-2019.EXISTS

Note: The swift 2019 changes will be enabled only when both FX and DE updates are available.

4.8 SWIFT.CODE.WORDS
The following swift codes needs to be configured in SWIFT.CODE.WORDS which is used to support
option J.

Figure 22.1 – SWIFT.CODE.WORDS for ABIC

Figure 22.2 – SWIFT.CODE.WORDS for ACCT

Figure 22.3 – SWIFT.CODE.WORDS for LEIC

Figure 22.4 – SWIFT.CODE.WORDS for TXID

Figure 22.5 – SWIFT.CODE.WORDS for CLRC

Figure 22.6 – SWIFT.CODE.WORDS for UKWN

Figure 22.7 – SWIFT.CODE.WORDS for ADD1

Figure 22.8 – SWIFT.CODE.WORDS for ADD2

 Figure 22.9 – SWIFT.CODE.WORDS for CITY

Figure 22.10 – SWIFT.CODE.WORDS for NAME

 Figure 22.11 – SWIFT.CODE.WORDS for NOSI

5 MT 300 generated on various events

The MT 300 messages generated on various stages for FX and ND.

5.1.1 New deal input-FX

Figure 23.1 – Forex for 300 advice
5.1.2 New deal input-ND
Figure 23.2 – ND.DEAL for 300 advice
5.2.1 Amendment-FX
Figure 23.3 – Forex for 300 –amendment advice
5.2.2 Rate fixing-ND
 Figure 23.4 – ND.DEAL for 300 –Rate fixed advice

6. Contact Details

Area Product Manager Contact Address

General SWIFT questions, Lisa Hall mlhall@temenos.com

payment and utility messages