Oracle Cloud GL study materials
Oracle Cloud GL study resources

Translation Rate Types and the CTA Difference at a German Subsidiary

Oracle Cloud GL · Put your knowledge to work in context.

All case studies

Translation Rate Types and the CTA Difference at a German Subsidiary

A US-based group reports in USD. Its German subsidiary keeps its primary ledger in EUR and is translated monthly into a USD reporting currency for consolidation. The German controller runs translation on the first working day. For January, the balance sheet is translated at the 31-Jan closing rate of 1.08 USD/EUR, and the income statement at the January average rate of 1.10. The Cumulative Translation Adjustment account shows a debit of $412,000, but the group consolidation team expects $398,000. The difference is traced to retained earnings: the opening balance was translated at the current closing rate, not at the historical rate. The team also translated the intercompany receivable at the closing rate and did not eliminate it before translation. The group uses a separate reporting currency ledger, and the translation rule set has not been reviewed since go-live.

1. Which rate types should apply to the balance sheet, income statement, and equity, and why?

Read the worked answer

Assets and liabilities use the period-end closing rate; income and expenses use the period-average rate; equity items such as opening retained earnings and capital use historical rates. The CTA absorbs the difference and keeps the translated balance sheet in balance. Translating opening retained earnings at the current closing rate re-measures equity and distorts CTA, which explains the $14,000 gap. Define rate types explicitly in the translation rule: period end for balance sheet accounts, period average for P&L, historical for equity. Do not use one rate for all accounts, and do not let a default rate type silently apply to equity. Review the rule set account by account.

2. What should be done about the intercompany receivable and the CTA difference?

Read the worked answer

Translate intercompany balances consistently and eliminate them in consolidation. Translating an intercompany receivable at closing while the payable sits in another ledger can create a mismatch, but the elimination should remove it; do not use CTA to absorb an elimination failure. The CTA difference is not a plug. Correct the historical-rate mapping for retained earnings, rerun translation, and compare CTA to the expected movement. The $14,000 is the equity re-measurement. Document rate types and add a translation checklist: rate type by account type, historical balances for equity, intercompany elimination, and CTA reconciliation. Lock the rule set after review so changes are controlled.

3. What controls would you add before the next close?

Read the worked answer

Add a pre-translation check that every account type maps to the intended rate type, a historical-rate table for equity, a CTA roll-forward, and a comparison of the translated trial balance to the prior month. Restrict changes to the translation rule set and require review before the close. Test with a known rate change and confirm that the reporting currency ledger is not used for journal entry. Because the rule set has not been reviewed since go-live, start with a full account-by-account review and sign-off by the group controller. These are configuration and process controls, not a one-off calculation.