
Accrued liabilities represent obligations for expenses that have been incurred and services already used, but for which no invoice or bill has yet been received. These “payable but unpaid” obligations are recorded as liabilities in the current period, ensuring that costs are matched to the month in which they actually occurred, rather than when payment is made.
For example, if a team uses cloud nodes and security audit services during the current month but receives the bill at a later date, the associated costs should still be recorded for this month, creating an accrued liability. Common types of accrued liabilities include salaries, interest, consulting, and custody fees.
Accrued liabilities are grounded in the accrual accounting principle. Under this method, revenues and related expenses are recognized when they are earned or incurred—not necessarily when cash is received or paid. This ensures that income and expenses from the same business activity are recorded in the same period, preventing profits from being overstated or understated.
For instance, if a Web3 project completes a marketing partnership in the current month but hasn’t yet received an invoice, the marketing service is considered “incurred” and should be recognized as an expense this month, forming an accrued liability. Waiting until next month to record the cost would misalign expenses and distort the project's performance for the current month.
On the balance sheet, accrued liabilities are typically listed under current liabilities—obligations due within one year—reflecting upcoming payment requirements. On the income statement, expenses associated with accrued liabilities are already recognized in the current period, representing the actual cost incurred.
Example: At month-end, a team accrues $100,000 in node custody fees. The income statement for the period records a $100,000 custody fee expense, and the balance sheet increases “accrued liabilities” by $100,000. When the invoice arrives and payment is made the following month, this accrued liability is reversed, decreasing both liabilities and cash.
Accrued liabilities play a crucial role in Web3 contexts:
Step 1: Identify Transactions. Review all categories of expenses incurred but not yet billed for the month—such as salaries, interest, technical custody fees, audits, and consulting—and confirm service completion.
Step 2: Estimate Amounts. Use contract rates, usage metrics (like node hours or API calls), milestone progress, or historical averages to estimate amounts; material or volatile items should be reviewed by management.
Step 3: Book Journal Entries. The standard entry is to debit the relevant expense account (e.g., consulting fee/custody fee/interest) and credit “accrued liabilities.” Ensure expenses are recorded in the correct account to distinguish between operating costs and capitalized expenditures.
Step 4: Reconciliation and Reversal. When invoices arrive, compare billed amounts to accrual estimates and adjust for any differences; upon payment, reverse the accrued liability and archive payment records.
Step 5: Disclosure and Approval. In DAO governance or project management contexts, disclose significant accrued liabilities for proposal approval and audit verification; retain contracts, proof of service completion, and estimation rationale.
Accounts Payable: These are obligations where an invoice or settlement document has already been received—amounts are clear and responsibility is defined; they represent confirmed payables or expenses.
Accrued Liabilities: Expenses have been incurred but no bill has been received; amounts are estimated based on contract terms and service progress and reconciled once invoices arrive.
Provisions: Obligations that may arise in the future but with uncertain amounts or probability—such as potential legal claims or warranty liabilities. Compared to accrued liabilities, provisions involve greater uncertainty.
First, token price volatility. If contracts are settled in tokens, accrue liabilities by converting token value into your accounting base currency (such as USD or stablecoins), documenting valuation dates and sources to minimize errors from price fluctuations.
Second, multisig and approval processes. DAO multisig delays can push payments into future periods; after accruing liabilities, track proposal and execution status to avoid long-outstanding “dormant” liabilities.
Third, smart contract auto-payments and timing mismatches. Some smart contracts release funds automatically based on milestones or time intervals, but service completion may not sync with invoice receipt—so accrue and reverse appropriately around these releases.
Finally, vendor coordination and audit readiness. For on-chain services (oracles, nodes, anti-Sybil tools), retain API usage data, service completion screenshots, and contracts to support audit sampling and expense verification.
Over- or under-accruing distorts profit and liability figures—impacting investor judgment and governance decisions. Auditors typically focus on estimation methods, contract terms, evidence of service completion, and subsequent invoice reconciliation.
From a compliance perspective, follow applicable accounting standards (such as IFRS or US GAAP) and local tax rules. For token-based expenses, clearly document valuation methodology and exchange rate sources with supporting snapshots. When dealing with treasury safety, assess cash flow impacts to avoid liquidity crunches caused by large lump-sum payments.
More projects now integrate on-chain data with traditional accounting systems—connecting wallet, exchange, and smart contract events to automatically identify accrual scenarios (like service completion or milestone achievement) and generate accrual recommendations.
The adoption of stablecoins reduces valuation volatility, making measurement of accrued liabilities more controllable. At the same time, improved governance transparency means more DAOs now include major accrued liabilities in periodic disclosures and audits—enhancing community oversight and treasury management.
Accrued liabilities ensure that expenses are accurately recognized in the period they occur—supporting true representation of profits and obligations. For Web3 projects and DAO treasuries, identifying service completion, estimating amounts, timely accruals, reconciliation, and disclosure are key to effective management. Distinguishing between accrued liabilities, accounts payable, and provisions—and establishing robust compliance, audit, and governance processes—reduces reporting errors and liquidity risk while enhancing project transparency and sustainable operations.
They’re not opposites—they’re two different aspects of financial statements. Accounts receivable are assets (your right to receive money), while accrued liabilities are liabilities (your obligation to pay). For example: if you sell something but haven’t been paid yet, that’s accounts receivable; if someone buys from you but you haven’t invoiced them yet, it’s an accrued liability for them. Both are based on accrual accounting but appear on opposite sides of the balance sheet.
The most typical examples are unpaid liquidity mining rewards and pending airdrop commitments. For instance, if your DeFi protocol promises governance token rewards at month-end but hasn’t distributed them yet, their fair value should be recorded as an accrued liability. Other examples include unpaid audit fees or developer compensation (if accrual accounting is used). All of these affect a project’s true financial position.
Mainly because the crypto industry has traditionally favored cash-based accounting—many projects lack formal finance departments. But as compliance requirements tighten and institutional capital enters the space, accrual accounting is becoming necessary. Ignoring accrued liabilities distorts financial reports and conceals actual debt burdens—posing risks to both investors and auditors. Using financial tools from professional platforms like Gate or consulting accountants is strongly recommended.
Accrued liabilities themselves don’t immediately use cash—but they represent inevitable future cash outflows. If large accrued liabilities exist without sufficient cash reserves, liquidity risk arises: losses show up on paper now but must be paid later. This is especially important for DAO treasury management—budgets should reserve enough cash to cover these obligations.
Auditors focus on three main issues: whether all accruals have been fully recorded (omissions are common), whether estimates are reasonable (especially when amounts are uncertain), and whether disclosures are adequate (including proper notes in financial statements). In crypto projects, common gaps include missed recording of unpaid partnership fees, outstanding rewards obligations, or reserves for potential penalties—all of which may require adjustment during audit reviews.


