You have set up a Flow to automatically assign a resource's manager to the approver field on Timecards. Users have reported that submitted Timecards…

The Certinia PSA application includes a specific configuration setting named Assign Project Manager To Timecard Approver within the Timecard Entry settings. When this checkbox is set to True, the system automatically assigns the Project Manager from the timecard's primary project as the approver. This built-in PSA configuration takes precedence over custom automation, such as the described Flow. Therefore, even though a Flow is designed to assign the resource's manager, this system-level setting overrides it, resulting in the timecard being routed to the Project Manager for approval.

A. PSA requires that only Project Managers can approve Timecards: This is incorrect. Certinia PSA's approval processes are flexible and can be configured to route to various individuals, including a resource's direct manager or a designated approver.

B. The process builder to assign the resource's manager is not active: The question specifies a Flow, not a Process Builder. Even if the automation were inactive, it wouldn't explain why the approver consistently defaults to the Project Manager; another mechanism must be responsible.

1. Certinia PSA Administration Guide: In the section "Timecard Entry Settings", the guide details the configuration options available for timecards. It explicitly describes the Assign Project Manager To Timecard Approver checkbox and its function: "If selected, the project manager on the project is assigned as the timecard approver." This confirms that the setting directly causes the behavior described in the question.

2. Certinia PSA Help Portal, "Timecard Approval Process": This documentation outlines the standard approval mechanisms. It clarifies that approvals can be managed through standard Salesforce approval processes, which can be customized to route to different approvers based on various criteria, disproving the notion that only Project Managers can approve timecards. The documentation implicitly supports that a specific configuration (like option C) would be needed to enforce a single approver type.