Malaysia · Group reporting
Several companies. One set of numbers.
Malaysian groups tend to grow by adding entities rather than by adding divisions. Each Sdn Bhd ends up with its own accounting file, its own chart of accounts and its own close date, and the group position gets assembled by hand weeks after the fact. The fix is not a migration — it is a consolidation layer that reads what each entity already produces.
Before and after
What changes when
the data finally talks.
Today's friction
- Each Sdn Bhd closing separately, into its own accounting file
- Charts of accounts that never quite match between entities
- Inter-company balances reconciled by hand and disputed at year end
- Group position assembled in a spreadsheet weeks after period end
- Ringgit and Singapore dollar balances converted at inconsistent rates
- No view of the group between close cycles
With Ontilus
- Every entity keeps its own system; consolidation happens in the data layer
- One mapped chart of accounts, agreed once and applied everywhere
- Inter-company entries matched automatically with the break surfaced
- Group position available any day, not only after close
- One rate source, recorded against every converted balance
- Access scoped per entity, with group reporting served from aggregates
What we build
Engineered for Group reporting.
Every system is bespoke to your entity structure. These are the modules this sector almost always needs.
Entity consolidation
Several Sdn Bhds rolled into one group position without anyone migrating accounting systems.
Chart mapping
Each entity's accounts mapped once to a group structure, so definitions stop drifting between companies.
Inter-company matching
Balances matched across entities automatically, with unmatched items surfaced rather than netted away.
Multi-currency
MYR, SGD and others converted from one recorded rate source, with the rate stored against the balance.
Entity isolation
Hard separation between legal entities, with access role-scoped and every access event logged.
Governed aggregates
Group reporting served from controlled aggregates instead of granting cross-entity access to raw records.
Outlet revenue
Where the entities underneath are outlets on different POS systems, sales are normalised and consolidated before they reach the entity roll-up.
Questions
Group reporting,
answered.
The questions operators in this sector ask first. If yours isn't here, ask us directly — we answer scoping questions before there's a contract in sight.
Talk to usDo all our companies need the same accounting system?
No, and requiring it is what usually kills these projects. Consolidation happens in the data layer: each entity keeps the system it runs, and its data is read and mapped to a shared group structure. That is what makes the work achievable without a migration nobody has budget or appetite for.
How are inter-company transactions handled?
Matched automatically across entities, with anything unmatched surfaced as a break rather than quietly netted off. The value is in the exceptions being visible during the period rather than discovered at year end, when correcting them is slow and contested.
How is multi-currency handled between MYR and SGD?
From one recorded rate source, with the rate stored alongside the converted balance so any figure can be traced back. Inconsistent rate handling between entities is one of the more common reasons a consolidated number cannot be reconciled to the entity accounts underneath it.
Can a subsidiary's staff see other entities' numbers?
Not unless you decide they should. Access is scoped per entity with isolation enforced at the data layer rather than in application code, and group-level reporting is served from governed aggregates — so consolidated figures are available without opening one company's records to another.
How long does a group consolidation take to deploy?
Around three weeks to a reconciled pilot on one entity and twelve to a group-wide system. The sequence matters more than the total: nothing goes group-wide until the pilot reconciles against that entity's own accounts, because a first number that disagrees with what the finance team already believes is very hard to recover from.
How we deploy
Live in 12 weeks.
Proven before it scales.
We pilot on one entity and validate against your own close reports before anything goes group-wide. See the full deployment approach →