Version: 4.5.2 (using KDE 4.5.1) OS: Linux Hello, I've first used MS Money, then GnuCash, and finally KMyMoney. The MS Money file has been imported through QIF export/import. I have also used OFX files. Note that a few transactions declared in MS Money, GnuCash, or OFX files overlap. I have found that some transactions "lost" their notes/memo in KMyMoney. It seems to be a display issue. Here is the content of such a transaction: <TRANSACTION ...> <SPLITS> <SPLIT ... memo="Memo A" id="S0001"/> <SPLIT ... memo="Memo B" id="S0002"/> </SPLITS> </TRANSACTION> Only the first memo ("Memo A") is displayed in KMyMoney. If I modify the notes through KMyMoney, both notes are set to "Memo C" (for example). That is, "Memo B" is lost. So far, I have only found issues on transactions imported from GnuCash (that may overlap with OFX imports). Reproducible: Didn't try Expected Results: Display all notes. And, most importantly, DO NOT lose information on modifications.
This is actually the way that kmymoney works. Each simple transaction has two splits one for the source account and one for the destination account. When you view the transaction from the source account "Memo A" is shown, when you view it in the destination account "Memo B" is shown. When you create the transaction in kmymoney the memo of the two splits are identical. The only way to obtain different memos is to go in the other account and change the memo from there which seems OK to me. Now if one of the accounts is a category then, if you view the transaction in the category (from the category's POV), you can't edit the transaction thus you can't obtain two different memos for income/expense transactions you can only do it for transfers. I'm not sure why it is this way but I think it has something to do with 'hiding the complexity of a double entry accounting system'. I'm going to mark this as not going to be done but if anyone has a strong opinion that this should be changed please speak up.
This seems related to bug 249844, except that refers to actions in KMM that change the memo only on one split of a transaction even if the user expected the memo to remain the same in both splits. This case is different because it refers to what happens on import when there are different memos in different splits of the same transaction. I know KMM wants to hide complexity, but should this include ignoring data on import that KMM really does have the ability to represent?