# Company Secretarial Software for Multi-Entity Groups: Reconcile the Record

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

## Summary
A multi-entity group needs more than a dashboard of companies. Reconcile each corporate record to its source, effective date, approval and owner, then connect changes to GRC, contracts and M&A without confusing tracking with filing.

## Full Content
Company secretarial software for a multi-entity group should make it possible to see what each corporate record says, where that information came from, who verified it and what changed. A group chart is not a control if nobody can explain when it was last checked or which source is authoritative. Start with a reconciliation method for entity, officer, ownership and board information. Then connect relevant changes to GRC, contracts and M&A, while keeping the legal record, filing task and downstream business action distinct.
![A multi-entity corporate register reconciled to source evidence and linked workflows](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793523824357/images/99130ac37c484dfa69b53962f2bce8f73f8a439270b6a8b1d1c67ee02dd7dadb.jpeg)
## What the market scan covers, and what a group still needs to test
For the query “company secretarial software for multi-entity groups”, the pages reviewed included [Digita Company Secretarial](https://tax.thomsonreuters.co.uk/digita/company-secretarial/), [IRIS Company Secretarial](https://www.iris.co.uk/products/iris-company-secretarial/), [Inform Direct](https://www.informdirect.co.uk/), [Kudocs for accountants](https://www.kudocs.co.uk/company-secretarial-software-for-accountants/), [CompanyMinder](https://companyminder.co.uk/), [Capterra's company-secretarial directory](https://www.capterra.co.uk/directory/31001/company-secretarial/software), and the official [Companies House software directory](https://www.gov.uk/software-company-changes).
The pages span accountancy practice software, director-facing company administration and broader entity-management positioning. Their descriptions foreground different workflows: Companies House data, filing, company registers, multi-company management, group structures and administrative tasks. The official Companies House list is specifically about software used to file specified company information. It is not a quality rating, a full company-secretarial feature matrix or a statement that every listed product covers GRC, contracts or M&A.
The gap is not whether a supplier offers registers or a group view. It is whether a group can reconcile its working record to the source, maintain the status of an unresolved difference and route a verified change to the people who need it. A list of entities becomes useful when it is connected to decisions, contracts and risk, without making a filing tracker look like proof that a filing was submitted or accepted.
## Reconciliation is the operating discipline behind a reliable register
Multi-entity groups often maintain several overlapping views: public company data, internal group structure, board records, delegated authority, contract records and operational systems. Those views may be correct for different purposes and may be updated at different times. The task is not to declare that one database is always right. It is to define which source is authoritative for each field, what evidence is needed to confirm a change and who resolves a conflict.
For example, a Companies House record may be relevant to a public filing or officer detail. An internal record may hold a proposed or approved future change. Board minutes may evidence a decision, while a filing record may show whether a submission was made. These items answer different questions. Label them by status and date. Do not silently replace a confirmed record with an unapproved proposal, or treat a board decision as evidence that a subsequent filing was completed.
The [Companies House filing guidance](https://www.gov.uk/software-company-changes) lists software for filing incorporations, company changes and charges. It says a presenter account and company authentication code are needed to use software to file company information. That page can help confirm that a product appears in a specific filing directory and the filing categories shown. It does not establish that a separate register-management tool submits filings. Ask the provider to state exactly what it can file, what it only tracks and what your team must do.
The [confirmation statement guidance](https://www.gov.uk/guidance/filing-your-companys-confirmation-statement) says every company, including dormant and non-trading companies, must file a confirmation statement at least once every year to confirm Companies House information is up to date. It also says a statement is required even if there have been no changes during the review period. Cite and follow the official guidance for current requirements; do not invent a date or deadline for a particular company without checking its record.
![A corporate record being compared against source information, decision evidence and an approval trail](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793523824357/images/d5bddd3dd6976b65d28f1f6d0e5fa4de48a06a7a6241583f51183d64c104b4cb.jpeg)
## A six-field reconciliation record
When a record differs across sources, capture the difference instead of hiding it. A useful reconciliation entry is short enough for teams to maintain and complete enough for a reviewer to understand what happened.
| Field | What the company-secretarial team records | Why it matters |
| --- | --- | --- |
| Entity and data point | The legal entity and exact field being checked | Prevents one company's record being mistaken for another's |
| Source | Where the current value came from | Shows whether the value is public, internal, approved or proposed |
| Effective date | When the value is stated to apply | Separates current data from future or historic changes |
| Difference | What conflicts or remains unverified | Keeps uncertainty visible instead of guessing a resolution |
| Owner and decision | Who will verify it and who can approve a correction | Makes responsibility and authority explicit |
| Completion evidence | What changed, who checked it and what remains outstanding | Distinguishes a completed update from a task merely marked done |
### 1. Define the entity perimeter
Start with the set of companies and other legal structures that the group actually manages. Note which entities are active, dormant, recently acquired, being wound down or otherwise subject to a different process. Do not treat a marketing group chart as the official legal structure. Assign a responsible owner to each entity and define how changes to ownership, officers or status enter the record.
If a group has entities in multiple jurisdictions, record the jurisdiction and identify where the relevant local requirement or adviser must be consulted. A UK-focused filing guide cannot be assumed to cover every country or entity type. The system should help the team see where it needs a different workflow, not conceal the boundary.
### 2. Set a source rule for each important field
For each data point, record the preferred source and the person who can confirm it. A board resolution may be the evidence of an internal decision. An official registry entry may be evidence of what the registry currently reports. A signed document may establish a contractual position. These are not interchangeable. State which source answers the question at hand and how a mismatch is escalated.
### 3. Record status without overclaiming
Use clear states such as “verified”, “awaiting approval”, “submitted”, “accepted” or “requires review” only when they accurately describe the process. If the organisation uses different terminology, define it. A filing task that is ready is not submitted. A submission is not necessarily accepted. A planned change is not an effective change. The workflow should not collapse those into a single green tick.
### 4. Capture the decision and supporting record
When a record changes, keep the relevant approval or decision evidence with the change history. Identify who prepared it, who reviewed it and which entity it concerns. If the change affects a board pack, delegated authority or director record, route it to the appropriate company-secretarial process. Do not infer authority from a platform role label.
### 5. Reconcile after a material event
A structural change, acquisition, officer appointment, contract approval or discovered discrepancy can trigger downstream review. Define which events prompt reconciliation and who starts it. The exact trigger list depends on the group's process and advice. Do not invent an all-purpose legal notification deadline. Check the relevant Companies House guidance or law for any actual filing requirement and timing.
### 6. Close the difference with evidence
A reviewer should be able to see the original discrepancy, the resolution, the source used, the date and any remaining action. If the data cannot be confirmed, preserve that uncertainty and escalate it. Do not make a record look complete by substituting a plausible value. A documented unknown is safer than an undocumented guess.
## Why the company-secretarial record must connect to GRC, contracts and M&A
A company-secretarial register is not the enterprise risk register. It provides the corporate context needed to understand which entity is involved, which board or officer record may matter and where an approved change belongs. GRC uses that context to scope a risk, control or assurance action. It should not assume that a corporate record proves the control operated.
Contracts need the legal party and authority context to support a reliable approval and obligation process. A contract owner should be able to distinguish the company named in the agreement from the group that manages the supplier relationship. Company secretarial should not need to duplicate every clause or renewal date.
M&A needs a clear view of the target and group structure, the status of diligence records and the corporate changes that require follow-up. A transaction finding that changes the entity perimeter should be connected to the relevant corporate record and any resulting risk, contract or integration action. Do not simply paste a target chart into a corporate register and call the post-close update complete.
The link between these modules should answer: which record changed, what source supports it, who approved the change, which other workstreams must review it and how each follow-up is evidenced? That is the practical platform connection. It preserves specialist accountability while avoiding blind hand-offs between separate lists.
![An entity change routed to the relevant corporate, contract, risk and deal workstreams](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793523824357/images/8a5faf496db376a9cdc9bbfa11703ff944a2f8a3a23a135fcc7db6ff9718d948.jpeg)
## Step-by-step software evaluation for a multi-entity group
1. \*\*Bring a real group structure.\*\* Use a representative set of entities with different owners and status, while removing confidential details.
2. \*\*Select three fields to reconcile.\*\* For example, officer, shareholding or filing status. State the source that should support each field.
3. \*\*Introduce a conflict.\*\* Ask the supplier to show an official record that differs from the internal version. Check whether both values and their dates remain visible.
4. \*\*Walk through a change.\*\* Show a proposed change, approval, filing task and confirmed outcome as separate states. Ask who can update each one.
5. \*\*Test the downstream hand-off.\*\* Ask how the change can be linked to a GRC risk, contract approval or M&A integration action without creating duplicate master data.
6. \*\*Inspect access and audit history.\*\* Confirm who can view, amend, review and approve records. Check how the system records a correction.
7. \*\*Test an exception.\*\* Make the evidence incomplete or the responsible owner unavailable. Confirm the system presents an open issue rather than inventing certainty.
8. \*\*Confirm filing capability.\*\* Compare the provider's stated filing capability with the official Companies House directory and the workflow your team actually needs.
A credible demonstration should make boundaries explicit. The supplier should distinguish record management from filing, and a proposed correction from an accepted update. The buyer should leave with a clear operating model: who owns data, who verifies it, who approves it, and which related teams act on the change.
## Where Simplif-i fits
Simplif-i's [company-secretarial workspace](https://simplif-i.com/solutions/company-secretary) describes entity records, group structure, statutory registers for directors, PSCs, members, share capital and charges, filing deadline tracking, board packs, resolutions, votes, minutes and follow-up actions. The page expressly says Simplif-i reads Companies House data and tracks deadlines, but does not submit filings or carry out identity verification. That distinction should be preserved in any buyer's operating model.
The same page says directors recorded for each entity can be synced to board workflows and that an authority matrix can be used to check who may sign a contract. The [GRC workspace](https://simplif-i.com/solutions/grc), [contracts workspace](https://simplif-i.com/solutions/contracts) and [M&A workspace](https://simplif-i.com/solutions/ma) describe the connected risk, agreement and deal work. These are product descriptions, not a guarantee that every record is current or that any filing has been accepted. Confirm your own process and source rules.
## FAQs
### What should multi-entity company secretarial software show first?
It should make the entity perimeter, owner, key corporate records, source and status clear. The team should be able to tell whether information is verified, proposed, awaiting filing or still under review.
### Is a Companies House data feed the same as filing software?
No. Reading or displaying Companies House data and tracking a deadline are different from submitting a filing. Check the product's exact capabilities against the official Companies House directory and confirm who is responsible for any submission.
### How often should a group reconcile its records?
Use a cadence that fits the group's governance process and applicable requirements, and reconcile after defined events that can change the record. Do not use a generic schedule as a substitute for checking current official guidance or the entity's actual filing position.
### Does the official Companies House software list endorse a product?
The GOV.UK page lists products that can be used to file specified categories of company information. It is not a product endorsement or a general assessment of entity-management, GRC or board workflow capability.
### How should a discrepancy be handled?
Keep both the conflicting values visible, record their sources and dates, assign an owner, route the decision to the right authority and close the issue only when the correction or accepted position is evidenced.
## Sources
- [Companies House, Find software to register or file changes to a company](https://www.gov.uk/software-company-changes)
- [Companies House, Filing your company's confirmation statement](https://www.gov.uk/guidance/filing-your-companys-confirmation-statement)
- [Thomson Reuters, Digita Company Secretarial](https://tax.thomsonreuters.co.uk/digita/company-secretarial/)
- [IRIS, Company Secretarial](https://www.iris.co.uk/products/iris-company-secretarial/)
- [Inform Direct, Company Secretarial Software](https://www.informdirect.co.uk/)
- [Kudocs, Company Secretarial Software for Accountants](https://www.kudocs.co.uk/company-secretarial-software-for-accountants/)
- [CompanyMinder, Company Secretarial Software](https://companyminder.co.uk/)
- [Capterra UK, Company Secretarial Software directory](https://www.capterra.co.uk/directory/31001/company-secretarial/software)
- [Simplif-i, Company Secretarial](https://simplif-i.com/solutions/company-secretary)
- [Simplif-i, GRC](https://simplif-i.com/solutions/grc)
- [Simplif-i, Contracts](https://simplif-i.com/solutions/contracts)
- [Simplif-i, M&A](https://simplif-i.com/solutions/ma)


---
Source: https://simplif-i.com/api/blog/readable/company-secretarial/cosec-multi-entity-register-reconciliation-20261101
Web Version: https://simplif-i.com/blog/company-secretarial/cosec-multi-entity-register-reconciliation-20261101
© Simplif-i - Unified Business Management Platform