In this region a group commonly holds a free-zone entity and a mainland entity at the same time, with different obligations. The system has to tell those two apart at the data layer, not by how the companies were named.
The country table below is empty, so these four axes carry the whole argument: the platform mechanics, and what the entity structures here demand.
Parallel ledgers: one posting produces the local statutory report and the group report side by side — nothing is booked twice.
Two entities of the same group can sit under different reporting regimes. Parallel ledgers plus per-entity configuration keep both correct while still consolidating into one reporting currency.
Issuing, archiving and reconciling documents sits in the configuration and integration layer — never a code branch per country.
Tax configuration has to change without touching the core — that is the first requirement wherever a market's tax framework is still taking shape.
Pay cycles, mandatory contributions and contract records follow each jurisdiction, on the same data layer as finance.
The working week and rest days here do not line up with most of the world, so close calendars, pay cycles and approval schedules are configuration parameters rather than constants of the system.
Three deployment models decide where the data sits; permissions and access logs are one shared design across every legal regime.
Many projects here require data to stay in-country or inside a specific infrastructure region. That is a deployment-model choice, decided during discovery rather than after go-live.
2 of 20 countries in this region carry source-verified facts on this page.
| Country | Accounting standards | Tax & e-invoicing | Data protection |
|---|---|---|---|
| Saudi Arabia | IFRS (SOCPA) | FATOORAH (ZATCA) | PDPL (SDAIA) |
| United Arab Emirates | IFRS | PINT AE (Peppol) | PDPL (Federal Decree-Law 45/2021) |
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 come to this region mainly through construction, supply and labour contracts — long-lived projects with many acceptance milestones and cash flows in several currencies. That is a project-management plus finance problem on one data layer, not an accounting-software problem.
Served directly from Vietnam together with regional partners — discovery and delivery remote or on-site, scoped per project.
The whole site and the platform run Arabic in genuine right-to-left layout, including forms, tables and the direction of arrows — not a translation pasted onto a left-to-right layout. The page you are reading has exactly such an Arabic version.
They are separated at the entity layer, not by naming: each entity keeps its own books, tax regime and document set, while consolidation runs through one close process. The exact scope for each side is agreed during discovery.
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.