Why does my own-wallet transfer look like income?

The receiving address shows an inbound blockchain transfer. Unless the reviewer knows you control the sending address too, it can look like funds received from another party.

Can I combine several addresses into one CryptoBankStatement?

No. Generate one statement per supported public address, then connect them in your wider evidence pack using transaction hashes and a wallet inventory.

Do the incoming and outgoing amounts always match?

Not always in a simple address-level comparison. Network fees, Bitcoin change outputs, token transfers and transaction structure can affect what each address shows. Use the transaction hash and underlying explorer record rather than matching only a rounded display amount.

Should I delete duplicate-looking transfers?

No. Keep the underlying transactions and explain the relationship. Removing one side can make the evidence incomplete and break the address-level reconciliation.

Can a wallet signature prove both addresses are mine?

Separate valid signatures may demonstrate current control of each supported address. They do not by themselves establish identity, historical control, beneficial ownership or source of funds.

2026-09-30 · 7 min readBy CryptoBankStatement editorial team

How to Explain Transfers Between Your Own Crypto Wallets

The blockchain records an outgoing transfer and an incoming transfer; it does not know that the same person controls both addresses.

Create a £3.99 address statement View the statement methodology

Written by: CryptoBankStatement editorial team

Last reviewed: 2026-09-30

Product documentation review only. No legal, tax, financial, immigration or banking advice.

Primary sources

CRYPTO10400: Cryptoasset record keeping — HM Revenue & Customs
Information you need to give to UK cryptoasset service providers — HM Revenue & Customs

To explain a transfer between your own wallets, list both public addresses, identify the shared transaction hash, state why you moved the assets, and provide address-level records covering both sides of the transfer. The same transaction should appear as money out from one address and money in to the other, subject to network fees and the way the blockchain represents the transaction.

A public blockchain does not label two addresses as belonging to the same person. CryptoBankStatement also should not infer common ownership merely because funds moved between them. Make the ownership claim separately and support it with wallet records, exchange withdrawal data, or address-control evidence if the reviewer requests it.

Build a wallet inventory first

Give each address a plain label, such as Ledger BTC savings or MetaMask operating wallet
Record the blockchain, asset and address exactly
Note the dates during which you controlled or used the address
Keep wallet-provider or exchange records that support your description
Do not include private keys or seed phrases in the evidence pack

Match the two sides by transaction hash

The transaction hash is the stable blockchain identifier connecting the sending and receiving records. Put it in your chronology with the date, asset, sending address, receiving address, amount and fee. Explain the purpose, such as moving from a software wallet to a hardware wallet.

Example internal-transfer note

“On 12 August 2026 I moved 0.40 ETH from address 0xSender, my MetaMask address, to 0xReceiver, my Ledger-controlled address. Both address statements reference transaction 0xHash. The movement was a custody change and not income from a third party. Supporting address-control evidence is attached.”

Bitcoin needs extra care

Many Bitcoin wallets derive multiple receiving and change addresses. One address statement may represent only part of the wallet. Do not call one public address the complete wallet unless you have established that scope independently.

How CryptoBankStatement can help

Generate a separate PDF and CSV for each supported address and reporting period. Each download costs £3.99 after a free preview. Place the statements together with a wallet inventory that maps the matching transaction hashes and labels the addresses you say you control.

Important limitations

CryptoBankStatement is not a bank, accountant, solicitor, tax adviser, immigration adviser or financial adviser. This content is not legal, tax, financial, immigration or banking advice. The receiving institution decides what documents it accepts. A transaction match shows movement between addresses. It does not, by itself, prove that the same person legally or beneficially owned both addresses. Bitcoin address reuse and change outputs can also make address-level reporting incomplete for an HD wallet.

Continue reading

Frequently asked questions

Why does my own-wallet transfer look like income?: The receiving address shows an inbound blockchain transfer. Unless the reviewer knows you control the sending address too, it can look like funds received from another party.
Can I combine several addresses into one CryptoBankStatement?: No. Generate one statement per supported public address, then connect them in your wider evidence pack using transaction hashes and a wallet inventory.
Do the incoming and outgoing amounts always match?: Not always in a simple address-level comparison. Network fees, Bitcoin change outputs, token transfers and transaction structure can affect what each address shows. Use the transaction hash and underlying explorer record rather than matching only a rounded display amount.
Should I delete duplicate-looking transfers?: No. Keep the underlying transactions and explain the relationship. Removing one side can make the evidence incomplete and break the address-level reconciliation.
Can a wallet signature prove both addresses are mine?: Separate valid signatures may demonstrate current control of each supported address. They do not by themselves establish identity, historical control, beneficial ownership or source of funds.

Create a £3.99 address statement