After loading DeutschWerk's EUR trial balance in Hall 3, the entity sits at Impacted. Before running the full consolidation, the Finance Controller has the option to run Translate only — a standalone rule that converts entity currency balances to reporting currency and stops there. No proportion, no elimination, no contribution rollup.
This serves three practical purposes in the GlobalMerge Q1 close. First, it lets the Finance Controller verify that average and closing rates are correctly applied — P&L accounts at the average EUR/USD rate, balance sheet accounts at the closing rate — before committing to a full consolidation run. Second, it allows the team to review translated balances in Smart View and confirm CTA is calculating correctly. Third, it is faster than a full consolidation — useful for troubleshooting FX rate issues without running the entire engine.
Running Translate only does not set the entity to OK. It confirms the translation is correct. The entity remains Impacted until Consolidate runs.
When the Finance Controller selects Consolidate from the Action menu, FCCS runs the complete consolidation engine in one sequence. Translation is the first internal stage — it fires automatically as part of the Consolidate action, so running Translate separately first is optional, not mandatory.
The sequence inside one Consolidate action, using DeutschWerk as the example entity: Translation → Entity Total → Proportion (80%) → IC Elimination → Contribution. Every stage runs in order. The entity reaches OK only after all stages complete.
Path A is preferred during the close period when FX rates are new, when a rate correction was made after a prior consolidation, or when the team is troubleshooting unexpected CTA balances. Path B is used when rates have been validated in a prior run or in UAT, or when time pressure at close means the team runs Consolidate directly. Both paths produce the same final result. The choice is a governance and efficiency decision, not a technical one.
Under IAS 21 (The Effects of Changes in Foreign Exchange Rates), the translation of a foreign subsidiary's financials into the group's presentation currency follows specific rules that reflect the economic nature of each account type.
P&L accounts (Revenue, Expenses) are translated at the average rate for the period. DeutschWerk's Q1 revenue of €5,000,000 is translated at the average EUR/USD rate across January to March. The average rate reflects the economic reality that revenue was earned and costs were incurred throughout the period — not at a single point.
Balance sheet accounts (Assets, Liabilities) are translated at the closing rate — the EUR/USD rate at 31 March. This reflects the current economic value of those positions at reporting date.
Equity accounts are translated at historical rates — the rate at the time each equity transaction occurred. Share capital issued when EUR/USD was 1.05 stays at 1.05 forever in the translation.
The difference between these three rate applications across the balance sheet accounts is what creates the Currency Translation Adjustment (CTA) — a balancing figure in equity that ensures the translated balance sheet still balances. FCCS calculates CTA automatically using prebuilt calculations on the Movement dimension. No manual journal required.
| Entity | Ownership % | Method | What Runs in Consolidation | Minority Interest |
|---|---|---|---|---|
| BritEdge Ltd | 100% | Full | Translation → Entity Total → Proportion (100%) → Elimination → Contribution | None — 100% owned |
| DeutschWerk GmbH | 80% | Full + NCI | Translation → Entity Total → Proportion (80%) → Elimination → Contribution. 20% NCI carved out to equity. | 20% of net income and equity disclosed as non-controlling interest |
| AsiaLink Pte | 50% JV | Equity method | No line-by-line consolidation. Investment carrying value on BS. Share of net income (50%) on P&L. | Not applicable — no control, no consolidation of lines |
| NovaTech Inc | 30% | Equity method | Investment at cost plus share of cumulative profits. 30% of net income on P&L. No translation needed (USD). | Not applicable |
FCCS automates basic intercompany eliminations — DeutschWerk's revenue vs BritEdge's COGS for the £420,000 component sale. What FCCS does not automate is unrealised profit in inventory. If BritEdge has not yet sold those components at period end, the profit DeutschWerk recognised is unrealised from the group's perspective. This requires either a custom Groovy rule (Hall 5) or a manual Enterprise Journal (Hall 7) — a judgement-based adjustment that FCCS cannot make automatically because it requires knowing the downstream sale status. This is the precise boundary between FCCS automation and human judgement in the close process.
FCCS uses PVA (Periodic Value Average) method for Flow accounts — Revenue and Expense use the period average rate. VAL (Value at ending rate) for Balance accounts — Assets, Liabilities, and Equity use the closing rate. These are the FCCS defaults; they can be overridden per account using Translation Override rules or Historical Rate entries for accounts requiring a specific historical rate.
The CTA account (FCCS_CTA) is automatically populated — it is the plug that makes the translated balance sheet balance. The two prebuilt Movement dimension calculations that drive CTA are: FCCS_OpeningBalance × closing rate − FCCS_OpeningBalance × prior closing rate (FX on opening) and FCCS_Mvmts_Subtotal × closing rate − FCCS_Mvmts_Subtotal × average rate (FX on movements). These run automatically inside every Consolidate action.
-
1
Navigate to Consolidation. From the FCCS home screen: Consolidation → Consolidate. Select the Point of View: Scenario (Actual), Year (FY2025), Period (Q1), Entity (GlobalMerge Corp for a full group run, or a specific entity for a single-entity run).Running at GlobalMerge Corp (the parent) triggers consolidation for all child entities in sequence, bottom-up through the hierarchy. Running at DeutschWerk only processes that entity.
-
2
Choose Consolidate or Translate. The Action menu offers: Translate (standalone, runs FX only), Consolidate (full engine including translation), Force Consolidate (reruns even if status is OK — used after rule changes), and Calculate (runs member formulas only without consolidation logic).Force Consolidate is used after Groovy rule changes in Hall 5 — when the data has not changed but the rule logic has. Regular Consolidate only runs on entities with Impacted or SC status.
-
3
Monitor the job. Navigate to Jobs → Consolidation Jobs. Each entity's consolidation appears as a separate line — status progresses from Running → Complete. Any entity that fails shows an error with a link to the job log. The log shows which stage failed: translation, proportion, or elimination.
-
4
Verify OK status. After the job completes, return to the Consolidation Status grid. All entities should show OK. If any entity shows Impacted after a consolidation run, a data change occurred during the run — investigate before reporting.
All four entities are at Impacted. Exchange rates are loaded: EUR/USD average 1.09, closing 1.11. GBP/USD average 1.26, closing 1.28. SGD/USD average 0.742, closing 0.748. NovaTech is USD — no rates needed.
The Finance Controller wants to validate DeutschWerk's EUR translation before running the full group consolidation — she is not confident the closing rate of 1.11 was correctly entered versus last quarter's 1.08. She asks you to run Translate only for DeutschWerk first, then pull the balance sheet in Smart View to confirm FCCS_TotalAssets is at 1.11, not 1.08.
After validation, run the full group consolidation and confirm: DeutschWerk's 20% minority interest is correctly calculated, the £420,000 BritEdge/DeutschWerk IC elimination ran, and AsiaLink shows only the equity method investment line — no revenue or cost lines in the group P&L.
- Run Translate only for DeutschWerk. Navigate to Consolidation → Consolidate → select DeutschWerk → Action: Translate. Job completes. Pull DeutschWerk balance sheet in Smart View at EUR and USD currency members. Confirm FCCS_TotalAssets × USD = FCCS_TotalAssets × EUR × 1.11 (closing rate). If it shows 1.08, the closing rate was entered incorrectly — correct in Application → Exchange Rates and re-run Translate.
- Validate DeutschWerk's P&L translation. Pull FCCS_Revenue in Smart View. EUR value = €5,000,000. USD value should = $5,450,000 (× average rate 1.09). Confirm CTA account has a balance in equity — it will not be zero because average ≠ closing rate.
- Run full group Consolidate. Select GlobalMerge Corp as the entity, Actual/FY2025/Q1. Action: Consolidate. Monitor job. All four entities should process bottom-up: BritEdge, DeutschWerk, AsiaLink, NovaTech, then GlobalMerge Corp.
- Verify DeutschWerk minority interest. Pull the Consolidation dimension in Smart View for DeutschWerk. Confirm: Entity Total = $5,450,000. Proportion = $4,360,000 (80%). NCI = $1,090,000 (20%) appearing in equity disclosure, not as a revenue deduction.
- Verify BritEdge/DeutschWerk IC elimination. Pull DeutschWerk's revenue at FCCS_Elimination member. Should show −$529,200 (the £420,000 IC sale at 1.26 GBP/USD). Pull BritEdge's COGS at FCCS_Elimination. Should show matching elimination. Net effect on group P&L: zero.
- Verify AsiaLink equity method treatment. Pull GlobalMerge Corp consolidated P&L. AsiaLink's revenue and cost accounts should be zero. Confirm a single "Share of JV income" line appears. Pull GlobalMerge balance sheet — confirm "Investment in AsiaLink" carrying value is present.
- Confirm all entities show OK status. Consolidation is complete. The Finance Controller can now open Hall 7 — Reporting — to build the Q1 group P&L and balance sheet.
The job log shows DeutschWerk's consolidation completed without errors. No failed stages. But the status grid shows DeutschWerk as Impacted after the run. The Finance Controller is alarmed — she has never seen this before.
Consolidation completed without errors but the entity did not reach OK. What could cause an entity to remain Impacted after a successful consolidation run? There are two likely explanations.
Root cause 1 (most common): DeutschWerk's controller posted a journal entry or loaded additional data during the consolidation run — after the job picked up the entity but before it completed. The new data changed the entity's status to Impacted again mid-run. Fix: confirm no loads or journal posts occurred during the consolidation window, then run Consolidate again for DeutschWerk only.
Root cause 2: The consolidation ran but encountered a lock conflict on a downstream calculation — DeutschWerk's data feeds a parent calculation that another user was accessing. The job completed its own scope but the parent entity recalculation set DeutschWerk back to Impacted. Fix: ensure no users are in forms or running reports during the consolidation window, then Force Consolidate DeutschWerk.
- → The Finance Controller runs Translate only for DeutschWerk. The entity stays at Impacted. She asks: "Did the translation fail?" How do you explain the difference between a failed Translate run and an expected Impacted status after a successful Translate run?
- → DeutschWerk's revenue is €5,000,000 translated at average rate 1.09 = $5,450,000. The balance sheet shows total assets of €8,200,000 translated at closing rate 1.11 = $9,102,000. The CTA account in equity is not zero. Calculate approximately what the CTA balance represents and explain in plain English why it exists.
- → AsiaLink is a 50% JV. FCCS applies the equity method — no line-by-line consolidation. AsiaLink had revenue of SGD 4,000,000 and net income of SGD 600,000 in Q1. What appears in GlobalMerge's group P&L and balance sheet for AsiaLink specifically? Show the amounts.
- → DeutschWerk sold €420,000 of components to BritEdge. BritEdge has not sold half of them at 31 March. The basic IC elimination ran. What is still unresolved, and which path in FCCS handles it — Groovy rule in Hall 5 or Enterprise Journal in Hall 7? What information does the system need that it cannot derive automatically?
- → Force Consolidate reruns the engine even when status is OK. When would a Finance Controller use Force Consolidate rather than waiting for an Impacted status, and what risk does running it unnecessarily create in an approved, locked period?
Questions progress from Recall → Application → Scenario. Click an option to reveal the answer. Use your score to decide if you are ready for Hall 5 — Calculation Studio.