Hi!

I've been using KMyMoney for a while for my personal finances, and really like it. However, there is one problem.

I import files from my bank accounts as csv-files, and when importing them, many of the comments/information is not imported. Instead of importing who the amount was paid to, I only get an "A". And others are interestingly truncated.
FOr instance, "Parkster" becomes "A", and "Bauhauskort" becomes "skor".

I have tried importing as UTF-8 or UTF-16 files, but so far, no success. In the import files window, it all shows correctly, but after import to the correct account, this "conversion" happens.

Any ideas on how to avoid this?

Magnus

Very strange. I use CSV to import bank data and don't see these problems. First of all: which version of KMyMoney are you using under which operating system, vendor and version?

In relation to your problem: do you have any payee matching enabled? See the manual section on transaction matching for more details if you haven't.

Hi!

KMyMoney 5.0.0, on Ubuntu 18.04.2. I have not set up payee matching.

One of my csv-files are here:
https://www.dropbox.com/s/ukrsfuw33034w ... j.csv?dl=0

Best,

Magnus

5.0.0 (or 5.0.1) might be a bit old. The CSV importer has received a few fixes and enhancements since then (see the projects release notes page for more details).

You may try to use a newer version via an AppImage which you can find on our build server. This AppImage is build every day from the source and will have a fix I just added which avoids a crash I noticed while loading your data into my system in build #115 by tomorrow.

Please report back if using a newer version resolves your issue or if there is something still open. Oh, you can download a KMyMoney file here until next Sunday which contains the imported data. I don't see a problem. Do you?

Hi!

Great, seems to be working with the appimage! However, a bit confusing, since I get no status report after importing the CSV-file - like how many items were imported, skipped, dubplicated etc, which makes it a bit more difficult to see what happes, I think.

But import seems to be working, as far as I can see. Going to test some more the next few days, see what turns up.

Best,

Magnus

Regarding the stats: that might be a (missing) feature that is working for other import methods (e.g. OFX and HBCI) the way you describe it. Needs to be checked.

Hi again!

Unfortunately, I was too quick. Using the appimage, version 5.0.4-ea3d48b, I still get the same "A" imported with the attached file. THis one is exported from another bank, but shows correctly in the preview when I choose ISO-8859-1 as character coding. But upon importing, many of the information fields are imported as "A" instead of the right content.

Any ideas on what is happening?

The file:
https://www.dropbox.com/s/62tpj6thor9ol ... s.csv?dl=0

Magnus

I am unable to duplicate that. I always get the correct contents into the fields. Can you post the contents of your ~/.config/kmymoney/csvimporterrc here (or on dropbox if you prefer)?

Hi!

How do I attach a file here....?

Here it is on Dropbox:

https://www.dropbox.com/s/3r035vs7hhe2p ... terrc?dl=0

Magnus

Hi again!

Got any new ideas on my problem?

Magnus

Not really. Did you ever run the application from a terminal? What is the output during the import on the command line? Maybe, this can provide some more information about what's going on.

Hi!

Good, this was interesting!! I tried importing a csv-file, as before, and there turns up a lot of stuff like these:

"Start matching payee" "Matilda Engman"
Found match with 'Matilda Engman' on 'A'
Found match with 'Matilda Engman' on 'matilda'
Multiple matches
Adding second split to Barn(A000011)

If I get it right, it finds a match in the list of payees. And that match is old and wrong. So: could the problem be that I have a bunch of such old entries there, that I should just delete?

Magnus

How does the matching entry for A looks like? Is it a 'Match payee name (partial)' then that would explain it. You could change that to 'Match payee name (exact)' or turn it off in case you don't need it for that payee. Or get rid of the payee completely (remove/delete it) in case you don't need it anymore. Since multiple matches are found, KMyMoney picks the first one. I see light at the end of the tunnel

YES!

I removed the payee "A", reassigned all there was to something else, and now the import seems to work!!

I did not change to "exact", I have it at "No matching", which is why I was suprised that there was matching done at all... maybe I should try Exact instead?

Magnus