Skip to Main Content
IBM Data and AI RegTech Ideas Portal

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

Shorter URL for this site is: or

Status Not under consideration
Created by Guest
Created on Feb 22, 2021

FTM-MER should be able to handle this double slash (//) checking

FTM-MER should be able to handle this double slash (//) checking

In existing Merva users are required to key in a double slash '//' at the beginning of

each account number. In FTM this is not required anymore but since the users are

used to keying in the double slash '//' for the account numbers, they will sometimes do the same thing in FTM also (refer to Attachment No. 1 for instance).

When users verify the message, the FTM will prompt the message stating that the message is valid and hence the user will proceed to submit the message without noticing the mistake. At the backend, what happens is that the FTM is formatting the message from the GUI into an unformatted format (refer to Attachment No. 2) to be routed through the queues respectively. The double slash is being combined with the predefined single slash in the unformatted format to form a triple slash '///'. FTM will read this triple-slash value as a code with a single slash value in which this code field should be filled only with a 'C' or 'D' value and is also not compulsory.

When this message is sent to SWIFT, the message will fail and lands in the TCCERROR queue instead because of this issue. The error is displayed in the Context field. Refer to Attachment No. 3 and No. 4 for a sample message for this particular issue reported by our Head Office users.

FTM-MER should be able to handle this double slash checking during the data entry validation screen.

Ref. CASE #: TS005043751

  • Guest
    Feb 25, 2021

    Hi Please explain why this feature is not in consideration. Thanks