> 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/intercompany.md).
# Intercompany
Review and resolve matched and unmatched intercompany activity across a consolidation group.
The Intercompany page brings intercompany activity for a consolidation group into one review table. Use it to inspect each source entry, confirm its match, and resolve unmatched activity.
***
### Open Intercompany
1. Open **Workflows** → **Accounting**.
2. Select **Intercompany**.
3. Select the date range you want to review.
**Intercompany** appears only for clients on Advanced or Enterprise. You also need a consolidation group before you can use the page. If the workspace doesn't have one, Kick shows **Create a consolidation group**. Click **Go to Ownership** and create the group first.
→ [Set Up a Consolidation Group](/accountants/bookkeeping-workflows/consolidation/set-up-a-consolidation-group.md#create-a-consolidation-group)
***
### Review intercompany activity
Each row shows:
* **Date**
* **Entity**
* **Source**
* **Reference**
* **General ledger**
* **Description**
* **Memo**
* **Match**
* **Status**
* **Amount**
**Date** stays pinned on the left, and **Status** and **Amount** stay pinned on the right. The Status column uses an icon with a **Matched** or **Unmatched** tooltip. The footer shows **Entries** with the number of rows remaining after filters are applied.
Select a transaction in the **Source** column to open it in [Transactions](/accountants/bookkeeping-workflows/transactions.md). When a row has exactly one journal entry, select its **Reference** to open the [journal entry editor](/accountants/close-workflows/journal-entries.md).
***
### Understand match statuses
Intercompany activity has one of two statuses:
* **Matched** means Kick found the related activity on the other side of the entity pair.
* **Unmatched** means the row still needs a match or a corresponding journal entry.
An [in-transit transfer](/accountants/bookkeeping-workflows/transfers.md#transfer-types) appears as **Matched** and shows the counterparty entity in the **Match** column. It is informational and does not require another action.
***
### Resolve unmatched activity
The action available in the **Match** column depends on the source:
* For an unmatched transaction with a known source, select the empty **Match** cell to find the related transaction.
* For another unmatched source, select the empty **Match** cell to create the corresponding journal entry for the counterparty entity.
* For a matched transfer, review or open the standard transfer match.
* For another matched row, select the match preview to open the related journal entry.
Matched transfers dated in a locked period are read-only.
Use the [Elimination Ledger](/accountants/bookkeeping-workflows/consolidation/reports-and-eliminations.md#use-the-elimination-ledger) when you need an adjustment that affects only the consolidated result.
***
### Filter the page
Use search to find rows by their visible details.
Use the exposed **Entity** control to filter the report by one or more businesses.
Use **Add filter** for:
* **Status**
* **General ledger**
* **Source**
Available sources include **Transactions**, **Manual journals**, **Opening balances**, **Loans**, **Bills**, **Invoices**, and **Recognition schedules**. Active filters appear above the table and can be removed individually or cleared together.
Use column settings to show or hide columns, and drag column edges to resize them. Kick saves the view for your user.
***
### Next step
If the consolidated result needs a group-level adjustment after you resolve the source activity, create a manual eliminating entry.
→ [Manual Eliminating Entries](/accountants/bookkeeping-workflows/consolidation/manual-eliminating-entries.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/intercompany.md?ask=&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.
