| Note: From October 1st, 2025, we introduced new plans that better reflect how our customers use Deputy: Lite, Core, and Pro. If you're an existing customer, look out for an email with all the details you’ll need. Learn more about the new plans and what this change means for you. |
This article discusses the Missed Break Allowance pay rule calculations as part of Deputy's Pay Rate Builder.
Before you begin, please read about adding and editing pay rule calculations
- Description
- Example use case
- Supported rule types
- Outputs
- Configurable parameters (standard)
- Configurable parameters (advanced)
Description
The Missed Break Allowance pay calculation rule is used to pay a single hour or unit when a team member has not taken a break before a set period of time in their shift.
Example use case
A team member must be paid an allowance if they have not taken a meal break of at least 30 minutes within the first 5 hours of their shift.
In this case, you can set the following parameters:
- Shift Length Threshold: 5 hours (the shift must be longer than 5 hours).
- Break type: Unpaid (to specify meal breaks).
- Break Length: 30 minutes (break must be at least 30 minutes long).
- Shift Period Threshold: Start 0, End 5 hours.
This means a team member must start their break no later than 4 hours and 30 minutes into their shift and take a 30-minute break to complete the break by the 5-hour mark. If the intent is simply that the break must have started by a particular time, increase the threshold accordingly.
Supported rule types
rThis rule is only available as a shift loading. This means it will be paid as an additional payment on top of other calculated hours, such as ordinary time and overtime.
Outputs
This rule will return one hour or one unit of pay.
Configurable parameters (standard)
These are the standard fields you can configure in the Shift Loading pay rule calculation.
| Name | Defines the name of the pay rule |
| Shift Length Threshold | The minimum length of the shift required for the rule to trigger. |
| Break Type | It can be paid, unpaid, or any. If any, either type of break is considered. |
| Break Length | The minimum length of break required for this rule not to be triggered |
| Shift Period Threshold | Sets a start and end time for when the break length must be completed, measured from the start of the shift |
| Export code | Defines if this pay rule should be exported to payroll. If yes, they can also specify a code for the rule. |
| Days of the week this calculation applies |
Defines which days of the week this rule applies to. For example, if Saturday and Sunday are selected, this rule calculates only the parts of the timesheet that overlap Saturday and Sunday. |
| Time of the day this calculation applies |
Defines which part of the day this rule applies to. By default, this is all day. However, it can be used to define a portion of a day (e.g., a defined night shift, such as 6 pm-6 am). If this is done, only those parts of the timesheet that overlap with this are calculated. |
| Public holiday |
Select whether this pay rule applies:
|
| Areas |
The rule applies to all areas by default. However, you can apply it only when a timesheet is worked in a specific area/location.
|
| Classifications | If you have set up classifications within the pay rate, you can select if a rule only applies to a particular classification. |
Configurable parameters (advanced):
These are the advanced fields you can configure in the Consecutive days worked pay rule calculation
| Apply to Training |
This pay rule will only be applied to team members with the selected Training record on their employee profile. Read more at Managing Training Records. |
|
Does this apply to a specific date |
If set as Yes, the pay rule will only apply on the defined date, assuming the date falls on the previously defined allowable day and time above. |
| Apply pay rule to unscheduled shifts |
Defines how the pay rule interacts with scheduled and unscheduled shifts:
|
| Pay portion rule |
Generally, an hourly rate will be assigned according to the exact hours that are matched, however, it is possible to enforce an hourly rate for a full shift even if it only matches a minor or major portion of that shift. Deputy recommends using the Exact Hours option in most cases. |
| Rate type |
Categorizes the pay rule as Overtime, Ordinary, Penalty or Non-Payable time. These are used to define time worked for other calculation types (for example, Periodic Overtime counts Ordinary and some penalty hours towards it). |
| Rate tag |
A custom value that can be applied to the timesheets. Deputy recommends only using this if advised by your implementation consultant. |
|
Pay once per day |
If set as Yes, this pay rule may only apply once per day. If No, it may apply to multiple timesheets on a given day. |
| Clock in and out requirements |
For this rule to apply, the team member must clock in and clock out within the defined periods. By default this is midnight to midnight (ie. any time is allowed.) |
| Apply this pay rule for custom timesheet fields |
With this, the rule will only apply if particular values are selected in the custom timesheet field questions. Note that only List and Boolean questions are available. Read more at Creating custom timesheet fields for shift questions. |
| Apply this pay rule when shift custom fields |
This rule will only apply if particular values are selected in the custom shift fields in the schedule. Note that only List and Boolean questions are available. Read more at: Creating custom shift fields |
| Custom Employee Fields |
This rule will only apply if particular values are selected in the employee’s custom fields (for example, job position). Note that only List and Boolean fields are available. (Available to customers on most Deputy plans). Read more about setting up custom fields for team members. |