Glossary
Quick definitions of key terms
Setup & configuration
Chart of accounts done once
ERPNext generates a starter chart when you create a company. It is a scaffold, not a design. This guide covers how to shape it deliberately before transactions make changes expensive.
How should I structure a chart of accounts in ERPNext?
Start from the statements you need to produce, not from the default tree. Decide the group structure first, keep leaf accounts few enough that people post consistently, and push analytical detail into cost centres and dimensions rather than into more ledger accounts. Account type matters more than name — it drives which report a balance lands in, and changing it after posting means restating.
Before you start
- A company record existsERPNext creates the default tree when the company is created, so the company must exist before there is anything to shape.
- Your current trial balanceWork from the accounts you actually use, not the ones your old system happened to create.
- Agreement on reporting linesWhoever signs off the monthly statements should agree the group structure before it is built.
- System Manager and Accounts Manager rolesBoth are needed to edit the account tree and company defaults.
The sequence
Read the generated tree before changing it
ERPNext builds a standard tree from the country selected on the company. Understand what is there before editing, because several accounts are referenced by default company settings and deleting them breaks those links.
Where Accounting > Chart of Accounts
Fix the group structure first
Groups determine how statements read. Build the top two levels to match the headings your statements need, then place leaf accounts underneath. Restructuring groups later is possible, but comparatives across the change become awkward to explain.
Where Accounting > Chart of Accounts > Add Child
Set account type on every leaf that needs one
Account type is what tells ERPNext how an account behaves — receivable, payable, bank, stock, tax, and so on. A receivable account without the Receivable type will not appear in ageing, and stock accounts without the Stock type break the inventory-to-ledger reconciliation.
This is the single field most often left blank, and the one that causes the most rework.
Keep leaf accounts to the number people will use correctly
Every additional expense account is a decision someone has to make at data-entry time. Where you want analysis rather than a different ledger line, use a cost centre or an accounting dimension instead.
Build the cost centre tree alongside
Cost centres carry the analytical cut — branch, product line, department — without multiplying accounts. Build the tree to match how the business is actually managed, not the org chart.
Where Accounting > Cost Center
Set company defaults
Default receivable, payable, bank, round-off and stock accounts live on the Company record. Until they are set, transactions either fail or post somewhere unhelpful.
Where Accounting > Company > Accounting Defaults
Freeze the structure and record why
Write down the reasoning behind the group structure somewhere the next person will find it. The most common cause of a messy chart is a second person extending it without knowing the original logic.
What usually goes wrong
Treating account name as the meaning
An account called Bank that is not typed as Bank will not reconcile. ERPNext reads the type field, not the label.
Mirroring the old system exactly
Carrying across accounts that existed only to work around a limitation of the previous software imports the workaround along with the data.
One account per customer or supplier
Some legacy systems required this. ERPNext uses parties against a single receivable or payable account, and duplicating that structure makes ageing unusable.
Deferring cost centres
Adding them after go-live means historic entries have none, so any comparative view has a gap that never fills in.
How to check it before you rely on it
- Run the Balance Sheet and Profit and Loss with no transactions posted — the headings should already read the way you want them to.
- Confirm every leaf account has an account type where one applies, particularly receivable, payable, bank, stock and tax accounts.
- Post one test invoice, one payment and one stock receipt in a test environment, then confirm each lands in the account you expected.
- Check the Company record shows a default for receivable, payable, bank, round-off and stock.
- Ask whoever reviews the monthly accounts to read the empty statements and confirm they would sign them.
Questions people ask
ERPNext will often let you, but the existing entries were classified under the old type. Reports covering periods either side of the change will not agree, so treat it as a restatement rather than an edit.
Cost centres suit a single primary analytical cut, usually the one the business is managed by. Dimensions suit additional independent cuts you want to report on separately. Using dimensions for the second and third cut keeps the cost centre tree readable.
Few enough that the person entering a supplier invoice picks the right one without asking. If entries are regularly miscoded, the answer is usually fewer accounts and better use of dimensions, not more accounts.
Yes, and it is the practical route for a large tree. Import the group structure first and the leaves second, because a child row fails if its parent does not yet exist.
This guide covers ERPNext configuration. It is not accounting, legal or tax advice, and it does not determine how any particular transaction should be treated in your statutory accounts.
Related guides
Want the structure reviewed before you commit to it?
A chart of accounts is cheap to change now and expensive to change after a year of postings. Send us the draft tree and we will tell you what will hurt later.
Get it reviewed