Eliminations are where structural problems become visible
Intercompany eliminations look like the most mechanical step in consolidation. Equal and opposite balances cancel, and the group view emerges. In groups with PRC operating entities, a Hong Kong holding layer, and an Australian parent, that is rarely how it works in practice.
Every elimination journal sits on top of three assumptions:
- Both sides have recorded the same transaction.
- Both sides have agreed on amount, date, currency, and counterparty.
- Both sides are presenting the balance under compatible accounting policies.
Cross-border groups break at least one of those assumptions every cycle. The elimination journal is where the breakage shows up.
The four most common breakage points
1. Counterparty mismatch
The PRC subsidiary has booked an intercompany payable to "HK Holdings Limited". The HK entity has the receivable booked against "Shanghai Trading Co. Ltd". The parent's mapping table treats them as a matched pair.
But during the year, an internal restructuring transferred the loan to a different HK SPV. Only one side updated the counterparty. The pair no longer matches at the entity level, and the elimination journal carries a difference that isn't a real difference.
The fix is a single, group-owned counterparty register, refreshed every period, with effective dates on every change.
If you are unsure how this intercompany elimination friction is currently impacting your group close, you can run a 2-minute diagnostic via our Close Clash Calculator to see where the evidence path is breaking down.
2. Timing differences
The PRC entity records an intercompany sale at fapiao issuance. The HK entity records the corresponding purchase at goods receipt. In a single month-end with international shipping, those events fall on different days, and frequently in different periods.
This isn't an error — it is the system working correctly at each entity level. But the group view needs a documented timing-difference policy: which side defines the period for the consolidated transaction, and where the in-transit balance lives until it resolves.
3. Currency and FX revaluation
A loan from the AU parent to a PRC subsidiary in CNY revalues every period under AASB 121 / IAS 21 on the parent side. The PRC subsidiary records it in CNY (its functional currency) without revaluation. At elimination, the amounts match in CNY, but the FX gain or loss sits only on one side.
The fix is to elimination-route the underlying loan and the FX revaluation as separate journal lines, both with documented policy references.
4. Standard differences
Lease accounting under CAS 21 (revised) is closely aligned with AASB 16 / IFRS 16 in principle, but there are timing and measurement differences in practice. Revenue under CAS 14 versus AASB 15 can produce different recognition dates for intercompany services and management charges. Without a translation step before elimination, the entries cancel arithmetically while still representing different economic events.
Designing eliminations that auditors can rely on
The structure that works:
Step 1 — Maintain an intercompany subledger at every entity
Each entity should keep an intercompany subledger separate from its main AR / AP, with counterparty, currency, transaction type (loan, trade, service, dividend, capital), and source document reference. This is the artefact every other step depends on.
Step 2 — Run a matching cycle before group close
A pre-close matching cycle, typically run two to five business days before the group cut, surfaces unmatched balances while there is still time to resolve them at source. The output is a matching report with three columns: matched, matched with timing difference, and unmatched.
Step 3 — Translate before you eliminate
Apply standard differences (CAS to AASB / IFRS) and FX policy at the entity level before the elimination journal is composed. Otherwise the elimination becomes a place where adjustments are hidden, and audit traceability is lost.
Step 4 — Post elimination journals as named, reasoned entries
Each elimination journal should carry: the entities involved, the transaction type, the matched amount, any timing or FX residual, and a policy reference. "Eliminate intercompany" is not a journal narration that survives audit sampling.
Step 5 — Carry unresolved differences forward, visibly
Open intercompany differences at period end go into a continuous log with owner and target resolution date. They do not silently roll into FX gain/loss or "other" adjustments. This is what allows the auditor to see the control environment operating across periods.
What "good" looks like at audit
When a group's intercompany discipline is working, the auditor's review of eliminations is short:
- A counterparty register with version control
- A matching report with a residuals analysis
- Translation entries booked separately from elimination entries
- An open-items log with movement
- A continuous reconciliation between gross intercompany and the elimination journal
When those artefacts are not present, the audit reverts to substantive testing of every material intercompany balance — and the cost shows up in fees, in management hours, and in late-cycle restatements.