When I started advising clients and preparing companies to hold bitcoin on the corporate balance sheet, the first thing I realized was that this is as much an operational and treasury challenge as it is an accounting one. Bitcoin is not cash in the traditional sense, and it brings custody, control, valuation, tax, and disclosure implications that CFOs must treat systematically. Below I share the operational controls I require teams to implement and the typical accounting entries to expect — explained plainly so you can act confidently and discuss the topic with auditors, board members, and your treasury team.

Operational controls every CFO must put in place

Integrating bitcoin is a cross-functional project. I always create a steering group with finance, legal, compliance, treasury, IT/security, and internal audit. These are the core controls and processes I mandate:

  • Governance and policy — Create a formal crypto treasury policy that defines purpose (held for treasury, strategic investment, or trading), authorized counterparties, approval limits for purchases and disposals, and reporting frequency. The board should formally approve the policy.
  • Custody strategy — Decide between self-custody and third-party custodians (e.g., Coinbase Custody, BitGo, Fireblocks). For self-custody, implement multi-signature wallets, hardware security modules (HSMs), geographically segregated key storage, and strict key rotation policies. For custodians, conduct vendor due diligence, review SOC 2 reports, insurance, insolvency protections, and escape procedures.
  • Segregation of duties — Ensure one team cannot both authorize and execute transfers. Typical segregation: Treasury approves trades, a different ops team executes, and finance reconciles and records transactions.
  • Access controls — Enforce least-privilege access, MFA, hardware keys, role-based access, and logging of all wallet operations. Maintain an auditable ledger of who approved transfers and who signed them.
  • Reconciliation and custody confirmation — Reconcile on-chain balances daily and match them to custodial statements. Reconciliation should include transaction IDs, amounts, addresses, and timestamps.
  • Private key management and disaster recovery — Document procedures for key loss, compromised keys, and succession. Test recovery procedures periodically (tabletop and live tests in a controlled environment).
  • Insurance and third-party risk — Where possible, obtain insurance covering theft, cyber breaches, and custodian insolvency. Understand policy limits and exclusions.
  • Valuation, treasury, and volatility policy — Define how you will value holdings (e.g., market price at close) for internal reporting, liquidity triggers, and hedging rules. Set thresholds that trigger hedging actions or rebalancing.
  • Tax and regulatory compliance — Coordinate with tax advisors early. Establish processes for tracking cost basis, transaction timestamps, and gains/losses. Conduct KYC/AML checks for counterparties and exchanges.
  • Internal audit and external audit readiness — Maintain detailed controls documentation, reconciliations, and evidence for auditor testing. Plan for external audit procedures that examine access logs, wallet addresses, and custodial confirmations.
  • Vendor SLAs and contingency playbooks — Define SLAs with custodians and exchanges and prepare contingency plans (alternative counterparties, cold storage transfers) should a vendor fail.

    • How to account for bitcoin: principles and common practices

    Accounting treatment depends on jurisdiction and the company’s intent (treasury vs trading) — and the standards are still evolving. I always tell CFOs: involve your external auditors early. The two common frameworks produce different practical outcomes:

  • Under IFRS — Most companies apply IAS 38 (intangible assets) because bitcoin does not give rise to contractual cash flows like cash or financial instruments. Intangibles are carried at cost less accumulated impairment, except when a reliable active market allows revaluation. In practice, many companies carry bitcoin at cost and test for impairment; upward movements are generally not recognized unless you adopt a revaluation model and an active market exists.
  • Under US GAAP — Historically, companies have treated cryptocurrencies as indefinite-lived intangible assets (similar to IFRS practice), measured at cost less impairment. There is pressure for clearer guidance; some entities treat certain holdings as inventory if held for sale in the ordinary course of business. Again, upward revaluations are generally not permitted — impairments flow through earnings.

    • Regardless of framework, the practical implications are similar: initial recognition at cost, subsequent measurement at cost less impairment (unless revaluation is permissible and elected), and recognition of gains/losses on disposal or impairment.

    Typical journal entries and a practical table

    Below I lay out standard journal entries you’ll use. Replace account names with your chart of accounts equivalents.

    Scenario Debit Credit Notes
    Purchase of bitcoin Crypto asset (at cost) Cash/Bank Record purchase price plus transaction fees capitalized to the asset
    Sale of bitcoin Cash/Bank Crypto asset (remove at cost)
    Recognize gain on sale Crypto asset disposal/COGS (if inventory) or Loss/Gain on disposal Gain on disposal (PL) Difference between sale proceeds and carrying amount
    Impairment (downward only) Impairment loss (P&L) Crypto asset (reduce carrying amount) Recorded when recoverable amount < carrying amount under applicable standard
    Transfer between company wallets (internal) No accounting entry if no change in ownership No accounting entry Record operational evidence and reconcile addresses

    Example: I buy 1 BTC at $30,000 (fees $500). Journal entry on purchase:

  • Debit Crypto asset $30,500
  • Credit Cash/Bank $30,500

    • Later I sell 1 BTC for $40,000 (fees $400). Cash received net $39,600. Remove the asset at cost of $30,500 and recognize gain:

  • Debit Cash $39,600
  • Debit Loss on disposal (if any) or adjust accordingly
  • Credit Crypto asset $30,500
  • Credit Gain on sale $9,100

    • Disclosure and reporting

    Transparent disclosure is essential. I advise clients to include in financial statements:

  • Accounting policy for crypto (classification, valuation, impairment rules).
  • Quantitative disclosures: carrying amount, movements (purchases, disposals, impairment), and any revaluations.
  • Risk disclosures: custodial arrangements, concentration risk, market risk, and liquidity risk.
  • Operational controls and insurance coverage summaries for stakeholder confidence.

    • Treasury, hedging, and tax practicalities

    Operationally, you’ll want to define hedging rules if you are exposed to price volatility. For treasury use, consider stablecoin overlays for operational liquidity or use options/futures to hedge large exposures. Tax timing matters: tracking cost basis per lot is critical when you dispose of portions of holdings. I push teams to use token tracking tools and integrate exchange/custodian reports into the accounting system — manual reconciliation becomes a nightmare otherwise.

    Finally, remember that regulators and standard setters are active in this space. Keep your auditors and legal counsel in the loop, document every decision, and be prepared to adapt policies as accounting guidance and tax rules evolve.