Your treasury team wants to diversify reserves into crypto. They've mapped out the exchange, screened the wallets, and confirmed the custodian passes sanctions checks. Compliance has signed off. The board approves. Everyone agrees the asset is liquid.
Then your CFO asks: "Where does this sit on the balance sheet?"
That's when you discover treasury's definition of "liquid" and finance's definition don't match.
Understanding the Source of the Questions
These questions arise from real conversations between compliance, treasury, and finance teams at companies exploring crypto holdings. They highlight a common issue: compliance can approve a transaction that leads to unexpected financial reporting outcomes. The problem isn't weak controls but rather different functions measuring different aspects of the same asset.
Q1: We Approved Bitcoin as a Reserve Asset. Why Is Our CFO Saying It Hurt Our Liquidity Ratios?
Market liquidity and accounting liquidity are not the same.
Bitcoin trades continuously in deep markets, making it easy to sell quickly. Treasury sees this and calls it liquid.
However, under IFRS, cryptocurrency may be classified as an intangible asset under IAS 38, not cash. If it doesn't qualify as a current asset, it sits below the line on your balance sheet.
Here's an example. You start with $100 million in cash, $100 million in other current assets, and $100 million in current liabilities. Your current ratio is 2.0x.
You move $30 million from cash to Bitcoin. Economically, you've swapped one asset for another. But if Bitcoin is classified as non-current, your current assets drop from $200 million to $170 million. Your current ratio falls from 2.0x to 1.7x, and your cash ratio drops from 1.0x to 0.7x.
You haven't lost economic value, but your balance sheet now shows weaker liquidity. That affects covenant compliance, credit analysis, and internal treasury limits.
The issue arises when treasury classifies an asset as liquid before finance determines whether the financial statements will do the same. Compliance needs to ensure both functions are aligned before the transaction is approved.
Q2: Can't We Just Wait and See How the Accountants Classify It After We Buy?
You can, but by then you've already changed your capital structure.
If the accounting treatment creates a covenant breach or forces you to reclassify your liquidity position in the next board deck, you're managing a problem instead of preventing one.
The approval framework should establish the accounting treatment in advance, not discover it during the next quarterly close. This means finance reviews the transaction before execution, not after.
Q3: Our Investment Is Up 20%. Why Did We Book an Impairment Loss?
Accounting rules determine when and where performance appears in your financial statements, not just whether the asset appreciated.
Tesla's Bitcoin holding illustrates this. In 2021, Tesla invested $1.5 billion in Bitcoin as part of a policy to diversify excess cash. Under the U.S. GAAP applicable at the time, Bitcoin was treated as an indefinite-lived intangible asset. Declines in market price triggered impairment charges, but increases in market price after an impairment couldn't flow back through earnings unless the asset was sold.
During 2021, Tesla recognized approximately $101 million of Bitcoin impairment losses. At year-end, its remaining Bitcoin had a carrying value of approximately $1.26 billion and a fair market value of approximately $1.99 billion.
Treasury saw an investment that had appreciated. The income statement showed impairment.
U.S. accounting has since changed. FASB's ASU 2023-08 now requires qualifying crypto assets to be measured at fair value, with changes recognized in net income. That removes the old asymmetry but introduces earnings volatility instead.
The point isn't which accounting model is better. It's that if your board paper argues crypto will improve returns on excess liquidity, someone should already know how those returns and losses will appear in reported performance.
Q4: We're Moving Cash into a Stablecoin Pegged to the Dollar. That's Still Cash, Right?
Not necessarily.
A stablecoin designed to maintain a one-dollar market price looks like cash. But under IAS 7, a cash equivalent must be highly liquid, readily convertible into a known amount of cash, and subject to an insignificant risk of changes in value.
Whether a particular stablecoin satisfies those definitions depends on its specific characteristics and contractual rights. "Stablecoin" isn't itself an accounting classification.
This can create two different pictures inside the same company. Treasury's dashboard shows $100 million of liquidity. The financial statements show $50 million of cash and cash equivalents plus $50 million of something else.
Both functions may be applying coherent methodologies, but management can still make a poor decision if nobody reconciles them before the transaction.
This is why due diligence on the stablecoin issuer isn't enough. Compliance can approve the issuer without answering what the institution actually owns from an accounting perspective.
Q5: We Already Approved ETH as a Holding. Why Do We Need a New Approval to Stake It?
Approving the asset is different from approving the activity.
Your compliance team approved ETH. Finance determined the accounting treatment. Risk set a position limit. Treasury acquired the token.
Six months later, treasury proposes staking the ETH to generate yield. The token hasn't changed, but the activity and risk profile have.
Staking can introduce validator or protocol exposure, liquidity restrictions, slashing risk, different custody arrangements, new flows of staking rewards, and additional accounting questions. A decision that sounds modest ("we already own it, let's earn a return") can alter the risk and control profile of an already approved asset.
The same problem appears when a stablecoin is deployed into a lending protocol or crypto is pledged as collateral.
Crypto approvals shouldn't attach only to a list of approved tokens. They need to attach to the combination of asset, structure, and activity.
Q6: What Should Compliance Actually Check Before Approving a Crypto Transaction?
For a material crypto transaction, the approval process should establish in advance:
- The legal and regulatory classification of the activity
- The proposed accounting treatment
- The balance sheet and earnings consequences under realistic upside and downside scenarios
- The effect on internal and contractual liquidity metrics
- The valuation methodology and pricing sources
- The financial reporting controls and reconciliations that will be required
- Whether later changes in use (staking, lending, collateralization) trigger renewed approval
Compliance doesn't need to make the accounting judgment. It needs to ensure the accounting answer exists before the transaction occurs.
Where to Go for More
If you're building a crypto approval framework, start by mapping where treasury, finance, risk, and compliance each measure the same transaction differently. The control gaps usually aren't inside functions. They're between them.
Before compliance gives the green light to a material crypto transaction, ask one additional question: If we approve this today, what will our financial statements say tomorrow?
The answer may change the decision.
