Your chart of accounts is a power structure
The CoA decides who can answer which question without asking permission. Design it before the ERP goes live, or spend the next five years working around it.
A chart of accounts looks like a taxonomy. It behaves like an org chart. Whatever the CoA cannot separate, no report can separate later without a manual mapping that someone maintains forever.
Structural vs analytical
Structural dimensions — entity, account, cost centre — belong in the CoA because they carry statutory meaning and rarely change. Analytical dimensions — campaign, product variant, customer cohort — belong in the reporting layer because they change constantly. Mixing the two is how a 400-account chart becomes a 4,000-account chart in three years.
- If it appears in a statutory filing, it is structural.
- If a marketing lead can invent a new value on a Tuesday, it is analytical.
- If you cannot say which it is, it is analytical until proven otherwise.
Before your ERP goes live
- 01Agree the segment model and lock the meaning of each segment in writing.
- 02Define who can create a value in each segment and what approval it needs.
- 03Map the legacy chart to the new one at the transaction level, not the balance level.
- 04Test the consolidation and the statutory pack on the new chart before cutover.
The CoA is the cheapest thing to design well and the most expensive thing to change later. Treat it as architecture, not configuration.