Internal Transfer vs Disposal: The Reconciliation Error That Costs Tax

The most expensive crypto bookkeeping mistake is also the most mechanical: a tool sees value leave one wallet and arrive in another and calls it a sale and a re-purchase. It was neither. This guide is why self-transfers are not disposals, how the error manufactures phantom tax, and how to classify correctly.

TL;DR

• A disposal needs a change of beneficial ownership (a sale/exchange to a counterparty). Own-wallet to own-wallet is not a disposal.
• Naive reconciliation books the outflow as a sale and the inflow as a fresh buy → phantom gain/loss + destroyed cost basis.
• Correctly handled, an internal transfer changes nothing: cost basis and acquisition date travel with the asset.
• Proof = both addresses in the entity's own wallet inventory, legs linked (incl. cross-chain pairs and exchange withdrawals).
• Internal transfer ≠ crypto-to-crypto — the latter changes the asset and is a disposal in many frameworks (jurisdiction-specific).
• This is the classification that ties reconciliation to the tax base.

Why a self-transfer is not a disposal

A disposal — a sale or exchange — requires the asset to change beneficial owner and (typically) proceeds to be received. Moving the same asset between wallets you control has no counterparty, no proceeds, and no change of ownership. There is therefore no gain or loss to recognise; the asset simply sits in a different address. The precise rule is framework- and jurisdiction-specific, but the no-change-of-ownership principle is the near-universal starting point and underpins the French 150 VH bis and the accounting treatment alike.

How the phantom event is manufactured

At the wallet level, a self-transfer is indistinguishable from a sale unless the tool knows both addresses are yours:

1. Value leaves wallet A → tool books a disposal at market price → phantom gain/loss.
2. Value arrives in wallet B → tool books a new acquisition at market price → cost basis reset.

Now you have a taxable event that never happened and a broken cost-basis history that distorts every future disposal of that asset. At volume, across chains and exchanges, this is the single largest source of wrong crypto numbers — and it is purely a classification failure.

What correct handling preserves

Cost-basis and acquisition-date continuity across internal transfers is the requirement. Everything downstream — the disposal gain, the €305 test, the 2086, the GL — depends on it.

Proving "own to own"

Classification is only as good as wallet-inventory completeness:

• Both source and destination addresses must be in the entity's own inventory.
• The two legs must be linked as one movement.
• Cross-chain cases (e.g. a CCTP burn-and-mint) must be paired across chains.
• An exchange withdrawal to your own wallet must be matched to the on-chain receipt.

If a destination wallet is not in the inventory, the tool cannot know the transfer is internal — which is why completeness is the precondition, not an afterthought.

Internal transfer is not crypto-to-crypto

A frequent conflation: "I moved my BTC between my wallets" vs "I swapped BTC for ETH." The first is an internal transfer (same asset, same owner — not a disposal). The second is a crypto-to-crypto exchange that changes the asset held and is a disposal in many frameworks (in France, for occasional investors, crypto-to-fiat/goods/services is the taxable disposal while crypto-to-crypto is generally deferred — see the capital-gains calculation). Different economics, different tax — never merge them in classification.

Practical guidance

1. Default own-to-own movements to "internal transfer", not disposal.
2. Guarantee wallet-inventory completeness — the classifier needs both addresses.
3. Carry cost basis and acquisition date to the destination — never reset on transfer.
4. Pair cross-chain and exchange-withdrawal legs so they are recognised as internal.
5. Keep crypto-to-crypto separate — that is a disposal question, not a transfer.
6. Review reconciliation for phantom disposals before they reach the tax base or GL.

How vendor tools handle internal transfers

Cryptio and Ledgible classify own-to-own movements as internal transfers and carry cost basis across them when both wallets are in the inventory. Confirm the tool defaults self-transfers to non-disposal, preserves basis and acquisition date, and pairs cross-chain/exchange legs — and surfaces any unmatched leg for review rather than silently booking a sale.

How Wag3s helps

Wag3s Ledger recognises own-to-own movements across wallets, chains, and exchange withdrawals as internal transfers, carries cost basis and acquisition date intact, pairs cross-chain legs (including CCTP), and flags unmatched legs for review — so no phantom disposal reaches the tax base or the GL. See the Ledger product page and the Wag3s for accountants page.

Further reading

• Crypto Bank Reconciliation: Subledger to General Ledger
• Cross-Chain Transfer Reconciliation (CCTP & Bridges)
• Crypto Capital Gains Calculation France (150 VH bis)
• The France €305 Exemption
• Multi-Chain Reconciliation
• Crypto Audit Trail and Piste d'Audit Fiable

Sources

• No-change-of-beneficial-ownership principle: a transfer between an entity's own wallets is not a sale/disposal (no counterparty, no proceeds) — characterisation is framework- and jurisdiction-specific
• Cost-basis and acquisition-date continuity across internal transfers (mis-booking as sale+buy creates a phantom gain/loss and resets basis)
• France: for occasional investors crypto-to-fiat/goods/services is the taxable disposal while crypto-to-crypto is generally deferred — article 150 VH bis CGI (jurisdiction-specific contrast with a same-asset internal transfer)