What Happened
A non-financial company decided to diversify its treasury reserves by moving $30 million from cash into Bitcoin. The board approved the investment, and compliance vetted the exchange and custodian. Anti-money laundering and sanctions screening controls were in place, and the transaction cleared without incident.
The company's economic position hadn't changed; it had simply exchanged $30 million of cash for $30 million of Bitcoin trading in deep, liquid markets. Treasury reported the move as a redeployment of excess liquid reserves. Then Finance closed the quarter.
The current ratio dropped from 2.0x to 1.7x, and the cash ratio fell from 1.0x to 0.7x. The balance sheet now showed materially weaker liquidity than the board had anticipated, despite no economic loss occurring at the point of purchase.
The problem wasn't the Bitcoin investment itself. It was that nobody had asked Finance what the transaction would do to the financial statements before Compliance approved it.
Timeline
Pre-transaction: Company holds $100 million cash, $100 million other current assets, and $100 million current liabilities. Current ratio: 2.0x. Cash ratio: 1.0x.
Approval phase: Treasury proposes moving $30 million into Bitcoin as a long-term reserve diversification. Compliance reviews and approves the exchange, custodian, wallet screening, and AML controls. Board approves based on the asset's deep market liquidity and potential appreciation.
Execution: Company purchases $30 million of Bitcoin. Economic value unchanged.
Quarter-end reporting: Under IFRS, the Bitcoin is classified as a non-current intangible asset per IAS 38 guidance from the IFRS Interpretations Committee. Current assets fall to $170 million ($70 million cash + $100 million other current assets). Current ratio drops to 1.7x. Cash ratio falls to 0.7x.
Post-incident: Management discovers the disconnect between Treasury's definition of "liquid reserves" (assets that can be sold quickly) and Finance's classification under IFRS (current vs. non-current balance sheet presentation). Financing covenant discussions become more difficult. Internal treasury limits require recalibration.
Which Controls Failed or Were Missing
Control gap 1: Accounting treatment not determined pre-transaction
The approval workflow required Compliance, Risk, and Treasury sign-off. It did not require Finance to confirm the accounting classification and balance-sheet impact before execution. Treasury classified Bitcoin as a liquid reserve based on market depth. Finance classified it as a non-current intangible asset based on IAS 38. Nobody reconciled these views before the board voted.
Control gap 2: No scenario modeling of financial statement impact
The board paper included economic analysis of Bitcoin's potential return and volatility. It did not model how the investment would appear on the balance sheet or income statement under realistic price movements. The company had no advance visibility into how the transaction would affect reported liquidity metrics or covenant compliance.
Control gap 3: Undefined terms in treasury policy
The investment policy permitted a percentage of "liquid reserves" to be deployed into alternative assets. It did not define whether "liquid" meant economic liquidity (tradability) or accounting liquidity (current asset classification). Treasury and Finance were applying different, internally coherent definitions to the same term.
Control gap 4: No cross-functional review requirement
The approval process treated accounting as a post-execution reporting function rather than a pre-transaction control input. Finance learned about the investment when Treasury requested the journal entry.
What the Relevant Standards Require
IAS 38 (Intangible Assets) governs the accounting treatment for cryptocurrency holdings that don't qualify as inventory under IAS 2. The IFRS Interpretations Committee has confirmed that cryptocurrency meeting certain characteristics should be accounted for as an indefinite-lived intangible asset. This means it's not automatically classified as cash or a current asset merely because it trades in liquid markets.
IAS 7 (Statement of Cash Flows) defines cash equivalents as investments that are highly liquid, readily convertible to known amounts of cash, and subject to insignificant risk of changes in value. Whether a digital asset qualifies depends on its specific contractual characteristics, not its label or market depth.
COSO Internal Control Framework requires that control activities occur at all levels of the entity and include appropriate segregation of duties, with a focus on controls over financial reporting. A material investment decision that affects balance sheet presentation falls squarely within the scope of financial reporting controls.
ISO 31000 (Risk Management) calls for risk assessment to consider consequences across multiple dimensions. A treasury decision that alters reported liquidity ratios creates financial reporting risk, covenant risk, and stakeholder perception risk. Finance must be involved in the approval process to assess these risks.
Lessons and Action Items for Your Team
Map your approval workflow to the actual decision points
Your crypto approval process should not end with "Is this asset permissible?" Add a mandatory step: "What will this transaction do to our financial statements?" Before any material crypto investment clears, Finance must document the proposed accounting treatment, the expected balance sheet classification, and the impact on key liquidity and leverage ratios.
Define "liquid" in your treasury policy with accounting precision
If your policy allows investment of "excess liquidity" or "liquid reserves," specify whether you mean economic liquidity or accounting classification. Better: require both. An asset that's economically liquid but classified as non-current creates exactly the problem this company encountered.
Require scenario modeling before board approval
Your board paper should include a table showing the balance sheet and income statement impact under three scenarios: purchase price, 30% decline, and 30% appreciation. This forces Treasury and Finance to align their assumptions before the transaction occurs. If you're operating under US GAAP post-ASU 2023-08, model the earnings volatility that fair-value accounting will introduce.
Treat accounting classification as a compliance control, not a reporting task
Compliance doesn't need to determine the accounting answer. It needs to verify that the accounting answer exists and has been documented before approving the transaction. Add a sign-off requirement: "Finance has confirmed the accounting treatment and financial statement impact."
Revisit approvals when the activity changes
If your company later decides to stake, lend, or collateralize previously approved crypto holdings, treat that as a new transaction requiring renewed approval. The token may not have changed, but the custody arrangement, liquidity profile, and accounting treatment likely have.
Test your controls with a walk-through
Take a proposed $10 million stablecoin investment through your current approval process. Does anyone ask whether it qualifies as a cash equivalent under IAS 7? Does anyone model what happens to your cash ratio if it doesn't? If the answer is no, your control framework has the same gap this company discovered.
The broader lesson: established companies don't lack controls when they enter crypto. They lack the connections between controls that different functions already apply. Treasury, Finance, Risk, and Compliance can all reach correct conclusions using their own frameworks while collectively approving a transaction that produces an unintended outcome. Your job as an auditor is to find those gaps before the financial statements do.
