Translated Currencies for Actuals Versions
With the 2024R2 release, we introduce translated currencies. With translated currencies we enable you to load actuals data in a specific currency for all levels. You can load your data in the local currency of each leaf level as usual. In addition, you can load the same set of data in a single currency for all levels.
Business Benefits
When your source systems store granular, transaction-specific exchange rates, you can get variances between the actuals in your source and the actuals in Adaptive Planning because of how we convert the data between currencies. Loading translated actuals eliminates the conversion of the actuals data.
With translated currency, you load your actuals already translated from your source. As a result, the actuals in Adaptive Planning exactly matches the actuals in the source for the currency.
In addition, reports pull from the actuals loaded in the currency, removing the need to calculate conversion with exchange rates.
Changes
In the Version area of Modeling, we provide a new Enable Translated Currency check box in the settings within sub-versions of actuals. When you enable this check box, the Selected Currencies drop-down prompt enables you to select 1 currency as a translated currency.
In Design Integrations, we update your ability to import actuals data into the version that you enabled for translated currencies. You have the option to select:
- The nested currency within the sub-version to load the full data set in a single currency for all levels.
- The sub-version itself to load data as usual in the local currency of each level.
We also update these APIs:
- v40 of the exportVersions: We add the currencyVersions attribute in the Include element to indicate if the nested currency of the sub-version is included in the response.
- v40 of the importStandardData: The API supports imports to the sub-version for the currency.
We also enable you to set up translated currency from the financial planning configuration manager task in Workday. We provide these new fields:
- Translated Currency on the Currency page enabling you to select up to 1 translated currency.
- Account Translation Rule Set on the Actuals page enabling you to select the rule set for mapping translation rate types to ledger accounts.
When you enable translated currencies on versions, we continue to display values using local currencies for each level on sheet data and Explore Cell on sheets.
When you enable translated currencies on versions and explore cells in these areas, we now display values using the reporting currency of those cells:
- Dashboards.
- OfficeConnect.
- Web Reports.
Example
Your instance uses both USD and EUR. For the sub-version, Ledger Import, you enable translated currencies and select USD as the translated currency. Now, you can load your entire actuals data set in USD from your source system.
In Integration, when you select Ledger Import version for importing your actuals data, you have the option to select the USD currency, which displays nested under the Ledger Import version.
Later, you build a report in USD and pull the appropriate data in the currency of the report, without the conversion of data with exchange rates.
What Do I Need to Do?
To see if your instance is eligible for this feature, a Named Support Contact must contact us. See Reference: Contact Us.