Transfer matching
Matching Crypto Transfers Across Wallets and Exchanges
A practical guide to matching internal crypto transfers, preserving acquisition history, accounting for fees, and investigating unmatched wallet movement.
Use this guide as a planning and preparation framework. Adapt each item to the organization, period, materiality, and professional requirements involved.
Federal tax sources last checked August 12, 2026. State, local, and non-U.S. rules are outside this guide and require separate review.
Prove the transfer perimeter
- Inventory every material sending and receiving wallet, exchange, broker, custodian, bridge, and related legal entity for the period.
- Document who owned or controlled each source at the time of movement; matching amounts and timestamps alone do not establish common ownership.
- Retain original exports and transaction hashes before normalizing addresses, symbols, timestamps, or classifications.
- Include closed accounts, archived addresses, subaccounts, and operational wallets that ended the period with no balance.
Match the principal movement
- Compare asset identity, network, contract address, quantity, timestamp, transaction hash, sending address, and receiving address.
- Allow for documented settlement windows, exchange processing delays, batched withdrawals, internal platform transfers, and time-zone differences.
- Keep bridge deposits and receipts visible as a connected sequence rather than assuming every cross-chain pair is economically identical.
- Use confidence levels or exception statuses when the available evidence supports a probable match but not a conclusive one.
Account for transfer fees separately
The IRS treats the same-owner principal transfer as nontaxable, while digital assets used or withheld to pay the transfer service are disposed of and require separate gain-or-loss analysis.
- Reconcile the gross amount sent, net amount received, and the units or other asset used to pay network, broker, or transfer-service fees.
- Do not force the sending and receiving quantities to match by deleting or burying the fee difference.
- Identify whether the fee was paid from the transferred asset, a separate digital asset, or fiat and retain the related evidence.
- Do not describe a fee incurred merely to move assets between the taxpayer’s own wallets as a digital asset transaction cost under the IRS definition; coordinate its final reporting treatment with the engaged tax professional.
Carry the accounting and basis history forward
- Preserve the acquisition date, cost information, lot identity, entity ownership, and relevant restrictions for the units received.
- Avoid recording both sides as income and expense, or as a disposal and new acquisition, merely because two platforms classified them differently.
- Keep intercompany or third-party transfers separate from movement between accounts owned by the same taxpayer or entity.
- Reconcile the matched movement to wallet, subledger, tax-lot, and general-ledger balances as required by the engagement.
Investigate and report exceptions
- Investigate unmatched deposits, withdrawals, missing transaction hashes, unsupported ownership, wrong-network activity, and asset-identity conflicts.
- Separate pending research from confirmed errors and assign an owner, evidence request, and next action to each material exception.
- Prepare a transfer schedule another accountant, tax professional, auditor, investor, or controller can follow without relying on undocumented software labels.
- Carry unresolved movements into the open-items register rather than silently clearing them to a suspense or plug account.
Primary references
This guide is general information, not accounting, tax, legal, or investment advice. Conclusions and requirements depend on the facts and a properly scoped professional engagement.