One ERP Across the EAC: Managing Operations in Multiple Countries
A vendor-honest guide for businesses and groups operating in more than one EAC country — why one system beats a copy per country, what "one ERP across the East African Community" actually requires, and the straight answers on tax, e-invoicing and payroll that no platform automates identically across every border.
A group with a head office in Nairobi, a branch in Kampala and a depot in Dar es Salaam is not one business with three addresses. It is three legal businesses sharing a logo — three registrations, three currencies, three tax regimes, three sets of auditors — and one owner who has to see them as a single picture on a Monday morning. Most regional groups solve this the expensive way: a separate system (or separate spreadsheets) per country and a heroic consolidation every quarter that lives in one accountant's head. This guide is about the structural alternative — one system across the EAC — and, just as importantly, about the claims to distrust while you shop for it.
It is deliberately vendor-honest. Where AWRA OpsHub does something across borders, we say so; where a capability is Kenya-only or not built at all — most importantly regional e-invoicing and turnkey statutory payroll — we say that too, because the fastest way to waste money on regional software is to believe a "works everywhere, fully integrated" claim you were never made to test.
When you have genuinely outgrown "a system per country"
Running a separate tool per country is the right choice until a threshold — and the threshold is not the number of countries, it is the number of questions you can no longer answer quickly. The signs are consistent across regional groups:
- "What did the group make last month?" takes a week to answer. Each country closes on its own calendar in its own currency, and someone stitches it together by hand.
- Nobody trusts the consolidated number. Three offices convert currency three different ways, and the group total depends on who built the spreadsheet.
- Inter-office money moves live in memory. Kenya paid a Ugandan supplier; the "loan" between the entities is a WhatsApp message, not an account.
- Stock and cash move across borders with no common record. A transfer from the Dar depot to the Kampala branch is invisible until it causes a variance.
- A lender, investor or group auditor now wants one view — and "let me pull the four files together" is no longer an acceptable answer.
The core idea: country as a dimension, not a copy of the software
The mistake that makes regional software expensive is treating each country as a fresh copy of the system. The structural answer is to keep one system and make country a first-class dimension on every record — the same principle regional NGOs use to run one system across five tax regimes, applied to a commercial group.
- Every transaction carries its country alongside its branch, product and cost centre. Reports then slice by country (for each registration's statutory books), by group (for the owner), or both — without re-keying anything.
- Each country is a full node, with its own bank and mobile-money accounts, stock locations, asset custody, approval chains and local currency — accountable locally, visible at group level.
- Currencies live at two levels: each entity keeps its books in its home currency (KES, UGX, TZS, RWF, ETB), and the group consolidates by a declared policy rather than by whatever rate a spreadsheet remembered — the discipline covered in multi-currency accounting for cross-border trade.
- Consolidation becomes a filter, not a project: the group view is a lens over the same dataset, so adding a fifth country is a configuration exercise — a new node, a new currency, the same dimensions — instead of a fifth spreadsheet empire.
The buyer's checklist for a regional group
Every demo looks good in one country. The value is in what you make the vendor prove across two. Here is the checklist that matters for a regional group, and the test for each.
| Requirement | Why it matters regionally | How to test it in the demo |
|---|---|---|
| Country as a dimension | A group view and a per-country statutory view must come from one dataset | Ask to see the same P&L filtered to one country, then to the whole group, with no export |
| Multi-currency done honestly | Home-currency books per entity, group consolidation by a stated policy | Book a UGX cost and a KES cost; see both in local currency and consolidated on one report |
| Inter-entity balances as real accounts | Cross-border money movements are the consolidation killer if undocumented | Have Kenya pay a Ugandan supplier; show the inter-office balance it creates |
| Per-country approvals and roles | Each office needs local autonomy without seeing the others | Log in as a Kampala approver; confirm they cannot see or approve Nairobi spend |
| Offline capture | Upcountry branches and border depots are not always online | Airplane-mode a device, record a sale and a transfer, reconnect and watch it sync |
| Honest about tax per country | This is where money is wasted — see below | Ask what is automated in each country, in writing; prefer "here is built, here is roadmap" |
The one claim to never take on trust
If a vendor says they are "fully integrated with tax and e-invoicing across East Africa," stop and make them prove it country by country. Kenya's eTIMS, Uganda's EFRIS, Tanzania's EFD and Rwanda's EBM are four different regimes — no honest vendor treats them as one checkbox. A confident regional wave-off is the single most expensive sentence in the room.
What one system honestly does — and does not — across borders
Here is the straight version, because the regional pitch is where over-claiming does the most damage:
- Multi-currency and consolidated management reporting: yes. Home-currency books per entity and a consolidated group view on one dataset are core.
- Statutory, audited consolidation with eliminations: your accountant's domain. The system gives you clean, consistent management consolidation; formal group accounts with statutory eliminations are prepared with your auditor — see consolidated reporting for EAC groups.
- E-invoicing: Kenya's eTIMS is the only built-in regime. EFRIS (Uganda), EFD (Tanzania) and EBM (Rwanda) are not integrated — AWRA runs your operations and your invoicing records reconcile against each country's existing fiscalization process. Do not buy on the assumption of regional e-invoicing integration.
- Statutory payroll: turnkey for Kenya only. Kenyan PAYE/NSSF/SHIF is built to a turnkey standard; elsewhere you configure deductions and confirm rates locally — covered in regional HR and payroll variance.
- Customs and clearing: not what this is. AWRA records the landed cost of cross-border goods (duties, clearing, freight you enter); it is not a customs-declaration or clearing platform — see AfCFTA and EAC trade.
None of these are weaknesses to hide — they are the difference between a vendor you can trust with a liability and one you cannot. Kenya ran this race first under eTIMS pressure; the winners treated compliance as a by-product of clean records, a lesson that carried across the region.
The rollout sequence: one country clean, then replicate
Regional groups that fail at this usually try to switch on every country at once. The reliable sequence is to get one country genuinely clean, prove the model, then replicate the configuration next door.
| Stage | What happens | The payoff |
|---|---|---|
| 1 | Stand up the home country fully — stock, sales, purchasing, banking | One entity is clean and trusted before anything is consolidated |
| 2 | Add the second country as a node — its currency, accounts, approvals | The dimension model is proven with two entities, not promised |
| 3 | Turn on inter-entity balances and cross-border allocations | Money moving between offices becomes an account, not a memory |
| 4 | Switch on the consolidated group view | The owner sees the group on one screen, in one policy currency |
| 5 | Replicate for each remaining country | A new country is configuration, not a new system |
For the country-by-country specifics, the buyer's guides for Uganda, Tanzania, Rwanda and Ethiopia each cover the local checklist and the honest tax boundary in that market.
See what one system across East Africa looks like
Country as a dimension, honest multi-currency, inter-entity balances and a consolidated group view — one dataset from Nairobi to Kampala, Dar, Kigali and Addis, and straight answers on tax in each.
Talk to us about regional operationsFrequently asked questions
Should each country run its own separate system instead?
Separate systems recreate the consolidation problem with better software — you still stitch the group together by hand. One system with country as a dimension gives each office full local autonomy (its own approvals, accounts and reporting) while the group view is a filter rather than a quarterly project. The one genuine exception is a legal data-residency requirement in a particular country — check each registration's rules.
Does AWRA handle e-invoicing across all EAC countries?
No — only Kenya's eTIMS is built in. Uganda's EFRIS, Tanzania's EFD and Rwanda's EBM are separate regimes that are not integrated today; AWRA runs your operations and your invoicing reconciles against each country's existing fiscalization process. Treat any vendor's "regional e-invoicing" claim as something to watch working country by country, not take on trust.
Can it produce our audited group accounts?
It produces consistent management consolidation from one dataset, which is most of the work. Formal statutory group accounts — with intercompany eliminations and the treatment your jurisdiction requires — are prepared with your auditor using those clean records as the source. The system removes the spreadsheet scramble; it does not replace your accountant's judgement.
How does it handle four different payroll regimes?
Honestly: statutory payroll is built to a turnkey standard for Kenya only. Regional groups typically run payroll per country — configuring deductions to local requirements and confirming rates with each authority — while operations, funds and assets consolidate in one system. Personnel costs still allocate to the right country and cost centre either way.
What currency does the group report in?
Each entity keeps its books in its home currency, and you choose the group reporting currency and the conversion policy (commonly transaction-date rates for activity and a stated method for consolidation). The failure mode is never the method — it is three offices using three methods nobody wrote down. One system applies your declared policy consistently.
