Home Tax & Compliance How BitBooks Supports Tax Reporting

How BitBooks Supports Tax Reporting

Last updated on May 02, 2026

What BitBooks does for taxes

BitBooks is not a tax-filing tool. We don't generate tax returns, calculate tax owed, or file with any tax authority.

What we do:

  • Keep accurate, audit-friendly books that your tax preparer can use
  • Track Bitcoin transactions in a way that supports capital gains and loss calculations
  • Track multi-currency activity for businesses operating across borders
  • Produce financial reports (P&L, Balance Sheet, etc.) that map cleanly to tax forms
  • Export data in formats your accountant can analyze (Excel, PDF)

Your tax preparer (a CPA, tax accountant, or tax software like TurboTax/H&R Block) takes BitBooks data and produces the actual tax return.

What your tax preparer typically needs

For a standard tax filing, your preparer asks for:

What they want Where to find it in BitBooks
P&L for the tax year Reports → Profit & Loss, year-to-date
Balance Sheet at year-end Reports → Balance Sheet, as of December 31
General Ledger for the year Reports → General Ledger, full year, exported to Excel
Trial Balance at year-end Reports → Trial Balance
List of contacts with addresses Admin → Contacts (export)
Bitcoin transaction history with rates General Ledger filtered to Bitcoin-related accounts; or transaction-level export
Realized and unrealized BTC gains The General Ledger plus FX revaluation entries
Tax form-specific data (1099 issued, etc.) Vendor list (kind=Vendor) for 1099 reporting

You'd export each of these and send to the tax preparer. They take it from there.

The Bitcoin-specific challenges

Bitcoin makes tax reporting more complex than fiat-only books because:

  • Realized gains and losses on each BTC sale need to be calculated based on cost basis (what you paid for those specific sats)
  • Cost basis methods (FIFO, LIFO, specific identification, average cost) vary by jurisdiction and choice
  • Unrealized gains may or may not be taxable in your jurisdiction (US: usually no for individuals, sometimes yes for treasuries; varies elsewhere)
  • Mining income is taxable as ordinary income at the time of receipt, then capital gains apply when you sell what you mined
  • Lightning vs on-chain doesn't fundamentally change tax treatment, but tracking Lightning's many small transactions is more involved

BitBooks records the data your preparer needs. The actual tax computation still requires their expertise.

The data BitBooks provides for crypto taxes

When your preparer asks for "Bitcoin tax data," what they typically want:

A list of all BTC purchases (acquisitions)

For each: date, amount in BTC, amount in USD (cost basis), the wallet it went to.

In BitBooks: filter the General Ledger or Transactions to your BTC wallet accounts, money-in side. Export to Excel.

A list of all BTC sales (disposals)

For each: date, amount in BTC, amount in USD (proceeds), the wallet it came from, the cost basis used.

In BitBooks: same as above but money-out side. The cost basis isn't auto-computed in current V2; your preparer matches purchases to sales using their preferred method.

A list of mining or earned BTC

For each: date, amount in BTC, USD value at receipt time, the wallet it landed in.

In BitBooks: filter to your "Sales: Bitcoin" or "Mining Income" account, money-in side.

Year-end BTC balance

The total BTC in all your wallets on December 31, with USD value.

In BitBooks: Balance Sheet as of December 31, look at the BTC asset accounts.

Cost basis methods

Most jurisdictions let you pick a cost basis method:

  • FIFO (First In, First Out). The oldest BTC you bought is the first one sold. Common default.
  • LIFO (Last In, First Out). Newest first. Less common; sometimes disallowed.
  • Specific identification. Pick which specific lots are sold. Most flexible but most paperwork.
  • Average cost. All your BTC averages out. Simple but less optimization.

BitBooks records all your purchases with their dates and rates. Your preparer (or a specialized crypto tax tool) applies the chosen method.

Specialized crypto tax tools

For complex Bitcoin tax situations, your preparer may want a tool like CoinLedger, Koinly, or similar to compute the gain/loss schedule. These tools take your transaction list and apply your chosen cost basis method.

You'd export your BTC transaction history from BitBooks (Excel from the General Ledger filtered to BTC wallets), import to the tax tool, and let it generate the schedule.

This is in addition to BitBooks, not a replacement for it. BitBooks is your books; the tax tool is just for the gains schedule.

What changes year over year

Each tax year is a separate exercise. The flow each January:

  1. Make sure December's books are reconciled and closed
  2. Run a year-end FX revaluation if applicable
  3. Make any year-end adjustments (depreciation, accruals)
  4. Close the year (set Lock Date to December 31)
  5. Export the reports your preparer needs
  6. Deliver to your preparer
  7. After preparer files, file your return

The first year is the hardest (figuring out what your preparer wants, learning the export workflow). Subsequent years are routine.

Common questions

"Will BitBooks file my taxes for me?"

No. We're not a tax-filing tool. Use a CPA or tax software for filing.

"Will BitBooks tell me how much tax I owe?"

No. Tax owed depends on your jurisdiction, deductions, credits, business structure, and many other factors a tax professional handles.

"What if my country has weird crypto rules?"

BitBooks tracks the data; your tax preparer applies the rules. Whether it's the US (capital gains, like-kind exchange disallowed for crypto), Germany (one-year holding rule), Portugal (no capital gains for individual investors as of 2026), or anywhere else, the underlying transaction data is the same. Your preparer knows the local rules.

"Can I get a 'tax report' button in BitBooks?"

Not yet. The Reports page produces the data; tax-specific reports (cost-basis schedules, 1099 prep, etc.) are roadmap items. For now, the General Ledger export covers what's needed.

Where to go next