TL;DR
The purchase pool tracks all buys and sells to calculate gains. Deposits and withdrawals don’t add or remove coins. They’re just transfers. Warnings appear if coins have no cost basis (e.g., missing trades, wrong timestamps, only one side of a transfer, or misclassified futures/margin liquidations). With depot separation, pools are tracked per exchange; without it, one pool covers your whole account. Transaction counts may differ in tax reports because trades can split into short- and long-term parts, or because of import issues causing duplicate entries. Stablecoin-to-stablecoin swaps (e.g. USDC → USDT) are still taxable trades, not tax-free conversions. Always check imports, timestamps, and balances to resolve issues.
Purchase Pool Explanation
The purchase pool is the pile of coins you accumulate in the background. Coins are added from trades, income, gifts, and mining, with their asset value on the day received. Coins are removed through sales, donations, and spends, all of which trigger capital gains calculations.
The order in which coins leave the pool depends on the chosen accounting method (e.g. FIFO, LIFO). Deposits and withdrawals do not affect the pool. They are considered internal movements with no tax impact. If you enter only a deposit, the coin becomes a “ghost coin” without a cost basis. It will appear on the dashboard total but not in the purchase pool, leading to warnings when sold.
With depot separation enabled, pools are built for each exchange or wallet individually. Without it, there is just one pool per coin for the entire account. For example, if you buy 0.1 BTC twice (total pool of 0.2 BTC) and later sell 0.05 BTC, your pool shows 0.15 BTC left. If the buys are missing and only the sale is entered, you will get purchase pool warnings. To identify problems, use validation tools such as How to validate my account?.
Are Stablecoin Swaps (e.g. USDC → USDT) Taxable?
Yes. Swapping one stablecoin for another (for example USDC to USDT) is still classified as a trade/sell in the purchase pool, not a tax-free exchange. Even though both coins are pegged to the same value, the swap removes coins from the pool and triggers a capital gains calculation just like any other trade. Keep this in mind when reviewing your purchase pool or tax report, since these swaps are correctly counted as taxable events, not internal transfers.
Transaction Counts in Tax Reports
The number of transactions on the tax report overview may differ from those inside the capital gains report. On the overview, only real transactions for the tax year are counted (e.g. 4,422). Within the capital gains report, a single real transaction may split into multiple parts depending on how the pool is consumed (e.g. separating into short-term and long-term holdings). This can result in a higher number of listed transactions (e.g. 7,272).
Additionally, the group by day option can create further differences. For license limits, only the number of real transactions is counted.
Duplicate entries: In some cases, a transaction that appears only once in your Transactions list may show up twice in the tax report. This is usually caused by an import issue (for example, a misclassified futures liquidation, see below) rather than a genuine duplicate trade. If you notice a mismatch between the transaction count in your transaction list and in the tax report, check the underlying trades for import errors before assuming a software bug.
Why Do These Warnings Appear?
Missing purchases or incomplete imports
Wrong timestamps (e.g. purchases dated after the sale)
Transfers not marked as “Transfer”
Margin/derivatives misclassified
One-sided tracking (e.g. only importing Exchange B, but not Exchange A where the purchase occurred)
Futures liquidations (e.g. Coin-M futures) imported incorrectly as spot trades, which can distort the spot balance and holdings shown for that coin and trigger purchase pool warnings
How to Fix It
Ensure all trades, deposits, and withdrawals are imported for all your wallets/exchanges.
Use the correct transaction types, especially for internal transfers.
Check timestamps and time zones on your entries.
Audit balances with the tools under Balance by Exchange.
Check for misclassified futures/margin trades. If your exchange API import records a Coin-M futures liquidation as a regular spot trade, it can distort your spot balance and holdings for that coin. In this case, manually correct the affected transaction(s) so the liquidation is booked correctly (e.g. as a margin/derivative entry) instead of a spot trade, and re-check your balances afterward.
Example
You bought 1 BTC on Exchange A, sold it on Exchange B, but only imported data from Exchange B. CoinTracking sees no purchase → assumes a buy at £0 → shows a warning and high gain.
How is Margin Loss Δ (Delta) calculated?
When you record a margin loss in CoinTracking, there are two calculations involved:
Margin Loss: This is the actual value of the coin lost on the day the loss is charged to your account. Example: You lose 0.001 BTC, worth $45 on that day → Margin Loss = –$45.
Margin Delta (Δ): This represents the capital gain or loss from when the coin was originally purchased until the day of the margin loss. Example: The 0.001 BTC was bought two months ago for $30. On the day of loss, it’s worth $45 → Margin Delta = +$15.
The delta can be positive or negative depending on price movements.
In terms of tax law, these deltas fall under private sale transactions. If the holding period is less than one year, personal income tax is due on the delta amount.