Segment disclosures can look like a presentation exercise, but they deserve a deliberate audit approach because the numbers often come from management reporting systems, allocation models and inter-segment eliminations rather than from a single ledger balance. SA 501, Audit Evidence—Specific Considerations for Selected Items, specifically addresses segment information. The practical question is how the auditor obtains sufficient appropriate audit evidence that the segment information presented and disclosed in the financial statements complies with the applicable financial reporting framework.
What SA 501 requires for segment information
Paragraph 13 of ICAI's SA 501 requires the auditor to obtain sufficient appropriate audit evidence about the presentation and disclosure of segment information. This involves understanding management's methods, evaluating whether those methods are likely to produce disclosure in accordance with the applicable framework, testing their application where appropriate, and performing analytical or other audit procedures suitable to the circumstances.
SA 501 also sets an important boundary: the auditor's responsibility for segment information is in relation to the financial statements taken as a whole. It does not require procedures necessary to express a separate audit opinion on segment information on a stand-alone basis.
Step 1: Identify the applicable reporting framework
First identify which accounting framework governs the entity's segment disclosures. For entities applying Accounting Standards, ICAI publishes AS 17, Segment Reporting. For entities applying Indian Accounting Standards, ICAI's Educational Material on Ind AS 108, Operating Segments explains that Ind AS 108 follows a management approach and is intended to help users evaluate the nature and financial effects of the entity's business activities and economic environments.
The audit file should record the framework used, the source of management's segment determination and the key disclosure requirements relevant to the entity. Audit evidence then has a clear benchmark.
Step 2: Understand how management builds the segment information
SA 501 directs attention to the method, not merely the final note. Walk through the reports and systems management uses and follow the flow into the financial statements. Understand, as relevant:
- how management identifies the segments used for financial reporting;
- which reports, ledgers or management-information systems provide the disclosed measures;
- how sales, transfers and charges between segments are recorded and eliminated;
- how shared costs and assets are allocated among segments;
- whether the method is applied consistently from period to period; and
- how changes in method, structure or presentation are evaluated and disclosed.
A mathematically correct segment note can still be misstated if transactions are mapped to the wrong segment, common costs are allocated inconsistently or inter-segment amounts are not eliminated properly.
Step 3: Reconcile the disclosure to reliable financial information
A strong audit trail usually includes a reconciliation from the segment working to the underlying accounting records and then to the financial statements. The exact reconciliation depends on the framework and measures presented, but relevant totals should be tested for completeness, arithmetic accuracy and consistency with entity-level or consolidated information.
Do not stop at agreeing the final total. Select material segment measures and trace them to supporting records. Where a report is generated from an information system, consider its reliability as audit evidence. Where management makes manual adjustments outside the ledger, test their purpose, authorization, calculation and posting.
Step 4: Test allocations and inter-segment items
SA 501 specifically identifies sales, transfers and charges between segments, elimination of inter-segment amounts, and allocation of assets and costs among segments as potentially relevant matters. These areas often involve judgment or manual processing.
For a shared-cost allocation, understand the stated basis, assess whether it is applied as described, recalculate selected items and investigate unusual movements. For inter-segment transactions, check that source records identify the counter-segment consistently and that material eliminations are complete. If an allocation basis changed, understand why and evaluate the resulting presentation and disclosure under the applicable framework.
Step 5: Use analytics to challenge the segment story
SA 501 contemplates analytical procedures or other procedures appropriate in the circumstances. Compare segment revenue, margins, asset intensity or other relevant measures with prior periods, budgets or operational data and investigate movements that do not fit the known business story.
A sharp margin improvement in one segment may be commercially plausible, but it can also result from common costs being shifted elsewhere. A large fall in inter-segment revenue with no change in the operating model may point to a mapping or elimination issue. Analytics help direct attention; they do not replace testing of the underlying method.
Worked illustration
Assume a manufacturing group reports Consumer and Industrial segments. Central IT and head-office costs are allocated using management-defined drivers, and the divisions sell components to each other. During the year, management changes the driver for one shared service from headcount to usage data.
A practical SA 501 response is to document the revised method, test whether the new driver is applied consistently to the relevant cost pool, recalculate selected allocations, reconcile segment revenue and results to underlying records, test selected inter-segment sales and related eliminations, and compare segment margins with prior periods and budgets. If the allocation change materially affects comparability or disclosure, evaluate whether the presentation meets the applicable reporting framework. The objective remains evidence over segment disclosure within the financial statements as a whole, not a separate opinion on each segment.
Common audit mistakes
- Checking only arithmetic: totals can add correctly while identification or allocation is wrong.
- Accepting allocation bases without testing application: document the basis and test how it was actually used.
- Forgetting inter-segment eliminations: test source transactions and the elimination process where material.
- Using analytics as the sole evidence: unexplained trends may require further substantive work.
- Creating a separate-segment audit objective: SA 501 frames the responsibility in relation to the financial statements as a whole.
Practical working-paper checklist
- Document the applicable segment-reporting framework.
- Obtain the segment note, supporting working and relevant management reports.
- Walk through how segments and disclosed measures are determined.
- Reconcile relevant segment totals to underlying records and the financial statements.
- Test material manual adjustments, allocations and inter-segment eliminations.
- Compare segment information with prior periods, budgets and other reasonable expectations.
- Investigate inconsistent methods, unexpected trends and unexplained reconciling items.
- Evaluate whether the final presentation and disclosures comply with the applicable framework.
- Document the evidence obtained and conclusion in the context of the financial statements as a whole.
Practical takeaway
A defensible SA 501 segment-information audit is built around three questions: How did management determine the segment information? Was that method applied correctly? and Does the resulting presentation and disclosure comply with the applicable financial reporting framework? Reconciliations, allocation and elimination testing, and expectation-based analytics turn those questions into a practical audit trail. Always confirm the current ICAI standard and the reporting framework applicable to the entity before finalising engagement-specific procedures.
