> ## 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.
# Configure eliminations
> Create automated rules and manual entries, then verify their effect in consolidated reporting.
export const ControlAppLink = ({path, breadcrumb, children}) => {
const link =
{children}
;
return breadcrumb ? {link} : link;
};
Use eliminations to remove intragroup activity or post a consolidation-only adjustment without changing an entity's source-system transactions.
## Choose the right method
| Method | Use it for | Scope and timing |
| ------------------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------------- |
| **Automated elimination rule** | Recurring activity that can be identified by an entity or group account | Applies from a required start date until an optional end date |
| **Manual elimination entry** | A one-time elimination, reclassification, or consolidation adjustment | Applies on the entry date you select |
## Before you begin
* Use a multi-entity workspace and wait for the relevant entity data to finish syncing.
* [Map the affected local accounts](/product-docs/configuration/account-mappings) to the intended group accounts.
* Confirm the reporting period, both sides of the intragroup activity, and the expected group-level effect.
* If the entities use different functional currencies, confirm the group currency and applicable translation configuration.
## Create an automated elimination rule
Open Automated Elimination Rules.
1. Add a row to the rules grid.
2. In **Entity**, select an entity to target one of its local accounts, or select **GROUP** to target a group account.
3. In **Account**, select the account whose activity should be eliminated.
4. Set the **Start Date**.
5. Set an **End Date** when the rule should stop, or leave it empty for an open-ended rule.
6. Save the row.
The end date must be later than the start date. Review existing rules before adding another date range for the same account.
> **Accounting behavior:** A saved rule creates automatic elimination activity for transactions in its configured account and date scope. It does not edit or delete the original source transactions.
## Create a manual elimination entry
Open Consolidation Adjustments / Manual Elimination Entries.
1. Add a row to the adjustments grid.
2. Set the **Date** that determines the entry's reporting period.
3. In **Entity**, select an entity for a local-account entry, or select **GROUP** for a group-level entry.
4. Select the matching **Account**.
5. Optionally select a **Dimension** and **Dimension Item**.
6. Enter a non-zero signed **Value** and a description that explains the purpose and supporting reference.
7. Save the row.
The selected entity controls the account, dimension, and currency scope:
| Entity choice | Available fields | Value currency | Mapping requirement |
| ----------------- | ------------------------------------------------------------- | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A specific entity | That entity's local accounts, dimensions, and dimension items | The entity's functional currency | The local account must map to a group account. Map a selected local dimension item to a group dimension item when the entry must appear in that group-dimension scope. |
| **GROUP** | Group accounts, dimensions, and dimension items | The group accounting currency | No local mapping is required because the entry already uses the group structure. |
Leave **Dimension** and **Dimension Item** empty for an undimensioned entry. For a dimensioned entry, choose the dimension first and then an item from that dimension.
Control adds **Value** to the selected account's statement value with the sign entered: a positive value increases the numeric result and a negative value decreases it. Check the current report signs before creating the offset; do not infer the required sign from the account name alone.
### Balanced group-currency example
Assume a EUR group report shows `+1,000` in **Intercompany revenue** and `-1,000` in **Intercompany expense** for counterparty Entity B. Enter these two rows on the same date:
| Entity | Account | Dimension | Dimension Item | Value |
| --------- | -------------------- | ------------ | -------------- | -----------: |
| **GROUP** | Intercompany revenue | Counterparty | Entity B | `-1,000 EUR` |
| **GROUP** | Intercompany expense | Counterparty | Entity B | `+1,000 EUR` |
The two values sum to zero and reduce both scoped report values to zero. If the current report uses different signs, reverse the example signs. For any balanced adjustment, create a separate row for each affected account and verify the rows together.
A manual entry changes consolidated reporting only; it does not post back to an entity's accounting system.
Automatic income-statement eliminations create a calculated equity effect for retained earnings. Manual
income-statement eliminations do not. Add the required manual balance-sheet entry when your adjustment must also
affect retained earnings. See [CTA
calculation](/product-docs/configuration/cta-calculation#how-income-statement-eliminations-affect-cta).
### Retained-earnings offset example
Assume you eliminate mismatched intercompany activity between two entities with a manual entry in Consolidation Adjustments / Manual Elimination Entries: Entity A's booked intercompany revenue and Entity B's booked intercompany expense.
| Entity | Account | Dimension | Dimension Item | Value |
| ------------ | -------------------- | --------- | -------------- | ------------: |
| **Entity A** | Intercompany revenue | — | — | `-9,500 EUR` |
| **Entity B** | Intercompany expense | — | — | `+10,000 EUR` |
Together these rows increase group profit by `500 EUR` (`9,500 EUR` less revenue, offset by `10,000 EUR` less expense), but Control does not move that difference into retained earnings on its own. Add a third row on the same date so the balance sheet keeps balancing:
| Entity | Account | Dimension | Dimension Item | Value |
| --------- | ------------------------------------------------------------------------ | --------- | -------------- | ---------: |
| **GROUP** | Retained earnings (or your group's designated retained-earnings account) | — | — | `+500 EUR` |
Check your current report signs before entering the value — do not assume the sign from this example without confirming it against your own balance sheet.
## Verify the result
1. Open the relevant P\&L or balance sheet with a consolidated group scope and the intended period.
2. Compare the result before and after eliminations by using the transaction-category filter.
3. Drill into the affected row and review the elimination transactions separately from source and CTA transactions.
4. Confirm that both the account effect and the final group total match the expected adjustment.
5. For foreign-currency entities, review **Elimination CTA** separately from the elimination entries.
A non-zero Elimination CTA can reflect currency translation, timing differences, mismatched amounts, or incomplete elimination scope. See [Cumulative translation adjustment](/product-docs/configuration/cta-calculation#interpret-elimination-cta-carefully) before treating the residual as an error.
## Troubleshooting
| Problem | What to check |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Eliminations is not available** | Confirm that the workspace has more than one entity and that your role has write access for configuration. |
| **The account is not selectable** | Select the entity first. Entity rows expose that entity's local accounts; **GROUP** exposes group accounts. |
| **A rule removes external activity** | Narrow the account scope or stop the rule with an end date. Do not use a mixed external/intercompany account unless the full scoped activity should be eliminated. |
| **The expected period is unchanged** | Check the rule start/end dates or the manual entry date, then confirm the report period and wait for active processing to complete. |
| **The adjustment is one-sided or has the wrong sign** | Review all manual rows for the adjustment and compare their signed values with the intended debit and credit effect. |
| **Elimination CTA is unexpectedly large** | Compare both entity sides, accounting months, translation treatment, and whether the rule included non-intercompany activity. |
## Next steps
| If you want to… | Continue to… |
| --------------------------------------- | -------------------------------------------------------------------------------- |
| Review the full consolidation workflow | [Consolidate a group](/product-docs/consolidation/consolidate-a-group) |
| Understand currency and elimination CTA | [Cumulative translation adjustment](/product-docs/configuration/cta-calculation) |
| Investigate statement values | [Drill down into financial statements](/product-docs/reporting/drill-down) |