Chart of accounts mapping is the correspondence table that links each account of an entity's local chart to an account of the group chart, so that entities using different accounting plans can be aggregated into a single set of figures. It is the translation layer of any multi-entity group.
The need arises from a simple fact: charts of accounts are national and often company-specific. A French subsidiary posts to the plan comptable général, a German one to an SKR chart, an American one to a chart its ERP generated at implementation. The same electricity bill can carry three different account numbers inside the same group.
Mapping tables degrade in three recognisable ways, and none of them raises an error. A new account is created locally to track something specific and is never added to the table, so it falls into a default bucket or into nothing. An account is remapped during a project without the prior year being restated, so comparatives silently shift. Two local accounts of different nature are mapped to the same group account, which merges information that should have stayed separate.
What a missing mapping actually costs is visible at close. An amount that lands in a default account has to be identified, traced back to the entity that posted it, understood, and reallocated by hand, usually during the days when nobody has time for it. The error is not detected by the consolidation tool: the tool aggregates what it is given.
Phacet works above the accounting systems rather than inside them. Consolidating data from multiple ERPs reads each entity in its own format and produces a common base without a migration, while semantic matching recognises equivalent items across differently structured ledgers instead of relying on account numbers alone.
