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

FTM for SWIFT Services

Showing 50

We would like to have FTM in High Availability

In an HA environment with 2 FTM SWIFT nodes there is a restriction to have a single copy of the FTM SWIFT code in a shared library /usr/lpp/IBM/ftmswift/v300, visible from both LPARs
over 2 years ago in FTM for SWIFT Services / Usability 0 Future consideration

Generate UETRs for MX during MSIF sending, not in the MER Data Entry (DNIMX&DNIFINPLUS)

1. For T2 MSGs that we enter in DNIMX domain the field for UETR is not mandatory so we can leave it empty but when we send the MSG from MER to InterAct and to SWIFTNet the UETR is not calculated and field PmtId – UETR is empty even if we put CD co...

Empty Remote DN in MX MSGs with manual entry in MER

We would like a warning MSG to be issued if Remote DN is not Entered in MX MSGs (DNIFINPLUS and DNIMX domains) because the MSG sent to InterAct will get the error in MSG Send Notification.

Automatic generation of field MsgId: Message Identification in MX MSGs when entered manually in MER

Field Field MsgId: Message Identification is mandatory and unique so it should be generated automatically during manual entry of MX MSGs in MER

FTM for Swift Services to support Universal Tablespace Partition by growth.

We would like FTM for Swift Services to support Universal Tablespace Partition by growth for Audit Tables.
over 2 years ago in FTM for SWIFT Services / Administration & Configuration 0 Future consideration

MT7xx / free text fields

MER facility:when (manually creating) an MT7xx is it often the case that text for free text fields are copied from several sourcen (because of contracts, etc).by doing so (copying from a source and pasting) MERVA automatically frowarded the exceed...
over 2 years ago in FTM for SWIFT Services / Usability 0 Future consideration

Message WareHouse Power Search of SWIFT Messages (MT and MX)

Currently COGNOS is used to query MT and MX messages. For MT there is a free text search, but the same is not made available for MX messages. In addition, general query performance is slow.Note that I have look at other SWIFT products, and they...
over 2 years ago in FTM for SWIFT Services / Other 1 Future consideration

The query criteria “Store Time” in MER Message List Filter confuses customer and end-user.

System: Message Entry and Repair Facility Actor: End-user Employees of financial institutions can use the Message Entry and Repair (MER) Facility to manually process financial messages. End-user is always using filter function in MER list pag...
over 2 years ago in FTM for SWIFT Services / Usability 0 Future consideration

Automatic activation of accounting for the SIPN FIN and FMT FIN services.

The manual procedure described in "System Administration Guide" for "Collecting accounting data for the SIPN FIN and FMT FIN services" is prone to be forgotten or overseen and should be better replaced by an automatic procedure like that applying ...
over 2 years ago in FTM for SWIFT Services / Administration & Configuration 0 Future consideration

Improved retry handling for FA transfers based on status information

The request is needed since the retry for files in Accepted status is no more needed given that SWIFT retries for 4 hours, if after 4 hours a file is not sent, it means that a huge technical problem is likely affecting the receiver, in this case w...
over 2 years ago in FTM for SWIFT Services / Usability 0 Future consideration