The official ERPNext documentation is thorough. It explains every field, every checkbox, every dropdown. If you need to know what “Valuation Method” means in an Item record, the docs tell you.
But the docs have a blind spot. They assume you already understand the mental model behind the software. They tell you what each setting does but not why you’d pick one option over another, or what order to do things in, or which decisions you’ll regret six months later because changing them means unpicking half your configuration.
This guide is about those gaps. The things that aren’t bugs or missing features, just knowledge the documentation expects you to show up with.
Before You Install Anything
There’s a question worth answering before you touch a server or sign up for hosting. What is this ERP replacing?
If the answer is “nothing, we’re starting fresh,” that’s actually easier. You have no bad data to migrate, no habits to unlearn, no legacy processes to defend.
If the answer is “a QuickBooks file from 2016, three Excel sheets the warehouse manager guards with his life, and a Google Drive folder called Accounting FINAL v2,” then you have a data problem before you have a software problem.
Spend time on this. Walk through every department and ask: what do you track right now, where do you track it, and what would break if that system disappeared tomorrow. Write down the answers. This isn’t just for data migration. It tells you which modules to set up first, which users need training soonest, and where the political resistance will come from.
The documentation won’t tell you to do this. It assumes you know what you need. Most first-time ERPNext users don’t, not because they’re incompetent but because they’ve never had to think about their business as a single connected system before.
The Mental Model That Makes Everything Easier
ERPNext is built on a framework called Frappe. Frappe has a concept at its center called a DocType. Everything in the system is a DocType. A Sales Order is a DocType. A Customer is a DocType. An Item is a DocType. The settings page for your company is a DocType called Company.
A DocType is a data structure with fields, validations, permissions, and behaviors attached to it. When you customize ERPNext by adding a custom field, you’re modifying a DocType. When you write a script that runs when someone submits a Purchase Order, you’re hooking into DocType events.
Why this matters early: it means the system is consistent in ways that aren’t obvious at first. If you learn how to customize one doctype, you can customize any doctype. If you understand how permissions work on Sales Orders, you understand them on Purchase Invoices too. The learning curve flattens once this clicks.
The docs explain DocTypes in the developer section. But you need the concept on day one, even as a non-developer, because it explains why everything in the interface works the way it does.
The First Five Things to Configure (In This Order)
Fresh ERPNext install. You’ve logged in as Administrator. Now what.
1. Company and Chart of Accounts
Go to the Company doctype and create your company. This is straightforward but the chart of accounts choice matters. Pick the right template for your country. Changing it later is possible but tedious. If you operate in multiple countries, set up a separate Company for each jurisdiction. Don’t try to cram everything into one company with creative account naming.
2. Fiscal Year and Accounting Periods
You’d be surprised how many people skip this, start entering transactions, then realize their fiscal year doesn’t match their tax reporting period. ERPNext lets you define fiscal years, and transactions are dated accordingly. Set this up before a single invoice exists.
3. Default Accounts
Under Company settings, there’s a section called Default Accounts. These tell the system which account to credit when you receive payment, which account to debit when you pay a supplier, which account inventory sits in. If you leave these blank or set them wrong, every transaction from now until you fix it will post to the wrong place. Fixing it later means correcting journal entries. Avoid that.
4. Letterhead and Print Settings
You’ll want to send invoices and purchase orders that look professional. Upload your company logo, set up your letterhead template, and configure the default print format for sales and purchase documents. Do this before you need to send your first invoice to a customer. Sending a plain-text PDF with no branding to a real client is a small thing that feels amateurish.
5. User Accounts and Roles
Create individual user accounts for everyone who needs access. Don’t share logins. The permissions system is role-based and reasonably granular. Give people the minimum they need. A warehouse worker doesn’t need access to the general ledger. A salesperson doesn’t need access to payroll. The Administrator account should be used for setup and emergencies only, not daily work. If someone leaves, disable their account immediately.
Setting Up Inventory Without Creating a Mess
Inventory is where setups go wrong most often. The system asks you for decisions upfront that ripple through every stock movement forever.
Items and Item Groups
Before creating individual items, design your item group tree. Think of it like categories in an online store. Raw Materials, Finished Goods, Trading Goods, Services. Sub-groups within those. A well-organized item group structure makes reporting and filtering easier for years. Restructuring it later means reclassifying hundreds or thousands of items.
When creating an item, the most important field you’ll hesitate on is Valuation Method. Two choices: FIFO (First In First Out) and Moving Average. FIFO tracks the actual cost of each batch and uses the oldest cost when you sell. Moving Average recalculates the average cost after every purchase. Most manufacturing businesses prefer FIFO because it reflects physical reality. Most trading businesses are fine with Moving Average because inventory moves fast. Pick one per item and stick with it. Changing it requires creating a new item and transferring stock.
Warehouses
Create warehouses that match your physical reality. Not too many, not too few. A common mistake is creating a separate warehouse for every tiny storage location. That turns stock transfers into a full-time job. Another mistake is having one warehouse called “Stores” when you actually have a raw material store, a finished goods store, a quarantine area, and a scrap area. Name warehouses clearly. Set up parent-child relationships if you have a main warehouse with sub-locations.
Opening Stock
If you’re moving from an existing system, you need to bring your current stock quantities and values into ERPNext. There’s a tool called Stock Reconciliation for this. The important part: you need to know not just how many units you have, but what they cost. Without cost data, your profit reports will be wrong from day one. Get this data from your previous system before you close it down.
The Accounting Setup People Get Wrong
Accounting in ERPNext is powerful and also unforgiving. Mistakes in accounting setup compound with every transaction.
The Chart of Accounts Should Match Your Reporting Needs
The default chart of accounts is comprehensive. Resist the urge to add accounts “just in case.” Every account you create will appear in dropdowns forever. Keep it lean. Add accounts when you actually need them, not because you might someday sell a product category that doesn’t exist yet.
Cost Centers
Cost centers let you track income and expenses by department, project, location, or whatever dimension matters to your business. Decide what you want to track before you go live. Adding cost centers later is easy. Making historical transactions retroactively use them is not.
Tax Templates
Sales tax, VAT, GST, whatever applies in your jurisdiction. ERPNext has a tax engine that handles this but you need to configure it correctly. Create a Sales Taxes and Charges Template for each tax scenario you encounter: domestic sales, interstate sales, exports, purchases from registered suppliers, purchases from unregistered suppliers. Link these templates to your items or your customers and suppliers so the system applies the right tax automatically. Manually selecting tax on every invoice defeats the purpose of having an ERP.
Payment Terms
Define payment terms templates like “Net 30,” “50% Advance 50% On Delivery,” “Due On Receipt.” Assign them to customers and suppliers. This feeds into the Accounts Receivable and Accounts Payable aging reports, which tell you who owes you money and who you owe money to. Without payment terms set up, those reports are just lists of transactions with no due dates.
Manufacturing Setup: The Module That Needs the Most Upfront Thinking
If you’re using the manufacturing module, you have more configuration to do than any other module user. Bill of Materials, Workstations, Operations, Routing. These aren’t just data entry tasks. They model your actual production process.
Bill of Materials accuracy matters more than you think
A BOM that says a finished product uses “approximately 2.5 meters” of raw material will cause problems. Stock levels will drift. Material requirements planning will order wrong quantities. Production costing will be off. Put in the effort to get BOMs accurate to the level of precision your inventory controls can actually track.
Routings are optional but transformative
A routing is the sequence of operations required to make something: Cut, then Weld, then Paint, then Pack. Each operation happens at a workstation. Without routings, you can still record production. With routings, you can track work-in-progress, measure workstation efficiency, and calculate actual labor cost per product. If you have more than five production workers, set up routings.
Workstations should reflect capacity reality
Define workstations with realistic capacity. If a machine can process 100 units per hour on paper but actually does 75 because of setup time and breaks, use the real number. Overstated capacity makes production planning useless.
Customization: When to Do It and When to Wait
The most expensive mistake in ERPNext setup is customizing too early.
When you’re new to the system, you don’t yet know what’s possible out of the box. A field you think is missing might exist on a different doctype or under a setting you haven’t discovered. A workflow you think needs custom development might be achievable with the built-in Workflow doctype and some clever automation rules.
Spend at least two weeks using the standard system with real data. Not test data. Real transactions, real customers, real items. See what genuinely doesn’t work. Then customize.
When you do customize, follow these rules:
- Custom fields are safe and easy. Add them freely.
- Custom doctypes are moderate effort. Use them when you need to track something the system doesn’t natively track.
- Custom scripts that modify core behavior are high stakes. Test them on a staging instance. Document what they do and why. Future you, or the person who maintains this system after you, will be grateful.
And never, ever customize by editing core ERPNext files directly. Use custom apps or the custom script doctype. Direct edits get overwritten on every update and turn maintenance into a nightmare.
Data Migration: The Part That Separates Success From Failure
Moving data from an old system into ERPNext is the most tedious and most important part of setup. Done badly, you import garbage and spend months cleaning it up. Done well, you start clean and stay clean.
Clean before you import
Your old system has duplicate customers, inactive items you haven’t sold since 2018, contacts with outdated email addresses, and transactions that don’t balance. Do not import any of that. Spend time cleaning the data in spreadsheets before it touches ERPNext.
Import in the right order
Dependencies matter. You can’t import sales orders before you import customers. You can’t import work orders before you import items and BOMs. The general order is: Chart of Accounts, Customers, Suppliers, Items, BOMs, opening stock, opening invoices, opening balances. For each record type, ERPNext has an import tool that takes a CSV file. Use it.
Validate after every import
Import 100 customers, then check a sample of 20 for accuracy. Are the names clean? Are the addresses complete? Are the tax IDs correct? Fix problems in the source spreadsheet and re-import. Don’t wait until you’ve imported everything to start checking. By then it’s too late.
Opening balances are a specific process
Your accountant should provide a trial balance as of your go-live date. You enter this through the Journal Entry doctype, with one side going to the appropriate account and the other side going to a temporary opening balance equity account. Once all opening entries are in, the temporary account should net to zero. If it doesn’t, something was entered wrong. Fix it before processing live transactions.
Users and Permissions: Getting This Right Prevents Drama
Permissions in ERPNext are role-based. Roles get assigned to users. Roles have permission levels on doctypes: read, write, create, delete, submit, amend, report.
Most businesses need five to ten roles. Not fifty. Resist the urge to create a unique role for every person. Group people by what they do: Sales User, Purchase User, Warehouse User, Accountant, HR Manager, System Manager.
The system comes with standard roles that are well thought out. Review them. Modify the permissions on the standard roles rather than creating new ones from scratch. It’s faster and less error-prone.
One permission that surprises new users: report access. If someone can see a doctype’s data through the report view but not through the list view, that’s controlled by a separate permission setting. Test with a dummy user account. Log in as each role and confirm they see what they should see and nothing else.
Before You Go Live: The Weekend Checklist
Going live means this system becomes the source of truth. Old systems become read-only or get turned off. Here’s what to verify first.
Run a full sales cycle. Create a customer, create a quotation, convert to sales order, create delivery note, create sales invoice, record payment. Does everything flow? Does the accounting hit the right accounts? Does inventory decrease correctly?
Run a full purchase cycle. Create a supplier, create a purchase order, create purchase receipt, create purchase invoice, record payment. Same verification.
Check tax reports. Generate your main tax report (VAT return, GST filing, sales tax report) and compare it to a manual calculation. If the numbers don’t match, find out why before go-live.
Verify opening balances. Run a trial balance and compare it to your accountant’s last trial balance from the old system. They should match exactly.
Back up everything. Take a full database and file backup. Store it somewhere safe that isn’t the same server. You need a clean rollback point if something goes wrong in the first week.
Tell your team. Everyone who touches the system needs to know the go-live date, what’s expected of them, and who to ask when they get stuck. The person who gets the questions should be someone patient, knowledgeable, and available during business hours for at least the first two weeks.
What Nobody Tells You About the First Month
The first month after go-live is hard. Not because the software is broken but because everyone is learning simultaneously. Transactions take longer. Mistakes happen. Someone will enter 1000 units instead of 10 and wonder why the inventory report looks insane. Someone will submit an invoice to the wrong customer. The accountant will find an opening balance entry that doesn’t tie out.
This is normal. Build in buffer time. Don’t schedule your annual audit for the month after go-live. Don’t promise customers faster turnaround during the transition. Accept that the first month is an investment in every month that follows.
The businesses that succeed with ERPNext are the ones that don’t quit during this period. They fix the mistakes, adjust the configuration, train the confused users, and keep going. By month three, most teams are faster than they were on the old systems. By month six, they can’t imagine going back.
A Setup Is Never Really Finished
Your business changes. The system changes. ERPNext releases new versions with new features. You’ll discover reports you didn’t know existed. You’ll think of automations that didn’t occur to you during setup. The configuration you build in the first month is a starting point, not a finished product.
Set aside time for system improvement. An hour a week to review what’s working and what’s not. A half-day a quarter to explore new features or clean up stale data. An annual review before fiscal year-end to make sure everything is still configured correctly for how your business actually operates now, not how it operated when you set everything up.
The documentation covers the software. The rest is judgment, patience, and the willingness to keep refining. That’s the part this guide is for.
We help businesses set up and run ERPNext at erpnext.space. If you’re starting fresh or migrating from something else and want experienced guidance through the setup process, we’re here. We’ve seen the mistakes so you don’t have to make them.