General Ledger / Intercompany is where ERP discipline either begins or breaks.
Intercompany Transaction Posting 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 net to zero in the consolidated view, the elimination audit trail traces back to each originating transaction, and no intercompany revenue or expense inflates consolidated results.
The control flow a finance team actually needs.
Step 1
Auto-Generate Both-Entity Journal Legs...
Step 2
Atomic Dual-Entity Post
Step 3
Intercompany Receivable And Payable...
Step 4
Consolidation Elimination Pass Matches...
Step 5
Unmatched Intercompany Alerts Before...
The ERP surface involved.
Module
General Ledger / Intercompany
Actors
Accountant (Entity A), Accountant (Entity B), Consolidation System, GL System
Tier
Tier 2
Finance area
Financial Accounting & General Ledger
Region lens
US and UK finance teams
Publication date
March 7, 2026
auto-generate both-entity journal legs from a single intercompany transaction; atomic dual-entity post (both or neither); intercompany receivable and payable accounts designated per entity pair; consolidation elimination pass matches and nets intercompany balances; unmatched intercompany alerts before consolidation close; elimination journal auto-created with audit reference to originating transactions; multi-currency intercompany with FX conversion on each entity leg; intercompany transactions tagged for regulatory disclosure
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 | auto-generate both-entity journal legs from a single intercompany transaction | Given two entities A and B within the same org |
| Control 2 | atomic dual-entity post (both or neither | when an intercompany transaction is recorded |
| Control 3 | intercompany receivable and payable accounts designated per entity pair | then both entity legs are posted atomically (both or neither), Entity A shows IC receivable + revenue, Entity B shows IC payable + expense, and the consolidation elimination nets both to zero |
| Control 4 | consolidation elimination pass matches and nets intercompany balances | |
| Control 5 | unmatched intercompany alerts before consolidation close | Intercompany balances net to zero in the consolidated view, the elimination audit trail traces back to each originating transaction, and no intercompany revenue or expense inflates consolidated results. |
| Control 6 | elimination journal auto-created with audit reference to originating transactions | Intercompany balances net to zero in the consolidated view, the elimination audit trail traces back to each originating transaction, and no intercompany revenue or expense inflates consolidated results. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Entity A records a sale to Entity B (both within the same organization). The system auto-generates a paired intercompany journal: Entity A books a revenue credit and an intercompany receivable debit; Entity B books an expense debit and an intercompany payable credit. Both legs must be posted atomically or neither posts. During consolidation, the system identifies intercompany pairs by matching intercompany account codes and eliminates both the receivable/payable and the revenue/expense to prevent double-counting in the consolidated financial statements. Any unmatched intercompany balance triggers a reconciliation alert before consolidation is finalized. |
| Control rules | auto-generate both-entity journal legs from a single intercompany transaction; atomic dual-entity post (both or neither); intercompany receivable and payable accounts designated per entity pair; consolidation elimination pass matches and nets intercompany balances; unmatched intercompany alerts before consolidation close; elimination journal auto-created with audit reference to originating transactions; multi-currency intercompany with FX conversion on each entity leg; intercompany transactions tagged for regulatory disclosure |
| Acceptance proof | |
| 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_transactions` { id: string, external_id: string, org_id: string, payer_entity_id: string, payee_entity_id: string, amount_minor: int64, currency_code: char(3), payer_functional_amount_minor: int64, payee_functional_amount_minor: int64, status: enum(DRAFT,POSTED,ELIMINATED) }; `intercompany_journal_legs` { id: string, transaction_id: string, entity_id: string, je_id: string, leg_type: enum(RECEIVABLE,PAYABLE,REVENUE,EXPENSE) }; (reference, product may differ).API and events
`POST /v1/intercompany-transactions` { org_id, payer_entity_id, payee_entity_id, amount_minor, currency_code, description, external_id } -> 201 { id, payer_je_id, payee_je_id, status: POSTED }; `POST /v1/consolidations/{run_id}/eliminate-intercompany`; emits `gl.intercompany.posted` and `gl.intercompany.eliminated` events; idempotent via `external_id`.State transitions
`DRAFT -> POSTED`; `POSTED -> ELIMINATED` during consolidation run; guard: partial post (one entity succeeds, other fails) is rolled back atomically; ELIMINATED entries are immutable.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.