ERP Implementation Consultant, Nigeria

Where Nigerian ERP rollouts struggle

Trouble in Nigerian ERP rollouts tends to come from a familiar handful of causes, and almost all of them can be anticipated.

• Exchange rates without discipline. The rate policy was agreed in selection, but at go-live users still type their own rates, and dollar balances stop agreeing with the bank.
• Withholding tax credits lost in migration. Amounts customers deducted and still owe credit notes for are left behind in the old system, and receivables look wrong from the first day.
• A reconciliation backlog. Receipts from several banks, POS terminals and payment gateways arrive in different formats, and nobody tested the imports with real statements.
• Depots switched without a count. Stock moves across as book quantities, and the first physical check disagrees with the system.
• Implementer staff changes. The consultant who designed the setup moves to another client, and knowledge leaves with them.

Every one of them gets a named owner and a test scenario in the project plan. How those needs become written requirements is explained in my business analyst work for Nigerian companies, with platform notes on the Odoo Accounting in Nigeria and Zoho Books in Nigeria pages.

Keeping the implementer aligned with what was sold

The most useful control in a Nigerian implementation is linking payment to accepted work. If milestones are paid on dates or on hours spent, the incentive is to move on. If they are paid when your process owners have tested and accepted a deliverable, both sides focus on what actually works. I help set up that link at the start and then manage it.

For each milestone I agree with the implementer what will be demonstrated, on which scenarios and with which data. Design documents for areas such as sales, depots, purchasing and finance are walked through with your process owners in plain language and signed before configuration. Build iterations are shown on your scenarios, and I record where they differ from the requirement. Anything new is logged as a change, priced by the implementer and approved or deferred by your sponsor.

I also watch continuity. Implementers in a busy market move people between projects, so I ask for named roles, a handover note whenever someone changes, and documentation of configuration and custom work kept somewhere your company controls. Those habits cost little and protect a lot.

If a change estimate seems out of proportion, I ask for its breakdown. Any requirement that quietly disappears from the build gets flagged in writing. For the wider approach, see ERP implementation; the fractional ERP lead page describes the part-time client-side role.

Migrating from Sage, QuickBooks and spreadsheets

Nigerian companies usually move from Sage, QuickBooks, a locally built accounting system or spreadsheets maintained by finance and depot staff. Whatever the source, extraction and cleansing are planned separately, and a few data sets need particular care in Nigeria.

Dollar balances. Domiciliary bank accounts, dollar supplier balances and foreign currency loans move with their original currency amounts and the rate your accountant specifies, so the naira values and later revaluations are explainable.

Withholding tax. Amounts deducted by customers that are still awaiting credit notes, and amounts you deducted from suppliers that are not yet remitted, move as open items with their supporting references.

Distributors and credit. Customer balances, credit limits and outstanding promotions or rebates move with each distributor's terms.

Depot stock. Quantities and values per depot come from a physical count at the cut-off, not from book figures alone.

After each trial load we reconcile ledger balances account by account, customer and supplier ageing tied to the control accounts, currency balances tied to bank statements, depot stock, and sampled records traced to their source documents. Every difference is explained and assigned before the next load runs. Older closed transactions normally remain viewable in the legacy system for the period your accountant recommends. My ERP data migration page and the spreadsheet migration page cover the method.

Cutover across banks, channels, depots and payroll

A Nigerian go-live involves more parallel switches than most. The runbook lists each one with who does it, when, and how completion is verified.

• Banks and payment channels. Every bank, POS provider and payment gateway is listed with how statements, settlement reports and payment files reach the new system. Receipts arriving during the switch are tracked so none are posted twice or missed.
• Electronic invoicing. Where the business falls under the tax authority's electronic invoicing arrangements, the connection is tested end to end with real invoice types, credit notes and rejections before go-live. Your tax advisor confirms the current requirements.
• Payroll provider handoff. Payroll and employee tax and pension deductions usually stay with the provider. Their salary journal is matched to the new accounts, departments and locations, then proven with an actual pay run before cutover.
• Depots. Depots often switch in a planned sequence rather than all at once, each with a stock count, user access checked and a supervisor on hand.
• Power and connectivity. The cutover window has backup power confirmed at key sites, a fallback way to record sales if a link fails, and a clear rule for entering those records afterwards.

My ERP go-live support service describes the full cutover approach.

Testing in real conditions, training and hypercare

UAT for a Nigerian rollout covers the scenarios finance and operations actually face. Finance tests invoices to customers who deduct withholding tax, supplier payments with deductions, dollar purchases at the documented rate, and statements from each bank and channel. Operations test depot transfers, deliveries and credit holds, including with the connection cut and restored. Each scenario is run by the people who will own it, and each issue is sorted with the implementer into real defects, design gaps, training needs or new requests.

The engagement runs in English, which is also the working language of most Nigerian finance and head office teams. For depot and warehouse staff, short task guides and recorded walkthroughs that key users, or a local partner, put together usually work best, and supervisors can explain them in whatever language their teams prefer. I check that material against the agreed processes.

Hypercare follows go-live: one issue log everyone can see and a brief call each day during the overlap between Nigerian and Indian working hours, kept up until the first close, VAT figures and withholding schedules reconcile. At that point your internal owner takes over, supported by documentation and a list of later improvements. Testing practice is described under ERP testing and UAT. Still choosing a platform? Start with the Nigerian ERP selection page or the Nigeria overview. Everything is delivered remotely; visits happen only by arrangement.