What the documentation confirms for both products
Both providers document importing cryptocurrency histories from multiple sources, but their interfaces and supported integrations differ by exchange and wallet. CoinLedger's onboarding guide lists CSV uploads, blockchain wallet addresses, exchange API connections and manual imports. Koinly's exchange-import guide describes API auto-sync and CSV upload paths. An advertised integration does not prove that every fee, old transaction or unsupported protocol action is imported without manual review.
Import method comparison
| User question | CoinLedger documentation | Koinly documentation |
|---|---|---|
| Can exchange records be imported with CSV? | Yes, for supported sources | Yes, including supported exchange templates |
| Can an exchange API synchronize records? | Yes, for supported integrations | Yes, when that exchange/API is supported |
| Can a public wallet address help? | Documented as an import method | Wallet integrations depend on network support |
| How do I handle gaps? | Missing-basis troubleshooting and manual import paths | Review affected accounts; reimport corrected data |
| Are all connections identical? | No, provider-specific import guides apply | No, provider-specific import guides apply |
These are *documented capabilities*, not direct timing, accuracy or security benchmarks. Before connecting an account, consult the exact integration guide for your exchange.
Why an API connection is not automatically better
An API can reduce repeated exports and update supported transaction history, but it inherits the exchange's data limits. It may not include a wallet you controlled outside that platform or earlier records beyond an endpoint's retention window. CoinLedger says its supported API-key and OAuth import flows use read-only access; a tax tracker should not require trade or withdrawal permissions. Verify the actual permission settings at the exchange and never supply a recovery phrase to a tax application. If a service requests signing or withdrawals as part of a basic tax import, stop and verify the requirement independently.
When a CSV workflow makes more sense
A CSV import offers an inspectable dated file and may work when you prefer not to maintain an API connection. It also creates a maintenance obligation: new transactions require a fresh export, and multiple overlapping files can duplicate records. Koinly's instructions advise using supported templates without unnecessary manual file edits. Keep original exports unchanged so corrections can be traced to the source. A CSV import that completes without an error message can still omit a wallet or account.
Missing cost basis is the real buying test
The useful question is not only whether a button says 'Import'. It is whether the product helps you explain missing cost basis and unmatched transfers. CoinLedger's troubleshooting guidance lists omitted past accounts, unsupported interactions and duplicate data as causes of warning states. Koinly similarly requires you to investigate transactions the source never supplied. Use a small set of your own genuine, known transaction records to assess whether the import and review workflow is understandable before relying on the final report. This article makes no claim that Jepeta performed that test for you.
A neutral decision checklist
- List the exact exchanges, networks, wallets and tax years you need.
- Compare *documented support for those specific sources*, not the total number of advertised integrations.
- Choose the import approach whose ongoing maintenance you can realistically perform.
- Review transfer matching, unsupported contract interactions, duplicate handling and missing-basis explanations.
- Verify account permissions before granting API access.
- Check the report access and pricing in your own region only after the data is reconciled.
An affiliate relationship must never decide which product appears stronger. This comparison has no paid partner CTA and is based solely on cited public documentation.
Scope and limitations
Provider help centers can change, so treat this as a dated documentation comparison, not an endorsement or hands-on performance study. Each product's supported networks, paid report features and integration behavior must be confirmed directly before purchase. For filing obligations and record reconciliation independent of software, see the Jepeta crypto tax records checklist.
Evidence and source-review method
- structured comparison — Primary-source editorial comparison of documented security or import/tax procedures, including a task-oriented checklist and limits. No live wallet test, tax filing, or exchange API account verification is claimed. · evidence · observed Oct 9, 2026
Editorial transparency
This article was prepared with AI-assisted tools and an evidence-oriented source review. Citations and limitations are provided below. Documentation comparison is not a hands-on test; historical content is not automatically certified under the later independent editorial review process. Editorial standards and corrections.
Sources
- CoinLedger: first-time import and review workflow · primary · verified Oct 9, 2026 · published Oct 8, 2025
- CoinLedger: common causes of missing cost basis warnings · primary · verified Oct 9, 2026
- CoinLedger: read-only API and OAuth import permissions · primary · verified Oct 9, 2026 · published Feb 18, 2025
- Koinly: importing exchange data by API or CSV · primary · verified Oct 9, 2026 · published Jun 24, 2026
- Koinly: CSV and Excel import procedure · primary · verified Oct 9, 2026 · published Jun 11, 2026