ERPNext implementation for Indian businesses
We set up ERPNext to hold your accounts as well as your operations. Everything sits in one database, so nobody has to spend the month-end making two systems agree.
Systems
What you get.
- Chart of accounts, cost centres and dimensions built to your reporting
- Stock, purchase and sales cycles with real approval rules
- Print formats, statutory documents and e-invoicing where it applies
- Reports that tie back to the general ledger, checked on test data before your data goes in
Proof
Who it's for
Indian manufacturers, traders and distributors who keep the books in Tally and lose the first week of every month making them agree with operations. Also teams whose first ERPNext implementation went wrong.
More on who this suits
Businesses in India that run operations in one place and keep the books in Tally, and spend the first week of every month making the two agree. They're usually manufacturers, traders and distributors with stock in more than one warehouse, a few dozen users, and a finance team that no longer trusts the operational reports.
It also suits businesses already on ERPNext whose first implementation went wrong. In that case we start by auditing what was customised and what breaks on upgrade.
What's included
Accounts built to your reportingChart of accounts, cost centres and dimensions, settled first.
We design the chart of accounts, cost centres and accounting dimensions around the reports your management actually reads. This structure limits what you can report on later, so we settle it first.
Stock, purchase and sales cyclesYour real approval rules, warehouses, batches and valuation on one ledger.
Purchase and sales flows with the approval rules you really use, warehouses, batches and serial numbers where you need them, and stock valuation that posts to the same ledger as everything else.
Statutory documentsPrint formats, GST, e-invoicing and e-way bills through India Compliance.
Print formats for invoices and delivery notes, and GST set up through the open source India Compliance app, including e-invoicing and e-way bills if your turnover requires them.
Reports that reconcileEvery report checked against the general ledger on test data.
Before your data goes in, we check every report against the general ledger using test data. If a stock report doesn't match the stock ledger, we treat it as a bug and fix it.
Migration and trainingMasters and opening balances brought across, and your users trained.
We bring across your masters and opening balances from your current system (the Tally to ERPNext migration page goes into detail) and train the people who'll use it every day.
Common mistakes we help you avoid
Changing core code
We build on ERPNext v15 and v16 without touching core, so upgrades stay routine.
Settings changed by hand in the live system
We package your setup as an app that applies itself on every deploy, so the test site and the live site stay identical.
Copying the old chart of accounts
A chart of accounts copied from the old system without asking what it needs to report.
Opening balances that don't match
Going live with opening balances that don't match, which throws off every report for the rest of the year.
Live data typed into the test site
People typing live data into the test site. We tell everyone up front that the UAT site will be wiped.
How we work
Every build runs through the same six steps, from a free call to go-live.
01
A call
30 minutes, no charge
02
Discovery
1 to 2 weeks, paid
03
Blueprint
Included in discovery
04
Build
3 to 8 weeks
05
Acceptance
1 to 2 weeks
06
Go-live and run
Ongoing
How it's priced and run
Every build follows our process. We start with a free call, then paid discovery and blueprint, then the build. Your team tests it on a separate site that gets wiped afterwards, and we go live with a runbook.
We run it as an Implementation. The scope is fixed against a signed blueprint and we bill across four milestones instead of by the hour, so you'll know the price before work starts.
After go-live, a Managed run covers support, small changes, framework upgrades (tested on a UAT site first) and regular checks that your backups actually restore.
Questions buyers actually ask.
A full ERP with data migration usually takes three to six months. The build itself is rarely what holds things up. The timeline mostly depends on how quickly the blocking questions get answered and the opening balances come in.
No. Everything specific to your business lives in your own app, in your own repository. That keeps framework upgrades routine, and any Frappe partner can read what we built.
Yes, through India Compliance, an open source app installed alongside ERPNext. We configure it as part of the build and test it against your actual invoice types.
We build on ERPNext v15 and v16. Which one we pick depends on the apps you need and when you plan to go live, and we decide that during discovery.
On Frappe Cloud in the Mumbai region with dedicated resources, so data stays in India. If you prefer your own cloud account, we set it up there and hand over the keys.
Let's start with a call.
Thirty minutes, free of charge, and you won't sit through a sales deck.