WFM Rest Break Compensation and Publishing Controls

WFM adds per-missed-rest-break compensation and condition-based schedule publishing controls, including location overrides.

·6 min read·11 views·NetSuite 2026.2·View Oracle Docs

Workforce Management (WFM) adds an allowance option for each missed required rest break, including a second break, alongside condition-based schedule publishing controls. Configure compensation through region-based wages, then review whether applicable conditions should block publishing, trigger a warning, or permit publishing without a warning, with overrides based on location.

What Changes for Missed Rest Break Compensation?

WFM supports a region-based wages allowance that applies for each missed required rest break, including a second required rest break. The update specifically identifies compensation configuration for multiple missed breaks, including those applicable in Minnesota, U.S.

The configuration decision is whether to apply the allowance for each missed break. When reviewing an arrangement that includes multiple required rest breaks, include the second required break in the configuration review rather than checking only a single-break scenario.

How do you configure the per-break allowance?

Go to Setup > Wage > Region Based Wages. When you create a condition, use the following configuration elements:

Configuration elementRequired selection or supported behavior
Condition typeSelect Allowance or Penalty.
Assigned ruleAssign a Break Requirement rule.
Per-break optionOn the allowance form, select the option to apply the allowance for each missed break.
Compensation basisUse a specified hourly rate or a percentage of the employee’s base hourly rate.

Configuration check: The per-break option is documented for an Allowance or Penalty condition with a Break Requirement rule. Check those prerequisites before looking for the option on the allowance form.

Review the compensation basis separately from the per-break selection. A specified hourly rate and a percentage of the employee’s base hourly rate are distinct choices. Confirm both the intended rate basis and whether the allowance should apply for each missed required break.

How Do Condition Rules Control Schedule Publishing?

The new Condition Rules section on the Schedule Validation Rules page determines what happens when a condition applies to a scheduled shift at publishing time. You can block publishing, show a warning before publishing, or allow publishing without a warning. Location-based overrides let you vary the applicable publishing behavior.

These controls address a different decision from compensation. Publishing validation governs whether an applicable shift can be published and whether a warning appears. The missed-break allowance setting governs compensation configuration. Review both rather than assuming that selecting per-break compensation establishes the desired publishing restriction.

Who can configure publishing settings?

The documented roles for configuring condition publishing settings are WFM Payroll HR and Administrator.

To update a condition’s publishing behavior:

  1. Open Workforce Management.
  2. Go to Setup > Validation Rules to open the Schedule Validation Rules page.
  3. In Condition Rules, select the region-based wage or region-based wage override agreement.
  4. Select the condition whose publishing rule and overrides you want to update.
  5. Click Change publishing rule.
  6. Set or revise the publishing rule.

By default, the validation rule applies to all WFM locations where the condition applies. Review that scope when deciding whether location-based overrides are needed. Do not assume a publishing rule is limited to one location simply because that location prompted the configuration change.

Publishing behaviorEffect when the condition applies to a scheduled shift
Block publishingPrevents publishing.
Warn before publishingDisplays a warning before publishing.
Allow without warningPermits publishing without a warning.

The table describes the supported outcomes; it does not prescribe which outcome to use for a particular regional wage arrangement.

How Do These Controls Differ from Standard Validation Rules?

WFM validation rules check staffing requirements and identify potential concerns with supported work restrictions. They cover employee numbers, ages, jobs, and proficiency levels. Distinguish the new condition publishing controls from the standard maximum and minimum rules when reviewing a scheduling issue.

Rule groupDocumented behavior
Maximum rulesPrevent publishing when configured limits are exceeded. Limits can include consecutive days worked, average hours per week, and maximum hours per day.
Minimum rulesEstablish a company-wide minimum shift length. Shorter shifts can trigger a publishing block or warning.
Condition rulesDetermine publishing behavior when a condition applies to a scheduled shift.

For troubleshooting, identify the relevant rule group before changing settings. A condition’s publishing choice and a standard maximum-hours limit address different checks. Review the rule responsible for the issue rather than treating condition publishing settings as a substitute for reviewing standard limits.

Which Condition Parameters Should You Review?

A condition requires one or more rules, and it applies if any of those rules apply. Review each rule independently: one narrowly configured rule does not make the entire condition narrow if another rule also qualifies.

The rule reference describes the following parameters. Use them where applicable; they are not a checklist of mandatory entries for every Break Requirement rule.

ParameterConfiguration considerations
Effective datesSet a start date, end date, or both for date-limited applicability. These values can usually remain blank.
Applicable daysSelect or clear individual days, or use Any day, Weekends, or Weekdays. Use the appropriate box for public-holiday-only conditions.
Time windowSet start and end times when the condition should apply only during particular hours.
Worked-time periodOptions include shift, day, week, fortnight, four-weekly period, and time worked since the last break.
Condition typesWhere applicable, select allowance or penalty, regular rate, penalty rate, overtime rate, or a combination.
Named condition and hours thresholdSelect a specific condition name if required, then enter the work-hour threshold after which the condition applies.
Shift boundariesWhere applicable, configure criteria based on shifts starting or finishing before or after a time.

What Should You Verify After Configuration?

Use representative cases to review the intended setup before operational use:

  • Compare one missed required break with multiple missed required breaks, including a second break.
  • Confirm the specified hourly-rate or base-rate-percentage basis.
  • Check the chosen publishing behavior when a condition applies to a scheduled shift.
  • Review relevant locations, including those intended to use overrides.
  • Review date, day, time-window, and hours-threshold boundaries where those parameters are configured.

These checks are configuration recommendations, not a statement that a particular setup satisfies regional legal requirements.

Who This Affects

  • Administrators and WFM Payroll HR: Configure condition publishing rules and review their location scope.
  • Scheduling teams: Review how publishing blocks, warnings, or publication without warnings fit the intended scheduling process.
  • Payroll and HR teams: Review per-missed-break compensation, the selected rate basis, and the intended regional wage arrangement.

Key Takeaways

  • WFM supports compensation configuration for each missed required rest break, including a second break.
  • The allowance option is available when an Allowance or Penalty condition has a Break Requirement rule.
  • Condition Rules support publishing blocks, warnings, or publication without warnings, with location-based overrides.
  • Publishing rules default to all WFM locations where the condition applies.
  • Review compensation settings and publishing controls separately, then check representative break and scheduling scenarios.

Frequently Asked Questions (4)

Where do I configure an allowance for each missed required break, and what prerequisites must be met?
Go to Setup > Wage > Region Based Wages and create a condition with an Allowance or Penalty type assigned to a Break Requirement rule. On the allowance form, select the option to apply the allowance for each missed break. The option supports compensation based on either a specified hourly rate or a percentage of the employee’s base hourly rate.
Can the per-break allowance cover a second missed required rest break?
Yes. WFM supports configuring the allowance for each missed required rest break, including a second required break. Review multiple-break scenarios when setting up the allowance, rather than checking only a single missed break.
What publishing outcomes can I set for a condition, and where do I configure them?
On the Schedule Validation Rules page, use the Condition Rules section to select the relevant agreement and condition, then click Change publishing rule. You can block publishing, show a warning before publishing, or allow publishing without a warning. WFM Payroll HR and Administrator roles can configure these settings.
Do condition publishing rules apply to every WFM location, or can I set location-specific behavior?
By default, a condition’s publishing rule applies to all WFM locations where that condition applies. Location-based overrides let you vary the behavior by location. Review the default scope and the relevant locations when configuring overrides.

Weekly Update History (1)

SuitePeople SuiteAppsadded

Added an entry for Workforce Management Updates on Schedule Validation and Missed Rest Break Setting.

View Oracle Docs
Source: Workforce Management Updates on Schedule Validation and Missed Rest Break Setting — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in SuitePeople

View all SuitePeople articles →

Also from NetSuite 2026.2

View all NetSuite 2026.2 changes →