// CRYPTO loss tax SPECIALISTS
CountDeFi reviews crypto tax software calculations for investors who have already imported their wallets, exchanges and transaction history but aren't confident the underlying data is complete, or that the reports are accurate. We review the underlying data import, identify what needs attention and recommend the clearest way to fix it.
We operate online and in your timezone.


// who we are

Founder

// crypto tax Strategy experts
We've been reconstructing complex crypto and on-chain transaction histories since 2017, and one thing comes up again and again: the tax software is rarely the real problem. A crypto tax report tool can only work with the transaction history it receives. Leave out a wallet and part of your cost basis may disappear. Import a transfer incorrectly and it can look like a disposal. Miss the acquisition history of an asset and the software has no way of knowing what you originally paid for it. As portfolios become more complex, these problems compound. One exchange becomes several. Assets move into self-custody. Tokens are bridged between chains. DeFi protocols create transactions that need context beyond the raw blockchain data. Manual adjustments made years ago can affect calculations much later.
How does CountDeFi help? We review the data behind your crypto tax calculation, trace material problems back to their source and determine what needs to be corrected before you rely on the final report. If your account is fundamentally sound, we help you get it into shape. If it needs deeper reconstruction, we'll tell you. At CountDeFi we do not bill by the hour. Our pricing scales with transaction volume and complexity, and all plans include software fees, transaction reconciliation, and a complete tax report.
View pricing →
Clients Worldwide
Crypto Tax Reports Completed
Crypto Transactions Reconciled
// services
If you think the work is finished but want an experienced pair of eyes on it before filing, we can review the portfolio and determine whether the underlying data is ready for reporting.
We review existing CoinTracker accounts to identify data problems that may be affecting the accuracy of your Summ tax report.
Missing cost basis can create gains that don't reflect what actually happened. We trace the acquisition history where possible and identify the records needed to correct it.
Moving your own crypto shouldn't automatically become a taxable disposal. We identify transfers, duplicates and other data issues that may be distorting your transaction history.
We review the transaction data in your existing Koinly portfolio, identify material issues and determine what needs to be corrected before you rely on the calculation and file incorrect crypto tax figures.
Whether you're using Blockpit, Coinpanda, Coinledger, Recap, Summ or any other crypto tax tool, we can review the data and results of any platform to ensure accuracy and give you peace of mind.
We check whether the wallets and exchange accounts behind your calculation have been captured properly and identify obvious gaps in the transaction history.
Staking, DeFi, bridging and other on-chain activity doesn't always arrive neatly classified. We review transactions that need additional context and determine how they should be represented in your records.
// EXPERT SKILLS
Most clients who come to us at this point have already done a lot of work. They've signed up for crypto tax software and connected exchanges, added wallets, uploaded CSVs and worked through warnings. The problem is that they have reached the point where they no longer know whether their tax report is right or not.
The reason is often that crypto transaction data imports aren't always as easy as to use as we'd like. An API key with the wrong permissions can leave part of an exchange history out. Opening and resaving an exchange CSV can change date formatting and cause rows to fail. A token that isn't recognised may not import normally. Deleted transactions can reappear as apparent duplicates if they weren't permanently removed. And a file containing 3 rows for the asset sold, asset received and fee paid may correctly become a single trade rather than 3 transactions.
The harder problems sit across data sources. A withdrawal from one wallet needs to meet the corresponding deposit elsewhere. Cost basis needs to follow the asset through that history. Duplicate imports need to be distinguished from legitimate repeated activity. DeFi and derivatives data may need additional context before the resulting transaction history accurately represents what happened.
CountDeFi helps you separate genuine errors from normal software behaviour. We review the history as a connected portfolio rather than a collection of warnings, so the finished filing position is supported by the underlying records, calculations and a methodology you can explain and defend.
// TAILORED PRECISION
Crypto tax software does an enormous amount of work that would otherwise have to be calculated manually. We use it ourselves. The important distinction is between calculation and reconciliation. The calculation engine can calculate gains and losses from the transactions recorded in the portfolio. It cannot recover a wallet you never added, know that an API connection omitted part of your history, or infer the original acquisition of an asset when that transaction isn't present in the data. It also doesn't follow that every unusual-looking import is wrong. An exchange CSV might contain separate rows for the asset sold, the asset bought and the trading fee, while the software correctly represents those rows as one trade. Futures and perpetual activity may be aggregated into daily gain and loss transactions. Internal exchange movements, duplicates and cancelled transactions may deliberately be skipped because they don't belong in the tax calculation.
This is why simply clearing every warning isn't reconciliation. We look at whether the portfolio makes sense as a whole. Are all the relevant wallets and accounts present? Do transfers connect? Is cost basis carried through the history? Are duplicate transactions genuinely duplicates? Are failed imports leaving gaps? Do balances and transaction histories reconcile with the records available from the exchange or blockchain? That is the human work that's often needed to ensure audit-proof crypto tax software reports.
// KOINLY SUPPORT
CountDeFi is Koinly's #1 Global Partner, and we use Koinly's calculation engine as part of our own reporting workflow. We know what the software is designed to do, which makes it easier to recognise when the problem isn't the software at all. If you need a second pair of eyes on your Koinly portfolio or tax report, we are Koinly experts.
A crypto tax software review starts with a free 15-minute consultation to discuss your portolio and recommend the right approach and pricing plan. We work remotely with clients across the US and globally.
// FIVE STAR Global REVIEWS
Can CountDeFi review a Koinly account I've already set up?
Yes. If you've already built your portfolio in Koinly, we can work with what you have rather than automatically starting again. We review the underlying transaction data, identify material issues and determine what needs correcting before you rely on the final tax reports.
Can you help with difficult CSV imports into crypto tax software?
Yes. CSV imports are a common source of problems, particularly when data comes from unsupported exchanges or needs to be reformatted to meet precise import requirements. Small changes to dates, currencies, column structures or transaction formats can cause rows to fail or produce an unusable import. We can review the source data, identify why it isn't importing correctly and reformat transaction data where necessary so your crypto portfolio can be reconciled properly.
Why are some transactions skipped or missing after an import into crypto tax software?
Certain crypto tax software may deliberately exclude duplicates, internal exchange transfers, cancelled transactions or records that will be imported from another source. But usually, not every skipped transaction is an error. For example, several rows in an exchange file may correctly become a single transaction. The important question is whether anything material is actually missing. We review the source records against the imported history rather than assuming every skipped row needs to be restored.
Can you fix missing cost basis and negative balances in crypto tax software? Yes, although the cause needs to be established first. Missing acquisition history, unmatched transfers, incomplete wallet data and failed imports can all leave assets without reliable cost basis or produce balances that don't make sense. We trace the issue back through the transaction history and determine what records or corrections are needed rather than simply overriding the resulting warning.
Can you review reflection tokens and tokens with transfer taxes?
Yes. Tokens with reflection mechanisms, rebasing or other unusual tokenomics can require additional work because changes in the amount you hold may not be represented as ordinary blockchain transactions. That can leave certain crypto tax software showing balances that don't match the wallet. Tokens such as SAFEMOON, AMPL and similar assets may require manual rebalancing or other adjustments so the transaction history reflects what actually happened. This is a good example of where the software isn't necessarily wrong. It simply doesn't have all the information needed to reconstruct the change automatically.
Can you review NFT transactions that are incorrectly imported into crypto tax software?
Yes. NFTs can create several data problems. Some integrations don't import them completely, NFTs may have no readily available market price, and the different legs of an NFT transaction may not automatically match. Depending on the history, reconciliation can involve adding missing NFT records, matching deposits and withdrawals to the corresponding transactions, and establishing appropriate values for transactions such as airdropped NFTs. CountDeFi reviews the activity in context rather than assuming the imported NFT history is complete.
What happens if my crypto tax platform doesn't recognise a token?
New, migrated and less common tokens may occasionally appear as unidentified assets if the software's token database cannot match them correctly. We check what the transaction actually involved and whether the correct asset can be identified. Where necessary, the transaction data can then be corrected or represented appropriately rather than leaving an unidentified token flowing through the rest of the calculation.
I've made lots of manual fixes already. Can you still review my crypto tax account?
Yes. In fact, this is a fairly common point at which professional review becomes useful. Fixing individual warnings without understanding their cause can sometimes create duplicate transactions, break transfers or obscure an earlier data problem.We review the portfolio as it stands, including manual changes, and work backwards where necessary to understand what happened.
Can you review reflection tokens and tokens with transfer taxes?
Yes. Tokens with reflection mechanisms, rebasing or other unusual tokenomics can require additional work because changes in the amount you hold may not be represented as ordinary blockchain transactions. That can leave certain crypto tax software showing balances that don't match the wallet. Tokens such as SAFEMOON, AMPL and similar assets may require manual rebalancing or other adjustments so the transaction history reflects what actually happened. This is a good example of where the software isn't necessarily wrong. It simply doesn't have all the information needed to reconstruct the change automatically.
Can you review reflection tokens and tokens with transfer taxes?
Yes. Tokens with reflection mechanisms, rebasing or other unusual tokenomics can require additional work because changes in the amount you hold may not be represented as ordinary blockchain transactions. That can leave certain crypto tax software showing balances that don't match the wallet. Tokens such as SAFEMOON, AMPL and similar assets may require manual rebalancing or other adjustments so the transaction history reflects what actually happened. This is a good example of where the software isn't necessarily wrong. It simply doesn't have all the information needed to reconstruct the change automatically.