Business Central Consultant, Nigeria

Checking availability before anything else

Business Central is not offered in every country in the same way. Microsoft publishes the countries where the online service is available and which localizations it provides itself; for other countries, partners may deliver local features through apps or offer alternative arrangements. The position can change, so the first task for a Nigerian buyer is to review the availability pages Microsoft maintains and require every bidding partner to state in writing how they propose to deliver Business Central to your Nigerian entity.

The questions I put to each partner:

• Licensing route. How the subscription would be purchased for a Nigerian company, and whether that route is supported by Microsoft for your situation.
• Localization source. Whether local features come from Microsoft, from the partner's own app, from a third-party app or from configuration only.
• Coverage. What the localization actually handles: VAT reporting, withholding on payments, statutory reports, bank formats and any e-invoicing connection.
• Continuity. Who maintains the app through Microsoft's regular updates, and whether you can keep it if you later change partner.

Partners' answers often differ more than their proposals suggest. I record them side by side, so your board compares substance rather than presentation. Tax content is for your advisor to confirm, and I do not give tax advice. The wider Microsoft picture is on my Dynamics 365 consultant Nigeria page.

Posting groups that carry VAT and withholding correctly

In Business Central, posting groups decide which general ledger accounts each transaction hits. Customers, vendors, items, resources and fixed assets carry groups, and combinations of business and product groups drive revenue, cost and tax accounts. A posting setup that is designed casually leads to journals every month to move amounts to where finance wanted them.

For a Nigerian company I draft a posting group matrix with your accountant before the partner configures anything:

• General business and product posting groups separating local sales, export sales and intercompany, and goods, services and freight, so revenue and cost land in meaningful accounts.
• VAT business and product posting groups for the treatments your advisor defines, such as standard, exempt and zero-rated, with the VAT statement lines that feed the return.
• Vendor posting groups and withholding handling. Deductions on payments are not standard in every localization, so I confirm whether the proposed app handles them or whether a defined process using payment journals and dedicated accounts is needed.
• Customer posting groups distinguishing trade, related party and staff receivables, plus how customer deductions are recorded against invoices.
• Inventory posting groups by depot or location where finance needs stock values split.

Every combination is tested with sample transactions in the partner's sandbox. Each treatment is set by your tax advisor, who should also confirm it reflects the rules in force today.

Dimensions for depots, regions and channels

Nigerian distribution and manufacturing businesses usually want profit seen by depot, region, channel and sometimes product line or key distributor. In Business Central, dimensions provide this without multiplying general ledger accounts. They need a plan, because the two global dimensions and the shortcut dimensions are chosen early and are awkward to change once entries exist.

The plan I prepare covers:

• Global dimensions, typically depot or location and business line, chosen for the analyzes used most often.
• Shortcut dimensions for region, channel, salesperson or project, visible on documents and journals.
• Default dimensions on customers, items, locations and vendors, so most entries are tagged automatically.
• Value posting rules that require a dimension on specific accounts, such as revenue and direct cost, so nothing posts untagged.
• Analysis views and account schedules, now called financial reports in recent releases, that deliver the management pack from posted data.

Transfers between depots deserve particular attention. Stock moving from a central warehouse to a regional depot passes through an in-transit location, and the dimension values must follow the goods correctly so depot margins are not distorted. I script these cases for acceptance testing. The distribution industry page gives the operational context, and management dashboards covers the reporting side.

Naira books and an additional reporting currency

A Nigerian company keeps its local currency in naira, while dollar purchases, loans and group reporting often matter as much to management. Business Central allows an additional reporting currency to be set in the general ledger setup. Once set, ledger entries store amounts in both the local currency and the reporting currency, and reports can be run in either.

That sounds simple, but the choice has consequences:

• Timing. Activating it early is far easier than adding it after a period of posting, which can require a heavy recalculation and testing exercise.
• Rates. Reporting currency amounts use the exchange rates maintained in the system, so the rate source and update routine must be agreed with your accountant and recorded.
• Adjustments. Exchange rate adjustment runs affect both currencies; the method and frequency are set by your accountant, and results are reviewed before posting.
• Inventory and fixed assets carry reporting currency values too, which affects how margins on imported goods appear in dollar terms.
• Alternatives. Some groups prefer consolidation into a separate company instead; I compare both with your group finance team.

I prototype the key reports with sample data, so management sees naira and dollar views before the partner commits the design. Accounting policy remains with your accountant and auditors. The multi-currency ERP page covers the broader controls.

Reading the partner's scope document closely

This document defines what you are actually buying from a Business Central partner. It is usually long, written by the partner, and easy to sign without noticing what is assumed or excluded. I review it against your requirements and give you a written list of points to resolve before signature.

What I look for:

• Scope by process, not only by module, so it is clear whether depot transfers, withholding, customer deductions and currency revaluation are included.
• Localization and extensions listed by name, with owner, licensing basis and maintenance responsibility.
• Data migration defined by object and history depth, with who cleans, who loads and who reconciles.
• Assumptions that shift risk to you, such as availability of your staff, completeness of data or a fixed number of workshops.
• Change control, describing how new requests are estimated and approved.
• Testing, training and support after go-live, including response expectations in Nigerian working hours.

I am not a Microsoft partner and do not sell licenses or implementation, so my review has no stake in the deal size. Where Business Central looks heavier than the business needs, I say so and compare alternatives. See the Business Central overview, the proposal review page, ERP consulting in Nigeria and my Nigeria page.