Chart of Accounts Design: Structure, Segments, and Best Practices
Lightbridge ERP defines a chart of accounts as the structured list of accounts a business uses to record every financial transaction, grouped by type: assets, liabilities, equity, revenue, and expense. A well-designed chart stays lean, encodes what a transaction is in the account and who, where, and why in segments.
This guide is general information, not accounting, tax, or legal advice.
The chart of accounts is the finance data layer, not a setup afterthought.
A chart of accounts is the structured list of accounts a business uses to record every financial transaction. Each account belongs to one of five types: assets, liabilities, equity, revenue, and expense. Every posted transaction lands in an account, and the financial statements are built by summarizing those accounts, so the chart is the backbone of the general ledger. In an ERP, it is the canonical finance layer that reporting, consolidation, and every downstream integration read from.
It is tempting to treat the chart as a quick setup task, something to finish so invoicing can start. That is a mistake. The chart is one of the most consequential early design decisions a finance function makes. A lean, well-structured chart delivers faster closes, cleaner integrations, and clearer reporting. A sprawling, ad hoc chart produces reclassification during close, fragile integrations, manual workarounds, and eventually a costly redesign. The design principles below apply whether a company runs a single ledger or, later, a consolidated group.
A chart of accounts is organized into five types with reserved number ranges.
A structured numbering scheme reserves a range for each account type so accounts group logically and the chart can expand without renumbering. The ranges below are a widely used convention; the exact digits matter less than the discipline: keep types separated, group related accounts into subranges, and leave gaps for growth. The account number should encode what a transaction is, never who, where, or why.
10000-19999
Assets
What the business owns or is owed: cash, accounts receivable, inventory, prepaid expenses, and fixed assets. Assets carry a debit balance and appear on the balance sheet.
20000-29999
Liabilities
What the business owes: accounts payable, accrued expenses, deferred revenue, and debt. Liabilities carry a credit balance and sit on the balance sheet opposite assets.
30000-39999
Equity
The residual claim of owners: contributed capital, retained earnings, and distributions. Equity is what remains after liabilities are subtracted from assets.
40000-49999
Revenue
Income earned from operations. Revenue accounts should stay few in number; product line, region, or contract type belong in segments, not in separate revenue accounts.
50000-59999
Cost of goods sold
The direct cost of delivering revenue: materials, direct labor, and the direct cost of services. Kept distinct from operating expense so gross margin is readable.
60000-69999
Operating expenses
The cost of running the business: payroll, rent, software, and general and administrative spend. Grouped into subranges by function rather than split per department.
Two ranges commonly sit above operating expenses: other income and expense (in the seventy thousands) and statistical or non-financial accounts (in the eighty thousands) for units like headcount or square footage. Keep cost of goods sold cleanly separate from operating expense so gross margin reads directly off the income statement, and keep account codes stable over time so period-over-period comparison and integration mappings do not break.
Keep the account list lean; capture detail in segments and dimensions.
The single most important modern design principle is the split between accounts and segments. An account records what a transaction is. A segment, also called a dimension, records its analytical context: which department, product line, location, or project it belongs to. Instead of creating a separate meal-expense account for every team, a business keeps one meal-expense account and tags each transaction with a department segment. Instead of many revenue accounts, it keeps a small set of revenue accounts and tags product line or region as a dimension.
This lean-account, rich-dimension design reduces account sprawl, simplifies maintenance, and improves reporting flexibility. A new team, product, or location adds a segment value, not a wave of new accounts, so the business can change without redesigning the chart. Because the account structure stays stable, integrations map once and keep working, and a data warehouse or reporting layer reads a consistent model. The illustrative example above (one expense account plus a department segment) is generic; the point is the pattern, not any particular set of accounts.
Most chart of accounts problems trace to a few recurring mistakes.
The failure modes below are predictable, and each has a straightforward fix rooted in the same principle: keep accounts lean and stable, move changeable detail into dimensions, and govern who can change the structure.
Account proliferation
Encoding department, product, or location into the account name, so one meal-expense account becomes a dozen. Every new team, product, or site then forces new accounts. The fix is a lean account list paired with segments.
Over-segmented revenue
Splitting revenue into many accounts to capture product or customer detail. This makes revenue recognition harder and pricing-model changes painful. Use a small set of revenue accounts and capture the detail with dimensions.
Dimensions inside the account number
Embedding who, where, or why into the numbering scheme. An account number should represent what a transaction is. Location, department, and project belong in segments so the number stays stable as the business changes.
No room to grow
Tightly packed numbering with no gaps, so adding an account means renumbering. Leaving gaps in each range lets the chart expand without disturbing history or breaking downstream integrations.
Unstable account codes
Renaming or renumbering accounts as the organization changes. This breaks period-over-period comparison and integration mappings. Keep account codes stable and move changeable attributes into dimensions.
No governance owner
Letting any user create accounts on demand, which produces inconsistent, duplicate, and orphaned entries. Define who can add or modify accounts and segment values, and document the policy.
Governance ties these together. Define who can create or modify accounts and segment values, document the policy, and obtain stakeholder sign-off before the chart goes live. A chart that anyone can edit on demand drifts into inconsistency within a few quarters, and cleaning it up later is far harder than designing it well once.
Modern ERP platforms implement segments as native tagging fields.
Every major ERP supports the lean-account, rich-dimension model, though each names it differently. NetSuite implements Department, Class, and Location as native segments and supports custom segments for further dimensions, so a single account carries analysis across many axes without extra accounts. Microsoft Dynamics 365 uses financial dimensions, Sage Intacct uses dimensions, and Oracle and SAP use a segmented account string or coding block. The concept is the same everywhere: classify with accounts, analyze with dimensions.
Lightbridge ERP is an independent, vendor-neutral ERP advisory firm and a former NetSuite partner. The NetSuite feature descriptions here reflect public Oracle NetSuite product documentation, not any insider arrangement, and Lightbridge accepts no vendor kickbacks or reseller quotas, so a platform recommendation follows fit rather than commission. When NetSuite is the chosen platform, Lightbridge configures the chart and its segments in-house with NetSuite-certified engineers on staff; for other platforms, it designs the structure and provides program governance while vetted partners execute. Whichever platform a business runs, the right structure is decided during a vendor-neutral ERP selection, so the chart is designed before the system is configured, not retrofitted after.
Design the chart of accounts for consolidation before the group needs it.
Even a single-entity company should design a chart that anticipates growth into a group. A consolidation is only meaningful when every entity classifies revenue, expense, assets, and liabilities the same way, so a consistent chart is the precondition for a clean rollup. Best practice is a global chart-of-accounts template reused across entities, with consistent numbering and a clear separation between operational activity and intercompany balances. Building that in early avoids a painful re-mapping later.
This guide covers the design of the chart itself. Standardizing charts across multiple legal entities, translating currencies, and rolling entities up into consolidated statements is the subject of the Lightbridge ERP guide to multi-entity accounting, and the removal of activity the group owes to itself is detailed in the intercompany accounting guide. Lightbridge ERP operates to ISO 27001 and SOC 2 controls, with certification in progress, and designs charts that stay stable as an organization scales from one entity to many.
Lightbridge ERP designs a chart of accounts that scales without redesign.
A chart of accounts is easy to set up quickly and expensive to fix later. Lightbridge ERP is an independent, vendor-neutral advisory firm whose senior finance professionals (CPAs, controllers, and former CFOs) design charts that reflect how a business actually operates and how leadership evaluates performance, not a generic template. The design leads with decision-making: which costs support revenue, how R and D, cost of goods sold, and operating expense separate, and which dimensions carry the analysis.
Because Lightbridge accepts no vendor kickbacks and no reseller quotas, the platform recommendation follows fit, and the chart is designed before any system is configured. For a broader program, ERP consulting and a structured ERP selection set the foundation, and ERP implementation puts the chart into the system with its segments and governance intact. This page is general information, not accounting, tax, or legal advice.
Chart of accounts design: frequently asked questions
- What is a chart of accounts?
- A chart of accounts is the structured list of accounts a business uses to record every financial transaction. Each account is grouped into one of five types: assets, liabilities, equity, revenue, and expense. The chart is the backbone of the general ledger and the finance data layer of an ERP, because every posted transaction lands in an account and the financial statements are built by summarizing those accounts. A well-designed chart stays lean and consistent so reporting, consolidation, and integrations all work from the same authoritative structure. This guide is general information, not accounting, tax, or legal advice.
- What are the main account types in a chart of accounts?
- A chart of accounts is organized into five account types. Assets are what the business owns or is owed. Liabilities are what it owes. Equity is the residual claim of owners after liabilities are subtracted from assets. Revenue is income earned from operations. Expenses are the costs of earning that revenue, usually split between cost of goods sold and operating expenses. Assets, liabilities, and equity form the balance sheet; revenue and expense form the income statement. A numbering scheme reserves a range for each type so accounts group logically.
- How should account numbers be structured?
- A common approach reserves a numeric range for each account type: assets in the ten thousands, liabilities in the twenty thousands, equity in the thirty thousands, revenue in the forty thousands, cost of goods sold in the fifty thousands, and operating expenses in the sixty thousands. Related accounts are grouped into subranges within a type. Leave gaps between accounts so new ones can be added without renumbering, and keep the numbers stable over time. The account number should represent what a transaction is, not who, where, or why, because those belong in segments.
- What is the difference between an account and a segment?
- An account records what a transaction is: a meal expense, software revenue, a fixed asset. A segment, also called a dimension, records the analytical context: which department, product line, location, or project the transaction belongs to. The best-practice design keeps a lean set of natural accounts for classification and captures changeable detail through segments for analysis. That way a single expense account works across the whole business while segments identify cost ownership, so the chart does not sprawl every time a new team, product, or location is added.
- Why use dimensions instead of more accounts?
- Using dimensions instead of adding accounts keeps the chart of accounts small and stable while still allowing rich reporting. If you encode department, product, and location into account names, the account count multiplies with every new team, product, or site, and reporting becomes rigid. With dimensions, one revenue account and one expense account serve the whole business, and you slice results by any dimension without redesigning the chart. This reduces maintenance, simplifies integrations, and lets reporting adapt as the business evolves rather than forcing a reimplementation.
- How do modern ERP systems implement segments?
- Modern ERP platforms implement the segment approach as tagging fields on each transaction rather than as extra accounts. NetSuite, for example, uses Department, Class, and Location as native segments and supports custom segments for additional dimensions, so a single account carries analysis across many dimensions. Microsoft Dynamics 365 uses financial dimensions, Sage Intacct uses dimensions, and Oracle and SAP use a segmented account string or coding block. The concept is consistent across platforms: keep natural accounts lean and capture analytical detail in dimensions. Lightbridge ERP designs the structure vendor-neutral, then configures it in whichever platform a business runs.
- How does chart of accounts design affect consolidation?
- For a group with multiple legal entities, a consistent chart of accounts is the precondition for clean consolidation. If each entity classifies revenue, expense, assets, and liabilities differently, the rollup does not aggregate correctly and every close needs manual mapping. Best practice is a global chart-of-accounts template reused across entities, with consistent numbering and a clear separation between operational activity and intercompany balances. This makes consolidation faster and more auditable. The mechanics of standardizing charts across entities and eliminating intercompany activity are covered in the Lightbridge ERP guides on multi-entity accounting and intercompany accounting.
Design the chart of accounts once, correctly.
When the chart has to stay lean, stable, and consolidation-ready as the business grows, Lightbridge ERP designs it vendor-neutral and configures it in your ERP. No kickbacks, senior finance talent.