Priority Hierarchy (Override Logic)

 

The most specifically stored hourly rate in the system always overrides all more general information. The following order applies (from highest to lowest priority):

 

1. Project  2. Customer  3. Employee  4. Activity

 

Practical Examples for Illustration

 

• Example 1: Project Hourly Rate Overrides All

You set up hourly rates in the project conditions. Even though hourly rates are also stored for the customer, employees, and activities, only the hourly rate from the project applies. The project hourly rate overrides all other levels.

 

• Example 2: Customer Hourly Rate Overrides Employee & Activities

An individual (e.g., discounted) hourly rate is stored for a customer. No specific project hourly rate exists. In this case, the customer hourly rate applies; the information for employees and activities is ignored.

 

• Example 3: Employee Hourly Rate Overrides Activities

An employee is assigned their own hourly rate. No deviations are defined at either project or customer level. The employee's hourly rate overrides the standard hourly rate of the selected activity.

---

Overview of Hierarchy Levels

 

Priority	Level	Description & Behavior
1 (Highest)	Project	Overrides hourly rates for customer, employee, and activity.
2	Customer	Applies if no project hourly rate is defined; overrides employee and activity.
3	Employee	Applies if neither project nor customer hourly rates are available; overrides the activity.
4 (Base)	Activity	Serves as a general standard hourly rate, unless a value is defined at a higher level.

---