Business Central and SYSCOHADA: what vendors don't tell you

Introduction

When a company or administration in West Africa looks for an ERP, one question invariably comes up during scoping meetings: "Is Business Central OHADA-compatible?" The answer most resellers give is a quick "yes," accompanied by a chart of accounts demonstration. But this answer is incomplete, and sometimes misleading. The reality is more nuanced — and understanding it can make the difference between a successful deployment and a project that derails at the first accounting close.

OHADA and SYSCOHADA: what are we actually talking about?

OHADA (Organisation for the Harmonisation of Business Law in Africa) is a legal framework that harmonises business law across 17 African countries, including Côte d'Ivoire, Senegal, Cameroon, Gabon, and the DRC. The accounting component of OHADA is SYSCOHADA — the OHADA Accounting System — whose revised version came into force on 1 January 2018.

The revised SYSCOHADA is not merely a chart of accounts. It is a comprehensive framework that includes a structured chart of accounts in 9 classes (classes 1 to 5 for the balance sheet, 6 to 7 for the income statement, 8 for special accounts, 9 for cost accounting), specific valuation and recognition rules (notably on financial instruments, leases, and employee benefits), standardised financial statements whose format is prescribed (balance sheet, income statement, TAFIRE — the Financial Table of Resources and Uses, which is unique to SYSCOHADA and has no direct IFRS equivalent), and consolidation rules for groups.

It is on this complexity that the real question of "compatibility" plays out.

What Business Central does natively

Microsoft Dynamics 365 Business Central is a modern cloud ERP, originally designed for the European and North American market. Its strength is its flexibility: the chart of accounts is fully configurable, meaning SYSCOHADA accounts (101000, 211000, 601100, etc.) can be created without any source code modification.

Business Central natively handles general accounting with a free chart of accounts (no structure imposed by Microsoft), subsidiary accounting (customers, suppliers, banks) with automatic matching, multi-currency management with automatic conversion — essential in the WAEMU/CEMAC space where FCFA, EUR, and USD transactions coexist, VAT and taxes with configurable posting groups, analytical dimensions (up to 8 dimensions, which amply covers breakdown needs by project, donor, or department), and budget management with actual/budget comparison.

In this sense, yes, Business Central can "speak SYSCOHADA." But it doesn't speak it on its own.

What Business Central doesn't do without human intervention

Here is what sales brochures generally don't mention.

SYSCOHADA financial statements are not delivered as standard.

Business Central generates financial statements in a generic format (balance sheet, income statement). But the precise format required by SYSCOHADA — with its specific headings, prescribed subtotals, and especially the TAFIRE — does not exist as standard. They must be built, either through "Account Schedules / Financial Reports" built into Business Central, or through Power BI reports connected to the accounting module. This is configuration work that demands a deep understanding of both SYSCOHADA and Business Central.

The chart of accounts must be manually configured.

Microsoft does not deliver a ready-to-use SYSCOHADA chart of accounts in the standard localisation. Some Microsoft partners in West Africa have developed extensions (add-ons) that include a pre-configured SYSCOHADA chart of accounts, but these are not official Microsoft components. The quality and completeness of these extensions vary considerably from partner to partner.

Local tax specificities require adaptations.

Each country in the OHADA space has its own tax rules: VAT rates, withholding tax, Corporate Income Tax (BIC), business licence, etc. In Côte d'Ivoire for example, the withholding tax on non-resident service providers (7.5%) must be automatically calculated and declared. These mechanisms are not in standard Business Central — they must be configured or developed through extensions.

SYSCOHADA cost accounting (class 9) is rarely implemented.

SYSCOHADA provides for cost accounting in class 9, with reclassification accounts by nature and function. In practice, most Business Central deployments in Africa use Business Central's analytical dimensions (which are more flexible and modern than class 9) rather than faithfully reproducing the SYSCOHADA structure. This is a pragmatic choice but one that deserves to be made explicit to the client.

The real issue: the consultant, not the software

The conclusion is simple: the question "Is Business Central SYSCOHADA-compatible?" does not have a binary answer. The right answer is: Business Central is a tool flexible enough to be made compliant with SYSCOHADA, provided the consultant configuring it masters both worlds — the African accounting framework AND Business Central's technical architecture.

A consultant who knows Business Central but not SYSCOHADA will produce technically correct but non-compliant financial statements. An accountant who knows SYSCOHADA but not Business Central will demand impossible or unnecessarily costly adaptations. The real competitive advantage lies in the ability to bridge the two.

This is precisely what NJIADATA brings: dual technical expertise (Business Central, Power BI, Azure) and business expertise (SYSCOHADA, WAEMU taxation, public budget management) that ensures the deployed system is both technically robust and regulatorily compliant.

What we recommend

For an organisation in the OHADA zone considering Business Central, here are the key points we systematically share with our clients.

Demand a documented SYSCOHADA chart of accounts.

Not just a list of accounts, but a complete mapping between Business Central accounts and SYSCOHADA financial statement headings. This document must be validated by your auditor before configuration begins.

Test financial statements from sprint 1.

Don't leave SYSCOHADA financial statement production (balance sheet, income statement, TAFIRE) to the end of the project. Run them with test data from the first weeks. Discrepancies are easy to fix early in the project, difficult in production.

Connect Power BI from day one.

Regulatory financial statements are necessary but not sufficient for steering. A Power BI dashboard connected in real time to Business Central gives executives a vision that SYSCOHADA statements — designed for compliance, not for decision-making — do not provide.

Anticipate local tax specificities.

Withholding tax, import VAT, employer contributions — each country has its particularities. Make sure your partner has already deployed Business Central in your country, not just "in Africa."

Plan for accountant training.

The transition from a traditional accounting package (Sage, SAARI, or even Excel) to Business Central is a significant change. Change management is not optional — it is often the number one success or failure factor.

In summary

Business Central is not "OHADA-certified" — this certification does not even exist. But it is a modern, flexible, cloud-native ERP that can be configured to fully comply with the revised SYSCOHADA, provided it is in the right hands. The value is not in the software — it is in the expertise of the person configuring it.

At NJIADATA, we consider Business Central the natural transactional backbone of our data value chain. It generates the data. Power BI transforms it into decisions. SharePoint archives it. And everything works within an integrated Microsoft ecosystem, with no data breaks and no re-entry.

Our slogan says it best: from source to insight.