Reconcile the segment note and preserve filing evidence

A segment note exposes management measures and reconciles them to consolidated GAAP reporting. It does not transform every internal allocation into a GAAP measurement. The note should let a reader see what management uses, how the segments are organized, which significant expenses and other items compose the measure, what changed, and where consolidated totals differ.

Build the current segment evidence map

For an in-scope public entity, record:

• reportable segments and aggregation conclusions;
• CODM title and position and how the CODM uses the reported measures;
• each segment profit or loss measure and why the reported measure or measures satisfy the current model;
• significant expense categories regularly provided to the CODM and included in each reported measure;
• other segment items and their composition;
• segment assets and other required amounts;
• annual and interim periods;
• single-reportable-segment implications;
• changes and prior-period recasting; and
• reconciliations to consolidated revenue, profit or loss, assets, and other required totals.

Preserve management-report versions, calculation owners, allocation rules, intersegment amounts, eliminations, and approvals. A reconciliation plug called “corporate” is not an explanation.

Know which filing layer you are reading

The official filing can contain audited statements and notes, management discussion, risk factors, controls information, exhibits, and inline-XBRL facts. Search can land in any of them or in a prior-year comparison. Before citing a result, confirm registrant, form, accession, filing date, period, amendment status, statement or note, table, units, comparative column, and surrounding language.

Inline XBRL attaches machine-readable accounting tags and context to numbers and narrative that remain visible in the human-readable filing. For an inline-XBRL fact, preserve entity, instant or duration, units, scale, decimals, sign, dimensions, extension status, and where the fact appears in the human-readable filing. A machine-readable value without context is not a verified reporting claim.

For example, suppose Granite Harbor's fictional note displays 4,200 in a column labeled “Clinical segment, USD thousands, year ended December 31, 2026.” A locator log might record a fictional extension concept ghd:SegmentMeasure, a January 1–December 31 duration, USD unit, thousands scale, Clinical member on a business-segment dimension, displayed precision, positive sign, and the exact note-table cell. “Duration” distinguishes a year's flow from an instant balance. The dimension identifies which segment the fact describes. “Extension” warns that the company supplied the concept rather than using a standard taxonomy concept. Those fields do not prove the measure is consolidated GAAP; they make the observation findable and comparable.

Cross-check without collapsing authority

Management discussion can explain trends and uncertainty. The segment note provides financial-statement disclosure. An exhibit can contain a contract. A tag exposes a data fact. They can corroborate one another while retaining different reporting roles and assurance boundaries.

Locator challenge

A search result displays a segment expense number. List the filing and XBRL fields needed before comparing it with the consolidated income statement, and state why the matched words do not prove the measure follows consolidated GAAP.