Detecting Rounding Errors on Your Account

Cryptocurrencies that have a very low value when compared to the likes of ETH or BTC have long decimal values that are very important and significant even far after zero.

An example would be XVG. In December of 2018, 5,000 XVG was worth just 0.5 ETH.

Unfortunately, some exchanges like Binance round off these decimals rather early in the trade history file that you export. These rounding errors can add up and make it look like you are selling more of the cryptocurrency than you own when you import your CSV files into CoinLedger.

You will likely be able to tell if your Missing Cost Basis warning is being caused by a rounding error if you hover over the warning icon and see that the amount of XXX coin that you own at the time is very close but slightly less to what it says you are selling.

There are a few options for correcting these rounding errors.

Switch to API Import

If you notice that a rounding error from the CSV import is affecting your account, you may want to switch to API import. If you do not see that API is supported for the exchange, feel free to send a feature request to our Customer Support team.

Enter the Missing Decimal Amount Manually

A temporary fix is to add an income transaction into the Incoming Transactions template.

For example, if the Missing Cost Basis warning says you are attempting to sell more XVG than you own at the time of the trade and the amount you are selling is 4997, yet the amount that you own is 4994, then you should add an at a date prior to when you were selling this coin.

This fix will have little to no effect on your true tax position as long as you add enough of the coin just to fix the rounding error.

Did this answer your question?