Bug 447457 - An OFX-imported transaction assigned to "Liability" will change from Deposit to Payment (or other way round) when re-assigned to "Expense"
Summary: An OFX-imported transaction assigned to "Liability" will change from Deposit...
Status: REPORTED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.1.2
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-24 06:22 UTC by Dawid Wróbel
Modified: 2021-12-24 09:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dawid Wróbel 2021-12-24 06:22:19 UTC
SUMMARY

A transaction assigned to "Liability" will change from Deposit to Payment (or other way round) when re-assigned to "Expense" or "Asset". This only happens once after the initial import of the transaction.

STEPS TO REPRODUCE
1. Import a transaction using OFX (using Direct Connect here, need to check if importing from OFX file applies as well)
2. Re-assign the category from the originally assigned to one of the opposing type (i.e. if it was Liability, assign to Asset or Expense and vice-versa).


OBSERVED RESULT
Notice the transaction changes from Payment to Deposit, or the other way round. Re-assigning the category back to the previous one at this point does nothing.

EXPECTED RESULT
Nothing should change except the category itself when re-assigning the transaction.

ADDITIONAL INFORMATION
This is most likely caused by some inconsistency in how the splits looks like in the imported transaction.
Comment 1 Thomas Baumgart 2021-12-24 09:25:38 UTC
Are you able to provide sample .kmy and .ofx files to reproduce the problem and attach them here? That would help very much.

Note: no need to check if that applies to file import as well. It does, since it uses the same logic.