Rate Model Not Applied When Time Is Submitted via Assigned To on Project Tasks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10 hours ago
Users can submit timecards under the following two conditions:
A resource assignment exists for the user against the Project or Project Task.
The user is either Assigned To or included in the Additional Assignee List on the Project Task.
My concern is specifically with condition #2. The current flow is as follows:
The Rate Model is populated on the Project.
A user is assigned to a Project Task via the Planning section in Project Workspace.
The user is able to submit a timecard for that Project Task.
When the timecard is submitted, the generated expense line uses a default rate.
The rate is calculated correctly only when a resource assignment exists for the user on the task prior to time submission.
It is unclear why assigning a user via the Assigned To field (or Additional Assignee List) does not cause the system to apply the Project’s Rate Model during rate calculation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi Buddy,
Being Assigned To a project task or added as an Additional Assignee only allows a user to log time. It does not make them a planned resource from a financial perspective. Rate calculation is tied to resource assignments, not task assignment.
When a resource assignment exists, ServiceNow knows which Rate Model to use and applies it correctly. When there’s no resource assignment, the system has no rate context, so it falls back to the default rate, even if a rate model is defined on the project.
So in simple terms:
Assigned To / Additional Assignee = permission to work and submit time
Resource Assignment = drives costing and rate calculation
That’s why the rate only comes out correctly when the resource assignment exists before the timecard is submitted.
Most teams handle this by either requiring resource assignments for anyone who will submit time, or by adding automation to create a resource assignment when someone is added to a task. It’s not a defect—just a separation between task ownership and financial planning in PPM.
@Pranav_Thanedar - Please mark Accepted Solution and Thumbs Up if you found Helpful 🙂
