Analytics Catalog/Oracle EPM/FCCS/FX & CTA Analysis
Explore the catalogFCCSCurrency dimensionMovement dimensionKnown issues
Oracle EPM Cloud · FCCS · Close report

FX and CTA Analysis, explaining the translation

Equity moved, and nothing happened. The CFO wants to know why, the auditor wants it proven by account, and both answers live in the same decomposition: the FX the translation computed, and where it went.

Second page on the reports shelf of the FCCS reference. The mechanics beneath it live in the dimension pages, Currency for the rates, Movement for where FX lands, and the whole reference is mapped on the FCCS index.

RuleAnalyze CTA by entity and account every period, while the rates are fresh and the people who booked them remember why. A year-old CTA question takes a week; a current one takes an hour.
Neverbook a plug to CTA to force the balance sheet. CTA is a computed number; a manual plug there buries a rate or mapping error where it compounds every period after.
Why CTA exists, in one small example— a balance sheet translated at three rates cannot balance, and the difference has a name.

A subsidiary's local books: assets 1,000, liabilities 600, common stock 300, retained earnings 100. Balanced. Now translate to the parent's currency: assets and liabilities at the closing rate of 2.0, giving 500 and 300. Common stock at its historical rate of 3.0, giving 100. Retained earnings at the average rate of 2.5, giving 40. The right side now sums to 440 against assets of 500, and the sheet is out by exactly 60. That 60 is the cumulative translation adjustment, posted to equity, and the balance sheet balances again. Nothing was booked wrong; three honest rates simply cannot agree, and CTA is where their disagreement lives.

How FCCS builds the number— the documented walk, from computed FX to the posting, and the one choice you cannot undo.
StepWhat happens
1 · FX is computedTranslation calculates the FX variance on opening balances and movements, the amounts needed to bring each translated closing balance to its untranslated closing at the ending rate. These land in the Movement dimension's system-owned FX members.
2 · Historical accounts reverseFor every account carrying a historical rate type, plain historical or the rate and amount overrides, the computed FX is reversed into the FX-to-CTA movement members. Held-constant accounts keep their historical value, and the FX they would have shown moves out.
3 · The reversals accumulate and postEverything reversed within the total balance sheet accumulates and posts to the CTA account as a balanced entry. Income statement accounts translate at average and are treated as historical, so their FX flows into the same destination.
The one-time choiceAt application design, CTA lands either in equity on the balance sheet, the US GAAP shape, or in comprehensive income as CICTA, the IFRS shape, with an optional redirection account. Once chosen, it cannot be changed, one of the few genuinely irreversible decisions in the application.
The analysis, built from the questions people ask— the report shape, and the four asks it has to survive.
The askWhat answers it
Why did equity move when nothing happened?CTA by entity, this period against last. The movers are the entities whose currencies moved, sized by their historical-account balances, and the answer usually fits in three rows.
Prove the CTA movement, by accountRows of historical accounts, columns of the FX members, opening FX, movement FX, FX to CTA. The decomposition exists in the cube already; the report just reads it. Practitioners have kept exactly this as a running reconciliation for years, account by account, and the cube makes it a retrieve.
Which rate did you apply, and can you show it?The audit finding in the field is rarely the math, it is missing documentation of rates. The rates table by period and currency, exported beside the analysis, closes the question before it opens.
We sold the subsidiary. Where is its CTA?At disposal, the cumulative CTA of the disposed entity recycles out of equity into income, which means someone needs CTA by entity from the beginning of time. Groups that tracked it per entity answer in a day; groups that did not reconstruct years, at year-end, with auditors waiting.

When the number itself is wrong, translated to one currency but not another, CTA stopped calculating, the opening rollover, the causes live on known issues and the Currency page's trap table. In the owned warehouse, the star schema we recommend building beside FCCS on your own cloud, mapped here, CTA lands by entity, account, and period from day one, so the disposal question and the auditor's decomposition are both queries, not projects. Mechanics verified against Oracle's translation documentation and practitioner references, July 2026.

A CTA number nobody can explain?
We decompose it by entity, account, and rate, wire the running reconciliation into the warehouse, and the next audit ask takes an hour.
Talk to us
Terms on this page
CTA
Where three honest rates record their disagreement. Computed, never booked.
historical rate type
Hold the account constant; send its FX to CTA instead.
CICTA
The same adjustment, presented in comprehensive income. The IFRS shape.
recycling
At disposal, the entity's cumulative CTA leaves equity for income.