If crypto tax lot selection changed your cost basis, preserve both versions before editing anything and identify which disposal, account, wallet, asset, and jurisdiction the setting affects. A lower or higher displayed basis is a calculation result—not proof that the new selection is legally valid or that tax is already due.

Key Takeaways

Lot selection links a disposal to particular acquisition records; changing that link can change basis, holding period, and gain or loss.

A platform preference, broker report, tax-software import rule, and filed tax position are separate records.

Identification rules differ sharply by jurisdiction; U.S. specific identification and U.K. pooling are not interchangeable.

Keep immutable exports and reconcile all affected disposals before accepting a recalculation.

Protect the account and exports using the online security guide, especially if the method changed without your action. Do not upload complete tax files, wallet addresses, or identity documents to an unknown “support” contact.

Why has crypto tax lot selection changed your cost basis?

A tax lot is a record of acquired units with attributes such as asset, quantity, acquisition time, acquisition cost, fees, wallet or account, and holding period. When part of a fungible asset is sold, exchanged, spent, or otherwise disposed of, a calculation must determine which acquisition units are matched to that disposal under the applicable rules.

Different eligible matches can carry different acquisition costs and dates. Selecting higher-cost units can produce a higher basis and a smaller arithmetic gain for that disposal; selecting lower-cost units can do the opposite. The holding period can also change. This arithmetic explanation does not establish which method a reader may use.

Record or setting	What it may control	What it does not establish by itself
Exchange lot preference	Broker's assignment for eligible transactions	Treatment in every wallet or country
Tax-software method	Imported calculation and report display	Timely identification or broker confirmation
Broker tax form	Information reported under that regime	Completeness of off-platform records
Wallet/account mapping	Which units are available to match	Beneficial ownership or legal tax result
Filed return and workpapers	Position actually reported	Whether an app's later display is correct

The IRS explains that adequate identification can require the particular units to be identified by the relevant time and supported by records; for broker-held units, the taxpayer may need to specify units to the broker and retain substantiation.［2］ HMRC uses a different framework for many fungible tokens, including same-day matching, a 30-day rule, and a section 104 pool.［3］ A universal “best lot method” therefore does not exist.

What might have changed besides the visible method?

Do not assume a single dropdown caused the entire difference. Recalculate only after comparing the data boundary.

Possible change	Typical effect
Lot method changed	Different acquisitions match the same disposal
Wallet or account scope changed	Available acquisition pool expands or contracts
Transfer link changed	Software treats an internal transfer as a disposal or a new acquisition
Fee treatment changed	Acquisition cost or disposal proceeds change
Missing acquisition imported	Basis becomes unknown, zero, or estimated
Duplicate transaction removed	Quantity and remaining lots change
Token identity remapped	Wrapped, bridged, migrated, or similarly named assets merge or separate
Time zone changed	Same-day ordering or tax-year boundary may change

This article focuses on lot selection and the immediate data needed to verify it. If trades, deposits, transfers, or fees are missing, first use the broader crypto record reconciliation guide. If the surprise comes from the execution price rather than the lot match, use the unexpected fill-price guide.

How should you reconcile a changed crypto cost basis?

1. Preserve the before-and-after state

Export the transaction ledger, lot report, gain/loss report, settings, account list, wallet list, and any broker tax form before making another change. Save the export time, software version if shown, tax year, jurisdiction profile, base currency, time zone, and selected method.

Then export the recalculated version separately. Do not overwrite the original or rely only on screenshots. A comparison needs stable inputs, not a dashboard that recalculates every time it opens.

2. Identify the exact change event

Check audit history, notifications, import logs, and recent account activity. Determine whether you changed a global preference, a tax-year method, an individual disposal, a wallet assignment, or an integration. If the change was unauthorized, secure the account before continuing and ask the provider to preserve its audit records.

Write down when the change became effective, not only when you noticed it. A current setting may apply prospectively, retroactively, or only during report generation depending on the service.

3. Confirm the governing jurisdiction and tax year

Use the law and official guidance that apply to the taxpayer, transaction, and year. Do not select a method because it produces the smallest displayed gain. Rules can govern whether identification is available, when it must occur, what communication is required, how wallets or accounts are treated, and what records substantiate the choice.

For U.S. federal examples, IRS guidance describes timely identification and adequate records, while Form 1099-DA instructions provide broker-reporting context.［1］［2］ For U.K. individual capital-gains examples, HMRC describes pooling and matching rules that can override a user's preferred FIFO-like display.［3］ Obtain qualified advice for your facts.

4. Freeze the transaction universe

Choose a fixed start and end time and inventory every relevant acquisition, disposal, transfer, fee, reward, fork, bridge, wrap, unwrap, and migration within scope. Record the original source and unique transaction identifier. Normalize time zones for comparison without deleting the source timestamp.

Do not merge assets merely because they share a ticker. Confirm contract, network, issuer, wrapper, and migration treatment. A mistaken asset merge can change lot quantities before the selection method is even applied.

5. Reconcile transfers before disposals

Internal transfers should connect an outbound record to its inbound counterpart under the rules and software model being used. If a transfer is misclassified as a sale, the system can create a fictitious disposal and a new lot, changing every later match.

Match quantity, asset identity, timestamps, transaction or transfer identifiers, and fees. Keep the original wallet/account locations because some regimes or reporting systems use them as part of the identification boundary.

6. Compare one disposal line by line

Select the earliest affected disposal and compare the old and new calculation. Record disposed quantity, proceeds, fees, matched acquisition IDs, acquisition dates, unit costs, total basis, holding period, and remaining quantity in each lot.

The arithmetic should reconcile: the matched quantities must equal the disposed quantity, and no acquisition unit should be consumed twice. If the first changed disposal is wrong, later differences may simply be downstream consequences.

7. Test whether the identification was timely and supported

For a jurisdiction that permits specific identification, locate the contemporaneous instruction, broker confirmation, standing order, or internal record required by the applicable rule. The IRS FAQ states that identification must be made by specified deadlines and adequate records retained; broker-custodied units may require communication to the broker.［2］ A later tax-software click cannot automatically reconstruct an earlier timely instruction.

If no qualifying identification exists, determine the applicable default with a tax professional. Do not backdate an instruction, alter an exchange confirmation, or fabricate a screenshot.

8. Measure the full impact before correcting reports

Once the first changed disposal is understood, recalculate every later disposal that draws from the affected lots. Compare basis, proceeds, holding period, gain/loss, remaining units, and any broker-reported values. Check whether the change crosses a tax year or affects an already filed return.

Do not edit a filed position solely to match software. Reconcile the source records, official information returns, workpapers, and applicable correction procedure with a qualified adviser.

How do U.S. identification and U.K. pooling differ?

The comparison below is deliberately high level and cannot select a rule for a reader.

Question	U.S. federal guidance example	U.K. individual CGT guidance example
Can particular units matter?	Yes, if identification and records satisfy the applicable requirements［2］	Fungible tokens commonly enter statutory matching and a section 104 pool［3］
Does timing matter?	Identification deadlines and records matter［2］	Same-day and following 30-day acquisitions receive specific matching treatment［3］
Does account/wallet context matter?	Current guidance includes account- and wallet-related rules and transition issues［1］［2］	Each token type generally has its own pooled allowable cost for the beneficial owner［3］
Can software preference decide the law?	No	No

The IRS Form 1099-DA instructions concern broker reporting and include basis-related rules and transition details; a form can still require reconciliation with the taxpayer's complete records.［1］ HMRC states that pooled allowable cost changes as units are acquired and disposed of, while same-day and 30-day matching apply before the residual pool.［3］

What evidence should you retain?

Keep raw exchange exports, wallet histories, transaction IDs, acquisition confirmations, disposal confirmations, fee records, transfer matches, lot-selection instructions, broker acknowledgments, tax forms, software exports, manual adjustments, and adviser notes. Record provenance for every manual edit.

Use read-only copies for analysis and a separate working copy for corrections. Hashing or version control can help you detect accidental file changes, but it does not prove tax correctness. Protect backups because transaction histories and wallet addresses can reveal sensitive financial patterns.

Summary

Preserve original and recalculated reports before touching the settings again.
Confirm the jurisdiction, year, account/wallet scope, and exact change event.
Reconcile asset identity, transfers, fees, and the first affected disposal before reviewing later rows.
Require timely, supportable identification where the applicable rule demands it.
Treat platform output as evidence to reconcile, not as personalized tax advice.

Frequently Asked Questions

Does a higher cost basis always reduce my tax?

It can reduce the arithmetic gain on one disposal, but tax treatment also depends on eligibility, holding period, other transactions, losses, jurisdiction, and reporting rules. Do not choose a method solely for that outcome.

Can I change tax lots after a trade is complete?

That depends on the applicable law, timing rule, custodian process, and records. A software interface may allow recalculation even when a legally effective identification can no longer be made.

Is FIFO the default for every crypto holder?

No. Defaults and matching rules vary. U.S. rules and U.K. pooling illustrate materially different approaches, and other jurisdictions may use other systems.［2］［3］

Why did changing one disposal affect later years?

Using different acquisition units changes which lots remain. Later disposals may therefore inherit different costs and acquisition dates, creating a chain of recalculations.

Does Form 1099-DA contain my complete crypto basis?

Not necessarily. Its contents depend on reporting rules, transaction dates, broker information, and available basis data. Reconcile it with your complete records and current IRS instructions.［1］

What if my exchange and tax software show different lots?

Compare their account scope, transaction imports, fee treatment, time zone, asset mapping, method settings, and identification records. Neither display should be accepted without reconciliation.

Can a VPN restore or correct cost basis records?

No. A VPN cannot change transaction history, broker reporting, tax-software calculations, legal identification, or an authority's rules.

When should I ask a tax professional?

Seek qualified advice when records are incomplete, the method changed after disposal, multiple jurisdictions apply, broker reporting conflicts with your ledger, or an already filed return may be affected.

Disclaimer: This article provides general information, not tax, legal, accounting, or financial advice. Tax rules depend on jurisdiction, taxpayer, asset, account, transaction date, records, and current law.

Sources:

Internal Revenue Service — Instructions for Form 1099-DA — https://www.irs.gov/instructions/i1099da
Internal Revenue Service — Frequently asked questions on digital asset transactions — https://www.irs.gov/individuals/international-taxpayers/frequently-asked-questions-on-digital-asset-transactions
HM Revenue & Customs — Cryptoassets for individuals: Capital Gains Tax: pooling — https://www.gov.uk/hmrc-internal-manuals/cryptoassets-manual/crypto22200

Sources checked 12 September 2026.

Related articles:

Crypto Tax Lot Selection Changed Your Cost Basis