CoinLedger can turn imported exchange, wallet and blockchain activity into tax reports, but a report is only as reliable as the transaction history and cost-basis rules behind it. Before relying on a total gain, loss or tax form, review where each important asset was acquired, how transfers were matched and which report calculation method is active. This guide explains how to review that process without treating the software result as personal tax advice.
Last reviewed: October 6, 2026. CoinLedger features, supported integrations, report settings, country-specific rules and tax forms can change. Confirm current settings in your own account and obtain advice from a qualified tax professional for your jurisdiction. This independent guide is educational and is not tax, legal, investment or accounting advice.
What cost basis and tax lots mean
Cost basis is generally the value assigned to an asset when it was acquired, adjusted where applicable for directly related costs and local tax rules. A tax lot is a specific unit or group of units acquired at a particular time and price. When some of an asset is sold, swapped or otherwise disposed of, a report calculation method determines which lot is treated as leaving first.
For example, a person may have acquired one ETH at three different prices. The later disposal is economically one transaction, but the reported gain or loss can differ depending on which acquisition lot is matched to it. CoinLedger can organize those records, yet it cannot see a purchase that was never imported or correctly identify a transfer whose source is absent from the history.
Why a portfolio value is not a tax result
A portfolio tracker can show current balances and market value. A tax report needs more: acquisition dates, disposal dates, historical values, transaction types, fees, transfers and the calculation method. A wallet can contain one BTC worth a certain amount today while its relevant cost basis came from several purchases across multiple years and platforms.
Do not use a dashboard balance as evidence that all tax data is complete. A balance can look correct while the report contains an unknown-cost-basis warning, duplicate transaction, missing inbound transfer or an incorrectly classified staking, reward or trade event. The review should begin with data completeness, not with the final total.
FIFO, LIFO and HIFO: what changes between methods
| Method | Which lot is matched first? | Why the result can differ |
|---|---|---|
| FIFO | The earliest acquired units | Older purchases may have a substantially different basis from recent ones |
| LIFO | The most recently acquired units | Recent purchase prices can change the gain or loss matched to a disposal |
| HIFO | The highest-cost units | Can produce a different gain calculation when detailed lot records are available |
| Country-specific method | Uses rules selected for the relevant jurisdiction | May use a pooled or adjusted-cost approach instead of the general methods |
There is no universally correct choice for every country or taxpayer. CoinLedger says the calculation methods it offers depend on the country selected in Tax Settings. The setting should follow applicable rules and an informed decision, not a quick comparison of whichever option displays the smallest current gain. A method may also affect how prior and future disposals use the remaining lots.
Why changing a calculation method deserves a review
Changing FIFO, LIFO or HIFO changes the matching logic, not the underlying blockchain or exchange history. A new result may be legitimate in some circumstances, but a switch can also make prior-year reporting inconsistent or cause the same acquisition history to be treated incorrectly. Preserve a copy of each completed report before changing settings, note the reporting year and ask a qualified professional when the consequences are unclear.
Do not choose a method solely because it reduces an estimate in the present moment. The relevant question is whether the records, jurisdiction and filing approach support it. CoinLedger’s own educational material notes that the suitable method can vary by personal circumstances and that detailed records are important for methods relying on specific lot identification.
Transfers are where missing cost basis often begins
A transfer between wallets or exchanges you control is not automatically a new purchase. The original acquisition information generally needs to travel with the asset in the records. If CoinLedger sees an inbound transfer but cannot see the earlier withdrawal or original acquisition, the receiving transaction can appear to have unknown cost basis.
Common causes include an old exchange account that was never imported, a wallet address entered with the wrong network, a CSV file with an incomplete date range, or a transfer sent through an intermediary wallet. The safe response is to locate the missing source record, not to invent a purchase price or label an internal transfer as income merely to remove a warning.
- Identify the asset, amount, date and receiving wallet shown in the flagged transaction.
- Search the sending wallet or exchange for the matching withdrawal and transaction ID.
- Confirm the network, fees and timestamp before manually matching anything.
- Import the missing source, expand the export period or correct the wallet connection if needed.
- Re-run the review and confirm that the cost-basis trail now makes sense.
Per-wallet and per-account records need careful context
Tax rules can distinguish between assets held in different wallets or exchange accounts. CoinLedger’s documentation about US per-wallet cost-basis tracking explains that a sale may need to be matched with lots held in the same account or wallet rather than with a purchase held elsewhere. The practical lesson for every user, even outside the United States, is that the location and route of an asset can matter to record keeping.
Keep labels clear. If two similar wallet addresses have different owners or purposes, do not merge them casually. If a custodial exchange changes its account structure, preserve original exports before altering any connection. Classification decisions should be reviewed with local professional advice rather than copied from an online example designed for another country.
How to review a CoinLedger report before using it
Start with a narrow sample rather than trying to inspect every line at once. Choose the largest purchase, largest disposal, a cross-exchange transfer, a DeFi or NFT interaction if applicable, and an unusual income event. Follow each item from the source exchange or blockchain record into CoinLedger and verify that the dates, amounts, assets, fees and type look reasonable.
| Check | What to compare | Why it matters |
|---|---|---|
| Date range | First and last source transaction against imported history | A missing month can affect many later lots |
| Major trades | Asset, amount, fee and timestamp | Catches parsing or timezone mistakes early |
| Transfers | Withdrawal, deposit and network fee on both sides | Prevents an internal movement from looking like a new acquisition |
| Warnings | Unknown basis, duplicates and unclassified records | These need an explanation before filing |
| Report method | Country setting and selected calculation method | Explains how lots were matched |
A discrepancy does not automatically mean CoinLedger is wrong. It may expose incomplete inputs, a source exchange’s export limitation, a timezone difference or a transaction that needs a more accurate classification. Keep notes about every manual change so a future review can understand why it was made.
Missing tax lots, duplicates and other warnings
A missing tax lot means the calculation cannot find enough reliable acquisition history for a disposal. The appropriate remedy depends on the underlying event. For an internal transfer, add the original source records. For an airdrop, reward, payment or other receipt, determine the correct classification under the applicable rules before changing it. For a genuinely unknown historical acquisition, obtain professional advice rather than assuming a convenient value.
- Duplicate imports: check whether the same exchange was connected by both API and CSV, or whether a wallet was added twice.
- Wrong asset or network: confirm the exact token contract and blockchain; tickers alone can be misleading.
- Split transactions: review whether fees, trade legs or smart-contract actions appear separately.
- Missing outbound transfer: look for a previous account, exchange or wallet that was not included.
- Unexpected income: do not relabel an event simply to remove a warning without understanding its source.
Keep source records separate from working files
Download and retain the original CSV files or reports from every relevant exchange before editing anything in tax software. Give each file a consistent name that identifies the platform, account, date range and download date. Keep an untouched original and use a separate working copy when an accountant, spreadsheet or import process needs changes.
These files can reveal balances, addresses, trading history and personal financial information. Store them on an encrypted device or in a protected service you control. Do not send a full transaction history through an unverified email thread, upload it to an unknown converter or provide a CoinLedger password, recovery phrase or exchange withdrawal credential to someone claiming to “fix” a report.
When a tax professional should review the result
Consider professional help when records involve multiple countries, inherited assets, business activity, mining, staking, lending, margin, derivatives, large missing history, prior filings or uncertain classification. Software can organize data and apply configured logic, but it does not know facts that were never imported and cannot make a legal conclusion for your personal situation.
Prepare a concise package: the final CoinLedger report, original source exports, a list of flagged transactions, the calculation method selected and notes on any manual edits. This is more useful than sending a professional a screenshot of a total without the history that produced it.
CoinLedger cost-basis review checklist
- Import all exchanges, wallets and historical CSV files that contain relevant activity.
- Confirm the tax country and report calculation method before relying on a result.
- Review high-value trades, transfers and unusual activity against original sources.
- Resolve missing cost basis by finding the source record instead of guessing.
- Check for duplicate connections, incorrect networks and incomplete date ranges.
- Save original exports and a dated copy of the final report.
- Document manual classifications and corrections.
- Ask a qualified tax professional about jurisdiction-specific decisions.
Official CoinLedger documentation
Use these official CoinLedger resources to confirm current report settings and understand the terms used in the application:
- Crypto Cost Basis 101 — explains cost basis, transfers and why acquisition history matters.
- Which report calculation methods does CoinLedger support? — lists available FIFO, HIFO, LIFO and country-specific methods.
- How is cost basis calculated? — describes the relationship between cost basis, gains and report settings.
- Per-wallet cost basis tracking — explains CoinLedger’s guidance for the US per-wallet tracking workflow.
A careful review is not about finding the lowest number on a screen. It is about making sure that the report reflects complete records, defensible classifications and the calculation method appropriate for your situation. Preserve the evidence behind the result so that you, an accountant or a future reviewer can understand how it was produced.