Money-type properties

Money-type properties are used to handle currency-specific data within the application. They support automatic conversion between currencies based on application settings, making it easier to manage and compare financial information across requests.



How money-type properties behave

  • Values are displayed in the request’s local currency on forms and in the expenditure grid.

  • System-generated money-type properties that pull values from expenditure data will use either monthly or yearly FX rates, depending on the application configuration.

  • Manually entered or calculated money-type properties are also converted using the current month’s or year’s FX rate, as set in the application configuration.


Expenditure aggregation (money-type property option)

The Expenditure aggregation setting allows administrators to configure a money-type property to automatically sum expenditure values from a request and its sub-requests, based on selected category groups.

This is especially useful for building roll-up views in investment programs or grouped requests, helping teams make informed financial decisions at the main request level.


What it does

The expenditure aggregation property:

  • Aggregates expenditure values based on selected category groups

  • Can include data from the main request, sub-requests, or both

  • Converts and calculates the value using the main request’s currency and current FX rates

  • Supports the selection of pre-decision or post-decision form data

  • Is only visible and calculated on main requests, sub-requests display the field as empty


Configuration options

To set up an expenditure aggregation property:

  1. Create a new money-type property in
    Administration → Capex Management → Properties

  2. Enable the Expenditure aggregation option during setup.

Then, configure the following:

  • Category groups: Select one or more predefined expenditure category groups to include in the aggregation.

  • Calculation scope:

    • Calculated in pre- or post-decision state (in the main request)

    • Include sub-request values from pre- or post-decision state

    • Include/exclude main request values

Like other calculated fields, expenditure aggregation properties become read-only after creation.Once created, this property becomes read-only, like other calculated fields.

image-20250807-112633.png

Calculation behavior

  • Calculated only on main requests

  • Value is stored in main request’s currency

  • Auto-recalculates when expenditure data changes in the main request or any sub-requests

  • If no category groups are configured, the property behaves like a standard money field with no aggregation