
Accrued liabilities refer to obligations that a company has incurred but not yet paid, such as utility expenses that have been used but not yet invoiced or settled. Current liabilities are debts expected to be settled within one year or within a business’s operating cycle. Because accrued liabilities are typically linked to routine business operations and involve short payment cycles, they are commonly classified as current liabilities. However, the final classification depends on the actual settlement timeframe.
Common examples of accrued liabilities include provisions for wages, interest, taxes, and regular service fees. When expenses are recognized in the current period but cash is paid later, they are first recorded as accrued liabilities to accurately match costs with revenues in financial statements.
Accrued liabilities are generally categorized as current liabilities because most accrued items are paid within a short period, such as salaries paid the following month, quarterly interest payments, or annual tax settlements. As of January 2026, both International Financial Reporting Standards (IFRS, see IAS 1) and US Generally Accepted Accounting Principles (US GAAP, see ASC 210) use “within 12 months or one operating cycle” as the main criterion for classifying current liabilities (source: IFRS IAS 1 and US GAAP ASC 210, January 2026).
However, “usually” does not mean “always.” If a contract or arrangement specifies that an accrued liability will be settled more than one year in the future, it should be classified as a non-current liability. For instance, annual post-paid long-term service fees or anticipated expenditures for ongoing litigation require assessment based on agreements and cash flow plans.
Accrued liabilities are common in Web3 contexts, following the core principle of “expense incurred, cash unpaid.” For example:
In decentralized autonomous organizations (DAOs), if a proposal authorizes a service with a defined cost range and the service has been delivered but not paid for, an accrued liability is recognized to reflect the obligation accurately.
The classification hinges on the expected settlement period and operating cycle. The process can be outlined as follows:
Step 1: Identify the obligation. Ensure that the expense has been incurred and that the company is responsible for payment—this includes contract terms, governance proposals, or service acceptance records.
Step 2: Review the terms. Check contractual or internally approved payment schedules to see if payment is required within 12 months or aligned with the normal operating cycle.
Step 3: Assess cash flows. Consider funding plans and historical payment practices. If typically settled within a year, classify as current; if due after a year, classify as non-current.
Step 4: Presentation on financial statements. Disclose each category separately on the balance sheet. If amounts are significant and of different natures, separately disclose the composition and maturity structure of accrued liabilities to enhance transparency (source: IFRS and US GAAP reporting practices, January 2026).
An increase in accrued liabilities raises current liabilities, affecting metrics such as the current ratio and quick ratio. If short-term obligations accumulate, the business must maintain sufficient cash or equivalents to meet them; otherwise, liquidity pressures may arise.
Misclassification of accrued liabilities in financing or loan agreements can distort covenant calculations. For example, recording long-term obligations as current could reduce the current ratio and impact credit access or compliance. Accurate accruals help timely reflect costs and prevent profit overstatements.
Typical examples of accrued liabilities include:
In Web3 scenarios, event rewards, technical maintenance fees, node hosting expenses, and cross-chain bridge security audits completed but unpaid also form accrued liabilities. Classification as current depends on payment terms and expected settlement dates.
Using trading platform operations as an example—platforms like Gate may encounter the following:
These scenarios illustrate common practices; accounting treatment should follow contract terms and applicable standards while considering actual settlement arrangements for classification.
The primary risks involve cash flow pressures and insufficient disclosure. If many accrued liabilities mature simultaneously without adequate cash reserves, it may threaten payment capability and platform credibility, raising concerns about user fund safety. Misclassification can also mislead decision-making and financing arrangements.
Effective management involves:
Step 1: Creating an accrual register. Regularly track salaries, taxes, service fees, and user incentives with clear amounts and due dates.
Step 2: Aligning with cash budgets. Integrate maturity profiles of accrued liabilities into rolling cash forecasts to maintain liquidity buffers.
Step 3: Enhancing disclosure and approval processes. Separately disclose material accruals; require multi-signature approvals and clear audit trails for payments. In Web3 teams, tools like multisig wallets and fund management protocols can help mitigate operational risks.
Both are liabilities but originate differently. Accrued liabilities are for incurred expenses that can be reasonably estimated but have not yet been invoiced or reached their settlement date; accounts payable usually refers to amounts owed based on received invoices or formal bills from suppliers.
For example, audit services provided without an invoice are recorded as accrued liabilities; once invoiced, they shift to accounts payable. In practice, each is reported under separate accounts to facilitate payment management and reconciliation.
Accrued liabilities represent obligations where “the expense is incurred but cash is paid later.” Classification as a current liability depends on whether they are expected to be settled within 12 months or an operating cycle. Most business-related accruals clear in the short term and are thus treated as current; long-term arrangements require non-current classification. Accurate accruals and classifications not only reflect costs and obligations truthfully but also help manage cash flow and compliance risks—this applies equally to Web3 projects and trading platforms.
While both are forms of debt, their origins differ. Accounts payable arise from known debts supported by invoices or contracts—such as goods purchased from suppliers but not yet paid for. Accrued liabilities stem from estimated debts based on activities already performed—such as wages earned by employees but only paid at month-end. Simply put, accounts payable have supporting documents; accrued liabilities are based on estimates.
The key criterion is when the debt is expected to be paid. If payment is due within one year (or one operating cycle), it is a current liability; if due after one year, it is non-current. For example, monthly accrued wages typically paid next month are current; deferred compensation promised to employees for payment five years later is non-current. The repayment term—not just the nature of the obligation—is decisive.
Most accrued liabilities have short durations—they are expected to be paid within a year—so they fit naturally under current liabilities. Common items like accrued wages, bonuses, and interest usually require settlement soon after each month, quarter, or year ends. Current liabilities represent short-term financial pressure and imminent cash outflows; accrued liabilities from daily operations match this profile. Exceptions include long-term items such as pension accruals or deferred compensation—these are non-current.
Errors in estimating accrued liabilities directly impact total debt and net profit. Overestimating increases current period costs and understates profits while lowering liquidity ratios—making finances appear more strained; underestimating does the opposite—artificially inflating profits and masking actual repayment pressures. Such inaccuracies can mislead investors, creditors, and management. Therefore, companies should use robust estimation methods (such as historical data or industry benchmarks) and disclose key assumptions in financial statement notes to ensure accuracy and transparency.
Crypto projects and DAOs operate differently but follow similar financial principles. Accrued liabilities cover incurred but unpaid costs—such as developer wages, audit fees, or airdrop commitments. Given DAOs’ decentralized nature and on-chain governance, managing accruals requires greater rigor—often using smart contracts or multisig wallets for transparency. Projects should clearly disclose these obligations in financial statements or on-chain data to avoid treasury risks or loss of community trust due to poor estimates.


