ERP Implementation Consultant, India

Where Indian ERP implementations tend to slip

Indian implementations rarely fail on software. They slip because of how the project is run around the software. The same patterns appear across manufacturers, distributors and service companies:

• Decisions waiting on the promoter. Many choices, from approval limits to pricing rules, can only be made by the owner, who is also running sales and finance. Without a structured queue, the partner configures a guess.
• Partner team changes. The consultant who ran discovery moves to another account, and the replacement relearns your business from scratch.
• Compliance left late. GST setup per registration, e-invoicing connectivity and TDS sections are treated as settings to finish at the end, when they shape masters and documents from the start.
• Customization by request. Each department asks for its familiar Tally report or format, and small changes add up to an upgrade problem.
• Branches trained last. Head office learns the system; depots and plants receive a short call a few days before go-live.

Most of these can be prevented with ownership and structure rather than more budget. That is where a client-side consultant earns their place, and it is also why ERP implementation support works best when it starts at kickoff rather than after the first missed milestone.

How I oversee the implementation partner from your side

My job is to make sure the partner builds what your business needs and agreed to, and that your team does its part on time. In practice that means a few steady habits rather than heavy process.

Each week I review progress with the partner's project manager, update the decision and risk logs, and send your sponsor a short status note in plain language. Before any area is configured, I take process owners through the design and get a clear sign-off, so the partner is not left guessing. When the partner demos a completed iteration, I check it against the requirement list and note anything that drifted.

On the compliance side, I review how each GSTIN is set up, which document series are used per registration, how place of supply is determined, how HSN and SAC codes are maintained and how TDS sections are linked to vendors. I also confirm who owns the connection to the e-invoicing and e-way bill systems, whether through the platform or a GST service provider, and that it has been tested end to end. Your chartered accountant confirms the treatment; I make sure the configuration matches it.

When the partner says a request is out of scope, I go back to the signed proposal and requirement list and give you a straight view, which keeps disputes short and the relationship workable.

Data migration from Tally, spreadsheets and older packages

Most Indian projects migrate from Tally, sometimes alongside spreadsheets for stock or an older local package for production. The data usually needs more work than the partner's estimate assumes, and that work falls on your accounts and stores teams.

Before the first trial load, I review the extracts with your team. Ledger groups need mapping to a cleaner chart of accounts. Party ledgers often hold duplicates, inactive parties and missing GSTINs or PAN details. Godowns need translating into warehouses and locations. Stock items may have been created over years with inconsistent names and units, so we decide which to merge, retire or carry forward.

Open items need particular care. Bill-wise receivables and payables, advances, pending TDS, post-dated checks and goods in transit between branches all have to land in the new system as they stand at cutover. I agree with your accountant whether to bring across balances only or some transaction history, and what stays in Tally as a read-only archive for audit.

Every trial load closes with a reconciliation: trial balance by ledger, ageing by party, stock by item and location, all signed off by the people responsible for those numbers. My ERP data migration page and migration checklist describe the wider method.

Cutover in India: timing, e-invoicing switch-over and payroll

Choosing the go-live date is an accounting decision as much as a project one. A start of month keeps GST periods clean. Avoid the weeks around year-end closing, when the old books are being finalized and audit work begins. I agree the date with your finance head and chartered accountant, and plan backwards from it.

Indian cutovers have a few specific steps that need a named owner:

• the last invoice raised in Tally or the old system, and the first in the new one, with document series continuity agreed with your accountant
• switching e-invoice generation to the new system without leaving any invoice reported twice or not at all
• e-way bills already issued for goods in transit at the cutover point
• pending purchase orders, job work material with subcontractors and stock in transit between branches
• payroll, which often runs in a separate HR or payroll tool, with salary and statutory journals mapped into the new ledger

I build these into a cutover checklist with timings, owners and checks, and rehearse the key steps in the test environment. On the day, I coordinate business tasks with the partner and your team. My ERP go-live support page goes deeper on cutover and the days after it.

UAT, training and hypercare across plants and branches

User acceptance testing should be run by the people who will live with the system: billing clerks, stores staff, purchase executives, plant supervisors and accountants. I write the scripts in business language and include the cases that matter in India, such as an interstate stock transfer with its tax invoice, a credit note against an e-invoiced sale, a job work return with process loss and a vendor payment net of TDS. Each defect is classified as a fix, a design gap, a training need or a new request, so the partner focuses on what genuinely blocks go-live. My ERP testing and UAT service explains the approach.

Training follows a train-the-trainer model. Key users at each location learn first and then teach their teams. The engagement runs in English, and where staff are more comfortable in Hindi or a regional language, your key users or the partner adapt the guides and deliver those sessions.

Hypercare starts on go-live day with a daily issue review, all handled remotely in Indian working hours. I treat the first month-end close and the first GST return prepared from the new system as the real test, and stay involved until both are complete. Still at the platform decision? My ERP selection work in India covers that step, and the India ERP consultant page gives the wider picture.