It’s a familiar scenario for many finance professionals: you’re deep in the throes of bank reconciliation, aiming for that satisfying zero difference, and suddenly, you hit a snag. You’ve meticulously matched transactions, reviewed statements, and yet, there’s a persistent discrepancy. The core of this challenge often lies in understanding how the 'Adjusted Bank Balance' functions within Microsoft Dynamics GP, especially when you encounter a situation where you wish to adjust it without altering the fundamental checkbook balance or the GL cash account.
The Unyielding Principle: The Bank is Always Right
As the documentation points out, the fundamental truth in bank reconciliation is that the bank’s record is the ultimate arbiter. If you've been reconciling for a while and consistently hitting a three-way match (adjusted bank balance, checkbook balance, and GL account), but there's an amount you feel shouldn't be there, it’s a sign that something has been amiss for some time. The adjusted bank balance reflects what your bank statement should look like after accounting for outstanding items. If this balance is off, it means either the bank statement's ending balance wasn't entered precisely as it appeared, or transactions were entered into the reconciliation window that shouldn't have been, or perhaps outstanding items were missed.
When the Adjusted Balance Leads You Astray
So, what happens when this adjusted balance is incorrect? The system is designed such that if you've achieved a three-way match over a period with an erroneous transaction in the reconciliation window, that incorrect amount has effectively been absorbed into your adjusted bank balance. Trying to simply remove that transaction from the reconciliation window without addressing its impact on the checkbook balance and GL cash account isn't directly possible. The system expects these figures to align. If a transaction was incorrectly added or an outstanding item was missed, it has already influenced the adjusted balance, and to correct it, you must also acknowledge its effect on your internal accounting records.
Addressing Discrepancies: A Practical Approach
This isn't to say you're stuck. The key is to understand that to 'remove' an erroneous transaction from the reconciliation window, you must also correct its impact on your checkbook balance and GL cash account. This might involve reversing an incorrect entry or ensuring that all outstanding items are properly accounted for. The documentation hints at this by stating that to get a transaction out of the reconciliation window, you must also affect your checkbook balance and GL cash account. It's about ensuring consistency across all financial records. For instance, if a deposit was entered twice in the reconciliation, you'd need to reverse one of those entries, which would then adjust both your checkbook balance and GL cash account accordingly, allowing for a true reconciliation.
The Importance of Accuracy from the Start
Ultimately, the goal is to ensure that the bank statement's ending balance is entered accurately into the reconciliation window. Any transactions that appear on your bank statement but not in your checkbook, or vice versa, need to be carefully considered and accounted for. The system provides tools to manage EFT/ACH files and to move reconciled transactions to history to help with performance, but the foundational principle remains: accurate data entry and diligent review are paramount. If you're carrying a negative balance or a persistent discrepancy, it's a signal to dig deeper and correct the underlying issue, rather than trying to force a reconciliation with an inaccurate adjusted bank balance.
