You’re sitting in a consolidation review. Someone points to the intercompany receivables line. “Why isn’t this zero?” The room goes quiet. The FCCS specialist checks metadata. The accountant checks the trial balance. Neither sees the full picture.

This is where intercompany eliminations break. Not because the accounting is hard — you can’t owe money to yourself. But because the system mechanics, the metadata dependencies, and the FX complexity sit in different places. Accountants know the standard. FCCS specialists know the configuration. The gap between them is where troubleshooting dies.

Let’s close that gap.

TL;DR

The accounting requirement: IFRS 10.B86 and ASC 810-10-45-1 require elimination of all intragroup transactions. You can’t owe money to yourself.

The FCCS mechanics: Elimination happens automatically when 7 conditions are met: account flagged as intercompany, valid Plug account, valid ICP partner, consolidation % > 0%, common parent exists, partner is sibling/descendant, method = Subsidiary.

The FX complexity: Intercompany balances eliminate, but FX gains/losses on non-functional currency balances may survive. Under US GAAP, qualifying long-term loans can defer FX to CTA (ASC 830-20-35-3).

The common traps:

• Rate type mismatches create Plug differences
• FX accounts should never be flagged as Is Intercompany
• Elimination occurs at first common parent, not at each parent level
• Missing documentation kills CTA treatment for long-term loans

The Accounting Problem

IFRS 10.B86 and ASC 810-10-45-1 state the requirement:

Intra-group assets and liabilities, equity, income, expenses and cash flows relating to transactions between entities of the group shall be eliminated.

Translation: You can’t sell to yourself. You can’t owe money to yourself. From the group’s perspective, money moving between subsidiaries isn’t revenue — it’s just moving between pockets.

But here’s what the standard doesn’t tell you: What happens when the two entities use different currencies? What if the intercompany balance is denominated in a third currency? What survives consolidation and what doesn’t?

That’s where the mechanics matter. And where FX meets intercompany, things get interesting.

Intercompany balances eliminate in consolidation, but FX gains and losses on non-functional currency loans may survive as real economic exposure.

The Logic Flow (The Accountant’s View)

Same Currency: The Simple Case

Let’s start with the T-account view for a straightforward case. This is what the accountant needs to see to confirm the requirement is met.

Scenario: Parent Co (USD) owns Entity A (USD) and Entity B (USD). Entity A sells $100 worth of inventory to Entity B on credit.

Before Consolidation:

The Elimination:

Clean elimination. Both sides match. Contribution shows zero for all intercompany balances. That’s the happy path.

But here’s the problem: Most global groups don’t have the luxury of same-currency transactions.

Cross-Currency: The Real World

Scenario: Parent Co (USD, parent currency) owns Entity A (USD functional currency) and EuroCo (EUR functional currency). Entity A loans $100,000 USD to EuroCo. Parent Co consolidates in USD.

Here’s where it gets tricky: The loan is denominated in USD. Entity A records it in USD (its functional currency). EuroCo records it in EUR (its functional currency). They’re both right — but they won’t match.

Step 1: What Each Entity Records

EuroCo’s loan payable dropped from €90,909 to €80,000 because the USD strengthened against EUR. The $100,000 USD principal is fixed — but in EUR terms, EuroCo owes less.

Step 2: What Gets Eliminated

Entity A’s loan receivable: $100,000 USD (no change, functional currency) EuroCo’s loan payable: $100,000 USD when translated to parent currency

Both translate to $100,000 at the parent level. The elimination works:

But look at what’s left behind:

What Survives Consolidation:

The Key Insight: The intercompany balances eliminate. The FX gain/loss does not.

Under US GAAP’s ASC 830-20-35-3 exception, long-term intercompany loans can defer FX gains and losses to CTA instead of hitting P&L.

Why? Because the FX gain represents real economic exposure. EuroCo genuinely benefited from the currency movement — it owes less in its functional currency. That gain survives consolidation. The intercompany balance eliminates, but the FX impact doesn’t.

But here’s where it gets nuanced: What if the intercompany loan is long-term in nature? The accounting standards provide specific guidance.

The FX Survival Question: When Do Intercompany FX Gains/Losses Survive?

The treatment depends on two factors:

1. The nature of the intercompany transaction (trade vs. long-term investment)
2. The accounting framework (US GAAP vs. IFRS)

flowchart TD
    Start[Intercompany FX Gain/Loss] --> Q1{Transaction Type?}
    
    Q1 -->|Trade A/R, A/P| P1[P&L under both frameworks]
    Q1 -->|Short-term Loan| P1
    Q1 -->|Long-term Loan| Q2{Framework?}
    
    Q2 -->|IFRS| P2[P&L - No exception]
    Q2 -->|US GAAP| Q3{Qualifies under
ASC 830-20-35-3?}
    
    Q3 -->|Yes| P3[CTA - OCI, not P&L]
    Q3 -->|No| P1
    
    style Start fill:#e1f5ff
    style P1 fill:#f8d7da
    style P2 fill:#f8d7da
    style P3 fill:#d4edda

Let’s look at what the standards actually say.

US GAAP: The ASC 830-20-35-3 Exception

ASC 830-20-35-3 allows FX gains/losses on intercompany loans “of a long-term-investment nature” to go to CTA (OCI) instead of P&L.

Translation: If the loan is effectively capital in substance — no intention to repay — FX goes to equity, not earnings.

Qualifying Criteria:

Does NOT Qualify: Trade payables/receivables, loans with specified maturity, interest on the loan (separate monetary item).

⚠️ Warning

Missing documentation at loan inception kills CTA treatment. Without contemporaneous board approval and written management assertion, the CTA treatment won’t survive audit scrutiny.

Example: Parent Co (USD) loans $50,000 to Mexico SA (MXN functional). Management asserts settlement is not planned. USD strengthens from MXN 10 to MXN 13. The FX loss reclassifies from P&L to CTA upon consolidation.

CTA on Disposal: When a foreign subsidiary is sold or substantially liquidated, accumulated CTA (including FX from qualifying intercompany loans) reclassifies from equity to P&L as part of the gain or loss on disposal.

IFRS: No Equivalent Exception

IAS 21 requires all FX gains/losses on monetary items to go to P&L. Period.

The nuance: IAS 21.32 allows exchange differences on monetary items that are part of the net investment in a foreign operation to go to equity. But intercompany loans generally don’t qualify — that’s reserved for equity investments.

US GAAP vs. IFRS:

Practical impact: A USD loan from parent to EUR subsidiary creates P&L FX gains/losses under IFRS. Under US GAAP, if the loan qualifies, those move to CTA. For dual-reporters, this creates a reconciliation difference.

The Plug Account Problem: ERP-Level FX vs. Consolidation

Here’s the operational challenge: EuroCo’s ERP automatically generates FX gain/loss entries. When FCCS eliminates the loan, the FX entry remains — orphaned in the Plug account.

flowchart LR
    subgraph ERP[ERP Records]
        A1[Loan at €90,909] --> A2[Revalue to €80,000]
        A2 --> A3[FX Gain €10,909]
    end
    
    subgraph FCCS[FCCS Elimination]
        B1[Loan eliminated ✓] --> B2[FX entry remains]
        B2 --> B3[Plug catches orphan]
    end
    
    ERP --> FCCS
    
    style ERP fill:#e1f5ff
    style FCCS fill:#fff3cd

The Fix:

🚨 Caution

FX gain/loss accounts should not be flagged as Is Intercompany. They’re not intercompany balances — they’re revaluations of existing balances. Flagging them triggers FCCS to look for a matching partner that doesn’t exist.

The trap: Flagging FX accounts as Is Intercompany = True creates unwanted Plug entries because FCCS can’t find a matching partner for the FX remeasurement.

The Plug Account: Where Mismatches Land

Same-currency intercompany should match. Cross-currency intercompany should match after translation. But what if they don’t?

Scenario: Entity A (USD) records A/R from EuroCo as $100,000. EuroCo (EUR) records A/P to Entity A as $95,000. Rate differences, timing differences, plain old data entry errors.

FCCS doesn’t care why they don’t match. It posts the elimination anyway — and puts the difference in a Plug account.

Net Plug balance: $5,000. That’s your mismatch. It sits there until you investigate. The Plug account is the “catch-all bucket” — it’s where every intercompany difference lands.

Plug Account: What It Is and Why It Matters

The Plug account is a single clearing account that catches mismatches. When Entity A’s intercompany receivable doesn’t match Entity B’s intercompany payable, the difference lands here.

Why Keep It Simple:

One Plug account (or one per account type) is standard practice. The Plug represents timing differences, rounding, or data errors — it’s not a permanent balance. It should be investigated and cleared.

What the Plug Tells You:

📝 Note

The Plug account is a temporary home for differences. It’s not where differences live forever. If you have persistent Plug balances, fix the underlying data — don’t build complex account structures to manage them.

When Account Types Don’t Match

Here’s a trap that catches even experienced consolidators: What if Entity A records an intercompany asset and EuroCo records an intercompany expense?

Scenario: EuroCo pays Entity A’s invoice for consulting services, but Entity A hasn’t recorded it yet. EuroCo records:

1
2

Dr: Intercompany Expense    €50,000
    Cr: Cash / A/P           €50,000

Entity A hasn’t recorded the intercompany receivable. No matching asset.

What FCCS Does:

If the accounts are both flagged as Intercompany and have Plug accounts assigned, FCCS will eliminate what exists. But you can’t eliminate an asset against an expense — they’re different account types. The Plug account on each side receives the offsetting entry.

Result:

• Intercompany Expense (EuroCo): Eliminated, Plug receives offset
• No Intercompany Asset (Entity A): Nothing to eliminate

This is why intercompany matching is critical. The Plug account catches everything, but you still have to investigate it.

Common Account Type Mismatches:

The last one is common in period-end cut-off: Entity B received goods but Entity A hasn’t invoiced yet. Entity B records the payable; Entity A has no intercompany revenue to eliminate against. Plug catches the difference.

The Engine Room (The Technical View)

When Does FCCS Eliminate?

FCCS processes intercompany eliminations automatically during consolidation — but only when all conditions are met:

How Common Parent Elimination Works:

In a multi-level hierarchy, FCCS eliminates at the first common ancestor where both entities meet as siblings. Consider this structure:

1
2
3
4
5
6
7

GrandParent
├── Parent A
│   ├── Entity 100 (ICP = 200)
│   └── Entity 101
└── Parent B
    ├── Entity 200 (ICP = 100)
    └── Entity 201

If Entity 100 has an intercompany receivable from Entity 200:

• Entity 100 consolidates to Parent A, then GrandParent
• Entity 200 consolidates to Parent B, then GrandParent
• Elimination occurs at GrandParent — the first common ancestor

The elimination posts to GrandParent’s Elimination member, not to Parent A or Parent B. This is because Parent A only sees Entity 100’s side of the transaction, and Parent B only sees Entity 200’s side. Only GrandParent can see both sides and eliminate them.

📝 Note

If you expect elimination at Parent A or Parent B, you’ll be disappointed. It doesn’t happen there because neither parent sees the complete picture.

Same-Entity ICP: An Edge Case

By default, FCCS won’t eliminate transactions where an entity records an intercompany balance with itself (ICP = the same entity). This is correct — you normally don’t owe money to yourself.

When You Might Need This:

• Reclassification entries within the same entity
• Opening balance adjustments
• Management reporting allocations

How to Override:

Set StrictElimCondition = False in FCCS application settings. This allows same-entity ICP elimination.

🚨 Caution

This is an edge case. Most implementations keep StrictElimCondition = True (the default). If you need same-entity elimination, investigate the data model first — it usually signals a structural issue.

The Equity Method Exception:

Entities with consolidation method = “Equity” don’t trigger automatic intercompany elimination. Why? Because equity-method entities aren’t fully consolidated — only the share of net assets goes to the balance sheet, and the share of profit/loss goes to the income statement.

Common Setup Mistakes:

The Cross-Currency Mechanics

For entities with different functional currencies, the sequence matters:

Sequence:

1. Entity A (USD functional) records in USD
2. EuroCo (EUR functional) records in EUR
3. EuroCo translates to parent currency (USD) — rate types applied (Average for P&L, Ending for BS, Historical for equity)
4. FCCS eliminates — both sides now in parent currency
5. Plug account catches any mismatch

Rate Types Matter:

The Trap: If Entity A and EuroCo use different rate types for the same transaction, the translated amounts won’t match. FCCS will eliminate anyway — and the Plug catches the difference.

Common Rate Type Mismatches:

Investigation Tip: When Plug accounts show differences for cross-currency transactions, check if both entities used the same rate type. A $5,000 Plug difference might not be a data error — it could be Entity A using average rate (€1 = $1.20) while Entity B uses ending rate (€1 = $1.25).

Resolution Options:

1. Adjust one entity to use the same rate type as the other
2. Post a manual elimination adjustment to clear the Plug
3. Accept the difference if it’s immaterial and document the cause

Example: Entity A records intercompany revenue at average rate. EuroCo records intercompany expense at historical rate (the rate when goods were received). The two sides translate to different USD amounts. Plug account shows the difference.

Configuration Dependencies

The Validation Query (The Bridge)

Smart View Layout

Here’s the layout that proves eliminations are working:

POV:

• Entity: [Subsidiary entity]
• Period: [Current month]
• Scenario: Actual
• Consolidation: Entity Input, Elimination, Contribution
• Data Source: FCCS_Intercompany Eliminations
• Intercompany: [Partner entity]

Rows:

1
2
3
4
5
6

Accounts (Intercompany accounts only):
- A/R - Intercompany
- A/P - Intercompany
- Revenue - Intercompany
- COGS - Intercompany
- Plug - IC Differences

Columns:

1
2
3
4

A: Account Name
B: Entity Input (Entity Currency)
C: Elimination (Entity Currency)
D: Contribution (Entity Currency)

Expected Results:

Validation Questions:

1. “Do intercompany receivables and payables net to zero in Contribution?”

   • If yes → Eliminations working correctly
   • If no → Check: (a) ICP dimension populated, (b) Plug account assigned, (c) Consolidation % > 0%

2. “Is the Plug account balance zero?”

   • If yes → Matching is clean
   • If no → Mismatch between entity and partner. Investigate the difference.

3. “Do FX gains/losses on intercompany loans survive elimination?”

   • If yes → Expected behavior for loans denominated in non-functional currency
   • If no → Check rate types and revaluation logic

Intercompany Match Report

FCCS includes a built-in Intercompany Match Report. Use it.

Location: Reports → Intercompany Matching

What it shows:

• Entities with unmatched intercompany balances
• Plug account balances by entity
• Partner mismatches

Common findings:

• Entity A recorded $100, Entity B recorded $95 → $5 difference in Plug
• Entity A recorded with ICP = Entity B, Entity B recorded with ICP = FCCS_No Intercompany → No elimination
• Entity A recorded with ICP = Entity B, Entity B recorded with ICP = Entity C → No elimination

Day 2 Maintenance

New Intercompany Account

Steps:

1. Create the account in Account dimension
2. Set Is Intercompany = True
3. Assign Plug account (existing or create new)
4. Verify Plug account has Is Plug Account = True in metadata
5. Load data with valid Intercompany Partner (ICP dimension)
6. Run consolidation, check Elimination member

🚨 Caution

If you forget the Plug account assignment, FCCS won’t error — it just won’t eliminate. You’ll see the data in Entity Input but nothing in Elimination.

New Subsidiary Added

Steps:

1. Add entity to hierarchy with correct parent
2. Set Consolidation method (Subsidiary, Proportional, etc.)
3. Set Functional Currency in Entity metadata
4. Configure Intercompany Partner for any intercompany accounts the new entity has
5. Verify Plug account assignments for those accounts
6. Run consolidation at parent level

Cross-Currency Balance Mismatch

Symptoms:

• Plug account has non-zero balance
• Elimination amounts don’t match between entity and partner
• Intercompany Match Report shows unmatched balances

Troubleshooting:

1. Run Intercompany Match Report
2. Identify entities with difference
3. Check: (a) Both entities recorded the transaction, (b) Same amount in functional currency, (c) Same ICP partner, (d) Same account
4. If amount differs: Adjust the incorrect entry
5. If ICP differs: Correct the Intercompany Partner dimension
6. If account differs: Reallocate to correct account
7. For cross-currency: Check rate types on both accounts match (Ending for BS, Average for P&L)
8. Re-run consolidation, verify Plug = 0

Year-End Close Prep

Checklist:

• Run Intercompany Match Report
• Resolve all unmatched balances (Plug = 0)
• Verify all intercompany accounts have valid Plug assignments
• Confirm ICP dimension populated for all intercompany data
• Check FX gains/losses on intercompany loans are correctly reported in P&L
• Validate Elimination member shows expected amounts
• Confirm Contribution member nets intercompany to zero

The Trap

The most common misunderstanding: “Intercompany elimination removes the transaction.”

No. It doesn’t remove the transaction from Entity Input. It posts an offsetting entry in the Elimination member. The transaction still exists in Entity Input — the Consolidation dimension shows what happens when you consolidate:

• Entity Input: What each entity recorded
• Elimination: What FCCS eliminated
• Contribution: Entity Input + Elimination = Net presentation

If you expect Elimination to zero out Entity Input, you’re looking at the wrong dimension. Look at Contribution. That’s where the net happens.

📌 Important

FX gains/losses on intercompany loans: Wait, isn’t the loan eliminated? Yes. But if the loan is denominated in a currency other than the entity’s functional currency, that entity recorded FX gains/losses in its P&L. Those gains/losses represent real economic exposure. They survive consolidation.

🚨 Caution

The real trap: Confusing Investment Elimination with Intercompany Elimination. Investment elimination removes the parent’s investment account against subsidiary equity (Pillar 4). Intercompany elimination removes transactions between entities (Pillar 5). They’re different. If you run investment elimination on intercompany receivables, nothing happens — wrong account, wrong partner, wrong logic.

Quick Reference

Key Insight:

1
2

Intercompany balances → Eliminate
FX gains/losses on non-functional currency loans → Survive

What’s Next

This deep-dive covers Pillar 5 of the eleven consolidation pillars. The executive summary introduced all eleven — this is the detailed breakdown for intercompany eliminations.

The pattern is the same across all pillars: accounting requirement → system mechanics → validation → maintenance. Know the standard. Know the system. Build the bridge between them.

Intercompany eliminations aren’t complex because the accounting is hard. They’re complex because the configuration is specific, the FX impact survives, and the Plug account catches everything that doesn’t match. Get the setup right, and the system does the work. Get it wrong, and you’re chasing Plug balances through consolidation logs.

Sources

• Oracle FCCS Documentation: Intercompany Eliminations
• Oracle FCCS Documentation: Intercompany Dimension
• PwC Foreign Currency Guide: Accounting for Long-Term Intercompany Loans — ASC 830-20-35-3 exception for long-term-investment nature intercompany loans
• PwC Foreign Currency Guide: Intercompany Balances — FX gains/losses survive consolidation
• PwC Foreign Currency Guide: Elimination of Intercompany Profits — Historical rate for profit-in-inventory elimination
• IFRS 10 — Consolidated Financial Statements, paragraph B86
• IAS 21 — The Effects of Changes in Foreign Exchange Rates (no long-term-investment exception)
• ASC 810-10-45 — Consolidation: Presentation, paragraph 45-1
• ASC 830-20-35 — Foreign Currency Transactions, paragraph 35-3 (long-term-investment exception)