One Workday, Many Rulebooks: Getting Global Absence Right Before You Build
Most HR teams know their absence policies well. The harder part is tracking and administering time away from work when employees sit in different jurisdictions. A company with staff in Ohio, Ontario, and London is working with three sets of rules for vacation, sick time and protected leave, and those rules rarely line up neatly.
Entitlements may accrue monthly in one place and by hours worked in another. Years of service change accrual rates in some locations and not others. Carryover, expiration, documentation and payroll treatment can all differ, sometimes within the same country. Moving all of that into Workday raises a practical question HR leaders need to answer before the project starts:
How do you give every employee one consistent way to request and track time away, while still meeting the rules that apply where they work?
The answer depends on decisions made well before anyone configures a plan. Below are the areas where global absence deployments most often go wrong, and what to think about before yours begins.
Time Off and Leave Behave Differently in Workday
You already know the difference between a vacation day and a medical leave. What matters in a global deployment is that Workday handles them differently. Time off is usually a short time away from work and managed through time off plans. Leaves of absence change the worker’s status, can pause or alter accruals and benefits, and require a return-from-leave process.
Across countries, the line between the two isn’t always drawn in the same place. Extended sick time may be time off in one country and a leave in another. Parental leave may be partly paid by the employer, partly by a government program or partly unpaid. Each answer affects who administers the absence, what the employee sees, how the worker’s status changes and what payroll receives.
That is why this needs to be settled early in a global deployment. If the team decides absence by absence during configuration, the same type of absence can end up built three different ways in three countries, with three different owners. Agreeing up front on how the organization will manage absence from request through approval, pay, leave administration and return to work gives the design team one consistent approach to apply in every country.
Standardize the Structure, Not the Rules
A common mistake is assuming a global standard means every country uses the same absence plan. The countries rarely allow it.
In Workday, an absence plan is assembled from several parts: eligibility rules that decide who gets the plan, accrual rules that decide how time is earned, limits and carryover rules, validations that stop invalid requests, and business processes that route approvals. A global design keeps the structure of those parts consistent, while letting the values inside them change by location.
The differences go well beyond the number of days off:
- United States: No federal law requires paid vacation, so entitlement is set by company policy. Paid sick leave is different. A growing number of states and cities require it, each with its own accrual rate, cap, carryover rule and permitted uses. FMLA adds job-protected leave with its own eligibility tests.
- Canada: Vacation entitlement and vacation pay are set by each province, or by the Canada Labour Code for federally regulated employers. In Ontario, employees earn two weeks of vacation after a year of employment and three weeks after five years, so service dates drive accrual.
- United Kingdom: Statutory annual leave is 5.6 weeks a year. For irregular-hours and part-year workers, holiday can accrue at 12.07 percent of hours worked, so two employees in the same UK office may need different accrual methods.
- France: Paid leave accrues at 2.5 working days per month, and the leave year often follows a reference period rather than the calendar year. Employees can also continue to accrue paid leave during certain periods of sick leave.
- Germany: The statutory minimum is 24 working days based on a six-day week, or 20 days for a five-day week, and collective agreements often grant more. Unused leave can generally carry over only in limited circumstances, and employers are expected to notify employees before leave is forfeited.
From a List of Local Rules to a Design You Can Build
Lists like this are where many deployments start, and where many get into trouble. A list of country rules tells you what someone believes is required. It doesn’t tell you where the rule came from, which employees it covers or who can change it.
On a global absence deployment, the design team has to turn each rule into something that can be built, tested and maintained. In our deployments, every absence requirement is captured with four pieces of information before configuration begins:
- Source: whether it comes from legislation, a collective agreement, or company policy and local practice
- Population: which workers it applies to, defined by data Workday can read, such as location, worker type, contract or union membership
- Rule: how the entitlement is earned, used, limited, carried over and paid
- Owner: who confirms the rule today and who maintains it when it changes
This step usually shrinks the design. Requirements described as legal often turn out to be company policy, and policies that differ only slightly between countries can often be combined. What remains are differences the organization can explain: why the plan exists, who it applies to and what would need to change to retire it. Confirming the legal source is work for qualified counsel. The design team’s job is to make sure someone is accountable for the answer.
Set the Global Framework First
Once requirements are sorted, the team needs global principles that every country plan follows. These are the decisions that keep a deployment consistent as it moves from the first country to the tenth:
- Plan and time off naming
- Employee and manager responsibilities
- Approval routing
- Request and correction methods
- Eligibility design
- Balance validations
- Documentation requirements
- Leave entry and return-from-leave responsibilities
- Payroll mapping
- Reporting
- Data governance
- Ongoing ownership
With those principles in place, each local request can be measured against them. Some variations are necessary because a law or agreement requires them. Others exist because a legacy system or site practice once needed them. A Workday deployment is a good moment to retire the second kind.
Design the Employee Experience Before the Plans
Employees in different countries will have different plans. They should not however have a different experience. A manager with team members in three countries should approve time off the same way for all of them, and an employee who transfers from Toronto to Manchester shouldn’t have to relearn how to request a day off.
That consistency has to be planned. Before configuration, decide what every employee should be able to do regardless of location:
- See which absence options they are eligible for
- View balances in the unit their plan uses, whether hours or days
- Submit and correct requests through the same process
- Track request status and receive standard approval or denial notifications
- Know who to contact when they need help
Units matter more than teams expect. A US employee may track sick time in hours while a French colleague tracks leave in working days. Decisions like this shape what employees see, how managers approve and how payroll receives the result, so they belong in design, not in testing. Teams that have worked through these choices across several countries know where they tend to surface late, and can raise them while they are still easy to change.
Plan for Change Before You Go Live
The decisions above are easiest to make at the start of a global Workday deployment. They are also the decisions most likely to be revisited after it. Absence rules keep moving. Paid sick leave laws continue to spread across US states and cities. Collective agreements are renegotiated. Organizations add countries, acquire companies and update policies. Each change lands on a set of plans that someone has to update without breaking the rest.
Without an owner and a process for that work, absence configuration drifts. Within a few years, teams often find:
- Duplicate plans
- Inconsistent naming
- Approval differences no one can explain
- Conflicting eligibility rules
- Manual workarounds
- Unclear ownership
- Country-specific configuration that is hard to maintain
The best time to set up governance is before the deployment begins, when roles are being assigned anyway. Decide who owns global standards, who approves local exceptions, who confirms policy and legal changes, and how updates are coordinated across HR, payroll, legal, Time Tracking and reporting. Recording the source and owner of every requirement during design gives that team a working reference on the first day after go-live. Each local difference then stays because someone approved it for a reason.
Bring Payroll In at the Start
Many organizations involve payroll only after absence design sessions are finished. By then, decisions with direct pay impact have already been made. Bring payroll subject matter experts into design from the first session to answer:
- Which absences are paid, partially paid or unpaid?
- Which entries must be sent to payroll?
- Are payouts required when employment ends?
- Are certain absences paid differently by country?
- Are there absence or payroll audits to account for?
In a global deployment, payroll is often run by different providers in different countries, which makes these answers even more important. Each provider needs absence data in a form it can use.
Reporting Starts in Design
Absence reporting across countries is only as reliable as the consistency underneath it. If one country tracks vacation in hours and another in days, or similar plans carry unrelated names, a global balance report becomes hard to read and harder to trust.
Workday delivers standard reports such as Time Off Balance Month by Month, Time Off Summary by Date Range, and the Time and Absence Hub brings much of this information together for administrators. These reports can be copied and adjusted for each location, but they work best when plan naming, units and population definitions were decided with reporting in mind.
Ask early who will use absence data and what they need from it. Finance may need liability by legal entity. HR may need to follow up on balances approaching expiration. Operations may want absence trends by site. Each need points to a design decision.
Getting It Right Before You Build
Global absence deployments rarely struggle because Workday can’t support a country’s rules. They struggle because decisions about structure, ownership, payroll and governance were left until configuration, when they are hardest to make. Organizations that sort requirements by source and population, set global principles first and plan for change before go-live end up with absence plans their teams can explain and maintain, and a process employees understand wherever they work.
About Helios
Helios has worked in workforce management for more than 20 years, including early design workshops that helped shape Workday Time Tracking. When Workday wanted guidance on workforce management across the United Kingdom, France, Germany and Australia, it brought in Helios to advise. Our consultants lead Time Tracking, Absence, Scheduling and Labor Optimization deployments for large global organizations with collective agreements, union rules and complex local requirements.
That experience shapes how we approach every global deployment. We start with worker populations and the source of each requirement, separate what the law requires from what local practice has added, and build a global framework each country can fit into. The result is a design your team can explain, test and maintain long after go-live.
To learn more, read our white paper, Expanding Workforce Management Globally: Seven things leaders need to consider before a global implementation, or contact Helios to talk through your global absence deployment.
