> ## Documentation Index
> Fetch the complete documentation index at: https://docs.antei.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Hierarchy & Scoping

> Understand how Antei models organizations, entities, jurisdictions, and accounts to enable precise compliance operations.

<Icon icon="folder-tree" size={26} color="#4B5563" />

# Data Hierarchy & Scoping

Antei structures data across five hierarchical levels — Organization, Entity, Office, Jurisdiction, and Account — to support secure, jurisdiction-aware compliance workflows. Each layer is designed for data isolation, auditability, and localized compliance execution.

***

## Why It Matters

* Ensures **clear separation** of data by legal entity and country
* Localizes tax logic while maintaining **central governance**
* Supports multi-country compliance with **modular architecture**
* Prevents drift by scoping workflows to **jurisdictional accounts**

***

## Entity Structure in Antei

```mermaid theme={null}
flowchart TD
  Org[Organization]
  Entity1[Primary Entity]
  Entity2[Subsidiary Entity]
  OfficeA[Office - UK]
  OfficeB[Office - Singapore]
  Juris1[Jurisdiction - UK]
  Juris2[Jurisdiction - SG]
  Account1[Account - UK]
  Account2[Account - SG]

  Org --> Entity1
  Org --> Entity2
  Entity1 --> Juris1
  Entity1 --> Juris2
  Juris1 --> Account1
  Juris2 --> Account2
  Account1 --> OfficeA
  Account2 --> OfficeB
```

***

## Core Concepts

<Steps>
  <Step title="Organization">
    * The top-level workspace in Antei
    * Owns all subordinate entities, users, workflows, and access scopes
    * Primary point of authentication and governance
  </Step>

  <Step title="Entity (Legal Unit)">
    * Every Org has one **primary legal entity**
    * Additional **subsidiary entities** can be added for internal transfers or intercompany use
    * Tax workflows are always scoped to a specific entity
  </Step>

  <Step title="Jurisdiction">
    * Represents the country/state requiring compliance
    * Tied to an office or entity for scoping
    * Holds compliance logic such as tax rules, calendars, return formats
  </Step>

  <Step title="Account">
    * Represents a tax registration in a jurisdiction (e.g. UK VAT, India GST)
    * All filings, invoices, and reconciliations are scoped to this unit
    * Each account has unique metadata, identifiers, and workflows
  </Step>

  <Step title="Office">
    * Physical office or branch under an entity
    * May be required to track **Permanent Establishment (PE)** in certain countries
    * Helps trigger jurisdictional registrations or risk evaluations
  </Step>
</Steps>

***

## Hierarchy Breakdown

| Level                 | Description                                                                    |
| :-------------------- | :----------------------------------------------------------------------------- |
| **Organization**      | A customer-level workspace. Contains users, roles, and primary entity.         |
| **Primary Entity**    | Main legal unit for compliance workflows.                                      |
| **Subsidiary Entity** | Additional legal entities for internal use.                                    |
| **Office**            | Branch or location, used to evaluate PE and local presence.                    |
| **Jurisdiction**      | Country or region requiring compliance.                                        |
| **Account**           | Tax registration (e.g., VAT ID, GSTIN). All filings and logic are scoped here. |

***

## Data Isolation & Integrity

* Data is **isolated by Org** — no cross-org access is possible
* Each entity has its **own data lineage**, including transactions, notices, and filings
* Accounts carry **jurisdiction-specific logic**, which cannot be overwritten globally
* **Multi-entity reconciliation** is available for internal transfers and intercompany workflows
* Entity metadata includes tags like `isPrimary`, `entityType`, and `country_of_incorp`

***

## UI Mapping

The Antei UI adapts based on the hierarchy:

* **Dashboard** shows account-level compliance health by entity and jurisdiction
* **Entity Selector** limits access and actions to scoped records
* **Access controls** ensure users can only operate within permitted accounts
* Invoicing, reconciliation, and filing are always **run at the Account level**
* Logs, documents, and audits are grouped by Org → Entity → Jurisdiction → Account

***

## Real-World Example

You run a SaaS company headquartered in the US and registered in India and Germany:

* **Organization:** `ACME Corp`
* **Primary Entity:** `ACME Inc. (Delaware)`
* **Subsidiaries:**
  * `ACME India Pvt Ltd`
  * `ACME GmbH`
* **Offices:**
  * Bangalore, India
  * Berlin, Germany
* **Jurisdictions:**
  * Karnataka (IN-KA)
  * Berlin (DE-BE)
* **Accounts:**
  * GSTIN: `29ABCDE1234F2Z9`
  * EU VAT ID: `DE999888777`

Each account has its own tax calendar, return template, and local workflow logic.

***

## How This Powers Compliance

* All filings, reconciliations, and tax logic are **scoped by account**
* Avoids accidental data crossover between unrelated entities or countries
* Localizes compliance by **jurisdictional rules and timelines**
* Enables **entity-level access control** and **audit-ready documentation**

***

## Next Steps

* [→ Access Control & Roles](/trust-center/Infrastructure%20&%20Availability/access-control)
* [→ Jurisdictional Compliance Setup](/otherTools/AccountSetup/Introduction)
* [→ Filing Architecture](/otherTools/FilingLogic/Introduction)