Multi-Entity Compliance Reporting Guide

Definitions

Field definitions

Controlled vocabulary guidance

Entity scope

Examples: Legal entity, branch, establishment, reporting unit, subgroup, group, shared service, external party, or not applicable.

Governance: Keep legal-entity type distinct from reporting convenience. Version hierarchy relationships and retain source evidence and effective dates.

Local versus group scope

Examples: Local duty, local report, group oversight, shared control, group mapping, unmapped, not applicable, and local-only.

Governance: A group value may summarize local data but cannot replace a local duty, local owner, local evidence set, filing, or certification.

Applicability

Examples: Applicable, not applicable, pending review, out of scope, expired, superseded, unknown, or disputed.

Governance: Require trigger, source, reviewer, effective period, and rationale. Unknown and pending review must remain visible in group reports.

Compliance status

Examples: Not started, in progress, met, failed, overdue, waived, accepted risk, not applicable, unknown, submitted, rejected, or restated.

Governance: Define status transitions, evidence requirements, owner, period, and whether a status is local, group-derived, or manually overridden.

Certification state

Examples: Not required, prepared, pending local certification, certified, rejected, withdrawn, expired, or restated.

Governance: Keep preparation separate from certification. Require scope, period, criteria, certifier authority, evidence, exceptions, and decision timestamp.

Materiality band

Examples: Critical, high, medium, low, informational, or not assessed.

Governance: Use an organization-designed rule with quantitative units and qualitative triggers. Do not allow an aggregate threshold to hide a critical local event.

Reconciliation result

Examples: Matched, matched within tolerance, variance explained, variance open, late data, duplicate, missing, adjusted, or not testable.

Governance: Record the population, comparison basis, tolerance and unit, source, reviewer, cause, action, and effect on certification or publication.

Lineage state

Examples: Fully traced, partially traced, source unavailable, transformed, manually adjusted, eliminated, restated, or lineage exception.

Governance: Material values should not be presented as fully reliable when the source, mapping, transformation, or adjustment cannot be traced.

Practical workflow

1. State the reporting decisions and boundaries

   Write the decisions the report must support, such as local filing readiness, control oversight, board escalation, regulator response, audit support, or remediation funding. Name the legal entities, branches or establishments, jurisdictions, obligation types, controls, periods, systems, reports, and users in scope. Separate group oversight from any local filing, attestation, certification, or submission that must be completed by an applicable entity or authorized local owner.

2. Build the legal-entity hierarchy

   Create a versioned hierarchy with stable entity ID, legal name, entity type, parent and child relationships, ownership or control relationship where relevant, branch or establishment markers, jurisdiction, registration references, lifecycle status, effective dates, and source evidence. Do not model a branch as a separate legal entity unless the applicable source and reporting rule support that treatment. Preserve historical hierarchy versions so prior reports remain reproducible.

3. Map jurisdictions and applicability

   For each obligation, control, report, and entity, record jurisdiction, regulator or authority, activity or license trigger, applicability decision, effective period, local deadline, language or form requirement, and responsible reviewer. Treat jurisdiction as more than an address: a requirement may follow incorporation, establishment, employees, data, customers, products, regulated activity, contract, or filing status. Route uncertain applicability to qualified compliance or legal review and retain the decision.

4. Separate local duties from group oversight

   Maintain distinct records for local obligations, local reports, local evidence, local owners, and local certifications. Link them to group obligations or oversight reports only through an explicit mapping. A group dashboard may show status, trends, and exceptions, but it does not automatically file, certify, or evidence a local duty. Display local non-applicability, late data, unknown status, and unsubmitted items rather than allowing a green group aggregate to hide them.

5. Define obligation, control, and report ownership

   Assign obligation owner, control owner, evidence owner, report owner, local approver, group reviewer, system steward, and escalation owner separately where responsibilities differ. Record accountable and responsible roles, substitutes, approval authority, service boundaries, effective dates, conflicts, and handoff conditions. Never infer ownership from the entity hierarchy alone; a shared service may operate a control while a local entity remains accountable for its duty.

6. Create local and group definition mappings

   Maintain a definition crosswalk for obligation type, control status, evidence state, breach, exception, overdue, certification, materiality, and completion. Give each local value a source, owner, version, applicability, and mapping to a group value where a valid mapping exists. Allow one-to-many, many-to-one, unmapped, and not-applicable states, and expose semantic differences instead of forcing a false common definition.

7. Design the reporting taxonomy

   Define the dimensions needed for the decision: entity, entity type, parent or group, jurisdiction, regulator, obligation, control, report, owner, business activity, period, status, materiality, exception, evidence, and certification. If a report uses financial data, map the relevant chart-of-accounts or financial taxonomy version separately from the compliance obligation taxonomy. Do not use an account code as proof of obligation applicability or control performance.

8. Specify standard fields and source systems

   Use stable fields for entity_id, jurisdiction_id, obligation_id, control_id, report_id, owner_id, period, cutoff, status, evidence reference, exception reference, certification state, currency, time zone, taxonomy version, lineage ID, and reconciliation status. Name the system of record and source priority for each field. Record missing, conflicting, stale, manually overridden, and not-applicable values rather than silently defaulting them.

9. Set period, clock, and data-cutoff rules

   Declare reporting period start and end, local legal deadline, group reporting deadline, source extraction time, cutoff time zone, daylight-saving treatment where relevant, business-calendar rule, late-arriving data policy, correction window, and restatement process. Preserve source-local timestamps and a canonical timestamp when events cross jurisdictions. A submission received after a group cutoff remains late even if it is included in a later restatement.

10. Handle currency only where the measure needs it

    Keep compliance counts, statuses, evidence states, and certification states in their native semantic units. For amount-based measures, store source currency, amount, precision, exchange-rate source, rate date, rate type, target reporting currency, conversion result, and rounding rule. State whether conversion is spot, period average, closing, contractual, or organization-designed. Never imply that currency conversion makes local monetary thresholds interchangeable.

11. Collect local submissions and evidence

    Collect the entity-level report or control result with source records, evidence links, reviewer, owner decision, period, cutoff, applicability, exceptions, certification state, and late or unknown reason. Preserve the local report as an authoritative submission for its declared duty. Store group-facing extracts separately when transformations, mappings, redactions, or aggregation change the representation.

12. Validate completeness and lineage

    Check expected entities, obligations, controls, reports, evidence items, owners, and certifications against received records. For every material group value, retain source entity, source report, source timestamp, mapping version, transformation rule, aggregation step, elimination or adjustment, reviewer, and output location. Reject or flag orphaned records, duplicate IDs, expired definitions, broken links, missing owners, and values that cannot be traced to an approved source.

13. Apply materiality and exception rules

    Define quantitative and qualitative materiality by report, obligation, entity, jurisdiction, control, and decision. Consider missed legal deadlines, unauthorized access, wrong applicability, missing certification, repeated control failure, unreliable lineage, affected population, duration, regulator or client impact, and aggregation risk. Record exception ID, issue, affected scope, reason, compensating control, owner, approver, due date, expiry or review date, and treatment in local and group reports.

14. Reconcile entity reports before aggregation

    Compare expected entity populations to submitted populations, then compare source totals, statuses, evidence counts, and certification states to the entity report. Explain missing, duplicate, late, amended, out-of-period, and manually adjusted records. Use an explicit tolerance with units. Do not roll an unreconciled submission into a clean group total without labeling the variance and its effect on interpretation.

15. Aggregate with controlled eliminations

    Apply the approved hierarchy, definition mappings, period rules, currency treatment, duplicate policy, and aggregation method. Eliminate only named overlaps, intercompany items, duplicate records, or approved adjustments with source, rationale, owner, approval, amount or count, and effective period. Preserve pre-elimination entity values, the elimination journal or record, post-elimination result, and drill-down. An elimination must never remove a local duty or its evidence from the local report.

16. Review and certify at the right scope

    Route each local report and certification to the authorized entity or local owner named by the applicable rule. Route group oversight reports to the group reviewer with the local submission population, exceptions, reconciliations, and limitations attached. Require the certifier to state scope, period, criteria, evidence reviewed, unresolved exceptions, late or unknown records, restatements, and reliance on group or shared-service data. A group certification cannot silently substitute for a required local certification.

17. Control access, publication, and drill-down

    Limit local, group, auditor, regulator, shared-service, and administrator access by entity, jurisdiction, report, evidence sensitivity, role, and action. Separate view, edit, certify, approve, export, administer, and audit permissions. Apply least privilege, recertification, joiner-mover-leaver controls, and logging. Make every group value drill down to permitted entity reports, source evidence, adjustments, and exceptions without exposing restricted local information to an unauthorized user.

18. Close, restate, and improve the cycle

    Publish the report version, data cutoff, received and expected populations, reconciliation results, material exceptions, certifications, access review, and distribution list. Define late-data, correction, restatement, and archival rules. Track unresolved defects, repeated mapping failures, owner gaps, and local-versus-group disagreements. Reapprove taxonomy, formulas, hierarchy, materiality, and access rules after material regulatory, organizational, system, or reporting changes.

Comparison

Limitations and exceptions

• This is an organization-designed reporting and control method, not legal advice, a filing instruction, an audit opinion, a certification standard, or a guarantee that a report satisfies a regulator, client, court, insurer, or professional body.
• A group report, parent control, or shared-service process does not automatically satisfy an entity-level or jurisdiction-specific obligation. Applicability, local evidence, local deadlines, authorized signers, and local submissions require the treatment specified by the applicable source and qualified reviewers.
• Legal-entity hierarchies, ownership relationships, registrations, branches, establishments, tax attributes, and reporting scopes can change. Use authoritative local records and effective-dated governance instead of treating an organization chart or identifier as permanent legal truth.
• A common taxonomy can improve comparison while still losing local meaning. Preserve source definitions, unmapped values, not-applicable decisions, language, thresholds, and rule versions when they affect a local decision.
• Currency conversion, time-zone normalization, chart-of-accounts mappings, eliminations, and aggregation adjustments can create a false appearance of precision. Keep source units, rate or cutoff basis, rounding, transformation, and unresolved variance visible.
• Certification is limited to the stated scope, period, criteria, evidence, authority, and assumptions. It does not prove that all records were found, all obligations were met, all controls operated continuously, or all legal judgments were correct.
• Access controls and drill-down can conflict with confidentiality, privacy, privilege, client restrictions, data residency, or regulator access requirements. Design authorized views and redactions with appropriate legal, security, privacy, records, and compliance owners.
• Lineage and reconciliation can show that a number was derived consistently without proving that the source was complete or legally correct. Preserve source limitations, manual adjustments, late data, exceptions, and restatements in the report record.

Primary sources

Methodology

Use this organization-designed method as a versioned reporting contract. Start with the entity hierarchy and an applicability register; for each local obligation, record entity, jurisdiction, source, local definition, owner, deadline, evidence, certification need, and group mapping. Define group terms separately and preserve a local-to-group crosswalk with unmapped and not-applicable states. Set period, cutoff timestamp, source refresh, time zone, correction window, and late-data rules before collecting submissions. Report entity coverage (%) = entities with an applicable obligation mapped to a local owner and evidence rule / entities expected in scope x 100; the unit is percent of expected legal entities. Local report completeness (%) = local reports accepted by the local cutoff / local reports due x 100; the unit is percent of local reports due, and group reports do not enter this denominator. Control evidence coverage (%) = applicable controls with current evidence / applicable controls due for evidence x 100. Certification coverage (%) = reports certified by an authorized owner at the required scope / reports requiring certification x 100. For amount-based measures, post-elimination group amount [reporting currency] = sum of eligible entity amounts converted under the declared rate basis [reporting currency] - approved eliminations [reporting currency] + approved consolidation adjustments [reporting currency]. Reconciliation difference [reporting currency] = published group amount - computed post-elimination group amount. For counts, use the analogous unit of report, obligation, control, or entity and never mix counts with currency. Define materiality per decision using amount, count, percentage, affected entities, duration, deadline, qualitative impact, and aggregation risk; show both raw variance and rate. Preserve pre-aggregation values, elimination records, mappings, lineage IDs, manual adjustments, exceptions, certifier decisions, access restrictions, and drill-down. A group oversight result may be complete while one local duty is late or uncertified, so expose the local state instead of averaging it away. Review the model as of August 13, 2026 against current source pages, local law, regulator instructions, contracts, policies, and system behavior; qualified legal, tax, accounting, privacy, security, records, and compliance owners decide applicability and final certification.

FAQs

Related CaseDocker capabilities

Related guides and resources

• Compliance management
• Compliance management information
• Legal playbooks
• Regulatory obligation register design guide
• Compliance control owner matrix
• Regulatory filing readiness checklist