ERP Core ConceptsGlossary

What Is Chart of Accounts?

Also known as: COA, account structure

Definition

A chart of accounts is the organized list of accounts a business uses to classify every financial transaction, typically structured with segments for natural account plus dimensions such as site, department, product line, or project.

Chart of Accounts Explained

A chart of accounts has two dimensions of design. First is the natural account list, grouped into assets, liabilities, equity, revenue, and expense, usually with numeric ranges reserved per group so an account number immediately signals its type. Second is the segment structure, which adds the contextual dimensions the business needs to slice results: site, department or cost center, product line, project, and sometimes customer channel. A common structure looks like account-site-department, though enterprise systems support many more segments.

The central design tension is granularity. Too few accounts and you cannot answer basic management questions without manual analysis. Too many and every posting becomes a judgment call, coding errors multiply, and the trial balance becomes unreadable. The reliable rule is to add a natural account only when the distinction requires different accounting treatment or appears on a financial statement line, and to use segments or subledger detail for everything else. Analysis needs are almost always better served by dimensions than by proliferating accounts.

Multi-entity and multi-site organizations face a further decision: a single global chart with entity segments, or separate local charts mapped to a group chart for consolidation. A single global chart makes consolidation trivial but forces every entity to accept the same structure, which can conflict with statutory reporting requirements in some countries. The mapped approach preserves local flexibility at the cost of maintaining and auditing the mapping. Most mid-market manufacturers with domestic sites choose the single chart; multinational groups usually end up with mapping.

Restructuring a chart of accounts after go-live is genuinely expensive. Historical data must be remapped for comparability, every report and allocation rule must be revised, integrations that post to hard-coded accounts break, and audit trails become harder to follow across the boundary. Government contractors face additional constraints because indirect cost pools and allocation bases must remain consistent and defensible across periods. This is why chart design deserves disproportionate attention during implementation rather than being treated as a configuration detail.

Why It Matters

  • The chart of accounts determines what management reporting is possible without extracting data to an external tool.
  • Segment design sets whether you can measure profitability by site, product line, or contract natively.
  • Restructuring after go-live requires remapping history and rebuilding every report and allocation, so early decisions are effectively permanent.
  • For government contractors, chart structure directly supports indirect rate pools and incurred cost submissions.

In Practice

A frequent gotcha: an implementation copies the previous system chart verbatim, including 40 legacy accounts nobody has used in five years and three accounts named variations of miscellaneous expense. Postings scatter across them and the expense analysis is useless. Cleanse the chart before conversion, and require a documented purpose for every account carried forward.

Frequently Asked Questions

How many accounts should a chart of accounts have?

There is no correct number, but most mid-market manufacturers operate well with 200 to 600 natural accounts plus segments. Add an account only when the distinction requires different accounting treatment or appears separately on a financial statement. Use segments for site, department, and product line analysis rather than creating parallel account ranges for each.

Can you change the chart of accounts after go-live?

You can, but it is costly. Historical balances must be remapped so year-over-year comparisons remain valid, every financial report and allocation rule needs revision, and integrations that reference specific accounts will break. Adding accounts is straightforward; changing the segment structure is close to a re-implementation of the financial module.

Working with Chart of Accounts in a live environment? Our engineers do this every day - and our AI agents automate most of it.