> ## Documentation Index
> Fetch the complete documentation index at: https://control-dev.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Review and correct intercompany eliminations

> Match intercompany postings into elimination groups, separate booking differences from FX differences, and correct booking differences without changing source ledgers.

Use elimination groups to match the two sides of each intercompany balance and transaction and confirm that they cancel in consolidation. Control links the elimination postings that belong together, measures what each group leaves after elimination, and splits that amount into a booking difference that you correct and an FX difference that belongs in the cumulative translation adjustment (CTA). You can post a correction from the same page without changing any entity's accounting system.

## Availability

| Attribute | Value |
| - | - |
| Availability | Enabled per workspace for groups with more than one entity. Ask Control support to enable elimination groups. |
| Navigation | When enabled, the sidebar shows **Intercompany** with **Overview**, **Eliminations**, and **Currencies**. |
| Roles | Every role can review. Every role except Viewer can link postings, approve groups, change the review threshold, and post corrections. Organization admins also turn **Automatic linking** on or off and set **Correction accounts**. |

## Before you begin

* Create the eliminations with [automated elimination rules or manual elimination entries](https://control-dev.mintlify.site/product-docs/consolidation/eliminations.md). Elimination groups link existing elimination postings; they do not create eliminations.
* [Map the intercompany local accounts](https://control-dev.mintlify.site/product-docs/configuration/account-mappings.md) to group accounts. Accounts without a group account mapping are outside the group statements and the CTA.
* [Select the CTA destination accounts](https://control-dev.mintlify.site/product-docs/configuration/cta-calculation.md#configure-the-destination-accounts).
* Wait for entity data to finish syncing. Amounts stay unavailable until reporting is current.

## How elimination groups work

**Industry concept:** In consolidation, an intercompany receivable cancels the matching payable, and intercompany revenue cancels the matching cost. An amount left after both sides are eliminated is a currency effect, a timing difference, or a sign that the entities booked different amounts.

**Control behavior:** An elimination group holds the elimination postings that belong to the same intercompany item, such as the eliminated loan receivable in Example Oy and the eliminated loan payable in Example AB. Linking does not change reported figures. It tells Control which postings should cancel, so Control can measure and explain what is left:

* **Consolidation difference** is what the group leaves after elimination, in the group currency. It equals **Booking difference** plus **FX difference**.
* **Booking difference** is a mismatch in the booked amounts. Control tests P\&L groups at each posting's booking-date rate and balance-sheet groups at the closing rate. This is the amount to correct.
* **FX difference** is the rest, caused by translating at consolidation rates. It goes to Elimination CTA and needs no correction.
* An elimination posting that is not in any group counts in full as booking difference.

Example (illustrative): Example Oy (EUR) records 10,000 EUR of intercompany revenue from Example AB (SEK). Example AB records the cost as 110,000 SEK, which was 10,000 EUR at the invoice-date rate of 11.00. The group report translates the cost at a consolidation rate of 11.20, or 9,821.43 EUR, so the group leaves a consolidation difference of 178.57 EUR. At booking-date rates the postings net to zero, so the whole 178.57 EUR is FX difference. Had Example AB booked 105,000 SEK, the booking difference would be 454.55 EUR.

**Customer decision:** You decide which entity's booking is wrong, and whether the fix belongs in Control, in the entity's accounting system, or both.

### Difference statuses

The **Consolidation difference** cell of each group shows a status icon. Hover over it for the label and Control's explanation.

| Status | Meaning | What to do |
| - | - | - |
| **Balanced** | The postings cancel exactly. | Nothing. |
| **Translation** | The postings net at the test rates, so the whole difference is FX difference. An investment eliminated against subsidiary equity, and one entity's self-cancelling bookings, are also translation. | Nothing to correct. The amount stays in Elimination CTA. |
| **Within tolerance** | The booking difference is at or below the review threshold. It stays a booking difference and is never moved to FX. | No correction is proposed. |
| **Difference** | The booking difference is above the review threshold. The explanation names a likely cause, such as amounts that differ or an entity that has not revalued a foreign-currency balance. | [Correct the booking difference](#correct-a-booking-difference). |
| **Timing** | A difference whose postings fall in different months, or whose linked posting is dated after the period end. | Verify the counterpart posting. No correction is proposed. |
| **Needs evidence** | Control cannot split the difference, for example because only one entity is represented or the group spans P\&L and balance-sheet postings. The whole net counts as booking difference. | Find the missing counterpart, or review each statement's postings separately. |
| **Unavailable** | An amount or exchange rate is missing, or the group includes changed, missing, or out-of-view postings. | See [Troubleshooting](#troubleshooting). |

## Review the Overview

Open the (Intercompany → Overview).

1. Set **As of** to the month you are reviewing. It defaults to the last full month.
2. Optionally choose **All**, **P\&L**, or **Balance sheet**, and narrow the entities.
3. Read **Elimination booking differences** for the amounts to correct and **Elimination FX differences** for the amounts that go to CTA.
4. Select a bar to open the groups and postings it sums. Select **Show all entities** to see counterparts in other entities, or **Open in Eliminations** to continue on the **Elimination groups** tab.

Overview figures are cumulative as of the selected month end: balance-sheet eliminations at their closing balances and every P\&L elimination to date.

By entity pair, the booking-difference chart reads from left to right:

1. One bar per entity for its unlinked eliminations, including groups that contain only that entity's postings.
2. **Group level · unlinked** for group-level eliminations, posted to **GROUP**, that are not in a group.
3. An **Unlinked eliminations** subtotal.
4. One bar per linked entity pair, such as **Example AB ↔ Example Oy**.
5. **Corrections pending sync**, when posted corrections have not reached reporting yet.
6. The total, **Elimination booking difference**, labeled **After sync** while corrections are pending.

**By account pair** and **By elimination group** show the same amounts by group account or by group. There, unlinked group-level eliminations appear as **Group-level eliminations**.

### Read the CTA card

With **As of date** selected, the CTA card builds the closing CTA on the selected date from these bars:

| Bar | Contains |
| - | - |
| ***Entity* currency translation** | Currency CTA from translating that entity's own balances. |
| **BS elimination booking difference** | Balance-sheet booking differences, including unlinked and group-level postings. The booking-difference chart breaks it down. |
| **BS elimination FX difference** | FX differences of balance-sheet groups. |
| **P\&L eliminations to date** | Every P\&L elimination through the date. Control carries it to equity, so CTA holds the opposite amount. |
| **P\&L eliminations not carried**, **Corrections pending sync**, **Not yet in stored CTA** | Shown only when not zero. A **Not yet in stored CTA** amount that remains after the next sync needs investigation. |

Select **Over time** to see stored CTA movements by **Month**, **Quarter**, or **Year**, with the **CTA balance** as a line. The **Derived and stored CTA** table below the card reconciles the Elimination CTA derived from the groups with the stored CTA. An **Unreconciled difference** is not automatically an FX difference. See [Currency translation adjustments](https://control-dev.mintlify.site/product-docs/configuration/cta-calculation.md) for how CTA is calculated.

## Review elimination groups

Open (Intercompany → Eliminations → Elimination groups).

1. Choose the period, statement, and entities. The period defaults to the last full month and can cover up to 36 months. Balance-sheet postings show closing balances through the period end; P\&L postings show activity in the selected months.
2. Check the **Automatic linking** line for the latest linking run.
3. Expand a group to see its postings with their **Local amount**, **Booking amount**, and **Consolidation amount**, and the group's **Consolidation difference**, **Booking difference**, and **FX difference**.
4. Double-click a group, or press Enter, to open its details: the diagnosis, any proposed correction, and the group actions.
5. When the group is right, select **Approve group**. Approval records your review and pins the postings so automatic linking does not move them. It posts nothing, and it no longer applies if the group changes.

### Create and change groups

| Method | How |
| - | - |
| Automatic linking | Runs after every sync that brings new or changed eliminations. It links postings that share a reference first, then uses AI for the rest when [AI features](https://control-dev.mintlify.site/product-docs/ai/processing-and-policy.md) are enabled. It never moves postings a user placed and never links group-level eliminations. Turning it on links the existing backlog. |
| Create a group | Tick two or more ungrouped postings, select **Group *N* postings**, optionally add a reason, and select **Create group**. |
| Edit a group | In group details, select **Edit group**, tick or untick postings, and select **Save changes**. |
| Move one posting | Drag the transaction onto another group, or open it and choose **Move to** a group or **Move to ungrouped**. **Undo move** reverses the last move. |
| Ungroup | In group details, select **Ungroup postings**, then **Ungroup**. The postings return to automatic linking. |

Postings you place in a group are pinned. A posting that automatic linking placed returns to ungrouped when its amount or account changes, so it can be linked again.

## Correct a booking difference

When a group's booking difference is above the review threshold, Control drafts one proposed correction and shows it under the group as **Correction ready to post**, or as **Correction suggested** when you must choose the entity or an account. Control does not propose corrections for **Timing** groups, for groups with a correction still waiting for sync, or for groups of group-level postings only. Proposals cover complete months: a difference that arises in the current month gets its proposal after the month ends.

1. Open the group and select **Correct** under **Proposed correction**. In the grid row, the same action is **Adjust**.
2. In **Book the correction in**, choose the entity whose booking is wrong. The amounts alone do not show which side is wrong, so check the underlying invoice or agreement.
3. Review the suggested journal. Change any **Account**, and choose the offset account if Control could not determine it. **Eliminated** shows which lines are removed in the group view.
4. Enter a **Reason**. It becomes the journal description.
5. Select **Post correction**.

> **Accounting behavior:** Posting saves a balanced journal, **Intercompany correction**, in the selected entity's ledger in Control, in that entity's currency, with you as the poster. Lines marked **Eliminated** are also eliminated in the group view. Control writes nothing to the entity's accounting system. The journal reaches the statements, the group, and the Overview after the next reporting sync; until then the group shows the difference after sync with a clock icon.

Control drafts the journal as follows:

* It is dated at the end of the month of the group's latest posting. If that month is [closed in Control](https://control-dev.mintlify.site/product-docs/integrations/closed-periods.md) for the entity, it is dated at the end of the reviewed period instead, so check **Dated** in the dialog before posting. A correction for a missing revaluation is dated at the end of the reviewed period and reverses the next day, when the entity's own revaluation takes over.
* The offset line uses the entity's account mapped to the group account an organization admin selected under **Correction accounts**: **FX gain/loss (revaluation differences)** or **Intercompany clearing (P\&L differences)**. Without one, Control suggests an account only when exactly one account name matches. For other balance-sheet differences, you choose the offset account.
* Control rejects a journal dated in a month [closed in Control](https://control-dev.mintlify.site/product-docs/integrations/closed-periods.md), an eliminated line on an equity account, and a non-eliminated line on an account covered by an automated elimination rule.

Instead of posting the proposal as drafted, you can:

* select **Dismiss** to set it aside until the group changes. The dismissed correction stays listed under the group and can still be posted.
* select **Edit in journal editor** to change the journal, then **Preview correction** and **Post journal**. Use **Draft journal** under **Correction journals** for a correction that Control did not propose.

To reverse a posted correction, select **Undo** on its journal row, or **Undo journal** in group details. You cannot undo a correction dated in a closed month, and you must undo a group's corrections before you ungroup it.

> [!WARNING]
>
> A correction changes the entity's figures in Control only. If the same fix is also booked in the entity's accounting
> system, both reach the statements after sync. Undo the Control correction when the source-system fix arrives.

## Set the review threshold

On the Overview, select **Threshold** to see or change the workspace's review threshold, in the group currency. Until someone sets it, the threshold is 100.

A booking difference at or below the threshold is **Within tolerance**: it stays a booking difference, is never moved to FX, and gets no proposed correction. Above the threshold, Control proposes a correction. A new threshold applies to every period and redrafts the proposals.

To test another value for one group without saving it, change **Review threshold** under **Difference diagnosis** in the group's details.

## Understand as-of dates and timing

* A posting dated after the end of the Overview's as-of date or the selected period is not in the books on that date. Control leaves it out of the group's difference and shows it as **Dated after the period end: not in the books then**.
* If only one entity's side remains, its whole net is booking difference, shown as **Timing** when it is above the threshold. On the Overview it counts in that entity's unlinked bar. Control proposes no correction; review the group as of a later month once the counterpart is booked.
* In a month that has not ended, balance-sheet groups are tested at the latest available rate because the month-end rate does not exist yet.

## Verify the result

1. After the next reporting sync, open the group again. The clock icon is gone, the correction's lines appear in the group, and the journal status no longer reads pending sync.
2. On the Overview, confirm that **Corrections pending sync** is gone and that **Elimination booking difference** fell by the corrected amount.
3. Open the [P\&L](https://control-dev.mintlify.site/product-docs/reporting/pnl.md) or [balance sheet](https://control-dev.mintlify.site/product-docs/reporting/balance-sheet.md) for the whole group and the same period. In the entity picker, turn on **Eliminations pivot** to show entity values, eliminations, and the group total side by side.
4. Confirm the correction in the corrected entity's values and its eliminated lines in the eliminations column. Then compare the combined balance of your Currency CTA and Elimination CTA accounts with the closing CTA on the CTA card.

## Troubleshooting

| Problem | What to check |
| - | - |
| **Intercompany** is missing from the sidebar | Elimination groups are not enabled for the workspace, or the workspace has one entity. Ask Control support. |
| A group shows **Incomplete group** | Some of its postings are outside the selected period or entities. Widen the selection. |
| A group shows **Needs review** | A posting's amount or account changed, or the posting left reporting. Inspect it, then select **Accept current evidence** or **Edit group**. |
| A difference you expected to be FX shows as **Difference** | Hover over **Booking difference** to see the test basis. If an entity has not revalued a foreign-currency balance, the explanation names it and the proposed correction reverses the next day. A difference within the threshold stays a booking difference by design. |
| A posting is in the wrong group | Drag it onto the right group, or open it and use **Move to**. Moved postings are pinned. |
| A group has only one entity's side | On the Overview, open that entity's unlinked bar and select **Show all entities** to find the counterpart, then add it with **Edit group**. If the counterpart is dated later, the difference is timing. |
| A posting dated after the period end leaves a difference | Expected until that date. Review the group as of the month in which the counterpart is booked. |
| No correction is proposed | The group is **Within tolerance** or **Timing**, a correction is waiting for sync, the difference arose in the current month, or the group holds only group-level postings. |
| The proposal needs an entity or offset account | Choose them in the correction dialog, or ask an organization admin to set **Correction accounts**. |
| Posting fails because figures or exchange rates changed | Select **Refresh** and review the redrafted proposal. |
| Amounts are unavailable or a scope is too large | Wait until reporting is current. A view supports up to 5,000 processed elimination postings; narrow the period or entities above that. |

## Use an AI client

A [connected AI client](https://control-dev.mintlify.site/product-docs/ai/mcp-server.md) can read elimination groups:

* `get_saved_elimination_groups` returns the groups that touch a period, with each posting's status and the groups' balance-sheet and P\&L effects.
* `get_elimination_review` returns the entity and account elimination review with closing balances before CTA.
* `control_api_get` can also read the booking and FX difference summary, each group's diagnosis, and the proposed corrections.

Ask for a read-only review first, for example:

> For Example Group, review the elimination groups for September 2026. List each group whose booking difference is
> above the review threshold, with its entities, accounts, booking difference, FX difference, diagnosis, and proposed
> correction. Do not post anything.

Review and post corrections in Control, where the dialog shows the drafted journal and requires a reason. In a session with write access, a client can also create a group or post a proposed correction through `control_api_request`. Confirm each write yourself: the change is made as you, under your role. Inside a Control agent run, `propose_manual_eliminations` creates a proposal only; nothing is written until an organization admin approves it.

## Next steps

| If you want to… | Continue to… |
| - | - |
| Create or change the eliminations to link | [Configure eliminations](https://control-dev.mintlify.site/product-docs/consolidation/eliminations.md) |
| Understand Currency and Elimination CTA | [Currency translation adjustments](https://control-dev.mintlify.site/product-docs/configuration/cta-calculation.md) |
| Investigate a statement value | [Drill down into financial statements](https://control-dev.mintlify.site/product-docs/reporting/drill-down.md) |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.