SWIFT Standards 2015 Annual Maintenance

SWIFT Standards MT November 2015
TEMENOS T24
SWIFT 2015 Installation Notes
Version 6.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.
TEMENOS Confidential Page 1 SWIFT Standards 2015 Installation notes.docx
2010 Temenos Headquarters SA - all rights reserved.
Version Date Author Amendment

V1.0 25/08/2015 Temenos First publication
V2.0 09/09/2015 Temenos Additional Update details added
V3.0 17/09/2015 Temenos Section 4.3 Overview of the solution for supporting
TAG59F changes added and an example
V4.0 18/09/2015 Temenos Section 2 updated with additional update details in
table
Section 4.5 New
Details added for Swaps and FX messages
table
table
Updated Section 4.3.1 new table with local
references required for R07 R08 and R09
Updated Section 4.3.3 added releases R07 R08 and
R09


Table of Contents
1 Introduction .................................................................................................................................... 5
2 Update Details ................................................................................................................................ 5
3 Installation Process ....................................................................................................................... 8
3.1 Updates ................................................................................................................................ 8
3.2 Installation of S5 Module ...................................................................................................... 8
3.2.1 SPF .................................................................................................................................... 8
3.2.2 COMPANY ......................................................................................................................... 9
3.2.3 T24.UPGRADE Service ..................................................................................................... 9
3.3 SWIFT.PARAMETER table ................................................................................................ 10
4 New functionality ......................................................................................................................... 11
4.1 Overview of Swift 2015 changes ........................................................................................ 11
4.2 SWIFT.PARAMETER......................................................................................................... 11
4.2.1 Example Restricted currency ........................................................................................ 12
4.3 Overview and Setup for TAG59F ....................................................................................... 14
4.3.1 Funds Transfer ................................................................................................................. 15
4.3.2 Standing Order ................................................................................................................. 18
4.3.3 Example Tag 59F ............................................................................................................. 20
4.3.3.1 Funds Transfer Outward ........................................................................................... 20
4.3.3.2 FT Inward Tag 59F ....................................................................................................... 21
4.4 Swift Ref ............................................................................................................................. 23
4.4.1 Identify using OFFICE TYPE ........................................................................................... 23
4.4.2 Identify using Group type ................................................................................................. 24
4.4.3 Default identification ......................................................................................................... 24
4.5 Forex/Swap MT360 & MT361 ............................................................................................ 24
4.5.1 Configuration .................................................................................................................... 25
4.5.1.1 Forex ............................................................................................................................ 25
4.5.1.2 Swap............................................................................................................................. 29
5 Further Information ...................................................................................................................... 34
5.1 Contact Details ................................................................................................................... 34

1 Introduction
This document contains the installation process for the Swift 2015 changes.
2 Update Details
The following table contains details of the updates that are required to be installed for the Swift 2015
changes
Release Dependant Expected Module Updates

Module available
date
R10 S5 26th August DE Changes T24Update R10_DE_Outward_17

T24Update R10_FT_Contract_68
2015
T24Update R10_FT_Delivery_5
IBAN Changes T24Update R10_IN_IbanAPI_5
T24Update R10_IN_Config_6
Payment changes T24Update R10_AC_PaymentNetting_4

T24Update R10_DE_Outward_18
T24Update R10_DE_Messaging_5
T24Update R10_DE_Inward_5
T24Update R10_DE_ModelBank_29
T24Update R10_FT_StandingOrders_26
18 September Forex R10_FX_Contract_38

2015
18th September Swaps R10_SW_Delivery_14
2015
R11 S5 31st August T24Update R11_DE_Outward_14
2015 DE Changes T24Update R11_FT_Delivery_3
IBAN Changes T24Update R11_IN_Config_3

T24Update R11_IN_IbanAPI_3
T24Update R11_AC_PaymentNetting_5
Payment changes T24Update R11_DE_Inward_2
T24Update R11_DE_ModelBank_11
18th Sept 2015 Forex R11_FX_Contract_23
18th Sept 2015 Swaps R11_SW_Delivery_6
R12 S5 4-Sep-2015 DE Changes T24Update R12_DE_Outward_2

IBAN Changes T24Update R12_IN_Config_3

T24Update R12_IN_IbanAPI_3

Payment Changes T24Update R12_AC_PaymentNetting_5

R13 SF & S5 4-Sep-2014 DE Changes T24Update R13_DE_Outward_7


Payment changes T24Update R13_AC_PaymentNetting_3

23rd Oct 2015 Swaps R13_SW_Delivery_3
AMR14 SF & S5 2-Sep-2015 DE Changes T24Update R14_FT_Contract_14


Payment Changes T24Update R14_AC_PaymentNetting_2

AMR15 SF & S5 TBC DE Changes TBA
IBAN Changes TBA
Payment changes
23rd Oct 2015 Forex R15_FX_Contract_1
23rd Oct 2015 Swaps R15_SW_Delivery_1

R15_SW_Contract_1
201408 SF & S5 28-Aug-2015 DE Changes T24Update 201408_DE_Outward_5
T24Update 201408_FT_Delivery_1

T24Update 201408_FT_Contract_16
IBAN Changes T24Update 201408_IN_IbanAPI_1
Payment changes T24Update 201408_AC_PaymentNetting_1

T24Update 201408_DE_Outward_6
T24Update 201408_DE_Inward_6
T24Update 201408_DE_Messaging_4
T24Update 201408_FT_StandingOrders_13
Forex 201408_FX_Contract_11
Swaps 201408_SW_Delivery_2
201407 SF & S5 4-Sep-2015 DE Changes T24Update 201407_DE_Outward_1


T24Update 201407_IN_Config_2
Payment changes T24Update 201407_AC_PaymentNetting_1

23rd Oct 2015 Forex 201407_FX_Contract_2

rd
23 Oct 2015 Swaps 201407_SW_Delivery_2
201412 SF & S5 4-Sep-2015 DE Changes T24Update 201412_DE_Outward_1


T24Update 201412_IN_Config_2
Payment Changes T24Update 201412_AC_PaymentNetting_1

18th Sept 2015 Forex 201412_FX_Contract_2
18th Sept 2015 Swaps 201412_SW_Delivery_2
201507 SF & S5 20 Sept 2015 Swaps 201507_SW_Contract_1

201507_SW_Delivery_1
18th Sept 2015 Forex 201507_FX_Contract_2
18th Sept 2015 DE T24Update 201507_DE_Outward_1

18th Sept 2015 IBAN T24Update 201507_IN_Config_1

T24Update 201507_IN_IbanAPI_1
18th Sept 2015 Payments T24Update 201507_AC_PaymentNetting_1

T24Update 201507_AC_StandingOrders_2
For Release R07 R08 and R09 please contact your account manager.
Note In addition to the above updates the activation of the changes will also be dependent on the
installation of the S5 Module; please contact your account manager.
As previously advised releases prior to R13 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 2015 changes.
3.1 Updates
Please refer to the table above which contains details of the updates that are required per release. The
standard updated installation process should be followed.
For clients on Release R13 or above both the SF and S5 modules are required to be installed in the
system.
3.2 Installation of S5 Module

Once the updates have been installed into the system, the S5 module is required to be installed. The
standard instructions for installing a new module should be followed. These are detailed below for
quick reference.
3.2.1 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.

Install a new Product ID and Product Code
3.2.2 COMPANY
Add the new product to the APPLICATIONS field on the COMPANY file. When the upgrade service is
running each COMPANY record is checked to see what products are installed; updates are released
for any existing products or when installing a new product the required files are created and any
records for that new product are released. Most new products will have files created even if no records
are released so updating the COMPANY record(s) is a vital step.
3.2.3 T24.UPGRADE Service
The TSA.SERVICE T24.UPGRADE is also used to add new products to T24. Before running the
service the BATCH record associated with the service (E.G BNK/T24.UPGRADE) needs to have the
product code(s) added to the DATA field. It is recommended that once the product(s) have been
installed that the BATCH record is amended again to clear the DATA field ready for the next upgrade.

DATA field on BATCH record updated with new product codes
Once the BATCH record is authorised the T24.UPGRADE service can be run.
The same post install actions need to be taken as in a full release upgrade.
3.3 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 2015. Once this has been authorised the Swift 2015 change will
be active.
Note: In the live environment this should be done on the date that you require these changes to
be live
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 2015 changes
The following enhancements have been made to T24 to
Provide the ability to restrict certain currencies from being used in specific payment
messages
Support TAG59F
IBAN - Provide the ability to identify a Unique National ID
4.2 SWIFT.PARAMETER
A new table SWIFT.PARAMETER is introduced providing the following functionality.
Provision to restrict certain currencies from being used in specific message types
Allow the activation of the new changes in the environment on a specific date
The following screen shows the SWIFT.PARAMETER table.

The fields CURR.SWIFT.REL is used to define what the latest swift standards are live in the system,
and used to trigger the changes.
Whereas, the field PREV.SWIFT.REL, will in future hold the previous swift standards that have been
installed in the system.
The fields RESTRICTED.CCY and MESSAGE.TYPE are used to define currencies that are restricted
from being used in certain message types.
For example precious metals are restricted to the MT6xx series messages. The following example
shows the currency code XAU being restricted for MT101 message types.
If a restricted currency is entered into a transaction, where the field SEND.PAYMENT is set to Yes;
the system checks for the restriction of the currency for both the debit and credit in the
SWIFT.PARAMETER table; if the currency is restricted, a corresponding override is generated.
Should the override be accepted the payment message is moved to the REPAIR queue when the
formatting service SWIFT.OUT is run.

4.2.1 Example Restricted currency

A funds transfer is entered for a restricted currency. The field SEND.PAYMENT is set to Yes in the
Funds Transfer.
An override has been generated by the system and subsequently accepted by the user.

The DE.O.HEADER record is moved to repair when the SWIFT.OUT Service is run.

4.3 Overview and Setup for TAG59F

In order to support TAG 59F, additional fields are required within the following applications
Funds Transfer Capture Outward Tag 59F value
o BEN.NAME Beneficiary Name
o BEN.ADDRESS Beneficiary Address
o BEN.COUNTRY Country code of the beneficiary, must be a valid record in
the Country table
o BEN.TOWN Beneficiary Town
Funds Transfer Capture Inward Tag 59F values
o IN.BEN.NAME This no input field is used to capture the Incoming
Beneficiary Name from Tag 59F

o IN.BEN.ADDRESS This no Input field is used to capture the Incoming

Beneficiary Address from Tag 59F
o IN.BEN.COUNTRY This no input field is used to capture the Incoming
Beneficiary Country from Tag 59F
o IN.BEN.TOWN - This no input field is used to capture the Incoming
Beneficiary Town from Tag 59F
Note For an incoming message the values for TAG59F are initially captured in these fields. However
when a payment is redirected outside the bank, they will subsequently mapped to the relevant outward
Tag 59F fields when generating an outward MT103/202.
Standing Order - Capture Outward Tag 59F values
the Country table
Netting Entry - Capture Outward Tag 59F values
the Country table
Beneficiary
The following existing fields in the Beneficiary table are used to default the fields into Funds
Transfer
o BEN.NAME.1/BEN.SHORT.NAME.1
o BEN.STREET.ADDR
o BEN.TOWN.COUNTRY
o BEN.POST.CODE
When a user enters a BENEFICIARY.ID into a Funds Transfer or Standing order, the
details from the above fields are mapped to the newly added corresponding fields in
the applications.
Depending on the T24 release that is being installed this may be a combination of core fields
released in the updates and local reference fields. Where local references are required to be
configured for a release the details are provided below.
4.3.1 Funds Transfer

This setup is required for the releases R10, R11, R12, R13, R14, 201407, 201408,
201412, R15 and 201507.
For the Funds Transfer module the following four local reference fields are required to be
added to the application
IN.BEN.NAME.59F
IN.BEN.ADD.59F

IN.BEN.CNTY.59F
IN.BEN.TOWN.59F
1. Create four new records in LOCAL.TABLE with id as given below

2. Add the above LOCAL.TABLEs to the FUNDS.TRANSFER" record in the table

LOCAL.REF.TABLE. As shown in the screen shot below.
Note for Releases R07, R08 and R09 the following LOCAL.REFERENCE fields are required to be
configured in FUNDS.TRANSFER
R07 R08 R09

FT.BEN.NAME.59F(Multi value) FT.BEN.NAME.59F(Multi value) FT.BEN.NAME.59F(Multi value)
FT.BEN.ADDR.59F(Multi value) FT.BEN.ADDR.59F(Multi value) FT.BEN.ADDR.59F(Multi value)
FT.BEN.CTRY.59F(Single) FT.BEN.CTRY.59F(Single) FT.BEN.CTRY.59F(Single)
FT.BEN.TOWN.59F(Multi value) FT.BEN.TOWN.59F(Multi value) FT.BEN.TOWN.59F(Multi value)
FT
IN.BEN.NAME.59F(Multi value) IN.BEN.NAME.59F(Multi value) IN.BEN.NAME.59F(Multi value)
IN.BEN.ADD.59F(Multi value) IN.BEN.ADD.59F(Multi value) IN.BEN.ADD.59F(Multi value)
IN.BEN.CNTY.59F(Single) IN.BEN.CNTY.59F(Single) IN.BEN.CNTY.59F(Single)
IN.BEN.TOWN.59F(Multi value) IN.BEN.TOWN.59F(Multi value) IN.BEN.TOWN.59F(Multi value)

4.3.2 Standing Order

This setup is required for the releases R07, R08, R09, R10, R11, R12, R13, R14 and 201407
only.
For the Standing Order module the following four local reference fields are required to be
added to the application
BEN.NAME.59F
BEN.ADDRESS.59F
BEN.COUNTRY.59F
BEN.TOWN.59F
2. Create four new records in LOCAL.TABLE with id as given below

2. Add the above LOCAL.TABLEs to the STANDING.ORDER" record in the table

LOCAL.REF.TABLE. As shown in the screen shot below.

4.3.3 Example Tag 59F
4.3.3.1 Funds Transfer Outward

The following screen shot shows the new fields in Funds transfer where the data has been
entered which will be included in Tag 59F
BEN.NAME Abdul Kalam
BEN.ADDRESS APJ KALAM
BEN.COUNTRY - DE
BEN.TOWN KALAM TOWN

Below is a preview of the outgoing message with the fields mapped to Tag 59F.
4.3.3.2 FT Inward Tag 59F
An inward message is updated in the system. The following fields are populated with the
relevant data from the inward message from Tag 59F
IN.BEN.NAME
IN.BEN.ADDRESS
IN.BEN.COUNTRY
IN.BEN.TOWN


4.4 Swift Ref

Bank Directory Plus may contain duplicate NATIONAL IDs for some financial institutions. These cases
are deliberate when the financial institution decides that having individual branch NATIONAL ID is
irrelevant for payments.
However, you may need to identify one unique record in a set of records sharing a NATIONAL
ID for two purposes:
to identify the main or the most important entity amongst the duplicates
to find the BIC related to the duplicate NATIONAL IDs
If a set of records shares an identical NATIONAL ID, and you must identify the main record
(that is, the most important), and you do not have its address
T24 has been enhanced to use the following logic when locating a unique National ID which is
subsequently then used in T24 to derive the BIC from the IBAN
1. Check if any of the records have been defined with the OFFICE.TYPE as HO (Head Office)
where only one record has been defined as HO then the system will use this if not
2. Check if any of the records have been defined with GROUP.TYPE set as PARENT if only
one record has been set as Parent the system will use this
3. Should T24 not be able to identify a unique record using either the OFFICE.TYPE or
GROUP.TYPE it will select the first record in the list.
Please see the following examples
4.4.1 Identify using OFFICE TYPE

If in the set of records the OFFICE TYPE hierarchy specifies the most important record, then
use that record.
The following example shows a set of records where one record is a Head Office and the
others are Domestic Branches:
RECORD KEY OFFICE PARENT OFFICE KEY NATIONAL ID INSTITUTION NAME STREET ADDRESS 1
OFFICE TYPE
BD0000000ABW DB BD0000000ACR 12000 UNICREDIT BANK Wienerstrasse 24
AUSTRIA AG
BD0000000ACR HO BD0000000ACR 12000 UNICREDIT BANK Schottengasse 6-8

AUSTRIA AG
BD0000000ACA DB BD0000000ACR 12000 UNICREDIT BANK Sparkassaplatz 1

AUSTRIA AG
In this example T24 will use the record BD0000000ACR as this is the only record with the OFFICE TYPE
defined as HO.
RECORD KEY OFFICE PARENT OFFICE KEY NATIONAL ID INSTITUTION NAME STREET ADDRESS 1
OFFICE TYPE
BD0000000ACR HO BD0000000ACR 12000 UNICREDIT BANK Schottengasse 6-8
AUSTRIA AG

4.4.2 Identify using Group type

If the OFFICE TYPE hierarchy cannot be used, then use the GROUP TYPE hierarchy.
The following example shows a set of records where one record is a Parent and the others are
either Members or are not specified. Use the Parent as the most important.
RECORD KEY OFFICE GROUP TYPE COUNTRY NATIONAL ID INSTITUTION NAME

TYPE CODE
BD0000000JB5 HO Parent US 11300595 CAMBRIDGE TRUST COMPANY
BD000000A1DT HO US 11300595 CAMBRIDGE TRUST COMPANY OF
NEW HAMPSHIRE
In this example T24 would use record BD0000000JB5 as this record is the only record with the
GROUP.TYPE is defined as Parent
RECORD KEY OFFICE GROUP TYPE COUNTRY NATIONAL ID INSTITUTION NAME
TYPE CODE
BD0000000JB5 HO Parent US 11300595 CAMBRIDGE TRUST COMPANY
4.4.3 Default identification

If OFFICE TYPE and GROUP TYPE cannot be used, then select the first record in the set.
The following example shows an equal set of records:
RECORD KEY OFFICE COUNTRY NATIONAL INSTITUTION NAME CITY

TYPE CODE ID
BD0000000ACE DB AT 11990 UNICREDIT BANK AUSTRIA Ternitz
AG
BD00000027TV DB AT 11990 UniCredit Bank Austria AG Neunkirchen
Fil.Neunkirchen
BD00000027TW DB AT 11990 UniCredit Bank Austria AG Wiener Neustad
Regionaldirektion NOe-Sued
Burgenland
In this instance T24 would use record BD0000000ACE as this is the 1st record in the list
above
RECORD KEY OFFICE COUNTRY NATIONAL INSTITUTION NAME CITY
TYPE CODE ID
BD0000000ACE DB AT 11990 UNICREDIT BANK AUSTRIA Ternitz
AG
4.5 Forex/Swap MT360 & MT361

T24 has been enhanced to support the following 2015 Swift changes in the following
messages
MT360
MT361
MT600
MT604
MT605

TAG MESSAGE Optional/Mandatory Sequence T24 Module
14F MT360/MT361 Mandatory Sequence C and F SW - Swaps
37N MT360/MT361 Optional Sequence C and F SW - Swaps
72 MT360/MT361 Optional Sequence A SW - Swaps
26C MT600/MT604/MT605 Mandatory Sequence A FX Forex
32F MT600/MT604/MT605 Mandatory Sequence B or C FX Forex
4.5.1 Configuration
In addition to the updates, the following configuration is required to support the above changes for
releases R10, R11, R12, R13, AMR14, AMR15, 201407, 201408, 201412 and 201507.
Note: The version names used in the below screen shots can be configured as per the client requires
4.5.1.1 Forex
Field level validation for METAL.TYPE and QUANTITY
When METAL.TYPE is GOLD, QUANTITY must be GOZ or TOZ
When METAL.TYPE is PALL, PLAT or SILV, then QUANTITY must be GOZ
Validation errors should be raised if any other values are specified for QUANTITY.
Step 1
Create a version for FOREX.

Step 2
Create a record in EB.API for the version routine.

Step 3
Attach the version routine to do the validation for METAL.TYPE and QUANTITY fields.

Example
The following example shows the field validation within the Forex module using the above version and
routine.

4.5.1.2 Swap
The following configuration is required to support the changes in the Swap module.
Step 1
Create a MARKET.RATE.TEXT with RATE.TEXT as OTHER.

Step 2
Attach the routine to the swap 360/361 message in the DE.MAPPING application.

Step 3
Create a contract in Swaps and commit the record

Delivery Message


5 Further Information
5.1 Contact Details
Area Product Manager Contact Address
General SWIFT questions, Lisa Hall lhall@temenos.com

payments and utility
Phil White pwhite@temenos.com
messages

SWIFT Standards 2015 Annual Maintenance

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SWIFT Standards 2015 Annual Maintenance

Hochgeladen von

Copyright:

Verfügbare Formate

SWIFT Standards MT November 2015

Information in this document is subject to change without notice.

Version Date Author Amendment

TEMENOS Confidential Page 2 SWIFT Standards 2015 Installation notes.docx

TEMENOS Confidential Page 3 SWIFT Standards 2015 Installation notes.docx

TEMENOS Confidential Page 4 SWIFT Standards 2015 Installation notes.docx

Release Dependant Expected Module Updates

R10 S5 26th August DE Changes T24Update R10_DE_Outward_17

Payment changes T24Update R10_AC_PaymentNetting_4

18 September Forex R10_FX_Contract_38

IBAN Changes T24Update R11_IN_Config_3

18th Sept 2015 Forex R11_FX_Contract_23

18th Sept 2015 Swaps R11_SW_Delivery_6

R12 S5 4-Sep-2015 DE Changes T24Update R12_DE_Outward_2

IBAN Changes T24Update R12_IN_Config_3

TEMENOS Confidential Page 5 SWIFT Standards 2015 Installation notes.docx

Payment Changes T24Update R12_AC_PaymentNetting_5

18th Sept 2015 Forex R12_FX_Contract_13

18th Sept 2015 Swaps R12_SW_Delivery_3

R13 SF & S5 4-Sep-2014 DE Changes T24Update R13_DE_Outward_7

IBAN Changes T24Update R13_IN_IbanAPI_2

Payment changes T24Update R13_AC_PaymentNetting_3

18th Sept 2015 Forex R13_FX_Contract_11

23rd Oct 2015 Swaps R13_SW_Delivery_3

AMR14 SF & S5 2-Sep-2015 DE Changes T24Update R14_FT_Contract_14

IBAN Changes T24Update R14_IN_IbanAPI_1

Payment Changes T24Update R14_AC_PaymentNetting_2

18th Sept 2015 Forex R14_FX_Contract_5

18th Sept 2015 Swaps R14_SW_Delivery_2

AMR15 SF & S5 TBC DE Changes TBA

IBAN Changes TBA

23rd Oct 2015 Forex R15_FX_Contract_1

23rd Oct 2015 Swaps R15_SW_Delivery_1

TEMENOS Confidential Page 6 SWIFT Standards 2015 Installation notes.docx

IBAN Changes T24Update 201408_IN_IbanAPI_1

Payment changes T24Update 201408_AC_PaymentNetting_1

201407 SF & S5 4-Sep-2015 DE Changes T24Update 201407_DE_Outward_1

IBAN Changes T24Update 201407_IN_IbanAPI_2

Payment changes T24Update 201407_AC_PaymentNetting_1

23rd Oct 2015 Forex 201407_FX_Contract_2

201412 SF & S5 4-Sep-2015 DE Changes T24Update 201412_DE_Outward_1

IBAN Changes T24Update 201412_IN_IbanAPI_1

Payment Changes T24Update 201412_AC_PaymentNetting_1

18th Sept 2015 Forex 201412_FX_Contract_2

18th Sept 2015 Swaps 201412_SW_Delivery_2

201507 SF & S5 20 Sept 2015 Swaps 201507_SW_Contract_1

18th Sept 2015 Forex 201507_FX_Contract_2

18th Sept 2015 DE T24Update 201507_DE_Outward_1

TEMENOS Confidential Page 7 SWIFT Standards 2015 Installation notes.docx

18th Sept 2015 Payments T24Update 201507_AC_PaymentNetting_1

3.2 Installation of S5 Module

TEMENOS Confidential Page 8 SWIFT Standards 2015 Installation notes.docx

Install a new Product ID and Product Code

3.2.3 T24.UPGRADE Service

TEMENOS Confidential Page 9 SWIFT Standards 2015 Installation notes.docx

DATA field on BATCH record updated with new product codes

3.3 SWIFT.PARAMETER table

TEMENOS Confidential Page 10 SWIFT Standards 2015 Installation notes.docx

The following screen shows the SWIFT.PARAMETER table.

TEMENOS Confidential Page 11 SWIFT Standards 2015 Installation notes.docx

4.2.1 Example Restricted currency

TEMENOS Confidential Page 12 SWIFT Standards 2015 Installation notes.docx

TEMENOS Confidential Page 13 SWIFT Standards 2015 Installation notes.docx

4.3 Overview and Setup for TAG59F