Mon – Sat: 9:00 AM – 7:00 PM IST
Finance

What is a chart of accounts?

The structure every financial report is built on — and the one design decision that is genuinely hard to reverse.

In short

A chart of accounts is the structured list of accounts used to classify financial transactions. Modern ERPs usually implement it as segments — company, cost centre, natural account, project, and so on — combined into a code. The natural account says what happened; the other segments say where and why.

Why It Matters

Why this matters in practice

Nearly every reporting limitation traces back to the chart of accounts. If cost cannot be analysed by product line, it is usually because no segment captures product line. Adding one later does not populate history, so comparatives break. This is why it is designed before configuration and why rushing it is expensive in a way that is not obvious at the time.

Determines what every report can and cannot show
Segments separate what happened from where and why
Adding a segment later leaves history unpopulated
Depth should follow reporting need, not completeness
How It Works

How it works in practice

Decide the segments

Company, cost centre, natural account at minimum. Product, project, region or channel where the business manages by them.

Design the natural accounts

Detailed enough to report, coarse enough to post consistently. If posters cannot choose reliably, the detail is false precision.

Set validation rules

Not every combination is valid. Cross-validation rules stop meaningless codes being created.

Plan the hierarchy

Roll-ups for reporting, defined so statutory and management views both derive from one structure.

Document and govern

Who may create an account, and on what basis. Ungoverned charts grow accounts nobody can explain.

Worked example

A worked example: when a dimension should not be an account

A business creates separate expense accounts for each department: Salaries — Sales, Salaries — Production, Salaries — Admin, and so on. With eight departments and forty expense types, the chart runs to several hundred accounts.

It works, and it scales badly in a specific way. Adding a ninth department means creating forty new accounts. Reporting salaries across the business means summing eight accounts. Any analysis that crosses the two dimensions requires either a hierarchy that mirrors every combination or a spreadsheet.

The structural answer is to make department a separate segment rather than part of the natural account. Forty expense accounts and a department segment express the same information, and adding a ninth department becomes one new segment value. This decision is made at implementation and is painful to reverse afterwards, because changing it means remapping history. It is worth more design time than it usually gets — the question to ask of every proposed account is whether it describes what was spent or who spent it.

Key terms

The vocabulary, briefly

Term What it means
Natural account What was spent — salaries, rent, materials. The core segment.
Segment A dimension of the account code, such as cost centre, department or location.
Account hierarchy The rollup structure used for reporting, which can differ from the posting level.
Control account An account whose balance is maintained by a sub-ledger rather than by direct posting.
Statutory mapping The link from your accounts to the format required by regulators.
What Goes Wrong

Common mistakes worth avoiding

Too much detail

Hundreds of near-identical accounts get posted to inconsistently, which destroys the comparability the detail was meant to give.

Encoding organisation structure into natural accounts

Reorganisations then require renumbering. Use a separate segment.

No cross-validation

Invalid combinations accumulate and have to be cleaned up at year end.

Designing it without the people who report

The users of the output should shape the structure, not only the people posting to it.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Accounts actually posted to Unused accounts are clutter that makes coding errors more likely.
Postings to suspense or miscellaneous Coding difficulty. High volumes mean the chart does not fit the business.
Reclassification journals Corrections after posting, which usually indicate ambiguous account definitions.
Depth of reporting hierarchy Very deep hierarchies tend to indicate dimensions that should be segments.
FAQ

Questions we are asked about this

Enough that every meaningful category is distinguishable and no more. If two accounts are regularly confused by posters, they should probably be one.
Adding accounts is routine. Adding a segment or restructuring is a major exercise affecting history and comparatives, which is why the initial design deserves real time.
Enough to distinguish things you actually report on separately, and no more. Hundreds of expense accounts in a mid-market business usually signals that dimensions have been built into the natural account rather than into segments. A practical test: if you never produce a report that shows one account separately, it probably does not need to exist, and its presence increases the chance of miscoding.
You can add accounts easily. Restructuring segments or renumbering is substantially harder, because historical postings must be remapped for comparatives to work and the mapping is rarely one-to-one. This is why the structure deserves disproportionate design attention at implementation — it is one of the few decisions that is genuinely expensive to revisit.
Many organisations maintain one posting chart with mapping to statutory formats, which keeps a single source of truth. Where local statutory requirements prescribe a specific chart structure, a parallel chart may be necessary. Either way, the mapping between them must be maintained as a controlled artefact rather than living in a spreadsheet, because an unmaintained mapping produces statutory reports that quietly stop reconciling to the ledger.
Give them dedicated accounts, separated by counterparty, so elimination at consolidation is mechanical rather than investigative. Intercompany balances posted to general trade accounts are among the most time-consuming things to unpick at group close, because you are trying to identify which portion of a receivables balance relates to another group entity after the fact rather than at the point of posting.
Related

Where to read next

What is SAP FICO?

Read more

What is period close?

Read more

What is sub-ledger accounting?

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.