In Oracle Financial Consolidation and Close Cloud Service (FCCS) and Hyperion Financial Management (HFM), entity currency and reporting currency are two distinct currency views of the same financial data — representing the same amounts in different currencies. Entity currency (abbreviated [EC] in FCCS/HFM) holds each entity’s financial data in its functional currency — a Saudi entity’s data is in SAR, a UAE entity’s data is in AED, an Egyptian entity’s data is in EGP. Reporting currency (abbreviated [RC] or [PUSD] depending on the application) holds the translated equivalent of each entity’s data in the group’s reporting currency — typically USD for a group with international operations, or SAR for a Saudi-headquartered group. The translation from entity currency to reporting currency is performed by the consolidation engine using the rate types configured for each account — average rate for income statement items, closing rate for balance sheet items, historical rate for equity.
Currency Layer Architecture in FCCS
FCCS stores currency data in the Value dimension — a system dimension that contains the currency-context members for each data value. The primary Value members relevant to currency are:
| Value Member | Currency | How Populated |
|---|---|---|
| [Entity Currency] (EC) | Entity’s functional currency (SAR, AED, EGP) | Entity finance team submission; Data Management data load from ERP |
| [Entity Curr Adjs] (ECA) | Entity’s functional currency | Manual adjustments posted in entity currency by entity or group finance team |
| [Entity Curr Total] (ECT) | Entity’s functional currency | Calculated: EC + ECA |
| [Parent Currency] (PC) | Parent entity’s currency (or group reporting currency) | Calculated by FCCS translation engine from ECT using configured rate types |
| [Parent Adjs] (PA) | Parent/reporting currency | Group-level adjustments posted in reporting currency |
| [Proportion] (POWN) | Parent/reporting currency | Proportional consolidation: PC × ownership percentage |
| [Elimination] (ELIM) | Parent/reporting currency | Intercompany elimination postings |
| [Contribution] (CONSOL) | Parent/reporting currency | Net consolidated contribution: sum of all Value layers |
Why the EC/RC Architecture Matters for Audit
The entity currency / reporting currency architecture in FCCS provides a complete audit trail of the translation process: auditors can see the original entity currency submission (EC), the translated reporting currency value (PC), and the exchange rate that was applied (derivable from the rates stored in the rate accounts for the applicable period). This traceability is essential for IAS 21 compliance — the auditor must be able to verify that the correct exchange rate was applied to each account type. An EPM architecture where translation happens outside FCCS (in a spreadsheet or a manual calculation before loading) and only the translated amounts are loaded into FCCS loses this audit trail, because the EC values are absent or not tied to the translated RC values in a way that allows the translation rate to be verified.
GCC Multi-Currency Reporting
GCC groups frequently need more than one reporting currency — SAR for SOCPA statutory reporting, USD for international investor communication, and potentially EUR or GBP for specific bond issuances or investor bases. FCCS supports multiple reporting currencies through additional parent currency layers or through separate consolidation runs with different rate tables. The architectural decision — whether to maintain multiple currency views within a single FCCS application or to run separate consolidations for each reporting currency — depends on the volume of the report output required and the close timeline available.
What Goes Wrong in Practice
The most specific entity currency / reporting currency configuration error is loading data into the Parent Currency layer directly — bypassing the entity currency layer and the FCCS translation engine — because the integration team found it simpler to load pre-translated amounts from the ERP than to load functional currency amounts and configure FCCS’s translation rules. This shortcut produces a consolidation that appears to work but has no entity currency data, no verifiable exchange rate application, and no translation difference calculation — because the translation never occurred within FCCS. Auditors who request the IAS 21 currency translation disclosure find that the information does not exist in the application.
How Loop Wise Solutions Configures This
We always load data into the entity currency layer and configure FCCS’s translation engine to perform the translation — never bypassing FCCS translation by loading pre-translated amounts. The entity currency layer is the non-negotiable starting point for any FCCS consolidation that must satisfy IAS 21 disclosure requirements.
