CoinTracking Missing Transactions

Missing Transactions
in CoinTracking?

Missing counterparts for deposits or withdrawals cause cascading errors throughout your tax report. TX-Partner identifies the missing transactions and corrects your data foundation.

Book Data Check

30 min · Free · No commitment

★★★★★ Trustpilot
500+ Cases of Experience
8Years Professional Experience
Robert Thorn Johannes Anderl

Robert & Johannes · personally review your data

Typical Scenario

A crypto accounting with 4,000+ transactions. Of these, 1,200+ deposits and withdrawals without transfer counterparts. This causes a chain of subsequent errors in the tax report:

1200+
Unpaired Deposits/Withdrawals
Without transfer counterpart in CoinTracking
Checks
Diagnosis Path
Analysis ? Checks ? Missing Transactions
4.000+
Total Transactions
Typical portfolio with DeFi and multi-chain usage
Cascade
Error Cascade
One missing TX can trigger dozens of subsequent errors
Common Errors

The 3 Most Common Causes of "Missing Transactions" in CoinTracking

"Missing Transactions" in CoinTracking: The counterpart of a deposit or withdrawal is missing from the data. TX-Partner encounters these scenarios most frequently.

01_SCAM_SPAM

Scam & Spam Token/NFTs

Unwanted airdrops and scam tokens create deposits without counterparts. CoinTracking cannot assign these and lists them as "missing transactions". The most common cause in CoinTracking.

02_API_IMPORTS

Incomplete API Imports

Exchange APIs don't export everything. Internal transfers, staking rewards, or older transactions are often missing. CSV supplements are necessary for deposits and withdrawals to be fully paired. Exchange history overview →

03_BRIDGES_CROSSCHAIN

Bridges & Cross-Chain Swaps

In cross-chain swaps, Asset A goes out and Asset B comes in – CoinTracking doesn't recognize the connection because different assets are involved. With bridges, the target chain is often missing from the import: For example, if you bridge from Ethereum to Base but only imported the Ethereum address, you have a withdrawal without a deposit on the other side.

Why This Matters

Unpaired Deposits/Withdrawals = Cascading Errors in Tax Report

"Missing Transactions" means: The counterpart of a transaction is missing from the data. Example: Only the withdrawal from Binance exists, but the deposit to your own wallet was never imported. CoinTracking cannot recognize the transfer because one side is missing. These gaps cause cascading errors in the tax report.

1

Crypto Accounting

Crypto accounting in tax tool

2

Tax Calculation

Crypto tax tools & tax advisors

3

Compliance

DAC8, Tax authorities, Tax advisors

When deposits and withdrawals in CoinTracking have no transfer counterpart, cascading errors occur in the tax report – from incorrect acquisition costs to erroneous profit calculations.

TX-Partner Approach

Crypto Accounting, Not Just Symptom Treatment

TX-Partner analyzes the cause of missing transactions – not just the symptom. The crypto accounting is completely processed: missing exchanges, wallets, DeFi interactions.

Crypto accounting is the foundation. If it's correct, everything else follows.

Analyze Missing Transactions

Systematically evaluate Analysis ? Checks ? Missing Transactions.

Identify Missing Sources

Exchanges, wallets, DeFi that have not been imported.

Close Gaps

On-chain data, CSV exports, manual supplements.

Verify Transfers

Finally verify deposits and withdrawals marked as transfers.

Ready?

Missing Transactions definitively add.

30 minutes that make the difference.

Book Data Check 30 min · Free · No commitment

500+ documented cases · 15+ years crypto experience

Frequently Asked Questions

What We Get Asked Most

Via the path Analysis → Checks → Missing Transactions. This check displays all deposits and withdrawals that have no transfer counterpart. These are transactions where CoinTracking doesn't know where an asset came from or where it went.
These are deposits and withdrawals that have no assigned transfer counterpart. CoinTracking doesn't know where an asset came from or where it went. The most common cause is scam and spam tokens, followed by incomplete API imports and cross-chain transfers. These unpaired transactions cause cascading errors in the tax report.