Segment reporting and management MIS from the same numbers

Short answer: Ind AS 108 reports the segments management actually reviews, which makes the FP&A pack the evidence for the note. If the pack and the note are built separately, they will disagree, and the pack is the document a reviewer asks for. One set of dimensions, one allocation rule and one mapping keeps them in step.

The link most FP&A teams underrate

The segment note is not a statutory artefact invented by the accounts team. Ind AS 108 uses the management approach: the reportable segments are the components whose results are regularly reviewed by the chief operating decision maker for resource allocation and performance assessment, reported on the basis on which that function reviews them.

Read that again with an FP&A hat on. The board pack you produce every month is the source of a disclosure in the audited financial statements. Not an input to it, a description of it. Which means three things about the pack:

1. Its structure is a disclosure decision. Change the business lines the pack reports and you may have changed the reportable segments.
2. Its measures are the disclosed measures. Segment profit is reported as reviewed, even when that is not an Ind AS measure.
3. Its allocation rules become disclosed policy. How shared costs reach a business unit has to be described, and applied consistently between periods.

The recurring questions on the note itself are in operating segments: the questions regulators keep asking. This post is the other half: keeping the management numbers in a state where the note is a by-product.

What goes wrong when they are built separately

A common pattern in Indian groups: FP&A maintains business-line reporting in a set of workbooks with its own cost allocations, while the accounts team builds the segment note from the trial balance with a different allocation and a different definition of the segment result. Both are internally consistent. They disagree by a number nobody owns.

The symptoms are familiar. Segment margins in the investor deck that do not match the note. An “unallocated” column large enough to be a segment. Corporate cost that appears in the pack but not the note, or in both at different amounts. A restated comparative in the pack that was never restated in the note. And, once a year, a week spent reconciling two views of one business.

One set of dimensions

Start from the structure rather than the reports. Decide the dimensions the business is actually run on, and tag transactions with them at source: division, location, product, customer, region, project. Then a business-line view, a location view and a regional view are three cuts of one set of entries rather than three workbooks.

Two rules make this hold:

• The dimension belongs on the transaction, not on the report. A report-level mapping from account to business line breaks the first time an account serves two lines.
• Every dimension value has an owner. New plant, new product line, new project: someone has to add it before the entries arrive, or they land in “unassigned” and nobody notices until the quarter closes.

One allocation rule

Shared cost allocation is where the two views usually part company, and it deserves more discipline than it gets.

• Write the driver, not the result. Head-office cost allocated on revenue is a rule; the resulting numbers are not.
• Multi-step allocations need an order. IT cost to support functions, then support functions to business lines, in that order, produces a different answer from allocating everything at once. Fix the order and state it.
• Keep gross and allocated views side by side. Segment profit before and after allocation are different measures. Both are useful, and the pack should be explicit about which one it is showing.
• A change in driver is a change in policy. If you change it, restate the comparative or say plainly that you have not.

One mapping to the statutory chart

The management chart of accounts and the statutory one do not have to be the same, and it is usually better that they are not. The management chart answers “how is the business performing”; the statutory one answers “what does the framework require us to present”. What they have to share is a mapping, maintained as a master rather than reconstructed each quarter.

With one mapping in place, the segment reconciliation that Ind AS 108 requires — segment revenue, result, assets and liabilities against the reported amounts — becomes arithmetic over the same entries instead of an argument between two teams. The reconciling items are identifiable and nameable, which is exactly what the standard asks for.

A short checklist

1. List the dimensions the business is genuinely managed on, and where each one is captured today.
2. Find every cost currently allocated in a workbook and write its driver down.
3. Fix the order of multi-step allocations and record it.
4. Map every management reporting group to the statutory chart, and keep the unmapped list at zero.
5. Rebuild the last four quarters of the pack from the mapped data and compare with what was circulated.
6. Line the pack up against the segment note and name every difference.
7. Agree with the accounts team which view is the disclosed one before the next quarter, not after it.

Where FINK fits

FINK is MIS, and only MIS. It does not produce statutory financial statements or their notes: that’s a different product, FINAHQ, from the same entity. What FINK does is hold the management view of the same mapped data: dimensional reporting by division, location, product, customer, region or project, cost allocation on your own drivers including multi-step allocations, bespoke reporting groups that group ledgers the way the business is run rather than the way it files, and an MIS chart of accounts that is yours and mapped to the statutory one.

Because the figures are computed arithmetically from the ERP data and every figure links back to the journal entry it came from, an allocated business-unit result can be opened up rather than defended. And because both the management view and the statutory reporting read the same mapped data, the pack and the note stop drifting. The measure-definition version of the same problem is in one definition of EBITDA, and what happens when the statutory layout itself changes is in budget versus actuals under Ind AS 118. To size the work it takes out of your quarter, calculate your value or talk to us.

This article is general information, not professional advice. Check the current text of Ind AS 108 and discuss your position with your auditors.