Bug 426796

Summary: reports in more than one currency do not convert to base currency for totals
Product: [Applications] kmymoney Reporter: jlboz <KMyMoney>
Component: reportsAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED DUPLICATE    
Severity: normal CC: ostroffjh
Priority: NOR    
Version: 5.0.6   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:

Description jlboz 2020-09-21 07:24:16 UTC
SUMMARY

Various reports, such as budget reports, and the Assets & Liabilities Summary on the home page, can include entries from accounts in more than currency. When calculating totals KMM adds the numbers without any currency conversion. The result is therefore wrong if more than one currency is included. For example, if the base currency is Australian dollars and a report includes 100 Russian roubles and 100 Australian dollars the total is reported as 200 Australian dollars when it should be more like 103. 

There does not appear to be any setting that can fix this. The report configuration setting "convert values to base currency" makes no difference: the result is the same whether this setting is selected or not. In any case there is no reason anyone would want a report in more than currency without conversion because the totals must be nonsense. Also, the Assets & Liabilities Summary is not a report and cannot be configured using report settings, so it will still be wrong even if each report could be fixed with the existing settings.


STEPS TO REPRODUCE
1. open a report that includes entries with more than one currency
2. find a total which combines entries with more than one currency
3. 

OBSERVED RESULT

Total equals the numerical sum of each entry

EXPECTED RESULT

Total equals the sum of the entries after each is converted to the base currency

SOFTWARE/OS VERSIONS
Windows: 10
macOS: n/n
Linux/KDE Plasma: n/n
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.47.0
Qt Version: 5.9.1

ADDITIONAL INFORMATION
Comment 1 Jack 2020-09-22 20:39:34 UTC
The issue is not in the conversion, but in the labelling with the wrong currency.   Fixed in 5.1.1.

*** This bug has been marked as a duplicate of bug 423870 ***