Why Bybit Tax Reporting Is More Involved Than It Looks
Bybit's account statement has documented gaps
Bybit's own documentation says the account statement export does not include Bybit Earn, structured products, custodial trading subaccounts, MT4/MT5 accounts, or bonuses. That list is long enough that users who export the statement and call it done are often missing whole categories of taxable activity. Five things that make Bybit records more complex than a single export covers:
- Account statement explicitly excludes Earn, MT4/MT5, structured products, subaccount balances, and bonuses per Bybit's own documentation
- Data export is only available on the web account - the Bybit app does not support exports
- If your history runs longer than 12 months, you need multiple export periods
- Different activity types may require different export types: Transaction Log, Order History, and Account Statement cover different surfaces
- Some spot order history is not included in the account statement, so the two exports can describe different activity
Bybit does not issue tax forms
Unlike some US-registered exchanges, Bybit does not issue tax forms such as 1099-DA. Bybit says it does not offer services in the United States, so there is no US reporting infrastructure. If you traded from a permitted jurisdiction, the raw Bybit CSV is the primary source - reconciliation falls entirely on the exported file rather than any platform-issued tax document.
How to Export Your Bybit Transaction History
Which export type covers which activity
Bybit splits history across several export types. The right one depends on what you need to report:
- Transaction Log - balance changes across the account; often the broadest view of what moved when
- Order History - filled spot orders, fees, and trade-level detail not always included in the statement
- Account Statement - summary-level record, but explicitly excludes Earn, structured products, MT4/MT5, subaccounts, and bonuses
For a spot-heavy year, the Transaction Log or Order History usually gives more complete detail than the statement alone. If your year included Earn or specialist products, those records need a separate export.
Web-only export and date-range limits
Use the Bybit web account - the app does not support data export. Steps:
- Open Bybit's Self-Export My Account Data or Data Export flow on the web account.
- Select the export type that covers the activity you need: Transaction Log, Order History, or Account Statement.
- Choose the full date range. If your history runs longer than 12 months, export multiple periods.
- Wait for the export to finish, then download the CSV while the link is still valid.
Bybit Products and Their Tax Treatment
Spot trades and Convert swaps
Selling crypto for fiat and swapping one coin for another are typically taxable disposal events in all seven countries DYOR.tax supports. The cost basis of each trade lot, holding period, and sale proceeds determine the gain or loss. Spot trades are the most reliably exported activity on Bybit, and the Transaction Log or Order History CSV covers this surface well.
Bybit Earn, staking, and reward income
Bybit Earn products and staking distributions typically need income treatment when received - the fair market value at receipt is often the taxable amount, and that same value becomes cost basis for the later disposal. This is where the account statement gap matters most: Bybit says Earn activity is not included in the statement export, so you need a separate export for those rows if your year included Earn rewards.
Perpetuals, derivatives, and MT4/MT5
Perpetual contract P&L and funding fees use different CSV formats than spot history. MT4/MT5 accounts are also explicitly excluded from the account statement. DYOR.tax currently processes Bybit spot and transfer exports. If your year depended on perpetuals or derivatives, keep those records as a separate layer to review alongside the report.
How DYOR.tax Processes Your Bybit CSV
What's in the report
DYOR.tax turns your supported Bybit CSV rows into a clean timeline of buys, sells, deposits, withdrawals, and cost basis lots. The cost basis method applied depends on your filing country: FIFO, LIFO, or HIFO for US filers; Section 104 pooling for UK filers (same-day and 30-day matching included); ACB for Canadian filers; FIFO for Australian, New Zealand, Indian, and South African filers. Transfers are kept separate from disposals, and reward rows flagged as income in the CSV are separated from trade rows.
Supported countries
Because Bybit does not serve the US, this page sees more traffic from traders filing in the United Kingdom, Canada, Australia, New Zealand, India, and South Africa. All six are fully supported. The US country option is also available in the calculator for filers in US-permitted contexts.
Also available
If you used other exchanges alongside Bybit, the Binance tax calculator and OKX tax calculator follow the same CSV-upload flow and support the same seven countries.
Country-Specific Tax Treatment
The Bybit CSV is the raw input. The tax treatment comes from your filing country, not from the exchange:
- UK: HMRC Section 104 pooling with same-day and 30-day matching. Crypto-to-crypto swaps are disposals. Earn rewards typically treated as miscellaneous income on receipt, capital gain on later disposal.
- Canada: CRA Adjusted Cost Base method. Disposals include sells, swaps, spending, and gifting. Frequent traders may shift from capital gains into business income.
- Australia: ATO FIFO. Most disposals including swaps trigger CGT events. Longer-term holdings may qualify for the 50% CGT discount.
- India: 30% flat tax on VDA gains plus surcharge and cess. Earn and staking income separately reportable as VDA income.
- New Zealand: IRD intent-based income test leads the analysis. Most crypto is taxed as income rather than as a capital gain.
- South Africa: SARS revenue vs capital distinction based on the facts. FIFO applied in DYOR.tax reports.
If reward income rows are the most complex part of your Bybit history, our staking tax guide explains how receipt and later disposal are typically treated separately.