Map the obligation before measuring it

Place six cards on a table: December electricity estimated before billing; sales tax collected for the state; cash received before customer service; a product defect allegation; a note due in March; and a signed contract for next year's steel. Which cards are liabilities, and why?

Do not answer from the noun. Write one sentence for the event or condition that exists at December 31.

Four questions that prevent category errors

1. What did Cedar Trail receive, collect, promise, borrow, or become exposed to, and on which date did that event or condition arise?
2. Had the counterparty performed, had Cedar Trail performed, or were both sides still waiting?
3. Is uncertainty about amount, or about whether a loss condition will be confirmed?
4. Which Topic owns the matter before the general contingency guidance applies?

Electricity already consumed is a routine accrual even when estimated. Tax collected for an authority is a payable, not seller revenue. An advance for future service is a contract liability. A lawsuit enters the contingency lane. The note needs a debt chronology. The steel contract may remain executory while separate loss or disclosure questions require research.

Why the word “reserve” is unhelpful

An accounting liability is not a cash bucket. Calling warranty or litigation accruals “reserves” can hide whether any asset has been restricted. Keep the recognized obligation, expected cash timing, funding plan, and liquidity risk in distinct columns.

Practice

Complete Q:current-liabilities-refinancing-and-contingencies/obligation-map-001. For each rejected route, name the fact that made it wrong.

Exit check

Create a seven-column obligation map: item, counterparty, past event, present obligation or condition, uncertainty, governing Topic, and next evidence owner. Leave the measurement column blank until every row has a defensible route.