Give the whole group one chart of accounts, one set of dimensions and one set of statement layouts. Each entity keeps its local accounts and cost centres. Control maps them to the group structure, so a change in one place reaches every report that uses it.
Point each local account at the group account with the same meaning. Many local accounts, from one entity or several, can map to the same group account. Generate a first group chart from the entity accounts, then refine it.
Map local cost centres, projects and departments to group dimension items. Each group item can sit under a parent item, so report pickers show the whole tree, from one cost centre up to the total company.
Arrange group accounts into the P&L, balance sheet and cash flow your team reviews, with groups, nested groups and formula rows. A Functional P&L splits one account by department or cost centre through the mapped group dimensions.
New local accounts arrive with the next sync and show as unmapped until they are mapped. With AI automapping on, Control posts one shared proposal when they need new group accounts. Change a mapping and the reports on those group accounts follow. Edit a layout and only the report changes, never the mappings or the source transactions.
Set up the group chart, map the entities to it and lay out the statements. After that, keeping it current is a mapping decision, not a rebuild.
Generate a first group chart of accounts from the entity accounts, then refine it.
Point local accounts and dimension items to their group equivalents, by hand or from reviewed AI suggestions.
Place group accounts in P&L, balance sheet and cash flow layouts.
Map new local accounts as they arrive. Reports that use a group account follow its mappings.
No. Each entity keeps its local accounts and dimensions in its own accounting system. The group structure sits in Control, and mappings connect the two without renaming or rebuilding the source systems.
It arrives as a local account after the next sync and stays outside the group structure until it is mapped. With AI automapping on, Control posts one shared proposal when the mapping needs new group accounts, and the workspace reviews it.
No. A layout decides where a group account appears and how rows and formulas calculate. It does not change account mappings or source transactions. Changing a mapping, by contrast, can change values in every report that uses that group account.
Yes. Claude, ChatGPT, Codex and other MCP clients can read group accounts, dimensions and statement layouts over MCP, next to the statements built on them. Each user’s Control permissions still apply.
Book a demo with the Control team. Bring your accounting systems and one question, and we walk through how a group like yours runs on Control. Or start for free and set it up yourself.