ERP implementation, planned for a small business.

A plan sized for a small business.

Most implementation plans online are written for large companies: steering committees, months of workshops, consultants on site. A trading firm with ten people does not need that, and paying for it does not make go-live safer.

A small business needs the same steps in the right order, done properly. Each step depends on the one before. Skip the data cleaning and the migration goes wrong. Skip the training and people drift back to Excel.

The eight steps below work for any ERP. How PrimoERP runs them is in its own section near the end.

Step 1: decide the scope and one owner.

Write down what goes into the ERP on day one and what waits. A good first scope is the work that creates most of your entries: sales, purchase, stock and accounts. Payroll, manufacturing or a shop counter can follow.

Then name one owner, usually the business owner or a senior person in accounts, because most decisions are about how the business works. The owner decides, chases the data and signs off each step. Agree a rough go-live date now, too.

• Which companies, GSTINs, branches and warehouses go live first.
• Which modules start on day one, and which come later.
• Who will use the system, and what each person needs to see.
• Which reports the owner and the accountant need every month.

Step 2: clean the master data.

Master data is the lists everything else is built on: customers, suppliers, items and the chart of accounts. If these are wrong, every invoice built on them is wrong. It is usually the longest step, and the one most often rushed.

Export each list from Tally, BUSY or Excel into a spreadsheet and fix it there, before anything is imported: remove duplicates, fill gaps, agree one way of naming things.

• Customers: legal name, GSTIN, state, addresses, credit days and limit.
• Suppliers: legal name, GSTIN, PAN and any TDS section.
• Items: one name each, the unit, HSN or SAC code, GST rate, and batch or serial tracking if needed.
• Chart of accounts: the ledgers you really use, with old and duplicate ones merged.
• Opening balances: every ledger as at the cutover date, from the old trial balance.
• Open items: unpaid customer invoices and supplier bills, one by one, not only the totals.
• Opening stock: quantity and value of each item, in each warehouse.
• Employees, if payroll goes live: salary structure, PF and ESI details, bank account.

Step 3: set up tax, numbering and approvals.

Configuration tells the ERP how your business works. Do it before the data goes in: some settings are hard to change after the first entries. Write each decision down, so the reason is on paper, not in one person’s head.

• Company details, the financial year and the date the new books start.
• Each GSTIN, with its state and address, and how place of supply is worked out.
• GST rates, TDS sections, and e-invoicing if your turnover requires it.
• Numbering for invoices, bills and vouchers for each GSTIN, agreed with your accountant.
• Warehouses and branches, and which ones each user can see.
• Users and roles: who can create, who can approve and who can only view.
• Approvals: purchase orders above an amount, large discounts, sales beyond a credit limit.

Step 4: move the data, then reconcile it.

Import the master data first, then opening balances, then open invoices and bills, then opening stock, so each step can be checked against the one before.

Then reconcile. Put the old system’s reports next to the new one’s, as at the cutover date, and compare them line by line. A difference found now takes minutes to fix; found during a GST return, it takes days. Ask your accountant to sign off the trial balance: it proves the books came across whole.

Step 5: train each team on their own screens.

People learn an ERP by doing their own job in it, with their own data. A tour of every module for everyone is forgotten by Monday.

Train each team separately, on the migrated data, close to go-live. Give each person three or four of their daily tasks to do from start to finish, and write down their questions: those become the notes for go-live week.

• Sales: quotes, orders, invoices and customer balances.
• Stores: goods received, stock transfers, deliveries and stock checks.
• Purchase: purchase orders, supplier bills and approvals.
• Accounts: receipts, payments, bank matching, GST and TDS reports, and month close.
• The owner: the reports they will read each week, on their own login.

Step 6: pick a cutover date.

The cutover date is the day the new system becomes your books. The start of a month is easiest, because GST returns, TDS and most reports run by month. A quarter is easier still, and 1 April is cleanest, but there is no need to wait a year.

Going live mid-year is normal. The months before cutover stay in the old system, and the new one starts from the opening balances on the cutover date. Ask your accountant how that year’s returns and audit will use both.

Then decide on a parallel run, where both systems take every entry for a while. A week or two catches mistakes while the old numbers are there to compare. Longer doubles everyone’s work, and people stop doing it properly. Many small businesses skip it and reconcile carefully instead.

Step 7: go-live week, day by day.

Questions come fastest in go-live week. Keep it free of other projects and leave, with someone who knows the system within reach of every team.

• Day 1: close the old system to new entries. Make the first invoices, receipts and bills in the new one.
• Day 2: check the first day’s entries with each team. Fix numbering, print formats or permissions now.
• Day 3: run the first stock and receivables reports and compare them with what people expect.
• Day 4: turn the most common questions into one-page notes.
• Day 5: the owner reads the week’s reports, and the accountant checks the bank and GST entries.

Step 8: the months after go-live.

The first month close is the real test. Close it with your accountant, match the bank and check the GST reports against what you expect to file. If it closes cleanly, the implementation worked.

Over the next two or three months, watch for people working around the system: notebooks, side spreadsheets, entries rushed in at month end. Each points to a setting, report or training gap to fix.

Add the next module only once the first ones run without help. Payroll or a second branch goes in more easily on books that already agree.

A realistic timeline, in weeks.

An illustration, not a promise. It assumes the owner gives the project a few hours a week and the data is in reasonable shape. Some steps overlap: training can start while the data is checked.

Who does what.

A RACI chart lists, for each task, who does the work, who answers for it, and who is asked or kept informed. Your vendor may do more of the work; signing off stays with you and your accountant.

The go-live checklist.

Tick every line before the cutover date. If one can’t be ticked, move the date, not the line.

• Scope written down, and one owner named.
• Customer and supplier GSTINs checked; every item has an HSN or SAC code and GST rate.
• The opening trial balance matches the old one, signed off by the accountant.
• The stock summary matches, item by item and warehouse by warehouse.
• Unpaid invoices and bills add up to each customer’s and supplier’s balance.
• Numbering, print formats and approvals tested with a real document.
• Every user can log in and sees only what they should.
• Each team has done its own daily tasks in the system.
• Cutover date fixed; the old system closed to new entries from then, backed up and readable.
• Someone to call for help, every day of go-live week.

Why ERP projects fail.

When an ERP project goes wrong in a small business, the software is rarely the cause. Time, data and habits are. Each of these is cheap to fix if caught early.

• No owner: everyone is in charge, so decisions wait and nobody chases the data.
• Dirty data moved as it is: duplicate customers, wrong GST rates and missing HSN codes travel into the new system.
• Opening balances never reconciled: the error shows up months later, in a GST return or the audit.
• Too much on day one: every module and report before anyone has used the basics.
• Copying the old system exactly: Tally or Excel workarounds rebuilt in the ERP.
• A go-live date in the busiest month: year end or the festive season.
• The old system left open: people keep entering in both, and neither is right.
• No budget for setup: the licence is paid for, the work to set it up is not.

Audit trail and old records.

Two legal points shape the plan. A company’s accounting software must keep an audit trail that can’t be switched off, so ask each vendor how theirs records changes. And books must be kept for years, so the old system’s data has to stay readable after cutover.

The rules differ for a company, an LLP, a partnership and a proprietor. Ask your CA which apply to you.

• Ask each vendor to show the edit log of a changed invoice.
• Keep the old Tally or BUSY company readable, with a backup somewhere safe.
• Export the old reports as at the cutover date and file them with the sign-off.

How PrimoERP does it.

Everything above applies to any ERP. This is how we run the same steps for PrimoERP customers in India, with packages whose scope and price are on our pricing page.

We bring in your customers, suppliers, items and opening balances, then check the numbers with you before you go live. Each team learns on its own screens. We sit with you in go-live week, then stay on phone, WhatsApp and email.

Your accountant gets a login of their own, free, on top of your plan’s users, so the person who signs off the trial balance can check it in the system.