Testing segment reporting completeness means starting from the internal management reports regularly reviewed by the chief operating decision maker — not the published segment note — identifying every operating segment those reports actually distinguish, and then checking that each one meeting the quantitative thresholds, or aggregated under a documented justification, appears in the disclosed note with the right revenue, result, assets and reconciliation to the entity total.
Why the test has to start from the internal reports, not the note
The management approach underlying Ind AS 108 means segments are defined by how the business is actually managed and reported internally, not by a reporting structure the entity chooses for external presentation. Testing the note against itself — checking the arithmetic adds up — proves nothing about whether a segment the CODM actually looks at has simply been left out.
The testing sequence
- 01Identify the chief operating decision maker and obtain the reports regularly reviewed by that person or groupThis can be the CEO, a management committee, or a board sub-committee — identified by function, not by title. Ask what reports actually go to that function on a recurring basis, not what the client calls its 'segment reporting' internally.
- 02List every distinct component the internal reports break performance down byBusiness line, geography, customer channel — whatever the internal reports actually use as the unit of review. This list is the universe of candidate operating segments, independent of what the entity has disclosed.
- 03Test each candidate against the aggregation criteria where the entity has combined componentsAggregation requires similar economic characteristics and similarity across the specified indicators — nature of products, production process, customer type, distribution method, and regulatory environment. A documented aggregation that does not actually meet these criteria is a completeness failure, not a presentation choice.
- 04Apply the quantitative thresholds to each identified operating segmentTen percent of combined revenue, reported profit or loss, or assets. Confirm the arithmetic behind each threshold test, and check whether the 75 percent external revenue coverage test required additional segments to be disclosed even though they individually fell under the thresholds.
- 05Trace segment revenue, result and assets to the general ledger and the internal reports side by sideThe figures in the disclosed note should reconcile to what the CODM actually saw, not to a re-cut performed only for the financial statements.
- 06Test the reconciliation of segment totals to the entity's consolidated totalsUnallocated items, eliminations and consolidation adjustments should be separately identified and explained, not absorbed into one segment's numbers.
| Step | Evidence |
|---|---|
| CODM identification | Organisation chart and governance structure, corroborated by who actually receives the internal reports |
| Candidate segment list | Internal management reporting packs for the year, obtained directly, not via the client's segment note |
| Aggregation test | Comparison against the specified similarity indicators, documented component by component |
| Quantitative threshold test | Recomputed percentages against combined revenue, result and assets |
| Reconciliation to entity totals | Unallocated items and eliminations separately traced |
Regulatory requirement
Ind AS 108 sets out the management approach to identifying operating segments, the aggregation criteria, the quantitative thresholds, and the 75 percent external revenue test. Verify the current text before concluding.
How we think about this
The threshold arithmetic and the reconciliation to entity totals are computations that should be performed in full against the actual internal reports, not inferred from the published note. Deciding whether two components genuinely share similar economic characteristics for aggregation is a judgement, and it is the judgement most often used to make an inconvenient segment disappear.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Audit documentationInd AS 108: operating segments, and why they're defined by management's own view, not the auditor'sSegments aren't drawn by an accounting standard's own logic — they're drawn from how the business genuinely reports to the person who actually runs it.
- Audit documentationInd AS 1: presentation of financial statements, and what a complete set actually requiresFour statements plus notes isn't optional structure — Ind AS 1 defines exactly what counts as a complete set, and a financial statement missing one piece isn't compliant regardless of how good the other three look.
- Audit workflow & automationStatutory audit planning checklistUnderstanding the entity, setting materiality, risk assessment at planning, and briefing the team against a realistic timeline — a rounded planning reference.
- Audit data & extractsTrial balance mapping for audit softwareMapping a client's idiosyncratic ledgers to a standard chart of accounts is the step that decides whether analytics and disclosures work at all, and the one most firms rush.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.