Multi-Currency ERP for Pan-African Operations
Buyers use "multi-currency" to mean three unrelated things, and vendors answer whichever one they can. A guide to separating transaction currency, reporting currency and entity currency across a continent containing pegged zones, managed floats and markets where more than one currency circulates.
A group with entities in Lagos, Nairobi and Abidjan asks whether a system supports multi-currency and receives an enthusiastic yes. Six months later the finance director discovers that the yes answered a question nobody had asked. This happens so consistently that it is worth treating as a definitional problem rather than a vendor problem.
There are three separate capabilities hiding under one phrase. Most systems have the first. Many have the second. Very few have the third, and the third is usually what a pan-African group actually needs.
Three meanings, separated
Meaning one
Transaction currency
Can I buy in dollars and sell in naira, with the rate that was actually applied recorded on the transaction? Almost every system says yes. The question worth asking is whether the rate is stored on the record or recalculated at report time — because only the first survives a later argument about margin.
Meaning two
Reporting currency
Can a head office read the whole business in one denomination? Usually yes, as an indicative conversion for dashboards and on-screen reports. The important word is indicative: it must never appear on an invoice, statement, receipt or export, or the number becomes ambiguous in the one place ambiguity is fatal.
Meaning three
Entity currency
Can one instance hold entities whose statutory books are in different currencies, and consolidate them properly? This is the hard one, and it is where most groups actually live. It is also where "yes" most often means "we can show you a converted total", which is not consolidation.
Work out which of the three you are asking about before your first demo, and put it in writing. Half the disappointment in this category is a definitional mismatch that both parties believed had been resolved.
A converted total is not a consolidation. Ask whether the number could survive an auditor asking how it was produced.
The continent has four currency behaviours, not fifty-four
For operational purposes, African currencies sort into four groups by behaviour rather than by geography. Which group your entities sit in decides how much of your effort goes into currency discipline at all.
| Behaviour | Where it shows up | What it demands of your system |
|---|---|---|
| Pegged to an external anchor | The CFA franc zones in West and Central Africa | Almost nothing extra. Intra-zone balances stop generating revaluation noise, and cross-zone exposure is entirely against the anchor. The one discipline is not assuming the peg is permanent |
| Managed or basket-linked | Botswana, and arrangements linked to the rand | Stability that breeds complacency. The risk is pricing off supplier invoices because currency feels solved, and never seeing landed cost |
| Floating, with real movement | Most large economies on the continent | The rate actually applied stored on every transaction, landed cost folded into the unit, and margin reviewed per consignment rather than per month |
| More than one currency in practical circulation | Markets with recent redenomination or partial dollarization | Absolute fidelity. Record what happened in the currency it happened in. Any system with an opinion about the currency becomes the problem |
A group spanning three of those four — which is common — should not expect one currency policy to fit all its entities. It should expect one recording discipline to fit all of them, which is a different and much more achievable thing.
The entity question, answered precisely
Here is our position, and it is a restriction rather than a feature, which is unusual enough to explain properly.
The base currency is locked per organization. Everything is stored, invoiced, printed and accounted in it — there is no ambiguity about what any given number means, ever. A group with entities in three countries therefore runs an organization per entity, each with its own locked base currency, and views the group through an indicative display currency on dashboards and on-screen reports.
That is genuinely useful for management. It is genuinely not statutory consolidation: no eliminations, no group accounting standard applied, no automatic revaluation postings. Those stay with your auditors, working from records we hold.
Group currency handling, layer by layer
One locked base currency per entity
Stored, invoiced, printed and accounted in one denomination. The restriction is the feature — an unambiguous number is worth more than a flexible one.
Transactions at the rate actually applied
Stored on the record rather than recalculated. This is what makes a historic margin defensible instead of arguable.
Counterparties holding their own trading currency
A dollar supplier stays a dollar supplier without anyone remembering to set it each time.
Landed cost folded into the unit
Freight, duty, clearing and inland transport allocated onto the receipt, so an imported unit carries its real cost across any currency boundary.
Indicative group display currency
An optional organization-wide preference for dashboards and on-screen reports. Never on an invoice, statement, receipt or export — deliberately, and non-negotiably.
Two base currencies in one organization
Not supported. An entity genuinely operating at statutory level in two currencies is two entities and should be run as two organizations.
Statutory consolidation with eliminations
Management consolidation only. Eliminations, group accounting standards and statutory revaluation postings stay with your auditors.
Treasury — hedging, forwards, exposure limits, forecasting
Not built and not intended. We record what happened; we hold no view on what will happen.
The two "not built" rows in the middle are the ones to raise with every vendor you shortlist, in exactly these words. A great many products describe a converted group total as consolidation, and the difference only becomes visible when an auditor asks how a number was produced.
What it costs to get this wrong
A cross-border sale, recorded two ways
Method A is not wrong arithmetic. It is arithmetic performed too late to be actionable, on a rate that nobody involved in either transaction ever saw. For a single-country business that is tolerable. For a group whose entities trade with each other across three currency behaviours, it makes intercompany performance unanalysable — which is usually the exact question the group was formed to answer.
The intercompany mechanics are worked through in intercompany and multi-entity operations for regional groups, and the consolidation boundary in consolidated reporting for regional groups.
The straight answer
What AWRA OpsHub does today
- Every African currency as a base currency preset, resolved from the organization's country.
- A locked base currency per organization, in which everything is stored, invoiced, printed and reported.
- Foreign-currency transactions with the rate actually applied stored on the record.
- Suppliers and customers holding their own trading currency.
- Landed cost from freight, duty, clearing and handling, allocated onto the receipt.
- An optional organization-wide display currency for dashboards and on-screen reports, clearly indicative.
- Cross-entity management reporting, so a group can read its footprint in one denomination.
What it does not do
- No multiple base currencies inside one organization. The base is locked and the display currency never appears on an invoice, statement, receipt or export.
- No statutory consolidation. No eliminations, no group accounting standard, no automatic revaluation postings.
- No treasury function. No hedging, forward contracts, exposure limits or position management.
- No rate forecasting and no view on which currency to hold.
- No special logic for pegs or managed floats, deliberately — a hardcoded monetary assumption becomes the problem the day it stops holding.
- No automatic bank feeds in any market, so settlement rates are recorded from your documents rather than pulled.
The absence of peg logic is a design position rather than a gap, and this continent is where it earns its keep. Fixed rates on this continent have been changed by announcement more than once. A system that hardcoded one would have needed emergency surgery on each occasion; a system that simply records the rate applied needed nothing at all.
What is not built for your market today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in your market. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a revenue authority pipeline, a bank or mobile money feed, a statutory return format or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Tax and e-invoicing pipelines
Electronic invoicing against your revenue authority's published interface, with the parts vendors gloss over — retries, a failure queue and a daily report of sales carrying no fiscal reference.
Banks, payments and mobile money
Statement feeds, payment gateways, bulk-payment files and collection accounts wired into the Payments Register so money in and out reconciles without re-keying.
Payroll and statutory returns
Payroll and social security schedules produced in the layout your filing body expects, generated from live payroll records rather than rebuilt each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedFour habits for a pan-African group
-
Decide which of the three meanings you are buying
Transaction, reporting or entity currency. Put it in the requirements document in those words, and make every vendor answer against the right one.
-
Set each entity's base currency deliberately at setup
Never accept a default, ours included. It is locked once operations begin and changing it later is a migration rather than a setting.
-
Record the rate at the transaction, not at the report
This is the one habit that cannot be retrofitted. Everything downstream — margin, intercompany analysis, budget variance — depends on it and nothing recovers it later.
-
Keep statutory consolidation with your auditors, and say so out loud
Management consolidation from one system plus statutory consolidation from your auditors is a correct and common arrangement. What fails is a group assuming its operations platform was doing the second one.
Where to go next
The continental framework is in the best ERP software for African businesses, and the trade dimension in AfCFTA and cross-border trade.
By currency environment: the CFA franc and the euro peg, kwacha, pula and a redenominated dollar, multi-currency across East Africa, Egypt and Morocco and frontier economies.
Our take
Separate the three meanings before you take a demo, because a yes to the wrong one is how six months disappear. Then buy the recording discipline rather than the currency features: one locked base currency per entity, every transaction stored at the rate actually applied, landed cost folded into the unit, and a group view that is honest about being indicative. Keep statutory consolidation with your auditors and treasury with your bank. Across a continent containing pegs, floats and redenominations, the system with the fewest opinions is the one still working in five years.
See group currency handled without pretence
One locked base currency per entity, the rate actually applied on every transaction, landed cost folded into the unit, and a group view that never claims to be a statutory consolidation.
Talk to us about your groupFrequently asked questions
Can one organization operate in two base currencies?
No, and the restriction is deliberate rather than a limitation we intend to remove. The base currency is locked per organization and everything is stored, invoiced, printed and accounted in it, which is what makes any given number unambiguous. There is an optional organization-wide display currency for dashboards and on-screen reports, but it is indicative only and never appears on an invoice, statement, receipt or export. An entity genuinely operating at statutory level in two currencies is two entities.
How does a group with entities in several countries consolidate?
Each entity runs as its own organization with its own locked base currency, and group-level viewing uses an indicative display currency across dashboards and cross-entity reporting. That gives management a comparable read of the whole footprint. It is explicitly not statutory consolidation — there are no eliminations, no group accounting standard applied and no automatic revaluation postings — and that work stays with your auditors, using records we hold. Insist on this distinction with every vendor: many describe a converted total as consolidation.
Do you handle the CFA franc peg differently?
No, and that is intentional. We hold no special logic for pegged, managed or basket-linked currencies, because a system that hardcodes a monetary assumption becomes the problem on the day the assumption changes. A pegged pair simply produces the same rate transaction after transaction, which the general mechanism handles without needing to know it is a peg. The practical benefit for franc-zone businesses is that intra-zone revaluation produces zero every time, so you can stop performing it as a ritual.
Where do exchange rates come from?
For your transactions, from you: the rate actually applied is what gets recorded, because it is the only rate that reflects what happened. We do not impose a market rate on your purchases or sales, and we do not pull settlement rates from bank feeds — there are no automatic bank feeds in any market. Separately, our own subscription pricing is denominated in Kenyan shillings with a US dollar equivalent derived from a live rate refreshed on a schedule, which is a billing mechanism and does not touch your books.
Is there any treasury capability?
None. No hedging, no forward contracts, no exposure limits, no position management and no rate forecasting. If your group needs those it needs a treasury function and probably bank products, and an operations platform is the wrong place to look for them. What we contribute is that whoever manages your exposure is working from transactions recorded at real rates rather than from a spreadsheet reconstruction, which is a genuinely useful input and not a substitute for the capability.
What breaks if we get the recording wrong?
Attribution. Applying a conversion at reporting time produces arithmetic that is not wrong, only performed too late to act on and against a rate nobody in either transaction ever saw. For a single-country business that is tolerable. For a group whose entities trade across pegged, floating and redenominated environments, it makes intercompany performance unanalysable — you can see that group margin moved, but not which entity, which month or which leg caused it. That is usually the exact question the group structure exists to answer.
Which African currencies are supported?
Presets ship for the great majority of African currencies, alongside VAT and tax rate defaults for those countries, so setting up an entity in most markets on the continent does not begin with data entry. Treat both currency and tax presets as starting values you own rather than as maintained regulatory content — we say the same about our own defaults as about anyone else's, and we can prove we mean it: our Zimbabwe preset carried the pre-redenomination code for a long time after the change before being corrected. Set them deliberately at setup.
