Crypto Tax Accountant Canada: Start With Reconciled Data

What the taxpayer is responsible for

The taxpayer needs to identify every exchange, wallet, address, chain, protocol, NFT marketplace, staking account, fiat account, and relevant year. They also need to explain facts a data export cannot show, such as gifts, lost access, hacks, personal payments, business purpose, loans, and ownership of addresses.

Delegating calculation does not make incomplete source data disappear. The strongest engagement begins with an honest account inventory and preserves raw files before platforms close, APIs change, or transaction histories become unavailable.

What a Canadian tax professional does

The Canadian tax professional applies the Income Tax Act and CRA guidance to the client's facts, resolves legal and classification questions, decides what goes on the return, and prepares and files it. They also advise on other return items, provincial or territorial tax, entities, GST/HST, foreign-property reporting, disclosures, and audit responses where applicable.

What Count On Sheep reconciles

Count On Sheep gathers and normalizes digital-asset data, matches same-owner transfers, identifies missing legs and duplicates, values events in Canadian dollars, builds ACB roll-forwards, calculates candidate gains and income, and documents exceptions. The output is designed for review by the client's Canadian tax professional.

When one person or service may perform more than one role

Some Canadian accounting firms have in-house crypto data specialists and may perform reconciliation and tax preparation together. Others ask the client to bring a complete report. What matters is that each job has an owner, the filing professional can inspect the assumptions, and no one mistakes an automated export for a resolved tax position.

Multiple exchanges and wallets

Each platform may use different symbols, time zones, fee formats, and transaction labels. Wallet transfers can be imported as false disposals on one side and zero-cost acquisitions on the other. A complete account map and transfer matching are the starting controls.

DeFi, staking, NFTs, bridges, and airdrops

On-chain activity can contain multi-step swaps, receipt tokens, LP positions, rewards, gas, bridge messages, NFT minting, collateral, and liquidations. CRA has not published universal treatment for every DeFi event, so the ledger needs both decoded mechanics and a visible exception for professional judgment.

Missing platforms or closed accounts

Closed exchanges, inaccessible emails, missing API history, and unsupported wallets can break adjusted cost base across several years. Reconstruction may use bank records, blockchain evidence, counterparties, prior reports, screenshots, and reasonable documented estimates. Missing basis should never be silently set to zero.

High transaction volume

Volume creates a control problem rather than merely a row-count problem. Thousands of automated trades can be clean, while 50 DeFi events can be difficult. The work depends on data quality, transfer density, token ambiguity, and the number of exceptions that need human review.

Prior-year inconsistencies

Opening ACB comes from prior activity. A current-year report can be mathematically precise and still wrong when earlier acquisitions, losses, or business treatment were inconsistent. Reconciliation should identify the first reliable opening point and expose corrections needed for the Canadian tax professional.

Business-versus-capital uncertainty

CRA considers frequency, holding periods, market knowledge, time spent, and financing. Classification changes the amount included in income and the accounting method. The evidence framework is explained in our guide to capital gains vs business income for crypto.

Complete exchange exports

Download trades, orders where useful, deposits, withdrawals, fiat movements, fees, rewards, statements, and account-profile details. Preserve native CSV, PDF, and JSON files. A tax summary without the raw export prevents source tracing.

Wallet addresses and transaction histories

List owned addresses by chain and label their purpose and ownership period. Include transaction hashes and exports for swaps, transfers, approvals, claims, mints, burns, bridges, and protocol interactions.

Fiat deposits and withdrawals

Bank and payment records help connect exchanges, trace principal, and identify missing accounts. They are reconciliation evidence, not a substitute for the transaction-level gain or income calculation.

Protocol, NFT, and staking records

Supply contract addresses, pool or vault IDs, NFT token IDs, staking statements, reward credits, position snapshots, loan and collateral data, liquidations, bridge messages, and the protocol terms relevant to ownership or redemption.

Prior-year ACB and tax reports

Provide prior ledgers, ACB pools, return schedules, loss carryover information, reconciliation reports, and any notices of assessment. Opening units and cost should tie to the previous closing position.

Notes on gifts, lost access, hacks, and business activity

Explain events the blockchain cannot classify. Include recipient relationships, recovery attempts, police or platform reports, loan agreements, business purpose, time spent, financing, and changes in strategy.

1. Scope every account, wallet, chain, and year

Build an inventory before importing. Confirm entities, spouses or affiliated persons where relevant, ownership dates, closed accounts, fiat routes, and the first year needed to support opening ACB.

2. Ingest and normalize raw data

Preserve raw files, then standardize timestamps, time zones, token contracts, symbols, transaction types, and fee fields. Every normalized row should retain a source pointer.

3. Match same-owner transfers

Connect withdrawal and deposit legs by asset, amount, time, address, hash, and fee. Same-owner wallet movements are not dispositions by themselves, so accurate matching prevents false gains and false basis.

4. Remove duplicates and find missing legs

The same on-chain event may appear in a wallet feed, exchange export, and protocol integration. Remove duplicates without losing lineage. Investigate unmatched flows as possible missing platforms, swaps, gifts, payments, or unsupported acquisitions.

5. Value transactions in CAD

Assign Canadian-dollar values with timestamp, time zone, source, quote path, and method. Flag thin liquidity, stale prices, stablecoin deviations, and estimated values for review.

6. Calculate ACB, gains, losses, and income candidates

Build pooled ACB by identical asset, allocate cost to dispositions, subtract eligible selling outlays, and create separate reward, mining, staking, compensation, and business schedules. The transparent calculation method is covered in our guide to calculate Canadian crypto gains using adjusted cost base.

7. Flag classification and source-data exceptions

List missing basis, disputed wallet ownership, capital-versus-business questions, superficial losses, DeFi property-right issues, and valuation assumptions. Quantify the transactions and amounts affected.

8. Deliver workpapers to the client's Canadian tax professional

Provide the ledger, ACB, gains and loss summary, income schedules, source archive, valuation notes, and exception log. The tax professional resolves positions and uses accepted figures in the return.

Reconciled transaction ledger

Each row should identify date and time, source, asset, units, event, counterparty or address, Canadian-dollar value, fee, classification tag, and transaction hash or account record. Transfers need matched counterparts.

ACB roll-forward by asset

Show opening units and pooled cost, acquisitions and fees, dispositions and allocated ACB, adjustments, and closing units and cost. A closing balance should tie to owned wallets and the next year's opening schedule.

Proceeds, gains, and losses

Summaries should reconcile to transaction detail and separate capital candidates from business results. Include selling outlays and superficial-loss adjustments rather than reporting only gross proceeds.

Mining, staking, and other income schedules

List units, credit or receipt time, CAD value, source, restriction or control facts, and how the amount enters later cost. Keep centralized staking separate from unresolved validator or liquid-staking questions.

Superficial-loss adjustments

Show the 61-day window, acquisition and continued-ownership conditions, affiliated-person facts, quantity affected, denied loss, and addition to replacement-property ACB.

Source and valuation notes

Document exchange rates, token contracts, time zones, pricing sources, thin-liquidity methods, manual corrections, estimates, and links to source evidence.

Unresolved-items and assumptions log

State each missing record, uncertain right, classification choice, estimated value, and professional decision needed. Include the affected amount and what would change under an alternate conclusion.

Transfers are not mistaken for disposals

Owned-wallet movements should be linked across accounts and chains. Unmatched withdrawals stay flagged until there is evidence of a sale, gift, payment, loss, bridge, or missing receiving wallet.

Every output traces to a source

A reviewer should move from a summary number to the transaction row, source file, statement, or hash. Manual adjustments require the same traceability as imported data.

CAD valuation is reproducible

The value should identify token, contract, units, timestamp, time zone, price source, conversion path, and method. Estimated values should be labelled and material sensitivity explained.

Missing basis is visible, not silently set to zero

Zero basis can overstate gains and conceal a broken opening pool. List missing acquisition evidence and show the amount at risk while reconstruction continues.

Classification assumptions are explicit

Capital, business, property income, loans, transfers, and unresolved DeFi rights should be tagged. A default software category is not a tax opinion.

Prior-year ACB carries forward consistently

Opening units and cost should equal the prior year's accepted closing schedule, adjusted for documented corrections. If they do not, the break must appear in the exception log.

Transaction count is only one factor

More rows can increase processing and review, but count alone is a weak quote. Clean exchange trades can be easier than a smaller number of multi-chain DeFi events. Ask what percentage of data is automated, matched, duplicated, or unresolved.

Chains, protocols, NFTs, and missing data

Each chain and protocol adds decoding, contract, valuation, and ownership work. NFTs can require token-level basis. Missing exchanges or wallets add reconstruction. Closed services and thin-liquidity tokens increase judgment and documentation.

Prior-year cleanup

Current ACB may depend on several earlier years. A scope that begins in 2026 but needs 2021 acquisitions is not a one-year engagement. Prior reporting also has to be compared with the rebuilt data.

Business classification and professional review

Capital-versus-business uncertainty can require alternate calculations, evidence schedules, inventory work, and additional time from the Canadian tax professional. That review is distinct from raw-data cleanup.

Why a scoping review comes before a useful quote

A credible quote follows an account inventory, year range, sample files, estimated volume, protocol list, missing-data review, prior-report check, and deliverable definition. Publishing a generic price without that scope would create a false expectation.

Review the exception log

The taxpayer and Canadian tax professional review material missing records, classification questions, valuation estimates, superficial losses, DeFi rights, and alternate results. Each accepted resolution is added to the workpapers.

Resolve tax positions with the Canadian tax professional

The professional decides capital or business treatment, income category and timing, unresolved protocol events, foreign-property reporting, deductions, and any disclosure or prior-year correction.

Prepare and file the Canadian return

The client's Canadian tax professional uses the accepted figures and applies them to the full return. Count On Sheep does not prepare or file Canadian tax returns.

Preserve records for at least six years

CRA generally asks crypto users to keep supporting records for at least six years. Preserve raw exports, source documents, normalized data, calculations, workpapers, professional resolutions, and the filed-return connection.