Crypto Tax Recordkeeping: Cost Basis, Exchanges, Fees and Ledgers

A tax ledger is an evidence chain for events, not merely a price table

Crypto tax records should reconstruct who exchanged which asset, when, in what quantity, for what consideration, with which fees and at what value in the tax currency. Japan’s National Tax Agency provides current guidance and worksheets, but treatment changes with business context, entity, NFTs, staking, foreign tax and legislative year. This page designs records and is not tax advice.

Confirm current authority material, residence, tax year and selected valuation method with a qualified professional. Expanded service-provider reporting under CARF does not eliminate the taxpayer’s own records. Third-party reporting can differ from a personal ledger, so reconcile account IDs, tax residence and asset mappings.

Confirm the formal classification under the applicable law.

Preserve CSV, statements and on-chain evidence before transformation

Download exchange CSVs, annual statements, deposit and withdrawal histories, fee reports and reward reports by period. Name files with provider, account code, period, download date, timezone and version. Store originals read-only. Perform transformations in separate files and retain import-script and mapping versions. Export regularly because a discontinued service may not remain accessible.

For self-custody, preserve public address, network, contract, transaction hash, block time, from/to, token movements and gas. Explorer labels and fiat conversions can change, so keep raw transaction data separate from enrichment. Screenshots are not machine-readable enough; CSV alone does not prove wallet ownership or purpose.

• Raw file: Preserve provider output with hash and download date.
• Mapping: Map provider symbols to network, contract and tax asset ID.
• Ownership: Classify self, shared, business and third-party wallets.
• Evidence URL: Save explorer and official terms with access date.

Fix contract, timezone and rate source instead of relying on a ticker

The same ticker can exist on several networks, and migrations leave old and new contracts. Include network, contract, decimals and issuer in the tax asset ID. Do not automatically merge wrapped tokens or liquid-staking receipts with the underlying. A bridge event may be a transfer, exchange or mint/burn depending on evidence and local law.

Align exchange timestamps, block time, bank statements and the local tax-day boundary. Mixing UTC with JST can move a year-end event. Choose and document an accepted conversion source and whether it uses transaction price, bid, ask, mid or daily close.

Version the method, opening balance, fees and rounding

Japan’s NTA materials cover total-average and moving-average methods for individuals and related forms. Preserve the selected or filed method, opening units and value, acquisitions, disposals and ending units for each asset. Do not switch method opportunistically during a year; check formal change procedures. Corporate and other-jurisdiction rules differ.

In a fictional moving-average example, two units at USD 20,000 average are followed by a purchase of 0.5 at USD 30,000 plus a USD 10 fee included in basis. New average = (40,000 + 15,000 + 10) ÷ 2.5 = USD 22,004. Whether the fee belongs in basis and the recognition time require tax confirmation.

Do not collapse staking, DeFi, bridges and NFTs into one net row

A staking reward may raise questions about accrual, claim or when it becomes freely disposable. Liquid-staking receipts, interest-bearing tokens, LP tokens and bridged tokens can be transfers, exchanges, deposits or income under different rules. Do not classify by protocol name alone.

One transaction can contain approval, swap, liquidity deposit, reward claim and gas. Decompose token transfers, internal calls and event logs. Determine how gas is allocated, how failed-transaction fees are treated and whether paying a fee in the native token is a disposal. First establish the technical meaning through the DeFi contract and approval guide.

Always reconcile automated tax-software output to primary evidence.

Close with quantity reconciliation, an unknown queue and change history

For each asset, calculate opening units plus acquisitions, rewards and inbound transfers less disposals, fees and outbound transfers equals ending units. Reconcile against statements and wallets. Classify differences as rounding, missing exports, internal transfers, delisting, rebase, airdrop, fork, spam token or migration. Do not erase the difference with an unexplained manual adjustment.

Place unresolved events in an unknown queue with an owner and due date rather than assigning zero value or “transfer.” Lock the return-supporting ledger version, method, software, rates and professional adjustments. Later corrections become a new version. Apply local retention, privacy, succession and business-record rules with encrypted, distributed backups.

1. 01Freeze all sources

   Preserve CSVs, statements, addresses, transactions and bank evidence.

2. 02Normalize events

   Use one schema for asset ID, time, quantity, rate, fee and purpose.

3. 03Reconcile quantities

   Roll every asset from opening to ending balance.

4. 04Resolve unknowns

   Assign an evidence owner and due date instead of guessing.

5. 05Lock the reviewed version

   Save method, rounding, adjustment and approver.

The Financial Templates Hub can structure the event ledger, source list, open questions and review sign-off without storing private keys, seeds or complete identity files. Check current NTA material and a qualified tax professional for an actual filing.