is there a way to avoid that?
We really need more information. It may not matter, but what version are you using (from Help/About) on what OS/Distribution. What exactly do you mean by “every update?” It is always the same stock/equity? Assuming you mean importing (either direct or with a file) is there a matching entry in the update file (what type of file is it?
Sorry. I use currently 5.2.2 on Linux Mint 22.3. Im just migrating from another personal finance manager (which is available only under windows).
It happens when I run an update on my investment account using aqbanking. Not for all shares (etfs) but for some of them. All with the text “Dummy booking added by KMyMoney to reflect online balance - please adjust” and all with the quantity of 0,00000. When I check the quantity for the shares affected in kmymoney with the value provided by my banking app, its exactly the same.
I searched the repo when and why this addition of a transaction was added. Found it. Still don’t fully understand why it happens in your case.
Since you’re running on Linux, can you start KMyMoney from a terminal window and perform the download. KMyMoney will print additional information to the terminal window. Most important is the part where it processes the import from the bank and shows a message with the following content:
Creating dummy correction booking for 'XXX' with #.#### shares
where XXX is the symbol of the investment and #.#### a value. Can you drop that line here?
BTW: when the numbers match and no transaction is created, KMyMoney prints
Online balance matches balance in KMyMoney account!
sorry for the late reply .. was on holiday .. now i have the problem that I can’t update the depot anymore .. always get the result “Orders could not be encoded” ..
in the console i can see “JobGetBalanceInvestment” with code “HKWPD” .. looks good for me .. but afterwards I see “job_virtual.c: 279: No segment results” in the console ..I think i will need to do some more research here maybe even some debugging ..
at the moment i can’t get it to work .. i switched to csv-import .. i will come back if everything else is setup and working properly
A fix for this has been added to the development version. It can be downloaded from the download page showing the development version. Can you check if solves the problem with the unnecessary transaction? Thanks.