A lower crypto price can create a potential tax loss, but it does not automatically create a reliable tax result. Before selling, swapping or spending an asset, review the complete activity trail behind it: the acquisition lot, cost basis, wallet path, fees, calculation method and evidence that supports the classification. CoinLedger can organize this information into a report, but it cannot supply history that was never imported or decide what is appropriate for a particular taxpayer. This guide is a practical record-review workflow for people considering tax-loss harvesting.
Last reviewed: October 9, 2026. CoinLedger features, country settings, tax rules, supported integrations and report terminology can change. This independent educational guide is not tax, accounting, legal or investment advice. Confirm current information in CoinLedger and speak with a qualified professional in your jurisdiction before filing or acting on a tax decision.
1. Unrealized loss versus realized loss
An unrealized loss is a decline in the market value of an asset you still hold. A realized result is generally created when an event disposes of that asset, such as a sale, a swap into another asset, or in some settings a purchase made with crypto. The exact treatment depends on the local rules and facts, but the distinction matters: a portfolio screen can show a large decline without showing a completed taxable event.
CoinLedger can help organize the historical prices and transaction details used in a report. It does not turn a market decline into a filing conclusion. First identify the exact activity being considered, then verify the lot and records that would support the result.
2. Why a price fall is not enough
It is tempting to compare a current price with the price remembered from a purchase and call the difference a loss. Real records are often more complicated. The asset may have arrived through several purchases, transfers, rewards, a swap, a bridge or a previous exchange account. The balance might be correct while its acquisition history is incomplete.
Do not treat a red percentage beside a token as a tax calculation. A reliable review needs dates, amounts, source records, fees, asset identity and the lot-selection approach. If one of those inputs is uncertain, resolve it before treating a report estimate as a decision-ready number.
3. What CoinLedger can show—and what it cannot prove
CoinLedger can consolidate imported activity and calculate reports according to the settings and transaction information available in the account. It can make gaps visible through warnings, missing cost basis, unmatched transfers or unusual entries. That visibility is useful: it tells you where an audit trail needs attention.
However, software cannot know whether a missing withdrawal came from an old exchange account, whether a manual classification reflects the facts, or whether a particular transaction has a special treatment under local law. Treat the output as a structured working record. It becomes more dependable when each material number can be traced back to an original exchange export or on-chain record.
4. Complete history comes before tax-loss harvesting
Importing only the platform where a sale happens can break the cost-basis chain. An inbound deposit might appear as a new asset with unknown basis when it was actually bought years earlier elsewhere. Likewise, omitting an old wallet can make an internal transfer look like income or a disposal.
Build a source inventory before reviewing the final report. Include active and closed exchanges, self-custody wallets, hardware wallets, blockchain networks, card activity, historical CSV exports and DeFi applications where relevant. Record the first and last date covered by each source. A dated inventory is much easier to review than relying on memory after several years of activity.
5. Check every exchange, wallet and blockchain source
For each source, compare the connection or CSV date range with the period in which you used it. Check whether an API connection includes deposits, withdrawals and trades, not merely balances. For wallets, confirm the correct address and network. Similar-looking token tickers on different chains are not automatically the same record.
| Source type | What to verify | Common issue |
|---|---|---|
| Centralized exchange | Trades, deposits, withdrawals, fees and full date range | API or CSV begins after older activity |
| Self-custody wallet | Exact address, blockchain and token contract | Wrong network or a forgotten address |
| DeFi protocol | All transaction legs and wallet interaction | A complex action appears as one simple swap |
| Crypto card or spending account | Asset disposal and merchant activity | Spending history is absent from trade data |
6. Missing cost basis is a question, not a value to guess
A missing-cost-basis warning usually means the report cannot reliably connect an outgoing asset to a known acquisition. The safe response is not to enter a convenient purchase price. Locate the earlier purchase, deposit or transaction that explains the holding. If the history genuinely cannot be reconstructed, seek qualified advice about the available evidence and applicable treatment.
Start with the flagged asset, quantity, date and account. Search for the matching outbound transfer or acquisition in an earlier wallet or exchange. Confirm timestamps, network fees and transaction identifiers before changing a classification. Keep a brief note explaining each correction, including the source file or transaction ID used.
7. Remove duplicate imports before trusting totals
Duplicates can happen when the same platform is connected by API and imported again through CSV, when an address is added twice, or when an export overlaps a previously imported date range. A duplicate purchase can inflate holdings; a duplicate sale can create an incorrect gain or loss. Both can make a report look more complete while making it less accurate.
Compare suspicious repeated entries by timestamp, quantity, trade ID, transaction hash and fee. Do not delete records merely because they look alike; some exchanges legitimately split one order into multiple fills. Preserve the original evidence and document why a duplicate was removed or excluded.
8. Identify transfers between accounts you control
A movement from one wallet or exchange account you control to another is economically different from a sale to a third party. The transaction history must reflect that distinction. If the outbound side is missing, the inbound side may look like a new acquisition. If both sides are misclassified, the report may show an artificial gain, loss or income event.
Match transfers using amount, timing, transaction hash, asset and network. A network fee can mean the sent and received quantities are not identical. Bridges and wrapped assets require extra care because the technical route can involve several transactions. Do not force a match when the evidence does not support one.
9. Fees deserve their own review
Trading, withdrawal, network and protocol fees can be handled differently depending on the transaction and jurisdiction. A fee may appear as a separate asset movement, a reduced received amount or part of a trade record. Review the source statement before assuming that every fee has been captured or classified in the same way.
For a material transaction, compare the exchange confirmation or blockchain explorer with the CoinLedger record: assets sent, assets received, quoted fee, network fee and final timestamp. This is especially useful for swaps and withdrawals, where a small fee difference can explain why a transfer does not match perfectly.
10. FIFO, HIFO, LIFO and Specific Identification
When multiple lots of the same asset exist, a calculation method decides which one is treated as disposed of first. FIFO generally uses the earliest acquired units; LIFO uses the latest; HIFO uses the highest-cost units. Specific Identification requires detailed records that can support matching a particular acquisition lot to a particular disposal. Availability and suitability vary by jurisdiction and reporting context.
| Method | Lot selected first | Review question |
|---|---|---|
| FIFO | Earliest acquired units | Are older purchases and transfers fully imported? |
| LIFO | Most recently acquired units | Does the applicable framework permit this treatment? |
| HIFO | Highest-cost units | Are lot records detailed enough to support the selection? |
| Specific Identification | A documented chosen lot | Can the chosen lot be evidenced and consistently reported? |
11. Review one tax lot from start to finish
Choose one high-value disposal and trace it through the report. Identify the acquisition date, quantity, value, fees, source platform, wallet path and the calculation method that matched it. Then compare those details with original records. One carefully checked example often reveals whether a broader import or setting needs attention.
Repeat the exercise for a cross-exchange transfer, a DeFi transaction and an older lot if they are material to your history. The goal is not to inspect every small transaction manually. It is to test the reliability of the pathways that create the largest reporting impact.
12. Do not change a method only because the total looks better
A different method can produce a different result from the same history. That does not make the lowest estimate automatically appropriate. Method choice can affect prior reporting, remaining lots and future disposals. Rules may limit the methods available or require consistency.
Before changing a setting, save a dated copy of the current report, note the reason for the comparison and obtain professional advice where needed. A defensible record is more valuable than a number optimized for a single screen.
13. A sale is not the only possible disposal
Depending on local rules, converting one cryptoasset into another, using crypto to pay a merchant, funding a card purchase or making certain other transactions may have reporting consequences. The interface may describe these activities differently, but the source data still needs to show what left, what arrived, when it happened and what fees were charged.
Do not assume that “no cash was withdrawn” means nothing needs review. Keep confirmations for swaps, card activity and merchant payments. If an activity is unfamiliar, classify it only after reviewing credible documentation or obtaining professional advice.
14. DeFi swaps, bridges, wrapped assets and liquidity activity
DeFi activity can create several on-chain steps behind one user action. A swap may include approvals, token movements and gas fees. A bridge can burn, lock, mint or release assets across networks. Wrapped assets and liquidity positions may not map neatly to a simple exchange trade. These cases should be reviewed transaction by transaction when material.
Keep the transaction hashes, protocol name, network and a short plain-language description of the purpose of each action. Do not rely only on a token ticker or wallet balance. The technical trail is often the evidence needed to explain the record later.
15. Staking rewards, airdrops and earned tokens
Rewards, airdrops, referral benefits and other received assets may need different treatment from a purchase or an internal transfer. A zero-cost-basis assumption or a generic “income” label can be wrong for a particular situation. Record the source, date, quantity, wallet and any platform statement that explains why the asset was received.
If several small receipts are involved, use a consistent evidence folder rather than relying on a screenshot of an account balance. Clear source records make it easier for a professional to review a classification without reconstructing the event years later.
16. Pre-sale checklist
- Confirm that all relevant exchanges, wallets and historical CSV files are imported.
- Resolve material missing-cost-basis and duplicate warnings.
- Review the exact tax lot, acquisition source and calculation method.
- Verify transfers, bridges and fees surrounding the asset.
- Save original exports and a dated pre-transaction report.
- Consider jurisdiction-specific rules with a qualified tax professional.
This checklist does not instruct you to sell. It helps ensure that, if an action is already being considered for independent reasons, the related records are not being reviewed too late.
17. Economic substance matters
Tax reporting should describe real activity supported by records, not a sequence created only to manufacture a preferred output. A mechanical sell-and-rebuy sequence can carry trading, price, liquidity, platform and legal risks even when the user believes the number on screen is attractive. It can also be difficult to explain if transaction records and intent are unclear.
Focus on accurate reporting, complete evidence and the actual economic exposure you are willing to hold. CoinLedger is useful for organizing records; it is not a substitute for a professional conclusion about a strategy or a transaction’s treatment.
18. Crypto wash-sale discussion: current rules and proposed changes
Online discussions frequently apply stock-market wash-sale concepts to crypto without stating the jurisdiction or date. In the United States, CoinLedger has explained that the traditional wash-sale rule has not historically applied to cryptocurrency in the same way it applies to securities, while proposals and potential legislative changes deserve monitoring. A proposal is not the same as enacted law.
Do not rely on a blog post, social-media claim or an older guide to determine current treatment. Confirm the rule that applies to your country and tax year with official sources and a qualified professional. Users outside the United States may face completely different rules.
19. Post-transaction review
After a completed transaction, return to the record rather than assuming it processed as expected. Compare the final exchange confirmation or on-chain transaction with the CoinLedger entry. Check the asset amount, date, fee, proceeds, transaction type and the lot result. Preserve the evidence while it is easy to retrieve.
If a result changed unexpectedly, investigate the data pathway: an import may have refreshed, a transfer may have been matched differently, or a prior transaction may still be incomplete. Correct the underlying record only when you can explain the change and retain supporting evidence.
20. Build a filing-ready evidence pack
A filing-ready package is more than a PDF total. It should let a future you, accountant or reviewer understand how the total was produced. Keep original exchange exports, wallet addresses, relevant transaction hashes, calculation-method notes, manual-edit notes, final reports and copies of material confirmations together in a protected location.
Frequently asked questions
Does a loss on my dashboard mean I can claim it?
No. A dashboard decline may be unrealized and may not include the correct acquisition lot, fees, transfer history or local rules. Review the underlying records first.
Should I enter a number to clear missing cost basis?
Not without evidence and appropriate advice. Find the original acquisition or transfer record where possible, document the source and seek professional guidance if the history cannot be reconstructed.
Can CoinLedger decide which tax method is right for me?
CoinLedger can apply settings and organize records. Whether a method is available or appropriate depends on your jurisdiction and facts.
What should I keep after generating a report?
Keep the dated report, original exports, transaction confirmations and notes that explain material corrections or classifications.
Official CoinLedger references
Use these clearly labeled official resources to confirm current CoinLedger guidance and terminology:
- CoinLedger Help Center — What is tax-loss harvesting? — an overview of the concept and its reporting context.
- CoinLedger — Cryptocurrency tax-loss harvesting guide — educational discussion of losses and record review.
- CoinLedger — Crypto wash-sale rule guide — current discussion of the US wash-sale topic and legislative context.
- CoinLedger — Crypto accounting guide — explains why complete transaction records matter.
- CoinLedger — DeFi crypto tax guide — background for reviewing DeFi transactions and records.
Good tax records are built before a deadline: complete imports, traceable tax lots, documented corrections and protected source evidence. Use the report as a starting point for review, not as a reason to skip it.