Corporate Digital Asset Investment Policy: Board and CFO Framework
Corporate Digital Asset Investment Policy: A Board and CFO Governance Framework
Short answer: A corporate digital asset investment policy should define why the company may hold an asset, how much liquidity can be exposed, who can approve and execute transactions, where keys and assets are held, how positions are valued and accounted for, and what forces a review or exit. It should not begin with a Bitcoin allocation target. The board first protects operating cash, debt obligations, tax payments, payroll, and covenant compliance; only then can it approve a bounded risk budget.
A useful policy turns a board decision into controls that treasury, accounting, tax, legal, security, internal audit, and external service providers can follow. It also creates evidence: who approved an asset, which wallet was authorized, which price source was used, why a transaction fit the mandate, and how the books reconcile to the chain and custodian.
This guide was reviewed against FASB Accounting Standards Update 2023-08, SEC Staff Accounting Bulletin No. 122, COSO internal-control material, and IRS digital-asset reporting resources through July 11, 2026. It addresses a U.S.-oriented operating company, not a bank, broker-dealer, investment company, pension, charity, or government entity. Those organizations can face different or additional rules.
A policy is not an investment thesis
An investment thesis explains why management expects an asset to help the company. A policy defines what management is allowed to do even when the thesis is wrong.
The current draft previously asserted that holding cash could be a fiduciary breach, prescribed 20% to 50% Bitcoin allocations, and treated volatility as harmless. Those claims were unsupported and operationally dangerous. Cash, short-duration instruments, and credit facilities serve specific liquidity functions. Crypto assets can lose substantial value, trade around the clock, encounter custody or market failures, and create earnings volatility under fair-value accounting.
A board does not need to decide whether Bitcoin is “digital gold” before it can ask better questions:
The policy should make those answers enforceable.
The seven documents in a complete governance package
One document rarely carries the whole control system. A practical package separates stable policy from frequently changing procedures.
| Document | Purpose | Approval owner | Update frequency |
|---|---|---|---|
| Board resolution | Authorizes the program, objective, maximum exposure, and delegated officers | Board | At launch and material change |
| Digital asset investment policy | Defines eligible activities, limits, governance, reporting, and exceptions | Board or delegated committee | At least annually |
| Treasury procedures | Converts policy into trade, transfer, custody, reconciliation, and incident steps | CFO or treasurer | As operations change |
| Asset admission memo | Records legal, accounting, market, technical, and custody analysis for one asset | Cross-functional committee | Before admission and on trigger |
| Wallet and key register | Identifies approved accounts, purpose, ownership, signers, recovery, and limits | Treasury and security | Continuously |
| Counterparty register | Records approved exchanges, custodians, OTC desks, banks, and limits | Treasury, legal, risk | Continuously |
| Reporting pack | Shows exposure, liquidity, performance, control exceptions, and reconciliations | CFO to board | Monthly or quarterly |
The board resolution should not be a slogan about monetary debasement. It should record the business purpose, decision process, delegated authority, maximum risk envelope, review date, and management's duty to stop activity when controls fail.
Assign control owners before allocating capital
Digital assets cross functions that may not routinely work together. The policy should name an accountable owner for every control, not merely say “management.”
| Control area | Accountable owner | Required independent challenge |
|---|---|---|
| Investment objective and risk appetite | Board | Audit or risk committee |
| Liquidity reserve and allocation calculation | CFO or treasurer | FP&A and board committee |
| Legal and regulatory analysis | General counsel | External counsel where needed |
| Accounting policy | Controller | External auditor consultation where appropriate |
| Tax treatment and lots | Tax lead | External tax adviser where needed |
| Asset and protocol technical review | Security or engineering lead | Independent security review |
| Custodian and exchange due diligence | Treasury | Legal, security, and procurement |
| Trade preparation | Authorized treasury dealer | Separate approver |
| Wallet signing | Named signers or custody workflow | Policy engine and threshold approval |
| Reconciliation | Accounting operations | Controller review |
| Incident response | Security incident commander | Legal, treasury, communications, board escalation |
| Internal control testing | Internal audit or equivalent | Audit committee |
Segregation must survive vacations, departures, and emergencies. If the treasurer can add a destination, prepare a transfer, approve it, and reconcile it, a nominal multisignature wallet does not solve the control failure.
Define the objective in testable terms
Common objectives include strategic reserve exposure, payment operations, customer settlement, protocol participation, acquisition consideration, or research and development. Each creates a different control set.
“Hedge inflation” is too vague on its own. It should be translated into a measurable mandate such as:
Permit a limited, long-horizon allocation funded only from surplus liquidity, with no reliance on disposition proceeds for forecast obligations over the approved horizon.
That statement can be tested. It implies a defined surplus-liquidity calculation, a long holding horizon, no use of operating reserves, and no assumption that the asset can be sold at a favorable price when bills are due.
The policy should also state prohibited objectives. An operating company may forbid leveraged speculation, market making, unsecured lending, anonymous counterparties, or yield strategies even if the underlying asset itself is eligible.
Calculate surplus liquidity before a percentage allocation
A fixed percentage of “treasury” is ambiguous. Does the denominator include restricted cash, customer funds, undrawn credit, foreign subsidiaries, acquisition reserves, or operating cash needed next month? A defensible limit starts with obligations.
Surplus-liquidity formula
Use a board-approved horizon and stress case:
Surplus liquidity = readily available liquid resources minus protected obligations minus contingency buffer
Protected obligations may include:
The contingency buffer should reflect revenue volatility, customer concentration, refinancing risk, and the time required to access backup liquidity.
Worked risk-budget example
Assume a company reports:
| Item | Amount |
|---|---|
| Cash and eligible short-duration liquidity | $120 million |
| Protected 12-month operating obligations | $72 million |
| Debt, tax, and committed capital needs | $18 million |
| Board-approved contingency buffer | $20 million |
| Calculated surplus liquidity | $10 million |
If the board permits at most 20% of calculated surplus liquidity in digital assets, the initial cap is $2 million, or 1.7% of the $120 million headline liquidity figure. The policy should say whether the cap is based on acquisition cost, current fair value, or both.
Now stress a 70% decline. The $2 million position falls to $600,000, a $1.4 million loss. Directors should ask whether that loss, plus earnings volatility and operational costs, remains tolerable. If not, reduce the risk budget before purchase.
These figures are illustrative, not a recommended allocation. Their purpose is to show why “25% of excess cash” is not a complete control.
Use multiple limits, not one allocation ceiling
A mature policy can apply all of these:
Limits should state how prices are determined and what happens after passive appreciation causes a breach. An automatic sale may create tax, market-impact, or disclosure problems; indefinite discretion can make the cap meaningless. A common design stops new purchases immediately and requires a documented review within a specified period.
Asset admission: approve properties, not popularity
Bitcoin and Ether differ from stablecoins, wrapped assets, governance tokens, liquid-staking tokens, and tokenized securities. The policy should not label one “store of value” and another “yield” and assume the risks are solved.
Asset admission scorecard
| Dimension | Questions for the admission memo |
|---|---|
| Business purpose | Which approved objective requires this asset? |
| Legal characterization | Could holding, trading, staking, lending, or distributing it trigger specific obligations? |
| Accounting scope | Does it meet every criterion in the selected accounting guidance? Are staking rewards, wrappers, or receivables separate units of account? |
| Tax | How are acquisition, rewards, forks, disposals, fees, and basis tracked? |
| Market quality | Where does it trade, with what depth, spread, concentration, and manipulation risk? |
| Network | What are finality, reorganization, congestion, fee, and upgrade risks? |
| Custody | Can approved providers or internal controls support the asset and recovery process? |
| Smart contracts | Does exposure depend on bridges, wrappers, staking contracts, or upgradeable code? |
| Governance | Who can change supply, transfer rules, redemption, collateral, or protocol parameters? |
| Valuation | Which principal or most advantageous market and price source support fair value? |
| Liquidity | Can the company exit within its stress horizon without unacceptable impact? |
| Disclosure | Could the position be material by size, volatility, concentration, or narrative importance? |
Admission should expire or reopen after defined triggers: a material network upgrade, depeg, custody change, regulatory event, accounting change, security incident, market-liquidity deterioration, governance capture, or loss of a reliable valuation source.
Activities require separate approval from assets
Approval to hold Ether should not automatically authorize staking it. Approval to hold USDC should not authorize lending it to a protocol. Each activity adds a risk layer.
| Activity | Added risks requiring explicit treatment |
|---|---|
| Spot purchase and hold | Price, custody, execution, tax, valuation |
| Staking | Lockup or exit queues, slashing, validator, reward accounting, protocol and service-provider risk |
| Liquid staking | All staking risks plus issuer, smart-contract, liquidity, price-basis, and accounting-scope questions |
| Lending | Borrower, collateral, liquidation, platform, legal, and withdrawal risk |
| DeFi liquidity provision | Smart contract, oracle, impermanent loss, governance, front-running, and token-incentive risk |
| Derivatives | Leverage, margin, liquidation, basis, counterparty, documentation, and hedge-accounting questions |
| Cross-chain bridge | Contract, validator, finality, wrapped-asset, and recovery risk |
| Customer custody | Safeguarding, legal ownership, operational, disclosure, and regulatory duties distinct from corporate holdings |
An operating company can choose a simple policy: spot assets only, no lending, no leverage, no bridges, no staking, and no smart-contract approvals. Simplicity is a control decision, not a failure to capture yield.
Accounting: understand the scope of ASU 2023-08
FASB ASU 2023-08 requires crypto assets within its scope to be measured at fair value each reporting period, with changes in net income. It also requires separate presentation and enhanced disclosures, including information about significant holdings, contractual sale restrictions, activity, gains, and losses.
The scope is not “all digital assets.” A qualifying asset must meet specified criteria, including being an intangible asset, not giving the holder enforceable rights to underlying goods, services, or other assets, residing on a distributed ledger, being cryptographically secured, fungible, and not created or issued by the reporting entity or its related parties.
That means accounting needs a documented conclusion for each asset and arrangement. Questions can become harder for:
The original page's “five-exchange VWAP” rule was invented. Fair-value methodology should follow applicable accounting guidance and the entity's facts, including the principal market, observable inputs, market accessibility, cut-off time, and controls over pricing data. Management should align with its accounting policy and auditor rather than adopt a generic web formula.
SAB 122 changed safeguarding guidance, not every custody question
SEC Staff Accounting Bulletin No. 122, effective January 30, 2025, rescinded SAB 121's Topic 5.FF interpretive guidance. The rescission does not mean obligations to safeguard customer crypto assets have no accounting consequences. An entity should analyze loss obligations under applicable contingency guidance and provide disclosures required by relevant standards and SEC rules.
For an operating company's own treasury, the immediate issue is usually asset recognition, fair value, control, disclosure, and custody risk. If the company safeguards assets for customers or affiliates, that activity needs a separate accounting and legal analysis rather than being folded into the treasury policy.
Valuation controls
Around-the-clock markets create cut-off and source questions that traditional treasury teams may not have documented.
A valuation procedure should define:
Accounting should obtain balances independently from the trade preparer, reconcile custodian statements and wallet addresses, verify ownership or control, and investigate every unexplained difference.
Tax-lot and transaction records
The IRS states that digital-asset income and dispositions must be reported under applicable tax rules. Corporate tax treatment depends on the entity, transaction, jurisdiction, and asset. A policy should require complete records, not promise “tax optimization.”
Capture at transaction time:
Selling an asset to recognize a loss and immediately reacquiring economic exposure can raise tax, accounting, legal, market, and policy issues. The policy should prohibit ad hoc tax trades and require tax-led review based on current law and the company's facts.
Custody is a control architecture
“Use a custodian plus a 3-of-5 multisig” is not a complete custody strategy. The company must determine legal title, key authority, recovery, insolvency treatment, service dependencies, insurance limits, transaction policy, and evidence.
Custody models
| Model | Strength | Main exposure |
|---|---|---|
| Qualified or institutional custodian | Specialized controls, statements, workflows, possible regulatory oversight | Provider, legal entity, omnibus structure, availability, and contractual risk |
| Collaborative or MPC custody | Distributed signing and configurable policy | Service dependency and policy-admin concentration |
| Company-controlled multisig | Direct control and transparent threshold | Internal key operations, succession, recovery, and signer coercion |
| Exchange custody | Convenient trading and settlement | Concentrated venue, prefunding, insolvency, and withdrawal risk |
| Hardware wallet held by one executive | Simple | Key-person, loss, coercion, weak segregation, and poor continuity |
The last model should not hold material corporate reserves.
Custodian due diligence
Review the exact contracting entity, asset ownership language, segregation, subcustodians, insolvency treatment, key architecture, withdrawal authorization, allowlists, policy changes, SOC reports or equivalent assurance, incident history, insurance scope and exclusions, financial condition, geographic dependencies, service levels, data export, fork and airdrop treatment, staking terms, and exit process.
Do not summarize insurance as “assets are insured.” Identify insured risks, named insured, limits, deductibles, exclusions, aggregation, and whether a claim would benefit the company.
Wallet and key register
Every approved address should have a record containing:
Watch-only addresses should feed treasury and accounting monitoring independently of the transaction system. A wallet appearing in a spreadsheet is not proof that the company controls it; control evidence should be obtained and retained under an approved procedure.
Transaction workflow
A material transfer should pass through distinct stages:
No employee should approve a destination change through the same email or chat thread that requested the payment. High-risk changes need callback or another independently maintained verification channel.
Trading and counterparty controls
An investment policy should define how the company gets from fiat to the approved asset without leaving large balances on a venue or leaking intent.
Set rules for:
A lower quoted price can be more expensive after spread, fees, slippage, settlement delay, failed withdrawal, and counterparty exposure. Evaluate all-in execution and settlement risk.
Rebalancing without improvisation
The policy should distinguish four events:
A purchase breach should be blocked. Passive appreciation may trigger a pause and review rather than an immediate sale. Liquidity deterioration can require a planned reduction because the original source of risk capital has disappeared. A control failure may justify suspension or emergency transfer even if market price is favorable.
The board should define deadlines and responsible officers for each event. “Management may reconsider” is not a control.
Drawdown and crisis policy
Volatility is a real financial risk when it affects liquidity, earnings, financing, covenants, reputation, or the ability to execute strategy. A 50% decline should not automatically force a sale, but neither should a policy prohibit selling under all circumstances.
Drawdown decision tree
When a threshold is crossed, management should ask in order:
Price alone may not determine the answer. An exchange failure with no price decline can be more urgent than a broad market drawdown.
Trigger library
Require immediate escalation for:
Incident response playbooks
Suspected key compromise
Pause affected workflows, preserve logs, identify all privileges held by the key, revoke sessions or policy credentials, move assets through the pre-approved recovery path where safe, notify custody and response contacts, and reconcile every transaction from the suspected period. Do not improvise a destination during the incident.
Wrong-address or fraudulent-payment attempt
Stop pending approvals, verify whether anything was broadcast, preserve communication evidence, alert the custodian or venue immediately, and invoke legal and law-enforcement channels where appropriate. Public chains do not provide a general chargeback.
Custodian outage
Confirm whether the issue affects interfaces, signing, withdrawals, or underlying asset control. Freeze new deposits, monitor independently, assess liquidity obligations, and activate the documented alternate-custody or liquidity plan only after destination verification.
Chain fork or contentious upgrade
Suspend transfers around the event if policy requires, follow custodian support, determine which asset the company recognizes, assess replay protection, and do not interact with forked assets until legal, accounting, tax, and security owners approve a plan.
Stablecoin depeg
Separate market-price deviation from redemption impairment. Confirm issuer terms, reserve or redemption information, venue liquidity, counterparty concentration, and operational access. Execute only the pre-approved response tier; a panicked swap through thin liquidity can amplify loss.
Board reporting pack
Directors need decision information, not a page of wallet balances.
Exposure dashboard
Control dashboard
Decision dashboard
“Satoshis per share” can be a voluntary operating metric for some public companies, but it is not a universal GAAP disclosure requirement and can mislead if financing, dilution, debt, or enterprise value are ignored. Any non-GAAP or supplemental metric needs clear calculation, consistency, and applicable disclosure review.
Policy exception process
Emergencies and unusual transactions will test whether the policy is real. An exception should state:
Never allow a standing “CFO discretion” clause to override every numeric and procedural limit. Delegation should be bounded and reviewable.
Annual policy review
At least annually, and after material triggers, review:
Record the evidence considered. Renewing the same policy date without re-performing the analysis creates false comfort.
A board-ready policy outline
The final policy can use this structure:
The policy should reference procedures rather than hard-code every vendor, wallet address, or employee name. Stable authority belongs in the policy; operational details belong in controlled registers and procedures.
Readiness scorecard
Score each domain from 0 to 2: absent, documented but untested, or implemented with current evidence.
| Domain | Evidence question |
|---|---|
| Objective | Is the business purpose specific and testable? |
| Liquidity | Are protected obligations and contingency buffers calculated under stress? |
| Risk limits | Are cost, fair-value, asset, custodian, wallet, and activity caps enforceable? |
| Asset admission | Does every asset have current legal, accounting, tax, market, technical, and custody analysis? |
| Authority | Are board, treasury, accounting, security, and signer duties separated? |
| Custody | Are legal title, key control, recovery, provider failure, and exit tested? |
| Transactions | Are destination, intent, calldata, approvals, finality, and reconciliation independently verified? |
| Accounting | Is scope, valuation, cut-off, ownership evidence, and disclosure documented? |
| Tax records | Can every unit and transaction be traced to basis and reporting evidence? |
| Counterparties | Are legal entity, exposure, settlement, financial, and operational risks monitored? |
| Incidents | Have key compromise, provider outage, depeg, fork, and wrong-address playbooks been rehearsed? |
| Reporting | Does the board receive exposure, control, and decision evidence? |
A score below 16 of 24 suggests the program is not ready for material funding. A high score is not an audit opinion or security certification. Any zero in liquidity, authority, custody, transactions, accounting, or incident response should block launch.
Frequently asked questions
How much Bitcoin should a company hold?
There is no universal percentage. Start with protected obligations, contingency reserves, financing constraints, risk appetite, and a severe drawdown scenario. The resulting risk budget may be zero.
Does FASB require all crypto assets to be measured at fair value?
No. ASU 2023-08 applies to assets meeting all of its scope criteria. Stablecoins, wrapped assets, tokenized claims, issuer-related tokens, staking arrangements, and other instruments may require separate analysis.
Did SAB 122 remove crypto custody risk?
No. It rescinded SAB 121's specific staff accounting guidance. Entities still analyze safeguarding obligations, loss contingencies, disclosures, legal duties, and operational risk under applicable requirements.
Should a company self-custody its Bitcoin?
Only if it can operate stronger key governance, segregation, recovery, monitoring, succession, and assurance than the alternatives. Direct control is not automatically lower risk than an institutional custodian.
Is multisig enough for corporate custody?
No. It distributes signing authority, but the company still needs destination controls, independent transaction review, secure devices, administrator governance, recovery, reconciliation, and incident procedures.
Should the policy ban selling during a drawdown?
No blanket rule fits every company. Selling may be necessary after liquidity deterioration, covenant pressure, thesis failure, custody risk, or legal change. The policy should define review triggers and authority rather than promise permanent holding.
Can the company earn yield on treasury crypto?
Only after separately approving the activity and its added legal, accounting, tax, liquidity, counterparty, slashing, and smart-contract risks. Yield is compensation for risk, not a free enhancement.
How often should wallets be reconciled?
Frequency should match activity and materiality. Operational wallets may need daily or continuous monitoring; inactive reserves still need independent balance, control, and period-end verification.
Source note and analytical limits
FASB ASU 2023-08 supports the accounting scope, fair-value, presentation, and disclosure discussion. SEC SAB 122 documents the rescission of SAB 121 and directs safeguarding entities back to applicable contingency and disclosure requirements. COSO material supports the control-environment, risk-assessment, control-activity, information, and monitoring approach. IRS resources support the requirement to retain and report digital-asset transaction information under applicable tax rules.
The surplus-liquidity formula, illustrative balance sheet, multi-limit framework, asset-admission scorecard, transaction workflow, board pack, incident playbooks, and readiness score are CryptosEyes analytical tools. They do not determine fiduciary compliance, accounting treatment, tax liability, regulatory status, or an appropriate allocation for a particular company.
What to read next
Read <a href="/insights/on-chain-corporate-governance-dao-llc-guide-2026">the DAO-LLC and onchain governance guide</a> for the relationship between legal authority and executable votes. Then use <a href="/insights/whale-on-chain-custody-standards-2026-analysis">the multisignature custody analysis</a> to examine signer and recovery design, and <a href="/insights/crypto-exchange-reserve-risk-checklist-2026">the exchange reserve-risk checklist</a> when assessing trading and custody counterparties.
The practical takeaway: approve a loss-bearing capacity and control system, not a narrative. A company should be able to fund every protected obligation, explain every balance, reproduce every approval, and recover from a provider or key failure without relying on the asset price to cooperate.
About the Editorial Team
CryptosEyes publishes independent, source-grounded treasury research. Illustrative controls are separated from accounting requirements, current guidance is linked directly, and no universal allocation is presented as prudent.
Source & Review Basis
This article is reviewed against the source types below. Source links are provided to help readers verify primary documents, market context, and methodology independently.
Scope criteria, fair-value measurement, income-statement treatment, presentation, transition, and disclosures for qualifying crypto assets.
Official project overview and summary of the amendments for assets within scope.
January 2025 rescission of SAB 121 and direction to apply relevant contingency and disclosure requirements to safeguarding obligations.
Internal-control perspectives for blockchain use in financial reporting, oversight, risk assessment, control design, information, and monitoring.
Enterprise risk-management framework and board-management oversight context.
Federal digital-asset reporting overview for individuals, businesses, and other taxpayers.