https://bugs.kde.org/show_bug.cgi?id=419974
Bug ID: 419974
Summary: MyMoneyStatementReader uses base currency instead
brokerage account's own when adding new price
Product: kmymoney
Version: git (master)
Platform: Other
OS: All
Status: REPORTED
Severity: normal
Priority: NOR
Component: importer
Assignee: kmymoney-devel@kde.org
Reporter: m...@dawidwrobel.com
Target Milestone: ---
SUMMARY
When importing new statement, e.g. as a result of CSV file processing, the
logic naively assumes the transaction's currency is the base currency instead
looking at the brokerage account's trading currency.
STEPS TO REPRODUCE
1. Create a brokerage account with a trading currency different from the base
currency, e.g. EUR and USD, respectively
2. import securities, e.g. using a CSV file with prices in EUR
OBSERVED RESULT
Price Editor shows all the imported prices denominated in USD instead EUR,
which throws off all the USD totals across the app. The amounts and quantities
are imported properly and reported in EUR. The ledger also displays the prices
properly. However, the "Investment value" denominated in base currency (USD) is
already off.
EXPECTED RESULT
Statement reader should use the target account's trading currency when adding
new price entries, since we already assume the same currency when importing the
transactions.
--
You are receiving this mail because:
You are the assignee for the bug.
