Legal Entity and Corporate Secretarial Software: Producing a Current Ownership Chart Before the Deal Team Asks Twice

Why the ownership chart is always three weeks out of date

A bank asks for the current group structure, the ultimate beneficial owners with percentages, and evidence of good standing for eleven entities, because they are onboarding a new facility. The company secretary opens a folder. There is a PowerPoint org chart last edited fourteen months ago. There is a spreadsheet with entity names, numbers and registered offices, maintained by one person who also does board meetings. The minute books are Word files in a directory named by year, plus two physical binders in a cupboard for the entities acquired in 2019. The share capital history for the Luxembourg subsidiary is in a notarial deed in French that nobody in the group has read since it was signed.

So the answer takes three weeks and involves emailing local counsel in four countries. By the time it is assembled, a director has resigned and one entity's registered agent has changed. The pack is wrong on the day it is delivered.

Across corporate services projects we have delivered, the recurring pattern is the same: 15 to 30 hours of senior time per structure request, filing deadlines tracked in a personal calendar, and one or two near misses a year where an annual filing was late. That last one is not administrative. In the UK, persistent failure to file a confirmation statement puts a company on the road to being struck off the register, and a struck off entity in the middle of a group holds assets it can no longer deal with. Deals stop. Bank accounts freeze. The remediation is restoration proceedings and legal fees, all because a deadline lived in a spreadsheet owned by someone on parental leave.

Problem 1: entity data is temporal, and spreadsheets are not

The most common design failure is storing the current state. A director is not a row, it is an appointment with a start date, possibly an end date, a role, and a document that evidences it. Ownership is not a percentage, it is a series of allotments, transfers, buybacks and reorganisations that produce a percentage on a given date. Registered offices change. Company names change. Constitutional documents get amended.

The question a lawyer or a bank actually asks is who were the directors on 14 March 2023, or what was the shareholding immediately before the reorganisation. A spreadsheet holding the current state cannot answer either, and neither can a system that overwrites.

What a custom build does: everything is effective dated. Every officer appointment, every share transaction, every address, with the supporting document attached and the source of truth recorded. Then as at date queries work: give the system a date and it produces the register as it stood, which is exactly what due diligence and litigation both ask for. Diligent Entities and Athennian both handle this properly and it is a real reason to buy either if the rest of the fit is good. What we see driving builds is not the absence of effective dating, it is everything in the next three sections.

Problem 2: packaged systems are built around one company law

Athennian is a well built modern product with genuine strength across North American corporate law. Diligent Entities has broad coverage and enterprise depth. Both are shaped, inevitably, by the legal systems they serve best. If your group is entirely English companies, or entirely US and Canadian corporations, that shape fits.

It stops fitting when the structure contains a Luxembourg SARL with a notarised share register, a Cayman exempted company with a register of members held by the registered office, a Dutch stichting, a Jersey trust with a trustee and a protector rather than directors and shareholders, a Delaware LLC with membership interests and a manager rather than shares and directors, and a general partnership with capital accounts. Those are not variations of a company. They are different objects with different registers, different filings and different notions of ownership. Force them into a share capital model and the workaround starts on day one.

What a custom build does: define entity types with their own attributes, registers and filing obligations, rather than treating everything as a company with optional fields. A trust holds trustees, settlors, beneficiaries and a protector. A partnership holds partners with capital and profit shares that are not the same number. A foundation holds a council. Ownership becomes an interest relationship that can be shares, membership interests, partnership interests or beneficial interests, which is what lets one chart span the whole structure honestly.

Problem 3: filing deadlines are jurisdiction specific and the calendar is a person

Each jurisdiction has its own obligations and its own clock. A UK company files a confirmation statement annually and accounts to its own deadline. A Delaware corporation has an annual report and franchise tax due on 1 March. Registered agent renewals, local director requirements, economic substance filings and beneficial ownership register updates all run on separate cycles. Every one has a different consequence for lateness, ranging from a penalty to dissolution.

What a custom build does: obligations are generated from the entity type and jurisdiction with a rule per obligation, so adding an entity in a country you already operate in automatically creates the right calendar. Each obligation has an owner, a lead time, an escalation and a completed state that requires the filed document to be attached, so completed means evidenced rather than ticked. The calendar stops being a person, which is the whole point, because the person will eventually go on leave at the wrong moment.

Where jurisdiction rules change, and they do, the rule lives in one place and applies to every entity in that country at once. That is the difference between a system and a spreadsheet with conditional formatting.

Problem 4: the outputs are the product, and they are all assembled by hand

Nobody wants an entity database. What people want out of it is a set of documents: the group org chart with percentages, the signing authority matrix showing who can bind which entity for what value, a KYC pack for a bank with certified constitutional documents and current officer lists, a certificate of incumbency, a due diligence disclosure for a transaction, and the board minute for the resolution that authorises all of it.

In most groups every one of those is assembled by hand from the same underlying facts, which means every one of them can disagree with the others.

What a custom build does: generate them from the register. The org chart draws itself from the interest relationships as at any date, including intermediate holdings and minority stakes, and exports in a format the deal lawyers will accept. The signing matrix comes from delegated authority records with limits and expiry. The KYC pack is a template that assembles the current documents for a named entity set and records what was sent to whom and when, which matters the second time the same bank asks. This is the section where corporate services teams get their week back.

Problem 5: beneficial ownership is a chain calculation, not a field

Beneficial ownership regimes across jurisdictions ask who ultimately owns or controls an entity, typically above a percentage threshold, and the answer usually requires multiplying interests up a chain through intermediate holding companies, sometimes through trusts where control and benefit sit with different people. The UK register of people with significant control is one implementation of this idea and other regimes differ in their thresholds and definitions.

Doing this by hand for a group of 200 entities is where errors enter, and the errors are the kind regulators notice.

What a custom build does: compute the chain. Given the interest graph, the system multiplies through the structure, applies the threshold you specify per jurisdiction, and produces the candidate list with the calculation shown so a lawyer can review it rather than recreate it. Where a trust or a nominee arrangement sits in the chain, the system flags it for human judgement instead of guessing, because that judgement is legal advice and should not be automated. Changes anywhere in the structure re-run the calculation and flag entities whose filed position may now be out of date.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, the honest shape for entity management is this. A first release covering the entity register with effective dated officers and ownership, document storage against entities, and the multi jurisdiction filing calendar runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding share capital transaction history, minute books and generated resolutions, org charts and signing matrices, KYC pack assembly, beneficial ownership calculation and external portal access runs $150,000 to $400,000 phased over 6 to 11 months.

What drives cost up here specifically: the number of legal systems, since each one brings entity types, registers and filing rules that are genuinely different work. Non company structures such as trusts, partnerships and foundations, which need their own models. Multi tenancy, if you are a law firm or trust company serving clients, because client separation has to be enforced at the data layer and not by a filter. And the migration, which for entity work means reading minute books, and reading minute books means paralegal time you must budget as part of the project rather than assume.

What keeps cost down: loading your top jurisdictions and the entities that are actually active, and treating dormant entities as a later tranche.

Build versus buy, and when buying is the right call

Buy if you have under about 40 entities in one or two familiar jurisdictions, all conventional companies. EntityKeeper is inexpensive and adequate at that size, and Athennian is excellent if you are North American. If your registered agent is CSC and you are happy with that relationship, their entity management is a reasonable place to keep records, with the obvious caveat that it deepens a dependency on one provider.

Build when two or more of these are true. You hold more than roughly 150 entities. Your structure spans three or more legal systems, particularly if it mixes common law and civil law. You hold trusts, partnerships or foundations that no share capital model fits. You are a law firm or trust company administering entities for clients and need multi tenant separation with client portals under your own brand. Or you have had a filing miss, a restoration, or a deal delayed because the structure could not be evidenced on demand.

How to choose a developer for corporate secretarial software

Ask them how they would store a director appointment. If the answer is a field on the entity, stop. The correct answer is an effective dated relationship with a start, an optional end, a role, and an evidencing document, and they should raise as at date queries without being prompted.

Ask how they would model a Jersey trust and a Delaware LLC in the same system as an English limited company. A developer who has done this will describe entity types with distinct registers and a general interest relationship. One who says they will add a type field to a companies table is about to build you a system that cannot hold half your structure.

Ask what they will do about beneficial ownership calculation through a chain, and check that their answer includes flagging trusts and nominee arrangements for human judgement rather than computing through them silently. That restraint is a sign they understand where software should stop.

Ask who owns the code and where the data is hosted, in writing, before kickoff. You should own the repository, the infrastructure accounts and the right to bring in another firm. At Digital Heroes the client owns the code from the first commit. For entity data, also agree the export format up front, because a register you cannot extract in a structured form is a register you do not really control.