SUMM, formerly known as CryptoTaxCalculator, is a popular crypto tax platform for importing cryptocurrency transactions, calculating gains and losses, tracking portfolios, and preparing tax reports.
But importing your wallets and exchanges into SUMM is only the beginning.
A crypto tax report is only as accurate as the transaction data behind it. If a wallet is missing, a transfer is incorrectly categorized, a purchase is not recorded, or a transaction has the wrong value, the resulting gains, losses, cost basis, and tax reports can also be affected.
That's why crypto tax reconciliation is an important step before relying on your SUMM tax reports.
In this guide, we'll walk through how to reconcile a crypto account in SUMM, including importing data, reviewing warnings, identifying missing transactions, checking wallet balances, resolving categorization issues, reviewing cost basis, and validating the final tax reports.
Import all wallets, exchanges, and blockchain addresses used during the relevant period.
Don't assume that a successful import means the account is fully reconciled.
Review SUMM's warnings and review sections for missing or potentially incorrect data.
Pay particular attention to transfers, negative balances, missing purchases, pricing issues, and incorrect transaction classifications.
Use blockchain explorers to investigate transactions that cannot be understood from the imported data alone.
Make sure your cost basis follows the crypto when assets move between wallets and exchanges.
Review portfolio balances and individual asset holdings as an additional reconciliation check.
Review gains, losses, income, and other reports before generating the final tax report.
Complex DeFi, staking, liquidity pools, NFTs, bridges, and high-volume trading may require additional manual review.
Tax treatment varies by jurisdiction, so the final classification should be reviewed against the applicable tax rules.
What Is Crypto Reconciliation?
Step 1: List All Your Crypto Accounts
Step 2: Import Your Wallets and Exchanges Into SUMM
Step 3: Review Your Transactions
Step 4: Resolve Warnings and Categorization Issues
Step 5: Investigate Transfers
Step 6: Check for Missing Transactions
Step 7: Review Negative Balances
Step 8: Check Pricing and Missing Cost Basis
Step 9: Review DeFi and Complex Transactions
Step 10: Check Portfolio and Wallet Balances
Step 11: Review Gains, Losses, and Tax Reports
Step 12: Perform a Final Reconciliation Check
Common SUMM Reconciliation Problems
SUMM Reconciliation Checklist
When Should You Hire a Crypto Reconciliation Professional?
Frequently Asked Questions
Crypto reconciliation is the process of comparing your cryptocurrency transaction records against your wallets, exchanges, blockchain activity, and other available records to make sure the data in your crypto tax software is complete and accurate.
It involves much more than importing transactions.
A proper reconciliation generally involves checking:
Completeness of transaction history
Wallet and exchange balances
Transfers between accounts
Transaction classifications
Missing purchases
Missing sales
Duplicate transactions
Cost basis
Asset prices
Fees
Negative balances
DeFi transactions
Staking and rewards
Liquidity pool activity
NFT transactions
Other unusual blockchain activity
The objective is to create a transaction history that explains where your crypto came from, where it went, what happened to it, and what tax treatment may apply.
The first step is to identify every account and wallet you've used, including the accounts that you no longer use.
Make sure you import all the blockchain networks you've used on the wallet, such as Ethereum, Hyperliquid, Polygon, Base, etc.
One of the most common reconciliation problems we see is that someone imports their current accounts but forgets an old exchange or wallet.
For example:
2019: Buy BTC on Exchange A
↓
2020: Transfer BTC to Wallet B
↓
2023: Transfer BTC to Exchange C
↓
2025: Sell BTC
If Exchange A or Wallet B is missing from SUMM, the software may not have the acquisition history needed to establish the correct cost basis.
Therefore, historical accounts can be just as important as your current accounts.
Once you've identified your accounts, import them into SUMM.
Depending on the integration, you may be able to use:
API connections
CSV files
Public blockchain wallet addresses
Other supported integration methods
For exchange APIs, use a read-only API key whenever possible. A read-only key allows transaction data to be retrieved without giving the connected application trading or withdrawal permissions.
For CSV imports, download the relevant transaction history from the exchange and upload it into SUMM.
For blockchain wallets, provide the relevant public wallet address.
SUMM allows you to assign account names or nicknames, use descriptive names.
Instead of:
0x8f72...A91C
use something like:
Ledger – ETH Wallet A91C
or:
MetaMask – DeFi A91C
This makes transaction review considerably easier.
Once your accounts have been imported, go to the transaction section.
At this point, don't assume everything is correct simply because transactions are appearing.
The first question should be:
Does this transaction history represent everything I actually did with crypto?
Use the available filters to review transactions by:
Account
Wallet
Exchange
Transaction type
Import source
Warnings
Other available classifications
SUMM can automatically categorize many common transactions, but blockchain transactions can be considerably more complicated than traditional exchange trades.
For example, a single blockchain transaction can involve:
Multiple token movements
Smart-contract interactions
Gas fees
LP tokens
Wrapped assets
Staking contracts
DEX swaps
Rewards
Protocol fees
That's why automated categorization should be treated as a starting point for reconciliation rather than a substitute for reviewing the underlying activity.
One of the most useful places to start is the Warnings or review area.
Look for issues involving:
Categorization
Pricing
Missing purchases
Negative balances
Other transaction warnings
The goal isn't simply to make the warning disappear.
The goal is to understand why the warning exists.
For example, if SUMM shows an outgoing transaction but doesn't know what happened, you may need to determine whether it was:
A transfer
A sale
A payment
A donation
A DeFi interaction
A transaction to another wallet
Another type of disposal
Correct classification can have a direct impact on the tax calculation.
Transfers are one of the most important parts of crypto reconciliation.
Consider this example:
Binance → Ledger
You withdraw 2 ETH from Binance and receive approximately 2 ETH in your Ledger wallet.
If both accounts belong to you, this is generally a movement of your own cryptocurrency rather than a sale.
However, SUMM needs to understand the relationship between the outgoing and incoming transactions.
If the transfer isn't correctly identified, you could potentially end up with:
A missing acquisition
An unexplained deposit
An incorrect disposal
A broken cost-basis trail
An incorrect wallet balance
Suppose:
Wallet A: -1 BTC
Wallet B: +1 BTC
If both wallets belong to you, the transactions should generally be connected as an internal transfer rather than treated as a sale and a purchase.
The exact tax treatment of transfers can depend on jurisdiction and circumstances, but maintaining the complete transaction trail is important regardless.
A missing transaction is one of the biggest problems in crypto reconciliation.
Suppose SUMM shows:
Wallet A → 10 ETH
But you cannot find the corresponding 10 ETH entering Wallet A.
There are several possibilities:
The transaction really is missing.
The sending wallet hasn't been imported.
The transaction is in another account but hasn't been matched.
The exchange import is incomplete.
The transaction was incorrectly categorized.
The blockchain integration didn't capture the activity correctly.
This is why a missing transaction shouldn't immediately be treated as income or another taxable event.
Start with the blockchain transaction and determine:
Where did the crypto come from?
Then:
Where did it go?
Then:
Do I own or control both addresses?
And finally:
Is the corresponding transaction present in SUMM?
This approach helps reconstruct the complete flow of funds.
Negative balances are another important reconciliation indicator.
Imagine SUMM shows:
ETH balance before transaction: 2 ETH
ETH sold: 3 ETH
Something is missing.
Possible explanations include:
Missing purchase
Missing transfer
Incorrect transaction date
Incorrect transaction classification
Duplicate transaction
Missing wallet
Incomplete exchange history
A negative balance should therefore be investigated rather than simply ignored.
A missing acquisition doesn't only affect the wallet balance.
It can also affect:
Cost basis
Capital gains
Capital losses
Holding period
Tax reporting
Portfolio value
A small missing transaction early in your history can sometimes affect transactions many years later.
Crypto tax calculations require reliable acquisition and disposal information.
For each taxable disposal, you generally need to establish:
Proceeds - Cost Basis = Gain or Loss
But establishing cost basis can become difficult when cryptocurrency has moved through multiple wallets and exchanges.
For example:
Coinbase → Ledger → MetaMask → Uniswap → USDC
The cost basis of the original asset needs to remain connected to the asset as it moves through the ecosystem.
A wallet transfer doesn't magically create a new cost basis.
This is why complete historical data is so important.
You may encounter:
Missing purchase history
Missing acquisition price
Incorrect purchase price
Missing transfer
Incorrect transfer classification
Duplicate purchase
Missing historical exchange
Incorrect transaction date
Unsupported token pricing
These issues should be resolved before relying on the final gains and losses.
DeFi can make crypto reconciliation significantly more complicated.
A single interaction with a protocol may involve multiple assets and smart-contract interactions.
Examples include:
Token swaps
Staking
Yield farming
Lending
Borrowing
Liquidity pools
LP tokens
Wrapped assets
Bridges
Protocol rewards
Governance tokens
NFT activity
For example, you might deposit:
1.2 ETH + 2,500 USDC
into a liquidity pool and receive an LP token representing your position.
Later, you withdraw:
0.8 ETH + 2,900 USDC
plus fees or other rewards.
The tax treatment of liquidity pool transactions can vary by jurisdiction and remains an area where the precise facts and applicable rules matter.
From a reconciliation perspective, however, you still need to understand the entire transaction sequence.
Don't simply look at the final withdrawal.
You need to understand:
What was deposited → what was received → what happened while it was in the protocol → what was ultimately withdrawn.
Once you've reviewed individual transactions, step back and look at your overall portfolio.
This is one of the best sanity checks for a reconciled account.
Suppose you know your actual holdings are approximately:
| Asset | Actual Balance | SUMM Balance |
| BTC | 1.25 BTC | 1.25 BTC |
| ETH | 8.50 ETH | 7.90 ETH |
| USDC | 20,000 USDC | 20,000 USDC |
| SOL | 500 SOL | 620 SOL |
The differences in ETH and SOL should be investigated.
Look at each asset individually and trace the transactions that produced the balance.
This can reveal problems that aren't obvious when looking only at the total portfolio value.
Once you've resolved the transaction-level issues, review the reports.
Don't immediately download the report and send it to your accountant.
First, perform a reasonableness check.
Look at:
Total gains
Total losses
Income
Individual asset gains
Largest gains
Largest losses
Unrealized gains/losses, where applicable
Transaction counts
Portfolio value
Cost basis
If you see an unexpectedly large gain or loss, investigate the transactions behind it.
Suppose you normally trade small amounts of SOL but the report suddenly shows a $250,000 gain.
That doesn't necessarily mean the report is wrong.
But it is certainly worth investigating.
Click into the underlying transactions and determine:
What asset was sold?
When was it acquired?
What was the cost basis?
What were the proceeds?
Was the transaction correctly classified?
Was there a missing transfer?
This is the difference between generating a report and reconciling an account.
Your tax calculation may depend on the applicable inventory or cost-basis method in your jurisdiction.
Common methods discussed in crypto tax reporting include:
FIFO - First In, First Out
LIFO - Last In, First Out
HIFO - Highest In, First Out
Specific Identification
The rules governing which methods are permitted, how they must be applied, and whether wallet-level tracking is required vary by jurisdiction and tax year.
For U.S. taxpayers in particular, the rules around digital-asset cost-basis allocation and wallet/account-level tracking have evolved, so you should use the rules applicable to the relevant tax year rather than relying on an older workflow.
The important reconciliation point is this:
Your cost-basis method cannot produce reliable results if the underlying transaction history is incomplete.
A perfectly configured tax calculation can still be wrong if the data going into it is wrong.
For U.S. taxpayers, Form 1099-DA adds another important reconciliation consideration.
Broker reporting requirements for digital assets mean taxpayers may receive transaction information from exchanges or brokers.
However, an exchange's records may not contain the complete history of your crypto activity.
For example, you could have:
Wallet → Exchange → Sale
The exchange may know about the sale, but the acquisition cost basis may originate from an earlier purchase on another exchange or wallet.
This is why taxpayers should not assume that the number appearing on a 1099-DA represents their complete crypto tax picture.
Your reconciliation process should consider:
Exchange-reported transactions + other wallets + historical acquisitions + transfers + cost basis + taxable activity
rather than looking at the exchange form in isolation.
Here are some of the issues we commonly encounter when working with crypto tax software.
A user imports their current wallet but forgets an old wallet containing the original acquisition.
Result: Missing cost basis or unexplained deposits.
Some exchanges have limitations around API data or historical CSV exports.
Result: The account appears connected, but older transactions are missing.
Crypto leaves one account and arrives in another, but the two transactions aren't correctly linked.
Result: Potentially incorrect income, gains, losses, or balances.
The system records a disposal before it has recorded the corresponding acquisition.
Result: Missing transaction or incorrect transaction classification needs investigation.
A DeFi transaction or blockchain transaction is automatically categorized incorrectly.
Result: Incorrect tax treatment.
A token doesn't have reliable pricing information.
Result: Incorrect or incomplete transaction value.
The same activity is imported through multiple sources.
For example:
API + CSV + blockchain wallet import
may result in overlapping data depending on the integration.
Result: Inflated transaction counts or incorrect balances.
A single smart-contract interaction can involve several movements of assets.
Result: The transaction may require manual investigation and categorization.
A portfolio with 2000 transactions is very different from an account with 90,000 transactions.
For high-volume accounts, manually reviewing every transaction in the same way is inefficient.
A better approach is to use a structured workflow:
Confirm that all:
Exchanges
Wallets
Blockchains
Historical accounts
CSV files
APIs
have been imported.
Review:
Warnings
Negative balances
Missing prices
Missing purchases
Categorization issues
Investigate unusual or high-value transactions using:
Blockchain explorers
Exchange records
Transaction hashes
Wallet addresses
Supporting documentation
Compare:
Actual holdings ↔ SUMM holdings
for each major wallet, exchange and asset.
Review:
Gains
Losses
Income
Cost basis
Transaction counts
Major taxable events
Unusual results
Perform a final review before delivering or filing the tax report.
This workflow becomes particularly valuable for accounts involving multiple years and tens of thousands of transactions.
Before considering your SUMM account ready for tax reporting, use this checklist.
All exchanges have been identified.
All wallets have been identified.
Old and inactive accounts have been included.
All relevant blockchain networks have been included.
Historical transaction data has been imported.
API connections are working.
CSV files cover the required period.
There are no obvious gaps in transaction history.
Duplicate imports have been checked.
Warnings have been reviewed.
Categorization issues have been investigated.
Transfers have been matched where appropriate.
Negative balances have been investigated.
Missing purchases have been investigated.
Missing prices have been reviewed.
Duplicate transactions have been checked.
Acquisition history is complete.
Cost basis is available for disposed assets.
Transfers preserve the appropriate acquisition history.
The applicable inventory/cost-basis method has been selected.
DEX swaps have been reviewed.
Staking has been reviewed.
Liquidity pool activity has been reviewed.
LP tokens have been reviewed.
Bridges and wrapped assets have been investigated where relevant.
DeFi rewards have been reviewed.
Gains and losses have been reviewed.
Income has been reviewed.
Major gains have been investigated.
Major losses have been investigated.
Portfolio balances have been checked.
Final reports have been reviewed before filing.
Not every crypto account requires professional reconciliation.
If you've made a few purchases and sales on one exchange, the process may be relatively straightforward.
However, professional reconciliation can become valuable when you have:
Multiple exchanges
Multiple wallets
Several years of activity
Thousands of transactions
DeFi activity
NFT transactions
Staking
Liquidity pools
Bridges
Margin or derivatives trading
Missing historical records
Closed exchanges
Negative balances
Significant unexplained gains or losses
The challenge isn't necessarily the number of transactions alone.
A portfolio with 5,000 simple trades can sometimes be easier to reconcile than a portfolio with 1,000 highly complex DeFi transactions.
The real issue is the complexity and completeness of the transaction history.
SUMM can automate a significant amount of crypto transaction processing, including importing data and automatically categorizing many transactions.
But no software can completely eliminate the need to understand the underlying data.
Think of the process as:
Import → Review → Investigate → Reconcile → Validate → Report
rather than:
Import → Download Tax Report
That distinction is particularly important when you're dealing with complex crypto activity.
Yes. SUMM is the new name of the platform formerly known as CryptoTaxCalculator.
Start by importing all relevant exchanges, wallets and blockchain addresses. Then review the transactions, warnings, categorization issues, negative balances, missing purchases and pricing issues. Investigate unusual transactions using exchange records and blockchain explorers, then compare the resulting balances and tax reports against your actual activity.
Incorrect balances can result from missing transactions, incomplete imports, duplicate transactions, incorrect transfer classifications, incorrect dates, or other data issues.
The best approach is to investigate the individual asset balance and trace the transactions contributing to it.
A negative balance generally indicates that the transactions currently recorded do not explain how you acquired enough of the asset before it was disposed of.
Possible causes include missing purchases, missing transfers, incomplete imports, duplicates or incorrect classifications.
A transfer between wallets you own is generally not a disposal simply because the cryptocurrency moved from one wallet to another. However, the tax treatment of particular transactions can vary by jurisdiction and circumstances.
Even when a transfer isn't taxable, it should still be recorded correctly because the transfer helps preserve the asset's history and cost basis.
Cost basis is needed to calculate the gain or loss when cryptocurrency is disposed of.
If you bought BTC for $20,000 and later disposed of it for $50,000, the cost basis is a critical part of determining the resulting gain.
If the original purchase isn't present in your crypto tax software, the resulting tax calculation may be incomplete or incorrect.
SUMM can automate importing and categorizing many transactions, and its warnings and review features can help identify issues.
However, automated software should not be treated as a guarantee that every transaction has been correctly reconciled.
Complex transactions may require manual investigation.
Start by reviewing the underlying blockchain transaction.
Identify:
What assets were sent.
What assets were received.
Which smart contract was involved.
Whether fees were paid.
Whether the transaction involved a swap, staking, lending, liquidity pool, bridge, reward or another activity.
Whether the resulting classification is appropriate for your tax jurisdiction.
There is no single check that guarantees accuracy.
A proper review should include:
Complete transaction history + correct classifications + matched transfers + accurate cost basis + reasonable balances + reviewed gains/losses + applicable tax rules.
The final report should make sense when compared with your actual crypto activity.
At Bitcounts, we help clients reconcile cryptocurrency transactions across exchanges, wallets and blockchains before preparing their tax and accounting reports.
Our reconciliation work can include:
Exchange and wallet data imports
Transaction completeness checks
Transfer matching
Missing transaction investigation
Cost-basis reconstruction
Negative balance resolution
DeFi transaction review
Staking and reward classification
NFT and token transaction review
Blockchain investigation
Gain and loss review
Tax-report quality control
We've worked with both relatively simple portfolios and large crypto accounts containing tens of thousands of transactions across multiple years, exchanges and wallets.
The objective isn't simply to make the software produce a report.
The objective is to make the transaction history explainable, complete, and supportable.
If your SUMM account contains complex activity or you're unsure whether your data is fully reconciled, Bitcounts can help review and reconcile the account before you rely on the final tax report.
This article is for general informational purposes only and does not constitute tax, accounting, legal, or financial advice. Cryptocurrency tax rules differ between countries and can change over time. The appropriate treatment of a transaction depends on the taxpayer's jurisdiction and individual circumstances. Consult a qualified tax professional before making tax or reporting decisions.