Intercompany Elimination is where ERP discipline either begins or breaks.
Intercompany Transaction Matching and Elimination looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Intercompany balances eliminated completely before group financials published; elimination proof available for auditors; intercompany reconciliation cycle time reduced.
The control flow a finance team actually needs.
Step 1
Intercompany Transaction Tagging With...
Step 2
Automated Matching Engine Comparing...
Step 3
Configurable Matching Tolerance Per...
Step 4
Mismatch Report Listing Each Unmatched...
Step 5
Workflow For Entities To Agree On...
The ERP surface involved.
Module
Intercompany Elimination
Actors
Group Accountant, Entities (multiple), Consolidation System
Tier
Tier 2
Finance area
Financial Close, Consolidation & Statutory Reporting
Region lens
US and UK finance teams
Publication date
April 1, 2026
Intercompany transaction tagging with counterparty entity ID on all relevant transactions; automated matching engine comparing receivable/payable and revenue/expense by counterparty and account; configurable matching tolerance per currency; mismatch report listing each unmatched pair with amounts in both functional currencies and group currency; workflow for entities to agree on intercompany adjustments with audit trail; auto-generation of elimination journal entries on match confirmation; elimination entries tagged as elimination-type and excluded from entity financials; consolidation blocked until all material intercompany pairs are matched or waived with documented reason.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Intercompany transaction tagging with counterparty entity ID on all relevant transactions | Given intercompany-tagged receivable/payable and revenue/expense balances across entities |
| Control 2 | automated matching engine comparing receivable/payable and revenue/expense by counterparty and account | when the consolidation system runs automated matching |
| Control 3 | configurable matching tolerance per currency | then matched pairs within tolerance are confirmed and elimination JEs are generated zeroing intercompany balances at group level |
| Control 4 | mismatch report listing each unmatched pair with amounts in both functional currencies and group currency | unmatched pairs appear on the mismatch report |
| Control 5 | workflow for entities to agree on intercompany adjustments with audit trail | consolidation is blocked until all material pairs are matched or waived with documented reason |
| Control 6 | auto-generation of elimination journal entries on match confirmation | Intercompany balances eliminated completely before group financials published; elimination proof available for auditors; intercompany reconciliation cycle time reduced. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Each entity posts intercompany revenue, expense, receivable, and payable transactions tagged with the counterparty entity ID. The consolidation system pulls all intercompany-tagged balances from each entity's trial balance and attempts automated matching of receivables to payables and revenues to expenses by counterparty pair and account mapping. Unmatched or out-of-balance intercompany pairs are flagged for Group Accountant resolution; entities are notified to investigate and correct or agree on an adjustment. Once all intercompany pairs match within tolerance, the system generates elimination journal entries that zero out intercompany balances at the group level. Consolidation proceeds only after all eliminations are applied. |
| Control rules | Intercompany transaction tagging with counterparty entity ID on all relevant transactions; automated matching engine comparing receivable/payable and revenue/expense by counterparty and account; configurable matching tolerance per currency; mismatch report listing each unmatched pair with amounts in both functional currencies and group currency; workflow for entities to agree on intercompany adjustments with audit trail; auto-generation of elimination journal entries on match confirmation; elimination entries tagged as elimination-type and excluded from entity financials; consolidation blocked until all material intercompany pairs are matched or waived with documented reason. |
| Acceptance proof | Given intercompany-tagged receivable/payable and revenue/expense balances across entities; when the consolidation system runs automated matching; then matched pairs within tolerance are confirmed and elimination JEs are generated zeroing intercompany balances at group level; unmatched pairs appear on the mismatch report; consolidation is blocked until all material pairs are matched or waived with documented reason; (negative) when consolidation is triggered with unresolved material intercompany mismatches then the system returns 409 UNRESOLVED_IC_MISMATCHES. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`intercompany_match` { id: string, entity_a_id: string, entity_b_id: string, period: string, receivable_minor: int64, payable_minor: int64, currency_code: char(3), status: enum, waiver_reason: string, external_id: string }; `elimination_journal_entry` { id: string, consolidation_run_id: string, type: enum(IC_ELIMINATION), external_id: string }; (reference, product may differ).API and events
`POST /v1/consolidation-runs/{id}/match-intercompany` -> 200 { matched: int, unmatched: int, eliminations_generated: int }; `GET /v1/ic-mismatches?consolidation_run_id`; `POST /v1/ic-mismatches/{id}/waive` { reason } -> 200; emits `consolidation.ic_matched` and `consolidation.elimination_generated` events; idempotent via `external_id`.State transitions
`UNMATCHED -> MATCHED -> ELIMINATION_POSTED`; alternate `UNMATCHED -> WAIVED`; guard: consolidation proceeds only when all pairs are MATCHED or WAIVED; WAIVED requires documented reason and Group Accountant role.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.