Negative Balance Due to Incorrect Fee Deduction
complete
Sarah T. - CoinTracker
Users may experience:
- Users will see an erroneous negative balance in the outgoing wallet during a transfer where both the outgoing and incoming wallets have associated fees. The outgoing wallet is reflecting both the outgoing and incoming fees, creating an insufficient balance.
Expected behavior:
- Only the outgoing fee should be deducted from the outgoing wallet, and the incoming fee should be deducted from the incoming wallet.
As a user, what should I do?
- Users with fees on both the incoming and outgoing side of the transaction should deduct the amount of the fee from the receiving/incoming side of the transaction and ignore the second fee so there's no double fee on transfer.
Additional Information
Please upvote this post to indicate that you are experiencing this behavior.
We have information on
bug reports
and what the status means in our help center
. For further assistance or inquiries regarding this bug you can contact the support team
.Keywords: transfer fee, insufficient balance, negative balance
Log In
Sarah T. - CoinTracker
complete
Thank you for your patience as we worked on resolving this issue. The reported behavior has now been addressed. To ensure everything is updated, please re-import your data into CoinTracker using the Re-import feature.
If you continue to notice any issues, we recommend
contacting our support team directly
for further assistance. Additionally, please make sure view access
is enabled in your account settings, which helps us troubleshoot effectively.We truly appreciate your patience and cooperation!
S
Steep Perch
Sarah T. - CoinTracker
What do you mean reimport data? Your saying I have to delete and reimport all wallets? Or just refresh?
This post was marked as
being verified
This post was marked as
in progress
This post was marked as
planned
This post was marked as
confirmed
This post was marked as
in progress
This post was marked as
confirmed
This post was marked as
in progress
Support Ops Tools
This bug is still active as of April 3rd, 2025. It will not be fixed by the US tax deadline.
In the meantime, we suggest using the workaround listed in the report to handle those transactions.
This post was marked as
confirmed
Load More
→