Product Feedback

What is the issue? CoinTracker imports a Kraken USDC buy correctly but classifies the following hybridearnwithdrawal as a standalone send instead of an internal transfer into Kraken Earn. No corresponding receive is created and no Earn wallet is created. Who is affected? Users syncing Kraken accounts with Kraken Earn transactions involving hybridearnwithdrawal entries after a USDC purchase. What is the workaround? No workaround available. Affected users may upvote this post to stay notified of updates. Keywords: kraken, usdc, earn, withdrawal, ingestion

There are 2 different portfolio numbers. I am logged in as the same user but there is a stark difference from what I see on the Webpage. I though the APP is a read-only from the webpage?

Users Feature Request: The search bar on the Transactions page is not properly applying date filters. The manual date filter still works, but can be slower and tedious compared to the search option. Example: type a date (e.g. "Dec 24 2018") in the search bar → transactions auto-filter to that date/range. Current behavior: typing a date does nothing; only the manual date filter works. As a user, what can I do? You can 🔼 upvote this feedback post to indicate you would like this feature improved! The post status will be changed to Complete should we pursue this improvement. 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: transaction filter, dated, date filters, search by date, transactions

What is the issue? When a transaction contains both a Staking reward and a Stake operation, the staked lot is chosen by the account's cost basis method rather than the reward lot just received. The cost basis on the Stake row often won't match the paired Staking reward row. Reported income isn't affected, as that comes only from the Staking reward rows. Who is affected? Customers with auto-compounding staking positions, whether auto-imported or entered manually. What is the workaround? No action is needed for income reporting. Customers who need the staked lot to match can edit cost basis on the affected Stake rows. Manual edits won't be overwritten by future fixes, but can cause duplicates or other side effects and may need review once a fix ships. You can upvote this post to indicate you are experiencing this behavior. The status will be updated once a fix is rolled out, and up-voters will be notified. Keywords: staking, auto-compound, cost basis, lot selection, stake, staking reward, Flexa

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.

The coin went from old contract https://etherscan.io/token/0xb90b2a35c65dbc466b04240097ca756ad2005295 to new contract https://solscan.io/token/4nV5gNwwP68zUDat26ySChREqVaQaLudfJBkSgEzpump via https://migrate.fun/project/mig172

Users Feature Request: Implement a bulk editing token feature for correcting token recognition errors in transactions on CoinTracker. When CoinTracker incorrectly identifies a token in a transaction, users currently have to manually edit each transaction to select the correct token. This process can be laborious and inefficient for users with hundreds or thousands of transactions. A bulk editing tool would streamline this correction process, similar to the existing functionality for bulk ignoring transactions. As a user, what can I do? Reach out to customer support to be added to the beta group for testing the feature. 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! Keywords: bulk editing, token correction, transaction management, user efficiency

Users Feature Request: Improve the process for editing the cost basis of an outgoing asset in CoinTracker. Currently, users must navigate through several steps to locate and edit the incoming transaction that sets the cost basis. This process can be cumbersome and unintuitive. A direct method to access and modify the cost basis from the outgoing transaction's details would enhance user experience significantly. As a user, what can I do? To adjust the cost basis for an outgoing asset, follow these steps: Navigate to the Tax Center for the year of the outgoing transaction (for example, for 2023, go to 2023 Tax Center ). Download the Capital Gains CSV from the bottom right of the Tax Center. In the CSV, search for the outgoing transaction. The Received Date column shows the date of the transaction where the cost basis was set. Go to Transactions and filter by the Received Date. There, you can edit the cost basis of the token. You can 🔼 upvote this feedback post to indicate you would like a more streamlined 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! Keywords: cost basis, capital gains, tax reporting, transaction editing

Users Feature Request: Implement a feature on the CoinTracker transactions page that clearly indicates whether a capital gain or loss is classified as short-term or long-term. Allow for filtering on gains. As a user, what can I do? 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: capital gains, short-term, long-term, transactions page

Users may experience: Some users have reported that some of the token amounts shown in their cardano transactions are in the wrong decimal place. This can cause an incorrect amount for proceeds/cost basis. As a user, what should I do? No further action needed. 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. Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keyword: Cardano, wrong decimal place, wrong cost basis, wrong proceeds, USDCx, inflated amount, transactions