-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Net investment not calculated on FIFO basis #141
Comments
Yes, as of today it's just an addition/subtraction on buy/sell. I assumed the net part would make that clear (I understand doing this way would make net investment go negative when you withdraw all money). I will have a look at it again and see if FIFO would make sense. If you have resources that talk about this stuff feel free to share the links here. I also don't know if FIFO could be applied universally. I do apply FIFO on tax harvesting page where the usage is clear. |
That makes sense. I was trying to reconcile with the Kuvera app. Mutual funds and stocks can have 2-3 prepectives to them - Realised, unrealised, and, total. We can make some changes to labels to align with current industry standards (atleast in India). For eg, (making these suggestion after looking at few bank apps and broker apps)
What do you think? |
Thanks for the feedback, let me take some time and think through it. Couple of things I have realized so far
|
I am seeing the same issue when I see XIRR calculated incorrectly where there are multiple buy and sell transactions for the same instrument. Using FIFO the XIRR is very different (as calculated by ZeroDha) vs what paisa shows. For all MF and equity instruments FIFO is the norm atleast in India so this can be an option for all calculations. |
Graph before withdrawal:
Withdrawal:
Graph after withdrawal:
Net investment goes from 17000 to 9700 after withdrawal of 7300. Instead we should be extinguishing units on FIFO basis and calculate Net investment remaining after that.
Cheers!
Thank you developing this.
The text was updated successfully, but these errors were encountered: