A South Asian group usually carries several legal entities across regions, product lines and licences. The problem is not one elegant ledger — it is dozens of ledgers that have to talk to each other without a reconciliation team standing in the middle.
The four axes below cover the platform mechanics and where projects in this region usually trip; the page carries no country-level compliance facts for South Asia yet.
Parallel ledgers: one posting produces the local statutory report and the group report side by side — nothing is booked twice.
Local statutory reporting here is often more detailed than group reporting, the reverse of the usual assumption. Parallel ledgers let the local books hold that detail without the group books carrying it.
Issuing, archiving and reconciling documents sits in the configuration and integration layer — never a code branch per country.
Document obligations can differ between entities of the same group, so issuing has to be switchable at entity level rather than system level.
Pay cycles, mandatory contributions and contract records follow each jurisdiction, on the same data layer as finance.
Payroll answers to rules at more than one administrative level, and most projects have to absorb a seasonal workforce that swings in size.
Three deployment models decide where the data sits; permissions and access logs are one shared design across every legal regime.
The legal framework for data in this region is moving quickly. Picking a deployment model that keeps data in-country from the start is the cheapest way to avoid redoing the work when rules tighten.
4 of 9 countries in this region carry source-verified facts on this page.
| Country | Accounting standards | Tax & e-invoicing | Data protection |
|---|---|---|---|
| Bangladesh | BFRS (ICAB) | Mushak 6.3 (NBR) | Personal Data Protection Act 2026 |
| India | Ind AS | GST e-invoice (IRP) | DPDP Act 2023 |
| Pakistan | IFRS as adopted in Pakistan · IFRS for SMEs | Digital Invoicing (FBR) | no verified source yet |
| Sri Lanka | SLFRS · LKAS | Tax Invoice (IRD SEC/2026/E/03) | PDPA No. 9 of 2022 · Amendment Act No. 22 of 2025 |
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.
For Vietnamese companies, South Asia currently shows up at the supply end and the sales end more than at the entity end. Apus serves both stages: cross-border supplier, order and receivables management first; a new legal entity as a configuration once you actually land.
Served directly from Vietnam together with regional partners — discovery and delivery remote or on-site, scoped per project.
This is exactly what parallel ledgers are for: the local books hold the level of detail required, while the group books take only what consolidation needs. The precise depth is agreed during discovery, because it differs by licence type and by industry.
No certified partner in the region yet. Projects are served directly from Vietnam combined with on-site presence within the agreed scope, and the partner programme is open to consultancies here.
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.