Glossary
Quick definitions of key terms
ERPNext Guides
Practical, step-by-step guides for configuring and running ERPNext. Each one covers what to set up, the order to do it in, what usually goes wrong, and how to check the result before you move on.
What are these guides for?
They are working instructions for people configuring or operating ERPNext, written from implementation experience rather than restated documentation. Each guide names the screens you work in, the sequence that avoids rework, the mistakes that are expensive to undo, and a verification step so you know the configuration is correct before the next one depends on it.
Browse the library
Grouped by the stage you are at. Setup guides assume a fresh site; operations guides assume you are live and running transactions.
Planning & budgeting
Setup & configuration
Setting up the chart of accounts
Structure the ledger before the first transaction, because almost every later report depends on decisions made here.
Read guideOpening balances and cutover
The week either side of go-live decides whether anyone trusts the numbers. Here is how to make the handover provable.
Read guideUser roles and permissions
ERPNext has several permission mechanisms that interact. Knowing which one to reach for is most of the work.
Read guideOperations
Batch and serial traceability
The choice between batch and serial is made once per item and is difficult to change. Make it deliberately.
Read guideStock reconciliation and cycle counting
Counting everything once a year tells you the size of the problem. Counting a little continuously tells you the cause.
Read guideSubcontracting and job work
Material you own, sitting in someone else's premises, changing form. The accounting is the hard part, not the paperwork.
Read guideAbout these guides
ERPNext version 15 and later on the Frappe framework. Where a screen moved between versions the guide says so. If you are on an older release the sequence generally holds even when a menu path has changed.
No. They are written so an in-house finance or operations lead can work through them. Where a step carries real risk of data loss or a statutory consequence, the guide says so plainly rather than assuming you will spot it.
Regulatory subjects such as GST returns, TDS and the labour codes are handled in separate dedicated guides, because they need review by a qualified professional before publication and are updated on a different cycle to configuration content.
Each guide carries the date it was last reviewed. Configuration guides are checked against the current ERPNext release; anything that depends on an external system is rechecked when that system changes.
Stuck partway through one of these?
If a step is not behaving the way the guide describes, the cause is usually a setting made earlier. Send us the detail and we will tell you where to look.
Ask a question