Process before screens
We sit with the people who buy, make, store, and invoice. The system is fitted to that sequence, not to a generic demo company.
Approach
A project plan your operators can follow.
ERPNext is capable on the first day of a trial. It becomes the book of record only after masters, controls, and a cutover are agreed. This is the sequence we run.
- 01
Discover
Workshops with finance, stores, sales, and production. We leave with a process map, a gap list against standard ERPNext, and a decision on what stays standard.
- 02
Design
Chart of accounts, item structure, warehouses, tax templates, price lists, roles, and approval rules are written down before anyone configures a screen.
- 03
Configure
Company, fiscal year, masters, print formats, workflows, and naming series are set in a staging site your team can already click through.
- 04
Build
Only the gaps that configuration cannot cover become custom fields, server scripts, print formats, or a small Frappe app. Each one has an owner and a test.
- 05
Migrate
Customers, suppliers, items, opening stock, and opening balances move in a trial load first. Open orders move at cutover. Full history is a separate decision.
- 06
Prove
Role-based scripts: raise a purchase, receive it, issue to a work order, deliver, invoice, and collect. Finance signs the trial balance, stores signs the stock balance.
- 07
Train
People practise on a copy of their own data, in the role they will actually use. Managers get a short close and approvals session.
- 08
Go live
A cutover checklist with owners and times: freeze the old books, load final openings, switch print formats, and run hypercare for the first month.
Who does what
| Work | Accruix | Your team |
|---|---|---|
| Process map and gap list | Accruix drafts | You correct and sign |
| Chart of accounts and taxes | Accruix proposes | Finance signs |
| Item, customer, and supplier files | You extract and clean | Accruix maps and loads |
| Customizations | Accruix builds the accepted gaps | You reject the rest |
| User acceptance | Accruix writes the scripts | Each role runs them |
| Cutover weekend | Accruix loads and reconciles | You freeze the old system |
| Hypercare | Accruix sits with the first close | You raise issues in the queue |
Rules we do not bend
Configure before you customize
ERPNext already covers most of accounting, stock, and manufacturing. Custom code is reserved for a rule the standard product cannot express.
Agree the books early
Chart of accounts, cost centers, and tax templates are signed off before transactions start. Retrofitting them after go-live is how projects stall.
Train on your data
A demo company teaches the menus. A staging site with your items, customers, and a real order teaches the job.
Go-live is a checklist
The date is the last line of a cutover plan: openings, open documents, user access, print formats, and a named person for the first close.