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 18, 2021

Expected FTM-MER NOT to split bank/location or Prefix/Suffix

Expected FTM-MER NOT to split bank/location or Prefix/Suffix.

Field 22 - for MT305 / MT600

Field 22C - for MT300, MT320

For example, current MERVA:

Party Ref Party



Party Prefix PBBE Party Suffix K0

Ref 0175

Party Prefix PBBE Party Suffix PX

Hence, user expectation to not split Prefix/ Suffix for future mapping purpose.

Ref. Case #: TS005025936

Additional Information [8 Mar]:

Objective: Mapping exercise will be part of Sprint 2 project, to ensure the interface and mapping of information from Source System to FTM-MER is in order.

This mapping is from Source System (Equation System) to FTM-MER and from FTM-MER to Intellimatch.

In current MERVA System, there is only one fields (both information of Party Prefix & Suffix are combined) instead of separate fields provided in FTM-MER, refer to example below.

Therefore, user doubt that whether the FTM-MER can identify what is the "Party Prefix" or "Party Suffix" when source system remain unchanged to provide the same format of information.

For example:

Source System (Equation) / Current Merva System:

Party Ref Party



Party Prefix Party Suffix




Party Prefix Party Suffix


  • Admin
    Mar 16, 2021

    Please explain the future mapping concern.