> 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/bookkeeping-workflows/consolidation/set-up-a-consolidation-group.md).

# Set Up a Consolidation Group

Create a consolidation group and choose the ledger for each entity.

After mapping the ownership structure, create a consolidation group to choose the parent, subsidiaries, and ledger each entity contributes to consolidated reporting.

***

### Before you create a group

To create a consolidation group, you need:

* A client on Advanced or Enterprise
* At least two business entities in the workspace
* An active Equity relationship from the parent to each subsidiary
* An [accounting ledger](/accountants/setting-up/ledgers.md) for every entity in the group

Wholly owned subsidiaries can be included in consolidated totals. A partially owned subsidiary can appear in the group but remains **Not consolidated**.

→ [Use the Ownership Canvas](/accountants/bookkeeping-workflows/consolidation/ownership-canvas.md)

***

### Create a consolidation group

1. On the Ownership canvas, click **Consolidate** in the toolbar.
2. Select the entities to include.
3. Set one entity as **Parent** and at least one entity as **Subsidiary**.
4. Click **Continue**.
5. Select the ledger for each entity.
6. Click **Consolidate**.

The full-screen flow is titled **Add consolidation**:

* **Select parent and subsidiary entities**. Step 1 of 2, with Entity, Entity type, Ownership, Members, and Role columns.
* **Confirm ledger basis to consolidate**. Step 2 of 2, which adds a Ledger column with a selection for each entity.

To start with a parent and its wholly owned subsidiaries already selected, select the parent entity on the canvas and click **Consolidate** in the command bar.

{% hint style="info" %}
Consolidation supports a flat parent and subsidiary structure. A subsidiary owned by another subsidiary, an entity owned by a different parent, or an entity already in another consolidation group cannot be included.
{% endhint %}

***

### Find the consolidation group

After creation, the group appears in two places:

* On the canvas, the group pill is labeled **\[Parent entity] (Consolidated)**.
* In the Entities area of the left navigation, the row is labeled **\[Parent entity] (Consolidation Group)**.

Expand the navigation row to open **Profit & Loss**, **Balance Sheet**, or **All reports**. Group members remain in the regular entity list.

***

### Update a consolidation group

Select the consolidation group on the canvas to review its settings:

* **Details**. The group name and parent entity.
* **Ledger basis**. The ledger selected for each group member.
* **Reporting**. Links to the **Elimination Ledger** and the consolidated [Profit & Loss](/accountants/reports/profit-and-loss.md) and [Balance Sheet](/accountants/reports/balance-sheet.md).

Use **View Reporting** in the command bar to open all reports for the group.

***

### Unconsolidate a group

1. Select the consolidation group or its parent entity.
2. Click **Unconsolidate**.
3. Confirm **Unconsolidate**.

Unconsolidating dissolves the group. The entities and their relationships remain on the [Ownership canvas](/accountants/bookkeeping-workflows/consolidation/ownership-canvas.md), so you can create another group later.

***

### Next step

After creating the group, review its consolidated financial statements and eliminations.

→ [Review Consolidated Reports and Eliminations](/accountants/bookkeeping-workflows/consolidation/reports-and-eliminations.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/accountants/bookkeeping-workflows/consolidation/set-up-a-consolidation-group.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.