Feedback request: Project–Branch entry for Time Cards and Payroll scenarios

Dear community!

We always listen to your feedback and it is very helpful and valuable.

I’m glad to share that in 26R1 we are introducing improvements to Project–Branch defaulting in Purchasing and AP documents. More details will be available in the release notes soon.

We are continuing to move in this direction. At the moment, our main focus is on Employee Time Cards and Employee Time Activities in combination with Payroll and corresponding Project transactions and Journal transactions.

We would really appreciate your feedback, especially around real-life payroll and time entry scenarios. In particular:

1. Do you have cases where employees enter time for projects that belong to a different branch than the employee has, and this creates issues after time is released or payroll is processed?
   1. What is the semantic of the branches of such clients?
   2. Which payroll (built-in or external) is used?
   3. What branch do your customers expect to see in the project expense and employee liability and why?
   4. Which workarounds currently is used?
   5. Other additional information that can be useful in that case.
2. Are there cases where posting of project labor costs to the employee’s branch is required or preferred, even when a project belongs to a different branch? Describe them in the same structure as 1st question please.

Additionally, if you have encountered project–branch challenges in the following forms:

• Expense Receipts;
• Expense Claims;
• Project Transactions (manually created);
• Journal Transactions (manually created),

please feel free to share those scenarios as well - we will definitely take them into consideration for future improvements.