[kmymoney4] [Bug 362263] OFX import transactions inherit split from preexisting transaction

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362263

Jack <ostroffjh at users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ostroffjh at users.sourceforge
                   |                            |.net

--- Comment #1 from Jack <ostroffjh at users.sourceforge.net> ---
I can confirm I've seen this behavior in the past.  It appears that KMM takes
an imported transaction, and even if it doesn't actually  match it to an
existing transaction, if the closest match (although I have no idea what
criteria it might use) is a split transaction, then it makes the imported one
split also.  It's been a while since I've seen it, but as I recall, it's not
too hard to remove the extra/unneeded split, and make the transaction as it
should be.

Note that I can imagine some cases where this behaviour could be desired, such
as for a pay check, and you have set up splits to handle various deductions. 
However, I think most of the time, it is not desireable.  As much as I hate
adding to configuration options, or pop-ups for the user to specify details
about an import, I think the right solution to this requires one or the other -
either a setting to say never create a split transaction on import, or a pop-up
stating the import matched a split transaction - should it be used or not.

-- 
You are receiving this mail because:
You are the assignee for the bug.