Accrued operating liability

An accrued operating liability records a present obligation for operating goods or services already received. An invoice or cash payment can follow the reporting date. The later document may improve measurement, but it does not move the received service into a later period.

Separate existence from measurement

Start with evidence that the entity received the good or service by period end. For electricity, that evidence may include meter readings, service dates, usage history, and the supplier's rate schedule. Once the obligation is supported, measure the amount from the best available evidence and record the related expense or asset.

Suppose December electricity is estimated at $4,800 and billed in January. The December entry is:

Dr Utilities Expense                 $4,800
    Cr Accrued Utilities Liability            $4,800

When the invoice arrives, compare it with the estimate. Settlement clears the liability. A difference may require a true-up under the applicable facts; it does not mean the December service never occurred.

Do not route every estimate through contingency guidance

This concept assumes that service receipt and the resulting obligation are established. Uncertainty remains in the amount. A loss contingency asks whether a loss has been incurred under a different evidence model. The use of an estimate does not make those questions identical.

The close file should preserve the service cutoff, source data, estimate method, approval, entry, later invoice, settlement, and true-up. It should also identify whether the cost belongs in expense, inventory, another asset, or a specialized Topic.

Boundaries

The example excludes disputed service, variable contract terms, income taxes, payroll law, leases, environmental obligations, asset-retirement obligations, and foreign currency. It also assumes current presentation. A liability can be accrued without being current, so classification needs its own horizon and settlement facts.

Follow the authority and learning path

ASC 210-10-45-5 provides the general current-liability presentation principle. It does not set the recognition or measurement rule for every operating accrual. The liability definition comes from the FASB Conceptual Framework, which is nonauthoritative. Transaction-specific Codification guidance controls a real conclusion.

Study the routine-liability lesson before tracing the Cedar Trail close. Then complete the payroll-and-leave task with the stated cutoff and plan evidence.