ERP Consultant for Nigeria

VAT, withholding tax and the move to e-invoicing

For most Nigerian businesses, tax compliance work is spread across VAT, withholding tax deducted by customers or on supplier payments, and employee taxes handled through payroll. When sales invoices, supplier bills and credit notes are kept in different tools, the monthly returns depend on someone rebuilding the numbers by hand, and withholding tax credit notes from customers are easily lost.

Tax administration is also changing. The federal tax authority, long known as FIRS, has been introducing electronic invoicing in stages, and recent reform laws are reshaping how tax is administered. For an ERP, that points toward invoice data that is complete, consistent and ready to be exchanged electronically, with customer tax identification numbers captured properly and an approach for transmission errors.

I do not advise on tax. I configure tax codes and reports on your accountant's instructions, and I ask every vendor to show how its product or a connector would handle the e-invoicing requirements as they currently stand. Because details and timing can change, confirm applicability with your tax advisor before design is finalized. My ERP gap analysis puts these points into a fit-gap matrix alongside your operational needs.

Keeping a clear foreign exchange trail in naira and dollar books

Nigerian companies often keep books in naira while paying foreign suppliers, servicing loans or billing some customers in dollars. When exchange rates move, management needs to know which rate was used for each transaction, why, and what the exposure looks like today. A spreadsheet maintained by the treasury team rarely gives auditors or directors that confidence.

I treat currency as a design topic, not a setting. Requirements cover which rate source applies to purchases, sales, payroll allowances and revaluation, who may override a rate and with what approval, where bank confirmations and import documents are attached, and how realized and unrealized differences are reported. Your accountant and auditors decide the accounting policy; the ERP should apply it consistently and show its working.

Platform behavior varies. Odoo, ERPNext, Zoho and Microsoft Dynamics 365 all support multiple currencies, but they differ in how rates are loaded, how many rate types can coexist and how revaluation entries are produced. I test those details with your own scenarios during vendor demonstrations.

Distribution across depots, distributors and routes

Distribution in Nigeria tends to involve a head office, several regional depots, key distributors and van or route sales, with goods moving long distances and credit extended carefully. Without one system, stock in transit disappears from view, promotions are applied inconsistently and nobody can say quickly which customers are over their limit.

I map the whole order to cash and replenishment flow before anything is configured: how orders are taken in the field, how depots request stock, how transfers are documented, which discounts and promotions apply to which channels, and how returns and damaged goods are handled. Credit control rules and approval limits are written down with the finance team, because these are the points where losses usually occur.

Reporting is designed alongside the process. Directors typically want sales and margin by region, distributor and product, days of stock by depot and an aged debtor view that matches what credit controllers see. For deeper industry patterns, see my distribution ERP and manufacturing ERP pages, and my process mapping service.

Oil and gas services: equipment, crews and contract billing

Companies supplying the oil and gas sector with equipment rental, inspection, maintenance or specialist labor run on jobs and contracts rather than simple sales orders. Each contract can carry its own rate schedule, mobilization terms, currency and documentation requirements, and invoices are often checked line by line by the client before approval.

An ERP for this kind of business needs a clear link between the contract, the job, the equipment and people assigned to it, the time sheets and service tickets that prove the work, and the invoice. I design equipment registers with maintenance and inspection schedules, crew records with competence documents and expiry alerts, and job costing that brings in labor, parts, subcontractors and logistics so margin is visible while the job is still running.

Client portals, purchase order numbers and approval cycles shape how invoicing works, so I document each major client's requirements during discovery rather than discovering them after go-live. Related reading: my engineering ERP page and the ERP solution design service.

Power, hosting, data protection and remote delivery

Sites that depend on generators or backup power, and connections that vary through the day, influence how an ERP is hosted and used. I check which tasks must keep running during an outage, whether mobile apps can record deliveries and stock counts offline, and how the system recovers when connectivity returns. Hosting options, local or international, are compared on access, backup and support, and on what Nigeria's data protection law means for personal data about customers and staff, as confirmed by your legal advisor.

Payroll normally stays with a local provider who keeps up with employee tax and pension obligations, with journals posted into the ERP. Bank integration usually runs through payment files or an approved banking channel, designed with your treasury team.

I work remotely with Nigerian businesses. The time difference with India is a few hours, leaving a workable overlap for live workshops, and recorded walkthroughs help depot teams review designs at their own pace. The Nigeria overview summarizes the market context, my global page explains remote delivery across regions, and an ERP evaluation is a low-risk way to begin.