Choosing and implementing an ERP system without the pain

An ERP system brings finance, sales, purchasing, stock and reporting into one place. Done well, month-end becomes routine, stock figures can be trusted and managers see the same numbers. Done badly, it becomes an expensive system that everybody works around.

The difference is rarely the software. It is how the system is chosen and implemented.

Why ERP projects stall

• Unclear processes. If nobody can describe how an order becomes an invoice, the system cannot be configured to do it.
• Messy data. Duplicate customers, inconsistent product codes and unreconciled balances move straight into the new system.
• Too much customisation. Rebuilding old habits in new software adds cost, delays and upgrade problems.
• Too little training. Staff who are unsure of the system fall back on spreadsheets.
• No owner. Without a senior person who makes decisions, every question waits.

Choosing a system

Start with your requirements, not a product demonstration. Write down the processes the system must support, the reports management needs and the systems it must connect to. Then compare a short list on:

• Fit: how much of your process works without customisation;
• Local requirements: VAT and withholding tax, naira and foreign-currency handling, local payment and banking integrations, and NRS e-invoicing;
• Total cost over several years: licences, hosting, implementation, support and upgrades;
• Support: who will help you after go-live, and how quickly;
• Room to grow: more users, entities, branches and modules later.

Ask each vendor or partner to show your real scenarios, not their standard demonstration.

Implementation habits that work

Phase the work

Start with the core: finance, sales and purchasing. Add stock, production, CRM or payroll in later phases, once the foundations are stable.

Clean the data first

Agree a single list of customers, suppliers and products, fix tax IDs and codes, and reconcile opening balances before migration. Clean data is also essential for NRS e-invoicing, where invoices with missing or wrong buyer details are rejected.

Configure before you customise

Use standard features wherever they can do the job, even if it means adjusting a process. Keep customisation for what genuinely sets you apart.

Test with real scenarios

Run complete cycles in a test environment: a quote to cash, a purchase to payment, a stock count, a month-end. Involve the people who will do the work.

Train by role

Short sessions for each role, with simple guides for the tasks people do every day, are worth more than one long overview for everyone.

Plan the cut-over

Pick a quiet date, freeze changes in the old system, move closing balances, check them, and have support on hand for the first weeks.

E-invoicing changes the timeline

With the Nigeria Revenue Service rolling out e-invoicing in phases, your ERP or accounting system increasingly needs to produce structured invoice data and exchange it with the NRS platform. If you are choosing or upgrading a system, make e-invoicing support part of the requirements and the test plan from the start.

A short checklist

1. A senior owner who can make decisions.
2. Written requirements and real test scenarios.
3. A short list compared on fit, local requirements and total cost.
4. Clean master data and reconciled balances.
5. Standard configuration first, customisation only where it pays.
6. Role-based training before go-live.
7. A planned cut-over and support afterwards.