If I export an OFX file from my bank and import into KMyMoney, a transfer transaction is not able to be made a Transfer. I had to create a new Transfer transaction and delete the imported one. Is there a way to make an imported transaction a Transfer transaction, or is that something that KMyMoney is unable to do at this time?
Yes, you can convert a deposit or withdrawal to a transfer. You have to remove the category first, then you can change the transaction type. Then you can change whether it is "to" or "from" if necessary, and then specify the other account. The problem with transfers, is that from the bank's perspective, a transaction is only a transfer if the other account is also at the same institution. Otherwise, to them it really is a deposit or withdrawal.
Created attachment 109183 [details] attachment-17880-0.html Thank you for the quick answer. The transfer was between accounts at the same bank. It came is as a withdrawal. Eugene McClain On Saturday, December 2, 2017, 2:56:20 PM CST, Jack <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=387538 Jack <ostroffjh@users.sourceforge.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ostroffjh@users.sourceforge | |.net --- Comment #1 from Jack <ostroffjh@users.sourceforge.net> --- Yes, you can convert a deposit or withdrawal to a transfer. You have to remove the category first, then you can change the transaction type. Then you can change whether it is "to" or "from" if necessary, and then specify the other account. The problem with transfers, is that from the bank's perspective, a transaction is only a transfer if the other account is also at the same institution. Otherwise, to them it really is a deposit or withdrawal.
Having two accounts at the same bank and import both might initially end up with two distinct transactions: one a withdrawal the other one a deposit (with or without category assignment doesn't matter at that point). The next step would be to assign the 'opposite' account as category to each of them. This will lead to false balance information as the transaction now appears twice in both accounts (they are still distinct transactions. Deleting one of them does not help here, because each of them carries information for one account to detect duplicates during the next import. This will be deleted as well and in case you import the file again the transaction will reappear. The solution to this is to select both transactions in one account and 'merge' them into one using 'Transaction/Match'. p.s. Please use the forum at https://forum.kde.org/viewforum.php?f=69 or the mailing lists for user questions. Since it is not a bug, I close it here.
Created attachment 109191 [details] attachment-28436-0.html Thank you. On Sunday, December 3, 2017, 1:33:12 AM CST, Thomas Baumgart <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=387538 Thomas Baumgart <tbaumgart@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Thomas Baumgart <tbaumgart@kde.org> --- Having two accounts at the same bank and import both might initially end up with two distinct transactions: one a withdrawal the other one a deposit (with or without category assignment doesn't matter at that point). The next step would be to assign the 'opposite' account as category to each of them. This will lead to false balance information as the transaction now appears twice in both accounts (they are still distinct transactions. Deleting one of them does not help here, because each of them carries information for one account to detect duplicates during the next import. This will be deleted as well and in case you import the file again the transaction will reappear. The solution to this is to select both transactions in one account and 'merge' them into one using 'Transaction/Match'. p.s. Please use the forum at https://forum.kde.org/viewforum.php?f=69 or the mailing lists for user questions. Since it is not a bug, I close it here.