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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Cost rollup in project currency

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

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 feature addresses how financial amounts in projects and sub-projects with different currencies are managed and rolled up into a parent project's currency within ServiceNow Project Portfolio Management.
It ensures that amounts entered in functional currency fields are converted and stored in corresponding project currency fields, enabling consistent financial reporting across multiple currencies.
Show full answer Show less  

## Key Features

* **Currency Conversion for Project Amounts:** When creating a project in a functional currency, amounts entered in fields such as Planned Capital, Planned Operating, Actual Cost, and Planned Benefit are automatically converted to the project currency and stored accordingly, provided no cost plans, benefit plans, or expense lines are attached.
* **Financial Rollup Across Different Currencies:** Using the `com.snc.project.multicurrency.rollupifdifferent` property, you can enable rollup of financials from sub-projects into parent projects even when their project currencies differ. Conversion uses the Budget Reference Rate at the time of rollup, making rolled-up amounts approximate due to exchange rate variations.
* **Property Behavior:**
  * If `com.snc.project.multicurrency.rollupifdifferent` is **true**, sub-projects with different currencies can be associated and rolled up, though totals are estimated.
  * If set to **false**, rollup occurs only when parent and sub-project currencies match, though association is allowed regardless.
* **Interaction with Rollup Cost Property:** The behavior depends also on `com.snc.project.rollup.cost`:
  * If rollup cost is false, no cost rollup happens regardless of currency.
  * If rollup cost is true and multi-currency rollup is false, rollup happens only if currencies match.
  * If both are true, rollup supports different currencies with conversion.
* **Validation and Errors:** Illegal configurations, such as enabling cost rollup but disabling multi-currency rollup with mismatched currencies, trigger errors preventing association of sub-projects to parent projects.

## Key Outcomes

By configuring these properties appropriately, ServiceNow customers can:

* Ensure accurate or approximate financial rollup across projects with different currencies.
* Maintain consistent financial data in project currency fields derived from functional currency entries.
* Control associations between parent and sub-projects based on currency compatibility to avoid errors and maintain data integrity.

This functionality enables comprehensive multi-currency project financial management, facilitating better budgeting, cost tracking, and reporting across global projects within ServiceNow.  
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. * When parent and sub-project currencies match, sub-project amounts roll up to the parent and top project by addition, giving an accurate rolled-up amount. * If the parent project and sub-project have different project currencies, all sub-project costs are converted to the project currency of the parent or top project. The conversion references the Budget Reference Rate. The conversion rate depends on the exchange rates between the project currencies and the specified time period at which the conversion is made. As a result, 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 can't be rolled up. |
| True | False | Can't 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}