Why Your CoinTracking Transactions Show as White – And How to Fix Them

If you're staring at a sea of white transactions in your CoinTracking portfolio and wondering why the platform can't automatically classify them, you're not alone. Many crypto traders face this frustration, especially when manually cleaning up their transaction history. The good news? Understanding how transaction types work can solve most of these issues.

The Root of the Problem

When you import data from exchanges like Bitcoin.de through API, the platform pulls in raw transaction data. But here's the catch: if you've moved coins between exchanges and don't have complete data from all platforms involved, CoinTracking can't always connect the dots.

White (unclassified) transactions typically appear when the system detects money movement but lacks context. In your case, BTC withdrawals from Bitcoin.de that eventually returned create a tracking gap. The platform sees coins leaving but doesn't automatically know they came back from another exchange.

Understanding Transaction Types

The confusion between "Withdrawal," "Transfer," and "Deposit/Withdrawal" is common, but each serves a specific purpose:

Withdrawal signals that coins left your ecosystem entirely—perhaps sent to a friend or used for purchases. This triggers a taxable event in most jurisdictions.

Transfer indicates movement between your own wallets or exchanges. No taxable event occurs because you still own the assets. This is what you likely need for your Bitcoin.de movements.

Deposit/Withdrawal pairs work when you want to manually record both sides of a transfer on different exchanges.

For accurate tax reporting and portfolio tracking, properly categorizing these transactions is crucial. Many traders discover this when preparing their annual crypto tax documents—suddenly those white transactions become a serious headache. 👉 Track your crypto transfers accurately with automated classification tools to avoid manual cleanup nightmares.

How to Reclassify Your Transactions

Yes, you should change those "Withdrawal" entries to "Transfer" type. Here's the straightforward approach:

First, locate each withdrawal transaction in your CoinTracking history. Change the transaction type from "Withdrawal" to "Transfer-Out" on the Bitcoin.de side. This tells the system that coins left one of your wallets.

Then, you'll need to create corresponding "Transfer-In" entries for when those coins arrived at the other exchanges. Since you don't have API data from those platforms, manual entry is necessary. Record the receiving exchange, amount, and approximate timing.

The key detail: Make sure the amounts match on both sides. If you sent 0.5 BTC from Bitcoin.de, the receiving exchange entry should also show 0.5 BTC (minus any network fees, which you can record separately).

Does It Happen Automatically?

Unfortunately, no. Simply changing a transaction to "Transfer" type doesn't automatically create the matching entry on another exchange. You need to manually record both sides of each transfer.

Think of it like accounting: every transfer needs a debit and a credit entry. CoinTracking won't assume where your coins went—you must explicitly tell the system "these coins left Exchange A and arrived at Exchange B."

This manual process, while tedious, ensures accurate tracking. Automated systems can't guess which of your exchanges received transferred funds, especially when dealing with multiple platforms.

A Practical Workflow

Start by listing all your "Auszahlung" transactions from Bitcoin.de. Next to each one, note where those coins actually went. Then systematically create Transfer-In entries for each receiving platform.

Work chronologically to avoid confusion. Process one transfer at a time: change the Bitcoin.de withdrawal to Transfer-Out, then immediately create the corresponding Transfer-In entry on the receiving exchange.

For returned coins (those that came back to Bitcoin.de), reverse the process. If they show as deposits on Bitcoin.de, change them to Transfer-In and create Transfer-Out entries for wherever they originated.

Double-check your total portfolio balance after reclassification. If done correctly, your overall holdings should remain unchanged—you're just clarifying movement between your own accounts rather than gains or losses.

Preventing Future White Transactions

The best long-term solution is connecting all your exchanges via API where possible. This gives CoinTracking complete visibility into your trading ecosystem and dramatically reduces manual work.

For exchanges without API support, establish a routine: log transfers immediately when they occur. Don't wait until tax season to reconcile months of transactions.

Consider keeping a simple spreadsheet as a backup log for manual transfers. Record the date, amount, sending exchange, and receiving exchange. This makes future data entry much faster and reduces errors.

Getting your transaction history properly classified takes effort upfront but pays dividends when tax season arrives. Clean, accurately categorized data means reliable tax reports and a true picture of your portfolio performance—without the frustration of mysterious white transactions.