Cost rollup in project currency

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 3 minutes to read
  • Summarize
    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

    The cost rollup feature enables ServiceNow users to manage project financials across projects and sub-projects that may operate in different currencies. The rollup calculation is influenced by the budget reference rate, which determines how amounts are converted between currencies.

    Show full answer Show less

    Key Features

    • Currency Conversion: Users can manually enter amounts in functional currency fields, which will automatically convert to project currency fields if no cost, benefit, or expense plans are attached.
    • Financial Rollup: The com.snc.project.multicurrency.rollupifdifferent property allows financial data from sub-projects with different currencies to roll up to their parent project.
    • Property Behavior:
      • If the property is set to True, sub-project amounts can be rolled up, but accuracy may vary due to currency differences.
      • If set to False, rolling up is only possible when project currencies match.
    • Combination of Properties: The interaction of com.snc.project.rollup.cost and com.snc.project.multicurrency.rollupifdifferent properties can affect whether costs from sub-projects roll up to parent projects based on currency compatibility.

    Key Outcomes

    By utilizing these features, ServiceNow customers can effectively manage financial data across multiple currencies, facilitating better project oversight and financial accuracy. Misconfigurations can lead to errors, particularly when associating sub-projects with differing currencies, which can prevent proper financial rollup. Understanding property behavior is crucial for successful project management.

    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.

    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

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

    Table 1. Multicurrency cost rollup property behavior
    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.
    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.

    However, the behavior of com.snc.project.multicurrency.rollup_if_different property is different when flagged along with com.snc.project.rollup.cost property.

    Table 2. Multicurrency cost rollup property in combination with functional currency 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:

    Table 3. Property combinations for sub-project and parent project 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: System policy does not allow parent and child projects to have different project currency pops up.