Subsidiary Legal Entity Records and Governance Controls

Definitions

Field definitions

Controlled vocabulary guidance

Entity relationship

Examples: Parent, subsidiary, affiliate, commonly owned, controlled, contractual, branch, establishment, joint venture, fund, or reporting-only.

Governance: Store the relationship basis, source, effective dates, ownership or control description where relevant, and distinguish legal relationships from reporting convenience.

Entity lifecycle status

Examples: Proposed, forming, active, inactive, suspended, merging, dissolved, sold, retired, disputed, or unknown.

Governance: Require source, effective date, reviewer, and treatment of pending or disputed states; never use a dashboard status as proof of legal standing.

Jurisdiction basis

Examples: Incorporation, registration, establishment, activity, property, employees, customers, contract, regulator, court, financing, or filing.

Governance: A record may have multiple jurisdiction bases. Preserve each source and applicability decision instead of assigning one global jurisdiction.

Source authority level

Examples: Primary legal or regulator source, official registry record, organization record, executed instrument, qualified advice, secondary reference, unresolved, or unavailable.

Governance: The label describes source scope and provenance, not an automatic truth ranking. Record date, access, completeness, and limitations.

Governance action state

Examples: Proposed, notice prepared, pending approval, approved, signed, filed, effective, implemented, rejected, withdrawn, expired, or superseded.

Governance: Keep approval, signature, filing, effective date, and implementation as separate events unless the governing source clearly combines them.

Obligation status

Examples: Applicability pending, applicable, not applicable, planned, in progress, met, late, failed, waived, accepted risk, disputed, or unknown.

Governance: Require source, owner, period, evidence, decision authority, and local or group scope. Unknown and disputed must remain visible in reporting.

Attestation state

Examples: Not required, prepared, under review, approved, attested, rejected, withdrawn, expired, restated, or exception attached.

Governance: State the entity, population, period, criteria, evidence, signer capacity, limitations, exceptions, and decision timestamp.

Exception state

Examples: Open, mitigated, accepted risk, overdue, disputed, pending counsel, pending source, closed, expired, or superseded.

Governance: Do not treat an accepted risk or compensating control as closure. Preserve target date, expiry or review date, approver, and report treatment.

Practical workflow

1. Define recordkeeping decisions and the entity population

   State which records and evidence the model must support for entity onboarding or closure, board and shareholder actions, authority, statutory filings, licenses, intercompany agreements, guarantees, disputes, obligations, attestations, and changes. List the legal entities, branches, establishments, affiliates, funds, joint ventures, and reporting units in scope. Keep legal scope, operating scope, and reporting convenience separate, and preserve an explicit out-of-scope decision.

2. Build the versioned entity hierarchy

   Create one record per entity or explicitly identified non-entity unit and distinguish parent, subsidiary, affiliate, commonly owned, controlled, contractual, branch, establishment, and reporting relationships. Record stable internal ID, legal name, aliases, entity type, incorporation or formation jurisdiction where sourced, operating locations, status, parent or related entity, relationship basis, ownership or control description, effective dates, and source references. Preserve historical versions so an earlier decision can be reproduced.

3. Separate identifiers from legal conclusions

   Use identifiers such as a local registration number, LEI, tax reference, internal ID, or regulator reference only with its issuing source, scope, status, and retrieval date. Do not treat a matching name, identifier, organization chart, LEI, commercial database, or group record as proof of legal existence, authority, ownership, solvency, good standing, or current control. Record conflicting identifiers, aliases, duplicates, and unresolved matches for review.

4. Map jurisdiction and applicability

   For every filing, license, action, obligation, dispute, record, and review, state why a jurisdiction applies and which source supplies the rule. Consider incorporation, registered office, establishment, business activity, property, employees, customers, data, contract, regulator, court, financing, or transaction triggers. Record local deadline, language, form, signatory, evidence, and applicability decision. Route uncertain or conflicting analyses to qualified local counsel or the accountable specialist.

5. Capture ownership, directors, officers, and appointments

   Track ownership or control interests, voting or appointment rights, directors, officers, managers, secretaries, authorized representatives, committees, and end dates with role, entity, source, effective period, and review status. Distinguish legal title, beneficial ownership, significant influence, economic interest, control, nominee or service roles, and internal responsibility. Keep people and entity records linked without assuming that a group role or shared address proves the same legal capacity everywhere.

6. Design delegated authority by action and entity

   Create an authority matrix for opening or closing accounts, entering agreements, issuing or receiving notices, making filings, granting security, giving guarantees, settling disputes, hiring advisers, spending funds, approving policies, and signing or certifying records. Record the entity, action, threshold, role or named person, delegation instrument, conditions, substitutes, effective dates, expiry, escalation, and whether the system blocks or only flags an action. Separate operational routing from legal advice.

7. Control board, shareholder, and member actions

   Maintain an action register for resolutions, written consents, meeting notices, agendas, quorum or approval evidence, conflicts, minutes, signatures, conditions, filings, and follow-up. Link each action to the entity, action type, authority source, participants, date, effective date, required notice, approval status, and supporting documents. Treat board or shareholder approval, delegated signature, execution, filing, and implementation as distinct events unless the applicable source clearly combines them.

8. Track statutory filings and notices

   For each entity and jurisdiction, maintain an applicability-controlled filing register with source, filing type, period or triggering event, due rule, extension, form, required signatory, submission channel, receipt, status, correction history, and evidence. Include formation, changes to directors or officers, registered details, ownership or control updates, accounts or reports, charges, dissolutions, and other filings only where the identified source requires them. A central calendar should not hide local filing responsibility.

9. Govern licenses, permits, and regulated activities

   Map each license, permit, registration, approval, accreditation, or regulated activity to the entity, location, activity, regulator, scope, conditions, issue and expiry dates, renewal window, responsible owner, evidence, suspension or change triggers, and local review. Distinguish a license from an entity registration and an internal policy. Track whether a group license can cover the relevant entity or location only when the applicable source and qualified reviewer support that treatment.

10. Review intercompany agreements and guarantees

    Classify agreements by entity pair and relationship basis, then record purpose, services or funding, consideration or allocation method, tax and accounting review, transfer-pricing or related-party considerations where relevant, approvals, authority, execution, obligations, amendments, termination, and source documents. Track guarantees, indemnities, security, letters of comfort, and other credit support separately with beneficiary, exposure, cap, term, release condition, consent, and reporting owner. Do not infer enforceability or financial treatment from the repository record.

11. Connect disputes, claims, and investigations

    Create a related-work record for disputes, claims, investigations, threatened proceedings, regulatory inquiries, and settlement decisions. Link the affected entity, jurisdiction, forum, parties, counsel, authority, facts, exposure range, deadlines, privilege or confidentiality boundary, documents, insurance or guarantee relationship, reserve or reporting owner where relevant, status, and resolution. Preserve uncertainty and disputed facts rather than converting a preliminary assessment into a legal conclusion.

12. Maintain obligations and recurring actions

    Link obligations to the entity, jurisdiction, source, activity, license, agreement, action, owner, frequency, trigger, due rule, evidence, status, escalation, and exception. Include statutory, regulatory, contractual, financing, board, shareholder, license, records, insurance, dispute, and policy obligations where applicable. Keep source clause or citation, effective period, local variation, and change trigger. A reminder is not evidence that the obligation was performed.

13. Govern records and evidence

    Define record classes for formation and constitutional documents, registers, ownership evidence, appointments, delegations, resolutions, minutes, filings, receipts, licenses, agreements, guarantees, disputes, obligations, advice, attestations, exceptions, and change history. Set owner, source, version, confidentiality, privilege or access boundary, retention or hold rule, disposition decision, integrity evidence, and relationship links. Preserve immutable originals where needed and distinguish a derived index from the source record.

14. Set beneficial-ownership and source boundaries

    For each ownership or control assertion, record the definition used, source jurisdiction, source type, date, person or entity scope, direct or indirect path, confidence, corroboration, conflict, and reviewer. Reconcile registry information, filings, constitutional documents, contracts, financing records, and organization-provided evidence only for the decision at hand. A public or private source may be incomplete, delayed, inaccessible, or defined differently; unresolved source conflict must remain visible.

15. Run change-event management

    Trigger a controlled review when an entity is formed, merged, acquired, sold, renamed, redomiciled, dissolved, changes ownership, appoints or removes a director or officer, changes authority, obtains or loses a license, signs a guarantee, changes a registered address, enters a dispute, or receives a regulatory notice. Record event source, effective date, affected records, impact assessment, required filings, counsel review, communications, approvals, completed updates, and residual exceptions.

16. Collect attestations and approve exceptions

    Use attestations for a named entity, population, period, criteria, evidence set, responsible owner, reviewer, limitations, and decision date. Maintain an exception register for missing source data, late filings, authority gaps, unresolved ownership conflict, expired license evidence, incomplete records, local process variance, or system limitations. Require rationale, risk, compensating control, approver, target date, expiry or review date, and explicit treatment in reports. An attestation should expose exceptions, not erase them.

17. Route local counsel and specialist review

    Define review triggers for incorporation and restructuring, authority or enforceability questions, local corporate actions, regulated activity, licensing, beneficial ownership, guarantees, disputes, privilege, tax, accounting, employment, privacy, records, and cross-border transfers. Record reviewer capacity, jurisdiction, question, materials reviewed, advice date, conclusion or limitation, reliance boundary, action owner, and whether the review must be refreshed after a change. A central legal team can coordinate without replacing local expertise.

18. Report coverage, conflicts, and change health

    Publish entity-level and group oversight views with as-of date, population, source freshness, authority coverage, filing status, license currency, open disputes, obligation status, record completeness, attestations, exceptions, and unresolved conflicts. Preserve drill-down to permitted evidence and never collapse local non-applicable, pending, unknown, late, or disputed states into a clean group result. Review metrics, source quality, change latency, and recurring exceptions with accountable owners.

Comparison

Limitations and exceptions

• This is an organization-designed legal-operations governance framework, not legal advice, a corporate-secretarial instruction, a filing calendar, an audit opinion, or a conclusion that any entity, person, action, license, ownership assertion, or agreement is legally valid.
• Entity registries, regulator records, LEIs, public filings, commercial databases, organization charts, and internal records have different scopes, update cycles, access rules, definitions, and error modes. None should be treated as universal proof of legal status, authority, ownership, control, solvency, or good standing.
• Corporate governance, statutory filing, licensing, beneficial ownership, recordkeeping, board action, shareholder action, guarantee, dispute, and authority requirements vary by entity type, jurisdiction, source, facts, and time. A group baseline cannot replace a local applicability decision.
• Beneficial ownership and control terms are source-specific. A registry or filing may omit indirect interests, use a different threshold or definition, be delayed, be inaccessible, or contain an unresolved conflict. Record the assertion and its boundary rather than presenting a single field as complete truth.
• A delegated-authority matrix is an operational control and routing aid. It does not replace constitutional documents, board or shareholder action, powers of attorney, local law, lender consent, regulatory approval, or transaction-specific legal review.
• A filing, license, agreement, guarantee, dispute, obligation, or attestation record can be complete as a workflow record while the underlying legal position remains uncertain. Preserve source documents, reviewer limitations, pending decisions, disputed facts, and exceptions.
• Centralizing records and local counsel coordination can improve visibility but may create privilege, confidentiality, privacy, access, data-residency, records, or conflict risks. The organization must set permitted views, retention, sharing, and review boundaries.
• Percentages and thresholds in the methodology are internal measurement conventions. They do not establish a regulator, court, auditor, lender, insurer, client, or local counsel requirement and should not be applied outside the declared population, period, unit, and exclusions.

Primary sources

Methodology

Use this as a versioned legal entity master-data and corporate-recordkeeping control model reviewed as of August 13, 2026 against current primary legal and regulator sources, entity documents, filings, licenses, agreements, advice, and system behavior. First declare the entity population, non-entity units, jurisdictions, record classes, decision purposes, reporting period, cutoff, source hierarchy, access boundary, and exclusions. For each material fact, preserve source, retrieval date, effective date, definition, reviewer, confidence, conflict, and historical value. Entity hierarchy completeness (%) = in-scope entity records with required ID, legal name, entity type, jurisdiction basis, status, relationship, source, and effective date / expected in-scope entity records x 100; the denominator excludes approved out-of-scope units and duplicate records, while unresolved records remain in the denominator. Governance evidence coverage (%) = required governance facts with current source and review state / required governance facts in scope x 100; exclude only facts formally marked not applicable by an authorized reviewer. Authority coverage (%) = actions requiring authority review with a current authority record / actions requiring authority review in the period x 100; canceled test actions are excluded, while failed, late, or disputed actions remain in the denominator. Filing timeliness (%) = applicable filings submitted by the applicable deadline or approved extension / filings due in the period x 100; exclude formally withdrawn or not-applicable filings, but include late filings. License currency (%) = active licenses requiring evidence with current scope and expiry evidence / active licenses requiring evidence x 100; exclude inactive activities and licenses formally marked not applicable. Obligation coverage (%) = applicable obligations with owner, source, due rule, status, and evidence requirement / applicable obligations in the register x 100; pending applicability records are reported separately and excluded until a reviewer decides applicability. Attestation completion (%) = required attestations received by the declared cutoff / required attestations due by the cutoff x 100; exclude not-required and withdrawn attestations, but retain rejected, late, and exception-attached attestations in the denominator. Exception closure (%) = exceptions due for closure in the period that were closed with evidence / exceptions due for closure in the period x 100; accepted-risk, disputed, and overdue exceptions remain open. Source conflict rate (%) = records with an unresolved conflict among comparable sources / records for which two or more comparable sources were reviewed x 100; single-source records are excluded from this denominator and reported separately. Change processing latency is p50 and p95 elapsed days from accepted material change evidence to completion of required record updates for changes closed in the period; exclude canceled or invalidated events and report pending events separately. Keep every percentage bounded to 0-100, publish numerator, denominator, unit, period, source, exclusions, and unknown count, and never present an internal metric as proof of legal compliance. Re-test after entity, ownership, authority, filing, license, agreement, dispute, obligation, source, system, or law changes and require qualified local counsel or specialist review where the decision turns on jurisdiction-specific law.

FAQs

Related CaseDocker capabilities

Related guides and resources

• Legal playbooks
• Compliance management
• Contract management
• Case management
• Multi-entity compliance reporting guide
• Multi-entity contract management operating model