Crypto compliance and reporting, audit-ready
CryptaCount turns your crypto sub-ledger into financials that map to the standards you already report under — IFRS and US-GAAP — and supports the record-keeping behind MiCA, DAC8, and CARF. Every figure traces back to a transaction, so reporting and audit start from evidence, not reconstruction.
The problem with crypto and the standards
Crypto sits awkwardly across accounting frameworks. The same holding can be an intangible asset under one standard and measured at fair value under another; income from staking, mining, and rewards needs classifying; and the regulatory perimeter keeps moving. Doing this in spreadsheets means re-deriving treatment every reporting period and hoping it holds up at audit.
CryptaCount builds the treatment into the ledger, so the reporting outputs are consistent, repeatable, and tied to source data.
IFRS
Account for crypto under existing IFRS — typically as intangible assets (IAS 38) or, for broker-traders, inventory (IAS 2) — with cost or revaluation treatment carried correctly through the sub-ledger into your financial statements.
US-GAAP, including FASB ASU 2023-08
Apply FASB ASU 2023-08 — fair-value measurement of in-scope crypto assets, with changes recognised in net income — alongside the disclosures it requires. CryptaCount tracks fair value and the underlying cost basis so both the measurement and the disclosure are supported.
MiCA
For clients operating under the EU's Markets in Crypto-Assets regime, CryptaCount provides the transaction records, reconciliations, and reporting that support MiCA's financial record-keeping obligations.
DAC8 & CARF
The EU's DAC8 and the OECD's CARF introduce crypto-asset reporting obligations built on shared transaction data. CryptaCount maintains that data at the level these frameworks expect, so the reporting can be produced from one clean source.
Audit trail
An immutable, hashed audit trail underpins all of it — every balance traceable to its postings and on-chain origin, which is what turns "trust us" into evidence an auditor can test.
From sub-ledger to disclosure
The reporting doesn't sit apart from the books. It's generated from the same sub-ledger that records every transaction and feeds your GL/ERP — so the financial statements, gain/loss, and regulatory reports all reconcile to the same underlying data. One source, consistent outputs.
Why CryptaCount
- Accounting-first, built by accountants. Designed by an FCCA-qualified team with 10+ years in IFRS and US-GAAP consolidation — the standards aren't an afterthought.
- Traceable by design. Every reported number ties back through balanced journals to an on-chain transaction.
- Keeps up with the perimeter. Coverage tracks evolving frameworks (FASB ASU 2023-08, MiCA, DAC8/CARF) rather than freezing at one moment in time.
- Hosted securely. Run on SOC 2 Type II & ISO 27001-certified infrastructure (Google Cloud).
FAQ
Yes. It carries the correct treatment through the sub-ledger for IFRS (IAS 38 / IAS 2) and US-GAAP, including FASB ASU 2023-08 fair-value measurement, so financials map to whichever standard each entity reports under.
It is the US-GAAP update requiring certain crypto assets to be measured at fair value, with changes recognised in net income, plus related disclosures. CryptaCount tracks both fair value and cost basis to support the measurement and the disclosure.
It supports compliance by providing the transaction records, reconciliations, and reporting outputs those frameworks rely on. Compliance itself depends on your filings and obligations; CryptaCount supplies the underlying data and audit trail.
Yes. The immutable audit trail and transaction-level evidence let auditors test crypto balances back to source, the same way they would any other account.
Yes. Reports are generated from the same sub-ledger that posts to your GL, so financials, gain/loss, and regulatory reports all reconcile to one source.