System Properties for Capex Management
Weissr Capex Management uses request types, GLOBAL, CAPEX, EXPENDITURE, to organize workflow and data. Each request type has its own set of applicable properties, including both configurable and system-managed fields.
Overview of request types and properties
GLOBAL Properties
Applicable across all request types, including CAPEX, EXPENDITURE, and BUDGET.
Retrieve or calculate data dynamically based on the context of the request.
Example: Fields such as Request Name, Project Leader, and Requested Amount store universal information critical for all workflows.
CAPEX Properties
Specific to CAPEX requests, these properties manage data related to capital investments and projects.
Example: Fields like NPV (pre-decision), Payback Period, and Total Capex Amount provide detailed financial metrics for evaluating investment proposals.
EXPENDITURE Properties
Designed for expenditure requests, these properties handle data specific to financial outlays and budget line items.
Example: Fields such as Expense Type, Commitments, and Tax Depreciation focus on expenditure tracking and reporting.
Properties applicable to request type GLOBAL
Properties of type GLOBAL store information across all request types—CAPEX, EXPENDITURE, and BUDGET—in Weissr Capex Management. With built-in logic, GLOBAL properties can retrieve or calculate data as needed and operate consistently regardless of the request type. In Capex and Budget requests, GLOBAL properties pull data from the original project source. In Expenditure requests, they hold data specific to the individual expenditure request.
System properties applicable to request type GLOBAL
Note: Property names and their codes can be customized, so each instance may display different names for these properties.
ID | Property Type | Name | Description |
|---|---|---|---|
1 | String (single line) | Request name | A mandatory field used to describe the request or project. Also used to label each line in the Expenditure grid. |
3 | Currency | Currency | The local currency associated with the organizational unit for the request. |
7 | Node | Production unit | Represents the organizational unit (node) associated with the request. |
68 | String (single line) | External mapping ID | External system identified for integration purposes. |
86 | Date | Creation date | Automatically set to the date the request or expenditure was created. |
Properties applicable to request type CAPEX
Properties of type CAPEX are properties that store information about requests and projects within Weissr Capex Management. These properties have built-in logic to serve specific functions, such as calculating or retrieving data automatically based on the system’s rules. Unlike configurable properties, the behavior of static CAPEX properties cannot be modified through configuration. In both Capex and Budget requests, CAPEX properties display data directly from the original Capex request source.
System properties applicable to request type CAPEX
For some properties of type Money, the Code (original name) is set by default. However, in certain installations, this code may not appear automatically; if required for calculations, a support case should be opened to insert these values.
Note: Property names and their codes can be customized, so each instance may display different names for these properties.
ID | Property Type | Name | Description |
|---|---|---|---|
4 | Fiscal Year | Include to budget | The year when budget inclusion is expected or desired for the request/project. |
5 | User | Project leader | The user selected in this field can advance the request from the initial preparation step in the approval route. If no user is selected, only the creator of the request will be able to move it forward. |
6 | Model | Model | A drop-down selection of the available investment models that can be used depending on the characteristics of the request/project. |
8 | Route | Route | Defined routes based on investment size or approval authority. |
14 | Fiscal Year | Analysis start year | Sets the first year in which data can be entered for both the Capex form and Cash Flow model. For example, if capexes and outlays start in 2024, enter 2024 in this field. |
15 | String (single line) | Project no. | A unique serial number automatically generated by the system for each request or project. Example: The project number format includes:
|
16 | Money | NPV (Follow-up) | The Net Present Value (NPV) is calculated based on future cash flows (including expenditures) after final approval. |
17 | Decimal | Profitability Index (Follow-up) | The Profitability Index (PI), calculated as the present value of future cash flows divided by the present value of the investment. Calculated after final approval. |
18 | Decimal | Payback, disc. (Follow-up) | The discounted payback period, which calculates the time required to recover the costs of an investment. Calculated after final approval. |
19 | Money | NPV | The Net Present Value (NPV) is calculated based on future cash flows (including expenditures) before final approval. After final approval, this amount reflects the NPV at the time of approval and does not update with subsequent changes. |
20 | Decimal | Profitability Index | The Profitability Index (PI) is calculated as the ratio of the present value of future cash flows to the present value of the investment. This calculation is performed before final approval. After final approval, the PI becomes fixed and will not update with any subsequent changes. |
21 | Decimal | Payback, disc. | The discounted payback period, which calculates the time required to recover the costs of an investment. This calculation is performed before final approval. After final approval, the PI becomes fixed and will not update with any subsequent changes. |
22 | Money | Requested amount | The total of all expenditures (capex and opex) listed in the project's pre-decision "Capex" tab. After final approval, this amount is fixed and will not be updated with subsequent changes. |
25 | Money | Approved Budget amount | A non-editable field showing the amount approved for the project in a budget within the Capital Budgeting module, if it has been approved. |
26 | Current step | Current step | Indicates the current step the project is at within the approval route. |
27 | Project state | Approval state | Represents the current state of the project based on its position in the approval route. Possible states include Draft, Under review, Decision, Monitoring, Follow-up, Completed, Rejected, or Undefined. |
28 | Fiscal Year | Postponed in approved budget | The year to which the project is postponed in the approved budget. |
31 | String (multiline) | Comment from budget | Comments related to the project from the approved budget. |
32 | Approved in budget | Included in approved budget | A non-editable field indicating whether the project is included in the current approved budget. Options include Yes, No, or Not decided. The field remains blank if no budget is approved. |
33 | Money | Additional capex amount | Contains the sum of the "Requested amount" from all additional requests that have received final approval. Not calculated in additional funding or reallocation requests. |
34 | Money | Total approved capex amount | The combined total of the "Requested amount" and the "Additional capex amount". Not calculated in additional funding or reallocation requests. |
35 | User | Suggested decision maker | The decision maker assigned to the current step in the approval route. |
36 | Money | Total outcome | The sum of all listed expenditures (capex and opex) entered in the project’s post-decision "Capex" tab available after final approval. Not calculated in additional funding or reallocation requests. |
39 | Fiscal Year | Approved budget year | The budget year into which the request was included. |
41 | Date | Forecast start date | Editable only in the execution phase. Expenditures before this date are considered actual and non-editable in the "Capex" tab. Expenditures after this date can be edited. |
42 | Money | Total spent amount | The sum of all expenditures (capex and opex) listed in the project's "Capex" tab that occur before the "Forecast start date”. This value is calculated only after the final approval of the project. Only calculated in standard requests - not in any additional funding or reallocation requests. |
43 | Project state category | Project state category | Indicates the project's current state based on its position in the approval route. The possible state categories are:
|
44 | User | Owner | The user who created the request/project. The creator can advance the request from the initial preparation step in the approval route. |
45 | String (single line) | Status in approved budget | Indicates the project's status in the current approved budget. Options include Not included, Rejected, Postponed, or Approved. |
46 | String (singleline) | Approved budget name | The name of the approved budget in which the request is included. |
65 | Decimal | IRR (follow up), % | Internal Rate of Return (IRR), calculated on cash flow after final approval. |
66 | Decimal | IRR, % | Internal Rate of Return (IRR), calculated on cash flow before final approval. After final approval, the IRR becomes fixed and will not update with any subsequent changes. |
67 | Date | Final approve date | Automatically set to the date when the project received final approval. |
69 | Money | Decision amount total | The approved amount at the time of final approval, excluding additional approved requests. |
76 | Money | Total capex amount | The total pre-decision capex expenditure. Fixed after final approval. |
77 | Money | Total opex amount | The total pre-decision opex expenditure. Fixed after final approval. |
78 | Code | Analysis period length | Defines the project's analysis period length. This determines the number of years available for adding expenditures and the length of the investment model. |
79 | Money | Previous allocated amount | Calculated in additional funding requests. It represents the sum of the "Requested amount" from the original request and all previous additional requests. This amount matches the "Total approved capex amount" in the original request at the time the additional request is created. |
80 | Money | Total allocated amount | Calculated in additional funding requests. It is the sum of the "Requested amount" from the original request, the current additional request, and any previous additional requests. |
81 | Integer | ID | The request ID is in the database. Table |
82 | Integer | Investment program ID | The ID of the main request within an investment program. |
83 | Boolean | Modification in Capex | Automatically set to TRUE when adjustments are made to expenditures (capex and opex) in the project's "Capex" tab. |
84 | Money | Total allocated capex amount | Calculated in additional funding requests. It is the sum of the "Total capex amount" from the original request, the current additional funding request, and any previous additional funding requests. |
85 | Money | Total allocated opex amount | Calculated in additional funding requests. It is the sum of the "Total opex amount" from the original request, the current additional funding request, and any previous additional funding requests. |
92 | Boolean | Is additional request | Automatically set to TRUE for additional requests, including new funding or transfer funding requests. Set to FALSE for standard requests/projects |
Properties applicable to request type EXPENDITURE
Properties of type EXPENDITURE are properties that store information about expenditure requests, line items in the expenditure grid within a capex request project within Weissr Capex Management. These properties have built-in logic to serve specific functions, such as calculating or retrieving data automatically based on the system’s rules. Unlike configurable properties, the behavior of static EXPENDITURE properties cannot be modified through configuration.
System properties applicable to request type EXPENDITURE
For some properties of type Money, the Code (original name) is set by default. However, in certain installations, this code may not appear automatically; if required for calculations, a support case should be opened to insert these values.
Note: Property names and their codes can be customized, so each instance may display different names for these properties.
ID | Property Type | Name | Description |
|---|
ID | Property Type | Name | Description |
|---|---|---|---|
23 | Date | In use date | The date when the asset or expenditure item is expected to be operational or available for use. This field is required and is used as the start date for depreciation calculations, if applicable. Ensure this reflects the actual or planned commissioning date. |
87 | Code | Category | Defines the expenditure category for each line item. This property is required and helps classify spending for reporting and analysis. It can also be used in advanced settings such as expenditure aggregation in investment programs and main–sub-request relationships. |
88 | Integer | Useful life | Used to calculate the depreciation for the asset or expenditure item added in the expenditure grid. Before the 5.2 version, this property was often called “Tax depreciation”. |
89 | Money | Commitments | Displays the total value of commitment documents associated with the expenditure item. Useful for tracking obligated but not yet spent funds. |
90 | Code | Expense type | Indicates whether the expenditure is Capex or Opex. Used for financial classification and filtering. |
91 | Integer | Payment term | Specifies the number of days from invoice or commitment to expected payment. This is only used when the organization has enabled both accrual and cash-based expense reporting. |
Properties applicable to request type BUDGET
BUDGET properties store information about budget requests created within Capital Budgets in the Weissr Capital Budgeting module. These properties come with built-in logic for specific functions, such as automatically calculating or retrieving data based on system rules. The behavior of the system BUDGET properties is fixed and cannot be modified through configuration.
Learn more about system properties for budget requests here.