Koinly and CoinTracker both publish a help article about gains coming out too high. The cause is almost always the data, not the math — a transfer between your own wallets recorded as a sale, a purchase the tool never saw, an import that ran twice. Ledgerline reads your export and shows you which rows are doing it.
Koinly or CoinTracker transaction history, CSV
Two of these are things a spreadsheet cannot do. The other two are included so the list is complete.
| Finding | What it means | Counts toward the total |
|---|---|---|
| Split transfer proven | A withdrawal and a deposit share a transaction hash. One movement the export recorded as both a disposal and an acquisition. | Yes |
| Missing inbound proven | A wallet held an asset, then the balance goes below zero. Something arrived that was never imported. | Yes |
| No purchase on file | A sale with no cost basis, so the entire proceeds became gain. | Yes |
| Imported twice | The same movement appears on two rows — usually an API sync and a CSV import of the same account. | Yes |
| Opening gap context | The first sale of an asset with no earlier history in the file. Normal on a partial import. Counted, never in the headline. | No |
| Timing guess context | Two rows that look related but share no hash. Shown so you can check them. Never treated as proven. | No |
It flags rows in an export. The corrected number is between you and your preparer.
A finding describes what two rows are. It does not instruct you on how to treat a transaction for tax.
If a purchase is missing, the fix is finding it — not typing in a number you cannot document.
The file is parsed in your browser. There is no upload to delete.
Or scan free first and pay only if it finds something.
Hand reconciliation starts around $335.
Almost always missing data. When a tool cannot see where a coin came from, it assumes you paid nothing, and the whole sale price becomes gain. Move coins between your own wallets and it may record a sale on one side and a purchase on the other, which invents a disposal that never happened.
No. You keep using whatever you already have. Ledgerline reads its export and points at the rows distorting the total, so you can fix them at the source.
The file is read by code running in your browser. It is not uploaded. Close the tab and nothing remains.
No. Ledgerline is not a tax preparer and does not give tax advice. It reports inconsistencies in a file. What is reportable is your decision and your preparer's.
Then your export is clean and you owe us nothing. The free scan tells you either way.