[kmymoney] [Bug 518881] Account Ledger - Implement a user warning if a previously reconciled transaction is edited

[pc]

https://bugs.kde.org/show_bug.cgi?id=518881

pc <junk_2010 at live.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|DUPLICATE                   |---
     Ever confirmed|0                           |1

--- Comment #3 from pc <junk_2010 at live.co.uk> ---
Paul, thank you for the update.
I see you have closed this bug as a duplicate of bug 478530, which has itself
been closed as a duplicate of bug 449678.

I appreciate that I am only one user, however, I do not believe that this
ticket is a duplicate of the other two tickets. This is because if bug 478530
is implemented in its entirety it would I believe create a new issue with its
suggested automatic unreconciling of other transactions. Also to implement bug
478530 it in its entirety seems quite complex. I have similar concerns if bug
449678 is implemented in its entirety. Whereas what is being suggested in this
ticket is, at least at face value, a much simpler and a more “user beware”
approach that doesn’t actually stop the user doing anything if they really wish
to.


More detailed comments below.

In bug 478530 it says:
EXPECTED RESULT
KMyMoney should warn the user that entering the transaction will cause a
reconciled time period on the partner account to no longer be reconciled.
KMyMoney should then un-reconcile the checking account as of the date of the
new transaction.

An example of why the above implementation is not a good idea:
1) I have successfully reconciled an account to a specific date
2) For the next reconciliation period I realise that I had not entered a cheque
that had been written during the previous reconciliation period but not
cleared, and I wish to enter the cheque at the time of its transaction (date it
was written). An implementation of bug 478530 would un-reconcile the checking
account for the period the cheque was written in. To me this is undesirable
behaviour. I know I am not the only one who wishes transaction dates to be the
date the transaction was enacted, which is not necessarily the same date as the
transaction appears on a bank statement. See:
https://discuss.kde.org/t/wrong-starting-balance-in-reconciliation-kmymoney/39709/26
KMyMoney automatically unreconciling transactions does not seem a good idea to
me.


In bug 449678 it says (my comments in brackets):
SUMMARY
I noticed that it is possible to mark a transaction as reconciled outside of
the reconciliation process. I believe it should not be allowed. (I agree with
this in principle but I suspect that in practice there will be some users and
some potentially valid reasons for this to cause issues).

I would even think that if someone changes an old transaction that has been
reconciled, that the transactions after the changed transaction, should be
un-reconciled, to force a review. (I don’t believe KMYMoney unreconciling
transactions automatically is a good idea).

For now, I think it would be good if it would at least provide the option to
require the reconciliation process to execute before a transaction could be
reconciled. (Whilst I agree in principle there will be some users and some
potentially valid reasons for this to cause issues).


My summary is that the suggestion in this ticket is for a more basic, low level
approach - warn the user if he/she edits a previously reconciled transaction,
and allow them the option of what to do next. No automatic unreconciliation of
transactions if he/she goes ahead with the edit. This is the approach I have
seen in other finance programs. A much simpler “user beware” approach than that
being proposed in bug 478530 and bug 449678.

So basically I am suggesting the relatively simple idea of warning the user if
they edit a previously reconciled transaction is simpler to implement and
doesn’t actually stop people editing a previously reconciled transaction if
they really believe they need to do so. I also believe it compliments the more
robust, and now the same behaviour as KMYMoney 5.1.3, reconciliation behaviour
that has recently been implemented in the KMyMoney 5.2.2 branch. See bug 517479
and the discussion
https://discuss.kde.org/t/wrong-starting-balance-in-reconciliation-kmymoney/39709/26.

Hence I trust you don’t mind me re-opening this ticket to gather further
comment.

-- 
You are receiving this mail because:
You are the assignee for the bug.