From exchange CSV to Swiss tax annex.

Exchange exports are designed for account history, not Swiss tax reporting. A Binance ledger, Kraken trade log, Coinbase transaction file, or Swissquote export can each use different headers, date formats, fee logic, and asset labels.

Every exchange speaks differently

One export may call BTC "XBT", another may split one trade into multiple rows, and another may include fiat values while a different platform exports only quantities. This is why direct spreadsheet work becomes fragile across multiple exchanges.

Normalisation is the first step

The report process should normalise tickers, dates, quantities, fees, and transaction types. Buys, sells, deposits, withdrawals, rewards, staking, and fees should be classified before any tax summary is produced.

Multiple files should be combined

If you used more than one exchange, the calculation should combine all imported files into one timeline. This is especially important when assets are bought on one platform and sold on another.

What the final annex should contain

A good annex turns raw CSV rows into a readable summary: year-end wealth values, staking income, realised FIFO results, completeness warnings, source notes, and a transaction ledger.