FI / FICOintermediate

FICO Group Reporting Part 2: Currency Translation, Intercompany Elimination and the Consolidation Close

Key takeaway

Run the consolidation close: data monitor tasks (release, validation, translation), translation methods and differences, intercompany matching and reconciliation before elimination, elimination postings and differences, and the consolidation monitor sequence to final reporting.

Explanation

📌 KEY POINTS
✅ Translation methods apply closing rate (balance sheet), average rate (P&L) and historical rates (equity); differences go to translation reserve.
✅ Intercompany balances are matched and reconciled at entity level before elimination.
✅ Elimination posts offsetting entries; remaining differences go to elimination difference items.
✅ Data monitor tasks come first, then consolidation monitor tasks, then reporting.
⚠️ Large elimination differences mean entities didn't reconcile — fix at source, don't plug at group.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 covered basics. Now the close.

━━━━━━━━━━━━━━━━━━━━
▶ 1. DATA MONITOR

Release, validation, translation.

━━━━━━━━━━━━━━━━━━━━
▶ 2. TRANSLATION

Methods, rates, differences.

━━━━━━━━━━━━━━━━━━━━
▶ 3. INTERCOMPANY MATCHING

Entity-level reconciliation; disputes.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ELIMINATIONS

IC receivables/payables, revenue/expense; differences.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CONSOLIDATION MONITOR

Sequence and blocking of tasks.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Run data monitor tasks.
Review intercompany differences.
Run eliminations and review differences.

✅ CHECKPOINT: elimination differences within threshold and explained.

Code example

ABAP Code

===== TRANSLATION EXAMPLE (USD unit, group EUR) =====Balance sheet at closing rate 1.08 | P&L at average 1.10 | equity at historical → difference to translation reserve ===== ELIMINATION EXAMPLE =====Unit 1010 IC receivable 100 from 1710 | Unit 1710 IC payable 95 to 1010Elimination: −100 receivable | +95 payable → difference 5 → elimination difference FS item → investigate

Real project scenario

Every month the group team posted manual adjustments for elimination differences between two subsidiaries. Root cause: one booked service charges a month later. A cut-off rule and day-2 matching reduced differences to near zero.

Common mistakes

Plugging differences.
Late matching.
Wrong rates.
Skipping validations.
Task order ignored.

Best practices

Fix at source.
Early matching.
Maintain rates.
Validate data.
Follow monitor sequence.

Interview angle

Questions: "How does currency translation work?", "What are elimination differences?", "What is the consolidation close sequence?"
Strong answer: data monitor, translation methods, matching, eliminations, monitor sequence.

Practice this lesson

Quick check

1. The group team posts manual adjustments every month for the same intercompany differences. What is the right fix?

2. Explain source preparation, translation, intercompany elimination and monitor governance. In the S/4HANA Group Reporting context, which answer shows the strongest practical judgment?

3. Which rates are typically used in currency translation for consolidation?

Interview questions

1. A production issue is reported in S/4HANA Group Reporting around Group Reporting Advanced: Consolidation Units, Intercompany Elimination and Monitor. How would you troubleshoot it systematically and avoid the common failure patterns?

Answer it in your own words first, then compare.

2. You inherit an existing S/4HANA Group Reporting implementation covering Group Reporting Consolidation: Currency Translation, Intercompany Elimination and Close Governance. What would you review before changing it, and what would make you confident the change is production-ready?