Concept: Translated Currencies

Translated currencies enable you to load your actuals data for all levels in a single currency.

How Translated Currency Works

In Adaptive Planning, you always load data, or enter data, at the leaf level. A leaf level is a level that has no child levels. When your instance has multiple currencies, you assign every level a currency. Parent levels can have a different currency than its descendant levels. You load the data in the local currency of the leaf level. Then, Adaptive Planning converts the values into the local currency of each parent level, as the data rolls up the level hierarchy.

Translated currency is an option you can enable in an actuals sub-version to avoid the currency conversion through the level hierarchy. This option also avoids currency conversion in reports for actuals data.

With translated currency enabled, you convert your source data into a single currency of your choice before you load it into Adaptive Planning. This is especially useful for currency conversion in actual data at the transactional level, which Adaptive Planning can’t duplicate.

You can then use a manual import or the data loader in

Design Integrations

to load your actuals data in the local currency of each leaf level as usual. In addition, you can load the same set of data, into the same version, in a single currency for all levels. With the data already converted to a single currency, you can report on the actuals data in that currency, and the values match your source data.

Loading Actuals Data with Translated Currency

You can import actuals data with translated currency through a manual import or using the data loaders in

Design Integrations

. You can also use the

Manage Financial Planning Configuration

task in Workday to create the loaders and to load the data for the translated currency.

Design Integrations

, the versions that you enabled for translated currency have nested options with the currency tagged to the end of the version name.

Example: The version selector in

Design Integrations

looks like this:

Actuals

Import Ledger

Import Ledger USD

To load data in the local currency of each leaf level, you can select Import Ledger
for the

Version Parameter

. To load data in USD for all levels, you can select Import Ledger USD
. You must load each set separately.

Explore Cell with Translated Currencies

Sheets, including sheets on dashboards, always display data in the local currency of the level. There’s no way to display the translated currency in sheets. When launched from sheets, Explore Cell also displays the value in the local currency of the level. As you drill down through levels in Explore Cell, the value reflects the local currency of each level.

However, when you launch Explore Cell from reports or dashboard charts with a specific currency applied to the report, you get 2 different behaviors:

For regular data the value in Explore Cell doesn’t always match the value displayed on the report. Explore Cell displays the value in the local currency of the level, which can differ from the currency of the report. Example: A report in USD displays the data of Sales level (EUR). The value in a cell is 20 USD, displaying the report currency. The value in Explore Cell is 18.5 EUR, displaying the local currency of the level.

For translated currency, the value in Explore Cell displays the same value as the report, not the local currency. Explore Cell indicates when the value is from a translated currency.

CTA Accounts

We don’t recommend that you use the CTA system account for actuals data when you have enabled translated currency. Instead load the CTA values from your source data.

If you do use the CTA system account, we display a value of 0 in versions with translated currency. This is because we aren’t applying exchange rates to that currency. Because the data was loaded with the appropriate converted value, Adaptive Planning doesn’t calculate any CTA for Translated Currencies in the actuals cersion.

Limitations of Translated Currencies

In the version settings, you:

Can't select more than 1 translated currency.

Must enable the feature on sub-versions only. The sub-version can’t have more than 5 descendants.

Can’t enable translated currency on Root Actuals or Journal Entry versions.

In Integrations, you can't:

Use the Erase Data function in

Integration Management

to remove translated currency data directly. If you use this function to erase data at the parent version, you also erase data in the translated currency version.

Use

Erase Settings

tab in the Planning Data Loader. Instead use the Enable Replace Mode
option.

Export the translated data that you imported.

In Modeling, you can’t:

Refresh linked levels in versions with translated currency enabled.

In reports and dashboards:

You might not see your translated currencies in the dashboard currency selector. Dashboards only show the currency associated with the level and the Top Level currency.

When reports have the
Show splits in accounts
setting enabled, we display the local currency of the level for actuals and not the translated values.

To use the loaded pre-converted actuals data, the report can only have actuals versions enabled with translated currency. When you add at least 1 version without translated currency (Plan or Actuals), the entire report uses Adaptive Planning's conversion rates for all actuals versions.

Example: Using Translated Currency

Your level hierarchy looks like this:

Sales (USD)

Europe Sales (EUR)

US Sales (USD)

Mexico Sales (MEX)

Ledger Import is an actuals sub-version with USD as a translated currency. You have two sets of source data:

Local currencies per leaf level.

USD currency for all levels.

Design Integrations

, you set up the version parameter for your local currencies by selecting the Ledger Import version. You load the local currency data with this loader.

Then you set up the version parameter for translated currency by selecting Ledger Import USD, which is nested under Ledger Import. You load actuals that have already been converted to USD in your source data. Now, reports on actuals in USD automatically pull the data loaded into Ledger Import USD. The reported data matches the source data.