> 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/setting-up/multi-entity.md).

# Multi-Entity

Manage multiple businesses from one Kick workspace.

If you own more than one business, or have a holding company structure, Kick lets you manage all your entities from a single workspace. Each entity has its own books, reports, and transaction history.

Multi-entity requires a **Plus** plan or above. On Plus, an additional entity costs nothing until it reaches 250 transactions. Once it passes that mark it stays billed at $50/month for unlimited transactions, and the count doesn't reset at the start of a new year. If you're on an older Plus plan, your workspace is capped at 5 entities until you move to current pricing.

***

### How entities work

Each entity in your workspace operates independently with its own:

* Financial statements ([P\&L](/reports/profit-and-loss.md), [Balance Sheet](/reports/balance-sheet.md), etc.)
* Connected accounts and integrations
* Documents and [tasks](/working-with-your-team/tasks.md)
* Transaction history

You can view transactions across all entities in a single feed, or filter to a specific entity at any time.

***

### Add an entity

1. Go to the **Accounts** tab
2. Click **Add entity**
3. Enter the business name, entity type, country, industry, and annual revenue
4. Complete the flow to create the entity

Step 2 opens a guided setup flow. You can also open **⌘K** (or **Ctrl+K** on Windows) and choose **Add entity**.

Once created, connect the entity's accounts the same way you connected your first business.

→ [Connect Your Accounts & Integrations](/setting-up/connect-your-accounts-and-integrations.md)

***

### Moving expenses between entities

If a transaction lands in the wrong entity, you can fix it from the [Transactions](/common-workflows/transactions.md) tab: select the transaction and use **Move to entity**. Kick automatically generates the intercompany [journal entries](/common-workflows/journal-entries.md) on both sides, so your books stay balanced without any manual work.

***

### Splitting shared expenses

For expenses shared across businesses - like rent, software, or insurance - you can split a single transaction across multiple entities by amount or percentage. Kick handles the intercompany entries automatically.

→ [Splits](/common-workflows/splits.md)

***

### Personal entity

Every workspace includes a **Personal** entity for connecting personal bank accounts and credit cards. Transactions in the Personal entity don't post to your business books - you review them and move any business expenses across manually.

→ [Personal to Business](/common-workflows/personal-to-business.md)


---

# 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/setting-up/multi-entity.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.