Ideally months should be closed and, hence, being "protected" from future mistakes (for example adding or removing a transaction by mistake in a month). This might be complex. Closing books is not trivial and the current solution of MoneyPro is simple (to compute everything from day 1, without any closing).
Still, sometimes I can spend hours to retrieve a mistake I made. Recently the software had also problems and started to duplicate transactions. I had to recheck everything.
My suggestion would be to add an "assert" transaction (assertion as defined in computer science). This means you state that a given date the account amount is X. If you do anything that break that assertion (for exemple delete by mistake a transaction before the date), a waring would pop up and say that you will "break" what the assertion states. This gives you a chance to give up on what you do and on not messing up the past history.
Right now I use a dummy transaction (called "information") in the comment of which I write the account amount at the given date. It gives me a chance to find out where is the mistake, but it can be still quite long.
I think such function can be simple to implement and help many people.
Best and nice product (although becomes challening to manage accounts with many many transactions)....
Please sign in to leave a comment.