[kmymoney] [Bug 392755] kmymoney-4.8.1.1 suggestion: Category for realized profit/loss of an investment

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=392755

mahueb55 at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mahueb55 at gmail.com

--- Comment #5 from mahueb55 at gmail.com ---
While I understand the issue and do agree that the profits should show as an
income category (and losses as expense, accordingly) I am not sure whether I
agree with the requested solution. The example no. 2 Christian gave is ONE way
to value inventory (of securities, in that case) - FIFO, but it is certainly
not the only one. Who says that the 5 shares that were sold on 2018-01-01 are
the ones bought in 2016?

>From my point of view, the ideal target situation is:
- add the possibility to configure the valuation method (LIFO, FIFO, AVG, ?)
per security
- add the possibility to configure a category for  "gain/loss from sale of
securities" (or one category for gains and a separate one for losses) -
globally, per investment account or per security (to be discussed)
- then, when posting the sell transaction, derive the net gain or loss incurred
through the sales transaction automatically based on the configured valuation
method and
- automatically split the transaction and assign the gain/loss fraction of the
transaction to the category configured above.

That way, we're ensuring consistency. If we manually entered the gain or loss
instead we could end up with inconsistencies pretty fast because we would not
be able to guarantee that (buy transaction value) + (manually entered
gain/loss) = (sell transaction value). Or am I missing something?

Sidenote: It probably makes sense not to allow changes of the valuation method
as long as there is any nonzero number of shares of that security on our books
because past transactions would need to be revaluated in order to arrive at
correct & consistent values otherwise.

-- 
You are receiving this mail because:
You are the assignee for the bug.