https://bugs.kde.org/show_bug.cgi?id=314352
Jack <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |.net --- Comment #1 from Jack <[email protected]> --- I'm not sure how the VAT support is supposed to work (I'm in the US) but I believe this is just an unintended consequence of the way Payee matching works on import. If an imported transaction matches a Payee, then KMM uses the most recent already existing transaction as the starting point for the imported transaction. I have a similar problem, but with a credit card. For example, most of the time I use the credit card at StoreA, I just buy food, so it is a plain transaction (not split) with category Food. One day, I need to split a transaction at that store (part Food and part Liquor, for example.) The next time I import a credit card transaction for that store, it will be imported as a split transaction for those two categories. The amount of each split will be for the amounts from the old transaction and the total will be the amount from the newly imported transaction, so the total will not match. However, when this happens, I only needed to delete the splits, and put the correct category on the transaction. You should also be able to edit the transaction, delete the splits, and create them as you want them. I don't think you should need to totally delete the transaction. Someone else will have to answer whether VAT support is supposed to have any different effect on this Payee matching process. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kmymoney-devel
