> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/accountants/setting-up/multi-entity/adding-and-removing-entities.md).

# Adding & Removing Entities

Add or remove entities as your client's business structure changes.

### Adding an entity

Adding entities beyond the first requires a **Plus** plan or above.

**From the Accounts tab:**

1. Go to the **Accounts** tab.
2. Click **Add entity** in the top right. This opens a guided full-page flow to set up the new entity.

You can also press **⌘K** and select **Add entity**.

**From the Clients tab:**

1. Navigate to the client and click the options menu (⋯).
2. Click **Add entity**.

Kick generates a standard (but completely customizable → see [Chart of Accounts](/accountants/setting-up/chart-of-accounts.md)) chart of accounts for the new entity based on the entity type you select.

{% hint style="info" %}
**Tip:** The bookkeeping start date you set during entity creation controls when transaction data begins syncing for connected accounts. This can be updated later from the Clients tab.
{% endhint %}

***

### Removing an entity

Deleting an entity permanently removes **all** associated data. Take this action with caution.

1. Go to the **Clients** tab.
2. Hover over the entity and click the options menu (⋯).
3. Click **Delete entity**.

Not all roles can delete entities. See [Permissions](/accountants/managing-clients/roles-and-permissions.md) for more.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/accountants/setting-up/multi-entity/adding-and-removing-entities.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.