# Multi-Entity

Kick is built for clients with multiple businesses, holding companies, or any structure that requires separate books under one workspace. Each entity gets its own chart of accounts, financial statements, and transaction history — while shared tools like rules, categories, and the transactions feed work across all of them.

***

### How entities work in Kick

A workspace contains one or more entities. The first entity is created when you add a client. Additional entities can be added at any time from the Clients tab or from within the client's workspace.

Each entity has its own:

* [Chart of Accounts](/setting-up/chart-of-accounts.md)
* Financial statements (Balance Sheet, P\&L, Trial Balance, General Ledger, etc.)
* Integrations
* Documents
* Tasks
* Transactions

These operate independently — but Kick gives you tools to work across entities without switching between them.

→ [Adding & removing entities](/setting-up/multi-entity/adding-and-removing-entities.md)

***

### Consolidated transactions feed

The Transactions tab shows transactions for all entities in a single feed. This is useful when entities share similar categorization — you can review and categorize across the entire workspace without switching context.

To focus on a single entity, filter by entity in the top right.

{% hint style="info" %}
**Tip:** The consolidated feed is especially helpful for reviewing intercompany activity. Matched Transfers between entities are clearly surfaced, making it easier to confirm both sides are categorized correctly
{% endhint %}

→ [Transactions](/bookkeeping-workflows/transactions.md)

***

### Intercompany journal entry automation

When you move a transaction from one entity to another — or split a transaction across entities — Kick automatically generates the intercompany payable and receivable journal entries on both sides.

This means you don't need to manually create offsetting entries. The expense is booked to the correct entity, and the intercompany balances on each entity's Balance Sheet stay in sync.

This applies to:

* **Moving transactions between entities** — Change the entity on a transaction from the Transactions tab. The expense posts to the destination entity, and intercompany entries are created automatically.
* **Cross-entity splits** — [Split](/bookkeeping-workflows/splits.md) a shared expense (rent, software, insurance) across multiple entities by amount or percentage. Each entity's portion is booked with the correct intercompany entries.
* **Matched transfers between entities** — when you move funds from one entity to another, Kick will idenitfy it as an intercompany transfer and generate the appropriate journal entries.

***

### Multi-entity rules

Rules can apply across multiple entities, so you don't need to recreate the same rule for each one. This includes:

* **Transaction Rules** that categorize, assign counterparties, or set classes across entities
* **Split Rules** that allocate shared expenses across entities automatically
* **Transfer Rules** that match intercompany transfers

→ [Rules](/bookkeeping-workflows/rules.md)

***

### Multi-entity Chart of Accounts

All entities in a workspace share a single Chart of Accounts view. You can see which accounts are shared across entities and which are unique to a specific entity. Custom accounts can be created and scoped as needed.

→ [Chart of Accounts](/setting-up/chart-of-accounts.md)

***

### The Personal entity

Every workspace includes a Personal entity where clients can connect their personal bank accounts and credit cards. Transactions in the Personal entity do not post to the General Ledger — they sit on the Transactions tab for review.

When a personal transaction has a business purpose, move it to the appropriate business entity. The expense posts to that entity's books, and the other side is recorded as a contribution.

The Personal entity can be disabled if not needed.

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


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kick.co/setting-up/multi-entity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.