Comprehensive Capitalization Model: Troubleshooting Capitalization Issues

Edited

Capitalization requires multiple configurations to be correctly set up across projects, expense types, roles, rate cards, and financial periods. If capitalization amounts are not appearing as expected, it is likely that one or more required settings are missing or incorrectly configured.

This guide provides a structured approach to troubleshooting capitalization by identifying which configurations apply to non-resource forecasts, non-resource actuals, resource forecasts, and resource actuals.



Common Capitalization Issues

The table below outlines the key capitalization settings that must be checked for each type of capitalization. If capitalization is not applied to a financial record, use this table to identify potential missing or incorrect settings.

Setting

Non-Resource Forecast

Non-Resource Actual

Resource Forecast

Resource Actual

Project is eligible for capitalization

Project has an assigned methodology

Phase dates are correctly set

Implementation Date is correctly set (depending on the setting)

Capitalization profile is assigned

Allocation month / timesheet date is in a capitalizable phase

✅ (allocation month must be in a phase where the role is capitalizable)

✅ (timesheet date must be in a phase where the task is capitalizable)

Role is capitalizable in the phase

Task is capitalizable in the phase

Expense type is set as capitalizable

Rate card is set as capitalizable

Financial period is open for forecasts

Financial period is locked for actuals

Capitalization Lock Date is set



Step-by-Step Troubleshooting Guide

Use the table above to identify missing settings and follow these steps to resolve capitalization issues. For detailed configuration guidance, refer to the Comprehensive Capitalization Model: Non-Resource Cost Capitalization and Comprehensive Capitalization Model: Resource Cost Capitalization articles.

Step 1: Confirm Project Eligibility

Ensure Is Eligible to Capitalize Costs is set to ‘Yes’ in the Project Details page. If this is missing, no costs will be capitalized.

Step 2: Check Methodology and Phase Dates (for Resource Capitalization Only)

The project must have an assigned methodology, and phase dates must be correctly set to align with capitalizable roles and tasks.

Step 3: Check the Capitalization Profile (for Resource Forecasts Only)

Ensure the Capitalization Profile is assigned and that the resource role is capitalizable in the relevant phase.

Step 4: Check Capitalizable Phases (for Resource Capitalization Only)

  • For resource forecasts – The allocation month must be within a capitalizable phase where the role is capitalizable.

  • For resource actuals – The timesheet date must be within a capitalizable phase where the task is capitalizable.

Step 5: Check Capitalizable Tasks (for Resource Actuals Only)

Verify that the task booked in the timesheet is capitalizable in Methodologies, Phases & Tasks.

Step 6: Verify Rate Cards (for Resource Capitalization Only)

Ensure the resource’s rate card is capitalizable; otherwise, costs will default to OpEx.

Step 7: Check Expense Types

Verify that the expense type is set as capitalizable with a capitalization percentage greater than 0% in Financial Administration > Expense Types.

Step 8: Validate Financial Periods

  • Forecasts – Must be in an open financial period.

  • Actuals – Must be in a locked financial period.

Step 9: Verify Capitalization Lock Date and Implementation Date or End Date

  • Capitalization Lock Date – Must be set correctly; financial records before this date are locked.

  • Implementation Date or End date (Depending on configuration) – Must be set; records beyond this date are treated as OpEx.

Step 10: Ensure Non-Resource Actuals have been uploaded using the Financial Actuals Bulk Edit or Non-Resource Actuals & Forecast bulk edit file.

Manually entered actuals are not eligible for capitalization, as these records automatically default to a 0% capitalization percentage.



Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.