Investment transactions imported via AqBanking have wrong matching / wrong memo field when viewed in the investment account's ledger. Details: I'm using AqBanking to import transactions from my account in DKB where I have several investment transactions. I've noticed that the "detail matching" is often incorrect and can't be turned off. One particular example. Whenever I import a transaction of a value (say, 300 EUR) its details in the investment acct. ledger are (erroneously) matched to a previous 300 EUR transaction. I got used to correcting these manually anyway based on the Memo/description field. However, this is problematic because the Memo field in the checking account ledger is imported correctly, but in the Investment account ledger the Memo field is taken from a previous transaction. I noticed this happens for transactions with the same value, but not always; it will only certainly happens if the transaction has a transaction fee associated with it. For example, I imported a transaction today for 300 EUR with the following memo: DEPOT 111111111WERTP. ABRECHN. 17.08.18000001111111111 WKN ABCDEFGESCH.ART KV__FUND_NAME__IHR FONDSSPARPLANPREIS 123,456700 EURSTUECK 1,2345 12030000/1111111111 When I right click this transaction in the Checking account to go to the Investment account, I arrive at a transaction that has the Memo same as the last transaction with the same value: DEPOT 111111111WERTP. ABRECHN. 11.08.18000001111111111 WKN FFFFFFGESCH.ART KV__OTHER_FUNDS_NAME__IHR FONDSSPARPLANPREIS 1,234567 EURSTUECK 123,4567 12030000/1111111111 I think there's at least two issues here: 1) The Memo should never be moved over/copied. Memo of a transaction in the Investment account should be identical to the Memo of the same transaction in the Checking acct. 2) Possibly, matching any details of investment transactions doesn't make much sense. The transaction is also prefilled with the wrong investment fund details. Possibly that's the reason that the Memo is also taken over, because it's consistent with the other transaction details.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!