Planning with Currency Conversion

You can perform planning operations on a single target currency, such as the default currency, or on one or more source currencies. Messages will alert you when an operation affects multiple currencies, because these operations may have unexpected results.

All types of planning operations are supported on target currencies, or on data from multiple currencies:

  • Data entry

  • Spreading, distributing, and assigning values

  • Data actions

  • Structured allocation

These operations are carried out using the target cell’s currency. For example, if you copy a value of 500 USD to a cell that displays a value in Euros, the resulting value is 500 Euros.

If you make a change to a source currency value in a public version, the other currency members in the version are immediately updated to show your changes. If you made the change to a single target currency, other currency members in the version will show diagonal lines instead of values until you publish the changes to the version, and then values for all currencies are updated to reflect your changes.

When you copy a public version while multiple currencies are displayed, you choose which currency to use for planning operations in the new private version. If you select a target currency, the private version shows values only for this currency, and values are converted to other currencies when the version is published. If you choose to plan using source currencies, converted values are shown for other target currencies as you make your changes. See About Version Management for more information about copying and publishing versions.

Planning across multiple currencies

When you are planning on data in multiple currencies (for example, source currency data, or data from a model that has a currency dimension but does not use currency conversion), a planning operation can change values across more than one currency.

However, the different monetary value of each currency is not considered during the operation. As a result, planning operations that affect multiple source currencies may not provide the desired values. For example, if you enter 1 million to an unbooked account for North America while planning in local currencies, it could result in values of 500,000 CAD for Canada and 500,000 USD for the United States. The numerical value is divided evenly, but not the monetary value.

Data entry on North America
Automatic spreading to Canadian and US dollars
When a parent member has a booked value and child members that display multiple currencies, the parent member does not support planning operations. Data cannot be disaggregated to multiple currencies with booked values.

In cases such as this one, a message appears to let you know that data has been entered in multiple different currencies. If necessary, you can undo the operation using the Version Management panel.

Messages are also displayed when you create an allocation process using the currency dimension as a target, or a data action using the currency dimension in a copy rule or as the Aggregate To dimension, and when a user executes one of these processes in a story.

You can avoid this situation by planning on a target currency instead of source currencies, or by filtering the data to a single leaf member of the currency dimension.