My bank is ING Belgium. Their export is too complex, with the transaction information broken in the following fields (taken directly from the CSV): Account Number;Account Name;Counterparty account;Entry number;Booking date;Value date;Amount;Currency;Description;Entry Details;Message I had been able, with 4.7.x, to edit that CSV, and add two columns, one with the concatenation of the Counterparty account, Description, entry details and message for the memo, and another with Description and entry details for the payee. The fields would look as follows in the CSV: Account Number;Account Name;Counterparty account;Entry number;Booking date;Value date;Amount;Currency;Counterparty account-Description-Entry Details-Message;Description-Entry Details;Description;Entry Details;Message The other relevant information is that comma - "," is the decimal separator. With 4.8.0 and 4.8.1, the importer stubbornly decides that the field separator is the colon ":" if I feed it the changed CSV. I first tried editing the CSV and replacing the separator with the colon, but then the importer decides it should be the comma. If I use semi-colon, comma, or tab, it always claims the separator is the colon. This would be ok IF it were possible to change the separator in the importer, but that is impossible for some reason I just can't find. This behaviour, and the impossibility of overriding it, makes the CSV importer nearly useless for me. The information is split in so many ways by ING's exporter that in some cases "Description" is empty, in others has only "European Direct Debit", in others is "Entry Details" that is empty. I can provide a couple of example files, but they have too many details on my bank account and movements for me to be happy to provide them publicly.
Forgot to add, I am running MX Linux 17.1. Previously I was running MX Linux 16/Kmymoney 4.7.1
Created attachment 114613 [details] test file I tried this with the recent and maintained version 4.8.2 and could not reproduce the issue with the appended test case, which I created based on your informations. My suggestion is to update to 4.8.2
I can send you privately a file that triggers the issue. I'll also try to mask some data on a file to upload here, or as an alternative try to expand your sample until it happens. I tried to build kmymoney for mx-linux (debian based), as the last version available here seems to be 4.8.1, but found out I need to relearn a lot on how to build debian packages. Will keep trying.
Created attachment 115245 [details] Sanitized csv import This file "convinces" the importer to assume the separator is the colon, instead of the semi-colon
I've managed to build and run version 4.8.2, it still has the issue with the file I just attached.
As a workaround I fixed the ofxstatement conversion for ING Belgium and am using it now - https://github.com/jbbandos/ofxstatement-be-ing
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!