ERP Business Analyst Nigeria

From tax headings to testable statements

A tender line that says "the system must handle VAT and WHT" will collect a yes from every bidder and settle nothing. For a Nigerian business, the useful version breaks tax handling into behaviors that can be demonstrated and tested. During ERP requirements gathering, I typically draft statements along these lines, then refine them with your accountant:

• each customer and supplier record holds a tax identification number where your advisor says one is required, and documents cannot be finalized without it
• withholding tax deducted by customers is recorded against the invoice it relates to, and the credit document received later is matched and stored
• withholding tax on supplier payments is calculated by category, approved and reported for remittance
• VAT on sales and purchases is posted to separate accounts and can be traced document by document
• tax codes can be added or changed without rebuilding the chart of accounts

The last point matters because tax administration in Nigeria has been changing, and a rigid setup becomes expensive to adjust. Tax advice is outside my role; your accountant confirms the treatment behind every line, and current rules should be checked with them before sign-off. What I provide is the requirement itself, complete with owner, priority and test case.

Preparing invoice data for electronic exchange

The federal tax authority has been introducing electronic invoicing, and while the detailed scope and timing are for your advisor to confirm, the direction gives an ERP project clear homework. Invoices that will be exchanged electronically need complete, consistent data, and most of that data lives in master records that are messy today.

I approach this as a data readiness exercise inside the BRD. First, I list the customer, item and document fields that an electronic invoice is likely to need, based on current guidance your advisor provides. Then I assess how well your existing records meet that standard: missing identification numbers, duplicate customers, items described inconsistently between depots, credit notes issued without reference to an original invoice. Each weakness becomes either a clean-up task before migration or a validation rule in the new system.

The BRD also describes the process around submission: who submits, what happens on rejection, how a corrected document is linked to the original and which report shows the status of everything sent. Vendors then explain how their product, or a connector, would meet those requirements. Approaches differ, which is explored product by product for Nigeria: see Zoho, Odoo, ERPNext or Dynamics 365.

Exchange rate requirements management can defend

For many Nigerian businesses, the hardest finance question after a currency movement is easy to pose and hard to settle: which rate did we use for this transaction, and why? If the answer lives in a treasury spreadsheet or in one person's memory, auditors and directors will keep asking. The ERP can carry that answer, but only if the BRD spells it out.

I write currency requirements per transaction type. For imports, sales in dollars, loan repayments and expense claims, the BRD states which rate source applies, at which point in the process the rate is captured, who may override it, what approval and evidence an override needs, and where bank confirmations and import paperwork are attached. Revaluation requirements describe which balances are revalued, how often and with what rate, while your accountant and auditors decide the policy itself.

Reporting follows. I specify how realized and unrealized differences appear, how currency effects are separated from trading margin, and what exposure report treasury needs to plan payments. These details look small in a workshop and become very large in a dispute. The method is described on my ERP business analysis page.

Depots, distributors and resilience written into the BRD

Distribution businesses in Nigeria often move goods long distances from head office or a factory through regional depots to distributors and retailers. Each handover creates a requirement: who confirms dispatch, who confirms receipt, how damaged or short deliveries are recorded, and when stock in transit becomes someone's responsibility. I map these handovers with the people who perform them and agree a standard process that still respects genuine local differences.

Commercial rules come next. Credit limits by distributor, price lists by region, promotions and rebates, returns policies and route sales each get explicit requirements, because they are where revenue leaks when systems are vague.

Finally, resilience. Depots may run on generators and mobile data, so I record which tasks must continue during an outage, how long a site can work offline, and how transactions captured during the gap are synchronized and checked afterward. Hosting location and the handling of personal information under Nigeria's data protection law are listed as open questions for your IT manager and lawyers. Together, these requirements give vendors a realistic picture of daily operations. My ERP process mapping service explains how the maps are drawn.

What you receive at the end of the analysis

The engagement closes with a document set your company owns and can reuse with any vendor: process maps for the current and target state, a requirement register with reference numbers, a business requirements document, master data definitions with clean-up actions, a fit-gap matrix for every platform you shortlisted, a migration note on the balances and history leaving today's accounting software, and acceptance scripts cross-referenced to each requirement.

Every document is in English, the language I work in. If depot teams or drivers would find training notes easier in Hausa, Yoruba, Igbo or Pidgin, your own staff can adapt the quick guides, and I keep the underlying steps simple enough to translate accurately.

Because the work is remote, decisions are captured in writing as we go. Workshops are recorded with your agreement, drafts are shared in one folder and questions are resolved in comments. That record pays off when a vendor disputes scope or a new finance lead joins halfway through the project. For selection and delivery support after the analysis, see the Nigeria ERP consultant page, or start at the Nigeria overview.