Why Bitfinex Tax Reporting Is More Involved Than It Looks
Bitfinex has been running since 2012. That creates a specific problem: users with long account histories are working from records that span multiple market cycles, multiple exchange interfaces, and multiple export format versions. The basis for a current-year disposal can trace back to 2017 or earlier - and that older acquisition history has to survive the export process intact for the numbers to reconcile correctly today.
The structure of Bitfinex exports adds another layer. Trades and account movements live in separate report files, not one combined history. Funding income, margin records, and other specialist activity have their own paths. A filing that only exports the trade history is missing important rows before it even starts.
The Multi-Year Basis Problem on Long Bitfinex Accounts
Cost basis is an accumulation: every buy, every fee, every conversion from year one onward shapes the gain or loss on a disposal today. On an account that has been active since the early Bitfinex era, missing even one year of acquisition history understates the basis and overstates the taxable gain.
Bitfinex does not serve US persons, so this page is not framed as a US filing guide. But for filers in all other supported countries, the principle is the same: the full historical Trades and Movements export - not just the current year - is what builds an accurate basis trail. Export the maximum date range available rather than the minimum needed for last year's return.
Trades vs Movements: Bitfinex's Two Core Export Files
Bitfinex splits its history into separate report types. The Trades report covers executed orders. The Movements report covers deposits and withdrawals. Both matter for a complete reconciliation: trades show the acquisition and disposal events, movements show the transfer rows that explain where assets came from or went to.
Funding income rows and margin-related records sit in different report surfaces. If your filing includes Bitfinex lending, funding, or margin history, keep those exports beside the core Trades and Movements files rather than assuming the two main reports cover the full account.
How to Export from Bitfinex Reports
- Log in to Bitfinex and open Reports.
- Choose Trades for executed orders or Movements for deposits and withdrawals.
- Set the full date range you need - export the maximum history available, not just the current year.
- Press Confirm to preview, then press Export to download the file.
For funding and specialist records, check Bitfinex's Reports section for the report type that matches the activity. The current DYOR.tax flow processes one Bitfinex CSV per run - start with the file that covers the most critical activity for your filing year.
The Bitfinex Reporting Application: Useful Cross-Check, Not a Replacement
Bitfinex has a separate Reporting Application that can generate CSV or PDF tax reports once you connect a read-only API key. This is a useful cross-check against the raw Trades and Movements exports, but it is not a substitute for them. A tax report generated by the exchange shows you the exchange's interpretation of your activity. The raw CSV shows you the source rows, which is what DYOR.tax needs to rebuild basis independently.
What DYOR.tax Calculates from Your Bitfinex CSV
DYOR.tax turns the supported Bitfinex Trades and Movements CSV rows into buys, sells, transfers, and supporting history, then applies the country method you selected to rebuild cost basis lot by lot. The result is a filing-ready report with trade-level detail and a clear boundary between what the submitted file covers and what still needs separate review.
This page is strongest on the Bitfinex Trades and Movements surfaces currently supported in DYOR.tax. If your filing includes funding income, margin records, or other specialist reports outside those two formats, keep those files as supporting evidence rather than assuming one upload covers the full Bitfinex account.
Supported countries
- United Kingdom - Section 104 pooling with same-day and 30-day bed-and-breakfast rules; full historical Bitfinex records are critical for the UK pool calculation
- Canada - ACB method; 50% inclusion rate under current law; complete multi-year exports required for accurate adjusted cost base
- Australia - FIFO method; 50% CGT discount for assets held over 12 months; ATO tax year runs July-June
- India - flat 30% on taxable VDA disposals plus applicable surcharge and cess; check how Section 194S TDS may apply
- New Zealand - income treatment under IRD's purpose-of-disposal test; intent at acquisition determines tax treatment
- South Africa - revenue or capital depending on the facts; FIFO applied; 40% CGT inclusion if capital treatment applies
- United States - Bitfinex does not serve US persons; if you have historical activity that predates any restriction, consult a tax adviser about your reporting obligations
Also available: Kraken Tax Calculator if assets moved between exchanges in the same year, or our staking tax guide if funding income is part of the Bitfinex history you are reconciling.