Account Mapping Across Multiple ERPs Is a Classification Problem. AI Solves It

Before any consolidation can happen, someone must establish that account 4010 in Entity A's Tripletex instance corresponds to account 6020in Entity B's Business Central. Multiply that across a group with four different ERPs, a hundred accounts per entity, and a new acquisition every quarter — and you begin to understand why account mapping alone can consume weeks of controller time.

The conventional solution is manual: a finance team member builds the mapping from scratch, comparing account structures across systems, applying judgement about which accounts represent equivalent financial reality, documenting the logic. It works. It is also slow, error-prone, and must be repeated every time a new entity joins the group.

AI approaches this differently — as a classification problem.

Rather than matching account codes or names (which vary arbitrarily across ERPs), an AI-native system analyses financial behaviour: what types of transactions flow through each account, how balances move overtime, how each account relates to adjacent accounts in the structure. Financial behaviour is consistent across ERP systems in ways that naming conventions arenot. A trade receivables account behaves like a trade receivables account regardless of whether it lives in Fortnox or NetSuite.

The platform ingests the entity's ERP data, analyses account-level behaviour, and proposes a mapping to the group chart of accounts.The controller reviews the proposal — not a blank canvas, but a structured recommendation — and approves or adjusts. What previously took days to weeks takes minutes to hours.

Critically, the human approval step is a design principle, not a concession. Account mapping decisions affect every consolidated reportthat follows. The controller's institutional knowledge — the context that AI cannot infer — belongs in the loop. AI handles the analytical heavy lifting; the controller exercises judgement and maintains accountability.

When the next acquisition joins the group, the process repeats — and the platform's accumulated knowledge of the group's financial structure improves the quality of its initial proposals over time.

→ Read the full analysis:

Why AI-Native Architecture Is the Only Way to Automate Intercompany Eliminations Across Multiple ERPs

‍