Build the revenue note and a reviewable evidence trail

A revenue note should connect reported amounts with contract populations, timing, judgments, and uncertainty. Linden Peak's draft instead says, “Revenue is recognized when earned. Deferred revenue was $13 million. Backlog will become revenue.” None of those sentences lets a reader reperform the claim.

Give each disclosure a job

• Disaggregation explains how economic factors affect the nature, amount, timing, and uncertainty of revenue and cash flows.
• Contract-balance information explains opening and ending positions, unusual changes, revenue released from opening liabilities, and revenue tied to prior performance.
• Performance-obligation information explains satisfaction and payment terms, returns, warranties, agency, significant financing, and significant judgments.
• Contract-cost information explains closing assets, amortization, impairment, and methods.
• Remaining-performance-obligation information reports allocated consideration and expected timing within its scope and practical expedients.

Tie each amount to a controlled schedule and the same entity, period, units, currency, and contract population as the statement. Compare disaggregation with segment and other public information; explain material differences rather than forcing the dimensions to match.

Reconcile RPO without promising the future

Remaining performance obligations are the transaction-price amounts already allocated to promises the entity has not yet satisfied, subject to the disclosure's scope and permitted exclusions. That positive definition comes before any comparison with operational backlog.

Build an RPO bridge from opening amount, new and modified consideration, recognized revenue, cancellations, currency, acquisitions, and ending amount. Then map the ending amount to expected timing bands. Identify amounts excluded under practical expedients and variable consideration not included.

RPO is not management backlog, contracted cash, expected margin, or guaranteed future revenue. Cancellation, performance, estimates, price concessions, currency, and scope can change it. A valid analyst statement names those limitations.

Retain current authority and filing context

The 2026 FASB post-implementation report supplies current context: Topic 606 is mature and no issue required immediate standard setting, yet complex judgments remain. That report is not the operative guidance. Retain the current Codification locator, access date, entity and period, amendment status, and technical reviewer.

For a public filing fact, retain registrant, form and accession, report period, note and table, units and scale, sign, comparative column, tag, duration or instant, dimensions, decimals, and extension status. A matched XBRL number does not validate the underlying GAAP judgment.

Reopen the completed fictional tag-and-table example in L:statement-presentation-comprehensive-income-and-disclosure/07-segment-note-and-filing-evidence before using that checklist. Its one visible 4,200 fact demonstrates how duration, units, scale, dimension, extension tag, and exact note cell travel together; substitute a real official filing only after retaining its registrant, form, accession, period, and filing context.

Controller-ready close

Complete the Linden Peak case with a one-page issue matrix: issue, governing source, decisive facts, calculation, conclusion, alternative, open item, owner, reviewer, and release stop. The strongest memo shows what remains unresolved instead of using a reconciled schedule to imply technical approval.

Apply the note map and rollforward in the Cedar Trail worked example. Then use the Northstar practice to review a different note, rebuild its RPO bridge, and state its limits.