Key Takeaways
- ✓ Balance Mismatch means Blockpit's on-chain (Synced) balance differs from what it calculated — a gap in your history
- ✓ Blockpit auto-creates "+ Balancing" entries with €0 cost basis when purchase history is missing, inflating taxable gains
- ✓ Bridge transactions not recognized on both chains, and incomplete API imports, are the two most common root causes
- ✓ Faulty merge operations can cause double outgoing transactions — use Ledger Mode to identify and undo incorrect merges
- ✓ Fix the underlying transaction history; do not rely on Blockpit's auto-balancing as it worsens the tax calculation
A number in your Blockpit dashboard that can't be right. A warning you can't dismiss. A "Balance Mismatch" that the tool flags without saying clearly where it comes from. Most of the time this isn't a tool error, but a hint that there's a gap in your transaction history. This article shows what the warning actually means, where it typically comes from, and how to resolve it cleanly.
01 The Problem: Wrong Balance
"Balance Mismatch" is Blockpit's way of saying: What we see on-chain doesn't match what we've calculated.
Blockpit actively displays this discrepancy in the dashboard. That's helpful, but without understanding the cause, the problem remains unsolved.
02 Synced Balance vs. Calculated Balance
Blockpit distinguishes between two values:
Synced Balance
The actual on-chain balance. Blockpit reads this data directly from the blockchain. Example: 0.00056 ETH.
Calculated Balance
The sum of all imported transactions. What Blockpit calculates based on the data. Example: -1.28 ETH.
When these two values differ, transactions are typically missing from your documentation - or manual changes were made that led to inconsistencies.
03 The "+ Balancing" Problem: Blockpit Missing Value Explained
This is where Blockpit differs fundamentally from other crypto tax tools: Blockpit tries to automatically balance missing history.
When Blockpit notices you're selling assets for which no purchase history exists, it automatically creates a "+ Balancing" entry. This looks practical at first - but it's problematic for tax purposes.
How Balancing Works:
"+ Balancing" entries automatically receive a cost basis of 0.00 EUR. During a later sale, the entire sales proceeds are calculated as taxable gain - regardless of what you paid during the original purchase. Complete transaction history determines the correct cost basis.
In the example: 1.278 ETH sale - Blockpit shows +4,278.56 EUR as gain. That's the entire sales proceeds because the cost basis was set to 0 EUR.
04 Common Causes of Balance Mismatches
1. Bridge Transactions Not Recognized
When you bridge ETH from Ethereum to Arbitrum, Blockpit must recognize both sides: the outflow on Ethereum AND the inflow on Arbitrum. If one side is missing, a mismatch occurs.
The example from the dashboard: A bridge transaction wasn't recognized - ETH arrived at the wallet, but Blockpit doesn't see the inflow - negative calculated balance.
2. Incomplete Exchange Imports
API connections to exchanges often only fetch data from the point of connection. Historical transactions - especially older trades - aren't imported retroactively. You bought on Binance in 2021, but connect the API only in 2024. The old trades are missing.
This results in Blockpit seeing sales but no associated purchases. The cost basis is missing.
3. DeFi Protocols Not Fully Recognized
Complex DeFi interactions (Liquidity Mining, Yield Farming, Staking) aren't always interpreted correctly. The inflow of rewards can be missing or incorrectly classified.
4. Manual User Interventions
Sometimes well-intentioned manual corrections cause problems. Transfers are marked as trades, transactions are incorrectly merged, or duplicates arise from double deletion and re-importing.
The result: Double outgoing transactions, missing inflows, or transaction chains that no longer add up.
Quick Reference: Symptom → Cause → Solution
| Symptom in Blockpit | Likely Cause | Solution |
|---|---|---|
| Negative calculated balance | Bridge transaction not recognized | Import both sides of the bridge |
| High positive discrepancy | Incomplete exchange import (API without history) | Import complete CSV export |
| "+ Balancing" with 0 EUR cost basis | Missing purchase history for an asset | Find and import original purchase transaction |
| Double outgoing transactions | Incorrect merge or manual duplicate entry | Identify in Ledger Mode, separate merge |
| "Missing History" tag on asset | Asset without documented acquisition | Import source exchange or source wallet |
05 Merge Problems in Detail
One of the most common causes of balance mismatches are faulty merge operations. Blockpit offers the ability to "merge" related transactions - to connect them. This is useful for transfers between own wallets or complex DeFi transactions. But when it goes wrong, problems arise.
When Merge Makes Sense
A classic example: You transfer ETH from your exchange to your hardware wallet. Blockpit sees two transactions: an outflow at the exchange and an inflow at the wallet. Without merge, this would look like a sale and a separate inflow. With merge, Blockpit understands: This is the same ETH, just on a different wallet.
When Merge Causes Problems
The Most Common Merge Error:
- Existing TX not used: You see a transaction as "unlinked" and know where it belongs. Instead of using the existing automatically imported TX, you enter a new manual TX. Result: Two outgoing transactions for the same operation.
- Temporally mismatched TX merged: Transactions from different days are merged that don't belong together.
The Result: Double Bookings
The most common error: An automatically imported transaction already exists, the user enters the same transaction manually without merging it with the existing one. Blockpit now sees two outgoing transactions for the same operation. The calculated balance tips into negative.
06 Understanding the Recalculation
Blockpit has a Recalculation function. This updates all balance and tax calculations after changes. You can trigger the recalculation manually via a button - and should do so if you want to see results promptly.
When is Recalculation Needed?
Recalculation should occur after the following changes:
- Manual adjustments to transactions (changing classification, correcting values)
- Re-import of integrations (API sync, CSV import)
- New classifications (e.g., Staking Reward instead of Deposit)
- Merge or separation of transactions
What Happens During Recalculation?
Recalculation updates:
Balance Calculation
All asset balances are recalculated based on current transaction data.
Tax Calculation
FIFO/LIFO allocation, holding periods, cost basis, and gains/losses are recalculated.
Important: Recalculate Before Tax Report
Before creating any tax report, a recalculation should be performed. This is the only way to ensure all changes are considered and the report is based on current data.
After recalculation, automatically generated tags like "Missing History" and "+ Balancing" entries disappear - provided you've correctly added the missing transactions. This is a good indicator that crypto accounting is now complete.
07 Diagnosis: The Ledger Mode
Blockpit offers a specific diagnostic tool: the Ledger Mode. It shows the balance history per asset over time.
How to find the cause:
- Go to the affected asset (e.g., ETH)
- Switch to Ledger Mode
- Scroll through the chronological history
- Find the point where the calculation turns negative
- The transaction directly before is usually the cause
09 Fix Blockpit Balance Mismatch: Step by Step
Depending on the cause:
For Bridge Transactions:
Check if both sides of the bridge are imported. Often the incoming side is missing and must be added manually.
For Incomplete Exchange Imports:
Export the complete trading history as CSV directly from the exchange and import it manually. API connections often only provide current data.
For Manual Errors:
Check in Ledger Mode where the calculation tips. Often it helps to separate incorrectly merged transactions or identify duplicate entries.
For "+ Balancing" Entries:
Find the missing transaction and import it. The "Missing History" tags and balancing entries automatically disappear during recalculation.
When Professional Help Makes Sense
For individual mismatches, correction is often manageable. For more complex portfolios with:
- 20+ balance mismatches
- Multiple DeFi protocols across different chains
- Historical data spanning multiple years
- Many "+ Balancing" entries
...correction becomes more complex. TX-Partner specializes in these cases.
10 What Balance Mismatches Mean for Your Tax Return
Balance mismatches are not just a technical problem in Blockpit - they have direct tax consequences. Particularly critical: "+ Balancing" entries with a cost basis of 0 EUR create phantom taxable gains that end up in your tax return without any real profit having been made.
Tax Risks by Error Type
| Error Type | Tax Risk |
|---|---|
| "+ Balancing" cost basis 0 EUR | Phantom gains are taxed. Report looks correct, but the tax burden is too high. |
| Negative calculated balance | Warning visible in report. Tax advisor notices the issue, but it blocks filing. |
| Double entries from merge errors | Double sales or missing inflows distort both profit and holding period calculations. |
| "Missing History" not corrected | All sales of this asset are calculated with 0 EUR cost basis - regardless of the actual purchase price. |
Balance mismatches in Blockpit can in many cases be fixed yourself with some patience: re-import bridge transactions, undo merge errors, check Ledger Mode, recalculate. When the mismatch stays red after several attempts or the complexity goes beyond what the tool can handle, 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.
