GP 2016 – Bank Reconciliation, Credit Limit, and Safe Pay
Posted on: February 10, 2017 | By: Craig Thompson | Microsoft Dynamics GP
Authored by: Brent Stabiner
As of December 1st, 2016, Microsoft has released GP 2016 R2. With the release comes a small collection of new features and improvements. This post will cover a few different improvements and marks the fourth of several in a series of posts over the next several weeks that will cover these new features.
On December 1st, the Microsoft development team sent an email stating the following:
The Microsoft Dynamics GP team is pleased to announce that Microsoft Dynamics GP 2016 R2 has released! Dynamics GP 2016 R2 continues the great value delivered in previous Dynamics GP releases. Dynamics GP 2016 R2 includes enhancements to SmartList Designer; Power BI reports available on the home page in web client; key additions to the Project Accounting and Requisitions; and 25+ functionality features prioritized by customers.
Thanks to everyone for your efforts, passion and contributions to making Microsoft Dynamics GP 2016 R2 a great success!
The first improvement to be covered in this article is the Bank Reconciliation module’s ability to track history. There is now a new process for Reconciled Transaction Maintenance in the Routines section of the Financial module. This process moves reconciled transactions to the bank reconciliation history tables. As a result, the bank reconciliation process performance will include, as history and open tables are separated. Now, when a user removes the history in the Bank Reconciliation module, the reconciled transactions that have been moved to the history tables will be removed.
Another great improvement that came with the release of GP 2016 R2 is to credit limit warnings. Prior to the R2 update, the credit limit warning calculation would not consider unposted credit documents that have an amount already applied to a posted debit document. After the update, when GP does the math to determine if the credit limit is exceeded, the calculation will now include the unposted credit documents. This results in a much more accurate credit limit calculation.
Safe Pay, GP terminology for Positive Pay, also saw an improvement with the upgrade to GP 2016 R2. Prior to the release of this upgrade, the Safe Pay ACH file would contain the Vendor ID name in full when configured to display the vendor name on the detail payment line. If the Vendor ID didn’t match the Check Name on the Vendor Maintenance card, it would cause some confusion. However, now the Safe Pay ACH file will display the Check Name so it will match with the Payee Name printed on the check.
2020 Nucleus Research Report on ERP Technology