portfolio-performance / portfolio

Track and evaluate the performance of your investment portfolio across stocks, cryptocurrencies, and other assets.
http://www.portfolio-performance.info
Eclipse Public License 1.0
2.89k stars 599 forks source link

Bugs regarding Taxes on Interests within Delta Widget & Performance Calculation #1647

Open heldic opened 4 years ago

heldic commented 4 years ago

As mentioned in the forum already, I noticed some oddities regarding taxes paid on interests. I've created a small test portfolio and attached the testportfolio.xml.zip to this issue for verification.

Version: 0.46.6 (Jun 2020) Platform: macosx, x86_64 Java: 11.0.4+11-LTS

Explanations are in the Dashboard in the attached screenshot:

InterestTaxOddities

PerformanceCalculation

cqst commented 4 years ago

I noticed a bug quite close to this one so I don't open new one at the moment. (version 0.46.6)

Here is what i noticed related to taxes in performance view :

Taxes are always 0 in "performance calculation" widget when filtering on a specific data serie (which is supposed to include taxes on the period selected of course).

When it's "entire portfolio", it's ok to me.

ericbrook commented 4 years ago

Even more info: It doesn't matter whether this is for a stock or for an account. The difference seems to come from how you book the interest and tax. In this example I booked interest and taxes on a deposit account.

Case 1: If you book taxes on interest using two bookings, one for the interest and one for taxes, calculations seem to be correct. Looking at the performance calculation 'before tax' the tax is then moved to 'Performance Neutral Transfers'. image

Case 2: However, if you book taxes on interest in a single booking (using the tax-field when you book the interest), then taxes are still taken into account even if you ask for performance 'before tax'. image

image

Unless I am missing something, the behaviour and calculations should be the same in both cases.

I have attached a testportfolio (Interest-test.zip) with the above scenario. Version: 0.46.6 (jun. 2020) Platform: win32, x86_64 Java: 11.0.4+11-LTS

Osti92 commented 1 year ago

I also noticed this error today. So it seems to be still up to date.