https://bugs.kde.org/show_bug.cgi?id=342989
--- Comment #4 from harry bennett <kdeb...@saltyshells.com> --- Sorry, but I have to disagree as I have the statements to prove it. This is not hypothetical. This is real world. I feel that one of us is over-thinking this. According to their respective statements one account shows one date, a different account shows another,...... for the same transaction. This is an `issue` in the software because we are referencing against the date and not the transaction#. The transaction # should be the binding element not the date. We already know that a transaction can be split across multiple accounts. It would appear that although KMM assigns a transaction # it actually uses the date for reference. If KMM used the Transaction # for reference instead, each side could have a different date. As such, each side can/may perform any (additional) calculations using the date referenced on it's side respective of the transaction, such as interest. Example: [as viewed by Checking] transaction# (assigned by KMM)|trans_date | post date| transaction| amount 1234567890 |24dec14 | 29dec14 | to CC |too much [as viewed by CC] transaction# (assigned by KMM)|trans_date | post date| transaction| amount 1234567890 29dec14 | 24dec14 |from checking|never enough all that has occurred is a 'perspective' has been assigned to each side held together by the transaction # instead of by the date. Much like one side sees a credit and the other showing a debit. As far as interest calculations go, my CC balance is reduced on 24dec and interest charged on the payment amount stops then, but checking balance is not reduced until the 29th therefor collecting interest until then. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel