Updated for 2025 – Because legacy systems deserve modern solutions
Check fraud is a bigger issue than ever, and banks have put stronger security measures in place.
According to the Financial Crimes Enforcement Network, check fraud attempts have increased significantly in recent years, with losses reaching billions annually. While these security measures protect your business, they often require extra work on your part—unless you’re using the right automation tools.
With the release of GP 18.7 (also known as GP 2025) in October 2024, Dynamics GP’s eBanking Suite has never been more reliable for SafePay file generation. The October 2024 update enhanced security protocols and stability, ensuring your positive pay files meet modern banking requirements and integrate seamlessly with updated bank portals.
Important 2025 Context for Dynamics GP Users: While Microsoft announced that new sales of Dynamics GP perpetual licenses will stop in 2025 and new sales of GP subscriptions will stop in 2026, existing customers can continue leveraging these powerful fraud prevention features. Microsoft’s commitment to support through 2029 means your investment in SafePay automation will continue protecting your business from check fraud for years to come.
Why SafePay Matters More in 2025: Check fraud has evolved beyond simple forgery. Today’s criminals use sophisticated techniques including check washing, account takeover, and mail theft to steal from businesses. The FBI’s Internet Crime Complaint Center reports that check fraud remains one of the top threats to businesses of all sizes. Most banks now require positive pay files for accounts with significant check volume, and manual file creation leaves your business vulnerable to formatting errors that can delay legitimate payments while creating security gaps. Automated SafePay file generation isn’t just about efficiency—it’s about protecting your business from increasingly sophisticated fraud attempts.
But How Do You Generate This File That You Send to The Bank?
Most banks, if you are cutting over a certain threshold of checks, require that you submit a file to the bank that includes the check number, the check date, the check amount and payee. Most banks will not clear your checks until they match all the information submitted. This helps to eliminate check fraud because a duplicate check number cannot be used.
The Manual Way to Do This
I have seen Dynamics GP users create a SmartList, export it to Excel, then manually type the additional information, such as the bank account number, into the Excel file. Then upload this file to the bank. This is a waste of time. And it can also lead to formatting problems.
For example, let’s say your bank account is 0025768. When you put this into Excel perhaps you didn’t realize that Excel cut off the first few zeros. So now the bank account shows as 25768 which is not correct and the bank will not accept your file. Checks are delayed. The same thing can happen with check numbers being formatting incorrectly.
There is an easier way.
The Smart Way to Do This in Dynamics GP
Everyone on the current licensing program of Microsoft Dynamics GP already owns SafePay as part of the eBanking suite. Once set up, after you have cut your checks in Dynamics GP the file for the bank can be automatically generated with no additional manual entry.
Plus, SafePay will alert you if you have used duplicate check numbers. Your upload file can also contain any voided checks to prevent anyone from using one of those checks for fraud. It can be used by anyone in the company (with permissions) and uploaded easily to the bank’s secure website. The process is clean, quick and efficient.
Read more: How Dynamics GP SafePay Can Protect You From Check Fraud
By CAL Business Solutions, Connecticut Microsoft Dynamics GP / 365 BC & Acumatica Partner, www.calszone.com
