https://bugs.kde.org/show_bug.cgi?id=475666
--- Comment #1 from Jesse <jesgei...@outlook.com> --- My apologies for the long comments. I did some troubleshooting over the past few days. My only workaround to the original issue was to create an additional checking account in the same file and move transactions 1 statement at a time and then reconcile in the new account. This worked for a while and I got past the time period shown in my first attachment, but then it appeared again later but for a different amount ($323.52). At a loss, I scrolled through the transactions and noticed that a few were "bold" and realized that they were not marked as cleared. (Yes, you can start laughing/mocking this guy for something simple). Once marked as cleared the balances matched up and I could continue the reconciliation. Though I am quite sure that I marked them as cleared before reconciling. I'm getting old. However, back to the original problem, how can this be addressed for other users that won't recreate and reprocess and entire bank account (hey, I am doing this for my primary account from 2008 until today)? Somewhere I missed a $3 transaction but processed the reconciliation. - I couldn't add a fake transaction as it would throw off the real running balance - I couldn't adjust the reconciliation balance as it wouldn't match - If the $3 transaction was later reconciled, it wasn't affecting/correcting the balance - I saw another user Wish for the ability to change the starting balance in the wizard, but agree with you that that is not a good idea as it means that something is wrong. I was also considering improvements to the reconciliation wizard input box, like the preloaded ending balance that only sums transactions that are already marked as Cleared instead of the entire statement period, but in thinking about it, it makes complete sense. If they don't match up, something is wrong. Thanks for listening, and unless you want/need to address the issue above, we can mark this as closed. -- You are receiving this mail because: You are the assignee for the bug.
