Crypto accounting for Web3 companies

If your company holds its treasury on-chain, pays contributors in crypto, and operates across multiple chains, your books live where standard accounting tools can't see. CryptaCount is the crypto sub-ledger that turns all of it into clean, audit-ready accounting.

The Web3 finance reality

Web3-native companies — protocols, foundations, DAOs, and crypto startups — manage treasury in tokens and stablecoins, make payouts and grants on-chain, hold positions across many chains, and still have to produce financials your board, investors, and auditors will accept. Doing that in spreadsheets across block explorers doesn't hold together.

How CryptaCount handles it

• Multi-chain treasury. Ingest activity across every chain and wallet your company uses, into one set of books — powered by our own on-chain data infrastructure.
• Crypto payouts and grants. Track contributor payments, grants, and operational spend in crypto, classified correctly for accounting.
• Cost basis and gains. Apply your method to treasury movements and realize gains and losses without manual work.
• Clean entries to your ERP. Summarized journal entries post to Xero and Zoho today, with QuickBooks, NetSuite, and Sage on the roadmap, mapped to your chart of accounts.
• IFRS or US GAAP. Measurement handled per your policy, with the resulting entries on your books and a full audit trail.

Reporting your stakeholders accept

• Board and investor reporting — financials grounded in a complete transaction record
• Audit-ready — every figure traces from the GL line to the on-chain source
• DeFi and NFTs — protocol interactions and token activity captured, not dropped
• Fiat + crypto — your crypto books reconcile alongside the rest of your accounting

See the sub-ledger → · Compliance & reporting →

Why on-chain operations outgrow ordinary accounting

A Web3-native company runs its finances where standard accounting tools cannot see. Treasury sits in tokens and stablecoins across several chains, contributors and grantees are paid on-chain, protocol revenue arrives as token flows, and operational spend leaves through wallets rather than a bank. None of that shows up in a conventional ledger until someone manually reconstructs it from block explorers — a process that breaks down the moment activity scales past a handful of transactions a week. The gap is not a missing feature in the company's accounting system; it is that the system was never designed to read a blockchain. CryptaCount closes the gap by acting as the crypto sub-ledger that ingests every chain and wallet the company uses and turns the activity into clean, classified accounting. The engine is described on the crypto sub-ledger → page.

The pressure is sharper for a Web3 company than for a business that merely holds some crypto, because the crypto is the operation, not a side position. The board wants treasury reporting, investors want financials they can diligence, and auditors want a record that ties to the chain — all from activity that lives in tokens. A spreadsheet stitched together from explorers cannot carry that, and it certainly cannot reconcile against the rest of the company's fiat accounting.

The Web3 finance workflow CryptaCount enables

The platform is organised around the way an on-chain company actually operates. It ingests multi-chain treasury activity into one set of books, classifies crypto payouts and grants correctly, applies cost basis to treasury movements, and posts summarized journal entries to the company's ERP mapped to its chart of accounts. The finance team works from a single reconciled record instead of chasing wallets across explorers, and the crypto books reconcile alongside the fiat ones rather than living in a parallel universe.

• Consolidate treasury — activity across every chain and wallet ingested into one set of books
• Classify on-chain spend — contributor payouts, grants and operational spend recognised correctly for accounting
• Apply cost basis — gains and losses on treasury movements realised without manual work
• Post to the ERP — summarized journal entries mapped to your chart of accounts
• Measure per policy — IFRS or US GAAP measurement applied to treasury holdings
• Reconcile fiat and crypto — the crypto books tie out alongside the rest of the accounting

Because every posted line drills back to its on-chain source, the finance team can answer a board or auditor question by opening the transaction rather than reconstructing it from an explorer. How the postings are built is set out on the journal entries → page.

Treasury, payroll and grants as accounting events

On-chain operations create accounting events that ordinary tools never see, and getting them right is what makes the financials defensible. Paying a contributor in tokens is a compensation expense measured at value on the date of payment; a grant is an outflow that needs its own classification; a stablecoin payment for a service is an operating expense like any other, only settled on-chain. Treasury movements between the company's own wallets must net out rather than appearing as disposals, while a genuine disposal of a token for another asset realises a gain or loss that has to hit the income statement. CryptaCount classifies these events for accounting so the company's books reflect the economic substance of what happened on-chain, not just a string of raw transfers.

Measurement under IFRS or US GAAP

A Web3 company's auditors and investors expect the treasury to be measured under a stated policy, not marked by feel. CryptaCount applies measurement under IFRS or US GAAP according to the company's policy and posts the resulting entries to the books, so period-end positions rest on a consistent basis that can be explained and tested. Because the measurement is applied in the sub-ledger and recorded, the company can show how a treasury figure was arrived at rather than defending an ad-hoc mark. The IFRS treatment is described on the IFRS crypto accounting → page.

Reporting obligations a Web3 company faces

On-chain businesses are squarely in the path of the new crypto reporting regimes, and a clean data foundation is the only practical way to meet them. Frameworks such as the OECD's CARF, the EU's DAC8 exchange-of-information rules, and the MiCA regime in Europe assume a complete, classified, point-in-time record of crypto activity tied to identifiable venues and counterparties. Because CryptaCount already holds that record for the company's treasury and operations, the finance team can produce the underlying figures and reconciliations rather than scrambling when an obligation crystallises. The same record underpins board and investor reporting, so one reconciled source serves both the regulator and the cap table — see crypto compliance reporting →.

Closing the month when the company runs on-chain

For a Web3 company, a believable month-end close is what makes everything downstream possible — the board pack, the investor update, the runway model, the audit. The trouble is that an on-chain month does not close itself: treasury has moved across chains, contributors have been paid, grants have gone out, protocol revenue has arrived, and gas has been spent on hundreds of transactions. CryptaCount gives the finance team a repeatable sequence to bring that to a clean stop. It ingests the period's activity from every chain and wallet, reconciles the on-chain balances so the starting point is trustworthy, and surfaces the transactions that need a human decision — an unfamiliar counterparty, a token it has not seen, or a transfer that might be an internal treasury move rather than a disposal. The team resolves those exceptions, confirms the cost-basis results, and posts summarized journal entries to the ERP. Because the postings are summarized and mapped to the chart of accounts, the review at the ERP end is fast: a handful of lines per account, each backed by the full transaction list one click away. Self-transfers net to zero rather than inflating gains, the period locks once closed, and the same controlled process repeats next month. The outcome is that crypto stops being the line item nobody can explain at the board meeting and becomes just another part of the close — reconciled, classified, and tied to the chain. That predictability is what lets a finance team of a few people support a company whose entire treasury and operations live on-chain.

Common pitfalls in Web3 company accounting

• Reconstructing from explorers — manual explorer work does not scale and leaves no audit trail; direct ingestion preserves one
• Treasury transfers booked as sales — moves between the company's own wallets must net out, not create phantom gains
• Unclassified payouts — contributor payments and grants left as raw transfers misstate expense and compensation
• Crypto books in a silo — treasury accounting that never reconciles to the fiat ledger cannot support consolidated financials
• Ad-hoc valuation — marking treasury by feel rather than a stated policy fails audit and investor diligence
• No on-chain trail at the GL — figures that cannot drill back to a transaction hash cannot be defended to an auditor

How CryptaCount helps Web3 companies

For a Web3 company, CryptaCount turns on-chain treasury and operations into accounting the board, investors and auditors will accept. It consolidates multi-chain activity into one set of books, classifies payouts and grants correctly, applies cost basis and the company's IFRS or US GAAP measurement policy, and posts summarized journal entries to the ERP with every figure tracing back to its on-chain source. The finance team stops reconstructing wallets from explorers and starts closing crypto the way it closes everything else, with the crypto books reconciling alongside the fiat ones. Explore the crypto sub-ledger → and journal entries → to see the engine in detail.

How do we account for paying contributors in tokens?

Contributor payouts are classified as a compensation expense measured at value on the date of payment, with the underlying transfer captured and tied to its on-chain source. Grants and operational spend are classified to their own accounts, so the income statement reflects what the company actually spent rather than a row of undifferentiated transfers.

Does our crypto treasury reconcile with our fiat books?

Yes. The sub-ledger posts summarized journal entries into the same ERP and chart of accounts as the rest of your accounting, so the crypto books are part of one reconciled set rather than a separate silo. That is what makes consolidated, board-ready financials possible.

Can we report treasury across many chains in one place?

Yes. Activity across every chain and wallet the company uses is ingested into a single set of books, so the treasury position is consolidated rather than scattered across explorers. Each figure still drills back to the specific chain and transaction it came from.

Will our auditors and investors accept the output?

The output is grounded in a complete, traceable record: every figure traces from the GL line back to its on-chain source, entries are recorded with integrity hashing, and measurement follows your stated IFRS or US GAAP policy. That is the evidence base an auditor tests and an investor diligences, rather than a spreadsheet they have to take on trust.

Crypto on a web3 company's books

A web3 company often holds a treasury, pays contributors in crypto, and earns protocol revenue on-chain — all of which has to land on the books correctly and survive an audit. A sub-ledger gives finance one reconciled source for that activity, with consistent cost basis, traceable gains, and journal entries mapped to the chart of accounts. CryptaCount ingests on-chain and exchange activity and posts period summaries to the general ledger, supporting IFRS and US GAAP reporting. See the sub-ledger and journal entries.