UKG Pro WFM Pay Rule and Work Rule Configuration Checklist

Visit Dignity Do Right Thing

To configure UKG Pro Workforce Management (formerly UKG Dimensions) pay rules and work rules well, start from written pay policy, map each policy to a paycode, build the work rule building blocks and combination rules, then prove every rule with timecard test cases before payroll sees a single result. The order you work in and the testing matter more than any one setting.

This checklist is for payroll managers, timekeeping admins and implementation leads who own pay accuracy, whether you're building rules for the first time or cleaning up years of changes.

Key takeaways

  • Pay rules control how time is processed for each employee; work rules apply specific processing to shifts. Keep that split clear in your design.
  • Write the policy matrix first. Every overtime, differential and premium needs an owner, a trigger and a paycode before anyone opens setup.
  • Combination rules decide what happens when overtime, zones, schedule deviations and rest rules overlap. That's where the expensive errors usually hide.
  • The FLSA sets the floor: at least time and one half the regular rate for hours over 40 in a fixed 168-hour workweek. State law and contracts can add more.
  • Test with real edge-case timecards and sign off on expected versus actual hours, not screenshots of settings.

What is the difference between pay rules and work rules in UKG Pro WFM?

UKG's product help draws the line clearly. Pay rules "control how time and attendance information is processed for each employee," while work rules "are combinations of work rule building blocks that apply specific pay rules to shifts." Pay rule building blocks stay constant within a payroll policy. Work rules are where shift-level behavior lives.

In practice, an employee gets one pay rule that reflects their pay population, for example nonexempt hourly in one state under one union contract. The work rules attached to that pay rule decide how a given shift is paid. A charge nurse who works a regular day shift and then picks up an on-call shift may hit two different work rules in the same week under one pay rule. For a closer look at how this plays out across several sites, see our guide to UKG union contract and overtime rules for multi-site food plants.

The design mistake we see most often is one pay rule per department, because that's how the org chart looks. Pay rules should follow pay policy, not reporting lines. If two departments share overtime, rounding and holiday treatment, they can share a pay rule, which means less to maintain and less to test every time something changes.

Which building blocks do you need to configure?

Use this table as your inventory. UKG's help describes combination rules as the place where overtime rules, zones, schedule deviations and rest-between-shift rules interact. Confirm exact names and options in your own tenant, since setup screens vary by release and by what your organization licensed.

ComponentWhat it doesQuestions to answer before configuring
PaycodesOrganize time or money employees earn and identify spans of time for payrollWhich payroll earning code does each paycode map to? Does it count toward overtime?
Punch roundRounds punches and enforces shift start and end timesWhat interval, and does it average out for employees over time?
OvertimesWeekly, daily or consecutive-day overtime thresholdsWhich jurisdictions add daily overtime? Which paycodes count toward the limit?
ZonesTime intervals such as evenings or weekends that earn differentialsDoes the differential cover the whole shift or only minutes inside the zone?
Schedule deviationsTreatment of work before or after schedule, or unscheduled shiftsIs early or late work paid at a premium, or just flagged?
Rest between shiftsPremiums for work during an expected rest periodDoes any contract or local law require a rest premium?
Majority rulesApply one hour type to a shift that qualifies for several zonesShould a mostly overnight shift be paid entirely at the night rate?
Combination rules and paycode distributionsDecide how overlapping conditions are paid and which time counts toward overtimeWhen overtime and a weekend zone overlap, which paycode wins?

How should you build the policy matrix before configuration?

A policy matrix is a spreadsheet with one row per pay population and one column per rule. It becomes the single source of truth for your implementation partner, payroll and auditors. If a rule isn't in the matrix, it shouldn't be in the tenant.

Columns that belong in the matrix

  • Pay population name and who it covers: FLSA status, state, union, job family.
  • Workweek start day and time. This has to match the workweek you use for FLSA purposes.
  • Rounding interval and grace periods, with a reference to the policy document.
  • Overtime thresholds: weekly, daily, seventh day, and which paycodes count toward each.
  • Differentials and zones, with rates and whether they're flat amounts or percentages.
  • Meal break deduction rules and how a missed or short break is handled.
  • Holiday eligibility and the holiday-worked premium.
  • Target payroll earning code for every paycode.

Common matrix mistakes

  • Leaving "counts toward overtime" blank for PTO, holiday and on-call paycodes. Every paycode needs an explicit yes or no.
  • Treating automatic meal deductions as harmless. If employees work through the break, that time is still hours worked.
  • Copying a rule from another population "for now" without documenting why. Six months later nobody remembers.

If your time data feeds an external payroll, the earning code column matters twice. Our guide on integrating UKG Pro WFM with Workday Payroll walks through the mapping side.

How do FLSA overtime and regular rate rules affect configuration?

The Department of Labor's FLSA wages page says covered nonexempt employees must get overtime for hours over 40 per workweek at not less than one and one-half times the regular rate, and defines a workweek as a fixed, regularly recurring period of 168 hours. Two configuration consequences follow.

  1. Your overtime rule must use a fixed workweek. You can't average hours across a biweekly pay period under federal law, even if payroll runs biweekly.
  2. Overtime is based on the regular rate, not the base rate. 29 CFR 778.207(b) says the Act requires nightshift differentials to be included in the regular rate, whether they're a percentage or a flat amount per hour. If your zones pay a differential, weeks with overtime need a regular rate calculation, and someone has to decide whether UKG Pro WFM or the payroll engine does it.

The DOL's Fact Sheet #56A lists payments that can be excluded from the regular rate, including paid vacation, holiday, sick leave and other paid time off. That's why the "counts toward overtime" setting on PTO paycodes is a policy decision, not a technical default. Federal law doesn't require counting PTO toward the 40, but some contracts and employers choose to. We cover the trade-offs in whether PTO hours count toward weekly overtime.

How do you test pay rules and work rules before go-live?

Configuration review catches typos. Only timecard testing catches logic errors. Build a test library where each case has a scenario, the punches, the expected paycode totals and the actual result. Pay rule testing should sit inside your wider UKG go-live readiness checklist, with its own exit criteria.

Minimum test cases

  • A 40-hour week with no exceptions (baseline).
  • A week that crosses 40 hours on the last day of the workweek.
  • A shift that spans midnight on the workweek boundary.
  • An overnight shift that touches two zones, to test majority rules.
  • Overtime that lands inside a weekend zone, to test combination rules.
  • An early punch inside the grace period and one outside it.
  • A missed meal punch and a short meal.
  • Holiday worked, holiday not worked, and PTO in an overtime week.
  • A midweek transfer to a job with a different work rule.
  • A daylight saving time change week.

Have payroll, not the configuration team, own the expected results. When the person who built the rule also writes the expected answer, the test confirms the build rather than the policy. Trace each failure to a root cause: wrong policy, wrong configuration or wrong expectation.

Rounding deserves its own cases. Under 29 CFR 785.48(b), rounding to the nearest five minutes, tenth or quarter hour is accepted only if it averages out so employees are fully paid for the time they actually work. Run a sample of real punches through your proposed rule and compare rounded to actual minutes. Rules that live at the clock, such as overtime prompts and early punch restrictions, need the same scrutiny; see overtime, PTO and shift bidding rules at the time clock. Our article on stopping time theft in UKG Ready, Dimensions and Pro covers the punch behavior side.

Frequently asked questions

Can one employee have more than one work rule in UKG Pro WFM?

Yes. An employee has one pay rule, but work rules apply to shifts, so a single employee can have shifts paid under different work rules in the same week. That's common for people who cover on-call, training or a second job. Test transfers carefully, because overtime still has to be calculated across the whole workweek, not per job.

Should rounding be configured in UKG or at the time clock?

Pick one place and document it. Rounding once at the device and again in the punch round building block creates drift that's hard to audit and hard to explain. Wherever you put it, test real punch samples to confirm the rule averages out and doesn't consistently reduce paid time for employees.

Do shift differentials change the overtime rate?

Usually, yes. 29 CFR 778.207(b) says nightshift differentials are included in the regular rate, so weeks with both differentials and overtime typically need a weighted regular rate rather than one and a half times base pay. Decide whether UKG Pro WFM or payroll calculates it, then build a test case that proves the result.

What to do next

  1. Build or refresh your policy matrix and have payroll and legal sign it.
  2. Inventory current pay rules and work rules, and retire any that no longer map to a policy.
  3. Write expected results for the ten minimum test cases and run them in a non-production tenant.
  4. Decide and document where rounding and the regular rate calculation happen, then set change control so every future rule edit runs through the same tests.

Sources

Last reviewed: October 2026.

Comments

Popular Posts

Why Workday Onboarding Breaks Down for Frontline Employees

Interview Tips for Beginners: A Step-by-Step Prep Plan

How to Improve the Customer Experience (CX)

How to Market Your Handyman Services to Small Business Owners

Are Biometrics Better Than Passwords? What NIST Says

Are Mobile Apps Tracking Your Every Move? How to Check

Predictive Scheduling Laws: Where They Apply and How to Comply

Dollar General Store Walkout: Lessons for Retail HR

Boss Retaliation and False Accusations: Protect Yourself

How Do I Log In and Sign In to Workday HCM