New Zealand calls it Mondayisation, the UK calls it a substitute bank holiday, Canada calls it holiday pay in lieu, and the US calls it an observed holiday. Four names, four rules, and the same manual-check problem for global UKG Pro WFM deployments.
Table of Contents
When a public holiday lands on a Saturday or Sunday, most employees who weren’t scheduled to work that day lose it, unless the law says otherwise. A surprising number of countries have built some version of a “give the day back” rule into their labor law. New Zealand calls it Mondayisation. The UK calls it a substitute bank holiday. Canada calls it holiday pay in lieu, depending on the province. The US calls it an observed holiday, mostly by convention rather than law. Four names, four legal mechanisms, and for any organization running UKG Pro WFM or UKG Ready in more than one of these countries, the same payroll problem.
Workbridge
UKG Personalization
Missed punches dropped from 30% to under 5% — without touching UKG's core.
The problem isn’t that UKG can’t model these rules. It’s that every one of them depends on information the system only has part of: who was actually rostered to work that weekend, who’s covered by a collective agreement or enterprise agreement that pays more than the legal minimum, and whose timecard a manager corrected by hand after the automated interface already ran. Miss any one of those and someone ends up underpaid for a holiday they lost, or paid twice for a day they didn’t.
Workbridge
UKG Personalization
Migrating UKG Ready to Pro? Your customizations come with you. No rebuilds.
CloudApper’s AI TimeClock exists for that gap. Instead of trusting an overnight batch job to catch every edge case, it puts a confirmation step at the moments that actually matter: clock-in, timecard approval, and manager review. A casual employee whose eligibility depends on an irregular roster, a manager who edited a shift after the interface already calculated holiday pay, a union contract that pays above the statutory floor. Those are exactly the cases where an automated interface guesses and CloudApper’s AI TimeClock asks instead.
For payroll teams running UKG across several countries, that matters more than it sounds. The substitution logic doesn’t need to be perfect out of the box. It needs a layer that catches what the interface misses before it turns into a correction three pay cycles later, when nobody remembers why.
Four countries, four different rules
New Zealand: Mondayisation
Under the Holidays Act 2003, as amended in 2013, a public holiday that falls on a weekend is “Mondayised” for employees who wouldn’t otherwise have worked that day. The day’s entitlement moves to the following Monday, and for the holidays clustered around Christmas and New Year, to the Tuesday if both weekend days are affected. An employee who was actually rostered to work on the original date still gets paid for that date; it’s the employee who wasn’t rostered who picks up the moved day instead. That distinction between “rostered” and “not rostered” is where most of the manual checking happens, because rosters change and the system has to know about the change before it calculates pay.
Workbridge
UKG Personalization
50+ HR gaps UKG leaves open. WorkBridge closes them in days, not months.
One customer described their first year running the interface this way:
“For us it ran relatively smoothly, compared with previous years where we had to manually check roughly 7,000 employees. We still need to do manual checks for our casual employees, where managers have made changes after the interface has been run, and where our Collective Agreements pay over and above the legislation.”
Employment New Zealand publishes official guidance on what happens when a public holiday falls on a weekend.
United Kingdom: substitute bank holidays
The UK doesn’t apply Mondayisation to every bank holiday, but it does for the ones that matter most: when Christmas Day, Boxing Day, or New Year’s Day falls on a weekend, the government designates a substitute weekday, usually the next available working day. Whether an individual employee actually gets that day off depends on their contract rather than the holiday calendar itself, since UK law doesn’t guarantee paid leave on bank holidays at all; it’s an employer-by-employer entitlement set out in the contract. That means two employees at two different UK companies can have completely different substitute-day entitlements for the exact same calendar year, which is exactly the kind of detail a global payroll configuration can miss if it assumes one UK-wide rule.
Canada: a patchwork by province
Canada has no single federal holiday-substitution rule. Each province’s employment standards legislation sets its own approach, and most require either a substitute day off or a premium pay rate when a statutory holiday falls on a day an employee wasn’t scheduled to work. Ontario, Alberta, and British Columbia each define eligibility and the substitute mechanism slightly differently, and provincially regulated industries can have their own exceptions layered on top of the general rule. We’ve covered how this plays out in practice for Ontario statutory holiday pay automation in UKG Ready, where the same rostering and eligibility questions show up again.
United States: observed holidays, by convention
The US is the outlier. There’s no federal law requiring private employers to recognize any holiday, paid or unpaid, so there’s also no federal law requiring a substitute day when one falls on a weekend. What exists instead is convention: the federal government and a large share of private employers observe a holiday that falls on a Saturday on the preceding Friday, and one that falls on a Sunday on the following Monday. It’s a widely followed practice, not a statutory entitlement, which means it’s entirely up to each employer’s policy, and that policy has to be configured explicitly rather than assumed.
Europe: no shared standard at all
Across the EU and UK-adjacent markets, there’s no bloc-wide rule comparable to Mondayisation. Public holiday entitlement is set at the national level, and in several countries, a holiday that falls on a weekend simply lapses with no substitute day and no extra pay, while others grant compensation through national law or sector-level collective agreements. An organization running UKG Pro WFM across Germany, France, and the Netherlands can have three different answers to the same calendar question, and the collective agreement layer on top of national law is often where the real complexity sits.
The same three gaps, no matter the country
Underneath the different names and different laws, the manual-check burden tends to come from the same three places:
- Roster and eligibility exceptions. Casual, part-time, and irregular-schedule employees are the hardest group for any automated interface to classify correctly, because their eligibility for a substitute day depends on whether they were actually rostered for the original date, and rosters change constantly.
- Late manager corrections. When a manager adjusts a shift after the holiday-pay interface has already run its calculation, that change doesn’t retroactively trigger a recalculation on its own. Someone has to notice the correction and re-check the pay outcome.
- Collective and enterprise agreements that pay above the legal minimum. Statutory rules set a floor, not a ceiling, and agreements that pay more than the law requires need their own configuration layer that the base holiday-substitution logic doesn’t automatically know about.
We’ve written about how to automate work rule transfers in UKG Pro WFM, and the same configuration discipline applies to collective agreement rules that pay more than the law requires: the more precisely the exception is defined up front, the less a payroll team has to catch by hand after the fact.
A manual check isn’t a sign the system failed
It’s tempting to read “we still do manual checks” as evidence that the automation isn’t working. It’s closer to the opposite. The interface is built to apply a rule consistently across thousands of employees at once, which is exactly what it’s good at. It isn’t built to know that a particular manager swapped two people’s shifts last Tuesday, or that a particular collective agreement was renegotiated last quarter to pay a premium the legislation doesn’t require. That information lives with people, not in the base calculation, and no amount of tuning the interface will change that.
What changes the outcome is having a layer that asks the right question at the right moment instead of assuming the batch job already caught it, which is what CloudApper’s AI TimeClock is built to do.
Frequently asked questions
What happens when a public holiday falls on a weekend?
It depends on the country. Many give employees the day back on a different date: New Zealand moves it to the following Monday under a process called Mondayisation, the UK designates a substitute bank holiday for some holidays, and Canadian provinces require a substitute day off or extra pay. Others, including much of Europe, simply let the day lapse with no substitute and no extra pay.
Do all countries require employers to give a substitute day for a weekend holiday?
No. It comes down to local law and convention. New Zealand, the UK, and most Canadian provinces have legal requirements to shift the day or pay a premium. The US relies on employer convention rather than law, observing the nearest weekday. Many European countries have no substitute-day rule at all, and it’s left to national law or collective agreements to decide.
Does UKG Pro WFM handle public holiday substitution automatically?
UKG Pro WFM and UKG Ready can calculate holiday substitution rules, but the calculation depends on accurate roster, eligibility, and agreement data. Casual employees, late manager corrections, and collective agreements that pay above the legal minimum are the cases most likely to need a manual review after the automated interface runs.
What should payroll teams check manually after the interface runs?
The three most common gaps are casual or irregular-schedule employees whose eligibility depends on whether they were actually rostered, any shift changes a manager made after the interface already calculated pay, and collective or enterprise agreements that pay more than the statutory minimum.
If your UKG deployment spans more than one of these countries, the rules will never fully line up from one to the next. The manual-check layer is what keeps the differences from turning into payroll errors.
October 16, 2026
UKG Pro Position Management at a Food Producer: Who Sets the Defaults When 75 Employees Change Jobs Every Week
A large food producer on UKG Pro handles about 75 internal transfers a week. CloudApper automates the position defaults behind each move, including comp codes, cost centers, standard hours and union codes, through the UKG Pro API, and HR now owns and updates the rules without a database request.
October 15, 2026
Health and Welfare Pay for Military Base Stores: How a Retailer Made Every H&W Hour Traceable in UKG
A national specialty retailer with stores on US military installations moved health and welfare pay out of spreadsheets. CloudApper now applies the 40-hour weekly cap, multi-store proration and employer cost recovery against UKG time data, posting H&W pay codes to each timecard with a trail back to the hours.
September 30, 2026
When Your Best Candidates Already Worked for You: How a 50,000-Employee Home Care Organization Automated Rehire Campaigns and Geographic Filtering in UKG Pro
A 50,000-employee home health care organization extended UKG Pro Recruiting with CloudApper AI Recruiter to add geographic zip-code filtering, automated rehire outreach campaigns for former employees, and blind-ranking — reducing recruiter workload and improving hiring quality at scale.
September 29, 2026
If Your HR Events Aren’t in Slack, They Don’t Exist: How a 260-Person HR Tech Company Connected UKG Ready to Where Work Actually Happens
A 260-person HR tech company with a Slack-first culture connected UKG Ready lifecycle events to Slack using CloudApper iPaaS — so new hires, promotions, and PTO approvals appear where the organization already pays attention.
