Your group has a subsidiary in Abidjan, another in Douala, perhaps a third in Dakar. The parent company runs SAP, Dynamics 365, or Oracle. Then, when it comes to extending the information system to your African entities, you discover a reality your vendor never mentioned in their sales pitch: the OHADA zone is not a variant of the French General Chart of Accounts. It is a separate accounting system with its own financial statements, its own filings, and its own infrastructure constraints.
This article is for CIOs and CFOs who have subsidiaries in francophone sub-Saharan Africa — or who plan to open them — and who need to understand what this means concretely for their ERP.
Why Sub-Saharan Africa Is a Distinct ERP Market
The Organisation for the Harmonisation of Business Law in Africa (OHADA) groups 17 member states: Benin, Burkina Faso, Cameroon, Comoros, Congo, Côte d’Ivoire, Gabon, Guinea, Guinea-Bissau, Equatorial Guinea, Mali, Niger, Central African Republic, Democratic Republic of Congo, Senegal, Chad, and Togo. The founding treaty, signed in Port-Louis in 1993, had a central objective: harmonising legal and accounting rules to secure investment in the region.
For a CIO, this means your Ivorian subsidiary cannot simply use the French General Chart of Accounts (PCG) with minor adjustments. It must apply SYSCOHADA. If your group ERP lacks an OHADA localisation, you have a compliance problem — not merely a convenience issue.
The economic context amplifies the stakes. According to the IMF’s April 2026 Regional Economic Outlook, sub-Saharan Africa maintains a growth trajectory despite global pressures (IMF, April 2026). European multinationals continue to open subsidiaries there, yet global ERP vendors are not keeping pace: OHADA localisation remains a blind spot for many of them.
A useful clarification before we continue: Morocco and Tunisia are not OHADA members. Both countries apply accounting frameworks close to French norms. If your perimeter is limited to the Maghreb, this article does not apply directly to your situation.
OHADA and SYSCOHADA: What Changes for Your ERP
The SYSCOHADA Chart of Accounts: 8 Classes, Its Own Logic
The Revised OHADA Accounting System (SYSCOHADA Revised) was adopted in 2017 and came into force in most member states on 1 January 2018, through the Uniform Act on Accounting Law and Financial Information (AUDCIF) (OHADA.org). It structures accounting across 8 classes:
- Class 1: Long-term resources (equity, financial debt)
- Class 2: Fixed assets
- Class 3: Inventory
- Class 4: Third parties (customers, suppliers, government)
- Class 5: Cash and treasury
- Class 6: Ordinary activity expenses
- Class 7: Ordinary activity revenues
- Class 8: Non-ordinary activity (HAO) income and expenses
Account numbering differs significantly from the French PCG. Class 8 “HAO” (hors activités ordinaires — non-ordinary), which isolates exceptional events, has no direct equivalent in the PCG. Sub-account granularity also differs, particularly for third parties (class 4) and provisions.
The practical consequence: you cannot import your existing PCG chart of accounts into an ERP and relabel it as SYSCOHADA. You must reconfigure the chart of accounts from the OHADA reference framework — a significant parameterisation project in its own right.
OHADA Financial Statements: Formats With No Western Equivalent
SYSCOHADA requires financial statements that have no direct equivalent in IFRS or French PCG formats:
- The OHADA balance sheet follows a proprietary assets/liabilities structure, different from IFRS
- The SYSCOHADA income statement distinguishes results from ordinary activities (RAO) and non-ordinary activities (RHAO)
- The TAFIRE (Tableau de Financement des Ressources et des Emplois) is the local equivalent of a cash flow statement, with a distinct presentation logic
These statements must be produced in the exact format prescribed by OHADA to be valid with local tax authorities. If your ERP lacks OHADA reporting templates, your local accountants will produce them in Excel — a systematic source of errors and a real risk during a tax audit.
Local Taxation: Each Country Retains Its Own Rules
SYSCOHADA harmonises accounting, not taxation. Each member state retains its own rules:
- VAT varies by country and product category. Côte d’Ivoire applies a standard rate of 18%, Cameroon an effective rate of 19.25% (VAT + CAC surcharge), Senegal 18%. Exemptions and reduced rates exist in each country.
- Corporate income tax, withholding taxes, and sector-specific levies differ from country to country and can change mid-fiscal year.
- Local-specific charges apply on top: the Contribution des Patentes in Côte d’Ivoire, the Taxe sur les Conventions d’Assurance in Cameroon, and others.
For your ERP, this means tax tables must be configured country by country. A module working correctly in Côte d’Ivoire cannot be copy-pasted for Cameroon.
Social Declarations: The Challenge of Local Funds
Each country has its own social protection organisations, with their own forms, deadlines, and contribution rates: the National Social Insurance Fund (CNPS) in Cameroon, the Caisse de Sécurité Sociale in Senegal, the CNPS in Côte d’Ivoire. If your ERP includes a payroll module, it must handle these specifics country by country. Most global ERP vendors do not do this natively outside their historical markets.
Mapping ERP Vendors Present in the OHADA Zone
Global ERP Vendors: Real Presence, Partial Localisation
SAP S/4HANA and SAP Business One are present in sub-Saharan Africa via certified partners in major regional capitals (Abidjan, Dakar, Douala, Nairobi). SYSCOHADA configuration is technically achievable, but it is not native: it relies on the local integrator’s ability to configure the chart of accounts, financial statements, and tax tables. The quality of this configuration varies considerably between partners.
Oracle NetSuite has a presence through cloud resellers. OHADA localisation is limited and depends on the ISV offering the add-on module. Before selecting NetSuite for an African subsidiary, require a live demonstration with the active SYSCOHADA chart of accounts and automatically generated OHADA statements.
Microsoft Dynamics 365 Business Central offers OHADA localisations available through partner ISV modules. The Microsoft community in West Africa is active, particularly in Côte d’Ivoire and Senegal. Localisation quality again depends on the partner.
Francophone ERP Vendors With Established OHADA Localisation
Sage is the most established vendor in francophone Africa for mid-market businesses. Sage 100 and Sage X3 offer OHADA localisations deployed via a network of certified partners with a physical presence in the region: Groupe Osiris has operated from Abidjan (Osiris) and Dakar (Seninfor) since 1992 (waysup-afrique.com), LABEL is listed as a Sage Certified Partner ERP X3 in Côte d’Ivoire (labelci.com), and HOODO serves Central Africa from Douala. Sage’s historical presence in these markets is a genuine advantage: partners understand local accounting practices, not just ERP configuration.
EBP is primarily present in the Maghreb and a few West African countries via local distributors. Coverage remains less dense than Sage.
Cegid has a significant presence in Morocco, but remains sparsely deployed in sub-Saharan Africa. Groups using Cegid in France or the UK should not assume a comparable local support network exists south of the Sahara.
Odoo and Local African Vendors
Odoo deserves particular attention. It has become one of the most widely deployed solutions in sub-Saharan Africa — not because the Belgian publisher natively localised it for each OHADA country, but because local integrators have developed country-specific SYSCOHADA modules available in the Odoo Apps catalogue. Odoo Community’s open-source model allows an integrator to customise the chart of accounts, financial statements, and tax tables without depending on an official localisation agreement with the publisher (GitHub — l10n_cm_syscohada module). Odoo integrators are active in Côte d’Ivoire, Senegal, Cameroon, and the DRC. Entry cost is significantly lower than SAP or Sage X3, making it a relevant option for SME-sized subsidiaries.
Local African ERP vendors also exist — with native SYSCOHADA support and deep knowledge of local practices. Their primary limitation is integration into a group architecture and handling large-enterprise transaction volumes.
5 Pitfalls CIOs Consistently Miss
1. Network and electrical infrastructure
In some areas, power outages are frequent and latency to a European datacenter can exceed 200ms. A full-cloud ERP hosted in Europe can become unusable during a connectivity outage. Before selecting an architecture, ask your local integrator for network availability data for the target country, and plan for a degraded or offline mode.
2. Scarcity of certified integrators outside major cities
The pool of SAP-, Oracle-, or Sage-certified integrators is concentrated in regional capitals (Abidjan, Dakar, Douala, Nairobi). If your subsidiary is in a secondary city, proximity support will be difficult to secure. This is a selection criterion that is consistently underweighted during ERP selection.
3. Personal data sovereignty
Côte d’Ivoire has a personal data protection law (Law No. 2013-450 of 19 June 2013), enforced by ARTCI (artci.ci). Senegal has Law No. 2008-12 of 25 January 2008, enforced by the Personal Data Protection Commission (CDP) (cdp.sn). These laws govern cross-border data transfers. Hosting Ivorian or Senegalese employee and customer data in a European AWS datacenter without prior legal analysis can expose your group to real compliance risk.
4. Unpredictable fiscal updates
Tax authorities in African countries sometimes modify their rates and filing forms without an established calendar. If your ERP relies on a remote partner for compliance updates, you risk filing incorrect returns for several weeks. Prioritise integrators with a local team capable of reacting quickly.
5. Integration into group consolidation
Your group consolidates accounts in IFRS or French standards. Your African subsidiaries keep their books in SYSCOHADA. No automatic mapping exists between the two frameworks: you will need to build and maintain a correspondence table between SYSCOHADA classes and your group’s analytical codes. This work is systematically underestimated during the design phase and generates recurring delays at period-end close.
Which ERP Architecture for a Group With African Subsidiaries?
Three architectures are viable, depending on group size and number of subsidiaries.
Option A — Extended group ERP with OHADA localisation You deploy your group ERP (SAP, Oracle, Dynamics) in your African subsidiaries, with SYSCOHADA configuration handled by a certified local partner. This is the most coherent option from a group integration standpoint, but also the most costly and complex to maintain. It is relevant for sizeable subsidiaries (more than 50 ERP users, high transaction volume).
Option B — Group ERP + local accounting software Your subsidiaries use an OHADA-compatible local accounting package (Sage 100, EBP, or a local solution) to produce SYSCOHADA statements and local tax filings. A periodic interface aggregates data up to the group ERP for consolidation. This is the most pragmatic approach for small-to-medium subsidiaries (10 to 30 people).
Option C — Odoo or Sage X3 as unified ERP for African subsidiaries You deploy Odoo or Sage X3 with locally configured OHADA modules as a single ERP across all your African entities. Group consolidation is handled by a dedicated tool (Tagetik, LucaNet, Conso4S). This is a sound compromise for mid-size groups with several African subsidiaries.
| Profile | Recommended architecture |
|---|---|
| 1 subsidiary, fewer than 20 people | Option B (local software + accounting feed) |
| 2-5 subsidiaries, 20-100 people | Option C (Odoo or Sage X3 + dedicated consolidation) |
| Subsidiary with more than 100 people, operational ERP needs | Option A (group ERP with OHADA localisation) |
Key Principles for Running an ERP Project in the OHADA Zone
Start from local obligations, not from the ERP. The right question is not “how do we deploy our ERP in Côte d’Ivoire?” but “what are our Ivorian subsidiary’s accounting, tax, and social compliance obligations, and which ERP covers them natively?” The order of analysis changes the decisions.
Require physical local presence from the integrator. A partner managing the project remotely from London or Casablanca will not know the local tax nuances that only an in-country professional masters. Ask for verifiable local client references.
Budget for ongoing training. Staff turnover in some markets is higher than in Europe. A user trained today may have left in 18 months. A recurring training plan and French-language documentation tailored to the local context are not optional.
Plan for offline degraded mode. If internet access is unstable, users must be able to continue working — at minimum for data entry — without a connection. Verify that your architecture supports this before signing.
Build the SYSCOHADA-to-group mapping from the design phase. This work determines the reliability of your consolidated reporting feeds and the length of your period-end close. Leaving it “for later” is one of the most common causes of schedule overruns on these projects.
For related topics: our analysis of sovereign cloud ERP in Europe covers the foundations of data sovereignty thinking — a question that arises with even greater force in an African context. And if you need to assess your current system before deciding on an extension to African subsidiaries, our ERP audit guide before migration provides a structured method to build on solid foundations.
