BittyTax
something not right with calculation
I have just started to use Bitty tax and have found a possible bug, I was give in Dec 2020 3 x 1.37 of CGLD coins with a buy value of £1.08, if i leave the buy value blank in the csv file and run Bittytax the results are shown in the top have of the picture which shows the wrong income, but if I put £1.08 into the buy value and run again, the results are correct (lower half of picture).
I own noticed this as I was just started using , but if I have many more it would be harder to spot if at-tail. and would mean I have to go through ever transaction to double check if buy vale is not entered.
It could be that Im looking at this wrong but keep up the good work.
Andrew
Hi @Roadrunneruk, if you don't specify a "Buy Value", BittyTax will try and retrieve the market price for that token on that date from one of the different price data sources.
It's possible that an incorrect price, or price for a different token is being returned, you can check this in the Price Data appendix in the PDF report, or run bittytax with -d to see the prices that are being retrieved.
Hey!
I noticed this question and feel it might be a good place to discuss this.
Ive noticed this a few times, where the price is incorrect becuase its fetching data for the wrong token (with the same ticker).
I wonder if it would be worth having a 'config' type sheet in the excel file for overriding things like this? So we could link to the correct token where its being pulled wrong? Just thinking outloud really, but might be useful.
Hey @leeovery, there is a bit of discussion about this here https://github.com/BittyTax/BittyTax/issues/74.
I think a good solution would be for the conv tool to normalise the symbol names so it can be done per exchange and maybe also taking into consideration the timestamp of the transaction.
This sort of dynamic config might be useful for the BittyTaxAPI to return when you first run the tools, so you don't have to re-install the s/w, the latest config would always get downloaded.
Thats a good solution I think.
Another thing, sort of related, is brand new tokens, and wrapped tokens.
eg.
- SMRT (https://smartcoin.farm/#/) is new and not recognised yet (Im hoping by the time I need the tax report it'll be recognised but what if its not)
- USDT.e is the wrapped tether on the Avalanche network - this isn't new but isn't recognised.
Maybe we create a tool that could check for this, and then prompt in the terminal so you can manually enter the missing values, and they are written into the excel file...?