Registered Member
|
When doing an OFX import, Version 5.0.7 (U.S user, not German), with file downloading with this format (showing the header and first transaction):
The part with: <TRNAMT>63.68 is supposed to be a charge, but it instead appears as a payment in the ledger. KMM features a CSV import format tool, but it is simpler if there were import options when selecting the OFX file besides:
Method to detect duplicate transactions during import, and Timezone offset. Is there an separate add-on or other tool to designate the TRNAMT as a charge instead of a payment? BTW, I tried to import as a Quicken file but KMM only accepts QIF while this bank issues only QFX format. My workaround is to edit the OFX file and do a search and replace in three steps, like this:
|
KDE Developer
|
Do I understand it correctly that this simply reverses the sign of all TRNAMT on an account basis? This could be an additional option to be implemented in the OFX importer (like the others you mentioned).
ipwizard, proud to be a member of the KMyMoney forum since its beginning.
openSuSE Leap 15.4 64bit, KF5 |
Registered Member
|
That is correct. "Reverse charges and payments" could be an option for the import OFX dialog using this search and replace scheme.
|
KDE Developer
|
I opened #416279 on our bug tracker for it.
ipwizard, proud to be a member of the KMyMoney forum since its beginning.
openSuSE Leap 15.4 64bit, KF5 |
KDE Developer
|
... and implemented the feature today.
ipwizard, proud to be a member of the KMyMoney forum since its beginning.
openSuSE Leap 15.4 64bit, KF5 |
Registered Member
|
Nice to see the quick response by dev team to add this feature. I'm new to KMM, evaluating version 5.0.6 on Windows 10 as my possible replacement to Quicken 2017. I have questions related to OFX import:
1 - OP said "tried to import as a Quicken file but KMM only accepts QIF while this bank issues only QFX format".... I have an option in my KMM 5.0.6 to import OFX, and have discovered this import function will also import QFX. I have not tested fully enough to see if either type of file works better or if there are any issues with one. If someone know that this import does work correctly for both OFX & QFX, could someone change the menu label under Import to say both OFX/QFX? 2 - WIth OFX/QFX and also CSV imports, I'm have a lot of difficulty getting KMM to match transactions that are in the register. Example is a xan in my register for "All Trails" membership fee of 19.99. The downloaded xan in a csv or a qfx says "ALLTRAILS" same 19.99, same date. I was unable to get KMM to see these as a match until I manually changed my xan in the ledger to be the same"ALLTRAILS". I tried some different settings on the import but it didn't work until I changed my entry. Will KMM only match downloaded xans if the name is that exactly matching, even when the date and dollar amount match? Thanks for any experience or input! Jaimi NH USA |
KDE Developer
|
I try to provide some answers to your questions:
1 - QFX is Intuits proprietary extension of the OFX format. Since we don't know the details of this format, we don't want add it the UI, even though we hope that in most cases it will work (but there is no guarantee). See Wikipedia for some more information 2 - It does not need to be 100% identical. KMyMoney supports a few different methods to match the payees name with the regular expression one being the most powerful. See the manual for more details. Case-sensitivity can be controlled through a checkbox in that dialog. Hope that helps.
ipwizard, proud to be a member of the KMyMoney forum since its beginning.
openSuSE Leap 15.4 64bit, KF5 |
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft