Accounting Standards and Financial Reporting for Crypto-Holding Businesses

So your company holds bitcoin on the balance sheet. The bookkeeper logs the purchase without drama. Then year-end arrives, and someone has to put a number on that holding — and the number the standards hand back is rarely the one the business owner had in mind.

Here's the awkward truth about crypto accounting: the assets are new, but the rulebook was drafted for a different century of financial instruments. Most of it holds up. Some of it produces genuinely strange results. What follows is how the major frameworks actually treat a crypto balance, where the treatment bites, and what you need on file before an auditor comes knocking.

Why crypto breaks the usual accounting models

Accounting standards were built around three tidy buckets: cash, financial instruments, inventory. Crypto refuses to sit in any of them properly.

It isn't legal tender, so cash is out. It isn't a contract with a counterparty — which is the assumption baked into most financial instrument rules — so that bucket is out too. And it behaves nothing like stock sitting in a warehouse. No shelves involved.

Which leaves accountants doing what accountants do when the rules don't quite fit: making judgment calls, and documenting them carefully enough to survive review. Under IFRS, most companies land on intangible asset treatment. Under US GAAP, the historical default was an indefinite-lived intangible. Both routes share the same sting — cost less impairment. If the price climbs? The balance sheet doesn't care. It stays at what you paid.

The lopsided income statement

Prices fall, you book an impairment loss. Prices recover later? Under the older rules, that loss doesn't reverse. A company that bought early and watched the price multiply still carries the holding at original cost.

The result is a gap between what management sees on the treasury dashboard and what the accounts report. Two numbers, same asset, and the distance between them widens with every swing in the market.

Running a reporting cycle against the standards

In practice, applying any framework follows a sequence: pick the standards, classify and measure the transactions, pull the disclosures together, then review before the statements go out. For a typical cycle it looks like this.

1. Identify the applicable framework and any sector-specific requirements — IFRS as adopted in the relevant jurisdiction, US GAAP for an SEC registrant, or local GAAP for a private entity — and confirm the reporting period and presentation currency.
2. Map the entity's transaction types to the standards that govern recognition and measurement, such as revenue (IFRS 15 or ASC 606), leases (IFRS 16 or ASC 842) and financial instruments (IFRS 9 or ASC 326).
3. Collect and reconcile source data — ledger balances, contracts, bank confirmations and inventory counts — and document the judgements applied where a standard permits accounting policy choice or requires estimation.
4. Draft the primary statements (statement of financial position, statement of profit or loss and other comprehensive income, statement of cash flows, and statement of changes in equity) and tie each line back to the reconciled ledger.
5. Prepare the notes, including the accounting policy note, disaggregated balances and the disclosures each standard mandates, checking that every figure cross-references to a line in the primary statements.
6. Review the draft against the disclosure checklist for the chosen framework, obtain sign-off from management or the audit committee, and retain the working papers that support each material balance.

The order of the steps matters far less than the trail they leave. Every figure in the accounts should be traceable back to a source document — that's the whole game. Miss it and the audit turns into archaeology.

One more thing. Change your framework or your policy, and you disclose that change in the period it takes effect. Quietly retrofitting prior figures is how comparatives stop meaning anything. And where a standard offers more than one acceptable treatment, pick one, write down why, then apply it every period without exception.

How the main frameworks treat a crypto balance

Two frameworks dominate global reporting: IFRS, used across most of Europe, Asia, and many emerging markets, and US GAAP. There's a third path for businesses that hold crypto purely to sell it in the ordinary course. Here's how each approach lands.

None of these comes free. Fair value gives you the most current picture — and dumps every price swing straight into reported earnings. Cost less impairment is calmer, but it understates a holding that has gained. Inventory treatment makes sense for a trading desk; applied to a software company's treasury reserve, it reads oddly. Which one fits depends on why the business holds the asset in the first place.

A recent shift in the US rules

US GAAP has moved. ASU 2023-08 requires in-scope companies to measure crypto assets at fair value each reporting period, with the changes running through net income. The old asymmetry? Gone, at least for assets that qualify.

Scope limits to check first

Qualification is the catch. The asset has to be fungible, secured by cryptography, and not represent a contract with another party. A wrapped token, or one carrying a redemption right, may fall outside the definition. Check each holding against the criteria — don't assume the whole wallet qualifies just because the exchange lists it.

IFRS hasn't matched this with a crypto-specific standard. Companies reporting under IFRS still choose between the intangible asset route and the fair value option for intangibles — the latter exists, but it demands an active market and consistent, unwavering application.

Turning wallet activity into a clean audit trail

Financial reporting begins long before the year-end journal entry — and the hardest part of crypto bookkeeping isn't the double entry. It's proving where each unit came from, what it cost, and where it went. Auditors will ask for that chain. A screenshot of a block explorer won't cut it.

Build the trail on purpose. What tends to work:

• Record every acquisition with its date, fiat value at the time, and the source wallet or exchange.
• Keep a cost basis schedule per lot, because disposals need a consistent method such as FIFO or specific identification.
• Reconcile on-chain balances to the ledger every month, not once a year.
• Document impairment tests with a dated price source and the reasoning behind each write-down.
• Separate tokens that qualify for fair value treatment from those that do not, and label them in the ledger.

Do this properly and the auditor's questions mostly answer themselves — the evidence already exists when the request lands. Fair value also stops being a research project. You pull a price. You don't reconstruct history from a pile of exchange emails.

What the disclosures need to say

The numbers alone don't make a set of financial statements. The notes are doing half the work. A reader needs to know which standard you applied, why you chose that treatment, and how exposed the reported figures are to a price move.

In practice that means describing the accounting policy in plain terms, stating the carrying amount, and explaining any impairment booked during the period. If fair value applies, say which valuation method and which market source. Where holdings are material, a sensitivity note showing the impact of a price shift earns its place even when it isn't strictly required.

This is the spot where crypto reporting diverges most sharply from conventional asset reporting. A cost figure tells a reader almost nothing about an asset whose price moves daily. The notes are what make the position legible.

Where judgment calls tend to go wrong

Three failures repeat. First, inconsistent cost basis — the same token bought across several exchanges, part of it sold, and a different method applied in each period. Second, missing impairment tests: teams test once, then forget the asset exists until the next audit lands.

Third, and the costliest, is the classification question. A token that looks like a plain holding might carry a redemption right, which changes everything. A staking reward may raise a revenue recognition question rather than an asset measurement one. Get the classification wrong at the start and every later entry is built on sand.

None of this is beyond a competent bookkeeping team. But the accounting question has to be settled before the transaction goes in the ledger — not after the trial balance is already closed.

Setting a workable policy for your business

The single most useful thing a crypto-holding business can do is write the policy down. One short internal document — classification, measurement, cost basis method, impairment testing frequency, disclosure content — and most of the year-end argument evaporates before it starts.

Then revisit it. Holdings change character. New standards apply. The business starts accepting crypto as payment instead of just holding it as a reserve. Payment flows drag in revenue recognition and foreign exchange questions that a pure holding policy was never built to answer.

The standards will keep shifting as rulemakers catch up with the asset class. A documented, consistent approach gives you something solid to adjust from — and gives your auditor a clear basis for the opinion. More value in that than in any single measurement choice.