# Company Secretarial Software for Multi-Entity Groups: Keep Director Interests with the Right Decision **Category:** COMPANY-SECRETARIAL **Author:** AI Assistant **Published:** 2026-11-17 **Read Time:** 9 min read ## Summary Record director interests against the right company, transaction and decision. Keep sections 175, 177 and 182 distinct, and connect the governance record to contracts, GRC and M&A follow-up. ## Full Content Company secretarial software for a multi-entity group should keep a director’s interest declaration attached to the right company, meeting, transaction and decision. The record must show what was declared, to whom, when, how the board dealt with it and what restrictions or follow-up applied. It should not flatten distinct duties into one generic “conflict register”. Connect the company secretarial record to the relevant contract, GRC risk and, where the interest arises during a transaction, the M&A workstream. The software organises evidence. It does not replace the board’s judgement or legal advice. ## What the market scan covers, and the gap it leaves Search results for company secretarial software for multi-entity groups divide into two broad propositions. Inform Direct’s public feature page emphasises UK corporate administration and electronic Companies House filings. Board Intelligence’s IQ Entities page focuses on entity records, group ownership and governance teams. Other search results point toward board portals or international entity-management systems. The platform view is more fragmented: product pages often show either filing workflows, entity records or board governance, while the buyer’s actual task is to connect a declaration to an entity-specific decision and any contract or risk consequence. That distinction matters. A filing package may help maintain statutory records, but it does not automatically demonstrate how a board considered a director’s interest. An entity map may show ownership and officers, but it does not by itself evidence a declaration, an authorisation or a decision about participation. A board portal may preserve minutes, but the decision may also change who can negotiate or sign a contract. The gap is not a claim that every vendor lacks a feature. It is a workflow question: can you follow the record across company secretarial, GRC, contracts and M&A without losing the identity of the company or the decision-maker? The legal starting point is the [Companies Act 2006](https://www.legislation.gov.uk/ukpga/2006/46/contents). Sections 175, 177 and 182 address different situations. Read the applicable provisions and the company’s articles with counsel; do not turn a product template into a legal conclusion. The [Financial Reporting Council’s UK Corporate Governance Code 2024](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/uk-corporate-governance-code/) is relevant only to companies within its scope. It is not a universal governance code for every private company in a group. ## Keep the legal categories separate Section 175 concerns the duty to avoid a situation in which a director has, or could have, a direct or indirect interest that conflicts or may conflict with the company’s interests. The section includes the exploitation of property, information or opportunity. The Act distinguishes conflicts arising from a transaction or arrangement with the company, which are dealt with separately under sections 177 and 182. A section 175 situation may be authorised by the directors where the statutory conditions are met. The [section 175 text](https://www.legislation.gov.uk/ukpga/2006/46/section/175) should be read alongside the company’s articles and the other relevant provisions. Section 177 deals with a director’s declaration of the nature and extent of an interest in a proposed transaction or arrangement with the company. Section 182 covers declaration of an interest in an existing transaction or arrangement. The sections include qualifications and alternative routes, so avoid turning a summary into a complete procedural checklist. For exact wording, consult [section 177](https://www.legislation.gov.uk/ukpga/2006/46/section/177) and [section 182](https://www.legislation.gov.uk/ukpga/2006/46/section/182). The system should therefore record the facts and the decision path, rather than tagging every item “conflict” and treating them as identical. At minimum, capture which company is concerned, what situation or transaction is involved, what the director declared, when and to whom the declaration was made, the provision or procedure considered, who reviewed it and what was decided. The company’s governing documents and legal advice may determine the appropriate process. Store that basis with the record, and make clear when a legal conclusion remains outstanding. ## A practical record: declaration to decision to action A defensible record is useful because it enables the board and its advisers to reconstruct the process. It should be concise, consistent and linked to the underlying materials. It should not expose privileged advice or confidential commercial detail to people who do not need access. 1. **Identify the entity.** Record the exact company name and company identifier, not merely “the group”. Identify the board or committee involved and the meeting date or written decision process. In a group, the same director may hold office in more than one company, but each company’s records and decisions must remain distinguishable. 2. **Describe the interest in plain terms.** Record the nature and extent of the declared interest, the director’s explanation, the counterparty or opportunity where relevant, and any source documents. Do not rewrite the declaration as a broader legal conclusion unless the appropriate reviewer has made that assessment. 3. **Classify the route for review.** Note whether the issue concerns a potential conflict situation or an interest in a proposed or existing transaction. Link to the specific Companies Act provision or other applicable process considered. Record uncertainty and who has been asked to resolve it. 4. **Capture the governance response.** Record who considered the matter, whether the board or another authorised body made a decision, the decision and its rationale, and any limits placed on access, participation or information flow. The proper procedure depends on the company’s constitution and circumstances; do not assume a universal recusal rule from software defaults. 5. **Connect the commercial record.** Link the relevant contract, negotiation, supplier, customer, acquisition target or investment opportunity. Record any affected authority matrix or approval step. If a director’s interest changes who may approve or sign, the contract workflow must use the updated authority decision. 6. **Assign follow-up.** Give any action an owner and due date: obtain advice, update a record, circulate revised papers, confirm an approval or review the arrangement. Include a trigger for reconsideration if the transaction terms or director’s circumstances change. 7. **Preserve the audit trail.** Keep the original declaration, the final minutes or written decision, supporting papers and later changes under the organisation’s retention and access rules. Record who altered the data and why. Do not overwrite the original statement with a later summary. 8. **Check closure.** A secretary or designated reviewer should confirm that the minutes, decision, linked contract or authority record and any follow-up action agree. A completed task is not proof that the underlying decision was properly recorded. | Record element | What to retain | What it helps answer | | --- | --- | --- | | Company and governance body | Entity identifier, board or committee, meeting or decision date | Which company considered the matter? | | Declaration | Nature, extent, source and date of the director’s declaration | What was actually disclosed, and when? | | Review route | Provision or internal procedure considered, reviewer and advice status | How was the issue assessed? | | Decision | Decision-maker, rationale, minutes and any restrictions | What did the company decide? | | Connected work | Contract, transaction, authority or risk reference | What business activity could be affected? | | Follow-up | Owner, due date, trigger and closure evidence | Was the response implemented and reviewed? | ## Why a group spreadsheet is not a governance model A spreadsheet can list directors, interests and due dates. It becomes unreliable when one row tries to serve as the legal record, board minute, contract approval, conflict assessment and group-wide risk response. Those are connected but distinct records. A declaration may be relevant to one company’s decision and not another’s. A group-level view can help spot patterns, but it must not erase the company-by-company decision trail. The same problem appears when a declaration is retained only in a meeting pack. A later contract manager may not know that an approval route was restricted. A GRC team may see an associated risk but not the governance decision or its conditions. During an acquisition, an inherited target-board approval may need review against the post-completion structure; copying it into the buyer’s records does not establish that it still applies. A connected system should preserve the original record, link the downstream work and make review ownership clear. Access control is part of the design. The record may include sensitive personal information, commercial negotiations or legal advice. Decide who can view the declaration, who can see the board’s formal decision, and what a contract approver needs to know to follow the restriction without receiving unnecessary personal or privileged material. A platform should support least-privilege access and a reviewable history. The board secretary should not have to choose between a single readable record and appropriate confidentiality. ## Make the four-module connection operational A platform connection is meaningful only when it changes the hand-off: - **Company secretarial:** maintain the entity, director, meeting, declaration, minutes, resolution and decision references. Keep the record specific to the company whose board considered it. - **GRC:** link material governance issues to risks, controls, actions and review evidence. A concern should have a clear owner and escalation route, but do not assume every declaration is automatically a risk event. - **Contracts:** connect the decision to the affected agreement, counterparty and approval authority. If the board restricts participation or delegates a decision, ensure the contract approval process reflects that decision. - **M&A:** identify declarations or approvals relevant to the target, transaction team, negotiations or post-close governance. Preserve the diligence source and carry a validated action into integration rather than assuming the data-room record is complete. This is not a direction to publish sensitive board information in a general company-wide dashboard. Use linked identifiers, role-based permissions and a clear distinction between the underlying confidential declaration and the operational instruction needed by another team. For example, a contract approver may need to know that an alternative authorised signatory is required. They may not need the full declaration or associated legal analysis. ## How to test company secretarial software Use a realistic scenario involving a director who sits on two group boards and declares an interest in a proposed contract with a counterparty connected to that director. Ask the vendor to demonstrate separate records for each relevant company, the declaration, the route to review, the board decision, any limitation on access or approval, the affected contract and the follow-up. Then change the facts: the contract is already in force, a new company is acquired, or the director’s interest changes. Can the platform preserve the old decision and show who must review the new facts? Ask these questions: - Can the system distinguish a declaration about a potential conflict situation from a declaration concerning a proposed or existing transaction? - Does the record retain the exact company and board, rather than only a group label? - Can minutes or decisions link to a contract and authority workflow without exposing the entire board pack? - Can users record that legal review is pending and prevent an unreviewed template from being treated as a conclusion? - Does the audit trail preserve the original declaration and subsequent decisions? - Can the business export the records in a usable form if it changes systems? - Are any filings or identity-verification steps actually performed by the product, or does it only track records and deadlines? The last question matters because vendors use “company secretarial” to describe different scopes. Inform Direct’s public feature page describes filing and company administration workflows. Simplif-i’s company secretarial page says it tracks filing deadlines and records, while clarifying that filings and identity verification are completed through Companies House or an authorised agent. Check the actual scope before making a control owner rely on a reminder as a completed filing. ## Where Simplif-i fits Simplif-i describes its company secretarial workspace as covering entity structures, statutory registers, filing deadlines and board packs, including conflict declarations and board decisions. Its page also says director records can be connected to board work and to an authority matrix used to check who may sign a contract. See the [Simplif-i company secretarial solution](https://simplif-i.com/solutions/company-secretary). The platform connection is relevant to this article: company records can link to [GRC](https://simplif-i.com/solutions/grc), [contracts](https://simplif-i.com/solutions/contracts) and [M&A](https://simplif-i.com/solutions/ma). The product page says it tracks deadlines but does not file with Companies House or carry out identity verification. Verify that the specific conflict workflow, permissions and decision record meet your own governance requirements. Simplif-i is onboarding its first customers, so these are product capabilities described on the public site, not a claim of established customer outcomes. ## Frequently asked questions ### Is a director’s conflict declaration the same as a transaction-interest declaration? Not necessarily. Section 175 covers the duty to avoid certain conflict situations, while sections 177 and 182 address declarations relating to interests in proposed and existing transactions or arrangements. Read the statutory wording and company constitution for the facts at hand. ### Must every declaration appear in a group-wide register? The workflow should make declarations retrievable and connected to the correct company record, but do not assume one universal register format or disclosure rule from this article. Confirm the company’s legal and governance requirements, access controls and retention approach with advisers. ### Does software decide whether a director can participate in a meeting? No. The appropriate response depends on the facts, applicable law, the articles and the company’s decision. Software should record the decision made by the authorised body and any conditions, not impose a universal rule by default. ### How should a declaration affect contract approval? Link the relevant governance decision to the contract and authority workflow. Give the approver the operational instruction needed to follow the decision, with access to supporting confidential material restricted appropriately. ### What changes when a group acquires a company? Review the target’s governance records, entity structure, delegations and outstanding decisions against the combined operating model. Preserve the source and decision history. Assign an integration owner to validate what carries forward; do not assume a target record automatically governs the acquirer or other subsidiaries. ### What should we ask vendors to demonstrate? Ask for a live, company-specific trail from declaration to review, minute, decision, affected contract and follow-up. Include permissions and an export test. A slide showing a group chart is not evidence that the workflow handles a real board decision. ## Sources - [Companies Act 2006, section 175](https://www.legislation.gov.uk/ukpga/2006/46/section/175) - [Companies Act 2006, section 177](https://www.legislation.gov.uk/ukpga/2006/46/section/177) - [Companies Act 2006, section 182](https://www.legislation.gov.uk/ukpga/2006/46/section/182) - [Financial Reporting Council, UK Corporate Governance Code 2024](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/uk-corporate-governance-code/) - [Inform Direct, Company secretarial software features](https://www.informdirect.co.uk/features/) - [Board Intelligence, IQ Entities](https://www.boardintelligence.com/iq-entities-demo) - [Simplif-i, Company secretarial solution](https://simplif-i.com/solutions/company-secretary) --- Source: https://simplif-i.com/api/blog/readable/company-secretarial/cosec-director-interest-record-20261117 Web Version: https://simplif-i.com/blog/company-secretarial/cosec-director-interest-record-20261117 © Simplif-i - Unified Business Management Platform