Product Feedback

Bug Report: MATIC to POL Migration Classified as Taxable Trade What is the issue? Token migrations from MATIC to POL (Polygon Ecosystem Token) are being classified as taxable trades instead of non-taxable migrations. This results in incorrect unrealized returns and cost basis calculations. Who is affected? Users who held MATIC on Coinbase or Binance US during the automatic MATIC to POL migration period. What is the workaround? Users can manually reclassify the affected transaction by selecting the ⋮ menu on the transaction and choosing "Mark as non-taxable." ⚠️ Manual Edit Disclaimer Manual edits are a temporary workaround and will not be overwritten by future fixes or re-syncs. However, manual changes can sometimes result in duplicate transactions or other unintended side effects. Edits should be made with caution. Once a permanent fix is released, manually edited transactions may need to be reviewed or removed to ensure accuracy. Keywords: MATIC POL migration, token swap, taxable trade, cost basis, Coinbase Binance US

What is being requested? There are number of transaction types and features that Robinhood offers to users, some of these features are not supported by CoinTracker via our API integration. These transaction types and features include: Bonus Crypto Crypto Rewards Staking Withdrawals/Deposits Transfers between Robinhood wallets These transactions will likely be omitted or missing from your imported transaction history via our Robinhood integration. What can users do now? Users will need to manually add these missing or edit incorrect transactions to ensure their entire portfolio is reflected in CoinTracker. Users can upvote this post to receive updates. For further assistance, please contact our support team directly . Keywords: Robinhood API, bonus crypto, referral rewards, missing transactions, Robinhood

What is the issue? Trades of BNB for BNBLion (ERC-20) token result in $0.00 cost basis. Leading to incorrect cost basis carry forward on Transfers of the BNBLion token and incorrect gain/loss when tokens are disposed. BNBLion Contract: 0xdA1689C5557564d06E2A546F8FD47350b9D44a73 Who is affected? Users trading for BNBLion token on BNB Smart Chain (BSC) What is the workaround? No workaround available at this time. You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. Keywords: erc20 tokens, BNBLion, bnb smart chain, missing cost basis

What is the issue? Coinbase One credit card payments are being categorized as taxable send transactions. These transactions are payments made to pay off a credit card balance using USDC from the user’s Coinbase account. Who is affected? Users making Coinbase One credit card payments with USDC from their Coinbase account. What is the workaround? No workaround available. Keywords: coinbase, usdc, credit card, ingestion, taxable

Users Feature Request: As a user I would like support for derivatives trading offerings such as margin, futures, and leveraged trading products - I want to be able to either sync my trades automatically into CoinTracker or have CSV support to be able to include them in my crypto trading activity. *Note: Read our blog on derivatives trading here. * As a user, what can I do? Unfortunately, CoinTracker does not support derivatives trading, this is an offering we would like to support in the future. There is no workaround at this time, we recommend connecting with your tax professional on how to manage derivatives activity. You can upvote this feedback post to indicate you would like this feature added! The post status will be changed to Complete should we pursue this feature. Up-voters will be notified of the status change. I need additional assistance, who can I contact? For further assistance, please contact our support team directly. Thank you for your feedback and cooperation as we work to enhance your CoinTracker experience! Keyword: derivatives, margin, futures, perpetual futures, CSV, leveraged trading

What is the issue? CoinTracker does not automatically match send and receive transactions to a Transfer transaction when 2 assets received are grouped into 1 receive transaction. Who is affected? Users whose receive side of a transfer is grouped into a single receive transaction for multiple assets may be affected. What is the workaround? Manual workaround would be to group the assets into a single send transactions to match the receive Keywords: transfer matching, grouped receive, multi-asset, timestamp, transaction

When withdrawing HBAR from Kraken to a personal wallet (Ledger), CoinTracker groups the transfer and staking reward into a single “Multiple” transaction. Example behavior: • Kraken withdrawal: 508.82312 HBAR (transfer to Ledger wallet) • Staking reward received at same time: 8.84461019 HBAR CoinTracker imports this as one transaction containing: Receive: 508.82312 HBAR Receive: 8.84461019 HBAR (staking reward) Send: 508.82312 HBAR from Kraken Because of this grouping: The withdrawal is interpreted as a taxable SEND instead of a transfer. The staking reward cannot be separated from the transaction. The UI does not provide an option to split the transaction. The only available workaround is to mark the send as non-taxable or ignore the entire transaction and recreate it manually. Expected behavior: The transaction should automatically import as two events: Transfer Kraken → Ledger 508.82312 HBAR Staking reward (income) 8.84461019 HBAR This issue appears to occur because Hedera transactions can contain multiple operations within a single transaction hash. Feature request: • Add the ability to split “Multiple” transactions in the UI • Automatically detect transfer + staking reward combinations • Correctly classify exchange withdrawals as Transfers instead of Sends Without the ability to split these transactions, users must manually recreate transactions to ensure accurate tax reporting.

I transferred a custom token from one wallet to another and the transaction is classified as Trade, which affects long/short term holding and corresponding tax. There is no option to select Transfer type for the transaction.

What is the issue? Binance US transaction history not aligned between API sync, CSV export and account screenshots causing transactions to be missing from CoinTracker. This seems to specifically be affecting staking transactions. Who is affected? Users with Binance US accounts performing staking transactions, especially if relying on API sync or CSV import to reflect staking activity. What is the workaround? Users can manually add the missing staking transactions based on their Binance US account history. Keywords: Binance US staking, missing transactions, API sync issue, CSV import, MATIC ETH stake

What is the issue? Derivatives trades on the Typus Finance protocol (Sui network) involving negligible amounts of SUI and USDC are being displayed and calculated as extremely large cost basis and gains/losses. This creates misleading P&L and tax/income reporting. Who is affected? Users who interact with Typus Finance protocol on the Sui network. What is the workaround? There is currently no known workaround. You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. Keywords: Typus Finance, Sui Derivatives, perps, inflated gains, cost basis