Thank you,
@Tom Garrett, for the helpful attachments!
Since you have identified an actual journal entry that is out of balance, I think you may need to back out that entry.
I am curious, though, how this entry may have posted. Do you possibly have an add-in product that is bringing in PO invoices that may have caused this?
Before voiding the entry, I would do a little more digging to make certain that the GL is truly out of balance. Do you have access/comfort with SQL Queries? If so, you can check the data in the GL20000 table to confirm it is in balance. (I'm assuming JE 1036870 dated 01/31/2025 is in a current open fiscal year.)
I would also reconcile the financial year just to make certain the Detail and Summary information for the year is in balance. (Microsoft Dynamics GP > Tools > Utilities > Financial > Reconcile and then reconcile the Open Year that includes 01/31/2025.
If you don't have access/comfort with SQL, you can use SmartList > Financial > Account Transactions to export the transactions to Excel and sum the Debit Amount and Credit Amount columns. (Ideally you would do this for the whole fiscal year but that can be difficult if it is a large database. If that is the case, try exporting just January 2025 period, or even just 01/31/2025, to see if there truly is an out of balance.)
If you do need to back out the out-of-balance entry, here is a link from Crestwood on the steps to take. Note: I have not followed these steps before and I don't know if they are accurate and/or will work with an out of balance entry but the steps are logical and take advantage of core GP functionality:
Dynamics GP: Correcting Journal Entries - Crestwood Associates
[The last time I ran into an out of balance entry, I resolved it via SQL. The back-out GP functionality wasn't an option back in those days. 🙂]
If you back out the entry and then re-post it, you may want to reconcile the financial year one more time just to make sure everything still looks good.
