When imported transactions need a closer look
A successful import does not guarantee a coherent ledger. Overlapping files, inconsistent dates, and incomplete records can create warnings or duplicate activity. Cleanup focuses on the transaction entries themselves and documents the changes made to them.
- Overlapping imports that appear to contain the same activity twice.
- Transfer entries that have been separated or inconsistently labelled.
- Rows with missing fields, conflicting timestamps, or unclear descriptions.
- DeFi, staking, or NFT entries that need more source context before classification.
Record issues in Coinbase, Koinly, and CoinLedger
Name your software and the warning in your inquiry. Elena will confirm the source records, output format, and work to be included when agreeing your scope.
Coinbase: missing acquisition details
Coinbase explains that an external deposit may arrive without its original acquisition date and purchase information. Locate the sending account’s history and the earlier acquisition evidence.
Koinly: unmatched wallet transfers
Koinly checks withdrawals and deposits for potential transfer matches. Compare the source and destination histories, time zones, assets, and recorded fees when a movement remains unmatched.
CoinLedger: overlapping imports
CoinLedger documents duplicate records from repeated wallet imports or overlapping file and API imports. Review import coverage and the original event details before treating an entry as redundant.
The cleanup process
- Inventory the source files. Identify the periods and accounts covered, including overlapping exports.
- Review the entries. Compare potential duplicates, transfers, and incomplete rows against available evidence.
- Document corrections. Record changes and their supporting sources, and make unresolved items visible.
- Prepare the agreed ledger. Organize the transaction history in the format agreed in your scope.
Example: an overlapping import
| Available records | Review action |
|---|---|
| A January export and a full-year export both contain the same trade. | Compare identifiers, dates, amounts, and source coverage before treating the entries as duplicates. |
| The available details do not establish whether two rows describe the same event. | Keep the uncertainty in the review notes and request more evidence. |
The aim is a traceable ledger: corrections should have a reason and a source your reviewer can follow.
See how a correction is documented
The illustrative record package follows an overlapping trade import, a transfer with a recorded fee, and an incoming asset with missing history. Compare the source rows, working ledger, review notes, and open question.
What you receive
- An organized transaction ledger in an agreed format.
- Notes covering transfer matches, duplicate review, and classifications.
- A record of gaps and assumptions that remain unresolved.
Transaction cleanup starts from $200 USD. Volume, sources, years, and complexity determine the written quote. Software subscriptions, tax advice, and return filing are separate.
Crypto transaction cleanup FAQ
Can you help when my crypto tax software shows errors?
We review the available source records behind warnings and inconsistencies. The required files, correction work, and output format are agreed before work starts.
Will every software warning be removed?
The work is based on the available evidence. Some warnings can remain when history is incomplete or more information is needed; these are documented in the open-items list.
Do you decide the tax treatment of every transaction?
The service organizes records and documents classifications and uncertainties for review. Tax decisions, advice, and filing are separate from this scope.
What should I send first?
Start with the years, exchanges and wallets, and the issue you want to resolve. Wait until scope and sharing arrangements are agreed before sending financial records.
Review the records behind a missing cost basis warning
Begin by identifying the asset, affected rows, source accounts, and date ranges imported. The cleanup review checks whether the issue involves missing history, overlapping entries, or activity that needs more context.
- Keep a source inventory so earlier periods and separate accounts are visible.
- Compare candidate duplicates with the original event details before treating a row as redundant.
- Document the evidence for each correction and retain unresolved questions for your CPA or EA.
See the missing crypto cost basis guide for a history checklist and the duplicate transaction guide for an example of overlapping imports. Tax lot selection and return decisions remain separate from the record cleanup scope.