Your MIS chart of accounts is not your statutory one, and that is fine

Short answer: keep one set of ledgers and two mappings over them. The statutory view groups by nature because a filing format says so. The management view groups by how the business is actually run. Neither is the “real” one, and neither should be typed twice.

Why the two views diverge

A statutory line says employee benefits expense. A business head asks what the sales team costs, which is some of that line plus some of travel plus some of a recharge from a shared services entity. Both are correct answers to different questions.

The problem is never the difference. It is that the management answer usually gets built in a spreadsheet, from an export, by one person — and from that moment the two views can drift without anyone noticing.

What an MIS chart of accounts actually is

A mapping, held once, from every ledger in every entity to the management line it belongs to. Not a second ledger. Not a copy of the data. If the management pack and the books ever disagree, the mapping is wrong, and that is a much easier thing to fix than a reconciliation between two sets of numbers.

The test: can you take any figure in a management pack and open it out to the ledgers underneath? If not, the pack is an assertion.

The three places it breaks

A new ledger opened mid-year. Somebody opens a ledger in one entity in August. It belongs somewhere in the management view, but nobody maps it, so the pack for September is quietly short. Nothing errors — the number is just smaller than it should be.

An entity that names things differently. An acquisition arrives with its own naming. Mapping it to the group’s management lines is a day’s work that nobody schedules, so for two quarters that entity is reported at a level of detail nobody else is.

A line that means two things. Other expenses in one entity is the bin for anything uncategorised; in another it is a real category. Mapped as one management line, it produces a number that is meaningless in a board pack and impossible to question.

How to hold it

• One mapping, versioned. When a line moves, the change is dated. A board asking why a figure moved between quarters deserves an answer better than “we changed the pack”.
• Nothing unmapped. A ledger with no management line is a hole in the pack, so it should be visible as one rather than silently excluded.
• Both views from the same read. The management cut and the statutory cut come from one pass over the ledgers, so the totals cannot drift apart between them.

FINK holds the MIS chart of accounts as a mapping over the same data the books are on, with dimensional reporting for the cuts underneath it. If you want a sense of what slow management reporting is costing your group today, the value calculator works it out from your own answers.