Last Updated: 2026-10-26
A tax calculation can be internally consistent and still be based on a missing purchase, a duplicated transfer or the wrong token. Start by checking the record. This worksheet prepares a traceable history for you and your tax professional; it does not select a country's tax treatment, an accounting method or a form for you.
The earlier version of this URL attempted a broad international tax guide. This revision replaces that scope with record reconciliation. Original article history is preserved. No tax return, private wallet or customer account was examined for this guide.
Define the perimeter first
Write down the tax year and jurisdiction you are preparing for, the reporting currency, and every account and wallet that may contribute records. Include closed accounts and earlier acquisition history when it may explain assets sold in the period. An import starting on January 1 cannot reconstruct an older purchase merely because the later sale is visible.
Record the time zone of each export and retain its original file. Use a separate working copy for corrections. For wallet assets, identify the network and token contract or mint, not just a ticker: unrelated assets can share a symbol. For exchange records, retain the account identifier and the provider's transaction or order identifiers without exposing credentials.
The IRS digital-assets recordkeeping guidance, checked on 26 October 2026, lists transaction time, asset type, units, value and basis among the information needed for U.S. calculations. That is a U.S. reference, not a rule for every country. Follow the current authority and qualified advice for your own filing situation.
Use two layers: what happened and how it is treated
Scroll sideways to see every column. Keyboard: focus the table region and use the arrow keys.
| Observed record | Keep as evidence | Question to resolve separately |
|---|---|---|
| Exchange purchase | Filled units, currency paid, fee amount and fee asset, fill ID | Acquisition and cost treatment for the relevant rules |
| Withdrawal and matching receipt | Both endpoints, units, network, transaction ID, fee | Ownership, transfer matching and treatment of the fee |
| Sale or swap | Every asset leg, proceeds, fees and execution time | Disposal classification, units identified and basis |
| Reward or other receipt | Source, units, timestamp and valuation evidence | Nature and timing of income, if applicable |
| Bridge, wrap or liquidity transaction | All visible legs and the protocol operation | Whether economic ownership or the relevant classification changed |
| Failed or reversed operation | Status, fee and reversal records | Which movements actually settled |
Do not force an unknown deposit into “income” or an unmatched withdrawal into “sale” just to clear a warning. Keep an unresolved status with the evidence still needed. A same-owner transfer may also contain a fee paid in an asset; preserve that fee as its own movement rather than treating the entire event as one undifferentiated amount.
A complete synthetic reconciliation
The following invented example concerns a fictional asset T. Its transfer fee is deliberately paid in T; this is a teaching assumption, not a description of any particular blockchain. All times are UTC, the opening T balance is zero and no other movements occur.
Scroll sideways to see every column. Keyboard: focus the table region and use the arrow keys.
| Event | Account A: T | Account B: T | External USD cash | Evidence |
|---|---|---|---|---|
| Buy 100 T for $200, plus a $2 cash fee | +100 | 0 | −202 | One filled purchase and one cash fee |
| Send 80 T from A to B, paying 1 T as a separate network fee | −81 | +80 | 0 | One transfer recorded at both ends, plus the fee |
| Sell 60 T in B for $180 gross, less a $3 cash fee | 0 | −60 | +177 | Sale and cash fee |
| Closing balances | 19 | 20 | −25 net cash flow | 39 T remain across both accounts |
The asset check is 100 acquired − 60 sold − 1 paid as a fee = 39 T remaining. The transfer changes location, not the combined 80 T balance being transferred. The cash check is −202 + 177 = −25 USD. That negative cash flow is not a $25 investment loss: 39 T still exist, and this worksheet has not calculated their value or any tax result.
Three common import errors are visible here. Counting A's withdrawal and B's deposit as two purchases creates units that were never acquired. Omitting the 1 T fee leaves an unexplained one-token difference. Treating $180 gross sale proceeds as the cash receipt overstates cash by $3. Correcting those observations still does not decide the tax treatment of the fees or which units were disposed of.
Track unresolved differences instead of hiding them
Scroll sideways to see every column. Keyboard: focus the table region and use the arrow keys.
| Issue | Evidence to request | Working status |
|---|---|---|
| Sale appears before any acquisition | Earlier exchange export, wallet history, migration record | Missing acquisition; basis unknown |
| Two identical-looking receipts | Transaction IDs, import sources and source row numbers | Possible duplicate; do not delete until matched |
| Wallet balance differs by one token | Fee asset and decimals, failed operations, omitted movements | Quantity discrepancy |
| Fiat value is unavailable | Price source, timestamp, pair and conversion path | Valuation missing; do not substitute zero |
| App labels a bridge as a sale | Protocol transaction and both chain records | Classification pending review |
Each correction should record the old value, new value, reason, source and reviewer. Reimport the same file into a test copy and check whether duplicates return or manual labels disappear. Do not “fix” history by making a balancing entry with no explanation.
Check the report you actually export
Compare opening and closing asset balances with the supporting records. Match sale proceeds and fees to the relevant exports. Review missing-basis warnings, unclassified receipts and large manual adjustments individually. Where a broker statement and your working ledger differ, create a difference log; neither a matching total nor a mismatch alone proves the complete tax result.
Before filing, ask the appropriate professional to resolve the applicable jurisdiction and year, permitted unit-identification method, income/disposal classification, fee treatment and any amended or incomplete records. A software menu offering a method does not establish that you may use it.
The useful handoff is a folder of original exports, the reconciled working ledger, a correction log and an explicit unresolved-items list. “Everything imported” is a claim about ingestion; it is not proof that every operation was interpreted correctly. Use the tax-software comparison checklist to evaluate that difference before buying a report.
Scope: recordkeeping education and synthetic arithmetic, not individualized legal or tax advice. AITR may earn commissions on commercial links elsewhere; the IRS link above is an official reference, not an affiliate link. No personal testing or tax-filing result is claimed.