Defi accounting: accounting for liquidity, lending, staking and on-chain rewards

Defi accounting for finance and accounting teams. How to account for DeFi activity — liquidity provision, lending and borrowing, staking and rewards — under IFRS and US GAAP, and how a sub-ledger keeps it reconcilable and auditable. This guide covers the treatment and how CryptaCount's crypto sub-ledger automates it.

General information on accounting treatment, not accounting or tax advice. Verify against the applicable standards (IFRS / US GAAP) and your auditor.

What makes DeFi hard to account for

DeFi accounting is the discipline of turning decentralised-finance activity into ordinary accounting records: recognising the assets and liabilities a protocol position creates, measuring them at each reporting date, classifying them correctly, and proving every figure back to the chain. The activity itself — supplying liquidity to an automated market maker, lending into a money market, borrowing against collateral, staking, or harvesting rewards — is economically familiar. What makes it hard is that none of it arrives as a tidy statement. It arrives as a stream of on-chain events that an accountant has to interpret before a single journal can be posted.

The first difficulty is that a single user action can fan out into several accounting events. Adding liquidity to a pool is, at once, the disposal of two tokens, the receipt of a liquidity-provider (LP) token that represents a claim on the pool, and the start of an ongoing entitlement to fees. A lending deposit may mint a receipt token whose balance grows as interest accrues, so the asset's quantity changes without any further transaction from the holder. These are not edge cases; they are the normal shape of the activity, and each one has to be decomposed deliberately rather than booked at face value.

The second difficulty is substance over form. The token a wallet receives is rarely the asset the entity economically holds. An LP token is a claim on a changing basket of two assets plus accumulated fees; a staking-derivative token is a claim on staked principal plus rewards; a debt receipt token is a liability that grows over time. Accounting for the wrapper at its market price, without looking through to what it represents, produces misleading statements. The work is to recognise the underlying rights and obligations, which is exactly the judgement a wallet balance alone does not make for you.

The third difficulty is completeness and reconciliation. Positions move across protocols and chains, rewards drip in continuously, and impermanent loss reshapes a pool's composition block by block. The on-book quantity of every asset must still equal the actual on-chain position at the cut-off, and a reader has to be able to trace each balance to a transaction hash. Doing that by hand across dozens of positions is where manual processes break down, which is the gap a crypto sub-ledger is built to close.

How the activity maps to the books

Accounting starts with three linked decisions: recognition (what event creates an accounting entry, and when), measurement (at what value it sits on the balance sheet), and classification (which line it belongs to). DeFi does not change these questions; it just makes the inputs harder to read. The principle is to map each economic event to the asset or liability it actually creates, then apply the entity's framework and policy consistently.

Liquidity provision

When an entity supplies liquidity, it typically disposes of the contributed tokens and recognises a new position — represented by the LP token — that is a claim on its share of the pool. Whether that disposal triggers a gain or loss depends on the framework and the carrying basis of the tokens given up. While the position is open, the entity earns a share of trading fees, and the pool's composition shifts as prices move, producing impermanent loss or gain that only crystallises on withdrawal. The accounting has to distinguish the initial exchange, the ongoing fee income, and the final settlement when liquidity is removed, rather than treating the LP token as a single static asset.

Lending and borrowing

Lending into a protocol creates a receivable — a right to recover the supplied asset plus accrued interest. Interest is income that accrues over time, often reflected as a rising receipt-token balance rather than a discrete payment. Borrowing creates a liability measured by what must be repaid, with the cost of borrowing recognised as an expense as it accrues. Collateral posted to secure a borrow generally remains the entity's asset but is encumbered, and that restriction is itself a disclosure point. Liquidation events — where collateral is seized to cover a position — are disposals that have to be captured promptly because they happen without the holder initiating a transaction.

Staking and rewards

Staking rewards and liquidity-mining incentives are generally recognised as income when the entity gains control of them, measured at fair value on the date of receipt. That receipt value also becomes the cost basis of the new tokens, which matters because a later disposal measures gain or loss against it. The recognition date can be genuinely difficult: some rewards are claimable but unclaimed, some auto-compound into a growing derivative balance, and some vest over time. The policy for when control is obtained has to be stated and applied the same way every period, not decided case by case.

Classification under IFRS and US GAAP

Classification flows from why the asset is held and what it is. Most tokens are not cash or conventional financial instruments, which generally pushes holdings toward presentation as intangible assets, or as inventory where the entity is a trader. Receivables and payables created by lending and borrowing may carry financial-instrument characteristics and are assessed on their own terms. Under IFRS, the look-through to underlying rights and the resulting measurement model follow from that classification. Under US GAAP, the treatment of in-scope crypto assets has moved toward fair value with changes recognised in net income, which changes where the value movements from a DeFi position land in the income statement. This is framework-level guidance; the specific treatment for any position should be confirmed against the current standards and professional advice.

Cost basis and gains and losses

Every disposal in a DeFi position — swapping into a pool, withdrawing liquidity, repaying a loan in a different asset, or selling a reward token — needs a cost basis to measure the gain or loss against. The basis of tokens acquired by purchase is what was paid; the basis of tokens received as rewards is their fair value on receipt; the basis of tokens withdrawn from a pool reflects what was contributed adjusted for the pool's movements. Getting this right depends on tracking lots consistently across the whole lifecycle of a position, not just at the moment of sale.

Because the same asset is acquired at many points and many prices, the entity needs a consistent cost-basis method — FIFO, weighted average, or another supported approach — applied uniformly. The method determines which lots a disposal consumes and therefore the size and timing of the resulting gain or loss. Switching methods between periods, or applying different methods to the same asset, makes results impossible to reproduce and is a frequent audit finding. The discipline is to fix the policy and let the engine apply it deterministically.

As an illustrative example, suppose an entity supplies two tokens worth 100,000 in total to a pool and receives an LP token. Over the period it earns fees recognised as income, and at withdrawal the underlying basket — reshaped by price movements — is worth 96,000. The shortfall of 4,000 (all figures illustrative) is the realised impermanent loss on settlement, separate from the fee income earned along the way. Booking only the net wallet change would obscure both the income and the loss; decomposing the position surfaces each correctly.

Revaluation and impairment considerations

At each reporting date, open DeFi positions have to be carried at the right value. Where the measurement basis is fair value, the entity needs a defensible price for the underlying assets at the measurement date, sourced consistently and documented — and for an LP or derivative token that means valuing what it represents, not just quoting a thin market for the wrapper. Where the basis is cost less impairment, the entity has to test for impairment and write down when value has fallen below carrying amount, which for volatile tokens can be a recurring event.

Impermanent loss complicates revaluation because a pool's composition drifts continuously: the quantities of each underlying token change as the protocol rebalances against trades. A period-end valuation therefore has to reflect the actual basket the position holds at the cut-off, not the basket originally contributed. Accrued-but-unclaimed rewards add another layer — they may represent value the entity controls and should reflect, depending on the recognition policy. Consistency across periods is what keeps these movements explicable rather than arbitrary.

Controls and audit trail

Auditable DeFi accounting needs an unbroken chain from each reported figure back to the on-chain event that produced it. The control questions are concrete: has every wallet and protocol position the entity holds been captured, or is there an unmapped position somewhere — the completeness assertion. Does the on-book quantity of each asset reconcile to the actual on-chain balance at the cut-off. Was each reward and fee recognised at a documented value on a documented date. Is the classification of each position supported by evidence of why it is held.

• completeness — all wallets and active positions ingested, with gaps flagged rather than silently missing;
• reconciliation — ledger quantities agreed to the chain at each measurement date, treating any difference as an early warning;
• valuation evidence — the price source and date recorded for every reward, fee and period-end mark;
• classification support — the business purpose of each position documented so its presentation can be defended;
• deterministic recomputation — the same inputs always reproducing the same balances, so an auditor can re-run the numbers.

Because blockchains are public, the reconciliation can be performed against an independent source of truth — the chain itself — which is a stronger position than many traditional asset classes enjoy. A difference between the ledger and the chain points straight at a missing position, an unrecorded reward or a misclassified event, and catching it at close keeps it out of the published statements.

How CryptaCount handles DeFi

CryptaCount is a crypto sub-ledger that sits in front of the general ledger and turns DeFi activity into accounting records. It ingests on-chain transactions and exchange activity across the entity's wallets, decomposes each event into its economic parts — the disposals, the new positions, the fee and reward income, the liabilities created by borrowing — and classifies them so they map to the right accounts. Rather than booking an LP or receipt token at a single misleading price, it is built to recognise the underlying rights the position represents.

On that ingested activity, CryptaCount computes cost basis and gains using a consistent method, recognises rewards at their value on receipt, applies a measurement basis at each close, and posts summarised period journal entries to the general ledger. Each GL balance decomposes back into the individual on-chain events that built it, so an auditor can select a figure, trace it to the sub-ledger detail, and confirm it against the public chain. The same engine can present the activity under IFRS or US GAAP and supports DAC8, CARF and MiCA reporting, so an accounting firm, fund administrator or web3 treasury holds the underlying events once and reports from them many ways.