The Bank validation in the Employee Payment Information portlet in SAP SuccessFactors Employee Central (EC) is very important from Payroll standpoint. Obviously if information is incorrect employees won't get salary in their bank accounts. I would like to share what I have seen with my clients. This can definitely become handy while configuring Bank validations or troubleshooting payment information.
Payment information in EC is a self service portlet so there is high probability that employee may end up updating incorrect information. The bank details should be updated in compliance with country requirements. One important attribute of payment information is Routing number and customers want to make sure that it is correct.
SAP has given few Deep validations. One relevant for us here is Bank Account Validations (Company System and Logo Settings -> Enable Bank Account validations).
The validations are pre-delivered content for all countries supported by SAP. This can be downloaded from SAP help and imported in your system like any other data. Go to 'Import and Export Data' and Import this file by selecting the object 'Country specific validations..'
These validations can also be customized for every country (Manage Data -> Country specific validations). Though is not suggested to change these validations because SAP has configured this as per legal requirements for every country but just in case there is a legal change or customer specific requirement to support Integrations etc. then you can update this configuration.
Firstly I would like to begin by saying that we have an MDF for Bank but not every customer enables it for various reasons. So I would like to divide this blog in two parts - When Bank MDF is enabled and when it is not.
In this case the Bank master data can be manually created or imported into EC. System will perform the deep validations when you create/import Bank data. If you don't want that check enabled please turn it off (Company System and Logo Settings -> Uncheck Bank Account validations)
'Bank' field can be enabled on Payment information Detail object (Configure object definition -> Payment information Detail -> Enable the field 'Bank'). Now the Bank object and Payment information of an employee are connected via this 'Bank' field. When employee selects the Bank the routing number/Business Identifier code will be defaulted from Bank object. This makes sure that correct Bank information has been updated in the payment information. Further the fields like Routing number can be made as 'Read only' so that employee can't change it.
In this case when Employee updates the Bank details in Payment information then it is validated by the country specific validations as shown below.
In above screenshot you can see there are 3 options to validate the Routing number. For ex. if CAN supports only ISO Swift format validation then you cannot select Algorithm here. If you try you will get below error.
As per ISO Swift format you select (attribute above Validation type) the validation is performed. In our case 9c means up to 9 characters allowed so basically only the length is validated. If you enter 10 characters system will throw an error. Similarly 9!n means exactly 9 digits allowed. If you enter 8 digits system will throw an error. To validate the complete routing number you can write a business rule and show an error message if format is incorrectly entered by employee. This may become complex but depends upon the validation checks required.
For some countries which have Algorithm based validation like US not only the length but complete format is validated. So what I mean to say is that all countries have different validation formats.
When you neither have the Bank MDF enabled nor the country specific validations in place then system will give you a warning message saying that "no validations are configured so please ensure all information is correct".
The better way to validate Bank details is via Option 1 (maintain bank master data and connect it with Payment information by enabling 'Bank' in Payment information portlet) because you don't need to maintain or worry about extra checks. You need to make sure that your Bank master data has been imported correctly. But many clients don't maintain Bank data in EC because of Integrating SAP Finance with SAP SuccessFactors as SAP FIN is source of truth for Bank Master.
Payment information in EC is a self service portlet so there is high probability that employee may end up updating incorrect information. The bank details should be updated in compliance with country requirements. One important attribute of payment information is Routing number and customers want to make sure that it is correct.
SAP has given few Deep validations. One relevant for us here is Bank Account Validations (Company System and Logo Settings -> Enable Bank Account validations).
The validations are pre-delivered content for all countries supported by SAP. This can be downloaded from SAP help and imported in your system like any other data. Go to 'Import and Export Data' and Import this file by selecting the object 'Country specific validations..'
These validations can also be customized for every country (Manage Data -> Country specific validations). Though is not suggested to change these validations because SAP has configured this as per legal requirements for every country but just in case there is a legal change or customer specific requirement to support Integrations etc. then you can update this configuration.
Firstly I would like to begin by saying that we have an MDF for Bank but not every customer enables it for various reasons. So I would like to divide this blog in two parts - When Bank MDF is enabled and when it is not.
- Bank MDF is enabled in SuccessFactors Employee Central (EC)
In this case the Bank master data can be manually created or imported into EC. System will perform the deep validations when you create/import Bank data. If you don't want that check enabled please turn it off (Company System and Logo Settings -> Uncheck Bank Account validations)
'Bank' field can be enabled on Payment information Detail object (Configure object definition -> Payment information Detail -> Enable the field 'Bank'). Now the Bank object and Payment information of an employee are connected via this 'Bank' field. When employee selects the Bank the routing number/Business Identifier code will be defaulted from Bank object. This makes sure that correct Bank information has been updated in the payment information. Further the fields like Routing number can be made as 'Read only' so that employee can't change it.
- Bank MDF is not enabled in SuccessFactors Employee Central (EC)
In this case when Employee updates the Bank details in Payment information then it is validated by the country specific validations as shown below.
In above screenshot you can see there are 3 options to validate the Routing number. For ex. if CAN supports only ISO Swift format validation then you cannot select Algorithm here. If you try you will get below error.
As per ISO Swift format you select (attribute above Validation type) the validation is performed. In our case 9c means up to 9 characters allowed so basically only the length is validated. If you enter 10 characters system will throw an error. Similarly 9!n means exactly 9 digits allowed. If you enter 8 digits system will throw an error. To validate the complete routing number you can write a business rule and show an error message if format is incorrectly entered by employee. This may become complex but depends upon the validation checks required.
For some countries which have Algorithm based validation like US not only the length but complete format is validated. So what I mean to say is that all countries have different validation formats.
When you neither have the Bank MDF enabled nor the country specific validations in place then system will give you a warning message saying that "no validations are configured so please ensure all information is correct".
The better way to validate Bank details is via Option 1 (maintain bank master data and connect it with Payment information by enabling 'Bank' in Payment information portlet) because you don't need to maintain or worry about extra checks. You need to make sure that your Bank master data has been imported correctly. But many clients don't maintain Bank data in EC because of Integrating SAP Finance with SAP SuccessFactors as SAP FIN is source of truth for Bank Master.
- SAP Managed Tags:
3 Comments
| User | Count |
|---|---|
| 10 | |
| 6 | |
| 4 | |
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
