Forty-eight countries, and Apus has verified a compliance source for none of them. We keep the page the size of what we actually know: how the platform mechanics work, and what has to be settled in discovery before anyone talks about compliance.
There is no country-level fact on this page. The four axes below are the platform mechanics — true in every market — and a question frame for the first discovery session.
Parallel ledgers: one posting produces the local statutory report and the group report side by side — nothing is booked twice.
Which standards apply to each entity is an open question here; parallel ledgers mean you do not have to pick one standard up front and get stuck with it as the scope becomes clearer.
Issuing, archiving and reconciling documents sits in the configuration and integration layer — never a code branch per country.
Issuing and archiving documents sit in the configuration layer, so connecting to an electronic tax system is an integration item with a measurable scope rather than an architectural question.
Pay cycles, mandatory contributions and contract records follow each jurisdiction, on the same data layer as finance.
Many projects in the region carry a large field workforce and a small back office; payroll and time capture have to hold that ratio.
Three deployment models decide where the data sits; permissions and access logs are one shared design across every legal regime.
Uneven connectivity is a real design constraint, and the on-premise model exists for places where an outbound link cannot be an assumption.
3 of 48 countries in this region carry source-verified facts on this page.
| Country | Accounting standards | Tax & e-invoicing | Data protection |
|---|---|---|---|
| Kenya | IFRS | eTIMS (KRA) | Data Protection Act 2019 |
| Nigeria | IFRS · IFRS for SMEs | FIRS e-Invoice | NDPA 2023 |
| South Africa | IFRS · IFRS for SMEs | no verified source yet | POPIA |
The rest of the region — no verified source yet:
An empty cell means Apus has not verified a source for that country — not that the country has no rules. Deployment is still possible; the exact compliance scope is agreed during discovery.
Not localization bolted on afterwards — these mechanisms live in the data core and are shared by every market.
Headquarters and each subsidiary are separate legal entities inside one system — not one installation per country reconciled by hand.
A single posting produces reports under IFRS and under the local standard in parallel — nothing is booked twice.
Transact in each market's currency; consolidate into the group's reporting currency as part of the close process.
Country differences live in the configuration layer — standards, document templates, tax — so every market runs the same maintained core.
Vietnamese companies work in Africa mainly through long-running telecoms, agriculture and construction projects — where the real question is not which software but what head office can see. Apus answers with one shared data layer, where the site and the head office read the same number.
Served directly from Vietnam together with regional partners — discovery and delivery remote or on-site, scoped per project.
To say exactly what Apus knows. A page boasting coverage of forty-eight countries with no sources behind it is easy to write and not worth trusting; the country list here is real, and the compliance cells stay empty until a source dossier is approved. Projects in the region can still go ahead, and the compliance scope is settled in discovery.
The architecture tolerates interruption at the edge, and the specific connectivity plan is agreed during discovery; the on-premise edition runs entirely on your own infrastructure when the link out is unreliable. This is a familiar problem on infrastructure projects.
Apus serves customers globally: the platform runs in ten languages, local accounting standards are handled in configuration, and delivery combines remote work from Vietnam with partners — projects outside Vietnam run in English by default. Tell us about your market.
Forty-five minutes, in the context of your market — scope, compliance and timeline.