https://bugs.kde.org/show_bug.cgi?id=463708
--- Comment #11 from Jack <ostrof...@users.sourceforge.net> --- First, I do not believe there is any way to match the Category on import. The Category is set if the imported transaction is matched to an existing transaction. If there is not already a wishlist for that, perhaps we can eventually alter this bug for that purpose. Second, there are some import features available for online OFX import which might help, but are unfortunately not available for csv import. I have no idea how hard it would be to extend those features to file import. Finally, I'm actually not sure I understand how you plan to find the actual Payee from the long imported Payee. Payee matching happens at import time - I'm not aware of being able to do it after the import. Have you read the Handbook chapter on Payees, specifically the section on Transaction Matching Settings? https://docs.kde.org/stable5/en/kmymoney/kmymoney/details.payees.personalinformation.html#details.payees.personalinformation.matching Before I make any suggestions, I would need to see some real examples of the Description field your bank provides. Can you provide some? If it does include the Payee name, then you could set that payee to match on that name. Finally, I wonder if what you really want to do is to pre-process your downloaded csv to extract explicit payee and category columns from the description. It might be an extra step, but once you write the script, the extra work for each import might be less than what you plan. Separately, even if you continue as you started, how may payees do you eventually expect to have? The excessive import time is because each row needs to compare the "payee" (description) to every existing payee, looking for a match. If you are only importing a hundred rows at a time, and you only have a few hundred Payees, it won't be instant, but much less than 20 minutes. -- You are receiving this mail because: You are watching all bug changes.
