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: http://ibm.biz/WFS-Ideas or https://ibm.biz/RegTech-Ideas

ADD A NEW IDEA

FILTER BY CATEGORY

Transaction Processing - Validation, Enrichment, Routing

Showing 2

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 PBBEK0 0175 PBBEPX FTM-MER: Party Prefix PBBE Party Suffix K0 Ref 0175 Party Prefix...
over 1 year ago in FTM for SWIFT Services / Transaction Processing - Validation, Enrichment, Routing 1 Not under consideration

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...
over 1 year ago in FTM for SWIFT Services / Transaction Processing - Validation, Enrichment, Routing 1 Not under consideration