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 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
Amount Keying - ability to configure additional debits to be made available in Out of Balance transactions during the second wave - with the "most likely" debits
We understand Amount Keying makes items available for PCC to select in three waves. First the credits in an OOB (Out of Balance) transaction are made available. Then the "most likely" debits are made available in an OOB transaction. And third, the remaining debits in an OOB transaction are made available.
BB&T would like to be able to configure additional debits to be made available in OOB transactions during the second wave - with the "most likely" debits. The criteria would be similar to the criteria that is used when configuration PCC - routing and transfer number, amount, etc.
Do not place IBM confidential, company confidential, or personal information into any field.