[kmymoney] [Bug 341774] OFX file import behavior
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Thu May 17 03:16:10 UTC 2018
https://bugs.kde.org/show_bug.cgi?id=341774
--- Comment #3 from whelbig at windstream.net ---
On 05/16/2018 05:16 PM, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=341774
>
> Jack <ostroffjh at users.sourceforge.net> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |ostroffjh at users.sourceforge
> | |.net
>
> --- Comment #2 from Jack <ostroffjh at users.sourceforge.net> ---
> Does this still happen with a more recent version of KMM? There have been
> changes to the import code - but I do not know if this behavior should have
> changed, as I do not have this issue with the OFX files that I import.
>
I do not know if this behavior still persists. The bank that produced
the problematic file has merged with another institution and the .OFX
file I now receive is nearly useless. There is a small sample file
attached to the bug report that demonstrates the issue.
(To be clear the following is not a KMyMoney issue but rather a bank
issue that illustrates some of the gross inadequates of this bank's .OFX
implementation.
Almost every transaction downloaded must be edited to make it useful.
There is no Memo field only the Name field is given.
I have/had two vehicle and a personal load open and paid automatically.
The name that appears for all three is "Member Transfers" and the only
way to distinguish which is which is by the transaction amount.
All Debit card purchases include the text ATM/Debit Card Purchase as the
first 24 characters of a 30 character field leaving six characters for a
unique name.
All checks written show Share Draft as the payee and do not even include
the check number.
Probably more information than you wanted, but thank you for allowing me
to vent.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the KMyMoney-devel
mailing list