Summary: | When importing a QIF file containing an intinc transaction, the interest income gets imported into the ledger as a fee, and the checking account is debited instead of being credited. | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | allan <agander93> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | REPORTED --- | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | git (master) | ||
Target Milestone: | --- | ||
Platform: | Mint (Ubuntu based) | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
allan
2014-12-04 23:30:40 UTC
Advice/opinions needed, please. This behaviour appears to be the result of this code snippet ( circa line 795 in mymoneystatementreader.cpp) - " if (statementTransactionUnderImport.m_strInterestCategory.isEmpty()) s1.setAccountId(d->interestId(thisaccount)); else {// Ensure category sub-accounts are dealt with properly s1.setAccountId(d->interestId(statementTransactionUnderImport.m_strInterestCategory)); }" It seems that, in spite of the actual imported activity type, this code knows better and decides on the basis of the sign of the amount. I'm not sure that's such a good idea, apart from causing head-scratching, i might wish to import a negative fee, to offset a previous error, or similarly for a dividend. Any thoughts, please? Apologies - missed line off. if (statementTransactionUnderImport.m_strInterestCategory.isEmpty()) s1.setAccountId(d->interestId(thisaccount)); else {// Ensure category sub-accounts are dealt with properly if (statementTransactionUnderImport.m_amount.isPositive()) s1.setAccountId(d->interestId(statementTransactionUnderImport.m_strInterestCategory)); else s1.setAccountId(d->expenseId(statementTransactionUnderImport.m_strInterestCategory)); } I can't really comment on the code or this particular case, but I certainly have had cause to enter negative amounts for both fees and dividends to enter a correcting transaction. I'd hate to have to use a "wrong" category, just to be able to enter a transaction that is needed for such purpose. (In reply to Jack from comment #3) > I can't really comment on the code or this particular case, but I certainly > have had cause to enter negative amounts for both fees and dividends to > enter a correcting transaction. I'd hate to have to use a "wrong" category, > just to be able to enter a transaction that is needed for such purpose. I was going to say you can't actually use a "wrong" category, as that gets chosen by the sign of the amount. However, it has just dawned on me that this 'feature' is invoked only on imports. So, there is no problem doing manual corrections and having them correctly recorded. In a way, that reinforces my doubt about imports working the way they do, even if the use is very infrequent. Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. |