Each entity keeps its own system and its own close. Control reads every ledger, maps it once to the group chart, translates currencies with CTA and eliminates intragroup activity. Every group figure, and every elimination, opens to its entries.
| Line | Finland OyNetvisor | Services OyProcountor | US IncQuickBooks | UK LtdXero | EliminationsGroup entries | GroupEUR |
|---|---|---|---|---|---|---|
| Revenue | 600 | 290 | 400 | 200 | −90 | 1,400 |
| Cost of sales | −215 | −120 | −150 | −75 | −560 | |
| Gross profit | 385 | 170 | 250 | 125 | −90 | 840 |
| Operating costs | −265 | −105 | −150 | −95 | 90 | −525 |
| EBITDA | 120 | 65 | 100 | 30 | 0 | 315 |
Each entity connects its own accounting system. Syncs run at least daily, a refresh can be started on demand, and backdated entries are picked up again. Control proposes the mapping to the group chart of accounts, and your team accepts it once for the workspace.
Automated rules reverse recurring intragroup activity from the date you set. Manual group entries handle the one-off. Eliminations sit in their own column, CTA splits into currency and elimination, and none of it posts back to an entity’s books.
Drill from a group line to the entity, the local account and the entries behind it. One group account can sit in more than one statement layout, so the internal report and the official format read the same mapped numbers.
Groups with sub-groups ask two things first: how the close follows each ledger, and what happens to the numbers when the group chart of accounts changes.
Period locks stay in each accounting system. Control shows which months each source reports as closed, and a close recorded in Control never changes the lock in the source.
An account an entity opens after setup stays visible as unmapped until your team maps it, so nothing drops out of the group quietly.
Map a local account to a different group account and the change reaches every report that uses that group account, once the data is recalculated or refreshed.
Reports follow the current mapping, so earlier months can change with it. Control keeps no separate view of a report under an earlier mapping; export the mappings as CSV before a larger change if you need that state on file.
Connected entities consolidate in full. Minority interests are group-level manual entries.
How accounts, mappings and statement layouts relate: the Control data model in the product docs. How the group chart, eliminations, currencies and CTA run on every sync: multi-entity consolidation.
No. Each entity keeps its own system, its own close and its own period locks. Control reads every ledger through its official API, read-only by default; write-back, if you turn it on, posts only drafts an Owner or Admin approved, and eliminations and group entries change the consolidated view only.
Yes. In Control, turn on the eliminations column and drill into any group line: the elimination entries show separately from the source entries and the CTA, so the auditor can follow each one like any other posting.
Control produces the consolidated statements: the group P&L and balance sheet, every figure open to its entries. Your accounting firm prepares the statutory notes for the group accounts (konsernitilinpäätös in Finland) with them.
Control is a reporting layer, not an accounting standard. The group chart of accounts, the statement layouts and the currency translation rules are configurable for IFRS and local GAAP. Your accounting policies and your auditor decide the treatment.
Control keeps it in the EU, on Google Cloud in Finland, encrypted in transit and at rest. Finata Oy’s information security management system is ISO/IEC 27001:2022 certified. Details at trust.control.dev.
Bring last month’s group statements and tell us the systems your entities run. In 30 minutes we walk through the close on a four-ledger example group, and what setup would take for yours.
The app works best on a desktop browser.