Binance API vs CSV difference in transactions

[T_G]

Hello,
I have both tried the binance API and csv’s to recreate my wallet.
I have noticed that my API is working smoothly but is showing a minor difference in my btc balance of 0.000004. The number of transactions is also much lower than my wallet generated through csv’s, the API seems to group transactions according to the ‘mouse click’ which is favorable for me because number of transactions can have tax implications.

The csv generated wallet however appears to be 100% correct for all balances.
But as I said the number of transactions in Koinly is much larger and could negatively impact my tax bracket.

Does anybody have any advice for me as what I could/should do?

thanks

[Adrian_Mann]

Simple answer is live with the small error.

Basically I assume its caused by a rounding error between the values reported by the Binance api and the number of decimal points they may be calculating to in Binance back end system.

From the three exchanges I use api imports (Binance/Gemini/Coinbase pro) I only have this issue myself with Binance.

As I hate errors I have actual entered a couple of manual dummy btc withdrawal and deposit transactions to remove the errors from koinly. At the moment I have more funds than expected 0.0000035btc but this does sometimes change after a trade. All I do is edit the manual/dummy transaction so balances are correct again.

There was an error with the koinly api that was fixed maybe just over a month ago with the api import of small dsut conversions. The issue was it didn’t import the BnB fee but this is fixed now. It was a bit of a pain getting these transactions fixed but in the end I discovered the easiest way was to delete these transactions and resync the wallet from the beginning.

[T_G]

Thank you for your reply.
How do you feel about making a dummy transaction? Doesn’t sound that great for tax reporting.

I have also noticed the following:
-as you mentioned there is a rounding error provided by Binance API, I have confirmed this by going over the csv’s
-The big issue I have is that Koinly appears to read this data but isn’t consistent in applying it to the balances reported. In the attachment I have added you can see the negative values that Binance provides through their API. If you coun’t these values my Koinly balance should report 0.04932173
instead koinly reports 0.04932174. This doesn’t seem to be a rounding issue as Koinly does not do this to other intermediate balance values.

[Adrian_Mann]

Think you have a far point there as I’ve never looked into it that closely.

The number of trades I have and the value of the error was insignificant compared to the tax I owe. I’m UK based and my dummy transactions have a total value of £0.12 The most it would affect my tax return by is £0.12 if it was 100% profit (in reality its a lot less than 100% maybe 50% profit so £0.06). In the UK on the tax return you round your gains to the nearest whole pound so its not going to make a difference (also I only pay 20% tax on gains so that reduces the error to about £0.03 tax).

Koinly support doesn’t really pay that much attention to these boards so if you think its a bug and you have a paid subscription its best to open a ticket within Koinly (blue message icon bottom right corner) and include screen shots if possible.

They may at least give you an answer why the numbers don’t add up.

[T_G]

thanks for the advice man.
You have a point about the insignificance of the amount.