Cost rollup in project currency
Summarize
Summary of Cost Rollup in Project Currency
This content explains how cost rollup works in projects and sub-projects that use different currencies within ServiceNow. It details how amounts entered in functional currency fields are converted to project currency, how financials roll up from sub-projects to parent projects, and the impact of configuration properties on these processes.
Show less
Key Features
- Currency Conversion for Project Amounts: When entering amounts in functional currency fields (like Planned capital, Planned operating, Actual cost, and Planned benefit), these values are automatically converted to the project currency and saved in corresponding project currency fields.
- Constraints on Manual Entry: Manual entry or updates to functional currency fields are only allowed if the project does not have associated cost plans, benefit plans, or expense lines.
- Multicurrency Cost Rollup Property (com.snc.project.multicurrency.rollupifdifferent): Controls how cost rollup behaves when parent and sub-projects have different project currencies.
- True: Enables association of sub-projects with different currencies and rolls up amounts by converting sub-project costs to the parent project currency using the Budget Reference Rate. The rolled-up amount is an estimate due to exchange rate variations.
- False: Allows association regardless of currency differences but only rolls up costs when parent and sub-project currencies match.
- Interaction with Functional Currency Rollup Property (com.snc.project.rollup.cost):
- If com.snc.project.rollup.cost is false, costs from sub-projects do not roll up regardless of currency settings.
- If com.snc.project.rollup.cost is true and multicurrency rollup is false, rollup only occurs when project currencies match.
- If both properties are true, rollup supports sub-projects with same or different currencies.
Key Outcomes
- ServiceNow customers can manage projects with different currencies more effectively by configuring the currency rollup properties to suit their organizational needs.
- Accurate rollup of costs occurs when parent and sub-project currencies match; otherwise, rollups provide approximate values due to currency conversion.
- Proper configuration prevents errors such as disallowed associations between projects of differing currencies when rollup settings are incompatible.
- Understanding the interplay between the two main properties ensures correct setup for cost rollups and prevents system errors during project association.
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
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.
Roll up project financials from sub-projects to parent projects
Use the com.snc.project.multicurrency.rollup_if_different property for financial rollups when the sub-projects and parent project have different project currencies.
| Property flag | Behavior |
|---|---|
| True | If the property is set to True, then you can:
|
| False | If the property is set to False, then you can:
|
However, the behavior of com.snc.project.multicurrency.rollup_if_different property is different when flagged along with com.snc.project.rollup.cost property.
| 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. |
Illegal association of properties and possible errors
Following are the possible errors that may occur while making an illegal association:
| 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: |