> 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.md).

# Consolidation

Set up a consolidation group and review consolidated financial statements across related entities.

Consolidation brings selected entity ledgers into one reporting view. Kick automatically eliminates matched intercompany activity, then shows each entity alongside the post-elimination consolidated result.

If you need to manage separate entities without consolidating their financial statements, start with [Multi-Entity](/accountants/setting-up/multi-entity.md).

***

### Before you start

Consolidation is available for clients on Advanced or Enterprise. Plus doesn't include it. On other plans, **Ownership** and **Intercompany** don't appear in the navigation, and Reporting shows only individual entity reports.

→ [Plan comparison guide](/accountants/reference/plan-comparison-guide.md)

To create a consolidation group, you need:

* At least [two business entities](/accountants/setting-up/multi-entity/adding-and-removing-entities.md) in the same workspace
* An Equity relationship from the parent to at least one subsidiary
* An [accounting ledger](/accountants/setting-up/ledgers.md) for each entity in the group

If the client is on Advanced or Enterprise and you don't see **Ownership**, contact Kick support.

***

### Follow the consolidation workflow

1. [Map the ownership structure](/accountants/bookkeeping-workflows/consolidation/ownership-canvas.md) and other relationships between entities.
2. [Create a consolidation group](/accountants/bookkeeping-workflows/consolidation/set-up-a-consolidation-group.md) and select the ledger for each entity.
3. [Review consolidated reports and eliminations](/accountants/bookkeeping-workflows/consolidation/reports-and-eliminations.md) from Reporting.
4. [Review and resolve intercompany activity](/accountants/bookkeeping-workflows/consolidation/intercompany.md) with **Matched** and **Unmatched** statuses.
5. [Create a manual eliminating entry](/accountants/bookkeeping-workflows/consolidation/manual-eliminating-entries.md) when an adjustment belongs only in the consolidated result.

***

### Consolidation in Kick

A consolidation group is a parent entity and its selected subsidiaries, with a ledger selected for each member. You work with it in these places:

* **Ownership**. The canvas of business entities, owners, and their relationships, where you create the consolidation group.
* **Ledger basis**. The ledger each group member contributes to the consolidated reports.
* **Reporting**. The report catalog for individual entities and the consolidation group.
* **Eliminations**. The column on consolidated reports that removes matched intercompany activity and applies manual eliminating entries.
* **Elimination Ledger**. The detailed view of **Auto** and **Manual** eliminations, where you create group-level eliminating entries that affect consolidated reports only.
* **Intercompany**. The review table for matched and unmatched activity across the consolidation group.


---

# 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.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.