Chart of Accounts: What It Is, Structure, and Examples

A chart of accounts organizes your financial data. It lists all accounts a company uses to record transactions and serves as a standard base for financial reporting and analysis.

The chart of accounts sorts financial information into assets, liabilities, equity, revenue, and expenses. A clear structure makes it easier to connect accounting data with management reports, budgets, and forecasts.

Read more: What Great Financial Reporting and Analytics Actually Look Like

This article covers how a chart of accounts works, how companies organize and number accounts, and what to consider when creating one.

A chart of accounts, or COA, is a list of accounts a company uses in its general ledger. Each account usually has a name, a number or code, and a clear purpose. According to AccountingTools, the chart of accounts is simply the list of accounts used in an organization’s general ledger.

The chart of accounts shows which accounts exist and how the company organizes them. The general ledger records the transactions and balances for these accounts.

For instance, a manufacturer may record these monthly costs:

Each account provides specific details. The finance team can group these accounts into broader categories, such as total direct material costs.

Companies usually group accounts by their financial purpose.

The main categories are:

• Assets
• Liabilities
• Equity
• Revenue
• Expenses

A simplified manufacturing chart of accounts might look like this:

This setup gives each transaction a clear financial category and creates a foundation for reporting.

Companies often assign each account a unique number. These numbers help teams group similar accounts and find them more easily.

There is no universal numbering system for all companies. AccountingTools says companies can choose their own numbering method, but many set aside number ranges for different account types.

Here is one illustrative structure:

A manufacturer could then add detail within a range:

It also helps to leave space for future accounts.

For example, a company might reserve numbers 5100 to 5199 for material-related costs. If a new material category is added later, the team can include it in this range.

The account itself does not need to hold every detail needed for analysis. A simple rule helps:

Accounts show what the transaction is, while dimensions add business context.

For example, a company could use one marketing expense account and analyze it by country:

• Department
• Cost center
• Legal entity
• Product
• Customer
• Sales channel
• Region

This setup lets finance analyze the same financial category in different ways without needing a separate general ledger account for each combination.

For example, a single logistics expense account can include a cost center, entity, and region. This lets finance analyze logistics costs by these factors while keeping the main account structure simple.

Companies with multiple legal entities may use different account structures for local and group reporting purposes.

A local chart of accounts meets the accounting needs of a specific entity or country. A group chart of accounts gives a common structure for reporting across the whole group.

The company links the two through account mapping.

For example:

Each entity can keep the details it needs at the local level. Meanwhile, the group receives financial data in a shared reporting structure.

This is especially helpful when several entities use different local account codes, but management still needs to compare results across the group.

As a company grows, its chart of accounts usually grows with it. New entities, departments, reporting needs, systems, and management requests all add pressure to the structure. Over time, this can create inconsistencies that make reporting slower and analysis less reliable.

The most common problems are usually not caused by one bad decision. They build up gradually as teams add new accounts, use different naming logic, or create workarounds for reporting needs.

A chart of accounts can become difficult to manage when teams create a new account every time they need a new reporting view.

This often happens when the company uses accounts to store information that could sit in a dimension instead. For example, a business may create separate travel expense accounts for sales, operations, finance, and HR. The number of accounts grows, but the financial nature of the transaction stays the same: travel expense.

A cleaner setup would keep one travel account and use the department or cost center as a dimension. This gives finance the same reporting detail while keeping the COA easier to maintain.

Too many accounts can also make monthly reporting harder. Similar transactions may end up in different accounts, users may choose the wrong account, and finance may need extra mapping before reports are ready.

A practical rule is to create a new account only when the business needs to track a financially distinct category, not every time it needs another reporting angle.

The opposite problem can also reduce the value of the chart of accounts.

If too many transactions sit under broad categories, finance loses the detail needed to explain performance. A large account such as Other operating expenses may include software, consulting, travel, recruitment, external labor, and legal fees.

The total balance may be correct, but the account gives little insight into what actually changed.

This becomes especially important during variance analysis. If operating expenses increase by €200,000, management needs to know whether the increase came from software costs, consulting fees, temporary labor, or another category.

The goal is to keep enough detail to explain meaningful cost drivers while avoiding unnecessary account creation.

A well-designed chart of accounts still depends on consistent use.

In larger organizations, different entities or teams may record the same type of transaction differently. One subsidiary may post software subscriptions under IT costs, while another records them under professional services. A third may use an account called administrative expenses.

These differences make group reporting harder because similar costs need extra mapping before finance can compare entities.

They can also affect planning. If actual software costs sit in several account categories, comparing them with one software budget line becomes more difficult.

Clear account definitions help reduce this issue. Each account should have a defined purpose, and users should know which transactions belong there. For larger groups, common mapping rules can also create consistency even when local account structures differ.

Accounting and management reporting often work at different levels of detail.

The general ledger may contain separate accounts for salaries, bonuses, employer contributions, and benefits. Management reporting may show all four under one line called Personnel costs.

That creates a need for clear mapping:

Without clear mapping, finance may need to group accounts manually every month. This creates extra work and increases the chance of inconsistent reporting.

A documented mapping structure also helps when the company changes its COA. If a new account is added, finance can immediately define where it belongs in management reporting.

The same logic applies to planning. Detailed actual accounts can map to broader budget and forecast lines, which keeps actual vs. plan analysis consistent.

An account chart that is good will correspond with the way your business records its transactions, prepares performance reports, and reviews its results.

Start designing your chart of accounts by reviewing your reporting needs. Then set up the account structure, dimensions, naming rules, ownership, and mappings. This ensures your chart works for both accounting and management reporting.

Start by reviewing the financial reports the business already uses.

These may include:

• Income statement
• Balance sheet
• Cash flow statement
• Management P&L
• Cost reports
• Department reports
• Budget vs. actual reports
• Group reporting packs

Next, consider how much detail each report should include.

For example, a manufacturer might need to report total logistics costs and break them down by entity, plant, or region. The chart of accounts should show the main financial category, while dimensions add the extra details.

This approach prevents the chart of accounts from becoming a mix of requests from different teams. Each account has a clear purpose in the reporting structure.

Before adding a new account, ask yourself:

Will this account help us report or analyze a financially distinct category?

If not, the information might fit better as a dimension instead of a new account.

Accounts should show what kind of financial activity is happening.

Examples include:

• Salaries
• Freight costs
• Software subscriptions
• Raw materials
• External consulting
• Marketing expenses

Dimensions should carry additional context.

Examples include:

• Department
• Cost center
• Legal entity
• Country
• Product
• Customer
• Region
• Project

For example, a logistics company can use one Freight costs account and analyze it by entity, warehouse, and region. This lets the finance team see different reports without needing separate freight accounts for each location.

Keeping accounts and dimensions separate becomes more important as your business grows. Adding too much detail to the account structure makes the chart harder to manage and update.

Once you know which accounts you need, group similar ones together.

A logical structure makes the COA easier to understand and reduces errors during posting.

For example:

• Revenue accounts sit together
• Production costs sit together
• Personnel-related costs sit together
• Commercial expenses sit together
• Administrative costs sit together

The numbering system should match this structure and leave room for new accounts in the future.

For instance, if 5100–5199 is reserved for material-related costs, the company can add new material accounts later without changing the whole numbering system.

Account names should be clear and specific.

Software subscriptions are more useful than other IT costs.

External consulting is more useful than Professional costs if consulting is a meaningful reporting category.

Clear names help users know where to post transactions and reduce mistakes or inconsistent use.

Someone should clearly be in charge of the chart of accounts.

This person reviews requests for new accounts and decides if they are needed.

The owner should also define when the company can:

• Create an account
• Rename an account
• Merge accounts
• Close unused accounts
• Change mappings
• Update account definitions

This helps avoid duplicate accounts and keeps the structure consistent. For example, if one entity requests a new software account, the owner can check whether an existing account already covers that cost. If it does, the company avoids creating a duplicate account.

Regular reviews also help spot accounts that are no longer used or that different teams use in different ways.

AccountingTools recommends regular review and approval controls to keep the chart manageable and consistent.

The chart of accounts should link clearly to management reporting and planning.

Detailed accounts often need to be grouped into broader reporting lines.

For example:

Writing down these mappings gives the finance team a single way to handle actuals, management reports, budgets, and forecasts.

It also reduces manual work during month-end reporting. Instead of deciding each month where an account belongs, the reporting structure defines the relationship.

For companies with several entities, this is even more important. Local accounts might be different, but they can still fit into the same group reporting and planning structure.

A good mapping document should answer three questions:

• What detailed account records the transaction?
• Where does that account appear in management reporting?
• How does it connect to the relevant budget and forecast line?

When these links are clear, it is easier to keep up with actual vs. plan analysis and to explain the results.

Actual results often come from accounting at a detailed account level, while budgets and forecasts may use broader planning categories.

As a result, several accounts can map to a single planning line.

For example:

Suppose the personnel cost budget for the same period was €570,000. Actual personnel costs came in €30,000 above budget.

The account detail then helps finance see what caused the difference. The team can check whether salaries, bonuses, benefits, or employer contributions made up most of the variance.

A clear mapping between the chart of accounts and planning structure makes actual vs. budget analysis easier to follow.

A useful chart of accounts starts with the financial information the business needs to report and analyze.

Keep the account structure clear, use dimensions for extra business detail, and document how accounts link to reporting and planning. The goal is to create a structure that gives finance enough detail for analysis while staying simple enough to manage as the business changes.