Accounting risk

Reading depth

Each view includes the earlier layers; the complete engineer or auditor page is shown by default.

BeginnerCore purpose and mental modelPractitionerAdds mechanisms and economicsEngineer or auditorAdds state and verification

Dependency check

Advanced detail assumes prerequisite knowledge

Before using practitioner mechanisms or engineer and auditor checks, review any unfamiliar dependency. These paths come from canonical depends_on relationships; Web3 Academy does not track completed lessons.

Review 5 dependencies

• AssetRequired through Asset versus claim

  1. Accounting risk
  2. Net asset value
  3. Asset versus claim
  4. Asset

• ClaimRequired through Asset versus claim

  1. Accounting risk
  2. Net asset value
  3. Asset versus claim
  4. Claim

• TokenRequired through Asset versus claim

  1. Accounting risk
  2. Net asset value
  3. Asset versus claim
  4. Token

• Asset versus claimRequired through Net asset value

  1. Accounting risk
  2. Net asset value
  3. Asset versus claim

• Net asset valueDirect prerequisite

  1. Accounting risk
  2. Net asset value

Accounting risk is the possibility that balances, shares, debts, fees, profits, losses, or valuations no longer represent the system's actual assets and obligations.

Category: RiskWarning cross category cue

System record

Start with the economic purpose, participants, resources, and entitlements before studying implementation detail.

Why it exists

DeFi repeatedly converts between assets and claims, so small recognition, rounding, timing, or reconciliation errors can transfer value and compound across deposits, withdrawals, and integrations.

Traditional-finance analogy

Financial-reporting, valuation, and reconciliation risk is the closest comparison recorded for this concept.

Where the analogy stops

• Smart-contract accounting often determines executable transfers immediately, so an error can become an on-chain extraction path rather than only a misstated report.
• Token donations, rebases, callbacks, atomic loans, unusual decimals, and cross-protocol claims create state changes absent from a closed ledger.

Main actors

• ActorDepositor, borrower, shareholder, or fee payer
• ActorVault, pool, token, or accounting contract
• ActorStrategy, oracle, keeper, or reporter
• ActorAuditor, governance, fee recipient, or loss absorber

Assets and claims

Assets — controlled or transformed resources

Assets are resources the mechanism moves, holds, values, or transforms.

• AssetControlled assets, receivables, collateral, reserves, and strategy positions

Claims — entitlements and corresponding dependencies

Claims are rights to value, repayment, redemption, control, or another party's performance; each depends on an obligation or system that must honor it.

• ClaimShares, debts, fees, queued operations, and redemption entitlements

Accounting risk is the possibility that the numbers used to move value no longer represent the system’s actual assets, obligations, and user entitlements.

Why it exists

DeFi repeatedly converts assets into claims and back again. Deposits, withdrawals, borrows, repayments, interest, fees, rewards, losses, donations, rebases, queues, and cross-chain positions must be recognized at explicit times and units. A small rounding or recognition error can compound or be deliberately repeated.

Traditional-finance analogy

Financial reporting, valuation, and reconciliation risk are useful analogies. In a smart contract, accounting often controls an immediate asset transfer. An error is therefore not merely a misstated report; it can create a permissionless extraction path before a later close or audit.

Actors, assets, and claims

Table: Actors, assets, and claims

Ledger side	Examples
Recognized assets	Cash, collateral, receivables, reserves, deployed positions
Recognized liabilities	Debt, fees, pending withdrawals, contingent obligations
User claims	Shares, balances, lender receipts, redemption entitlements
Accounting inputs	Prices, timestamps, exchange rates, decimals, reports, actual balance changes

Mechanism, equation, and flows

reconciliationDifference = recognizedAssets
                        - recognizedLiabilities
                        - attributableNetValue

The target difference and tolerated rounding must be defined by the accounting model. A zero difference is not meaningful if assets or liabilities were omitted or valued under inconsistent units and timestamps.

1. A state transition observes balances and recognized positions.
2. It converts units and calculates shares, debt, fees, profit, or loss.
3. It transfers assets and records new claims or liabilities.
4. Later events update value, liquidity, impairment, and pending operations.
5. Reconciliation identifies whether every unit remains attributable exactly once.

Capital flow is the actual balance change. Claim flow is mint, burn, debt, or queue accounting. Return flow records named income and fees without confusing deposits or token donations with profit. Risk flow transfers any mismatch to users who mint, redeem, borrow, repay, or remain in the system at the wrong value.

State and loss allocation

Table: State and loss allocation

Event	Correct state change	Example failure
Deposit or withdrawal	Claims change by contributed or redeemed net value under stated rounding	First user or donation captures another user’s value
Profit, loss, or fee	NAV and ownership change once at the recognition time	Value or liability is double counted or omitted
Rebase or unusual transfer	Actual controlled balance and claim rules reconcile	Nominal amount is recorded although less or more arrived

Accounting creates no external return. It allocates income from borrowers, traders, networks, issuers, or incentives and allocates costs and losses. A mismatch transfers value between users, fee recipients, reserves, or claim classes rather than creating value.

Protocol and engineering context

OpenZeppelin’s ERC-4626 guide demonstrates how share price, rounding, donations, and inflation attacks interact in tokenized vaults. The mitigation is specific to an implementation and parameterization; ERC-4626 conformance alone does not certify accounting safety. The guide was reviewed 2026-08-10.

An engineer or auditor should specify recognition time, price source, units, decimals, rounding direction, fee base, pending-state treatment, impairment, actual balance deltas, and the invariant reconciling assets, liabilities, and claim supply after every operation and adversarial sequence.

Common misunderstandings

• “The contract balance is total assets.” Assets can be deployed or owed, while liabilities and pending claims may not appear in token balance.
• “Rounding dust is harmless.” A favorable direction can be repeated, amplified, or concentrated around empty and near-empty states.
• “A preview is the executable value.” Price movement, fees, limits, queues, and liquidity can make execution differ.

Continue with net asset value, vault share, and solvency risk.

Machine-readable model

Key equations

Canonical expressions come from the structured concept record. KaTeX renders the notation, while the plain-text expression and variable table keep its meaning and units inspectable without JavaScript. Read the narrative above for the model's domain, assumptions, and rounding rules.

1. Equation 1

   $$\mathrm{reconciliationDifference} = \mathrm{recognizedAssets} - \mathrm{recognizedLiabilities} - \mathrm{attributableNetValue}$$

   Plain-text equation: reconciliationDifference = recognizedAssets - recognizedLiabilities - attributableNetValue

   Variables and units for equation 1

   Symbol	Meaning	Unit
   reconciliationDifference	Reconciliation Difference	selected valuation unit (for example, USD)
   recognizedAssets	Recognized Assets	selected valuation unit (for example, USD)
   recognizedLiabilities	Recognized Liabilities	selected valuation unit (for example, USD)
   attributableNetValue	Attributable Net Value	selected valuation unit (for example, USD)

Assurance contract

Security properties

These structured statements define desired behavior. Their stable IDs can bind tests, invariants, specifications, audit findings, or proof results without turning descriptive review advice into an assurance claim.

Desired · not evaluated: No test, audit, or proof result is implied until scoped evidence is linked to this property.

1. SP-01Desired · not evaluated

   Controlled assets, deployed positions, receivables, liabilities, reserves, fees, losses, and claim supply reconcile after every state transition

2. SP-02Desired · not evaluated

   Deposits, withdrawals, borrows, repayments, profits, losses, fees, donations, and rebases use explicit recognition times and rounding directions

3. SP-03Desired · not evaluated

   No user can create valuable claims without contributing or becoming entitled to equivalent net value under the selected model

4. SP-04Desired · not evaluated

   Preview, accounting, executable, and market values remain separately named and cannot be substituted without stated slippage, liquidity, and timing assumptions

Prerequisites

Direct dependencies recorded by this concept's canonicaldepends_on relationships.

• Net asset valuePath 36

  Net asset value is the value of a product's recognized assets minus its recognized liabilities at a stated valuation time and in a stated reporting unit.

Learn next

Concepts that directly depend on this one, ranked by the recommended learning path. Check each page for additional prerequisites.

No concept directly builds on this page in the current graph; use the guided learning paths to choose another branch.

Knowledge check

Quiz

Answer in your own words, then open the model answer.

What problem does Accounting risk exist to address?

Model answer

DeFi repeatedly converts between assets and claims, so small recognition, rounding, timing, or reconciliation errors can transfer value and compound across deposits, withdrawals, and integrations.

Mark as understood