---
sourceDocument: Zurich Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-business-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Cost rollup in project currency

# Cost rollup in project currency {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Cost rollup in project currency

This topic explains how ServiceNow handles cost rollup calculations in projects and sub-projects that may use different currencies.
It covers how amounts entered in functional currency fields are converted to project currency, and how financial rollups occur between sub-projects and parent projects considering currency differences.
Understanding these mechanisms helps ServiceNow customers manage multi-currency project financials accurately.
Show full answer Show less  

## Key Features

* **Conversion of functional currency to project currency:** When creating a project in the default functional currency, amounts entered in fields like Planned capital, Planned operating, Actual cost, and Planned benefit are automatically converted and stored in corresponding project currency fields. This is only possible if the project has no attached cost plans, benefit plans, or expense lines.
* **Multi-currency rollup control with properties:** The `com.snc.project.multicurrency.rollupifdifferent` property governs how financial data rolls up from sub-projects to parent projects when currencies differ:
  * If set to **True**, sub-projects with different currencies can be associated and amounts are converted to the parent project's currency using budget reference rates. The rolled-up amount is an estimate due to exchange rate variations.
  * If set to **False**, rollup occurs only if sub-project and parent project currencies match. Association is allowed regardless of currency, but amounts do not roll up if currencies differ.
* **Interaction with the `com.snc.project.rollup.cost` property:** This property controls whether costs roll up at all:
  * If false, cost rollup is disabled even if sub-projects and parent projects have different currencies.
  * When true, rollup depends on the multi-currency rollup flag:
    * If multi-currency rollup is false, rollup only occurs when currencies match.
    * If multi-currency rollup is true, rollup occurs regardless of currency differences.
* **Error handling:** Illegal combinations, such as attempting to associate sub-projects with different currencies when rollup is disallowed, trigger system errors preventing the association and informing users accordingly.

## Practical Implications for ServiceNow Customers

* Customers can manage projects with different currencies and control how financial data rolls up by configuring properties appropriately.
* Enabling multi-currency rollup allows approximate financial consolidation at the parent project level, useful for global organizations dealing with multiple currencies.
* Disabling rollup or multi-currency rollup enforces stricter financial boundaries, preventing aggregation of costs across currencies.
* Understanding property interactions and error conditions helps avoid configuration mistakes and ensures accurate financial reporting.  
Cost rollup calculation in projects and sub-projects with different currencies varies
with the budget reference rate. The rate at which the amount is converted depends on the
conversion rate.

## Convert amount entered in functional currency fields to project currency {#project-costing-project-currency__section_et5_2py_vjb}

When you create a project in functional currency of the Default view, you can manually
enter or update the amount in the Planned capital, Planned operating, Actual cost, and Planned benefit fields. As you enter values in these fields, the amount is converted
to project currency and stored in the corresponding project currency fields such as
Planned cost in project currency, Planned operating in project currency, Actual cost in project currency, and
Planned benefit in project currency fields.  
Note:  
You can do so only if the project does not have a cost plan, benefit plan, or expense lines attached to it.

## Roll up project financials from sub-projects to parent projects {#project-costing-project-currency__section_twb_bqy_vjb}

Use the com.snc.project.multicurrency.rollup_if_different property for
financial rollups when the sub-projects and parent project have different project
currencies.
{#project-costing-project-currency__table_y5y_tty_vjb__entry__2}

| Property flag | Behavior |
|-|-|
| True | If the property is set to True, then you can: 1. Associate a sub-project to a parent project, where both the projects have different project currencies. 2. Roll up the sub-project amounts to the parent project amounts. However, the accuracy of the rolled up amount in the parent project varies because of the currency variation. * If the project currencies of the parent project and the sub-project are the same, then the project currency amounts from the sub-projects to its parent and the top project are rolled up by adding up the amounts in the sub-project, and the rolled up amount is accurate. * If the project currencies of the parent project and the sub-project are different, then all the costs of the sub-projects are converted to the project currency of the parent or the top project, referencing the Budget Reference Rate. The rate at which the amount is converted depends on the exchange rates between the project currencies, and the specified time period at which the conversion is made. Hence, the rolled up amount is only an estimate or an approximate value. {#project-costing-project-currency__ul_afc_vk2_wjb} |
| False | If the property is set to False, then you can: 1. Associate any number of sub-projects to a parent project, where the project currencies are same or different. 2. Roll up only if the project currencies of the sub-project and the parent project match. {#project-costing-project-currency__ol_anx_1l2_wjb} |
[Table 1. Multicurrency cost rollup property behavior]

{#project-costing-project-currency__table_y5y_tty_vjb}

However, the behavior of
com.snc.project.multicurrency.rollup_if_different property is
different when flagged along with com.snc.project.rollup.cost
property.
{#project-costing-project-currency__table_q1h_g32_wjb__entry__2}

| Properties flag | Behavior |
|-|-|
| com.snc.project.rollup.cost property is false | You can associate any sub-projects with parent project that have same or different project currency but the costs of sub-projects do not roll up to the parent project. |
| com.snc.project.rollup.cost property is true and com.snc.project.multicurrency.rollup_if_different property is false | You can associate sub-projects with parent project that has the same project currency. |
| com.snc.project.rollup.cost property is true and com.snc.project.multicurrency.rollup_if_different is true | You can associate any sub-project that has the same or different project currency with the parent project. |
[Table 2. Multicurrency cost rollup property in combination with functional currency property]

{#project-costing-project-currency__table_q1h_g32_wjb}

## Illegal association of properties and possible errors {#project-costing-project-currency__section_ivl_xym_2kb}

Following are the possible errors that may occur while making an illegal association:
{#project-costing-project-currency__table_or2_2zm_2kb__entry__3}

| com.snc.project.rollup.cost | com.snc.project.multicurrency.rollup_if_different | Behavior |
|-|-|-|
| False | Either true or false | Can associate sub-project to parent project even though project currency of sub-project and parent project is different but costs from sub-project to parent project cannot be rolled up. |
| True | False | Cannot associate sub-project to parent project if project currency of the sub-project and parent project is different. In such case of an association, an error message: `System policy does not allow parent and child projects to have different project currency` pops up. |
[Table 3. Property combinations for sub-project and parent project association]

{#project-costing-project-currency__table_or2_2zm_2kb}