Chart of Accounts in ERP: How to Build One That Supports Financial Reporting
A chart of accounts that serves financial reporting is designed around your business, not copied from a template. It starts by classifying accounts into assets, liabilities, equity, revenue, costs and expenses, then arranging them in clear levels and codes that make posting transactions and extracting results straightforward.
Adding and coding accounts looks like a purely operational task, but its impact reaches the accuracy of financial statements, the quality of performance analysis, and comparability between periods. The structure therefore has to fit the nature of the business, avoid unnecessary expansion, and never merge unrelated items into a single account.
- Tie every account to the report or financial decision it serves, so the chart does not become a list of codes without an analytical purpose.
- Design coding levels that allow detail when needed, without creating a separate account for every operational variation.
- Test how entries roll into reports before approving the structure, and track how classification affects the reading of results.
- Put governance in place for adding, changing or deactivating accounts, while keeping historical data consistent.
1. Impact on financial reporting
The chart of accounts in an ERP is a hierarchical structure that links every journal entry to a classified account and then aggregates balances for reporting. It consists of parent and child accounts — assets, liabilities, equity, revenue and expenses — with coding levels that define the depth of detail. How the chart is built directly shapes how data is presented and analysed.
Start with the main classes
Group accounts under assets, liabilities, equity, revenue, costs and expenses. This classification produces consistent statements, instead of distributing accounts by department name only.
Tie each group to a reporting objective
Separate current assets from non-current assets, and operating revenue from other income. This separation helps the reader distinguish the resources and results of the business from unrelated items.
Choose one consistent coding scheme
A single-digit primary coding works well: assets 1, liabilities 2, equity 3, revenue 4, expenses 5. Keep the code clear and progressive, and never mix different coding models inside the same chart.
Build levels that serve analysis
In one common model, 111 is cash, 112 is receivables and 113 is inventory. A child level lets you extract balances by the nature of the account instead of settling for a total assets figure.
Give fixed assets their own detail
Another model uses 121 for fixed assets, then 1211 for buildings and 1212 for machinery. This distinguishes asset components in the report and fixes each account's position inside the classification.
Test how revenue and expenses aggregate
A four-digit model might use 4000 for revenue and 5000 for expenses. Check how accounts appear in the income statement, and confirm that sales are separated from the expenses directly attached to them.
Review report output before sign-off
Post test entries to accounts at different levels, then inspect the trial balance and the statements. The test exposes duplicate accounts or accounts placed in a class that does not reflect their nature.
Protect comparability
Fix each account's definition and use across consecutive reporting periods. When more detail is needed, add a child account under the right group so totals remain analysable.
A reference coding model
The table below follows the five-class structure common under IFRS, with third-level examples. Adapt it to your business, but do not change the meaning of a code once it has been approved.
| Class | Code | Sub-level examples |
|---|---|---|
| Assets | 1 | 111 Cash · 112 Receivables · 113 Inventory · 121 Fixed assets (1211 Buildings, 1212 Machinery) |
| Liabilities | 2 | 211 Suppliers · 212 VAT payable · 221 Long-term loans |
| Equity | 3 | 311 Paid-in capital · 321 Reserves · 331 Retained earnings |
| Revenue | 4 | 411 Operating revenue · 412 Other income · 413 Returns and discounts |
| Expenses | 5 | 511 Cost of sales · 521 Selling and distribution · 531 Administrative · 541 Finance costs |
The financial presentation is completed by the breadth of the classification: the chart spans classes that include capital, assets, inventories, financial accounts and others. These classes distinguish accounts by nature while keeping them linked to the totals that appear in the statements.
2. Impact on statements and reports
Map every account to the right statement
Direct asset, liability and equity accounts to the statement of financial position, and revenue and expense accounts to the income statement. This mapping prevents a balance from appearing where it does not belong.
Separate items by maturity
Split assets into current and non-current, and liabilities into current and non-current. This makes liquidity and future obligations readable as distinct lines instead of hiding them inside one total.
Structure equity to track movements
Keep capital, reserves and earnings in distinct accounts. Separate retained earnings from the profit of the period so equity movements are clear when the statements are prepared.
Break revenue down by source
Separate operating revenue from other income, and distinguish sales from returns and discounts. This supports reading net operating revenue instead of merging unrelated elements into one line.
Tie costs to the operating model
In manufacturing, separate direct labour and absorbed indirect production overhead from production operating expenses. This allows production cost to be analysed and compared with the revenue it generates.
Group expenses so they can be analysed
Separate selling and distribution from administrative and finance costs. When a line rises, the report can identify the source without manually re-sorting entries.
Test classification against the standards
Use IFRS as the reference for checking whether the chart matches the required presentation of line items. One common classification model spans classes that include capital, assets, inventories and financial accounts.
Verify statements before approving changes
Review the trial balance, then trace each group into the statement of financial position and the income statement. If you reclassify an account, compare reports before and after and confirm balances stay in the correct class.
3. Mistakes in setup and maintenance
Do not start by copying a ready-made chart
Accounts differ with the business and its operating cycle, and moving a trading company's structure into a manufacturer can merge unrelated costs. Tie each group to a real transaction flow, then test its position in the reports.
Avoid runaway detail
A separate account for every customer or transaction scatters follow-up, while an account that is too broad hides the drivers of change. Set the level by the analysis you need, and use customer records or cost centres when they serve the purpose.
Fix coding rules before data entry
Common mistakes include similar codes for different classes or changing what a code means between departments. Document the meaning of each level, and review a sample of accounts to confirm the code follows the same classification.
Never delete accounts used in prior entries
Deleting an account that carries historical transactions confuses balance reviews and period comparisons. Deactivate the inactive account and create a replacement when needed, documenting the change date and reason.
Check for duplicates before adding an account
Creating a differently named account for an existing expense splits the total across two lines. Search the chart for similar accounts, compare descriptions and usage, then decide whether to merge or add based on a clear reporting purpose.
Set a review cycle that matches change
Practice suggests reviewing the chart quarterly, and every six months for fast-changing businesses. Stable companies can review annually, with an immediate review whenever the business model changes.
Test the impact of every change before rolling it out
Compare the trial balance and reports before and after the move, and confirm balances stay in the right classes. Testing exposes accounts that moved incorrectly or lost their link to a financial process.
Include local tax requirements in the review
The chart must reflect local tax requirements: btw (VAT) in the Netherlands and the EU — including btw-aangifte (VAT return), ICP/opgaaf intracommunautaire prestaties (intra-community supplies report), and verleggingsregeling (reverse-charge mechanism) — plus ZATCA requirements when operating in Saudi Arabia. Document how those requirements affect classification, and update the catalogue when operations or reporting structures change, using Belastingdienst as the reference authority.
4. Mistakes in the account catalogue
Do not mix parent and child levels
Placing detailed expenses at the parent level prevents clean aggregation. Create a parent expense account, then add children that express the nature of the spend, keeping a clear relationship between levels.
Do not design for today's state alone
A new activity may add accounts that are hard to fit later. Before approving the structure, map the revenue, purchasing, inventory and collection flows, then assign a logical position to each expected transaction type.
Avoid generic names that blur across departments
An account called "other expenses" makes entry analysis imprecise. Use descriptions that state the purpose, such as equipment maintenance or sales transport, and fix the naming convention in the catalogue.
Balance the number of levels against the analysis you need
Small companies may need three levels, while mid-sized and large ones need four or five. Do not add a level that produces no useful report, and do not cut what branch or business-line analysis requires.
Separate similar accounts with different natures
Merging cash with receivables hides the difference between what you hold and what you are owed. Review the nature of each balance and set its classification before migrating opening balances into the system.
Never adopt coding without documented rules
Inconsistent code length or ordering leads to duplicate accounts and poor search. Record the meaning of each segment, apply the same rule to new accounts, then test it against a sample of entries.
Link classification to local accounting requirements
The chart must respect tax requirements in your jurisdiction — btw in Europe (including btw-aangifte, ICP/opgaaf intracommunautaire prestaties, and verleggingsregeling), ZATCA in Saudi Arabia — and you should review how classification affects reports and records, and document who owns updating it when operations change, with Belastingdienst as the reference authority.
Test the catalogue before running live entries
Enter transactions that represent sales, purchasing, collection and payments, then review where they land in the trial balance and statements. To apply this review to the structure inside the system, start by configuring the chart of accounts in your ERP to match your workflows and required reports.
5. How to apply this inside your ERP
S&R CoreSync For Intelligent Solutions helps organisations configure their ERP through the ERP Setup service when the accounting structure and financial procedures need to become an organised setup inside the system. Work starts by defining the required accounts, linking them to posting and reporting flows, then aligning the configuration with how the business operates — including VAT, SEPA settlement and international reporting requirements.
Organisations still establishing their system may fit the Core Starter package; the choice depends on the scope of configuration and operating priorities. Where the challenge is inconsistency between accounts, entry flows and report output, the priority is reviewing the setup and accounting mapping before expanding usage.
When the transition has to be executed inside the system, S&R CoreSync delivers full ERP configuration and synchronisation (Full ERP Sync) alongside Core Starter. The right path depends on scope — whether configuring the system or aligning its components with financial operations. The goal is an account structure that can be managed and extended, connected to reporting needs and management decisions.
6. Frequently asked questions
How many levels should a chart of accounts have?
Small companies usually need three levels; mid-sized and large ones need four or five. The rule is that every level must produce a report or an analysis you actually use. If it produces neither, it is overhead without value.
Should account codes be numeric or alphanumeric?
Sequential numeric codes are the most common because they sort and roll up cleanly inside the system. What matters is that length and meaning stay consistent, the rule is documented, and every new account follows the same pattern.
What should I do with an account that already has posted entries?
Never delete it. Deactivate it for new postings and create a replacement if needed, documenting the change date and reason. Deleting breaks balance reviews and period comparisons and destroys the audit trail of historical entries.
What is the difference between the chart of accounts and the account catalogue?
The chart of accounts is the hierarchy and coding inside the system. The account catalogue is the documented register that explains what each account means and how it may be used. The first is operational, the second is governance and audit reference.
Related articles
Ready to build a structure that supports decisions?
Three paths by stage: system setup, full synchronisation, or the starter package.