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,
Post an idea
Upvote ideas that matter most to you
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 product management 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.
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...
Automatic generation of field CreDtTm:Creation Date Time in MX MSGs during sending of MSG from MER
Manual entry of MX MSGs (T2 and CBPR+) has mandatory field CreDtTm:Creation Date Time We woud like this field filled automatically with a system date and time at the end of MSG processing in MER Facility that is when the MSGs is put in a MQ queue ...
add indexes in MWH for BICFI from/to in BAH of InterAct messages' payload.
The SWIFT IA services esmig.t2 and ebacl.e1s1 will introduce the "V-Shape" model with the HVPS migration to ISO20022 in Nov 2022, whereas the ESMIG and E1S1 Operators will always be the Requestor or Responder in the IA-header but not the "corresp...
T2 domain in MER Facility for manual entry of T2 MSGs
MER Facility manual data entry for T2 MSGs would be much easier if there was a T2 domain like there is for CBPR+ or remit solutions , Proxy voting MX MSGs This would help data entry users to verify the fields and the whole MSGs according to ECB ru...
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, MT320For example, current MERVA:Party Ref PartyPBBEK0 0175 PBBEPXFTM-MER:Party Prefix PBBE Party Suffix K0Ref 0175Party Prefix PBBE Pa...
PBB User expecting to have shortcut button to view the next message instead of user have to quit (return to the queue) then only to select the next message in FTM-MER1) User excepting Next button after opening the message from Message List page2)...
FTM MER Screen – Additional data entry field for Routing
FTM MER Screen - Having an additional data entry filed (something like editable ‘comments’) in the Formatted Tab. The user can enter the comments filed by viewing the details of the Message. This would help in having the custom actions based on th...
FTM-MER should be able to handle this double slash (//) checking
FTM-MER should be able to handle this double slash (//) checkingIn existing Merva users are required to key in a double slash '//' at the beginning ofeach account number. In FTM this is not required anymore but since the users areused to keying in...
Do not place IBM confidential, company confidential, or personal information into any field.