Organisations here often do not carry many legal entities, but the expectation around audit trail and reporting quality is high. That is a data-discipline problem, not a scale problem.
Customers here ask how you prove it before they ask what it does. The four axes below answer in that order; the per-country compliance cells are unsourced and therefore empty.
Parallel ledgers: one posting produces the local statutory report and the group report side by side — nothing is booked twice.
What gets asked here is usually not whether the system can do it but how you prove it: every posting carries its origin, its author, its approver and its edit trail inside the system.
Issuing, archiving and reconciling documents sits in the configuration and integration layer — never a code branch per country.
Tax and document mechanics in the region are relatively settled; the part worth discussing is fitting in with the tools already running, and that is an integration item rather than a core one.
Pay cycles, mandatory contributions and contract records follow each jurisdiction, on the same data layer as finance.
Pay cycles and long-term employee contributions are configuration parameters per entity, not a module you buy separately.
Three deployment models decide where the data sits; permissions and access logs are one shared design across every legal regime.
Distance to regional infrastructure is a real question here; where the data sits is decided by the deployment model, and the on-premise edition remains an option when the requirement is that data never leaves the organisation.
2 of 14 countries in this region carry source-verified facts on this page.
| Country | Accounting standards | Tax & e-invoicing | Data protection |
|---|---|---|---|
| Australia | AASB (IFRS-equivalent) | Peppol (B2G) | Privacy Act 1988 |
| New Zealand | NZ IFRS (XRB) | Peppol (B2G) | Privacy Act 2020 |
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.
The corridor between Vietnam and this region is mostly agriculture, seafood and education — supply chains with strict quality standards at the receiving end. For those, the value is in having quality records, lot traceability and export documents in the same place as the books, rather than in a separate declaration portal.
Served directly from Vietnam together with regional partners — discovery and delivery remote or on-site, scoped per project.
Remote is the default, with handover milestones and operating documentation complete enough for your team to run the system after go-live; on-site presence enters the scope when the project genuinely needs it. The overlap between the two working days is wide enough for live sessions.
Access logs and edit trails are a base capability, not an add-on; the trust centre describes the exact scope. The rest — audit scope, cadence, who signs — belongs to the contract between you and your audit firm.
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.