Time Processing Rules Priority: Holiday Rules
Time & Labor processing rules can be set up within the
platform and are added to Company, Job, and Placement records to interpret Timesheet hours and calculate Payable and Billable Charges appropriately. Time can only be evaluated once, so it's important to understand how rules are applied to the time being evaluated and their processing order.The table order below is reflective of the priority order (top to bottom) that the rules are applied during time evaluation. Rules marked as Default are automatically applied to the processing pipeline and can not be configured.
To update your company's rule priority order, contact Bullhorn Support.
Time Processing Rule |
Category |
Description |
---|---|---|
Reversal (Default) |
Threshold |
Supports diff calculations.. This rule has the highest priority in the processing pipeline since it has to ensure a clean slate. After the reversal rule is executed, other rules will run normally as if the previous calculation never existed. |
Worked Holiday Threshold | Holidays | Time processing based on predefined holidays and one or more thresholds. |
Day of the Week Premium | Threshold | Time processing based on a certain day or multiple days of the week in order to give a candidate a premium based on days. |
Non-scheduled Workday | Threshold | Time processing based on a day of the week in order to allow a certain rate for days a candidate does not normally work. |
7th Day Threshold (Nth Day) | Threshold | Time processing based on a number of consecutive workdays. |
Daily Threshold | Threshold | Time processing within a single day for one or more thresholds, so time worked beyond each threshold is paid at a premium rate. |
Daily Min Wage Basis Threshold | Threshold | Time processing within a single day for one or more wage based thresholds; so if a candidate works over a certain amount of time at a certain regular pay rate, they are eligible for a premium rate beyond the threshold. |
Period Threshold | Threshold | Time processing based on a processing period and one or more thresholds. |
Orientation | Orientation | Time processing based on a new hire going through orientation. |
Worked Holiday | Holidays | Time processing based on predefined holidays. |
Period Based Quantity | PeriodBasedRate | Provides a set rate as a dollar type Earn Code for certain periods; for example, if a candidate that normally works a day shift is asked to work a night shift, they can be eligible for a bonus via a Period Based Quantity rule. |
Guaranteed Hours | Exempt | Time processing that is not strictly tied to the number of reported hours; so on a week or a day where the candidate works less than a certain amount, they are given the hours they were guaranteed. |
Low Census | Threshold |
This rule is specifically used by hospitals to call an employee off when there’s not enough demand. Most placements have a special clause that allows the hospital a certain number of call-offs per low census period. A low census call-off results in the employee getting paid but the hospital not getting billed or getting billed at a reduced bill rate. |
Expense Passthrough (Default) |
Expenses |
Supports expense processing. This is the only expense rule, as expenses do not need complex time and/or rate manipulation. |
Passthrough (Default) |
Threshold |
This rule consumes all remaining quantity entries. This rules happens later in processing to ensure hours are not depleted before other rules have the chance to process them. |
Shift Pricing (Default) |
System |
Applies to shift based pricing so special pay/bill rates can be applied to specific hours worked. This rule will always run as part of processing. However, if no Shifts are set at the Placement level, this rule will be skipped, as no entries will be identified with Shifts during preprocessing. |
FLSA Adjustment | FLSA | Provides Overtime calculations for candidates who work jobs with different rates. If there is a difference between the normal Overtime calculation and the FLSA Overtime calculation, then an adjustment is added. |
Negligible Quantity (Default) |
Threshold |
Identifies small quantities that are considered negligible or zero quantities and ensures they are ignored. |
Eliminator (Default) |
Threshold |
|
For holiday rules in particular, the Worked Holiday Threshold rule is applied before the Worked Holiday rule by default. This means that, by default, Holiday OT and DT are taken into account (if they are configured) through the Worked Holiday Threshold rule. The Worked Holiday rule catches any additional holiday time later in the priority list and exists to process holiday time if you have not set up Work Holiday Thresholds. The main difference between these two rules is the amount of Target Earn Codes that can be configured.
It's not expected that you would set up both the Worked Holiday Threshold Rule and the Worked Holiday Rule. If you need multiple Thresholds and multiple Target Earn Codes, use the Worked Holiday Threshold Rule. If you only need one Target Earn Code, use the Worked Holiday Rule.
Worked Holiday Threshold Rule
When an employee enters time under the Source Earn Code(s) (usually Regular) during a time period associated with the Holidays selected, then the time in excess Target Threshold hours gets attributed to the associated Target Earn Codes. You can choose multiple attributed Target Earn Codes for the Worked Holiday Threshold Rule.
The following example uses Exact as the Evaluation Method. For more information on other Evaluation Methods, see Advanced Holiday Rules.
An employee works 12 hours per day during a five day work week. The fourth day of that week is a Holiday. With the Worked Holiday Threshold Rule set up in the screenshot below, the employee will get 2 hours of Holiday DT, 2 hours of Holiday OT, and 8 hours of Holiday time.
Worked Holiday Rule
When an employee enters time against the Source Earn Code (usually Regular) during a time period associated with the holidays selected, then all hours are attributed under the Target Earn Code (typically Holiday). For the Worked Holiday Rule there is only one attributed Target Earn Code.
The following example uses Exact as the Evaluation Method. For more information on other Evaluation Methods, see Advanced Holiday Rules. The example below assumes the Worked Holiday Threshold Rule isn't configured.