Every corporate group hits a number. It's usually somewhere between 15 and 50 entities — and when you cross it, the governance model that got you this far silently collapses.
Not loudly. Not with a single catastrophic failure. Silently. The spreadsheets start lagging behind. The company secretary becomes a single point of failure. The board gets compliance reports that were already stale before they were formatted. And somewhere in your corporate register, there's an entity nobody has touched in eight months that still has the wrong director listed.
This is the 50-entity problem. And almost nobody talks about it until they're already in it.
Small corporate groups are manageable with discipline and good habits. One entity? A spreadsheet and a shared calendar works fine. Five entities? Still manageable with a skilled company secretary and a clear filing system. Even ten or fifteen entities can be held together by a single capable person who knows where everything lives.
But there's a threshold — and it's not a hard number. It's a point where the cognitive load of tracking obligations across every entity in the group exceeds what any manual system can reliably hold. Where the cost of a missed ASIC deadline, an incorrect officer record, or a stale beneficial ownership register stops being theoretical and starts showing up in real consequences.
For most corporate groups, that threshold is somewhere between 15 and 50 entities. And the dangerous part isn't crossing it — it's not knowing you've crossed it until something breaks.
The groups that handle this well build a governance foundation before they need it. The groups that handle it badly build the foundation after a regulator asks a question they can't answer quickly enough.
When a corporate group scales past its governance model's capacity, three things break in predictable sequence:
Compliance visibility disappears. Nobody in the group has a real-time view of which entities are compliant, which have upcoming ASIC lodgements, which have annual review fees due, or which officer appointments haven't been formally registered. The CFO doesn't know. The company secretary has a spreadsheet that's probably right, but probably isn't completely current. The board has reports that are already weeks old.
Accountability diffuses. In a smaller group, the company secretary owns the compliance calendar and everyone knows it. As the group scales, responsibilities blur. Which entities does the company secretary cover? Which ones does the legal team handle directly? Which ones are managed by external advisors who may or may not be updating your internal systems? The answer is usually "it depends" — which means it's probably nobody's job clearly enough.
Institutional knowledge becomes a liability. Every company secretary who builds and maintains a complex manual governance system becomes a single point of failure. When they leave — and eventually they do — the knowledge leaves with them. The complexity of the system they've maintained doesn't transfer cleanly into a handover document. And the new person spends the first six months finding out what they don't know.
Let's be specific about what manual tracking actually means in a 50-entity corporate group.
You're maintaining a compliance calendar that needs to track ASIC annual review dates, officer appointment and resignation registrations, registered office addresses, ABN/ACN records, share register maintenance, beneficial ownership records, and (increasingly) AML/CTF-related disclosures — across every entity in the group, including dormant ones.
You're doing this in a spreadsheet, or a set of spreadsheets, that were probably built by the previous company secretary and modified several times since then. The formulas work most of the time. The conditional formatting flags upcoming deadlines. The tabs are named in a way that made sense when there were 15 entities but is slightly confusing now.
And every single piece of data in that system is only as current as the last time someone manually updated it.
The spreadsheet trap isn't that spreadsheets are bad tools. It's that the manual update requirement creates a permanent lag between the actual state of your governance and what your governance system reflects. At five entities, that lag is manageable. At fifty, it's a governance gap that's always there, always growing, and never fully resolved.
The other failure mode is version control. How many versions of the compliance spreadsheet exist across the company secretary's laptop, the shared drive, the CFO's email attachments, and the board pack appendix from three months ago? The answer is almost always "more than one" — which means nobody can be certain which version reflects the current state.
The groups that scale governance well understand that the problem isn't any one of these things in isolation. It's that they're being managed as three separate workflows when they're actually one connected system.
Beneficial ownership data feeds your compliance obligations. Your compliance obligations drive your board reporting requirements. Your board reporting requirements depend on having accurate, current entity data. If those three systems don't talk to each other — if they're maintained separately by different people using different tools — you're not running a governance system. You're running three partial systems and hoping the gaps between them don't matter.
In practice, they do matter. When AUSTRAC asks about your beneficial ownership register, you need to pull data that's connected to your entity structure. When your board asks for a group-wide compliance status report, the answer depends on data that lives across your compliance calendar, your ASIC lodgement history, and your officer registers. When a director wants to know their personal exposure across all group entities, the answer requires connecting officer appointment records with compliance status across the entire structure.
A governance foundation that scales connects these things at the data level, not the reporting level. The connection isn't built in the board pack. It's built in the system that produces the board pack — so every output is drawing from the same source of truth.
The CFO and the company secretary need different things from a governance system — but they need them to come from the same place.
The company secretary needs:
The CFO needs:
Neither of these is possible with manual systems at scale. Not reliably. Not without a dedicated governance team that's significantly larger than most corporate groups are willing to build.
Yes. You can build this foundation yourself. But it's worth being clear about what that actually involves.
Building it yourself means selecting and integrating a combination of tools — probably a compliance calendar, a document management system, a task management platform, and some kind of reporting layer — and then writing the processes that connect them. Those processes will need to be maintained as the tools change, as your entity structure changes, and as regulatory requirements change.
It means the company secretary (or someone on their team) owns the integration layer — the piece that makes sure data flows correctly between systems. Every time an entity is added, the integration needs to be updated. Every time a reporting requirement changes, the process needs to be adapted.
It means your governance system is only as reliable as the person maintaining it. And it means that when that person leaves, the system they've built is harder to transfer than a commercial system would be.
The buy decision is about recognising that governance infrastructure has the same characteristics as financial or legal infrastructure: it needs to be reliable enough to depend on, auditable enough to trust, and stable enough to outlast any individual contributor. A custom-built system assembled from general-purpose tools rarely meets that standard at scale. A purpose-built governance platform — one designed specifically for multi-entity corporate groups — can.
The cost comparison is worth doing honestly. Maintaining governance manually for a 50-entity group typically involves significant company secretary time (at a minimum, a senior company secretary or a team), external agent costs for ASIC lodgements, advisor fees for compliance reviews, and the hidden cost of the errors that manual systems eventually produce. That cost, when totalled, typically exceeds the cost of a governance platform by a significant margin — before you account for the regulatory risk of getting it wrong.
A governance foundation that scales looks different from what most corporate groups currently have. Here's what it actually involves:
Single source of truth for entity data. Every entity in the group — including dormant ones, including shelf companies, including entities in restructure — has a current, accurate record in one place. That record includes registered office, officers, shareholders, beneficial owners, and compliance status. It updates automatically as changes are made and as regulatory data is reconciled against your records.
Automated compliance calendar. Deadlines are generated from entity data, not manually entered. When an annual review notice is issued, it appears in the system. When a deadline is missed, it's escalated — not discovered three weeks later when someone checks the spreadsheet. When a lodgement is completed, the calendar updates.
Connected beneficial ownership register. UBO data is connected to the entity register, not maintained separately. When ownership changes, the beneficial ownership register reflects it. When regulatory requirements for UBO disclosure change (as they are under Tranche 2 of AML/CTF), the system is built to accommodate the new requirements rather than requiring a manual rebuild of the register.
Board-ready reporting without manual compilation. Group compliance status, entity summary, officer positions, and beneficial ownership overview are available as live outputs, not prepared reports. Board packs draw from the live system, not from a snapshot taken two weeks before the meeting.
Audit trail and governance documentation. Every change is logged. Every lodgement is recorded. Every beneficial ownership update has a timestamp and an attribution. When a regulator asks what your records showed on a specific date, the answer is available — not reconstructed from email chains and spreadsheet version histories.
This is what EntityFlo is built to deliver for multi-entity corporate groups. Not a better spreadsheet. A foundation.
At what point does a corporate group need dedicated governance software?
Most corporate groups benefit from dedicated governance software well before they feel the pain of not having it. The inflection point is typically around 10–15 entities — at this stage, the complexity of tracking obligations, officers, and beneficial ownership across the group starts to exceed what manual systems can reliably maintain. By the time a group reaches 30–50 entities, manual governance is almost always producing gaps that aren't visible until they become problems.
How do we get a single view of compliance status across all our entities?
A single compliance view requires all entity data to live in one system — not spread across spreadsheets, document folders, and external agent systems. The starting point is consolidating entity records into a single platform that can track ASIC obligations, officer records, beneficial ownership, and lodgement history in one place. Once the data is centralised, group-level compliance reporting becomes a live output rather than a manual compilation exercise.
Should the CFO or the company secretary own the governance foundation?
Both need to be invested in it, but accountability typically sits with the company secretary — they own the operational accuracy of entity records, compliance calendars, and lodgement execution. The CFO owns the resourcing and risk decisions: investing in the right platform, building the right team, and ensuring governance risk is visible in group-level reporting. The governance foundation serves both functions, which means both need to be part of the selection and implementation decision.
How do we connect ASIC compliance tracking with beneficial ownership monitoring?
In most corporate groups, these are separate systems — ASIC obligations tracked in one place, beneficial ownership records maintained somewhere else (often in a spreadsheet or a legal matter management system). Connecting them requires either building an integration between the two systems or moving both to a platform that handles both natively. EntityFlo is designed to handle both within a single system, so that changes in entity ownership automatically flow through to beneficial ownership records and compliance obligations.
What does it cost to maintain governance manually for a 50-entity group vs using automation?
Manual governance for a 50-entity group typically requires at least one senior company secretary (or a team of two to three depending on complexity), plus external agent fees for ASIC lodgements (typically $150–$500 per lodgement for a law firm or agent), plus advisor time for compliance reviews and beneficial ownership assessments. In total, this often represents $150,000–$300,000+ in annual cost — before accounting for errors, penalties, or the time senior management spends managing governance risk reactively. Automated governance platforms for groups of this size typically cost a fraction of that, with significantly higher reliability and audit-readiness.
We use cookies to improve your experience. Essential cookies are always active. You can accept all cookies or choose essential only.