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

CBT automatic reconnect according to SWIFT "best practice"

We faced in production an abort of our FIN LTs with SWIFTs abort reason codes saying "Regional Processor is being shut down".

After discussions on PMR 40488,311,75 and a parallel case with SWIFT, it is clear that SWIFT does not document this abort reason explicitely as to be automatically re-connected by the CBT.
But SWIFT claims that is is "best practice" for a CBT to do so.

Therefore please review possilbe system abort cases and implement automatic re-connect/re-open of a session from CBT side as recommended by SWIFTs "best practices".

And if a re-connect is not possible, at least an error-event is needed to be reported by FTM/WBI-FN so that we can setup an alarm-chain.

In the current situation we were not even alerted as the system abort is just an informational event.

Ohterwise there are cases were SWIFTNet FIN LT sessions are "lost" without re-connect try and without error-notification.
  • Guest
  • Apr 9 2019
  • Future consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.