Dynamics GP makes it easy to implement and manage electronic payments to customers or vendors with SafePay.
What is SafePay?
If you’re not familiar with it, SafePay, aka Positive Pay, creates a file which is sent to your bank detailing the transactions you create over a specific period of time. Then, when a check is brought to the bank, the uploaded SafePay file is referenced to avoid fraud. This file includes information such as account number, check number, date, and amount.
Now that you know what SafePay is, you’re probably wondering how to set it up.
How to Implement SafePay for Dynamics GP
Be sure to have a sample file format sent from your bank for reference prior to starting this process. You will also need to set up or designate an existing checkbook ID to be used for SafePay.
Configure your file in Dynamics GP: Go to-->Tools/Routines/Financial/SafePay/Configurator (See screenshot below).Please refer to this Safepay documentation for additional information. (Microsoft CustomerSource login required to view). Don’t have a CustomerSource login? Click here.Your bank prerequisites will determine what your finished configurator file looks like.
Create record fields to correspond with field names. (Again, follow the SafePay user manual as well as the bank’s prerequisites to populate.) Select one of the three output record lines and click Field Name. It will automatically take you to the next record once you hit “Save.”
Populate the transaction types. Once you have populated the record fields, select “Codes Entry” at top of output fields screen. Again, the bank will direct you with regards to the codes needed.
Save this file and export it to a safe location, so that you can retrieve it if necessary. It can easily be exported from one company and imported into another company within GP.
Send this file to the bank for them to test and confirm its validity. Once this has been done you may begin utilizing SafePay.
While you waiting for the bank to confirm that the file you just created was set up properly, you can go ahead and generate the upload maintenance file. This is done as follows:
In Dynamics GP, go to -->Tools/Routines/Financial/SafePay/Upload Maintenance
Create the bank upload ID, find the correct output format, and find the bank ID associated with SafePay.
Select the appropriate upload filename and path.
NOTE: You have the option to include EFT transactions with SafePay. Once you have completed the upload maintenance, make sure to save it.
Once you have verified the accuracy of this file’s format with your banking institution you may now begin using it with live transactions.
Have questions about SafePay and how it works? Leave us a comment below or send us an e-mail.
Want to learn more about the robust financial capabilities offered by Microsoft Dynamics GP? Visit our website.
By: Chris Butcher, Intelligent Technologies, Inc., A SC Microsoft Dynamics partner
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies. However you may visit Cookie Settings to provide a controlled consent.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.