Establish the right and the receivable population

The close file lists $19,200 as Accounts Receivable. Only $10,000 is currently unconditional; the other $9,200 still depends on Linden Peak completing a support milestone. Combining the rights does not change their total, but it breaks billing, aging, allowance, and disclosure evidence.

Classify before measuring

For every item, retain counterparty, transaction origin, contract or note, invoice, right condition, due date, maturity, currency, collateral, related- party status, dispute, balance-sheet class, offset restriction, and ledger account. Trade accounts from ordinary customer activity are not interchangeable with employee advances, tax claims, interest, insurance recoveries, seller notes, or amounts due from affiliates.

Remove credit balances, duplicate invoices, unapplied cash, sold interests, and items outside the reporting entity only after documenting their correct path. Reconcile the selected population to the gross ledger, not the net statement caption.

Diagnose a cash shortfall

Northwind disputes $4,000. A customary concession communicated at contract inception may reduce the consideration Linden Peak expects to be entitled to. A later funding failure on an established $4,000 right ordinarily changes the credit-loss estimate instead. Contract amendment, side letters, sales practice, dispute substance, credit approval, aging, and later events decide the route; the lower expected cash amount does not.

Population ticket

Work through Juniper's worklist to see how the classifications produce different control totals. Then apply the method to the independent practice.

For each open item, write a one-line ticket: right, origin, condition, gross amount, classification, governing question, model population or exclusion, evidence owner, and unresolved fact. The aging team receives only the reconciled unconditional-right population.