PaymentConnector SAP

PaymentConnector SAP ensures that between the period of downloading the payment file from SAP and the reading of the file in the bank no unnoticed changes take place in the payment file.

Below is a brief explanation of the functionality of PaymentConnector SAP.

Safe payment

When the button “download payment file” is clicked in transaction FDTA in SAP the data of the payment file will first be forwarded to the application developed by Connect Solutions: PaymentConnector SAP. Over these data a hash is calculated (MD5 Hash Generator or SHA: Secure Hash Algorithm). This hash is added to the bottom of the payment file in accordance with the specifications of the bank package. Next the payment data including hash is returned to SAP and the payment file including hash is downloaded.

When this payment file is read into the bank application, the bank itself calculates a hash over the data and checks whether this hash matches the hash added to the payment file. If it does, the payment file can be processed further. If not, the bank will not recognise the hash and an error will follow. In other words: if someone makes a manual adjustment in the payment file after downloading the payment file, the hash total will no longer be correct and the payment file cannot be read.

However, this is not a sufficient guarantee to exclude possible fraud. The following scenario could occur: The payment file is downloaded including the hash total. Someone adjusts a bank account in the payment file and uses tools on the internet to calculate the hash code over the adjusted data. And then pastes this new hash at the bottom of the payment file. The bank then indicates that the hash is correct and payment can be made.

Procedure against fraud

PaymentConnector SAP is a solution that gives you the certainty that payments arrive at the right place. To prevent fraud the following procedure has to be set up in combination with PaymentConnector SAP.

At the moment the hash is calculated, before the payment file including hash is downloaded, PaymentConnector SAP automatically sends the hash code by e-mail to the two employees in the bank who have to sign the payment file. These persons check the hash the bank has accepted with the hash code they received by e-mail. And they only sign if both hash codes match.

To summarise: if someone has made a change afterwards and added a self-calculated hash to the payment file, this hash total will not match the hash the signers received by e-mail.

PaymentConnector SAP is available for SAP ECC and SAP S/4HANA.

PaymentConnector SAP = safe payment

Want to know more about PaymentConnector SAP? Please contact us for a no-obligation discussion with one of our consultants.