I'd like to change an account from being categorised as"asset" to "liability"

I imported using QIF (only available) from Homebank. However all my accounts are labeled as "Asset" & "current", even for example credit card accounts. How can I change existing accounts with their existing information to be listed as another e.g "credit card" under "liability" section? For example if I go on "edit account" under the "opening information" "type" only "current/savings/cash" are listed because this account is under the "asset" category. Or how could I make a subset of "asset" and change it to that?

There are two possibilities: a) modify the QIF files you have to carry enough information that KMyMoney detects the right account type during import or b) create the credit card account afresh, open the false account, select all transactions and move them to the newly created account. Once all transactions are moved, you can delete the old account.

Hope that helps

Cool, I was also wondering how to achieve this, independent of a QIF import.
(Though, I am still wondering why an account can't be reassigned to another type in the account editor.)

mkae wrote:(Though, I am still wondering why an account can't be reassigned to another type in the account editor.)

Most likely, there are incompatible dependencies; i.e. operations which could not be converted if the account type changed. An obvious example is an associated brokerage account: you can only have that with an investment account. There may be type-dependent restrictions in scheduled transactions (though at first sight I could not find any).

Hi,

I know old post but my question fits:

How can I move transactions from one account to the other?

If I select mutliple transactions in the ledger, I see no way to achieve that. If I right-click on the selection, it falls back to selecting the single line where I right-clicked!

This is something I'd really need!

Thanks!

If I select mutliple transactions in the ledger, I see no way to achieve that. If I right-click on the selection, it falls back to selecting the single line where I right-clicked!

You can open the context menu using the Menu_key.

Wow, amazing!

You know this is the first time in my life that I ever pressed the menu key (I am on windows 7)!!

Why does this option not appear in the "Transactions"-Menu on the menu bar like all other interactions?

So, for complete accounting happiness, I'm still wondering: I'm important a great many transactions from a self-made excel accounting "system" and expect to make many adjustments. Being able to move transactions between accounts is a life-saver, BUT: what if I decide a transaction (or rather a number of transactions) should be converted from an expense/income to an asset/liability or the other way round?

Let's say I've started to track cash withdrawals as expenses, but now decide I want to create an asset account "cash" to do more fine-grained accounting on daily cash expenses.. How do I move the existing withdrawals from the expense account to the asset account? I guess if they all originate in the same account then I just go to that account, search for the items and change from withdrawal to transfer, but what if I want to do that for several accounts where I can withdraw cash? I'd ideally like to have all accounts listed in the "move transaction" selection, not only the transactions of the same type!

Thanks!

Why does this option not appear in the "Transactions"-Menu on the menu bar like all other interactions?

Because it is only added to the context menu, I don't know why... that the way it was since I joined the community.

I'd ideally like to have all accounts listed in the "move transaction" selection, not only the transactions of the same type!

The same answer as the above. I don't see why an expense can't be changed to a transfer by moving the split from the expense account to an asset account but that's the way the application is written right now...

Did you know that you can edit multiple transactions using the transaction form? You can obtain the same result as 'Move transaction to...' by editing the transactions and changing only the category field.

Interesting - maybe this can be changed easily, if I need that more often, I'll have to take a look at the code! Otherwise I will need to resort to sql manipulation

About editing multiple transactions at once: that only works for assets/liabilities, not for categories. I do not understand why, it seems like a random restriction...

It's not just random. When you change transactions to another type of account, you have to take into account many factors to make sure you are not doing it wrong and then you get imbalances somewhere along the way.
In fact, you could only move as-is, from asset accounts to expenses (and viceversa), or from liabilities to incomes (and viceversa). In any other case, you have to adjust it manually or you would violate the double-entry principles.
You could of course, try to infer things and kind of do it automatically. In the end, we are playing with your data, and we prefer to keep it simple and safe, rather than sorry.

Thank you.

My comment about "random" was with respect to the inability to change transaction data in the category view (e.g., the payee or so).

Regarding double entry: I'm not an expert on this, so I'd like to learn: what happens if I move a split from expense to asset, for example? I understand that in double entry book-keeping, any account can have both positive and negative amounts booked on it?

About editing multiple transactions at once: that only works for assets/liabilities, not for categories. I do not understand why, it seems like a random restriction...

You don't need to do it for categories since changing the category when editing asset/liabilities is like making a 'move transaction' from the categories.

Yes, that it true, but I could also change other aspects of the transaction (payee or so)...

Christian, just wanted to say 'thank you' for this advice - it helped me fix this same issue.

Christian, just wanted to say 'thank you' for this advice - it helped me fix this same issue.

You're welcome.