East Asia is where buyers read the numbers most carefully and close the books most strictly. This page asserts nothing about any single country's rules — it describes the platform mechanics, and what you should ask before scope is agreed.
No country in East Asia carries source-verified compliance facts on this site yet, so the four axes below cover the mechanics and what a project here has to settle early.
Parallel ledgers: one posting produces the local statutory report and the group report side by side — nothing is booked twice.
Standards in the region diverge sharply and almost every jurisdiction keeps a local layer alongside IFRS. For a group with entities here, parallel ledgers are a precondition, not an upgrade option.
Issuing, archiving and reconciling documents sits in the configuration and integration layer — never a code branch per country.
What discovery has to settle is the connection into each jurisdiction's document system, not whether documents can be issued: issuing and archiving already sit in the configuration layer.
Pay cycles, mandatory contributions and contract records follow each jurisdiction, on the same data layer as finance.
Pay structures here are tied to seniority, layered allowances and mandatory contributions — payroll has to be configurable rather than picked from a template.
Three deployment models decide where the data sits; permissions and access logs are one shared design across every legal regime.
Data-residency requirements in this region tend to be a precondition rather than a negotiating point. The three Apus deployment models — SaaS, on-premise, source-code handover — exist for exactly that kind of requirement.
7 of 7 countries in this region carry source-verified facts on this page.
| Country | Accounting standards | Tax & e-invoicing | Data protection |
|---|---|---|---|
| China | ASBE | e-fapiao (STA) | PIPL |
| Hong Kong SAR China | HKFRS | no verified source yet | PDPO (Cap. 486) |
| Japan | JGAAP · IFRS · JMIS · US GAAP | Qualified Invoice System · Peppol JP PINT | APPI |
| Macao SAR China | FRS · GFRS | no verified source yet | no verified source yet |
| Mongolia | IFRS | eBarimt | no verified source yet |
| South Korea | K-IFRS | e-Tax Invoice (NTS) | PIPA |
| Taiwan | TIFRS | eGUI (MOF) | PDPA · PDPC |
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 busier direction of this corridor is inbound: East Asian groups have invested in Vietnam for decades, and for them the Vietnam page on this site is where Apus gets most specific. The outbound direction — a Vietnamese trading or engineering entity placed close to a major customer — runs on the same platform.
Served directly from Vietnam together with regional partners — discovery and delivery remote or on-site, scoped per project.
Because the site prints only what has a verified source. The six countries with facts here all sit in a compliance dossier that has been reviewed; no East Asian country is in it yet. Deployment in the region is still possible — the compliance scope is settled during discovery, not by a table on a website.
Yes. Japanese, Korean, Simplified Chinese and Traditional Chinese all run on the same data layer, so each person reads the same number in their own language and there is no copy to synchronise.
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.