Hourly rate fields are available on many of the setup tables in Time Portal. These rates are available in different areas to ensure that multiple rate scenarios are possible. They are also there to help reduce data entry and maintenance. Time Portal uses a weighted hierarchy to determine which hourly rates in the system get applied to an employee. Listed below are the current levels of Hourly Rates. When a worker clocks in, the system will look for the appropriate hourly rate to use for that worker. To do this, it begins with the Employee and works it way up to the company. It will check each level, traveling up the ladder of setup tables and will use the first rate that it finds. That rate will get stamped onto the Time Sheet Record when the record is created. This will store the rate data historically in case rates change in the future.
Note: Rates that have already been stamped on a Time Sheet Record must be changed on the edit screen within the Time Sheet. Updating rates in the setup tables will not update time sheet records. This is to prevent overriding historical data.
Let's look at some examples of how we can setup our rates and how they would get applied.
- Company
- Worker Contract
- Crew
- Job
- Employee
Rate Examples
Example 1: The most basic rate setup is to place your base hourly rate/minimum wage on your company. In this example, we have entered $10.00 as our base rate. This rate will get applied to every employee that uses Time Portal. When a worker clocks in, the system will travel up the ladder of setup tables to find the first rate available. Since we only have one rate applied at the company level, the system would end up at the company level and using $10.00.
Example 2: In this example, we have an employee John that gets paid at a higher wage than the rest of our employees because he is a crew manager. To set this up, we add his hourly rate of $15.00 to his employee record. When John clocks in, the system will begin at his employee record and work its way up the ladder but, this time the first rate that it hits is on John's employee record. The system will then use the employee rate of $15.00. All other employees would get $10.00 because their employee records do not have a rate.
Example 3: In this example, we have placed an hourly rate of $11.00 on John's crew. We have done this because John's crew is working in a different state and that state's minimum wage is higher than our home state. When John clocks in, He receives $15.00 an hour because that is the first rate the system hits for him. When any of the workers assigned to John's crew clocks in, they receive $11.00 an hour because going up the ladder from their employee records, the Crew rate is the first one reached. All other employees in the company would receive $10.00.
Example 4: Time Portal's Jobs have the ability to have rates as well. If we wanted to assign a specific hourly rate to be paid by Job, we could add a rate on the Job and the system would work it's way up the later as normal. Jobs also have a capability that the other levels in the latter do not. A Job can be made to "Have Precedence" over all other hourly rates. On the Job record, there is a flag called Has Precedence that can be turned on. When this setting is turned on, it moves that particular Job record down the ladder below Employee making it the first rate the system encounters when workers are clocked into that Job. An example where this may be useful is when you may be paying a lower rate for a particular activity such as Travel despite a workers typical hourly rate. In this example, even when John clocks into the Job Travel, he would get paid at the lower Travel rate because we have made that Job have precedence over his employee record.
Comments
0 comments
Please sign in to leave a comment.