https://bugs.kde.org/show_bug.cgi?id=342989
--- Comment #6 from harry bennett <kdeb...@saltyshells.com> --- I understand what you are saying, but it is theoretical not actual. In a perfect world that's how it would be. We do not live in that perfect world. My examples above are actual. If my CC company want's to credit my account 5 days before it leaves my checking account, that's their issue/problem not mine (unless of course the payment 'bounces'). Having the CORRECT dates (according to my account's statement) in my ledger on a per account basis is. As you yourself have stated, this sort of thing goes on all the time. The fact of the matter is, if i can't keep the dates correct in the ledger, then the ledger begins to fail in usefulness. The double-entry would, in fact, still exist. There would be no obfuscation (or the chance for more errors) via a (user edited) float account, as the transactions would be `glued` in KMM by the transaction#. As a secondary result, interest calculations would gain accuracy (see comment 4) OR (as you are suggesting?) A background float account could be created (transparent to the user), and in my scenario when dates do not match have a simple popup "dates don't match, should KMM float it -> y/n". leaving it otherwise transparent to the user unless they go digging for it. "<snip> It might be possible for KMM to add a second date to all splits, keeping a single transaction date for the internal bookkeeping...". this causes me to ask 2 questions: 1). which date would be driving the bus, as one of them would be incorrect. 2). although miniscule, would it not affect interest calculations (not that I care personally). What started all this was I reconciled my checking 3 weeks ago. than about 2 weeks ago I reconciled my VISA. When I sat down yesterday to reconcile my Checking, it was FUBAR. Although I have not found it yet, I am (fairly) sure that I have entered a transaction on the VISA side that tossed my checking, because I did not pick up on a (incorrect) date. This is becoming an all too regular SNAFU for me. Jack, thanks for taking the time to engage in dialog on this. I originally submitted this as a wishlist item to which it was marked as duplicate to bug 135198. I hope the devs get some usefulness out of our conversation. -- 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
