• Skip to primary navigation
  • Skip to main content
Connect Solutions
  • SAP solutions
    • INVOICE MANAGEMENT
      • InvoiceConnector SAP
      • E-invoicing Routty Cloud
      • SAP Integration with Tungsten AP Essentials
    • SAP ARCHIVERING
      • Archive Central
    • VENDOR PAYMENTS
      • PaymentConnector SAP
  • Customers
    • HEALTHCARE
      • Zuijderland MC
      • Maastricht UMC+
      • Amphia
      • Flevoziekenhuis
      • Universitair Medisch Centrum Groningen
      • Amsterdam UMC
      • St. Anna Ziekenhuis
      • Klina
      • Rivierenland
      • Sint-Trudo Ziekenhuis
      • Sint-Lucas Gent
      • Sint-Blazius
      • AZ Alma
      • Sint-Elisabeth Zottegem
      • AZ Monica
    • INDUSTRY
      • VDL
      • VDL Nederland
      • Inventum
      • Bostik bv
      • MCB Nederland
      • Schils bv
      • Vitablend
      • Prinsen Berning
      • Variass
      • KIVO Plastic Verpakkingen
      • SAEY Steel Service Center
    • RETAIL
      • Hunkemöller
      • Vogel's
      • Intertoys
      • SHI
      • Swiss Sense
      • Nedac Sorbo Mascot
      • Skantrae deuren
      • Outdoor Life Group
  • Customer cases
    • CUSTOMER CASES
      • Zuyderland
      • SAEY Steel Service Center
      • Intertoys
      • Schils BV
  • Knowledge Center
    • SAP WHITEPAPERS
      • InvoiceConnector SAP
      • InvoiceConnector SAP Fiori
      • PaymentConnector SAP
      • Kofax Readsoft Online Connector for SAP
      • AccessConnector SAP
      • Routty Cloud
    • KOFAX WHITEPAPERS
      • Readsoft Online
      • Power PDF Advanced
      • Autostore
      • SignDoc
      • Kofax ReadSoft Online Connector for SAP
    • SAP ARCHIVING
      • Archive Central Brochure
  • About us
  • News
  • Contact
  • Dutch

Vendor Payments

  • PaymentConnector SAP

PaymentConnector SAP

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.

  • PaymentConnector SAP

© 2025 ● Connect Solutions BV ● info@connect-solutions.nl ● T: +31(0)43 631 26 25 ● We are an official member of the SAP® PartnerEdge® open ecosystem ● Concept & build by: Socialhero.nu

We are using cookies to give you the best experience on our website.

You can find out more about which cookies we are using or switch them off in .

Connect Solutions
Powered by  GDPR Cookie Compliance
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.

Additional Cookies

This website uses the following additional cookies:

(List the cookies that you are using on the website here.)

Please enable Strictly Necessary Cookies first so that we can save your preferences!