1
Make movement readable
A transaction ID can show that movement happened. A label explains what the movement meant in your records.
Bitcoin tax software
Wallet Labeling for Bitcoin Tax Records
A Bitcoin-holder framework for preserving wallet ownership context, source and destination context, purpose notes, and uncertainty notes without exposing wallet secrets or turning labels into tax conclusions.
- Wallet labels
- Ownership context
- Wallet-secret boundary
Author and review
Reviewed under Bitcoin Plaster's tax-scope and wallet-secret boundaries
This support page explains wallet labeling as ownership-context recordkeeping. It does not give tax advice, filing instructions, software recommendations, professional referrals, technical wallet guidance, secret-sharing instructions, or treatment verdicts.
Wallet-labeling boundary
Labels preserve context. They do not decide treatment.
Wallet labels preserve factual context. They do not decide, prove, or change tax treatment, and they do not replace qualified review.
A wallet label is a factual note attached to a wallet, account, address group, or transaction. It preserves context for later review.
Labels help exchange records, wallet history, transaction IDs, fees, and personal notes stay readable together.
Labels do not decide, prove, or change tax treatment, and they never require wallet secrets.
2
Preserve ownership context
Labels help preserve whether a wallet was yours, someone else's, or uncertain without turning that note into a verdict.
3
Keep secrets out
Tax records should use non-secret context such as transaction IDs, public addresses, labels, fees, and uncertainty notes.
Record context
What a label does and why an address or transaction id is not enough
A Bitcoin address can show where coins moved. A transaction ID can prove that movement happened. Neither explains why the movement happened, who controlled each side, or how it should be reviewed later. That is what wallet labels are for.
A wallet label is a factual note attached to a wallet, account, address group, or transaction. It preserves ownership context, source and destination context, purpose, and uncertainty, and it makes exchange records, wallet history, transaction IDs, and personal notes easier to review together.
A transaction ID is a useful anchor. It can show that an on-chain movement happened and tie down time, amount, addresses, and fee, but it does not prove purpose or ownership, show whether a destination was yours, or decide treatment. An address has the same limit: it identifies a destination technically but does not explain what it meant in your records.
Public on-chain data can tell you that something happened. Only your label tells you what it was. A transaction ID plus a label is a readable record; a transaction ID alone is a puzzle you may have to solve again later, from memory, when the memory is gone.
This page is educational only, not tax, legal, or financial advice. Rules differ by jurisdiction and change over time. For the scope of this tax software lane, read the Bitcoin tax disclaimer. For the map, start at the Bitcoin tax software hub.
Six factual label examples
Keep labels plain, factual, and honest about uncertainty.
These examples carry real context without becoming legal or tax classifications. None of them is a treatment conclusion.
-
Withdrawal to cold storage, wallet mine
An exchange withdrawal to your own storage.
-
Transfer between my wallets
Both sides were intended to be wallets you control.
-
Wallet migration, old wallet to new wallet
A move after a device change, seed change, storage change, or wallet replacement.
-
Deposit back to exchange
Coins returning to a platform or exchange account.
-
Payment received or payment sent
An inbound or outbound payment, preserved as a factual note.
-
Uncertain, needs review
Ownership, source, destination, or purpose cannot be confirmed yet.
Self-custody context
Labels make scattered records readable together.
Self-custody can split a Bitcoin record trail across exchange records, wallet history, on-chain transaction IDs, later wallet activity, and personal notes.
The exchange may show coins leaving. The wallet may show coins arriving. The transaction ID may confirm movement. The label tells the record story that ties those pieces together.
- Which wallet was yours.
- Which exchange or source record connects to the wallet movement.
- Why coins moved, while the reason is still fresh.
- Which facts remain uncertain and need review.
Useful label fields
A useful label preserves wallet-level and transaction-level context.
A useful label is factual, not dramatic. It describes what happened, not what you want the treatment to be.
-
Wallet-level context
Preserve a name, ownership context, purpose, approximate active period if known, related exchange or account, old-wallet or new-wallet relationship, and uncertainty note.
-
Transaction-level context
Preserve date and time, transaction ID if on-chain, amount, fee, sending source, receiving destination, label for each side, purpose note, related record, and uncertainty note.
-
Plain factual language
Describe what happened, not what you want the treatment to be. A useful label is factual, not dramatic.
Context preserved
Ownership, source, destination, purpose, and fees should stay in one record story.
Labels do their most important work by preserving factual context across systems. None of these labels decides treatment.
-
Ownership context
Was this wallet mine, someone else's, or uncertain? If the answer is unclear, preserve the uncertainty instead of guessing.
-
Source and destination context
Connect the exchange record, wallet receipt, transaction ID, fee, and related source or destination record so the story remains readable.
-
Purpose and fee context
Write the purpose note close to the event and keep the fee attached to the movement it belongs to.
Movement records
A label adds human context to movement evidence.
A transaction ID and address can identify movement in a technical sense. They do not explain purpose, prove ownership context by themselves, or decide treatment.
A movement between places you control and a movement to someone else are different factual situations. If your records do not show which is which, a later reviewer needs more information. If you are unsure whether a wallet was yours, label the uncertainty rather than resolving it with a guess.
For reconciling exchange and wallet sources, see exchange CSV vs wallet history. For the movement boundary, see wallet transfer vs taxable event.
Old wallets
Old wallets are the classic gap.
A holder may retire an old wallet, replace a device, reorganize storage, or consolidate. Later, that old wallet can become difficult to identify if it was never labeled.
Preserve an old-wallet label and a new-wallet label, the approximate active period, the reason for the move, the transaction IDs and fees involved, source and destination context, and uncertainty notes.
Old wallet is better than nothing, but a label noting what it was used for and how it connects to the new trail is far more useful. It is trivial to write at the moment you retire the wallet and painful to reconstruct years later.
Sensitive information
Recordkeeping and wallet security are separate jobs.
A tax file is exactly the kind of document that gets copied, emailed, uploaded, and shared. That is why it must never contain anything that could move your coins.
-
Never use wallet secrets as evidence
Do not put seed words, private keys, backup phrases, passphrases, PINs, signing secrets, recovery details, extended public keys, account credentials, or other sensitive wallet material into tax records, imports, emails, or review files.
-
Use non-secret record evidence
Use transaction IDs, public addresses involved in the movement, wallet labels, source records, destination records, fee records, purpose notes, and uncertainty notes.
-
Separate recordkeeping from wallet security
A secret does not make a tax record stronger. It only makes the wallet less safe.
Non-secret evidence
Use transaction evidence and labels, not wallet secrets.
Do not put private keys, seed words, backup phrases, passphrases, PINs, signing secrets, recovery details, extended public keys, account credentials, or other sensitive wallet material into tax records, spreadsheets, cloud notes, software imports, emails, or files shared for review.
Do not share wallet secrets with tax software, professionals, or anyone else as labeling evidence. If a record needs to show that a wallet was yours, use non-secret context such as the transaction ID, public address involved in the movement, wallet label, source record, destination record, fee record, purpose note, and uncertainty note.
A secret does not make a tax record stronger. It only makes the wallet less safe.
Software and CSV review
Labels help software review, but they cannot make software know everything.
Software may use supplied labels and records to organize and calculate, and good labels can help connect withdrawals to receipts, old wallets to new, fees to events, and transaction IDs to purpose notes.
Labels especially help with silent CSV problems, where a row shows a withdrawal or receipt but not whether the wallet was yours or which movement it connects to. For loud and silent import problems, see CSV import errors.
Software should not be assumed to validate labels, confirm ownership, read intent, reconcile wallets, or choose treatment. Labels improve context. They do not remove the need to review output.
For what software can and cannot do, see what tax software can and cannot do. For how software limits show up in real record workflows, see Bitcoin tax software limitations.
Limits
Labels preserve context. They cannot create facts.
A label is useful only when it helps preserve or surface facts. It should not cover up missing records or force false confidence.
-
Labels do not decide treatment
They do not decide, prove, change, create, avoid, or replace treatment. They preserve factual context for review.
-
Labels do not recreate missing records
A label cannot recreate a missing source record, transaction ID, acquisition record, fee record, or destination record.
-
Labels do not make uncertainty disappear
If a record is unclear, mark it as uncertain and preserve the review question rather than forcing false confidence.
Qualified review
Some labeling problems are no longer just labeling problems.
This page gives no tax advice or treatment conclusions. It helps preserve facts and mark where review is needed.
-
Ownership cannot be confirmed
Wallet ownership is unclear, an old wallet cannot be identified, or source and destination records do not line up.
-
Records or output cannot be explained
Acquisition records are missing, a movement cannot be connected, or software output does not trace back to source records.
-
Facts exceed recordkeeping
Business, payment, gift, donation, prior-year gaps, formal tax-authority contact, or treatment questions exceed this page.
Professional boundary
When the question exceeds recordkeeping, stop at the boundary.
Qualified review may be appropriate when ownership context is unclear, an old wallet cannot be identified, acquisition records are missing, sources do not line up, output cannot be explained, or treatment questions exceed recordkeeping.
This page does not provide tax advice, legal advice, financial advice, filing instructions, audit-response steps, treatment conclusions, product recommendations, or professional referrals.
For the professional-boundary page, see when to use a tax professional.
Simple habit
Record the label while the context is fresh.
A label written at the time is far more useful than a reconstruction months later.
-
Record what moved
Preserve amount, date, time, transaction ID if on-chain, and fee.
-
Record where it came from and where it went
Preserve source, destination, wallet labels, account labels, and related source records.
-
Record whether the destination was yours
Use yours, someone else's, or uncertain as factual context without turning the label into treatment guidance.
-
Record the purpose note
Use plain factual language such as wallet migration, deposit back to exchange, payment sent, payment received, or uncertain, needs review.
-
Record uncertainty honestly
If ownership, purpose, source, destination, or review context is unclear, preserve the uncertainty instead of inventing certainty.
Recordkeeping framework
Wallet labels belong inside the broader Bitcoin-only recordkeeping framework.
Labels are one part of a record set that also includes acquisition records, wallet movement, transaction IDs, fees, source records, destination records, and uncertainty notes.
For the Bitcoin-only framework, see Bitcoin-only tax recordkeeping. For the full field guide, see Bitcoin tax records.
FAQ
Wallet labeling for Bitcoin tax records FAQ
These answers stay at recordkeeping, ownership-context, wallet-secret boundary, and qualified-review level. They do not give tax advice, filing instructions, treatment conclusions, product recommendations, or technical wallet guidance.
A wallet label is a factual note explaining what a wallet, account, address, or movement meant in your records. It can preserve ownership context, purpose, source and destination context, transaction IDs, fees, and uncertainty. It does not decide treatment.
Short version
Wallet labels preserve context.
They help explain which wallets were yours, why Bitcoin moved, which records connect, what fee belongs to a movement, which transaction ID supports it, and which facts remain uncertain.
Labels do not decide, prove, or change treatment, and they do not replace missing records or qualified review.
Use factual labels, keep wallet secrets out of tax records, mark uncertainty honestly, and treat software output as something to review against source records, not something that magically knows context you never preserved.
For the full tax-scope boundary, see the Bitcoin tax disclaimer.
Where to go next
CSV import errors
Use the import-quality page to understand how labels affect loud failures, silent errors, and review against source records.
What tax software can and cannot do
Review the broader software boundary before expecting tools to understand wallet ownership or intent automatically.
Bitcoin-only tax recordkeeping
Place wallet labeling inside the broader Bitcoin-only recordkeeping framework for holders using self-custody.
Tax disclaimer
Read the scope boundary for Bitcoin Plaster tax software support pages.