Image
Cumulative Translation Adjustments in Oracle Financial Consolidation & Close (FCCS)

Cumulative Translation Adjustments in Oracle Financial Consolidation & Close (FCCS)

Shreeram Sharma
June 6, 2019

When it comes to the financial close, stakeholders and regulatory bodies require speed and accuracy. By implementing Oracle Financial Consolidation & Close Cloud Service (FCCS), your organization can focus on core business needs, and eliminate the cost and dependencies of infrastructure overhead. Oracle FCCS allows companies to deliver financial and non-financial data to all stakeholders with precision and reliability.

One of the key features of Oracle FCCS is the built-in balance sheet movement translations with FX/Cumulative Translation Adjustments (CTA) Calculations. This option is only available for multi-currency applications. The applications can be configured to include the CTA account in the balance sheet, or in comprehensive income. This blog outlines the process of performing CTA translation adjustments in Oracle FCCS. Refer this blog to know Key Features of Oracle Financial Consolidation & Close Cloud Service (FCCS)

CTA Account

  • System allows to capture FX information in a separate CTA account for all of the historical accounts.
  • CTA member represents the total CTA adjustments.
  • Calculation logic is included in the consolidation script for the re-direction from the source historical accounts to the CTA account.
  • With one CTA account, all FX-CTA calculation results are accumulated to the single CTA account.
  • CTA account is part of Owner's Equity on the Balance Sheet for US-GAAP reporting purposes.

 

CICTA Account

  • CTA adjustments in a single Comprehensive Income CTA account (CICTA) can be captured as part of the Statement for Comprehensive Income for IFRS reporting purposes which aggregates to the balance sheet Other Reserves account.
  • Calculation logic is included in the consolidation script for the re-direction from the source historical accounts to the CTA account.
  • FCCS_CICTA account includes an optional CICTA Redirection Account setting.
  • FX calculation from historical accounts is written to the FCCS_CICTA account.

 

Exchange Rates

FCCS supports two system exchange rates

  • Ending Rate for Balance Accounts
  • Average Rate for Flow Accounts

 

Historical Accounts

  • The Historical Accounts group contains Historical accounts with a Rate Override or an Amount Override for translation.
  • Historical accounts are created as shared members, for example, FCCS_Common Stock
  • If an account is a Historical Account, but does not contain an Override (for example, Retained Earnings), it is not included in the Historical Accounts hierarchy.
  • Historical Account must assign "Historical Rate Override" or "Historical Amount Override" as the Exchange Rate Type.
  • System uses the applicable override for the account during translation.
  • If not specified the Historical account is translated using the Average rate.
  • A pre-built system form named Override Rates is generated from the Historical Account Hierarchy enables to either the Override amount or Override rate for each entity for each currency

 

Cash Change Hierarchy

  • Shows the opening and closing balance of cash accounts and calculates the change in cash adjusted for currency fluctuations.
  • No Configuration is required

 

About the Author

Shreeram Sharma,

EPM Practice Leader and Sr. Solution Architect, Jade Global

Shreeram develops, deploys, and manages Jade Global’s Oracle EPM services. He is an Oracle Certified implementation specialist with 15+ years in technical configuration, design, analysis, delivery and development. Shreeram’s experience in team management, leadership and client relationship management across different platforms helps align our client’s strategic goals with Jade Global’s service offerings. He brings his deep expertise in Oracle Hyperion, Oracle EPBCS/ PBCS, and Oracle FCCS in architecting, leading and creating highly sustainable solutions for our clients.

This post first appeared on LinkedIn

Add New Comment

Restricted HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <h2 id> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.