IBM Support

Release notes for IBM Financial Transaction Manager for High Value Payments 3.2.12 Multiplatforms

Release Notes


Abstract

Release notes for IBM Financial Transaction Manager for ISO 20022 High Value Payments 3.2.12 Multiplatforms

Financial Transaction Manager for ISO 20022 High Value Payments V3.2.12 offers the ability to process ISO 20022 high-value payment types. This addition to the modern, robust IBM Financial Transaction Manager suite brings together capabilities that were not available within the existing suite.

Financial institutions can now process the following payments through a single ISO 20022-compliant platform by using a common Internal Standard Format (ISF).
- T2 and EURO1/STEP1 ISO 20022 payment messages that follow the High Value Payments Plus (HVPS+) specification.
- Swift cross border payments that follow the Cross-border Payments and Reporting Plus (CBPR+) specification.

Content

 

Before installation

System requirements

Check the IBM Financial Transaction Manager system requirements to ensure that your installation platform is supported for the product edition that you plan to install. For more information about the system requirements for all of the different versions of the product, see the IBM Financial Transaction Manager system requirements website.
 

Downloading the product

For information about how to download IBM Financial Transaction Manager for High Value Payments for Multiplatforms see the download document for IBM Financial Transaction Manager for ISO 20022 High Value Payments 3.2.12.
 

Product documentation

Data Setup Utility
The following documentation describes the data setup utility (DSU) and the import and export workbooks:

  • DSUmigration_v3.2.12.pdf
  • DSUMigrationBR_v3.2.12.pdf

These documents are provided in the entitled documentation fix pack.

Database migration
For database migration instructions, refer to the migration instructions in {Install location}\shared\vnnn\pfs\Database\db2\{os}\doc


Transaction Server Scheduler XML
The following documentation describes the changes to the scheduler XML for the Transaction Server component:

  • TransactionServerSchedulerChanges_v3.2.12.pdf

These documents are provided in the entitled documentation fix pack.
 

Back to contents
3.2.12.0 Release

New features and updates

High Value Payments CBPR+ 2023 Mandates Support

WORKFLOW

In the FTM HVP reference application, the new message types are configured to be associated with the Incoming/Outgoing Generic Transaction flows.

MT110

The MT110 mapper is used to recommend the drawee bank, or confirm to an enquiring bank, the details concerning the check(s) referred to in the message.

The MT110 mappers are a pair of Inbound/Outbound mappers.

• MT110 Inbound Mapper: Map the MT messages to ISF messages. The default mapper name is MTToISFMapper.

• MT110 Outbound Mapper: Map the ISF messages to MT messages. The default mapper name is ISFToMTMapper.

The details of the mapping specification for both inbound and outbound mappers are included in a separate document. Refer to the detailed MT110 mapping specification for more information about obtaining the documentation for the mapping specifications.

MT111

The MT111 mapper is used to request stop payment of the check referred to in the message.

The MT111 mappers are a pair of Inbound/Outbound mappers.

• MT111 Inbound Mapper: Map the MT messages to ISF messages. The default mapper name is MTToISFMapper.

• MT111 Outbound Mapper: Map the ISF messages to MT messages. The default mapper name is ISFToMTMapper.

The details of the mapping specification for both inbound and outbound mappers are included in a separate document. Refer to detailed MT111 mapping specification for more information about obtaining the documentation for the mapping specifications.

MT112

The MT112 mapper is used in the Swift network by the drawee bank (on which a check is drawn) to the drawer bank or the bank acting on behalf of the drawer bank and is used to show what actions were taken in trying to stop payment of the check referred to in the message.

The MT112 mappers are a pair of Inbound/Outbound mappers.

• MT112 Inbound Mapper: Map the MT messages to ISF messages. The default mapper name is MTToISFMapper.

• MT112 Outbound Mapper: Map the ISF messages to MT messages. The default mapper name is ISFToMTMapper.

The details of the mapping specification for both inbound and outbound mappers are included in a separate document. Refer to the Detailed MT112 mapping specification for more information about obtaining the documentation for the mapping specifications.

camt.055.001.08

The camt.055.001.08 (camt.055) mapper is issued by the initiating party to request the cancellation of an initiation payment message that was previously sent.

The camt.055 mapper is configured as an Inbound mapper.

• camt.055 Inbound Mapper: Map the CustomerPaymentCancellationRequest messages to ISF messages. The default mapper name is camt055ToISFMapper.

The details of the mapping specification for inbound mapper are included in a separate document. Refer to Detailed camt.055 mapping specification for more information about obtaining the documentation for the mapping specification.

camt.058.001.08

The camt.058.001.08 (camt.058) mappers are used to tell the account servicing institution that the funds are no longer expected.

The camt.058 mappers are a pair of Inbound/Outbound mappers.

− camt.058 Inbound Mapper: Map the NotificationToReceiveCancellationAdvice messages to ISF messages. The default mapper name is camt058ToISFMapper.

− camt.058 Outbound Mapper: Map the ISF messages to NotificationToReceiveCancellationAdvice messages. The default mapper name is ISFTocamt058Mapper.

The details of the mapping specification for the inbound mapper are included in a separate document. Refer to Detailed camt.058 mapping specification for more information about obtaining the documentation for the mapping specifications.

camt.107.001.01

The camt.107.001.01 (camt.107) mappers are used by a drawer bank to the drawee bank, to tell the drawee bank of one check.

The camt.107 mappers are a pair of Inbound/Outbound mappers.

− camt.107 Inbound Mapper: Map the ChequePresentmentNotification messages to ISF messages. The default mapper name is camt107ToISFMapper.

− camt.107 Outbound Mapper: Map the ISF messages to ChequePresentmentNotification messages. The default mapper name is ISFTocamt107Mapper.

The details of the mapping specification for the inbound mapper are included in a separate document. Refer to Detailed camt.107 mapping specification for more information about obtaining the documentation for the mapping specifications.

camt.108.001.01

The camt.108.001.01 (camt.108) mappers are messages sent by a drawer bank, or a bank acting on behalf of the drawer bank, to the agent on which a check is drawn (the drawee bank) to request for the cancellation of the presentment and/or stop the payment of the check referred to in the message.

The camt.108 mappers are a pair of Inbound/Outbound mappers.

− camt.108 Inbound Mapper: Map the ChequeCancellationOrStopRequest messages to ISF messages. The default mapper name is camt108ToISFMapper.

− camt.108 Outbound Mapper: Map the ISF messages to ChequeCancellationOrStopRequest messages. The default mapper name is ISFTocamt108Mapper.

The details of the mapping specification for the inbound mapper are included in a separate document. Refer to Detailed camt.108 mapping specification for more information about obtaining the documentation for the mapping specifications.

camt.109.001.01

The camt.109.001.01 (camt.109) mappers are used to show what actions have been taken in trying to cancel the presentment and/or stop the payment of the check referred to in the message.

The camt.109 mappers are a pair of Inbound/Outbound mappers.

− camt.109 Inbound Mapper: Map ChequeCancellationOrStopReport messages to ISF messages. The default mapper name is camt109ToISFMapper.

− camt.109 Outbound Mapper: Map the ISF messages to ChequeCancellationOrStopReport messages. The default mapper name is ISFTocamt109Mapper.

The details of the mapping specification for the inbound mapper are included in a separate document. Refer to Detailed camt.109 mapping specification for more information about obtaining the documentation for the mapping specification.

Known issues

This section outlines the known issues and their workarounds (if any).
 

Issue 1

142495 - Rejected Recall messages and Response to Recall messages are shown as Accepted in Control Center

The integration of MT messages and nonpayment messages with the Control Center was implemented as part of this release. The status of successfully processed transactions is shown as Accepted and the rejected transactions is shown as Rejected on the Transaction page of the Control Center.
However, for the following message types, the rejected transactions are also shown as Accepted.
  • camt.056
  • camt.029
  • MT 196 / MT 296
  • MT 192/ MT 292
The FTM Base status column shows the correct status, but the status column alone shows as Accepted on the Transaction page of the Control Center.

Issue 2

141730 - Trace Number and Recipient account number fields are empty in the Control Center

The inbound transaction page has empty values for the trace number and recipient account number fields for all the nonpayment messages. These fields should show the alternate ID in the trace number field and the destination account number in the recipient account number field.

Issue 3

Special character slash (/) handling in tag 72 for the following flows
  • PACS.009 to MT202
  • PACS.008 to MT103
This issue can occur during the payment processing for the MX to MT flow when the data contains the special character slash (/) in the Instruction Information field.
The problem occurs because codes in the Instruction Information field are prefixed and suffixed with slash and can contain up to eight characters. If the data contains a slash, no logic or rule is available to identify whether the slash is a code separator or a data separator.
The following example shows the case where the user is trying to send 3 codes (INT, SDP, and REP) and corresponding data. The same data, when it is translated to MT, has a different structure of codes and data. This issue is due to the presence of the slash special character as part of the data under the Instruction Information, which leads to a different code and data structure in the MT because of its position within the data.
Example:
 
Original Data from MX (For example, pacs008):
----------------------------------------------------
<InstrForNxtAgt>
   <InstrInf>/INT/SYORPUTN/PRT</InstrInf>
</InstrForNxtAgt>
<InstrForNxtAgt>
   <InstrInf>/SDP/GENTINC/REP/NEWONEDATA</InstrInf>
</InstrForNxtAgt>
 
The code and data from the user (based on pacs008):
---------------------------------------------------------------  
Code: /INT/    
Corresponding Data: SYORPUTN/PRT
Code: /SDP/    
Corresponding Data: GENTINC
Code: /REP/    
Corresponding Data: NEWONEDATA
 

Data from the 2 instances of the Instruction Information is concatenated as shown in the following example.

Data concatenation per the CBPR+ rule:
------------------------------------------------  
/INT/SYORPUTN/PRT/SDP/GENTINC/REP/NEWONEDATA

The concatenated string is translated to MT with the code and corresponding data format that is shown in the following example.

Data translated to tag 72 of MT (MT 103):
----------------------------------------------------  
:72:/INT/SYORPUTN
/PRT/SDP
/GENTINC/REP/NEWONEDATA
 

Originally, the MX had 3 codes (INT, SDP, and REP) and each code had its corresponding data associated with it. Because the data for INT has a slash after SYORPUTN and the next part of the instruction information begins with a slash to represent a code, the data part PRT is treated as a code, and the structure is changed.

The translated MT has a different way of representing the code and data, which might be misleading. The translated results are shown in the following example.

The code and data as translated in MT:
----------------------------------------------------  
Code: /INT/    
Corresponding Data: SYORPUTN
Code: /PRT/    
Corresponding Data: SDP
Code: /GENTINC/    
Corresponding Data: REP/NEWONEDATA

 

Migration

None.

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSENX3","label":"IBM Financial Transaction Manager for High Value Payments"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"3.2.12"}]

Document Information

Modified date:
20 October 2023

UID

ibm17033684

Page Feedback