Crypto Lending & Borrowing Accounting: Receivable, Payable, Collateral

Two instincts trip up the accounting for crypto loans, and they pull in opposite directions. Lending crypto is not the same as selling it, so booking every transfer to a protocol as a disposal overstates activity. Borrowing crypto is not income, so treating an inflow of borrowed tokens as a gain is plainly wrong. What is left, once both instincts are set aside, is a set of harder questions: is the lending transfer a disposal or a continuing interest that leaves a receivable; what obligation and collateral does the borrower carry; how is interest paid in kind recognised; and how does liquidation risk feed into measurement. This article is that recognition map, kept distinct from the treasury-yield framing of the same positions, and hedged because each leg is an auditor judgement.

The short version

• Lending is not a disposal by default. The question is whether the transfer is a disposal (derecognise the asset, recognise any gain or loss) or a continuing interest that leaves a receivable — which turns on whether risks and rewards or control pass, and on the framework's derecognition rules.
• The borrower generally recognises an obligation to return the asset (a payable or liability) and accounts for the received asset. Borrowed crypto is not income.
• Collateral generally stays the poster's asset (disclosed as encumbered) unless control or risks have transferred — it is not a case of "whoever holds it owns it".
• Interest in kind is recognised as income earned or expense incurred, measured by the crypto's value, with the received interest then a separate asset (two layers).
• Liquidation risk affects measurement, impairment, and disclosure, and a liquidation is itself a derecognition or loss event.
• This is the recognition lens, distinct from the treasury-yield lens on the same activity. It is a fact-specific auditor judgement, not accounting advice.

Is lending a disposal?

The central question. Whether transferring crypto to a borrower/protocol is a disposal (derecognize, recognize gain/loss) or a continuing-interest position (derecognize but recognize a receivable, or retain recognition) depends on whether risks-and-rewards/control transfer and the framework's derecognition rules. Every-transfer-is-a-sale and it's-a-non-event are both wrong by default — a fact-specific auditor judgement (and distinct from internal transfer vs disposal).

The borrower side

A borrower receiving crypto it must return generally recognizes an obligation (a payable/liability to return the asset) and accounts for the received asset and any onward use under the applicable model; the liability's measurement is a framework question. Borrowed crypto is not income. Recognition/measurement is fact-specific, auditor-confirmed.

Collateral

Turns on control and the arrangement — an auditor judgement, not "whoever holds it owns it".

Interest in kind

Interest in kind: income as earned / expense as incurred, measured by the value of the crypto interest, with the received interest then a separate crypto asset (see crypto revenue and expense accounts). Two layers (income/expense recognition + subsequent asset accounting), both auditor-confirmed.

Liquidation risk

Collateralized crypto lending carries liquidation risk — collateral falling past a threshold can be liquidated. That risk affects measurement, impairment/expected-loss on a receivable, and disclosure; a liquidation event is itself a derecognition/loss event to account for when it occurs. Fact-specific auditor judgement — distinct from simply tracking a yield figure (treasury-yield is the other lens).

DeFi protocol-specific lending patterns

The recognition analysis differs depending on whether lending occurs through a centralised counterparty or a DeFi protocol, because the control and risk profile of each is different.

Overcollateralised DeFi lending (Aave, Compound, MakerDAO). In overcollateralised protocols, a borrower posts collateral (say 150 ETH worth of collateral for 100 ETH worth of borrowing) and receives the borrowed asset. The protocol holds the collateral via smart contract. For the lender (liquidity provider), the deposit into the protocol pool is the key event — the lender typically receives a receipt token (aTokens on Aave, cTokens on Compound) that represents its claim on the pool. Whether this is a disposal of the deposited asset or a continuing interest depends on how risks and rewards of the underlying asset are transferred to the pool. The receipt token's accounting — as a new asset, at what value — is itself a separate question. For the borrower, the collateral generally remains the borrower's asset (encumbered), and the borrowed asset creates a payable at its current value.

Flash loans. A flash loan is borrowed and repaid within a single transaction block — it has no duration. From an accounting perspective, the question of whether a flash loan creates a transient liability is largely academic for most entities; the more relevant question is whether using a flash loan as part of an arbitrage transaction (which does create income/loss) is properly recorded as a composite event rather than individual legs. The net economic result of the flash loan's use should be recorded, with the loan itself treated as a financing mechanism rather than a separate income/expense item.

Undercollateralised lending (Goldfinch, Maple Finance, TrueFi). In these protocols, borrowers receive loans with partial or no on-chain collateral, relying on off-chain creditworthiness assessments. For the lender, this raises expected-credit-loss (ECL) considerations analogous to traditional lending: the receivable should carry an ECL provision under IFRS 9 (or equivalent US GAAP current expected credit loss — CECL). The in-kind nature of the assets and the novel counterparty arrangements make the ECL estimation judgemental and fact-specific.

Liquid staking as implicit lending. Depositing assets into a liquid staking protocol (Lido, Rocket Pool) shares some structural features with lending — the depositor relinquishes direct control of the asset and receives a receipt token — but is generally treated under the staking-rewards framework rather than the lending framework because the primary economic substance is earning staking rewards on the protocol's behalf, not lending capital for a fixed return. The distinction matters for how interest income is recognised vs staking reward income (see liquid staking token accounting).

Common accounting errors in crypto lending

Treating a lending protocol deposit as a simple asset transfer with no derecognition question. When an entity deposits USDC into Aave, this is not a trivial ledger entry equivalent to moving cash between bank accounts. The derecognition and receivable assessment must be documented.

Failing to record interest income as it accrues. If a lender receives aTokens that automatically accrue interest, the interest is earned continuously — it is not an income event only when the position is closed. Under most frameworks, interest accrues over the period regardless of when it is collected.

Ignoring the value change of the collateral when assessing impairment on a receivable. A lender holding a crypto-denominated receivable should consider whether the borrower's collateral value has declined materially, which affects the expected loss provision on the receivable, even if no default has occurred.

Practical guidance

1. Assess derecognition first — disposal vs continuing-interest/receivable.
2. Borrower recognizes a return obligation — borrowed crypto is not income.
3. Collateral generally stays the poster's (encumbrance disclosed) absent control transfer.
4. Recognize interest in kind (income earned / expense incurred) + the subsequent asset.
5. Reflect liquidation risk in measurement/impairment/disclosure; account liquidation events.
6. Confirm each leg with your auditor — fact-specific; not accounting advice.

Choosing and configuring a tool

A lending position has more state than a simple holding — a transfer out, a receipt token, accruing interest, posted collateral, a possible liquidation — so the tool has to model each without flattening them into one entry. Tools such as Cryptio and Bitwave can record these flows against a configured model; before relying on one, confirm it can:

• treat a deposit into a protocol as a position requiring a derecognition or receivable assessment, not as a trivial transfer between accounts, and capture any receipt token (aTokens, cTokens) as its own asset;
• accrue interest in kind as it is earned rather than only when the position is closed, and book the received interest as a subsequent asset;
• hold collateral on the poster's balance sheet with an encumbrance flag, rather than moving it to whoever custodies it;
• record a liquidation as a derecognition or loss event when it occurs, and surface collateral value changes that feed an expected-credit-loss assessment on a receivable.

The tool records the events; the derecognition conclusion, the receivable or payable, the collateral treatment, and the interest recognition remain auditor judgements.

How Wag3s fits in

Wag3s Ledger records lending and borrowing transfers, collateral positions with their encumbrance, interest in kind, and liquidation events, with an audit trail behind each. The derecognition assessment, the receivable or payable, the collateral treatment, and the interest recognition stay with the entity's auditor — Ledger supplies the structured, sourced record and is built to support that review rather than make the calls itself. See the Ledger product page.

Further reading

• DeFi Lending Yield Treasury
• Internal Transfer vs Disposal (Crypto)
• Crypto Revenue and Expense Accounts
• DeFi Position Chart of Accounts
• Crypto Asset Account Classification
• Liquid Staking Token Accounting

Sources

• IFRS — IFRS 9 Financial Instruments: derecognition principles based on the transfer of risks and rewards and control, and the expected-credit-loss model relevant to a receivable from a borrower, including in undercollateralised lending.
• IFRS — IAS 38 Intangible Assets, and FASB — ASU 2023-08: the accounting for the crypto asset lent, received as interest, or posted as collateral.
• IRS — Digital assets hub: the US framework for digital-asset transactions, including interest received in kind. The derecognition analysis and the tax treatment are determined separately, the latter with a tax adviser.