Key Takeaways
- ✓ Negative balances mean more of an asset flowed out than in — always a sign of missing transaction history
- ✓ Scam tokens using real tickers (USDC, SOL) are the most common cause of extreme negative values in the millions
- ✓ DeFi aggregators (Cowswap, Jupiter, 1inch) often record only the outflow, leaving the inflow unrecognized
- ✓ Diagnose with Analysis → Checks → Transaction Flow Report; the transaction before going negative is usually the cause
- ✓ CoinTracking treats sales with negative balance as "Short" with 0 EUR cost basis, creating inflated taxable profits
You open CoinTracking and see: ~139 million euros in the negative. That can't be right, and it isn't. But the underlying problem is real and can be solved. This article shows you why CoinTracking displays negative balances and how to fix them.
01 The Problem: Negative Balances
A negative balance in CoinTracking is the tool saying: more of an asset has flowed out than ever flowed in. That's not possible on-chain, and it's always a hint that there's a gap in the transaction history. What looks like a display bug has very real consequences in the tax report.
Why this hurts in the report
CoinTracking interprets every sale without purchase history as "Short" with a cost basis of 0 euros. The entire sales proceeds are recorded as taxable profit, even if no profit actually occurred. What looks like a dashboard issue turns into a distorted tax report.
02 The 5 Most Common Causes
In practice, almost every negative balance traces back to one of five causes. Knowing the pattern saves you from working through every single transaction.
1. Dust attack and scam airdrops
By far the most common cause of absurdly high negative values are scam tokens carrying real tickers. Fraudsters send worthless tokens to your wallet with exactly the ticker of well-known coins, "USDC" or "SOL". CoinTracking only sees the ticker, not the smart contract behind it, and treats the scam token like the real asset. The result in the dashboard: millions of supposed USDC "leaving" your wallet.
2. DeFi aggregator swaps
Swaps through aggregators like Cowswap, Jupiter, or 1inch are often only recognized one-sided by CoinTracking: the outflow is captured, the inflow stays invisible. The tool then sees a sale without a counterpart, the balance tips into negative even though everything ran cleanly on-chain.
3. Manual edits to the history
A frequently underestimated factor: well-intentioned manual corrections. A transaction deleted because it looked "duplicate", or a classification changed because it seemed wrong at first glance. In many cases, that exact transaction was the missing inflow for a later sale, and the balance only goes red afterwards.
4. Bridge transactions across chains
Bridging tokens from one chain to another, ETH from Ethereum to Arbitrum for example, requires both sides in the documentation. CoinTracking has to recognize the outflow on the source chain and the inflow on the destination chain and link them. If one side is missing, you either get a negative balance on the destination or a phantom sale on the source.
5. CEX exchanges with incomplete history
Some exchanges only deliver a limited time range through their API. Anyone who bought on Binance in 2019 and sold in 2024, but connected the API only in 2022, ends up with a sale in the tool without a matching purchase. CoinTracking falls back to cost basis 0, the balance turns negative or at the very least gets distorted in tax terms.
Quick Reference: Identify the Cause by Symptom
| Negative Balance in | Probable Cause | Solution |
|---|---|---|
| USDC/SOL/ETH with values in the millions | Dust attack or scam token with real ticker | Mark contract as scam or rename ticker |
| Token after DEX swap (Jupiter, 1inch) | DeFi aggregator: inflow not recognized | Manually add missing inflow |
| Asset after manually deleting a TX | Manual user correction removed inflow | Restore deleted transaction |
| ETH/token after bridge | Bridge only imported one side | Import destination chain as separate source |
| Altcoin purchased years ago | CEX API doesn't provide complete history | Re-import complete CSV export |
03 Diagnosis: Transaction Flow Report
CoinTracking already ships the right diagnostic tool. Under Analysis → Checks → Transaction Flow Report you get the balance progression per asset over time. That's where you can locate the exact moment the balance first tips into negative.
How to find the cause:
- Go to Analysis → Checks → Transaction Flow Report
- Filter by warnings, this shows you the affected assets and when negative balances occur
- You'll see the timeline of your balances per asset
- The transaction directly before going negative is usually the cause
04 Step-by-Step Diagnosis
Opening the Transaction Flow Report for the first time can feel overwhelming. The following sequence brings structure to the analysis: prioritize first, then measure the gap, then locate the cause.
Step 1: Prioritize via Balance per Exchange
The "Balance per Exchange" view shows on which wallet or exchange position the negative balance sits. Not every position is equally relevant. ETH, BTC, and stablecoins carry real value and need to be clean. For altcoins, relevance depends on the portfolio. Obvious scam tokens and dust can be skipped on the first pass and cleaned up in batch later.
Prioritization by relevance:
- High priority: ETH, BTC, USDC, USDT - relevant assets with real value
- Medium priority: Altcoins depending on portfolio context
- Low priority: Obvious scam tokens, dust
Prioritization depends on the respective activity profile. Someone trading heavily on Solana prioritizes differently than someone focused on Ethereum DeFi.
Step 2: Measure the Gap to On-Chain Reality
The tool view only shows the difference to zero. How big the actual gap to reality is only becomes visible in the block explorer. Etherscan, Arbiscan, Solscan and others show the real on-chain balance. The comparison between CoinTracking and the block explorer reveals the actual extent and at the same time points to the cause.
Step 3: Filter the Transaction Flow
Filter the Transaction Flow Report by the affected asset and the specific wallet or exchange position. That narrows the data down to the relevant inflows and outflows; everything else drops out of view.
Step 4: Find the Tipping Point in Time
In the chronological view, there is exactly one moment where the balance turns negative for the first time. That transaction, or the gap sitting directly before it, is almost always the cause. This is where it pays to look closely.
Typical patterns:
- Sudden jump to negative: Single transaction is missing or wrong
- Gradual decline: Multiple missing inflows over time
- Extreme spike: Scam token with high fake value
Step 5: TX-by-TX Reconciliation Against On-Chain
In simple cases, the gap is obvious: a missing transaction, an obviously wrong label. In more complex cases, like nested DeFi activity or multi-chain transfers, only a transaction-by-transaction reconciliation against on-chain data will do. Tedious, but reliable.
05 Preventive Measures
Once balances are clean, you want to keep them that way. Four routines stop small gaps from growing back into three-digit negative balances.
Check Balances Quarterly
Don't only check balances right before filing. One check per quarter or after major activity phases saves you from heavy forensic work in March, when every other topic is already pressing too.
Combine API and CSV
API connections are convenient, but at many exchanges they only deliver a limited historical window. A full CSV export directly from the exchange fills in the history and closes exactly the gaps where cost basis 0 would later appear.
Caution with Manual Changes
Before making manual changes:
- Understand the change's impact on overall balance
- Don't delete transactions you don't fully understand
- Document what you're changing and why
- After each change, check if new negative balances have appeared
Mark Scam Tokens Right Away
As soon as a scam airdrop shows up, mark the contract as scam or rename the ticker clearly. Doing this on the fly prevents fake values from piling up over months and tipping the whole balance at year-end.
06 What Happens in the Tax Report: "Short (Warning)"
Negative balances don't stay in the dashboard. They migrate into the tax report. CoinTracking marks every sale without a matching purchase history as "Short (Warning)" and sets the cost basis to 0.00 euros. The result: numbers in the report that no longer match reality.
The example above shows what this means in practice: three trades, each calculated with cost basis 0.00 euros, adding up to over 5,000 euros in fictitious taxable profits. Per trade. Scaled across an active portfolio, five-digit numbers add up fast, all of it coming from gaps in the documentation.
07 What Negative Balances Do to the Tax Report
Negative balances are not a pure display problem. They distort the tax report, which later goes to the tax advisor's inbox or straight into the tax return. Every "Short (Warning)" with cost basis 0 EUR means: the numbers the tool produces no longer match reality.
| Risk | Impact |
|---|---|
| Short Warning with cost basis 0 EUR | Sale proceeds are reported as full profit, even when an actual loss occurred |
| Scam token as real position | Worthless tokens appear with a fictitious market value in the report |
| Multiple negative balances in parallel | The tool's allocation logic (FIFO or average cost) breaks, every following trade gets distorted |
| Uncorrected discrepancies before filing | If the tax office asks back, the seamless evidence chain is missing |
Since DAC8 went live in January 2026, crypto platforms report transaction data automatically to the tax authorities. If your tax report doesn't match the platform's filing, the tax office sees the discrepancy immediately. The same documentation is also the foundation for a proof of funds, the moment crypto profits are paid out to a bank account.
08 Fix CoinTracking Negative Balances: Solution Approaches
Which correction is right depends on the cause. The patterns below cover most cases and, when executed cleanly, lead to a balance without red fields.
Correction by cause
For scam tokens
Two clean paths: mark the contract directly as scam, then CoinTracking removes every position with that contract from the calculation. Or rename the ticker clearly, for example to "USDC-SCAM", so the token stays cleanly separated from the real asset.
For DeFi aggregators
Look up the missing inflow in the block explorer and add it manually. CoinTracking doesn't recognize every aggregator automatically; this is where you have to bridge the gap by hand.
For manual errors
Reconstruct the original transaction and re-enter it. Most common case: an inflow was accidentally deleted or a transfer misclassified.
For bridge gaps
Both sides of the bridge must be cleanly imported. Usually the target chain is missing as a separate entry, or the link between the two transactions isn't set.
When Professional Help Makes Sense
For straightforward cases, a few scam tokens or one obviously missing DeFi inflow, correction is done in half an hour. It gets more involved with:
- Dozens of negative balances across multiple assets
- Multiple DeFi protocols with nested activity
- Historical data spanning multiple years
- Multi-chain activity with bridges and wrapped assets
Negative balances in CoinTracking can in many cases be fixed yourself with patience. When correction stalls or the table stays red after several attempts, Robert or Johannes will look at it in the free Data Check and give an honest assessment of what you can solve yourself and where professional rework makes sense.
Co-Founder & Documentation Specialist
Robert Thorn is Co-Founder of TX-Partner. Brings experience from over 500 documented crypto portfolios, from simple Bitcoin trading to six-figure DeFi setups across multiple chains and years. Closes the gap between raw data and clean documentation for tax and banks.
