# Company Secretarial Software for Multi-Entity Groups: Make Authority Entity-Specific

**Category:** COMPANY-SECRETARIAL
**Author:** AI Assistant
**Published:** 2026-11-04
**Read Time:** 10 min read

## Summary
A group chart does not explain who approved a decision or under what authority. Make entity-level governance traceable across company secretarial, GRC, contracts and M&A.

## Full Content
Company secretarial software for a multi-entity group should do more than draw an organisation chart. It should help the group answer a harder question: for this decision, which company is acting, what authority governs it, who may approve it, and where is the evidence of that approval? A single group policy does not erase separate entities, differing constitutional documents or the need to maintain a reliable decision trail. Connect company secretarial records with GRC, contracts and M&A, and the group can follow authority changes into the work they affect.

## A group chart is not an authority model

![A group entity map linked to decisions, delegated authority and assurance records](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793782877150/images/8bdb57f42b3acd5948596f72c25ddd40f8d87ebfae071f2f7d407e89117c269e.jpeg)

## What the market scan covers, and what it misses

For “company secretarial software for multi-entity groups” and “GRC vs entity management”, search results and AI summaries focused on entity registers, structures, filing calendars, jurisdiction coverage, board records and software shortlists. The scan read [Board Intelligence's multi-entity buying checklist](https://www.boardintelligence.com/blog/entity-management-software-for-large-multi-entity-enterprises-a-buying-checklist) and official guidance from [Companies House on event-driven filings](https://www.gov.uk/government/publications/life-of-a-company-event-driven-filings/life-of-a-company-part-2-event-driven-filings). The vendor and buyer-guide pages are useful for understanding feature categories, but they are not proof that a particular product will fit a group's specific constitutional arrangements or workflow.

The gap is the hand-off from corporate data to day-to-day authority. A structure chart can show parent and subsidiary relationships, yet fail to answer which company's board approved a decision, whether the decision fell within its powers, who was delegated to act, and what changes when a director or entity structure changes. The open platform position is a consistent connection across company secretarial, GRC, contracts and M&A records. Not every event belongs in every module; the point is to avoid rebuilding context manually when it does matter.

## Treat authority as company-specific, not group folklore

Groups often use shared policies, common committees and central executives. That can be sensible. It can also create a dangerous shortcut: “the group approved it” is repeated as if it identifies the company that made the decision and the authority under which it acted. It may not.

The correct analysis depends on the company, its constitution, the relevant delegation, the decision and any applicable law. Section 171 of the [Companies Act 2006](https://www.legislation.gov.uk/ukpga/2006/46/section/171) says a director must act in accordance with the company's constitution and only exercise powers for the purposes for which they are conferred. This is a statement of directors' duties, not a software specification or a complete guide to corporate authority. The practical consequence is straightforward: preserve the constitutional and delegation context needed to understand a decision. Obtain legal advice where the authority is uncertain.

The official [Companies House event-driven filing guidance](https://www.gov.uk/government/publications/life-of-a-company-event-driven-filings/life-of-a-company-part-2-event-driven-filings) covers events such as director and secretary changes, registered office changes, share capital changes, charges and other company events. It is guidance about filings with the registrar, not an internal delegated-authority manual. Those are separate but related records. A filing accepted by Companies House does not by itself explain how the group's internal approval was obtained or who now owns a decision process.

## Build an entity-level authority record

For each company in scope, keep a clear relationship between the entity identity, constitutional source, current officers, relevant committee or board, delegated authority, decision record and affected business activity. The exact fields depend on the group. Avoid treating a corporate chart as an exhaustive source of legal or operational truth.

1. **Entity identity and status:** Why it matters: Distinguishes the company from the group brand; Question for the company secretary: Which company is the decision about?
2. **Constitution and amendments:** Why it matters: Identifies the source of powers and governance rules; Question for the company secretary: Which version was effective on the decision date?
3. **Directors and committee membership:** Why it matters: Shows who was in office or serving on the body; Question for the company secretary: Is the record current and date-sensitive?
4. **Delegated authority:** Why it matters: Records the permitted scope of a delegated decision; Question for the company secretary: What decision type, threshold or condition applies?
5. **Approval evidence:** Why it matters: Shows what was considered, approved and when; Question for the company secretary: Is the resolution or minute linked to the right entity?
6. **Operational owner:** Why it matters: Connects formal authority to execution; Question for the company secretary: Who carries out and monitors the decision?
7. **Downstream references:** Why it matters: Identifies affected risks, contracts or transactions; Question for the company secretary: Which module or process needs an update?

The structure should not be mistaken for a legal opinion. A software record can show an approved delegation and link evidence, but it cannot cure a defective resolution, prove that a person understood a complex legal issue, or determine whether a director has acted properly. The user must be able to see the underlying source and its effective date.

### 1. Define the entity perimeter

Start with a verified list of companies in scope and how each relates to the group. Record jurisdiction, company number, status and parent relationship where relevant. Identify dormant, recently acquired, recently disposed or special-purpose entities so they do not vanish from a workflow simply because they have little current activity. A missing or stale entity can distort committee packs, sign-off routes and risk ownership.

Use the official register as a source to check company information, but distinguish imported data from internally approved records. Companies House has stated its role is to register company information and make it available to the public. A public register helps users verify data; it does not tell the organisation whether an internal delegation is still appropriate or whether an operational process has been updated.

### 2. Attach each rule to its source and date

A delegated authority matrix is only useful if the group can explain where it came from, who approved it, which entity it covers and when it took effect. Store the source document or decision, version, approval date, effective date and superseding record. If the arrangement is maintained in a policy, board resolution or schedule, link the authoritative text instead of copying an undocumented paraphrase into a field.

When a person or committee changes, avoid overwriting the history. Keep the prior appointment or delegation period and mark what became effective on each date. That allows a later reviewer to reconstruct who was authorised at the time of a particular decision. Do not infer that an executive's title automatically grants identical powers across every subsidiary.

### 3. Separate formal approval from operational execution

A board or committee may approve a policy or transaction while an operational team carries it out. Preserve both the approval and the execution owner. When the approval is conditional, record each condition and how it will be verified. When an item is delegated, record the scope and reporting route. The decision record should distinguish proposed, approved, effective and completed states.

This discipline avoids two familiar errors. First, treating a paper approval as proof that an action was completed. Second, treating an operational team's progress update as evidence that the required body approved the decision. Keep the source, status and evidence type visible.

### 4. Identify events that should trigger a review

Some corporate events should prompt an authority and ownership review: appointment or departure of an officer, a new subsidiary, a change in shareholding, a change to articles, creation or closure of a committee, a major delegation update, an acquisition or disposal, or a material change in operating model. These are process triggers, not an assertion that each event automatically changes every authority.

Assign a responsible owner to decide which downstream records need updating. The company secretary may coordinate the corporate record, but the risk owner, contract owner and transaction lead remain accountable for their own records. Make the trigger visible and allow the reviewer to record “reviewed, no change” with rationale. A review that results in no action still needs a clear outcome when the event was material.

### 5. Test a decision from beginning to end

Choose a real, suitably redacted decision and ask whether a reviewer can trace it. Start from the entity, find the authority source effective on the relevant date, confirm the approving body or person, locate the resolution or approval, see the condition and execution owner, then follow the downstream record. If the reviewer must ask several colleagues which spreadsheet is current, the process is not controlled.

Run the test in both directions. From an entity event, identify which approvals or operational records may need review. From a contract, risk acceptance or acquisition workstream, identify the company and authority context behind the decision. A platform should make the relationship explicit without implying that every connected record is automatically correct.

![Entity authority record connecting the company, constitutional source and approval evidence](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793782877150/images/f1f8d51289ce831b8c344ea4a06ff26f3d847113dd1c6d63a6869c56421cdc84.jpeg)

![A corporate event routed for review across linked governance records](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793782877150/images/2a087fe2fc954b6fd901c8474a4ad8439c1766f539bc5880f55f67064c31d1a2.jpeg)

## Connect company secretarial to the other modules

### GRC: assign the risk to the entity that owns the process

A group risk may be created by activities in a particular subsidiary or held by an entity that owns an asset, data set or control. Link risk, control owner and evidence to the legal entity where the organisation tracks it. If a committee approval or exception affects risk oversight, connect the record with appropriate access. Simplif-i's [GRC page](https://simplif-i.com/solutions/grc) describes risks, assets, objectives, controls, internal audits, findings and remediation. The connection supports traceability; it does not replace the company's risk framework.

### Contracts: identify the company and internal authority behind the signature

The contract record should identify the contracting entity, operational recipient, owner, approval and signatory context. Company secretarial data can help teams review directors and an authority matrix, while the contract workspace tracks agreement versions, obligations, renewals and supplier links. Simplif-i's [contracts page](https://simplif-i.com/solutions/contracts) describes a signing-authority check against its authority matrix. Do not treat that as legal confirmation that a signature is valid in every circumstance; check the required arrangement and applicable law.

### M&A: keep entity changes and governance actions aligned

An acquisition or reorganisation can add, remove or alter relationships between companies. Diligence should identify the records and assumptions that need confirmation; integration should assign owners for each approved change. Keep the target's existing governance evidence distinguishable from the buyer's proposed operating model until the appropriate decision has been made. Simplif-i's [M&A page](https://simplif-i.com/solutions/ma) describes target records, deal-room documents, review findings and post-completion integration milestones. It says AI-assisted findings need human review.

## What to demand from multi-entity software

Ask a vendor to demonstrate one company-level decision with a history, not just a polished structure chart. Test effective dates, permissions, group-to-entity views, export, source-document links, approval states, change history and how an entity event is routed for review. Ask whether each workflow is standard, configured or manual. Ask how the system distinguishes a Companies House fact from an internally approved authority record.

Test awkward cases: two entities with similar names; one executive serving several boards; a committee with a limited remit; a historic approval that predates a policy change; a company recently acquired; and a decision that is recorded but not yet effective. The platform should make uncertainty and missing evidence visible. It should not silently fill a gap with a presumed group rule.

## Where Simplif-i fits

Simplif-i's published company secretarial workspace describes entity profiles, directors, persons with significant control, shareholders, share classes, allotments, transfers, charges, group structure, filing-date tracking and board records. It also states that it reads Companies House data but does not submit filings or perform identity verification. Its authority matrix is described as supporting checks on who may sign a contract. GRC, contract and M&A capabilities provide adjacent records for risk, agreements and transactions. These are product facts, not customer outcome evidence. Simplif-i says it is onboarding its first customers, so buyers should validate entity-scale, jurisdiction, permissions and migration requirements in a test using their own governance model.

## Frequently asked questions

### Is an entity chart enough for governance?

No. A chart shows relationships, but not necessarily the source, scope or effective date of authority, the approval evidence or who executes a decision. Keep the chart linked to current records and company-specific governance sources.

### Does a Companies House filing prove internal approval?

Not by itself. Companies House guidance concerns delivery and publication of company information. Internal approval and delegation evidence are separate matters. Retain both records where they are required for the process.

### Does a group executive have the same authority in every subsidiary?

Do not assume so. Authority depends on the company's constitution, relevant decisions and any delegation. Verify the applicable source for each entity and seek legal advice where the position is unclear.

### What should happen when a director or entity changes?

Use a defined event-driven review. Confirm relevant company records and filings, then assess whether board membership, delegated authority, risk ownership, contract approvals or transaction work needs updating. Record the outcome, including when the review concludes that no downstream change is needed.

### Can software determine whether a board resolution is valid?

A system can store, route and link records. It cannot replace legal analysis of the company's constitution, applicable law, meeting procedure and facts. Treat the platform as a control and evidence workspace, not a legal adjudicator.

## Sources

- [Companies Act 2006, section 171](https://www.legislation.gov.uk/ukpga/2006/46/section/171)
- [Companies House, Life of a company: event-driven filings](https://www.gov.uk/government/publications/life-of-a-company-event-driven-filings/life-of-a-company-part-2-event-driven-filings)
- [Companies House, About us](https://www.gov.uk/government/organisations/companies-house/about)
- [Board Intelligence, Entity management software buying checklist](https://www.boardintelligence.com/blog/entity-management-software-for-large-multi-entity-enterprises-a-buying-checklist)
- [Simplif-i company secretarial solution](https://simplif-i.com/solutions/company-secretary)
- [Simplif-i GRC solution](https://simplif-i.com/solutions/grc)
- [Simplif-i contracts solution](https://simplif-i.com/solutions/contracts)
- [Simplif-i M&A solution](https://simplif-i.com/solutions/ma)

---
Source: https://simplif-i.com/api/blog/readable/company-secretarial/company-secretarial-entity-authority-model-20261104
Web Version: https://simplif-i.com/blog/company-secretarial/company-secretarial-entity-authority-model-20261104
© Simplif-i - Unified Business Management Platform