IBM RegTech Ideas Portal



Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.


For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here


Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases


The shorter URL for this site is:

IBMers, please visit the WFSS Internal Ideas portal


note: The IBM ICM IDEAS Portal is no longer available at this location. If you have reached this page, please look for a new link in the Varicent Administrator. Direct links are found under the "?" in the upper right corner.
A period of transition is likely to impact this service, while ICM becomes Varicent. Please contact Varicent support if you have additional challenges or concerns.

Pain001V5 to ISF Mapper, request for Core Mapper with support for Post-Body Mapper to harvest ABN-specific Supplementary Data

In response to the requested Pain.001V5 to ISF mapper, please find attached the final specs (see file "FTM_Mapping_PAIN001.001.05 to ISF v0.3_Final for RFE.xlsx")

In short, we would require
1. a Core Mapper based on XSD Pain.001V5,
2. with support for a Post-Body Mapper for the mapping of the Supplementary Data to ISF Addenda. A sample Post-Body Mapper is requested for the below Supplementary Data mappings (see the attachement).

Re 1: Should be unambiguous, as the resp. XSD for Pain.001V5 is leading.

Re 2: This is a new feature, required to map Supplementary Data attributes which were introduced by the Pain.001V5 (ie Pain.001V3 does not cater for these).
Supplementary Data is ABN (channel-) specific, hence why ABN requires a customer-specific solution like a Post-Body Mapper.
This support for Post-Body Mapper must be maintainable and extendible, meaning that in case future channels require additional Pain.001V5 Supplementary Data fields to be mapped in ISF, ABN is capable of adding such new mapping requirements in the Post-Body Mapper themselves easily without requiring changes to the Core Mapper.

N.B. As response to PMR 40620,211,788 it became clear that the Pain.001V5 mapper in the SEPA pack is built with minimal mapping to ISF and does not support all the possible levels of repetition within the message and does not cover the full message content. Therefore we have been advised to raise this RFE.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 9 2019
  • Needs Review
Component Mapping & Translation
Priority High - Critical
  • Attach files