Oracle Fusion HCM (Netherlands) :: Dutch Statutory Absences Implementation and Functional Considerations

Oracle Fusion HCM (Netherlands):
Dutch Statutory Absences Implementation

and Functional Considerations
ORACLE WHITE PAPER |SEPTEMBER 2020
Disclaimer
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be relied upon in making purchasing decisions. The
development, release, and timing of any features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.
Note: In the images or examples included in this document regarding: user details, company names, addresses,
emails, and/or telephone numbers represent a fictitious sample of data (based upon made up data used in a
demo environment). Any similarity to actual persons, living or dead, is purely coincidental and not intended in
any manner.
ORACLE FUSION HCM (NETHERLANDS): STATUTORY ABSENCES IMPLEMENTATION AND FUNCTIONAL CONSIDERATIONS
Table of Contents
Introduction 1
Common Considerations 2
Effective Dates 2
Absence Record Maintenance 2
Unit of Measure 2
Enabling Absence Record Flexfield Contexts with Legislative Grouping Codes 2
Dutch Absence Setup Summary 3
Setting Up Sickness Absence Plan and Sickness Absence Types 4
Sickness Absence Plan 4
Sickness Absence Type 4
The Gatekeeper Law (Wet Verbetering Poortwachter) 6
Sickness-Related Absence Types for Gatekeeper Law Processing 7
Gatekeeper Law Absence Category 7
Gatekeeper Law Checklist Template 9
Reviewing the Template 9
Copying and Modifying the Predefined Template 9
Modified Checklist Template: Points to Consider 9
Selecting the Modified Checklist Template for a Legal Employer 10
Gatekeeper Law Case Manager 10
Assigning Case Manager Responsibility Type 10
Overriding the Case Manager Responsibility 11
Creating a Gatekeeper Law Absence Case 11
2 | ORACLE FUSION HCM (NETHERLANDS): STATUTORY ABSENCES IMPLEMENTATION AND FUNCTIONAL CONSIDERATIONS
Gatekeeper Law Start Date 12
Gatekeeper Law Start Date Example 12
28-Day Rule 12
Start and End Dates for Part-Time Absences 13
Managing the Gatekeeper Law Documents 13
Creating Gatekeeper Law Documents 13
Gatekeeper Law ESS Process 14
Gatekeeper Law Security Setup 15
Setting Up Maternity, Adoption, and Foster Care Absence Plans and Absence Types 16
Maternity, Adoption, and Foster Care Absence Plan 16
Maternity, Adoption, and Foster Care Absence Types 16
Digital Absence Reports 16
Setting Up Digital Absence Reports 17
Absence Management Setup: Absence Types, Reasons and Categories 17
Global Human Resources Setup 17
Review Statutory Deductions and Reporting Card 18
Managing TRU Sickness Report Details 18
Overriding Absence Contact Details 19
Running the Digital Absence Reports 19
Report Date Fields 19
Reporting Level and Output 20
Absence Report Parameters 21
Withdrawing Existing Reports 21
Reporting Multiple Absences in One Report 22
Sickness Report 23
Report Triggers 23
Reported Dates 24
Sickness Recovery Report 25
Report Triggers 25
Reported Dates 26
Long-Term Sickness Report 28
Report Triggers 28
Reported Dates 28
Long-Term Sickness Recovery Report 29
Report Triggers 29
Reported Dates 29
WAZO Report 29
Report Triggers 30
Reported Dates 30
Table of Figures
Figure 1. Absence Record Maintenance 1
Figure 2. Legislative Grouping Code Field 2
Figure 3. Absence Record: Legislative Information Region 2
Figure 4. Create Absence Type Page. 4
Figure 5. Sickness Absence Type: General Attributes 5
Figure 6. Absence Type: Add Plan 5
Figure 7. Absence Type: Work Accident Absence Reasons 6
Figure 8. Absence Type: Reason Field 6
Figure 9. Absence Type: Dates and Duration 7
Figure 10. Absence Type: Supplemental Absence Details 7
Figure 11. Gatekeeper Law Setup Flow 9
Figure 12. Gatekeeper Law Absence Category 10
Figure 13. Absence Category: Select and Add Type 10
Figure 14. Search Checklist Templates 11
Figure 15. Gatekeeper Law: Review Checklist Template 11
Figure 16. Gatekeeper Law: Search Checklist Templates 12
Figure 17. Gatekeeper Law: Duplicate Checklist Template 12
Figure 18. Gatekeeper Law: Edit Checklist Template Copy 13
Figure 19. Gatekeeper Law: Select Checklist Template for Legal Employer 14
Figure 20. Manage Case Manager Area of Responsibility 15
Figure 21. Gatekeeper Law: Create Case Manager Area of Responsibility 15
Figure 22. Absence Case: Case Manager Override 16
Figure 23. Create a Gatekeeper Law Absence Case 17
Figure 24. Absence Case: Gatekeeper Law Category 17
Figure 25. Gatekeeper Law Absence Case: Add Absences 18
Figure 26. Gatekeeper Law Absence Case: Gatekeeper Law Start Date 18
Figure 27. Add Document to Absence Case 20
Figure 28. Gatekeeper Law Document Types: Document Details 21
Figure 29. Allocate Gatekeeper Law Checklist Tasks Process 21
Figure 32. Create Childbirth or Placement Absence Type 23
Figure 33. Maternity Absence Type: General Attributes 24
Figure 34. Add Plan to Absence Type 24
Figure 35. Absence Type: Dates and Duration 24
Figure 36. Sample XML Report Output 25
Figure 37. Tax Reporting Unit: Sickness Report Details 27
Figure 38. Absence Record: Contact Override Fields 28
Figure 39. Run Digital Absence Reports 29
Figure 40. Sickness, Recovery, and WAZO Report Parameters 31
Figure 41. Long-Term Sickness and Recovery Report Parameters 32
Figure 42. Run Digital Absence Reports, Including Withdrawals 33
Figure 43. Run Digital Absence Reports, Including Withdrawals 33
Figure 44. Sickness Recovery Report: Partial Recovery Fields 37
Figure 45. Absence Case DDF Long-Term Sickness Segments 39
Figure 46. Absence Case DDF Long-Term Sickness Recovery Segments 40
Figure 47. WAZO Reported Dates 41
Introduction
Oracle Fusion HCM for the Netherlands enables you to manage and report on sickness and WAZO
(Work and Care Act) absences in accordance with Dutch legislation. This document describes the
setup steps for implementing:
» Gatekeeper Law (Wet Verbetering Poortwachter)

» Digital Absence Reports
» Sickness Report
» Sickness Recovery Report
» Long-Term Sickness Report
» Long-Term Sickness Recovery Report
» WAZO Report
This document focuses on the setup steps (and any prerequisites) required for absences relating to:
» Sickness (of all types)

» Maternity, Adoption, and Foster Care
Before proceeding with setting up Dutch absences, you must be familiar with global absence
management and the setup of Oracle Fusion HRMS for the Netherlands. Please refer to the Oracle
Help https://docs.oracle.com/en/cloud/saas/index.html for more information.
The related help topics for the Gatekeeper Law are referenced in the relevant sections of this
document.
Common Considerations
Effective Dates
When creating new components, ensure that you set an effective start date, which covers the time scale of the
absences you wish to enter, including any absence history that you may need to migrate.
Absence Record Maintenance

Ensure that any absence types you create have the appropriate absence record maintenance values populated, so
that absence records can be updated or maintained appropriately. For example, you might want to ensure that
administrators and managers can update sickness records but not employees.
Unit of Measure
In order for statutory payments to work correctly, you must specify the correct unit of measure for each statutory
plan, as described in subsequent sections of this document. Absence types can be in any unit of measure that is
appropriate for your business needs (for example, if your occupational plans are in hours, you will need to set up the
absence type in hours to ensure that you capture absences correctly). This may result in a mismatch between the
unit of measure on the type and statutory plan. In such cases, specify a conversion formula at the plan level.
Enabling Absence Record Flexfield Contexts with Legislative Grouping Codes

A legislative grouping code is a field on the absence type that enables you to map that absence type to a predefined
context of the Absence Recording Developer Flexfield (ANC_PER_ABS_ENTRIES_DDF). The flexfield segments
defined for that context will then display automatically in the Legislative Information region when you enter an absence
record, according to absence type. You specify the legislative grouping code as a general attribute of the absence
type.
In the Netherlands, the flexfield contexts are used to capture information that is either reported in the Digital Absence
Reports or generated by those reports. For example, the Dutch Postnatal Sickness DDF context includes additional
contact fields that are required for reporting.
You cannot run the digital absence reports without the flexfield contexts being associated with the relevant absence
types. To use the digital absence reports, you must configure your absence types to include the appropriate
legislative grouping codes.
The predefined legislative grouping codes available for the Netherlands are:
Dutch Pregnancy-Related Sickness
Dutch Postnatal Sickness
Dutch Organ Donor
Dutch Sickness
Dutch Work Accident
Dutch Maternity
Dutch Adoption
Dutch Foster Care
Their usage is described further in the Sickness Absence Type and Maternity, Adoption and Foster Care Absence
Type sections of the document.
Dutch Absence Setup Summary
The table below summarizes the Global Absence Management items that you must create to implement the
absences features described in this document:
GLOBAL ABSENCE MANAGEMENT SETUP SUMMARY FOR THE NETHERLANDS
Legislative Grouping
Absence Type Absence Reason Absence Category Absence Plan
Code
Pregnancy-Related N/A N/A Dutch Pregnancy- Sickness

Sickness Related Sickness
Postnatal Sickness N/A N/A Dutch Postnatal Sickness

Sickness
Organ Donor N/A N/A Dutch Organ Donor Sickness
Sickness N/A Gatekeeper Law Dutch Sickness Sickness
Work Accident Work-related accident Gatekeeper Law Dutch Work Accident Sickness
Accident caused by third

party
Not applicable
Maternity N/A N/A Dutch Maternity Maternity
Adoption N/A N/A Dutch Adoption Maternity
Foster Care N/A N/A Dutch Foster Care Maternity
The additional global HR setup steps and prerequisites required to implement the Gatekeeper Law or Digital
Absence Reports are described in the relevant sections of this document.
Setting Up Sickness Absence Plan and Sickness Absence Types
There are several steps for setting up absences so they comply with the Gatekeeper Law and statutory reporting
purposes:
Creating absence plans

Creating absence types
Adding user-defined sickness and work accident types to Gatekeeper Law absence category
Sickness Absence Plan

Use the Manage Absence Plans task in the Absence Administration work area to create the absence plans you
require for your enterprise, for example, a statutory sickness plan and an occupational sickness plan. Select the plan
type Qualification and the legislation Netherlands.
For more information, on setting up qualification absence plans, see the Oracle Help Center.
Sickness Absence Type

It is highly recommended you create one (or more) of each absence type listed below and link it to the relevant
legislative grouping code. This will simplify your setup if you implement the Gatekeeper Law and Digital Absence
Reports, either now or later. The names are user-defined, the following are some examples:
Pregnancy-Related Sickness
Postnatal Sickness
Organ Donor
Sickness
Work Accident
To create a sickness absence type:
1. In the Absence Administration work area, select Manage Absence Types.

2. Select Create. The Create Absence Type screen appears.
3. Set the effective date.
4. Select Legislation Netherlands.
5. Select the pattern Illness or injury.
6. Click Continue.
7. Enter the attributes of the type, including the Dutch Sickness legislative grouping code and days as the unit of
measure.
8. In the Plan and Reasons tab, select Add Plan.
9. Select the plan or plans that you created for the absence type.
10. If you are creating a Work Accident absence type, add the 3 predefined work accident reasons using this tab:
Work-related accident
Accident caused by third party
Not applicable
Note: The work accident reason is reported in the Sickness report; it will not be reported if you do not map your
absence reasons to your work accident types as described here.
11. In the Display Features tab, set the Reason as Entry Required for Administrative Transactions if the
absence type relates to work accidents. For other absence types, there is no statutory requirement to enable it.
Note: Although the following three fields are not a statutory requirement, you can set the following:
Schedule nonworking days: Use this if your unit of measure is not calendar days. This allows you to enter an
absence start or end date on any day of the week, irrespective of whether it is a workday.
Open-ended absence attribute: If you do not set this to Display and Edit, you have to enter an absence end
date when you enter an absence.
Advanced Entry mode: This enables you to enter part-time absences.
12. On the Supplemental Absence Details region, you must enable Notification Date. This represents the date on
which the employee notified their employer of their absence. It defaults to the current system date, but you can
override it. The date is mandatory for the Sickness Report and Sickness Recovery Report.
13. Configure the remaining fields to relevant for your organization.
14. Click Save and Close.
The Gatekeeper Law (Wet Verbetering Poortwachter)
The statutory Gatekeeper Law defines the rules and procedures that an employer must follow to reintegrate an
employee, who has been absent due to sickness, back into the workforce as soon as possible. The employee may
have been on a lengthy period of sickness absence, or there may be a pattern of related sickness absences with 28
days or less between each absence.
The aim is to support the employee in their return to work and thus avoid long-term sickness benefit payments for
which the UWV social insurance provider organization is responsible after two years of sickness.
The Gatekeeper Law process is divided into phases. In Fusion, there is a checklist task triggered at the start of each
of those phases, according to the start date of the absence case (the Gatekeeper Law Start Date).
A statutory document (or a requirement to write notes), is associated with each task. You can attach those
documents to the sickness case. The overall process is overseen by a Case Manager.
These are the key components and setup tasks required for the Gatekeeper Law:
ADDITIONAL SETUP REQUIREMENTS
Object Task How it’s Used in the Gatekeeper Law
Sickness-Related Manage Absence Types Create the absence types that are liable for Gatekeeper Law processing, for
Absence Types example, sickness and work accident absence types. (Plus any more that
you know are subject to managing according to the Gatekeeper Law.)
Gatekeeper Law Manage Absence Categories All sickness types that are liable for Gatekeeper Law reporting must be
Absence Category associated with the predefined Gatekeeper Law absence category.
Absence Case Manage Absence Cases An absence case associated with the predefined Gatekeeper Law category
contains the absences and documents, such as copies of reports, relating
to the case. Validation of the statutory “28-day rule” is provided.
Gatekeeper Law HR Manage Checklist Templates The predefined Gatekeeper Law checklist template includes the statutory
Checklist Template tasks for each stage of the statutory Gatekeeper Law process. You can
copy and modify the template to meet the needs of your organization.
The checklist tasks are allocated using the Gatekeeper Law Start Date on
the absence case. The checklist is suspended if all the absences in the
case have ended and the employee has recovered.
Dutch Legal Manage Legal Entity HCM If your organization uses a modified version of the predefined Gatekeeper
Employer Details Information Law checklist template, select it at legal employer level. Otherwise, the
predefined template is used.
Case Manager Create Area of Responsibility Allocate one or more case manager responsibilities to oversee the
Responsibility Gatekeeper Law in your organization. The Gatekeeper Law checklist tasks
are allocated to that responsibility type.
Custom Duty Roles Manage Duties Provide your case managers’ access to the UIs and employee data that
they need to oversee the Gatekeeper Law process.
Allocate Gatekeeper Schedule New Process This process allocates the Gatekeeper Law checklist tasks as they become
Law Checklist Tasks due to start, according to the Delay Duration on the checklist and the
ESS Process Gatekeeper Law Start Date. Schedule the process to run frequently enough
that you will comply with the Gatekeeper Law timeframes.
Create Sickness Dutch Gatekeeper Law Setup
Absence Administration
Absence Types
Add Absence
Types to Absence
Category
Review
Select Template
Gatekeeper Law Copy and Edit
Checklists
Customization Yes
Required?
for Legal
Checklist Template
Employer
Template
No
Responsibilities
Create Case
Manager
Responsibility
Security
Set Up
Case Manager
Security
ESS Processes
Define Schedule for

ESS Process
Figure 1. Gatekeeper Law Setup Flow
Sickness-Related Absence Types for Gatekeeper Law Processing

The setup steps for this are described in the Sickness Absence Types section of this document.
Gatekeeper Law Absence Category

The predefined Gatekeeper Law absence category is used for the management of absence cases according to the
Gatekeeper Law rules. It is essential that you add all absence types that may be subject to those rules to the
predefined Gatekeeper Law absence category. This is typically any Sickness or Work Accident absence types.
Absences relating to pregnancy-related sickness, postnatal sickness, or organ donation, are not subject to
Gatekeeper Law processing, so you do not need to add those types to the predefined Gatekeeper Law category.
You must use the predefined Gatekeeper Law absence category for your user-defined sickness and work accident
absence types. Do not use a user-defined absence category.
To associate your user-defined sickness and work accident types with the predefined Gatekeeper Law category:
1. In the Absence Administration work area, select Manage Absence Categories.

2. Search for and select the predefined Gatekeeper Law absence category and
3. Select the predefined Gatekeeper Law absence category and add each of your user-defined Sickness and
Work Accident absence types to it.
4. Set the status as Active.
5. Click OK.
6. Click Save and Close.
Gatekeeper Law Checklist Template
The Gatekeeper Law checklist is a predefined checklist template that includes tasks to reflect the statutory
milestones in the Gatekeeper Law process. Each task has a predefined start date (its Delay Duration) and a Task
Duration. These dates comply with the statutory requirements of the Gatekeeper Law.
You can use the predefined checklist template or modify a copy of it to suit your business needs, for example, to add
additional tasks.
The checklist tasks are allocated using the Gatekeeper Law ESS process.
Reviewing the Template

To review the predefined checklist template to determine if it meets the needs of your organization as it is:
1. From Setup and Maintenance work area, select Workforce Development > Define Common HCM Configuration
> Define Workforce Business Processes and Events > Define Checklists > Manage Checklist Templates.
2. Search for the checklist template name Gatekeeper Law and open the template:
3. Review the list of tasks on the template. The template includes the tasks, start dates, and maximum expected
duration of the tasks in accordance with the Gatekeeper Law rules.
The Delay Duration is used to calculate when a checklist task is due to start. The delay duration specified on
a predefined Gatekeeper Law checklist template task is the number of weeks after the Gatekeeper Law Start
Date on the absence case.
For example, if the Gatekeeper Law Start Date is 1-Mar and the Delay Duration is 3 weeks, the Create
Problem Analysis task is due to start 22-Mar (1-Mar + 3 weeks). The task will be allocated to the task
performer on this date (depending on the Allocate Gatekeeper Law Checklist Tasks ESS process schedule.)
The Target Duration is the expected maximum duration of the task. Added together with the Gatekeeper Law
Start Date and the Delay Duration of the task, it determines when a task is due for completion.
For example, if the Gatekeeper Law Start Date is 1-Mar, the Delay Duration is 3 weeks, and the Target
Duration Is 21 days, the Create Problem Analysis task is due to be completed by 12-Apr (1-Mar + 3 weeks +
21 days).
4. Click Done.
If the predefined template meets your organization’s requirements, no further steps are required. This template will
be used by default for all employees in your legal employer.
Copying and Modifying the Predefined Template

If you need to make changes to the template, you can copy and modify the template to suit your organization’s
requirements: To do this:
5. From the Manage Checklist Templates page, search for and select the predefined Gatekeeper Law template
again and click Duplicate.
6. You can edit your copy of the checklist template. For example, you could add own organization-specific tasks.
7. Then click Submit to save your modified version of the checklist.
Modified Checklist Template: Points to Consider

When creating a modified version of the checklist template, note the following:
The modified template must be associated with the Gatekeeper Law checklist category.
To ensure compliance with the statutory Gatekeeper Law rules and timelines, it is recommended that you do
not remove any predefined tasks or change the Required flag to No.
Although you can change the target and delay durations, you must ensure that the tasks finish no later than
the due date according to the Gatekeeper Law rules for statutory compliance.
It is recommended that you continue to use the Case Manager Responsibility type as the checklist task
performer. Allocate all statutory tasks to this responsibility.
For more information related to this feature, go to Applications Help for the following topics:
Managing the Gatekeeper Law Checklist Template: Points to Consider

Checklist Components: How They Work Together
Why has the due date changed for a Gatekeeper Law checklist task?
Why has the Gatekeeper Law checklist task been suspended?
Selecting the Modified Checklist Template for a Legal Employer

The Gatekeeper law checklist template used in your organization is specified at legal employer level. If you have a
modified version of the template, you must select it. Otherwise, the predefined Gatekeeper Law template is used for
your legal employer, by default.
8. Using the Manage Legal Entity HCM Information task, open the legal employer and the Dutch Legal Employer
Details and select the modified template. The default checklist template for the legal employer is the predefined
Gatekeeper Law template.
9. Click Submit to save the selected template.
Gatekeeper Law Case Manager

The role of the case manager is to manage the Gatekeeper Law process for an individual employee absence case.
The case manager will be responsible for the completion of the Gatekeeper Law checklist tasks and managing the
supporting documents. They will need access to the employee’s absence case.
The case manager or managers for your organization could typically be:
The employee’s line manager

A person in an occupational health or Arbodienst role
Anyone else in the organization
As a legislative requirement, the employee must agree to the case manager allocated to their case. For example,
even if line managers usually perform the role in your organization, the employee is entitled to request a different
case manager for their particular case.
This section describes:

Case manager responsibility type
Case manager security
Case manager overrides
Assigning Case Manager Responsibility Type

Assign the case manager responsibility type to the employees performing that role in the legal employer. The
checklist tasks for employees covered by the scope of that responsibility will be allocated to the respective case
manager. For more information on areas of responsibility, see the Oracle Help Center.
To assign the case manager responsibility:

1. Search for the employee to whom you will allocate the responsibility, select the Manage Areas of Responsibility
task in Person Management. Click Create:
2. Provide a responsibility name.
3. Select the Case manager responsibility type and complete the rest of the details as required.
Overriding the Case Manager Responsibility

You can override the case manager assigned to an employee’s Gatekeeper Law absence case and select a
different case manager. The new case manager can be any worker in the same legal employer.
For example, you may need to override the default line manager case manager when an employee would like
another case manager to administer their particular Gatekeeper Law absence case. You can select the case
manager override option at the start of the Gatekeeper Law process or at any stage during it, even if some tasks
were already allocated to a different case manager.
The new case manager does not need to have a new case manager responsibility assigned to them; if an override
exists on an absence case, the remaining checklist tasks will be assigned to them. If multiple overrides have been
entered on a case over a period of time, then the checklist task will be allocated to the case manager selected in the
override field on the ESS process date.
There may also be occasions when the case manager administering one or more cases must change during a
Gatekeeper Law process because, because, for example:
The employee has a new line manager

The existing case manager was terminated
When this occurs, you would typically set up the case manager responsibility for the new case manager and the
employee’s outstanding checklist tasks will be allocated to them. (If the new case manager will assume the role only
temporarily or very briefly, you could still use the override as an alternative.)
To enter a case manager override:
1. Select the Manage Absence Cases task in the Absence Management work area.
2. Select the context Netherlands in the Absence Case Legislative Information region.
3. Select the name of the worker who will manage this case in the Case Manage Override field.
Subsequent task allocations by the Allocate Gatekeeper Law Checklist Tasks process will allocate tasks to the new
case manager.
Creating a Gatekeeper Law Absence Case

Prerequisite
You must have one or more absence records whose absence type is associated with the Gatekeeper Law absence
category.
To create a Gatekeeper Law absence case:

1. Search for and select the employee in person management. Select Manage Absence Cases:
2. Click Create and enter the basic details of the case.
3. Select the category Gatekeeper Law:
4. In the Associated Absences section, click Select and Add to add your sickness-related absences to the case.
You cannot add absences that start more than 28 days after the previous absence ended. This is in accordance with
the statutory 28-day rule on what constitutes a “connected” or related Gatekeeper Law absence.
Note: You can select a Case Manager Override, if required.
5. Submit the absence case:
Note: You will not see a date in the Gatekeeper Law Start Date field yet. It is calculated when you submit the
absence case. You can view the Gatekeeper Law Start Date as a read-only field if you reopen the case.
Troubleshooting Tip: If no Gatekeeper Law Start Date is displayed when you reopen the ca, check the following:
The absence case category is Gatekeeper Law.
One or more Gatekeeper Law absence records are associated with the absence record.
Gatekeeper Law Start Date

Each phase of the Gatekeeper Law must be administered according to a statutory schedule. The date by which the
task associated with each phase is due (for example the Long-Term Sickness Report) depends on the start date of
the employee’s absence case. In Oracle Fusion, that date is the Gatekeeper Law Start Date:
» It is a read-only field on the absence case and is automatically calculated.

» This date is recalculated whenever absence records are added to or removed from the case (after the case is
submitted).
» If the Gatekeeper Law Start Date changes, any checklist tasks that have not yet started will have their dates
recalculated. No changes are made to completed tasks.
» If an absence case contains only one absence, the Gatekeeper Law Start Date defaults to the start date of the
absence case.
» If the case contains multiple “connected” (related) absence records, then the Gatekeeper Law Start Date takes
into account any “recovery” days between each absence record in the case. The date is calculated by adding the
number of recovery days between absence records (if two or more records exist) to the start date of the earliest
absence.
» The current Gatekeeper Law Start Date on a case is used in the allocation of the Gatekeeper Law checklist and
tasks, according to:
The Delay Duration specified for each task in the Gatekeeper Law checklist template. The delay duration is
the number of days or weeks after the GL Start Date when the task is due to start.
The frequency of the Gatekeeper Law ESS process.
Gatekeeper Law Start Date Example

An absence case contains one absence record with a start date of 03-Jan-2017. The Gatekeeper Law Start Date
defaults to 03-Jan-2017.
That absence ends on 31-Jan-2017 and a second absence record with a start date of 15-Feb-2017 is added to the
same case.
The employee therefore had 14 calendar days of “recovery” in between absence 1 and absence 2. The Gatekeeper
Law Start Date is recalculated to 17-Jan-2017 (03-Jan-17 + 14 recovery days).
For more information, go to Applications Help for the following topics:

Gatekeeper Law Absence Case: Explained
Gatekeeper Law Start Date: How It Is Calculated
28-Day Rule
All absence records in a Gatekeeper Law absence case must comply with the statutory “28-day Rule”. According to
the rule, the absences in a Gatekeeper Law absence case can have no more than 28 “recovery” days between one
absence ending and the next absence starting.
Even if two absence records are related and liable for Gatekeeper Law processing, if there are more than 28 days
between then, you must include them in separate absence cases. For example, if one absence ends 21-Apr and the
same employee starts a related absence on 1-Jun, you must create a new absence case for the June absence. A
new checklist is allocated and the checklist for the April case is suspended because that absence case is
considered ended.
The application validates the 28-day rule whenever you save a Gatekeeper Law absence case.
Start and End Dates for Part-Time Absences

Part-Time (partial) absences are managed in accordance with the Gatekeeper Law rules, that is, partial days are
ignored. For example, if an absence starts 01-Feb-2017 but the employee does not go sick until half way through
their working day, the hours worked that day are ignored; 01-Feb-2017 is the absence start date and the
Gatekeeper Law Start Date (if no other absence records exist).
Equally, if an absence ends half way a day and the employee returns to work for some of that day, it is considered
the final day of absence. Any hours worked during that day are ignored.
Managing the Gatekeeper Law Documents

The management of the documents associated with an employee’s Gatekeeper Law absence case is a key
requirement of the statutory process. Use Documents of Record to associate all related documents with a
Gatekeeper Law absence case. The Gatekeeper Law document category includes the following predefined
document types for that purpose:
Final Evaluation
First Year Evaluation
Notes
Plan of Approach
Problem Analysis
Recovery Information
UWV Sickness Report
Using the Global HR functionality, you can:
Create documents from an absence case

View those documents from either the absence case or the Documents of Records region of the person
record.
You can further secure document types using document type security.
Only the documents created in the absence case are available to view from the case. The case manager cannot
view the employee’s other documents from the case.
Creating Gatekeeper Law Documents

To create document records for a Gatekeeper Law absence case:
1. Open the employee’s absence case using the Manage Absence Cases task in Person Management.
2. In the Document Information section, select Create.
3. Select the Country Netherlands and the relevant document type.
4. In Document Details, optionally enter a document name.
The document owner defaults to the display name of the current user, but you can override it.
The document date defaults to the current system date, but you can override it.
5. You can add an attachment if required. For example, you could add the copy of a report.
6. Click OK and then Submit.
Gatekeeper Law ESS Process

The Gatekeeper Law checklist and tasks are allocated to the task performer using the Allocate Gatekeeper Law
Checklist Tasks Enterprise Scheduler Service (ESS) process.
The process allocates tasks if they are due to start on or before the process date, according to the current
Gatekeeper Law start date on the absence case and the delay duration specified for the task.
Allocating tasks in this way (as opposed to allocating the entire checklist at once) is particularly useful when
managing a Gatekeeper Law absence case, where the duration of the entire process could run for up to two years.
The process only allocates a checklist task if a Gatekeeper Law absence case exists and it contains one or more
absence records, the most recent of which has not yet ended as of the process date. (If the most recent absence
has ended, the assumption is that the employee has recovered and the Gatekeeper Law process is suspended.)
Use the ESS scheduling features to run the Gatekeeper Law process on an ad-hoc basis or to create a regular
schedule for it. It is recommended that you use a schedule to ensure that checklist tasks are allocated promptly
within the timeframes required by the Gatekeeper Law legislation. If you run the process as needed (schedule is “as
soon as possible”) and you do not specify an effective date, the current system date is used.
Additional Features
The ESS process runs for all Dutch legal employers within the enterprise.
The process is not dependent on the completion of one task before the allocation of the next.
If the employee is no longer on a Gatekeeper Law sickness absence as of the effective date, and if there are
tasks which were allocated previously but are still incomplete, the process suspends these tasks.
If the employee goes on another Gatekeeper Law sickness absence (within the 28-day period), and there
are previously suspended tasks, the process resumes the allocation of these tasks with new start and end
dates. It does not alter the dates of completed tasks.
For more information related to this feature, go to Applications Help for the following topics:
Scheduled Processes: Explained

Submitting Scheduled Processes and Process Sets: Procedure
Why has the due date changed for a Gatekeeper Law checklist task?
Why has the Gatekeeper Law checklist task been suspended?
Troubleshooting Tips
Why was a checklist task not allocated?
If a checklist task was not allocated as it should have been, verify the following:
Absence case is associated with Gatekeeper Law (before absence records were added to the case).
Absence case includes at least one absence record (and their types are associated with Gatekeeper Law
category).
If there is an end date on the most recent absence in the absence case, it is later than the effective date on
which the Allocate Gatekeeper Law Checklist Tasks process is run.
The first checklist task is due to start on or before the effective date. (Review the Gatekeeper Law Start Date
of the case and the delay duration of the task.)
The Case Manager area of responsibility is allocated.
Gatekeeper Law Security Setup

To use the Gatekeeper Law features, the Gatekeeper Law case manager requires access to the following pages in
order to manage the absence cases for the employees for whom they are responsible:
Manage Absence Case, including Document Records
Manage Worker Checklists
In many organizations, the Gatekeeper Law case manager is the line manager of the employee or HR manager.
Line managers do not have access to absence cases by default. If your case managers are not HR managers,
consider creating a new HCM Case Manager job role and map the following duties or privileges to the role.
GATEKEEPER LAW SECURITY
Display Name Duty Role or Privilege Name (Code) Description
Manage Person Work Area PER_MANAGE_PERSON_WORK_AREA_PRIV Allows access to the Person Management work area.
Search Person PER_SEARCH_PERSON_PRIV Allows searching for a person.
Manage Worker Checklist ORA_PER_CHECKLIST_MANAGEMENT_DUTY Manages checklist definitions.
Manage Absence Case ORA_PER_ABSENCE_ANALYSIS_DUTY Allows management of absence cases.
Manage Person Documentation ORA_PER_DOCUMENT_MANAGEMENT_DUTY Manages documents.
Setting Up Maternity, Adoption, and Foster Care Absence Plans and Absence
Types
You must select specific configuration options to make your maternity, absence or foster care absences available for
statutory reporting in the WAZO report. Additionally, create one or more absence plans to define the rules for
entitlement.
Maternity, Adoption, and Foster Care Absence Plan

Use the Manage Absence Plans task to create the absence plans you need to comply with legislation and to meet
the needs of your enterprise. For example, you may just need one statutory plan to cover all your WAZO-related
absences. Select the plan type Qualification and legislation Netherlands.
For more information on creating maternity plans and a worked example, go to the Oracle Help Center.
Maternity, Adoption, and Foster Care Absence Types

Create one (or more) of each absence type listed below. This will simplify your setup if you implement the Digital
Absence Reports, either now or later. The names are user-defined, so the following are examples only.
Maternity
Adoption
Foster Care
Note that pregnancy-related and postnatal sickness are managed and reported as sickness-related absences as
described in the Sickness setup section of this document.
1. In the Absence Administration work area, select Manage Absence Types.

2. Select Create Absence Type.
3. Select the pattern Childbirth or placement.
4. Click Continue.
5. Select the correct legislative grouping code, for example, Dutch Maternity, for your maternity, adoption, or foster
care type to enable Dutch-specific flexfield segments to display on absence records of this type for statutory
absence reporting.
6. In the Plan and Reasons tab, select Add Plan.
7. Select the plan you created for the absence type.
8. In the Display Features tab, the expected date of event is required for reporting maternity absences.
9. Configure the remaining fields to meet the needs of your organization.
10. Select Save and Close.
Digital Absence Reports

The digital absence reports are statutory reports required by the UWV social insurance organization for the payment
of certain sickness absences and all WAZO absences.
You can run the following reports and create legislatively compliant XML reports and submit directly to the UWV:
» Sickness Report – for short-term sickness-related absences
» Sickness Recovery Report – for full and partial recovery from short-term sickness-related absences
» Long-Term Sickness Report – for long-term Gatekeeper Law absences
» Long-Term Sickness Recovery Report – for recovery from long-term Gatekeeper Law absences
» WAZO Report – for maternity, adoption, and foster care absences
Setting Up Digital Absence Reports
To successfully run the digital absence reports, you must set up the reports in Absence Management and Global
Human Resources.
Absence Management Setup: Absence Types, Reasons and Categories

Set up your sickness and WAZO absences as described previously in this document. The table below is a summary
of the setup requirements and the reports in which they are used.
ABSENCE MANAGEMENT SETUP REQUIREMENTS
Long-Term
Absence Absence Legislative Sickness and
Absence Type Sickness and WAZO
Reason Category Grouping Code Recovery
Recovery
Pregnancy-Related N/A N/A Dutch Pregnancy-

X
Sickness Related Sickness
Postnatal Sickness N/A N/A Dutch Postnatal

X
Sickness
Organ Donation N/A N/A Dutch Organ Donor X
Sickness N/A Gatekeepe Dutch Sickness Leave

X X
r Law
Work Accident Work-Related Gatekeepe Dutch Work Accident

X X
Accident r Law
Accident caused Gatekeepe Dutch Work Accident

X
by third party r Law X
Not applicable Gatekeepe Dutch Work Accident X

X
r Law
Maternity N/A N/A Dutch Maternity X
Adoption N/A N/A Dutch Adoption X
Foster Care N/A N/A Dutch Foster Care X
Global Human Resources Setup

Review and complete the following HR tasks:
GLOBAL HUMAN RESOURCES SETUP REQUIREMENTS
Object Task Action
Statutory Deductions and Manage Payroll Calculation The employee must have a personal calculation card containing current
Reporting Card Information information.
Tax Reporting Unit: Sickness Manage Tax Reporting Unit The report sender and contact details entered here are used in all the
Report Details HCM Information digital absence reports. Contact details can be overridden at absence
record level.
Worker Data Validation Report Run Worker Data Optionally run this report to perform various checks on employee data for
Validation Report the selected legal employer. For example, check if each employee in a
Dutch legal employer has an address and date of birth.
Review Statutory Deductions and Reporting Card
Some of the information reported in the Sickness Report is recorded on the employee’s personal calculation card,
for example, the income relationship number, eligibility for the wage tax discount, employment type code, and
contract code.
For more information on the automatic and manual creation of Dutch calculation cards, see the Oracle Fusion HCM
(Netherlands): HR Implementation and Functional Considerations White Paper (Document ID 1572711.1).
Managing TRU Sickness Report Details

The digital absence reports include report sender details and contact details for both the report and the absences
being reported. This information is specified at TRU level, so there is some TRU setup required prior to running the
reports. Use the Manage Tax Reporting Unit HCM Information task and select Sickness Report Details to enter this
contact and sender information.
For information on setting up Sickness report Details for the TRU, refer to the Oracle Fusion HCM (Netherlands): HR
Implementation and Functional Considerations white paper.
Some organizations may appoint a single point of contact for all absences, for example, an occupational health or
Arbodienst representative, whilst other organizations may assign the role to individual line managers. You can
record either in the Contact Type field.
If you select a line manager as the contact type, their line manager’s gender and phone number are derived from
their person record. For an organization-level contact, the information is recorded on the TRU.
The following table shows the source of the sender and contact information in your reports.
Digital Absence Report TRU Sickness Report TRU Sickness Report Details:
Name
Tag* Details: Sender Information Contact Information
KetenPartij SENDER DETAILS
Loonheffingennr Tax Registration Number Tax Registration Number N/A - Report Region Header
CdRolKetenpartij Sender Role Role
ContactGegevensOrganisatie ORGANIZATION CONTACT DETAILS
NaamContactpersoonAfd Contact Person or Contact Person or Department

Department
TelefoonnrContactpersoonAfd Contact Phone Number Contact Phone
ContactGegevensZiekteMelding ABSENCE CONTACT DETAILS
NaamContactpersoonAfd Contact Person Name Contact Name (defaulted from

person record for line managers)
OmschrijvingLokaleVestiging Establishment Name Location (defaulted from person

record for line managers)
Geslacht Contact Person Gender (defaulted from person

Gender record for line managers)
TelefoonnrContactpersoonAfd Contact Person Contact Phone (defaulted from

Telephone Number person record for line managers)
The other tags in the Sender Data report region are:
NaamSoftwarePakket (Application Name) – defaults to Oracle Fusion HCM
VersieSoftwarePakket (Software Version) – defaulted from your Fusion release number, for example,
13.0.0.1.0
Overriding Absence Contact Details

You can override the TRU contact details at individual absence level. You may need this if an absence record spans
multiple assignments and each assignment has a different line manager or to record a contact who is someone
other than the organization-level contact or the employee’s line manager.
The override details you enter on the absence record is reported in the Absence Contact Details
(ContactGegevensZiekteMelding) region of any digital absence reports relating to the absence. Any contact
information already entered in the Contact Information region of the TRU is ignored.
To make these fields available on the absence record, select the legislative grouping code for the absence type.
If the absence report includes multiple absence records (in an absence case), the likelihood is that the same contact
will apply. However, if there is an override on some, but not all of the absence records being reported, the contact
override on the most recent absence is reported. If no contact override exists on that absence (even if there are
overrides on the previous absence records in the same absence case), then the organization-level contact is
reported.
This is consistent with the handling of connected absences in accordance with UWV requirements. The assumption
is that they share many of the same details anywhere, but where multiple absences exist in an absence case, the
details of the most recent absence record is reported.
Run Worker Data Validation Report

The Worker Data Validation Report includes various checks, including for example whether an address and date of
birth exists for each employee.
Note: An address is required in the Sickness and WAZO reports.
Running the Digital Absence Reports

You can navigate to the reports in one of the following ways:
Payroll > Checklists > Submit a Process or Report
My Workforce > Data Exchange > HCM Extracts > Submit Extracts
My Workforce > Data Exchange > Payroll > Submit a Process or Report
After you select a Dutch legislative data group, the following report tasks are listed:
Run the Sickness Report

Run the Sickness Recovery Report
Run the Long-Term Sickness Report
Run the Long-Term Sickness Recovery Report
Run the WAZO Report
Report Date Fields

When you run a report, the as-of date when the report was run is added to the absence, or group of connected
absence, or absence case (for long-term sickness reporting). This is to prevent it from being reported more than
once and to have a record of when the report was created.
The report date fields are read-only and the dates are generated automatically to show the date on which the most
recent report was run:
DIGITAL ABSENCE REPORTING DATE FIELDS
Absence
Date Field Description
Component
WAZO Report Date Absence Record If the date is null, you can create a report for this maternity, adoption or
foster care absence.
WAZO Report Withdrawn Date Absence Record If a WAZO Report Date exists, you can withdraw the most recent report for
this absence. When the withdrawn report date is added, the WAZO Report
Date is set to null.
Sickness Report Date Absence Record If the date is null, you can create a report for this sickness, illness-related,
or work accident absence.
Sickness Report Withdrawn Date Absence Record If a Sickness Report Date exists, you can withdraw the most recent report
for this absence. When the withdrawn report date is added, the Sickness
Report Date is set to null.
Sickness Recovery Report Date Absence Record If the date is null, you can create a recovery report for this sickness, illness-
related, or work accident absence. You can only report short-term absence
recovery if there is a Sickness Report Date.
Recovery Report Withdrawn Date Absence Record If a Sickness Recovery Report Date exists, you can withdraw the most
recent recovery report for this absence. When the withdrawn report date is
added, the Sickness Recovery Report Date is set to null.
Long-Term Sickness Report Date Absence Case If the date is null, you can create a report for this absence case.
Long-Term Sickness Report Absence Case If a Long-Term Sickness Report Date exists, you can withdraw the most
Withdrawn Date recent report for this absence case. When the withdrawn report date is
added, the Long-Term Sickness Report Date is set to null.
Long-Term Sickness Recovery Absence Case If the date is null, you can create a recovery report for this absence case.
Report Date You can only report long-term absence recovery if there is a Long-Term
Sickness Report Date.
Recovery Report Withdrawn Date Absence Case If a Long-Term Sickness Recovery Report Date exists, you can withdraw
the most recent recovery report for this absence case. When the withdrawn
report date is added, the Long-Term Sickness Recovery Report Date is set
to null.
Reporting Level and Output

The UWV requires absences to be reported at income relationship level. In the Fusion application, one income
relationship maps to one Statutory Deductions and Reporting Card.
Depending on your organization, your employees may have:
Single assignment on one card

Multiple assignments on one card
Multiple assignments on multiple cards
Where multiple cards exist for an employee, the trigger type for the report determines whether a report is generated
for each of the employee’s calculation cards, or just one card. If the reason is specific to:
Absence record, for example, it is a pregnancy-related absence type, then one report is generated for each
of the employee’s calculation cards.
Statutory calculation card, for example, the temporary worker code is 1, then one report is generated for the
absence (or group of connected absences) for those cards that contain that trigger.
Where there are triggers on both the absence and the card, a report is created for each card.
Absence Report Parameters

For the Sickness, Sickness Recovery, and WAZO reports, you can run a report for an individual employee or the
entire legal employer.
SICKNESS, SICKNESS RECOVERY AND WAZO REPORT PARAMETERS EXPLAINED
Required
Parameter Name Description
or Optional
Extract Run Name Required User-defined extract name.
Start Date Required Report will include valid absences with a start date on or after this date.
End Date Required Report will include valid absences with a start date on or before this date.
Legal Employer Required You must select the legal employer name. Reports will be generated for all valid
absences in the selected legal employer.
Employee Name Optional If Withdraw Previous Report is No, you can leave this blank, and create the reports for all
valid absences for the selected legal employer.
If Withdraw Previous Report is Yes, you must select the name of an employee in the
specified legal employer.
Withdraw Previous Required Defaults to No. Select Yes to rerun an existing report in withdrawal mode.
Report
Absence Optional Select the absence record if you are withdrawing a report. Otherwise, you can leave it
blank.
Test Mode Required Defaults to No. Select Yes to send an initial test report to the UWV. (Reports sent in this
mode are not retained by the UWV so do not need to be withdrawn.)
LONG-TERM SICKNESS AND LONG-TERM SICKNESS RECOVERY PARAMETERS EXPLAINED
Required or
Parameter Name Description
Optional
Extract Run Name Required User-defined extract name.
Legal Employer Required You must select the legal employer name. Use this field to limit the results of the
Employee Name parameter that follows.
Employee Name Required You must select the employee name.
Withdraw Previous Report Required Defaults to No. Select Yes to rerun an existing report in withdrawal mode.
Absence Case Required You must select the name of the absence case for which you are running the report.
(The employee may have multiple absence cases.)
Test Mode Required Defaults to No. Select Yes to send an initial test report to the UWV. (Reports sent in
this mode are not retained by the UWV so do not need to be withdrawn.)
Withdrawing Existing Reports

You can withdraw a report that was previously submitted to the UWV, for example, because it contains incorrect
information. To withdraw an existing report by running the report again:
» Select Yes in the Withdraw Previous Report parameter
» Select the employee whose report you wish to withdraw
This creates a copy of the existing report, but the value reported in the IndVerzoekTotIntrekken report tag is 1 (Yes),
instead of 2 (No).
A report that contains 1 in the IndVerzoekTotIntrekken report tag is an indicator to the UWV to discard the report.
You should only withdraw a report on an individual employee and absence basis. This is to prevent an unintentional
bulk withdrawal of reports that are actually correct.
Once you have withdrawn a report, the absence is available for reporting again. (For example, after you have made
any corrections, you could run a replacement report for the absence.)
A message is raised if you try to change the dates on an absence that was previously reported. The purpose of this
validation is to warn you that you may wish to withdraw the existing report before you make changes to the absence.
Create Absence or Report 1 is Yes

Is Report
Start Add Absence(s) to Run Report – Created Send to UWV End
Correct?
GL Absence Case
Withdraw Previous IndVerzoekTotIntrek No

Report parameter = No ken tag = 2 (No)
Run Report –
Withdrawal
Parameter = Yes
Report 1 is
(re)created
IndVerzoekTotIntrekken tag =
1 (Yes) – UWV will discard this
report
Make Corrections
Run Report –
Withdrawal
Parameter = No
IndVerzoekTotIntrekken tag = 2 Report 2 is

(No) - UWV will retain this report Created
Send to UWV End
Figure 2. Run Digital Absence Reports, Including Withdrawals
Reporting Multiple Absences in One Report

It is possible to report multiple sickness-related absences in the Sickness, Sickness Recovery, Long-Term Sickness
and Long-Term Sickness Recovery reports. (The WAZO report is for a single absence only.)
A report can only include multiple absence records if they are grouped together in an absence case (connected
absences). Any absence record is reported only once (excluding withdrawn reports).
A report containing multiple absence records will extract the details of the most recent absence record, where
appropriate. For example, the Sickness Report will include the sickness notification date of the most recent absence
because the Notification Date tag DatOntvangstMeldingWerkgever is reported once only.
Consider the following example:
Absence Case 1 comprises the following absences:
» Absence 1: 01-Jan-2017 to 11-Jan-2017
» Absence 2: 18-Jan-2017 to 23-Jan-2017
» Absence 3: 29-Jan-2017 to (open-ended)
Each absence is:
» Added to the absence case on its start date.
» End dated in the application the day after it ends.
Sickness report is scheduled to run two-weekly, e.g. 31-Dec-2016, 15-Jan-2017, 31-Jan-2017, etc.
Start Date
Report Date End Date Parameter Absences Reported
Parameter
31-Dec-2016 15-Dec-2016 30-Dec-2017 Null
15-Jan-2017 31-Dec-2016 14-Jan-2017 Absence 1. Start date falls within the date range of
the parameters.
31-Jan-2017 15-Jan-2017 30-Jan-2017 Absence 2 – reported as a connected absence

Absence 3 – this is the most recent absence; its
details will be used for in the report.
Each absence record is updated to include the Sickness Report Date.
Sickness Report
The Sickness report can include absences of the following types:
Pregnancy-Related Sickness
Postnatal Sickness
Organ Donation
Work Accident
Sickness
You can run the report at the following levels:
Legal employer
Employee
Absence record
Reports are generated either for an individual absence, or, if they are grouped together in a Gatekeeper Law
absence case, the related absences are included in a single report. The details of the most recent absence are
provided and only the dates of the earlier absences are provided
You can refer to Sickness Report parameters in the Absence Report Parameters section.
Report Triggers
Not all sickness absence types are eligible for payment by the UWV and therefore do not require a Sickness Report.
Absences that have one or more of the following indicators associated with them are liable for reporting.
SICKNESS REPORT TRIGGERS
Sickness Report Reason Code

Trigger Type Description
Selected Reported
Employee is Temporary worker sickness The Temporary Worker Code on the calculation card is 01
temporary worker any of the following:
1 – Phase 1
2 – Phase 2
17 - Phase A with temporary worker condition
Employee is standby Standby employee sickness The Influence Code on the calculation card is any of the 02
worker following:
D - Temporary worker without obligation to work
E - Temporary worker with obligation to work
Employee is Sickness after end of employment The employee is sick as of the termination date. 03
terminated
Article 29 B applies Sickness according to Article 29b 04

to employee.
Article 4 or 5 applies Sickness according to Article 4 or 5 05

to employee.
Pregnancy-related Pregnancy-related sickness Absence type associated with Dutch Pregnancy-Related 06

absence Sickness Legislative Grouping Code
Postnatal sickness Postnatal sickness Absence type associated with Dutch Postnatal Sickness 07
absence Legislative Grouping Code
Organ donation Organ donation Absence type associated with Dutch Organ Donor 08
absence Legislative Grouping Code
The reason for the report is specified in the Sickness Report Reason DDF segment on the absence record. It is
defaulted as described in the previous table and reported in the CdRedenAangifteAo report tag using the two-digit
numeric code shown in the last column Code Reported.
Reported Dates
The report includes the following absence dates (in the format YYYYMMDD):
SICKNESS REPORT: ABSENCE DATES REPORTED
Date Report Tag Description
Date of Reporting DatOntvangstMeldingWerkgever Notification Date field (enabled on absence type). The date when an employee
Sick notifies their employer of their absence. This defaults to the system date, but
can be overridden. If multiple absences exist, the notification date of the most
recent absence in the case is used.
Start Date of DatEersteAoDag Absence Start Date. One date per report. If multiple absences exist, this is the
Sickness date of the most recent absence in the case.
First Day of Previous DatBAo Absence Start Date of each connected (earlier) absence in the case, if multiple
Connected Absence absence records exist. There can be multiple dates in one report.
Last Day of Previous DatEAo Absence End Date of each connected absence in the case, if multiple
Connected Absence absences exist. There can be multiple dates in one report.
For example, employee has one open-ended sickness absence with a start date of 01-Feb-2017 and they notified
their employee that day. The start and end date report parameters are 01-Feb-2017 and 08-Feb-2017.
SICKNESS REPORT: ABSENCE DATES REPORTED (EXAMPLE)
Date Report Tag Date Reported
Date of Reporting Sick DatOntvangstMeldingWerkgever 20170201
Start Date of Sickness DatEersteAoDag 20170201
First Day of Previous Connected Absence DatBAo <Null>
Last Day of Previous Connected Absence DatEAo <Null>
In the next example, there are two related sicknesses in an absence case, neither of which has been reported yet:
Absence 1: 01-Feb-2017 to 15-Feb-17
Absence 2: 23-Feb-17 is open-ended
The start and end date report parameters are 01-Feb-2017 and 28-Feb-2017.
SICKNESS REPORT: ABSENCE DATES REPORTED (EXAMPLE)
First Day of Previous Connected Absence DatBAo 20170201
Last Day of Previous Connected Absence DatEAo 20170215
Sickness Recovery Report

The Sickness Recovery Report can include one or more absences that were previously reported in the Sickness
Report and from which the employee has made a full or partial recovery.
There is information on the Sickness Recovery Report parameters here.
Report Triggers
The trigger for a Sickness Recovery Report is either of the following:
Full recovery from either full-time or partial sickness. Indicated by the presence of an absence end date.
Partial recovery from sickness. Indicated by a Partial Recovery Percentage and a Partial Recovery Start
Date. For example, a full-time employee is now returning to work mornings only as of the recovery start date.
Additionally, the absence must already display a Sickness Report Date. (You cannot report sickness recovery if you
have not already reported the sickness itself.)
You record partial recovery in the Legislative Information region of the absence record.
Multiple reports can exist for one absence (or connected absences) if new recovery information is added. It is not
necessary to withdraw one report before you submit the next to the UWV, if each report contains different recovery
information. Withdrawal of a Sickness Recovery Report is required only when reported information is incorrect.
Reported Dates
SICKNESS RECOVERY REPORT: ABSENCE DATES REPORTED
Date of Reporting Sick DatOntvangstMeld Notification date on absence record. Date when employee notified employer of their
ingWerkgever absence. Defaults to system date, but can be overridden. If multiple absences are
included in the same report, this is the notification date of the most recent absence in
the case.
Start Date of Sickness DatEersteAoDag Absence Start Date. One date per report. If multiple absences exist, this is the date of
the most recent absence in the case.
First Day of Full Recovery DatHersteld The first full day of recovery. This is only reported if the absence has an end date. It is
reported as the absence end date + 1 day.
First Day of Partial Recovery DatWerkhervatting The day on which an employee partially recovered. This is stored on the Partial
Recovery Date field.
Note: The Partial Recovery Percentage field is for administrative purposes only so that you can see the most recent
recovery rate that was reported to the UWV. It is not included in the report.
Sickness Recovery Report Example:
Absence 1 - Start Date 01-Mar-2017. Previously included in the sickness report.

Absence record updated 22-Mar-2017 to show 25% recovery on that date. Recovery report required.
Absence record updated 29-Mar-2017 to show 50% recovery on that date. Recovery report required.
Absence record ended 10-Apr-2017. Recovery report required.
The Sickness Recovery Report is also scheduled to run daily.
In this example, three reports are required by the UWV because each contains new recovery information. The dates
reported in each are shown below:
SICKNESS RECOVERY REPORT 1: ABSENCE DATES REPORTED (EXAMPLE)
First Day of Full DatHersteld <Null>

Recovery
First Day of Partial DatWerkhervatting 20170322 – Shows 25% recovery.

Recovery
First Day of Full DatHersteld <Null>

Recovery
First Day of Partial DatWerkhervatting 20170329 - Shows 50% recovery.

Recovery
First Day of Full DatHersteld 20170411 (absence end date + 1) – shows full recovery.
Recovery
First Day of Partial DatWerkhervatting <Null>

Recovery
Long-Term Sickness Report
The Long-Term Sickness Report can include absences of the following types:
Sickness
Work Accident
The report is not generated for absence types of Pregnancy-Related Sickness, Postnatal Sickness, or Organ
Donation because they already have a (short-term) Sickness Report and the UWV does not require a Long-Term
Sickness Report for those absence types.
It is based on the assumption that if an absence (or group of related absences) requires a Long-Term Sickness
Report, it is being managed according to the Gatekeeper Law. Therefore, you run this report on an individual
Gatekeeper Law absence case basis. A Gatekeeper Law checklist task will be allocated to the case manager to
notify them when the report is due to be run.
The DDF segments for this report are displayed on the absence case (not the absence type), as that is the level at
which the Long-Term Sickness Report and Long-Term Sickness Recovery Report are created.
Select the Netherlands context on the absence case to display the Long-Term Sickness Report Date and Long-
Term Sickness Withdrawn Date segments.
For information on Long-Term Sickness Report parameters, refer to the Absence Report Parameters section.
Report Triggers
There are no inbuilt triggers for this report. Run this report for a Gatekeeper Law absence case as needed or when
prompted by the Gatekeeper Law checklist task.
Reported Dates
LONG-TERM SICKNESS REPORT: ABSENCE DATES REPORTED
Absence Start Date DatBAo The start date of each absence record in the case.
Absence End Date DatEAo The end date of each absence in the case. Optional information, although the
assumption is that any previous absences in a case will have end dates, although
the most recent absence may well be open ended.
For example, an absence case includes 2 absence records, the most recent of which is open ended:
Absence 1: 01-Jan-2017 – 17-Jan-2017
Absence 2: 31-Jan-2017 – <open ended>
The following dates are reported in the Sickness Period region of the report:
LONG-TERM SICKNESS REPORT: ABSENCE DATES REPORTED EXAMPLE
Absence Start Date DatBAo 20170101
Absence End Date DatEAo 20170117
Absence Start Date DatBAo 20170131
Absence End Date DatEAo <Null>
Long-Term Sickness Recovery Report

The Long-Term Sickness Recovery Report reports an absence case that was previously reported in the Long-Term
Sickness Report and from which the employee has fully recovered. (The most recent record in the case has ended.)
As with the Long-Term Sickness Report, this report is run on an individual Gatekeeper Law absence case basis.
The DDF segments for this report are displayed on the absence case (not the absence type), as that is the level at
which the Long-Term Sickness Report and Long-Term Sickness Recovery Report are created.
Select the Netherlands context on the case to display the Long-Term Sickness Recovery Report Date and Long-
Term Sickness Recovery Report Withdrawn Date fields.
There is information on the Long-Term Sickness Recovery Report parameters here.
Report Triggers
As with the Long-Term Sickness Report, you run this report on an individual absence case basis.
Reported Dates
LONG-TERM SICKNESS RECOVERY REPORT: ABSENCE DATES REPORTED
First Day of Absence DatEersteAoDag Start date of the earliest absence in the case.
First Day of Recovery DatHersteld End Date of the most recent absence in the case + 1 day (the first full day on
which the employee is able to return to work).
For example, an absence case contains two absence records, which have now ended:
Absence 1: 01-Jan-2017 to 17-Jan-2017

Absence 2: 31-Jan-2017 to 24-Feb-2017
LONG-TERM SICKNESS RECOVERY REPORT: ABSENCE DATES REPORTED EXAMPLE
First Day of Absence DatEersteAoDag 20170101 (absence 1 start date)
First Day of Recovery DatHersteld 20170225 (most recent absence end date +1 day)
WAZO Report
The WAZO report enables you to report a single absence of one of the following types to the UWV:
Maternity
Adoption
Foster Care
For information on WAZO Report parameters, the Absence Report Parameters section.
Report Triggers
All maternity, adoption and foster care absences must be reported to the UWV to comply with legislation. If you have
configured your WAZO-related absence types with the appropriate legislative grouping codes, those absences can
be included in the WAZO report, depending on the report parameters selected.
Reported Dates
WAZO REPORT: ABSENCE DATES REPORTED
Absence Start Date DatGewensteAanvangWazo Actual Start Date on WAZO absence record. An employee will usually agree
their start date some weeks before the absence starts, so an actual end date
should exist on the absence record by the time the report is run. However, in
the exceptional cases where there is a planned start date only, that will be
reported.
Estimated Date of DatVermoedelijkeBevalling Expected Date of Childbirth on absence record. This is specific to absence
Childbirth types configured for maternity. It does not apply to foster care or adoption.
There is no requirement to report on the actual date of birth.
For example, an employee has one maternity absence record:
Absence 1: 11-Nov-2017 to 10-Nov-2018. The expected date of birth is 15-Dec-2017.
WAZO REPORT: ABSENCE DATES REPORTED EXAMPLE
Absence Start Date DatGewensteAanvangWazo 20171101
Estimated Date of Childbirth DatVermoedelijkeBevalling 20171215
Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200
CONNECT W ITH US
blogs.oracle.com/oracle
Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means,
twitter.com/oracle electronic or mechanical, for any purpose, without our prior written permission.
oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0920
White Paper Title: Oracle Fusion HCM (Netherlands): Statutory Absences and Functional Considerations
September 2020
Author: Julia Margetson

Oracle Fusion HCM (Netherlands) :: Dutch Statutory Absences Implementation and Functional Considerations

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Fusion HCM (Netherlands) :: Dutch Statutory Absences Implementation and Functional Considerations

Uploaded by

Copyright:

Available Formats

Oracle Fusion HCM (Netherlands):

Dutch Statutory Absences Implementation

Absence Record Maintenance 2

Enabling Absence Record Flexfield Contexts with Legislative Grouping Codes 2

Dutch Absence Setup Summary 3

Setting Up Sickness Absence Plan and Sickness Absence Types 4

Sickness Absence Plan 4

Sickness Absence Type 4

The Gatekeeper Law (Wet Verbetering Poortwachter) 6

Sickness-Related Absence Types for Gatekeeper Law Processing 7

Gatekeeper Law Absence Category 7

Gatekeeper Law Checklist Template 9

Reviewing the Template 9

Copying and Modifying the Predefined Template 9

Modified Checklist Template: Points to Consider 9

Selecting the Modified Checklist Template for a Legal Employer 10

Gatekeeper Law Case Manager 10

Assigning Case Manager Responsibility Type 10

Overriding the Case Manager Responsibility 11

Creating a Gatekeeper Law Absence Case 11

Gatekeeper Law Start Date Example 12

Start and End Dates for Part-Time Absences 13

Managing the Gatekeeper Law Documents 13

Creating Gatekeeper Law Documents 13

Gatekeeper Law ESS Process 14

Gatekeeper Law Security Setup 15

Maternity, Adoption, and Foster Care Absence Plan 16

Maternity, Adoption, and Foster Care Absence Types 16

Digital Absence Reports 16

Setting Up Digital Absence Reports 17

Absence Management Setup: Absence Types, Reasons and Categories 17

Global Human Resources Setup 17

Review Statutory Deductions and Reporting Card 18

Managing TRU Sickness Report Details 18

Overriding Absence Contact Details 19

Running the Digital Absence Reports 19

Report Date Fields 19

Reporting Level and Output 20

Absence Report Parameters 21

Withdrawing Existing Reports 21

Sickness Recovery Report 25

Long-Term Sickness Report 28

Long-Term Sickness Recovery Report 29

Figure 2. Legislative Grouping Code Field 2

Figure 3. Absence Record: Legislative Information Region 2

Figure 4. Create Absence Type Page. 4

Figure 5. Sickness Absence Type: General Attributes 5

Figure 6. Absence Type: Add Plan 5

Figure 7. Absence Type: Work Accident Absence Reasons 6

Figure 8. Absence Type: Reason Field 6

Figure 9. Absence Type: Dates and Duration 7

Figure 10. Absence Type: Supplemental Absence Details 7

Figure 11. Gatekeeper Law Setup Flow 9

Figure 12. Gatekeeper Law Absence Category 10

Figure 13. Absence Category: Select and Add Type 10

Figure 14. Search Checklist Templates 11

Figure 15. Gatekeeper Law: Review Checklist Template 11

Figure 16. Gatekeeper Law: Search Checklist Templates 12

Figure 17. Gatekeeper Law: Duplicate Checklist Template 12

Figure 18. Gatekeeper Law: Edit Checklist Template Copy 13

Figure 20. Manage Case Manager Area of Responsibility 15

Figure 21. Gatekeeper Law: Create Case Manager Area of Responsibility 15

Figure 22. Absence Case: Case Manager Override 16