**NOTE*** The documentation for project rollup properties is WRONG. They need to be true for all 3 if you are submitting time/expense for project task and want to roll up to the project.
From servicenow
After reviewing both the documented behavior and the results observed in your instance, the outcome you are seeing is consistent with current system behavior: when glide.cost_mgmt.process_task_top_task is set to false, (THIS NEEDS TO BE TRUE)
the system creates only the task‑level expense line and does not generate a rolled‑up project‑level expense line. This explains why rollup does not occur under that configuration in your testing.
In other words, while documentation states that this property should be false for rollup, practical testing confirms that disabling top‑task expense processing prevents the project‑level rollup from being created. The rollup engine relies on that processing to generate the project‑level expense line.
Based on this, the behavior you are seeing is expected given the current configuration, and the documentation does not fully reflect this dependency. Using a configuration where top‑task expense processing remains enabled is required if project‑level expense rollup is expected.
With this clarification, there is no platform defect identified; this is a configuration and documentation mismatch.
