https://bugs.kde.org/show_bug.cgi?id=494072
--- Comment #4 from JAH <vanques...@gmail.com> --- Thank you for taking the time to review this issue. I apologise for the slow reply whilst I tried to recreate a dataset to better explain my experience. Your diagnosis seems quite right, that the problem lies with the “save to SQL” process in Vn 537 & 575 that I have tested. It seems to be partly corrected in the current Developer version master-3639 in that the following fields are now correctly populated EXCEPT in the Cash split: kmmSplits.shares kmmSplits.sharesFormatted kmmSplits.price kmmSplits.priceFormatted To test the process I posted one Foreign Currency dividend to a Base Currency Brokerage account (GBP in my case) and then duplicated the dividend twice at different forex rates. In each split, I recorded the forex rate used the memo field. With a Brokerage account in the Base currency, I would expect the sum of the Category Splits (here all in "Foreign Dividends") to equal the brokerage cash posting i.e. Dividend - Withholding Tax = Brokerage Cash In the developer version I notice that when posting these duplicate dividends kmymoney asks for a forex rate as each split is posted but does not ask for a forex rate (as usual) when committing the whole transaction. Consequently you should see in the attached files that instead kmymoney merely re-uses the “cash split” forex rate from the original transaction. Since the brokerage cash value is converted at a different rate from the splits it no longer equals the sum of those splits (highlighted in the attached spreadsheet). When posting these transactions it has always been difficult not being able to see the final brokerage cash value of the complete transaction (since that is what I’m usually trying to replicate). Instead a user has to leave the investment ledger and check the brokerage ledger to ensure the correct cash value has been posted then go back top the investment ledger for the next transaction. Would be possible to see the complete transaction (including brokerage currency values) in the new spit editor so a user could review / verify rates & values before committing the transaction? I have attached 2 files for each of 3 kmmymoney versions (537, 575 and Master3639) I tested. 1.) The original kmm files through which the transactions were input 2.) An highlighted spreadsheet derived from saving the kmm file as an SQLITE database. I did not test inputting transactions directly into the a SQL database. Please ignore any data in the memo fields apart from the Forex rate used (which are correct) I hope this better explains my issue and thank you again for a great product and continuing support. -- You are receiving this mail because: You are watching all bug changes.
