NL HR Setup PDF

Oracle Fusion HCM (Netherlands):
HR Implementation and Functional Considerations

R13 DRAFT 2
ORACLE WHITE PAPER |A
MUAG
Y U2S0T1 72 0 1 7
ORACLE WHITE PAPER |MAY 2017

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 Oracles products
remains at the sole discretion of Oracle.
ORACLE FUSION HCM (NETHERLANDS): HR IMPLEMENTATION AND FUNCTIONAL CONSIDERATIONS

Table of Contents
Disclaimer 1
Introduction 6
Whats in this Document 6
Other Information Sources 6
Document Updates 2
Comments and Suggestions 2
Organization Structures 3
Introduction 3
Enterprise 3
Creating an Implementation Project 3
Defining Enterprise Structures 5
Legal Jurisdictions 5
Legal Addresses 7
Legal Authorities 8
Legislative Data Groups 10
Legal Entities 11
Legal Employers and Payroll Statutory Units (PSUs): Overview 11
Legal Reporting Units and Tax Reporting Units: Overview 11
Creating Legal Entities 11
Legal Entity HCM Information for Legal Employers and Payroll Statutory Units 13
Legal Reporting Units 15
Legal Reporting Unit Registrations 17

Legal Reporting Unit HCM Information 17
Business Units 22
Workforce Structures 23
Locations 24
Divisions 25
Departments 27
Reporting Establishments 28
Organization Structure Models Supported by Dutch Localization 28
Roles in Organization 29
Grades 29
Jobs 31
Positions 32
Personal Data Setup 34
Addresses 34
Address Validation 34
Address Mapping 34
Name Styles and Name Formats 35
Name Style 35
Name Formats 37
Legislative Information 40
National Identifiers 41
Validations for BSN Examples 42
Hiring a Worker 43

Employment Validations for the Dutch Localization 47
Maintaining Person and Employment Information 48
Person Management 48
Employment Management 53
Adding a Nonworker 53
Terminating a Worker 56
Payroll Processing After Termination 57
HR Reports for the Netherlands 58
First Day Notification Report 58
Corrections 59
Validations 59
Audit Report 59
Prerequisites 59
Run the First Day Notification Report 60
Viewing Report Output 61
Viewing Payroll Flows for a Report 61
Corrections 62
Example of Correction 63
Viewing the Report Output 63
Additional Information for Payroll Interface 66
Tax Reporting Unit (TRU) Calculation Card 66
Validations for TRU Calculation Card 70
Personal Calculation Card Automatic Creation 70

Prerequisites 70
Review and Update an Automatic Statutory Deductions and Reporting Card: 70
Personal Calculation Card Manual Creation 76
Prerequisites 77
Creating the Statutory Deductions and Reporting Card Manually 77
Creating Calculation Components 79
Entering Calculation Component Details for Tax component: 80
Entering Calculation Component Details for Special-Rate Tax component: 80
Creating Enterable Calculation Values for Special-Rate Tax component: 81
Association Details 84
Validations for Personal Calculation Card 85
Banking Setup 86
Banks 86
Bank Branches 87
Bank Accounts 88
Assigning Legal Entities to Primary Ledger 89
Organization Payment Methods 89
Net Pay Balance 91
Consolidation Groups and Payroll Definitions 93
Consolidation Groups 93
Payroll Definitions 93
Person Payment Information 96
Assigning a Payroll to the Employee 96

Assigning Payment Methods to the Employee 97
Elements 98
Elements and Element Templates 98
Availability of Element Template Functionality Based on Customer License 98
Setting up the License Information (Before Release8) 98
Setting up the License Information (Release8 onwards) 100
Using Element Templates 101
Element Entries 105
Salary Basis and Compensation 105
Individual Compensation 106
Assigning Salary Basis and Compensation to a Payee 108
Adding a Salary 108
Adding Compensation 109
Running Global Reports for Netherlands 111
Worker Data Validation Report 111
Validations Delivered for the Netherlands 111
Run Worker Data Validation Report 112
Payroll Balance Report 114
Run Payroll Balance Report 114
Element Result Report 117
Run Element Result Report 117
Common Lookups Customization Level 120
Conclusion 121

Glossary 122

Introduction
This paper identifies and describes HR setup tasks for Oracle Fusion Human Capital Management (HCM) for the
Netherlands.
Whats in this Document

This document is intended to support the implementation team in understanding:
The organizational structures that need to be defined to manage HR processes for Dutch localization.
Netherlands-specific data that needs to be provided.
Where and how predefined Netherlands-specific data can be integrated with customer-specific data.
The data that needs to be defined to manage work relationships in the Dutch localization.
Netherlands-specific business rules that have been implemented.
The HR processes that can be executed for Dutch localization.
Information required for supporting the interfacing or transferring data to a third-party payroll system.
The migration process from a legacy system, by identifying Netherlands-specific fields that need to be populated
by such migration.
An additional white paper, Oracle Fusion HCM (Netherlands): Dutch Statutory Absences Implementation and
Functional Considerations, contains information about implementing:
The Gatekeeper Law (Wet Verbetering Poortwachter) statutory process

Sickness and Maternity Absences and the Digital Absence Reports
Includes configuring your absence types to map to legislative grouping codes.
Note: Flexfields described in this document are Developer Descriptive Flexfields (DDF) that must not be customized
at an implementation level. Customer Descriptive Flexfields (DFFs) are the fields delivered by the product to be
used for customization during implementation.
This documentation can also be beneficial to end users who run application processes after implementation.
Note: This document should not be considered a comprehensive guide for HR implementations. The focus of this
document is Netherlands-specific processes and information. For information about generic tasks, the
implementation team should refer to documentation listed in the following section.
Other Information Sources

Oracle Fusion HCM (Netherlands): Dutch Statutory Absences Implementation and Functional Considerations:
<insert hyperlink once published on MOS>
Oracle Fusion Workforce Deployment Implementation Guide:
http://docs.oracle.com/cd/E28271_01/fusionapps.1111/e20379/toc.htm
Oracle Fusion On-Premise Quick Start Implementation Guide:
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1395863.1
Oracle Fusion Cloud Quick Start Implementation Guide:

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1471160.1
Oracle Fusion Global Payroll User Guide:

http://www.oracle.com/technetwork/fusion-apps/payrolluserguider4-1873385.pdf
Oracle Fusion Global Payroll Interface Guide:

http://www.oracle.com/technetwork/fusion-apps/payrollinterfaceguider4-1873384.pdf
1 | ORACLE FUSION HCM (NETHERLANDS): HR IMPLEMENTATION AND FUNCTIONAL CONSIDERATION

Document Updates
This document is based on the most current application release as of the documents publication date. Content is
updated as needed only to reflect major changes to existing features or when significant new features are added to
the Dutch localization. For this reason, it is possible that some minor UI differences may exist between the version
being implemented and the version described in this document.
Comments and Suggestions

Your comments are important to us. We encourage feedback about Oracle Fusion Applications Help and guides.
Please send your suggestions to: oracle_fusion_applications_help_ww_grp@oracle.com.
You may also use the Send Feedback to Oracle link in the footer of Oracle Fusion Applications Help.

Organization Structures
Introduction
Before a customer can hire a worker in the Netherlands or run any country-specific process, the implementation
team must set up the organization structures required for the management of HR processes. You can perform all
setup tasks using the Functional Setup Manager (FSM).
The following sections describe how to create an implementation project and define enterprise structures and
related objects required for the Dutch localization implementations. These structures, which typically contain
country-specific information, must be defined before you can create application users.
Note: For the complete set of setup tasks required for a full implementation, please refer to the documents listed
under Other Information Sources.
Enterprise
The Enterprise classification represents the top structure in the organization that supports partitioning requirements
for Oracle Fusion applications. A person exists within the context of an enterprise. If a person is associated with two
enterprises, the person has two person records.
Once the users log in, they work in the context of an enterprise. All the structures explained below are created within
that context.
Since there is no concept of legislation at the enterprise level, no Netherlands-specific attributes are stored at this
level; these attributes must be stored at the level of other structures such as legal entity.
This document does not describe enterprise setup since this structure is defined at a higher level than HR and is
used across product lines.
Creating an Implementation Project

Setup tasks for organization structures should be defined in an implementation project. Follow these steps to create
an implementation project:
1. Sign in to the Oracle Fusion application using a role that has the profile of a super-user and privileges to create all
organizational structures:
Figure 1. Application Login Details

2. Select Setup and Maintenance from the Navigator:
Figure 2. Setup and Maintenance Navigation
3. On the Implementation Projects tab, click Create:
Figure 3. Create Implementation Project

4. On the Create Implementation Project page, enter the required information and click Next:
Figure 4. Create Implementation Project: Basic Information

5. Select Workforce Deployment as the offering, since this parent project contains all the tasks needed to set up
HCM organizational structures:
Figure 5. Create Implementation Project: Select Offerings

6. Click Save and Open Project.
Defining Enterprise Structures

You can now begin the process of defining enterprise structures. All setup tasks are located in the implementation
project task list under Workforce Deployment > Define Common Applications Configuration for Human Capital
Management > Define Enterprise Structures for Human Capital Management, as shown here:
Figure 6. Enterprise Structures Task List
Legal Jurisdictions
All legal entities must be registered against a jurisdiction that is governed by a legal authority. The legal jurisdiction
is a combination of a physical territory (like group of countries, country, a state or a city) and a legislative category
(such as Commerce Law), defined by the registration codes used by the government authorities to identify legal
organizations within the enterprise. Jurisdictions must be set up before creating registrations, because a jurisdiction
is required in the registration process. A jurisdiction may also have a start date and end date to show when the
jurisdiction is effective and when you can register against it. There is a predefined jurisdiction for Netherlands, that

is, Commerce Law. There is no system or functional specific requirement to register it for the Dutch HCM
localization. Netherland Commerce Law is used because it is setup as the identifying jurisdiction.
You must create the Netherlands Tax Office jurisdiction:

1. Select Manage Legal Jurisdictions in the implementation project task list:
Figure 7. Manage Legal Jurisdictions: Task

2. Create Netherlands Tax Office Legal Jurisdictions. Click Create in Manage Legal Jurisdictions page and enter
the required information:
Figure 8. Search Legal Jurisdictions
Figure 9. Create Legal Jurisdiction

The values for this jurisdiction are stored in the record XLE_JURISDICTIONS_B.
XLE_JURISDICTIONS_B
Name Column Values Comments
Name NAME Netherlands Tax Office
Territory TERRITORY Netherlands
Legislative LEGISLATIVE_CATEGORY Wage Tax

Category
Identifying IDENTIFYING No
Legal Entity LEGAL_ENTITY_REGISTRATION_CODE RN Indicates that the Legal Entity Registration

Registration number is used for registration. Registration
Code codes are setup in XLE Lookups. The
default value RN is used for the Netherlands
with the lookup type XLE_REG_CODE.
Legal LEGAL_REPORTING_UNIT_REGISTRATION_ HRX_NL_TRN Indicates that the legal reporting unit Tax
Reporting Unit CODE registration number is used to do
Registration registration. The value HRX_NL_TRN is
Code predefined for the Netherlands in the lookup
type XLE_REG_CODE_EST.
You can create additional jurisdictions as needed using the Manage Legal Jurisdictions task. Such additional
jurisdictions can be used in the registration process of legal entities or legal reporting units of the enterprise.
Legal Addresses
A legal address is the address of record for an entity. For example, the legal address of a legal authority is used in
communications with that authority. No legal addresses are predefined for the Netherlands. You must create legal
addresses for all organizational units of the enterprise.
To define legal addresses:

1. Select Manage Legal Addresses in the implementation project task list:
Figure 10. Manage Legal Addresses Task

2. On the Manage Legal Addresses page, click Create.
3. On the Location Create page, enter the address information:

Figure 11. Create Location
4. Click OK.
Legal Authorities
Legal authorities are the government entities with which an enterprise interacts, for example to send legal reports.
No legal authorities are predefined for the Netherlands. You must create a legal authority for each government
entity, such as a local tax office, that has a relationship with the enterprise. Later, you register each legal entity you
create with a legal authority.
To define legal authorities:

1. Select Manage Legal Authorities in the implementation project task list:
Figure 12. Manage Legal Authorities Task

2. On the Manage Legal Authorities page, click Create.
Figure 13. Create Legal Authority

3. On the Create Legal Authority page, select the Tax Authority Type based on the type of interaction. Typically, this
is set to Collecting and reporting.
Figure 14. Create Legal Authority: Basic Details

4. Click on Create Address icon to open the Create Address screen:
Figure 15. Create Legal Authority Address

5. Go back to Tax Authority page after adding the address and click the add Legislative Categories icon:
Figure 16. Create Legal Authority Legislative Category

6. Click Save and Close.
Legislative Data Groups

A legislative data group (LDG) defines the payroll and related data partition context for a user, allowing customers to
partition their payroll data. Although an LDG is not an organization, it is included here for completeness.
Each LDG has a context of a country.
Each PSU is attached to one LDG and an LDG may be attached to multiple PSUs.
Payroll configuration setup can be done at following levels:

Country (setup is applicable for all the LDGs or PSUs of the country).
LDG (setup applicable for a set of PSUs that belongs to this LDG).
PSU
An LDG must be defined in an HR-only implementation to migrate the employee-level information, such as payment
methods or salary, to a third-party payroll system.
If an LDG is associated with a PSU, then whenever you create payroll data, the LDG can be derived from the payroll
relationship for the transaction using the PSU association.
To define an LDG:
1. Select Manage Legislative Data Groups in the implementation project task list:
Figure 17. Manage Legislative Data Groups Task

2. On the Manage Legislative Data Groups page, click Create.
3. On the Create Legislative Data Group page, provide the required information and click Submit:
Figure 18. Create Legislative Data Group

Legal Entities
A legal entity is an entity unequivocally identified and given rights and responsibilities under Commercial Law,
through registration with the territorys appropriate authority. Legal entities have the responsibility to account for
themselves (balance sheet, income statement, specified reports) to company regulators, taxation authorities, and
owners according to rules specified in the relevant legislation.
Legal Employers and Payroll Statutory Units (PSUs): Overview

Oracle Fusion recognizes different types of legal entities:
A legal employer is a legal entity that employs workers. In the Netherlands, the concept of legal employer
corresponds to the concept of company.
A PSU is a legal entity that is responsible for paying workers, including the payment of payroll tax and social
insurance. A PSU can pay and report on payroll tax and social insurance on behalf of one or many legal entities,
depending on the structure of your enterprise.
PSUs provide a way to group legal employers so that certain statutory calculations, such as court orders and some
taxes, can be performed at a higher level. A legal employer can belong to only one PSU, and the PSU represents
the highest level of aggregation for a person. No balances are aggregated across PSUs.
In the Netherlands, a legal entity is a legal employer as well as PSU. You must define a legal entity that is both a
legal employer and a PSU.
No legal entities are predefined for the Netherlands. You must create all legal entities that apply to the enterprise
you are setting up.
Legal Reporting Units and Tax Reporting Units: Overview

A legal reporting unit (LRU) is the lowest level component of a legal structure that requires registrations. It is used to
group workers for the purpose of tax and social insurance reporting or to represent a part of your enterprise with a
specific statutory or tax reporting obligation. In the Netherlands, the concept of legal reporting unit corresponds to
the concept of an establishment.
If LRUs are used in Oracle Fusion Payroll for tax reporting purposes, then they are considered as tax reporting units
(TRUs). In the Legal Entity Configurator, when you create an LRU that belongs to a PSU, the application
automatically creates an LRU in HCM and associates it with the parent PSU. There can be multiple LRUs under one
Legal Employer or PSU in the Netherlands. You can define more LRUs under a Legal Employer or PSU in addition
to the one created automatically
LRU can be marked as TRU or Reporting Establishment or both. TRUs are especially relevant for the Netherlands
because the TRU establishes the connection with a set of external organizations. For the Netherlands, the TRUs
must have a one to one relationship with the reporting establishments. You must define an LRU as both a TRU and
Reporting Establishment.
Creating Legal Entities

To define legal entities:
1. In the Setup and Maintenance work area, select the Manage Legal Entity task:

Figure 19. Manage Legal Entity Task
2. Click Go to Task.
3. On the Select Scope page, select Search Legal Entities, and Select and Add in the Legal Entity field:
Figure 20. Manage Legal Entity: Select Scope

4. Click Apply and Go to Task.
5. Click Create in the search results. The Create Legal Entity page is displayed:
Figure 21. Create Legal Entity

6. Provide the required information, noting the following:
The Legal Entity Identifier is an internal code.
You must have previously defined an identifying jurisdiction.
You must have previously defined the legal address for the legal entity.
Start date and end date are optional, but it is recommended to enter the start date.
You must select both the Payroll Statutory Unit check box and the Legal Employer check box.

The type of registration information required is based on the identifying jurisdiction (Netherlands Commerce
Law jurisdiction).
Legal Entity HCM Information for Legal Employers and Payroll Statutory Units
You must specify additional information about legal entities for the Oracle HCM processes.
To provide HCM information:

8. Select Manage Legal Entity HCM Information task:
Figure 22. Manage Legal Entity HCM Information

9. Set the scope for this task if it is not selected already:
Figure 23. Manage Legal Entity Select Scope
10. Search for the legal entity you created.

11. If the entity is a legal employer, complete the required fields on the Legal Employer tab And review the
details:

Figure 24. Edit Legal Entity: Legal Employer
The Dutch localization supports all employment models. Refer to the section on employment models in chapter
Define Enterprise Structures for Human Capital Management of Oracle Fusion Applications Workforce Development
Implementation Guide (http://docs.oracle.com/cd/E28271_01/fusionapps.1111/e20380/toc.htm).
12. In the Dutch Legal Employer Details region, select the checklist template that is used for all the
Gatekeeper Law checklists allocated in your legal employer. The predefined Gatekeeper Law checklist
template is selected by default:
Figure 25. Edit Legal Entity: Dutch Legal Employer Details

13. Click the Payroll Statutory Unit tab:
Figure 26. Edit Legal Entity: Payroll Statutory Unit

14. Complete the fields on this tab and click Submit.
The Fiscal Year Start for a customer in the Netherlands must be set to January 1st of the year the enterprise goes
live on the Oracle Fusion product.
The LDG is associated at the PSU level.
For more information about legal entities, refer to the Define Enterprise Structures for Human Capital Management
chapter, Oracle Fusion Applications Workforce Deployment Implementation Guide, Oracle Fusion Applications
Workforce Development Implementation Guide, or Oracle Fusion Applications Compensation Management
Implementation Guide.
Legal Reporting Units

To create an LRU:
1. Select Manage Legal Reporting Unit HCM Information in the task list:
Figure 27. Define Legal Reporting Units for Human Capital Management Task
2. In the Select Scope window, select Manage Legal Reporting Unit and Select and Add in the Legal
Reporting Unit field. Then click Apply and Go to Task:
Figure 28. Define Legal Reporting Units: Select Scope

1. On the Select and Add: Legal Reporting Unit page, an LRU with the same name as the previously created
legal entity is automatically created. This is the primary legal reporting unit for the legal entity. You can
change the name, if required:
Figure 29. Manage Legal Reporting Units
Figure 30. Manage Legal Reporting Units: Addresses

2. To create a second LRU for this legal entity, go to the Select Scope page.
3. Select Manage Legal Reporting Unit, the name of the legal entity, and click Create New in the Legal
Reporting Unit field.
Figure 31. Manage Legal Reporting Unit: Select Scope

4. Click Apply and Go to Task.

5. Click Create. Enter the required information on the Create Legal Reporting Unit page:
Figure 32. Create Legal Reporting Unit

Legal Reporting Unit Registrations

To create a registration with the Tax Office:
1. Set the scope for this task by selecting the parent legal entity and then the legal reporting unit, as
described in previous tasks.
2. Select Manage Legal Reporting Unit Registration in the implementation project task list:
Figure 33. Manage Legal Reporting Unit Registrations Task

3. Click on Go to Task and create the registration for jurisdiction for the Netherlands Tax Office:
Figure 34. Edit Legal Reporting Unit Registrations
Legal Reporting Unit HCM Information

Additional information about LRUs (referred to as TRUs in this context) is required for Oracle Fusion HCM
processes.
To provide HCM information:

2. Select Manage Legal Reporting Unit HCM Information in the implementation project task list:
Figure 35. Manage Legal Reporting Unit HCM Information Task

3. On the Manage Tax Reporting Unit HCM Information page, select the legal reporting unit and click Tax
Reporting Unit and Reporting Establishment. This creates the TRU and reporting establishments for
that LRU.
Figure 36. Manage Legal Reporting Unit HCM Information Task

4. Review the Tax Reporting Unit Details:

Figure 37. Manage Legal Reporting Unit HCM Information
5. Enter information for the Wage Report and the digital absence reports. Select the context for each (Wage
Report Details and Sickness Report Details) and enter the required information for each. For more
information on how sender and contact details are reported in the digital absence reports, refer to Oracle
Fusion HCM (Netherlands): Dutch Statutory Absences Implementation and Functional Considerations.
WAGE REPORT INFORMATION
Field Name Description Required/Optional Default Value
Public Sector Checkbox The information Optional Unchecked by default.

Organization reported in this report
depends on whether the
organization is a public sector
organization or not.
Sender ID Numeric field (20 digits) Required
Contact Name Free text field Required
Phone Numeric field (14 digits). Required
Own Risk Cover Checkbox To specify Optional Unchecked by default.

whether there is insurance
cover other than WAO.
Payroll Frequency List Of Values This is used Required

to default the Payroll Period
field in the personal
calculation card (created
automatically). When entering
a new hire, the payroll for an
employee working for a Dutch
legal employer is validated
against the TRU Payroll
Frequency.

Figure 38. Manage Legal Reporting Unit HCM Information: Wage Report Information
6. Click on the Sickness Report details (contains information about the TRU required for the digital absence
reports):
SENDER DETAILS
Field Name Description Required/Optional
Sender Name Free text field Optional
Role Lookup type (NL_SICKNESS_REPORT_ROLE)

with the following values:
01 Message and content
02 Message only
Tax Registration Tax Registration Number must be in the format: Required

Number NNNNNNNNNLNN.
Contact Person or Free text field Optional

Department
Contact Phone 10 digit number Optional
CONTACT DETAILS
Field Name Description Require/Optional
Contact Type Lookup type (ORA_HRX_NL_SICK_CONT_TYPE) Optional

with the following values:
Organization include the same TRU-level
contact in all your digital absence reports
Line Manager include the employees line
manager in your digital absence reports
Contact Name Free text field Optional
Location (name of Free text field Optional

establishment)
Gender List of Values Optional
Contact Phone 10 digit number Optional

Figure 39. Manage Legal Reporting Unit HCM Information: Sickness Report Details
7. On the Manage Tax Reporting Unit HCM Information page, review the Reporting Establishment Details.
Figure 40. Manage Legal Reporting Unit HCM Information: Reporting Establishment Details
If data is migrated from a legacy system, the following Netherlands-specific fields need to be populated.
The following table shows the attributes of these Flexfields for record
PER_ORGANIZATION_INFORMATION_EFF (DESCRIPTIVE_FLEX_CONTEXT_CODE =
HRX_NL_ORG_WAGE_REPORT_INFO):
ORGANIZATION INFORMATION FOR WAGE REPORT FLEXFIELD CONTEXT
APPLICATION_COLUMN_NAME END_USER_COLUMN_NAME FLEX_VALUE_SET_CODE DESCRIPTION
ORG_INFORMATION1 PUBLIC_SECTOR_ORGANIZATION HRC_YES_NO Yes and No values
ORG_INFORMATION5 SENDER_ID HRX_NL_NUMBER_20 20 digits
ORG_INFORMATION2 CONTACT_NAME HRC_CHAR_80 80 characters
ORG_INFORMATION6 PHONE HRX_NL_NUMBER_14 14 digits
ORG_INFORMATION4 OWN_RISK_COVER HRC_YES_NO Yes and No values
ORG_INFORMATION3 PAYROLL_FREQUENCY HRX_NL_PAY_PROC_PERIOD Payroll frequency

The following table shows the attributes of these flexfields for the record
PER_ORGANIZATION_INFORMATION_EFF (DESCRIPTIVE_FLEX_CONTEXT_CODE =
HRX_NL_SICKNESS_REPORT_SENDER_INFO):
ORGANIZATION INFORMATION FOR SICKNESS REPORT SENDER FLEXFIELD CONTEXT
ORG_INFORMATION1 SENDER_NAME HRC_CHAR_80 80 characters.
ORG_INFORMATION2 TAX_REGISTRATION_NUMBER HRX_NL_CHAR_12 12 characters
ORG_INFORMATION3 ROLE HRX_NL_SICKNESS_REPORT_ Sickness Report

ROLE Role
ORG_INFORMATION4 CONTACT_PERSON_OR_DEPART HRC_CHAR_80

MENT 80 characters
ORG_INFORMATION5 CONTACT_PHONE HRX_NL_NUMBER_10 10 digits number
The following table shows the attributes of these flexfields for record PER_ORGANIZATION_INFORMATION_EFF
(DESCRIPTIVE_FLEX_CONTEXT_CODE = HRX_NL_SICKNESS_REPORT_CONTACT_INFO):
ORGANIZATION INFORMATION FOR SICKNESS REPORT CONTACT FLEXFIELD CONTEXT
ORG_INFORMATION1 ORA_HRX_NL_CONTACT_TYPE ORA_HRX_NL_CONTACT_TYPE Contact Type
ORG_INFORMATION2 CONTACT_NAME HRC_CHAR_80 80 characters.
ORG_INFORMATION3 LOCATION HRC_CHAR_80 80 characters.
ORG_INFORMATION4 GENDER HRX_NL_SEX NA
ORG_INFORMATION5 CONTACT_NUMBER HRX_NL_NUMBER_10 10 digits number
Business Units
Oracle Fusion HCM uses the business unit classification to group sets of data that are enabled with the Set ID
functionality. Thus, when you associate a business unit with a default set, this default set is inherited by every entity
connected to the business unit.
No Netherlands-specific data is required or captured at this level. However, you must assign a business unit to a
worker in the new hire process, so business units must be created for the enterprise.
To create a business unit:

1. Select Define Business Units for Human Capital Management in the implementation project task list:

Figure 41. Define Business Units for Human Capital Management Task
2. Click Create icon on the Manage Business Units screen.
Figure 42. Manage Business Units

3. On the Create Business Unit page, provide the required information:
Figure 43. Create Business Unit
You must have previously created the location and default set. (Default sets are created using the Manage Reference Data Sets
task. For more information about business units and default sets, refer to the Oracle Fusion Workforce Deployment
Implementation Guide: http://docs.oracle.com/cd/E28271_01/fusionapps.1111/e20379/toc.htm).
Workforce Structures
Workforce structure setup must be performed once organization structure setup is complete. Workforce structures
are used to:

Define additional partitioning of the workers within the organization, including divisions, departments, and
reporting establishments.
Assign roles to workers within the organization, including grades, jobs, and positions.
Set up actions and reasons that apply to the work relationship cycle of workers.
No workforce structures are predefined for the Netherlands. The implementation team is responsible for defining all
the workforce structures that apply to the enterprise for which the setup is being done. Note that some workforce
structures may not apply to every enterprise.
Locations
The first workforce structures to define are the locations where business is conducted or which are of interest to the
business. Locations can store information about the physical location of a workforce structure and can be assigned
to workers in order to define their physical work location.
For the Netherlands, you can create locations that are defined as internal organizations.
To create or manage locations:

1. Select Manage Locations in the implementation project task list:
Figure 44. Manage Locations Task

2. Click Create icon on the Manage Locations screen.

Figure 45. Search Locations
3. If the location is related to an internal organization (for example, a department), in the Create Location
page, provide the required general information and click Submit:
Figure 46. Create Location
Divisions
A division is a high-level organization that supports functionality for roll-up reporting. Division exists above a legal
entity, but below an enterprise. As there is no concept of legislation at the division level, no Netherlands-specific
attributes are stored here.

To create divisions:
4. Select Manage Divisions in the implementation project task list:
Figure 47. Manage Divisions Task

5. Click Create on the Manage Divisions screen:
Figure 48. Search Divisions

6. On the Create Division page, enter the required information:

Figure 49. Create Division
Note: In the sample screen above, the division is associated with the previously created location.
7. Click Next to provide additional division details, and then Review and Submit.
Departments
A department is a division of a business enterprise dealing with a particular area or activity. You can assign workers
to departments.
To create departments:
1. Select Manage Departments in the implementation project task list:
Figure 50. Manage Departments

2. Click Create on the Manage Departments screen:

Figure 51. Search Departments
3. On the Create Department page, enter the required information:
Figure 52. Create Department
Note: In the sample screen above, a location has been selected. Each time this department is associated to another
entity, such as a worker, this location will also be associated to that entity by default.
4. Click Next to provide additional department details:
5. Review and Submit.
Reporting Establishments
A reporting establishment represents an organizational unit used for HR statutory reporting. You can create a new
reporting establishment from scratch or you can select an existing TRU and define it as a reporting establishment,
but for the Netherlands, you must select existing TRUs and define them as reporting establishments. There must be
a one to one relationship between the reporting establishment and the TRU for the Netherlands.
You mark an LRU as both TRU and Reporting Establishment in LRU HCM Information, following the process
described in section Manage LRU Information earlier in this document
Organization Structure Models Supported by Dutch Localization

Some of the earlier sections describe a set of organizational units that have to be created in order to set up an
organization structure to manage HR processes for the Dutch localization. Each enterprise can combine in different
ways these organizational units to set up the organization structure model that best fits their business needs.
The organization model for the Netherlands Establishments relies on three main concepts:

LRUs (in the XLE model, required for Financials)
TRUs (required for Payroll data capture and calculation model)
Reporting Establishments (in the HCM model, required for Contract and Assignments)
Roles in Organization
A set of workforce structures, including grades, jobs, and positions, must be defined during implementation. These
structures are used to assign a role to each worker in the organization.
Grades
A grade defines the relative rank, level, or status of a worker. It is one of the key building blocks used for managing
compensation.
To create grades:
1. Select Manage Grades in the implementation project task list:
Figure 53. Manage Grades

2. Click Create icon on the Manage Grades screen:
Figure 54. Search Grades

3. On the Create Grade page, provide the required information:

Figure 55. Create Grade
Note: In the sample screen above, this grade is associated with the business unit created earlier.
4. Click Next to define the order of progression between grades:
Figure 56. Create Grade Step

5. Click Next to define grade rates:
Figure 57. Create Grade Rate
Grade rates can be used to define pay values for grades in a legislative data group (country). You can add a rate
that was previously defined or create a new rate:
Figure 58. Create Grade Rate Details

Figure 59. Grade Rate Table
Jobs
A job defines a set of roles or duties that are linked to a worker. Each enterprise must create the job codes that are
suited for its organization.
You must define a job structure while setting up the workforce structures in the Dutch HR implementation.
To create jobs:
1. Select Manage Job in the implementation project task list:
Figure 60. Manage Jobs Task
2. Click Create icon on the Manage Job screen.

Figure 61.Search Jobs
3. On the Create Job page, provide the required information:
Figure 62. Create Job: Basic Details
Note: On this page, the selected Job Set is the same as the default set selected for the business unit. Thus, this job
cannot be assigned to workers who belong to a business unit that is associated with a different job set.
4. Click Next to enter job details:
Figure 63. Create Job: Job Details
Positions
A position is a specific instance of a job in a department or business unit. The use of jobs or jobs and positions
varies by industry and customer requirements.
To create positions:
1. Select Manage Positions in the implementation project task list:

Figure 64. Manage Positions Task
2. Click Create icon on the Manage Positions screen:
Figure 65. Search Positions

3. On the Create Position page, provide the required information:
Figure 66.Create Position: Basic Details
Note: On this page, the position is associated with the previously created business unit. The business unit you
select here determines which jobs, departments, and location values can be selected on subsequent screens.
4. Click Next to provide additional position details:
Figure 67.Create Position: Position Details

Note: On this page, you can specify optional attributes, such as Full-Time or Part-Time, Regular or Temporary,
Entry Grade and Entry Step. You can also add previously defined grades that are valid for this position. No
Netherlands-specific data is required or captured in the Position Details page or other setup pages for positions.
Personal Data Setup

This section describes the setup and validations predefined for the Netherlands for the following person information:
Addresses
Names
Legislative information
National IDs
Addresses
The format in which addresses must be entered for workers located in the Netherlands is predefined and must not
be modified during implementation. The predefined format enables the following fields:
Country (Required)
Street Name (Required)
House or Building Number
House or Building Number Addition
Location Description
Postal Code (Required)
City (Required)
The following figure shows how an address in the Netherlands is captured in the application:
Figure 68.Create Address
Address Validation
The following set of validations specific to the Netherlands is performed when address is entered:
The postal code must be in the format NNNNAA or NNNN AA (where N is a number and A is an alphabet).
Address Mapping
If you are uploading the data through HCM Data Loader (HDL) or File Base Loader (FBL), then map the address
fields as follows:

PERSON ADDRESS MAPPING
UI Name Table Column Name (PER_ADDRESSES_F)
Street Name ADDRESS_LINE_1
House or Building Number ADDRESS_LINE_2
House or Building Number Addition ADDRESS_LINE_3
Location Description ADDRESS_LINE_4
Postal Code POSTAL_CODE
City TOWN_OR_CITY
Country COUNTRY
Name Styles and Name Formats

A name style determines how the name is displayed on a persons record. It specifies which components are shown,
the sequence in which they are displayed, and whether they are optional or required. This name style must not be
modified during implementation. The predefined name style for the Netherlands is:
Correspondence Title
First Name (Required)
Initials (Required)
Prefix
Last Name (Required)
Title 1
Title 2
Title 3
Partner Last Name
Partner Prefix
Name Style
The following figure shows how a Dutch name is captured in the application:

Figure 69. Dutch Person Name Format
The values for the 3 Title fields can be configured by making entries into the lookup type HRX_NL_TITLE.
To configure the Title list of values (LOV):

1. Navigate to the Manage Common Lookups page.
2. Search for the lookup HRX_NL_TITLE:
Figure 70. Manage Dutch Title Lookup

3. Click Create to add a new title:

Figure 71. Search Dutch Title Lookup
Name Formats
When a person's name is displayed to users, the format of the name can vary according to the context in which it
appears. For example, in an ordered list of names last name may appear before first name, but in other contexts first
name appears before last name. A name format is a template for arranging the predefined components of a name,
such as first name, last name, and title, in a specified order for a particular purpose.
In addition to the four name formats that are available for use in all localizations (display name, list name, full name,
and order name), three additional local format types are predefined for the Netherlands:
Own last name and partner last name - [Initial] [Prefix] [Last Name] [Partner Prefix] [Partner Last Name]
Partner last name and own last name - [Initial] [Partner Prefix] [Partner Last Name] [Prefix] [Last Name]
Partner name - [Initial] [Partner Prefix] [Partner Last Name]
You can select one of these formats in the person record of a person in a Dutch LDG and it will be used wherever
the default full name format would otherwise be used, such as on statutory reports or a payslip.
You can also define additional Netherlands-specific format types that can be used wherever the default full name
format would otherwise be used. This provides you with the flexibility to select a specific name format at individual
employee level and display the name as the employee prefers (using the predefined Dutch name style components)
instead of the default full name format.
To set up additional name format styles for the Netherlands:
Configure the new name format in two lookups, PER_NAME_FORMATS (with +NL Tag) and
HRX_NL_FULL_NAME_FORMAT. This ensures that these new formats are available in all the Dutch LDGs in your
enterprise.
1. Navigate to the Manage Common Lookups page and search for the lookup PER_NAME_FORMATS:

Figure 72. Manage Personal Name Format Lookup
2. Click Create and provide the required details:
Figure 73. Manage Personal Name Format: Add New Values
3. Perform the same setup for the Lookup HRX_NL_FULL_NAME_FORMAT.

4. Navigate to the Manage Person Name Formats page and click Create:

Figure 74. Search Personal Name Formats
Figure 75.Create Name Format
5. Select the new lookup that you created. Define the name format for the selected format type using the
following mapping:
NAME FORMAT MAPPING
Column Name Display Sequence Required Flag Prompt
TITLE 5 N Correspondence Title
FIRST_NAME 10 Y First Name
NAM_INFORMATION1 15 N Initials
PRE_NAME_ADJUNCT 20 N Prefix
LAST_NAME 25 Y Last Name
NAM_INFORMATION2 30 N Title 1
NAM_INFORMATION5 45 N Partner Last Name
NAM_INFORMATION6 50 N Partner Prefix
6. Enter the name in the Preview Name Format region and verify the formatted name:

Figure 76.Create Name Format: Preview
7. Click Save.
Legislative Information
The following figure shows how the Netherlands-specific legislative information is captured in the application:
Figure 77. Legislative Information
The Dutch localization supports the following legislative information:

Marital Status: Includes only those values that apply to the Dutch legislation.
Highest Education Level: Uses Netherlands-specific values in the lookup. You can add your own values as
none are predefined.
To set up the Highest Education Level lookups for the Netherlands:
1. Navigate to the Manage Person Lookups UI and click on PER_HIGHEST_EDUCATION_LEVEL.
2. Create lookup values with +NL tag. This ensures that the new values will be available in all the Dutch
LDGs in your enterprise:

Figure 78. Manage Person Lookups
3. Click Create to create new Highest Education Level.
4. Provide the required details and click Save:
Figure 79. Manage Person Lookups: New Values
National Identifiers
The following validation has been delivered for the Dutch National ID (BSN):
The BSN is either 8 or 9 characters long.

Check digit validation

Validations for BSN Examples
Validation for 8-digit number: The BSN is NNNNNNNC where C is control figure and it is the last digit. Each digit,
except the control digit, is multiplied by a number as mentioned in table below. The outcome is added up and the
result is divided by 11. The result is equal to the Control figure C.
EIGHT-DIGIT VALIDATION
Digit of BSN Multiplied with
First 9
Second 8
Third 7
Fourth 6
Fifth 5
Sixth 4
Seventh 2
Validation for 9-digit number: The BSN is NNNNNNNNC where C is control figure and it is the last digit. Each digit
except control digit is multiplied by a number as mentioned in table below. The outcome is added up and the result
is divided by 11. The final result is equal to the Control figure C.
NINE-DIGIT VALIDATION
Digit of BSN Multiplied with
First 9
Second 8
Third 7
Fourth 6
Fifth 5
Sixth 4
Seventh 3
Eighth 2
The following figure shows how a national identifier is captured in the application:
Figure 80. National Identifiers

Hiring a Worker
Once you have defined the organizational and workforce structures, you can manage workers data in the
application. To perform tasks related to person and employee management, you would typically sign in to the
application using a role connected to a user, such as Human Resource Specialist, rather than to a member of the
implementation team.
Note:
If the enterprise is using the Payroll Interface then element eligibility for the element Tax and Social Insurance
Calculations should be created before creating the payroll relationship. In addition, it is recommended that the user
does not check the Automatic entry checkbox while creating the element eligibility.
To hire an employee:
1. Select New Person under Workforce Management in the Navigator:
Figure 81. Hiring a Worker: Navigation

2. In the task list, select Hire an Employee:
Figure 82. Hire an Employee
Note: The other supported person types for the Netherlands are:
Contingent Worker
Nonworker

Pending Worker
3. On the Identification page, provide the required information:
Figure 83. Hire an Employee: Identification Basic and Personal Details
Figure 84. Hire an Employee: Identification National Identifiers
Note the following:
The Hire Reason field displays a list of valid action reasons defined for the hire action.
The Legal Employer field displays a list of all legal employers.
The name format is determined by the predefined name formats for the Netherlands.
The Date of Birth field is required for the Hire process.
National ID is validated according to the predefined National Identifier Netherlands rules.
4. On the Person Information page, provide the required information:

Figure 85. Hire an Employee: Person Information
Figure 86. Hire an Employee: Passport, Visas and Permits
Note the following:

An address must conform to the predefined Netherlands Address format.
Marital Status is a required field in Netherlands-specific Legislative Information section.
The following additional information is optional for the Netherlands:
Phone and E-Mail
Citizenship and Visa Information
Emergency Contacts
5. On the Employment Information page, provide the required information:

Figure 87. Hire an Employee: Employment Information Work Relationship
Figure 88. Hire an Employee: Employment Information Job

Figure 89. Hire an Employee: Employment Information Payroll Details
6. Review the information and click Submit.
Note the following:
In accordance with the simplified employment model (and as selected in legal employer setup), you enter
employment information at assignment level.
If you are using the two-tier single contract and single assignment employment model, the Type field in the
Contract details section allows you to select the contract type for the person being hired. The contract type
that you select here is defaulted in the Contract Type field in the Wage Report Details section of the personal
calculation card that is created. If no contract type is selected during new hire, the contract type on the
calculation card is defaulted to Unlimited Contract.
The Business Unit, Job, Grade, Department, Reporting Establishment and Location must have been
previously defined. The Business Unit you select determines which jobs, grades, and departments you can
select.
Reporting Establishment is required for a person to be included in legal reports for the Netherlands. In the
Netherlands, a Reporting Establishment is the same name as that of the TRU. This information is used in
validating the payroll frequency of the payroll that is added in the Payroll Details section. The frequency of
the payroll selected is validated against the payroll frequency, which is selected in the Manage Legal
Reporting Unit HCM Information page.
Employment Validations for the Dutch Localization

A set of Netherlands-specific validations check the consistency of employee information and ensure that all the key
information for legal reporting is entered. When hiring a Dutch employee, consider the following:
When a payroll is being added to the person in the Payroll Details page, the frequency of the selected payroll must
be the same as the payroll frequency of the TRU with which the employee's reporting establishment is associated.

Maintaining Person and Employment Information
Once the new hire process is complete, the person is recorded in the system. Payroll users can modify person and
employment information as needed, and add data not entered in the new hire process, such as birth and disability
information, which cannot be entered in the new hire process.
Person Management
To maintain person information:
1. Select Person Management under Workforce Management in the Navigator:
Figure 90. Person Management Navigation

2. Search for the person record:
Figure 91. Search Person
3. If you select the person, the Employment page is opened, If you wish to update their personal details,
select the Actions button in the Search Results table:

Figure 92. Manage Person Navigation
4. Navigate through the various tabs to view and manage the complete set of person information. Select
either Edit>Correct or Edit>Update to modify the information in any section:
Figure 93. Person Information

5. Click Edit in the Biographical Information section to enter additional data:

Figure 94. Person Information: Edit Biographical Information
Figure 95. Person Information: Edit Contacts Information
Figure 96. Person Information: Edit Documents Information
6. For the Netherlands, the Passport region is used to store ID card information along with the passport
information. The Type field lists both Regular and ID card in the list of values.

Figure 97. Person Information: Edit Passports
7. On the Create Document Record page, , an employer can upload a copy of the passport or ID card:
Figure 98. Person Information: Create Document Record

8. If Disabilities information is required, go to the Disabilities tab and click on Create button:
Figure 99. Person Information: Disabilities

9. Enter the required information:

Figure 100. Person Information: Disability Details
10. In the Legislative Information tab, select the content value Netherlands, and enter Netherlands-specific
disability information:
Figure 101. Person Information: Disability Country-Specific Details

11. Select the Disability Payment Type. This is a required field if you have selected Netherlands as the
context value.
Employment Management
The Person Management work area also provides tasks for maintaining employment information.
Figure 102. Create and Manage Work Relationship
You can modify an existing instance of employment or add a new instance if, for example, an employee has a job
change.
Adding a Nonworker
After having signed in the application to hire a Nonworker:
1. Select New Person under Workforce Management in the Navigator:
Figure 103. Add a Nonworker: Navigation

2. In the task list, select Add a Nonworker:

Figure 104. Add a Nonworker Task
3. On the Identification page, provide the required information:
Figure 105. Add a Nonworker: Identification
Note: If a Dutch Legal employer is selected, the following Netherlands-specific Nonworker types are displayed:
Benefit nonworker
Nonworker paid
Nonworker unpaid
4. On the Person Information page, provide the required information:

Figure 106. Add a Nonworker: Person Information
5. On the Employment Information page, provide the required information:
Figure 107. Add a Nonworker: Employment Information

Terminating a Worker
When a persons employment period ends, the work relationship must be terminated.
To terminate a work relationship:

1. Search for the employee, and then select Personal and Employment > Manage Work Relationship from
the Action menu in the Search Results table. (You can also select the Manage Work Relationship action
from the person record.)
Figure 108. Manage Work Relationship Navigation

2. From the person record, select Terminate from the Actions menu:
Figure 109. Terminate Work Relationship Navigation
3. On the Terminate Work Relationship page, enter the termination details, including the termination reason:
Note: The Termination Reason field displays a list of Action Reasons associated with the termination
action, as described earlier in this guide.

Figure 110. Terminate a Work Relationship: Termination Details
4. Review the termination details and click Submit.
Payroll Processing After Termination

An assignment pay status determines how an assignment is processed in the payroll run. The user needs to review
the default pay status that will be applied to assignments after termination and change it, if required.To check the
pay statuses of assignments:
1. Select Manage Assignment Statuses in the implementation project task list:
Figure 111. Manage Assignment Status Task
2. Review the pay status for terminated assignments and make changes, if required:
Figure 112. Manage Assignment Statuses Table

HR Reports for the Netherlands
The following statutory reports are available for the Netherlands:
First Day Notification Report (including audit report)

WAZO Report (for maternity, adoption and foster care absences)
Sickness Report
Sickness Recovery Report
Long-Term Sickness Report
Long-Term Sickness Recovery Report
These reports are designed using Flows, HCM Extract and BIP templates.
One HCM extract definition and one flow is delivered for each report. The reports can be accessed from the Data
Exchange Work Area or Payroll Checklists Work area using a role that has the profile of a Human Resource
Specialist.
The extract definitions are associated with the type HR Archive. The definitions are based on user entities (for the
design of extract blocks) and database item groups (for the design of data elements). The Dutch localization delivers
a set of user entities and database item groups that are specific to reporting for the Netherlands. You can use these
to customize the extract definitions. Those artifacts can be used for customized extract definitions.
Business Intelligence Publisher (BIP) templates in XSL format are provided for each of the reports. The First Day
Notification audit report is additionally available in RTF format. These templates are located in the BIP Catalog,
which can be accessed from Reports and Analytics.
For setup information for the digital absence reports, refer to Oracle Fusion HCM (Netherlands): Dutch Statutory
Absences Implementation and Functional Considerations white paper.
First Day Notification Report

The First Day Notification Report supports the legislative requirement to notify the tax office about a new employee.
The report is an electronic file in the Extensible Markup Language (XML) format. The report is generated when you
create a new work relationship for a new employee or rehire an employee on an existing work relationship.
The First Day Notification report is available for HR-only and Payroll Interface customers.
The Legal Employer data that is reported in the file is:

Tax Registration Number
The Employee data that is reported in the file is:
Date of Birth
Initials
Prefix
Last Name
Start (or Rehire) date of employment
BSN (National Identifier)
After the file is created, the creation date is added to the work relationship.
In the report process, a single XML is created for each Employee and Tax Registration Number combination.

Corrections
When an attribute reported in the First Day Notification report is corrected or updated, a new file will be created in
the next run of the report. The date on which the new file is created replaces the previous date. The new date is the
date on which the report has been regenerated.
The Tax Authorities mandate the use of start date while running First Day Notification Report. This start date is used
in the parameters of the file creation. The report creates files for employees who join on or after the date mentioned
in the start date parameter. In the exceptional case that an employee joins before the start date of the First Day
Notification Report, but needs to be reported, the employee can be selected by leaving the start date blank in the
report parameters.
The report is regenerated for the employee if a correction is made to any of the following fields:
Date of Birth
Initials
Prefix
Last Name
Validations
No file is created if any of the following occurs:
Tax Registration Number is missing.

Tax Registration Number is in invalid format.
Date of birth is missing when BSN exists.
Audit Report
An audit report helps you to identify the work relationships, and the creation date for the First Date Notification
report. It has a free format and is not based on any legislation. The output can be on paper or a PDF file. There is a
single audit report for the report process run.
AUDIT REPORT EXAMPLE
Tax Registration First

Employee Last Notification
Number Initials Prefix BSN Working
Number name Creation Date
Administrative Unit Day
123456789L01 123456 Janssen A 111222333 01-02-2006 28-02-2006
123456789L01 234567 Peters JAN 222333111 01-01-2006 31-01-2006
Prerequisites
Create the jurisdiction for Netherlands Tax Office with Legislative Category as Wage Tax and LRU registration
number as Tax Registration Number.
Create the Legal Entity and specify it as both PSU and a Legal Employer.
One TRU is created automatically when the legal entity is created. More TRUs under legal entity can be created,
if required.
Create the registration at LRU (TRU) level for the Netherlands Tax Office jurisdiction.
Define the TRU as a reporting establishment.
Create employees and attach them to the reporting establishment at Assignment level.

Run the First Day Notification Report
To run the report, click Submit on the Data Exchange work area or the Checklist work area. The following are the
default parameters:
Start Date Optional

End Date Optional
Legal Employer Required
Employee Name - Optional
1. Navigate to the Data Exchange or Payroll Checklist work area.
2. Go to Submit a Process or Report and select Netherlands specific Legislative Data Group:
Figure 113. First Day Notification Report: Submission

3. Search for First Day Notification Report and click on Next:
Figure 114. First Day Notification Report: Select Flow Pattern

4. Enter the parameters to be used to run the report:
Figure 115. First Day Notification Report: Parameters

Payroll Flow: Identifier for the process that is being run. You can enter a value each time the process is
executed. You can choose any format to describe the payroll flow.
Legal Employer: It is required to select the Legal Employer for which the report must be run
5. Click Submit.
Figure 116. First Day Notification Report: Review

6. Review the report output.
Once the report is executed successfully, you can view it in BIP (described is the viewing report outputs section),
and following is sample of output xml:
<?xml version = '1.0' encoding = 'UTF-8'?>
<Eerstedagsmelding version=1.0
xmlns=http://xml.belastingdienst.nl/schemas/Eerstedagsmelding/2008/01>
<Bericht>
<IdBer>100000009</IdBer>
</Bericht>
<AdministratieveEenheid>
<LhNr>333456222L78</LhNr>
<InkomstenverhoudingInitieel>
<DatAanvWz>2012-07-11</DatAanvWz>
<NatuurlijkPersoon>
<SofiNr>100000009</SofiNr>
<PersNr>955160008166219</PersNr>
<Voorl>INI</Voorl>
<Voorv>PRE</Voorv>
<SignNm>LN</SignNm>
<Gebdat>1973-01-01</Gebdat>
</NatuurlijkPersoon>
</InkomstenverhoudingInitieel>
</AdministratieveEenheid>
</Eerstedagsmelding>
Viewing Report Output

This section describes the process to view:
The payroll flows that have been executed for a specific report
The output of a specific report
Viewing Payroll Flows for a Report

After having submitted the report and confirmed that the execution is successful:

Figure 117. First Day Notification Report: Viewing Payroll Flow
1. Navigate to Work Area Checklists.
Figure 118. First Day Notification Report: Checklists Work Area Navigation
2. Search all the available flows related to the report whose output needs to be reviewed (or any other search
criteria) and the executed payroll flow:
Figure 119. First Day Notification Report: Search Payroll Checklists
Corrections
If any of the fields that are reported have changed since the report was last run, the report must be regenerated. The
last file creation date is tracked on the Manage Work Relationship page.
Any updates to the reported fields trigger the automatic selection of the First Day Notification - Recreate File
checkbox on the employee's work relationship. If this box is selected, a new report with the updated values will be
created for this employee the next time the First Day Notification Report is run for this legal employer (or the
individual employee). Once the report is generated again, the recreate option is deselected.
This report is regenerated for the employee if correction is made to any of the following fields.
Date of Birth

Initials
Prefix
Last Name
Note: Recreate File checkbox is not selected if there are changes to the Date of Birth field, although the report is
regenerated.
Example of Correction
1. Change the Prefix of the employee from Manage Person page:
Figure 120. First Day Notification Report: Correction Example

2. Go to Manage Work Relationship.
3. First Day Notification - Recreate File is selected and report will be generated again with new Prefix. Run
the report again as described previously.
Figure 121. First Day Notification Report: Work Relationship Details
Viewing the Report Output

1. Click on Work Area Reports and Analytics

Figure 122. First Day Notification Report: Reports and Analytics Navigation
2. Within the folder structure Navigate to Shared Folders > Human Capital Management > Workforce
Management > Person Management > Netherlands
Figure 123. First Day Notification Report: Reports and Analytics Navigation
3. Select First Day Notification HR Report.
4. Click View:

Figure 124. First Day Notification Report: Reports and Analytics View
Alternatively, you can execute the report using the following procedure:
1. Sign in to the Oracle Fusion application and navigate to the Data Exchange Work Area.
2. Go to Submit an HCM Process and select a Netherlands-specific LDG:
Figure 125. First Day Notification Report: Submit from Data Exchange Work Area
3. Search for Run First Day Notification Report and click Next:
Figure 126. First Day Notification Report: Select Flow Pattern

4. Enter the parameters to be used to run the report:
Figure 127. First Day Notification Report: Parameters

Legal Employer: It is required to select the Legal Employer for which the report must be run

5. Submit the report:
Figure 128. First Day Notification Report: Review

Additional Information for Payroll Interface

The setup tasks described up to this point in this document are required to manage the HR processes for an
enterprise.
If the enterprise is required to extract data from the Oracle Fusion application, using the Payroll Interface, to feed an
external payroll system, additional payroll-related data is provided to support the Payroll Interface. Detailed
documentation for the Payroll Interface can be found in the Global Payroll Interface Guide
(http://www.oracle.com/technetwork/fusion-apps/payrollinterfaceguider4-1873384.pdf). The sections that follow
describe how to define payroll-related information to support the Payroll Interface for Netherlands implementations:
Tax Reporting Unit Calculation Card (Employer Deduction Information Card)

Personal Calculation Card Automatic Card
Personal Calculation Card Manual Card
Consolidation Groups
Payroll Definitions
Organizational Payment Methods
Personal Payment Method
Elements and Gross Compensation
Tax Reporting Unit (TRU) Calculation Card

A TRU calculation card is a mechanism for capturing values required for payroll calculation at the level of a tax
reporting unit.
To create TRU Calculation Card:

2. Select Manage Legal Reporting Unit Calculation Cards in the implementation project task list:

Figure 129. Manage Legal Reporting Unit Calculation Cards Task
3. Click Go to Task.
4. Click Create.
5. On the Create Calculation Card page, enter the Effective As-of Date and Name:
Figure 130. Create Legal Reporting Unit Calculation Card

6. Click Continue. The Manage Calculation Cards screen appears:
Figure 131. Create Legal Reporting Unit Calculation Card: Sector Fund WW Contribution
7. Select the Sector Fund WW Contribution Calculation Component and click on Edit > Correct

Figure 132. Legal Reporting Unit Calculation Card: Sector Fund
8. Select the appropriate sector funds for this calculation component and click OK. When you add multiple
sector funds, you must mark one of them as the default sector fund:
Figure 133. Legal Reporting Unit Calculation Card: Sector Fund WW Contribution
9. Click on component group Taxes and provide the required details for the calculation components Tax
Calculation and Wage Tax Subsidy:
Figure 134. Legal Reporting Unit Calculation Card: Tax Calculation Details
10. Enter the differentiated WGA Contribution rate:
Figure 135. Legal Reporting Unit Calculation Card: Create WGA Contribution

Note: You enter the differentiated WGA Contribution rate for the TRU using the Overrides. If you do not enter an
override, a value of 0% is applied to all employees assigned to the TRU.
11. To override the 0% rate, click Create on the Social Insurance calculation component and select the WGA
Contribution component. Select the Enterable Calculation Values on Calculation Cards tab in the WGA
Contribution calculation component details:
Figure 136. Legal Reporting Unit Calculation Card: WGA Contribution Override
12. Click Create and enter the required information as below and click OK:
Figure 137. Legal Reporting Unit Calculation Card: WGA Contribution Override Details
13. The calculation card component with the override is created as shown below:
Figure 138. Legal Reporting Unit Calculation Card: WGA Contribution Details
14. Review the information entered.

15. Click Submit to save the TRU Calculation Card.
Validations for TRU Calculation Card

There can only be one card per TRU.
Validation for Card Components WW Sector Fund Contribution, Tax Calculation and Wage Tax Subsidy are the
required components. These components are automatically created when the card is created.
Validation for Sector Fund There can only be one default sector fund in the TRU card. This sector fund, which is
identified as default, is used in the automatic card creation for the employees associated with this TRU.
Personal Calculation Card Automatic Creation

Personal payroll calculations represent calculation information specific to a particular payroll relationship. Payroll and
Payroll Interface users can create the person card using the Manage Calculation Cards page. Since a calculation
card is required for all payroll relationships, the application creates the calculation card automatically when a payroll
relationship is created. The automatically created card contains the most commonly used values for different fields
in the card. The payroll administrators have the option to override the default values.
Following are the highlights of the automatic creation process for the Dutch Statutory Deductions and Reporting
Card:
Calculation cards are created automatically for all payroll relationships of type Standard. For the Netherlands,
standard payroll relationship applies to the person types Employees and Nonworker (paid).
Automatic card creation is enabled only for customers with a license for Payroll or Payroll Interface. The license
setup must be done appropriately for the automatic card creation. Refer to the section, Availability of Element
Template Functionality based on customer license, for information on setting up licenses.
A TRU calculation card must exist for the automatic card creation process. Without the TRU card, the calculation
cards will not be automatically created.
The card is created automatically upon completion of the new hire process. If additional assignments are added,
the existing card will not be updated automatically, nor will a new card be created. If required, you must create a
new card (for example, for a different TRU) or update the existing calculation card with the assignments, if the
same tax and social insurance rules apply to the new assignment.
It is assumed that reporting establishment specified in the employment page of the new hire flow is also a TRU.
It is assumed that the payroll frequency applicable for the TRU is present in the TRU flexfield.
The structure of the TRU card is the same as discussed in the above sections for manual card.
Prerequisites
As already mentioned in Hiring a Worker section, element eligibility for the element Tax and Social Insurance
Calculations should be created before creating the payroll relationship. In addition, the user should not check the
Automatic entry checkbox while creating element eligibility.
Review and Update an Automatic Statutory Deductions and Reporting Card:

1. Log in to the application using payroll administrator or payroll manager user.
2. Navigate to the Person Management work area, then search for an employee:

Figure 139. Search for a Person
3. Select Manage Payroll Calculation Information from the Actions menu.(You can also navigate to the
calculation card from the person record using the Manage Calculation Cards task.)
Figure 140. Navigation to Manage Payroll Calculation Information

4. Search for the cards available for this person. Check that the Effective As-of-Date is no earlier than the
employee hire date:
Figure 141. Search Person: Calculation Cards
The automatic calculation card created appears in the search results:

5. Select the Statutory Deductions and Reporting card listed in the search results.

Figure 142. Manage Calculation Cards: Social Insurance Component Group
6. In the calculation component details of Social Insurance Information and Subsidies and Discounts,
review the default values. Correct or update the values as required:
Figure 143. Manage Calculation Cards: Social Insurance Information Component Details
7. Select the Taxes component group to view the Tax and Special-Rate Tax calculation components:

Figure 144. Manage Calculation Cards: Taxes Component Group
Note: The reference column on the Tax component refers to the TRU to which the Tax component is attached. It is
automatically populated with the TRU linked to the reporting establishment selected during the hire process.
8. Select Special-Rate Tax, and expand the calculation component details Special-Rate Tax to see the
default values. Edit or update the values as required:
Figure 145. Manage Calculation Cards: Special-Rate Tax Component

9. Select the Enterable Calculation Values on Calculation Cards tab. You can specify values for individual
percentage and previous year annual income, which will override the values, specified at the legislative
level. When you create overrides, the new values will be considered for tax calculation.
10. Click Create to add calculation value:

Figure 146. Manage Calculation Cards: Special-Rate Tax Component Details Override
11. To set the Calculation Value for Individual Percentage, select Individual Percentage from the list of values
and specify the Rate:
Figure 147. Manage Calculation Cards: Special-Rate Tax Individual Percentage Override
Note: If you specify a rate for the individual percentage, this percentage is taken into account while calculating
special-rate tax instead of the values provided by the legislation. Individual Percentage is applicable for one year
and must be end dated to the year-end.
12. To set the Calculation Value for Previous Year Annual Income, select Special-Rate Previous Year Income
from the list of values and provide the override value:

Figure 148. Manage Calculation Cards: Special-Rate Previous Year Income Override
Note: If an override is created for previous year annual income, this amount is considered while calculating
special-rate tax as the previous year income instead of calculated previous year value. Special-Rate Previous
Year Income is applicable for one year and must be end dated to the year-end.
13. Select the calculation component Tax. In the calculation component details Standard-Rate Tax, review to
see the default values. Edit or update the values as required:
Figure 149. Manage Calculation Cards: Standard-Rate Tax Component Details

14. Select the Wage Report Information component group, calculation component Wage Report and
expand the calculation component details Wage Report Information to see the default values. The
contract type specified while hiring the employee is defaulted here in the Contract Type field. If no contract
type was selected during the new hire process, the default value for Contract Type is Unlimited Contract.

Figure 150. Manage Calculation Cards: Wage Report Component Details
15. Click Associations to display the Associations and Association Details. In the Associations section, an
association is created:
Between the calculation card and the TRU, and
Between the assignments created during new hire and the default sector fund selected on the TRU
calculation card.
Figure 151. Manage Calculation Cards: Associations
Personal Calculation Card Manual Creation

Personal payroll calculations represent calculation information specific to a particular payroll relationship. Personal
calculation cards capture information used to calculate one or more related payroll calculations. For example, a

calculation card might capture tax withholding information for calculating one or more tax calculations. A person may
have multiple calculation cards, one for statutory deductions and another for involuntary deductions. An employee
who has multiple assignments might have different calculation cards for each one.
A manual personal calculation card is required in scenarios where you need to create a new card to attach
assignments on a different TRU. This is not common. It is more likely that you will need to review the automatically
created card and edit any information if required or add additional assignments to an existing card.
Prerequisites
A valid TRU calculation card must exist.
Element eligibility for the element Tax and Social Insurance Calculations should be created before creating the
card. In addition, the user should not check the Automatic entry checkbox while creating element eligibility.
Creating the Statutory Deductions and Reporting Card Manually

1. Log in to the application using payroll administrator or payroll manager user.
2. Navigate to the Person Management work area, then search for an employee.
3. Select the employee from the search results and then select Manage Payroll Calculation Information
from the Actions menu. (You can also navigate to the calculation card from the person record using the
Manage Calculation Cards task.)
Figure 152. Manual Payroll Calculation Information: Navigation
1. Search for the cards available for this person. Check that the Effective As-of-Date is no earlier than the
employees hire date:

Figure 153. Manual Calculation Cards: Search
2. You can now either review any card that is displayed, or click the Create button to create a new card for
the employee:
3. Click the person's name in the Search Results to open the Manage Person Details page. Any available
calculation cards appear in the Search Results.
4. If you are creating a new card, select Statutory Deductions and Reporting in the Name field.
Figure 154. Manual Calculation Cards: Create Card

5. Click Continue. The Manage Calculation Cards page appears:
Figure 155. Manual Calculation Cards: Edit Card

Creating Calculation Components
6. In the Calculation Card Overview pane, select the Taxes component group:
Figure 156. Manual Calculation Cards: Taxes Component Group

7. Select the calculation component Tax, click Edit > Correct:
Figure 157. Manual Calculation Cards: Correct Tax Component
Note: The TRU selected must correspond to the Reporting Establishment selected during the new hire process.
8. Select the Tax Reporting Unit in the Correct Calculation Component window and click OK.
The selected TRU is shown as the Tax reference:
Figure 158. Manual Calculation Cards: TRU Reference

9. Click Create to create the Special-Rate Tax calculation component.
10. Select Special-Rate Tax as the calculation component and your Tax component as the parent.
11. Click OK.

Figure 159. Manual Calculation Cards: Create Special-Rate Tax Component
Note: You cannot create your Special-Rate Tax component before you have selected the Tax Reporting Unit in the
Tax component, as described in the previous steps.
Entering Calculation Component Details for Tax component:

12. In the calculation component details Standard-Rate Tax, enter the details corresponding to Standard-Rate
Tax:
Figure 160. Manual Calculation Cards: Enter Standard-Rate Tax Component Details
13. Click Save.
Note: When the card is saved, it is automatically associated to the selected TRU.
Entering Calculation Component Details for Special-Rate Tax component:

14. Expand the calculation component details Special-Rate Tax to enter the details corresponding to Special-
Rate Tax and click Save.

Figure 161. Manual Calculation Cards: Enter Special-Rate Tax Component Details
Creating Enterable Calculation Values for Special-Rate Tax component:

1. Select the Enterable Calculation Values on Calculation Cards tab. You can specify values for individual
percentage and previous year annual income. When you create enterable calculation values, the new
values will be considered for tax calculation.
2. Click Create icon to add calculation value.
Figure 162. Manual Calculation Cards: Create Special-Rate Tax Overrides

3. To set the Calculation Value for Individual Percentage, select Individual Percentage from the list of values
and specify the Rate.

Figure 163. Manual Calculation Cards: Special-Rate Tax Individual Percentage Override
Note: If you specify a rate for the individual percentage, this percentage is considered while calculating
special-rate tax instead of which are displayed on the calculation component details. Individual Percentage
is applicable for one year and must be end dated to end of the year by user manually. You can optionally
enter the approval date for the individual percentage rate on the calculation component details.
4. To set the Calculation Value for Previous Year Annual Income, select Special-Rate Previous Year Income
from the list of values and provide the override value.
Figure 164. Manual Calculation Cards: Special-Rate Previous Year Income Override
Note: If calculation values are created for previous year annual income, this amount is taken into account while
calculating special-rate tax as the previous year income instead of calculated previous year value. Special-Rate
Previous Year Income is applicable for one year and must be end dated to end of the year by user manually.
5. Select the Social Insurance component group to display the Social Insurance calculation component and
the Social Insurance calculation component details.
6. Enter both social insurance information and subsidies and discounts here. You can use the same process
to review and edit these as you did for Tax calculation component details.

Figure 165. Manual Calculation Cards: Social Insurance Information Component Details
7. Select the Wage Report Information component group and review and edit the Wage Report Information
component details in the same way. If you selected a contract type during new hire, it will be shown here.
Figure 166. Manual Calculation Cards: Wage Report Information Component Details
8. Click Create to create the Sector Fund WW component.
9. Select Sector Fund WW as the calculation component and Social Insurance as the parent.
10. Select a Sector Fund that is valid for the TRU:
Figure 167. Manual Calculation Cards: Sector Fund WW Component
The calculation component Sector Fund WW Details is added as shown below:

Figure 168. Manual Calculation Cards: Sector Fund WW Reference
11. Click Save.
Association Details
To create association and association detail:
1. In the Calculation Card Overview pane, click Associations:
Figure 169. Manual Calculation Cards: Associations
2. Click the Create button in Association Details, and select the assignment number and Calculation
component as shown below:
Figure 170. Manual Calculation Cards: Create Association Details

3. Click OK.

Figure 171. Manual Calculation Cards: Association Details
Validations for Personal Calculation Card

The card is validated when you save it. The following validation is provided:
A TRU (employer deduction information) card must exist for a personal calculation card to be created. Once the
TRU is selected and the calculation card is saved, you cannot change the TRU for the card.
Payroll frequency for the assignment on the card must match the payroll frequency for the TRU with which the
card is associated.
An assignment can only be associated to a single calculation card at any time.
All assignments being associated on the card must be on the same payroll.
A payroll cannot be deleted if it is attached to assignments that are associated with a calculation card.
Following are the additional validations provided for individual components:
SPECIAL-RATE TAX VALIDATION
Attribute Validation
Tax Type and Tax Table Both tax tables (white and green) are not allowed in combination of all tax types. Only green
table can be entered with all tax types, while white table is applicable only for 0, 3 and 5 tax
types.
Tax Code, Tax Type, Tax Table and You can enter either their standard tax code through the Taxation Type, Tax Table, and Payroll
Payroll Period Period fields, or they must enter their nonstandard tax code in the Tax Code field.
Tax Code Tax code 227 applies only to employees who are of state pension age or older.
Tax code 228 applies only employees who are younger than state pension age.
Daily Tax Table and Student Taxation A person cannot have both daily tax table and student tax at the same time.
Rate
Temporary Tax Discount Applies only to employees who are lesser than the state pension age. Applies only to Green
Table.

SUBSIDIES AND DISCOUNTS VALIDATION
Wage Tax Discount and Single Senior The Single Senior Discount is applicable only when the Wage Tax Discount is selected for the
Discount employee. This validation is applied on both the segments. You can select the Single Senior
Discount only if the Wage Tax Discount is selected. You cannot deselect the Wage Tax
Discount while the Single Senior Discount is selected.
Single Senior Discount The Single Senior discount is applicable only for employees who are of state pension age or
older with marital status as single.
Holiday Coupons The Holiday Coupons are not applicable for employees who are on a Quarterly payroll. The
Payroll frequency is obtained from the TRU selected on the tax component.
SECTOR FUND WW VALIDATION
Sector Fund WW The sector fund selected for the Sector Fund WW calculation component must be associated
with the TRU on the TRU card.
Assignment An assignment cannot be associated with more than one sector fund on the same calculation
card.
Banking Setup
An HR customer may want to add payee banking information even if payroll is not processed by Oracle Fusion
Payroll for the Netherlands. For example, banking setup may be required for reporting purposes or because the data
may be passed to other products, such as an expenses module.
To accommodate this scenario, the setup of banks and branches must be done before entering bank accounts and
payment methods for the payee. Additionally, some payroll setup, described later in this document, would be
needed.
No banks or branches are predefined for the Netherlands. Banks and branches must be defined during
implementation. This can be done manually, by entering the banks and branches in the application, or it can be
done in a mass upload process.
Banks
To define banks:
1. Sign in to the application with a user that has implementation privileges, such as
APP_IMPL_CONSULTANT.
2. Select Manage Banks in the implementation project task list:

Figure 172. Manage Banks Task
3. Click Create.
4. On the Create Bank page, provide the required information:
Figure 173.Create Bank
Bank Branches
To define branches for the banks you created:
1. Select Manage Bank Branches in the implementation project task list:
Figure 174.Manage Bank Branches Task

2. Click Create.
3. On the Create Bank Branch page, provide the required information:

Figure 175.Create Bank Branch
Bank Accounts
Once banks and branches are set up, you can define the bank accounts that are needed for the organization.
Normally, implementation teams set up bank accounts that are used at an organizational level, such as the source
bank accounts for payments, rather than bank accounts at the individual payee level.
No bank accounts are predefined for the Netherlands.
To define bank accounts:

1. Select Manage Bank Accounts in the implementation project task list:
Figure 176.Manage Bank Accounts Task

2. Click Create.
3. On the Create Bank Branch page, provide the required information:

Figure 177.Create Bank Account
Note: If you want to use this bank account for processing payments related to payroll, select the Payroll option in
the Account Use field.
Note: The only Legal Entities that can be selected are the ones that have been assigned to a Primary Ledger.
Assigning Legal Entities to Primary Ledger

To assign legal entities to a primary ledger:
1. Select task Assign Legal Entities
Figure 178. Assign Legal Entities Task

2. Add the newly created legal entity
Figure 179. Assign Legal Entity

3. Save the assignment.
Organization Payment Methods

After setting up banks, you can define the payment methods that can be used within the organization itself.

No organization payment methods are predefined for the Netherlands. Implementation teams must create the ones
applicable to the enterprise.
To define organization payment methods:

1. Select Manage Organization Payment Methods in the implementation project task list:
Figure 180. Manage Organization Payment Methods Task

2. Click Create.
3. Select the legislative data group associated with this payment method:
Figure 181. Create Organization Payment Method
4. On the Create Organization Payment Method page, enter the required information:
Figure 182. Create Organization Payment Method: Employee Payment Sources
In the process of creating an organization payment method a payment source needs to be created:

Figure 183. Create Organization Payment Method: Payment Source
Note: Netherlands supports the following Payment Types:
SEPA EFT
Cash
Net Pay Balance

During the payment process, the net pay balance is used to store the amount to be transferred as remuneration for
the payee. A net pay balance, named Net Pay, is predefined for the Netherlands, and no additional setup is required
during the implement phase.
To view the Net Pay balance:

1. Select Manage Balance Definitions in the Payroll Calculations or Setup and Maintenance work areas.

Figure 184. Search Balance Definitions
2. Enter Net Pay in the Name field and select Dutch LDG, then click Search:
Figure 185. Balance Definitions Search Results
3. Click the Net Pay balance in the Search Results to view the balance information:
Figure 186. Balance Definitions: Net Pay Balance Details
Note: The Use for Remuneration field is set to Yes.

4. Click Balance Dimensions in the left panel to display the dimensions associated with this balance:
Figure 187. Balance Dimensions
Note: The Core Relationship Payments balance dimension has been associated with this balance.

Consolidation Groups and Payroll Definitions
Consolidation groups and payroll definitions are normally concepts related to payroll, but if an HR-only customer has
the requirement to assign banking details for the employee, then these objects must be set up first.
Consolidation Groups
Consolidation groups are used within the organization to enable grouping of different payrolls for reporting purposes.
No consolidation groups are predefined for the Netherlands. If you will be creating payroll definitions for the
implementation, you must define at least one consolidation group first since it is required information for payroll
definitions.
To set up consolidation groups:

1. Sign in to the application with a role that has implementation privileges, such as
APP_IMPL_CONSULTANT.
2. Select Manage Consolidation Groups in the implementation project task list:
Figure 188. Manage Consolidation Groups Task

3. On the Manage Consolidation Groups page, click Add Row:
4. Enter a name and select a legislative data group. Description is optional, but useful to provide.
Figure 189. Search Consolidation Groups

5. Click Save.
Payroll Definitions
Payroll definitions contain calendar and offset information that determine when payments are calculated and paid.
Using payroll definitions, you can specify payment frequency, processing schedule, and other parameters for a
particular payroll. Payroll period types, such as weekly or monthly, determine the interval at which you pay
employees.

Each payroll definition can be associated with only one payroll period type, and you must set up at least one payroll
definition for each payroll period type that you use to pay employees. When you create a payroll definition, the
complete payroll schedule is automatically generated, based on the selected payroll period type, any offsets or
calendar adjustments, and the number of years that you specify. Once you have saved a payroll definition, you can
assign employees to it on the Manage Payroll Relationships page.
Before you can create a payroll definition, you must have already defined a legislative data group and consolidation
group.
No payroll definitions are predefined for the Netherlands.
To set up payroll definitions:

1. Select Manage Payroll Definitions in the implementation project task list:
Figure 190. Manage Payroll Definitions Task

2. Click Create.
3. Select the LDG for this payroll definition, and click Continue:
Figure 191. Create Payroll

4. On the Create Payroll page, enter the required information:
Note the following:
You must select an existing consolidation group.
Click Add Row in the Valid Payment Methods section to add an organization payment method to use as the
default, plus any additional payment methods that are valid for this payroll. You can select any organization
payment method defined for the LDG that is linked to this payroll definition.
5. Click Next, and provide the required information on the Payroll Offsets page:

Figure 192. Create Payroll: Payroll Offsets
In the sample screen above, only the basic information required to create a payroll definition (for the purpose of
assigning a payment method to an employee) is provided.

Person Payment Information
To add payment information for an employee, you must assign a payroll definition to the employee even if you will
not be processing payroll for the employee using Oracle Fusion Payroll.
For more information about personal payment methods, refer to the Oracle Fusion Global Payroll User Guide
(http://www.oracle.com/technetwork/fusion-apps/payrolluserguider4-1873385.pdf).
Assigning a Payroll to the Employee

If a payroll definition was not assigned to the employee during the hire process, follow these steps to do so:
1. Sign in to the application with a role that has payroll privileges, such as PAY_MGR_ALL.
2. Select the Manage Payroll Relationships task in the Payroll Calculations or Payment Distribution work
area:
Figure 193. Manage Payroll Relationships Navigation
3. Search for and select the employee.

4. On the Manage Person Details page, add the payroll in the Payroll Details section:
Figure 194. Manage Payroll Relationships: Details

Assigning Payment Methods to the Employee
Once banks and branches have been loaded in the system and a payroll definition has been assigned to the
employee, you can add payment methods to the employee record.
To assign personal payment methods:

1. Select the Manage Personal Payment Methods task in the Payroll Distribution work area:
Figure 195. Manage Personal Payment Methods Navigation
2. Search for and select the employee.

3. On the Manage Personal Payment Methods page, click Create:
Figure 196. Create Personal Payment Methods
4. On the Personal Payment Method page, select the Organization Payment Method for this employee:
Figure 197. Create Personal Payment Methods: Organization Payment Method
Note: If the payment type is SEPA EFT, you must add a bank account and provide banking details
An employee can have multiple payment methods.

Use the Payment Amount Type and Percentage fields to manage distribution across different payment
methods.

Elements
Although elements are used in a payroll project only, the implementation team of an HR project may need to create
a regular earnings element and connect it to compensation information, such as basic salary or other gross
compensation elements.
Elements may also be used in the process of calculating gross compensation for the Payroll Interface.
Elements and Element Templates

Elements are created through predefined element templates, which provide the user with an intuitive user interface
and manage the creation of different types of elements and their associated objects. The template engine gets a set
of rules from the template and processes the predefined template structure to create appropriate data.
Availability of Element Template Functionality Based on Customer License

The features of element templates depends on type of license a customer have.
HR-Only: An HR-only customer gets access to the basic version of the element templates. These templates create
the element and the customer needs to create the input values, formulas, balances etc to meet their business
requirements.
Payroll Interface: A payroll interface customer gets access to a number of payroll features not available to a HR-
only customer. This includes access to the full earnings element that will create the element, input values, formulas,
balances etc. These earnings elements can be processed through the calculation to Gross process, which is also
available to Payroll Interface customers. Any other types of element, such as deductions are created using the basic
version of the element templates and the customer needs to create the input values, formulas, balances etc.
Payroll: A payroll customer gets access to all full set of earning and deduction templates. These templates create
the element, input values, formulas, balances etc.
Disclaimer: If customers want to use element in payroll, then new elements should be created only after the Oracle
Product Usage is set to Payroll. This creates the full set of data that is required in payroll such as elements, input
values, balances, formula.
Setting up the License Information (Before Release8)

1. Navigate to Payroll Process Configuration Task using FSM:
Figure 198. Manage Payroll Process Configuration Task

2. Navigate to Default Group Tab:

Figure 199. Manage Payroll Process Configuration: Payroll License
3. Select Payroll License to decide Payroll License parameter name and edit it. Change the appropriate
license value.
The following values can be entered:
HR_ONLY Select this for a customer with an HR-only license

PAYROLL_INTERFACE Select this for a customer having HR-only and Payroll interface license
PAYROLL Select this for a customer having both HR and Payroll license.
Figure 200. Payroll License to Decide Payroll License
4. Navigate to Manage Default Process Configuration Group Profile Option Values Task in FSM:
Figure 201. Manage Default Process Configuration Group Profile Option Values
5. Set the appropriate configuration group in the profile option value field:

Figure 202. Manage Default Process Configuration Group Profile Option Values
Setting up the License Information (Release8 onwards)

1. Navigate to Payroll Process Configuration Task using FSM:
Figure 203. Manage Payroll Product Usage Task
2. Set the appropriate license customer has taken for that country:

Figure 204. Manage Payroll Product Usage for the Netherlands
Using Element Templates

No specific element template is predefined for the Netherlands, but a core template can be used to create base pay
and compensation earnings:
The following steps show how to create a regular earnings element for basic salary:
1. Sign in to the Oracle Fusion application using a role that has the profile of a Payroll Manager:
Figure 205. Payroll Manager Login

2. Select Manage Elements in the Setup and Maintenance or Payroll Calculations work area:

Figure 206. Search Elements
3. On the Manage Elements page, click Create.
4. On the Create Element window, select a legislative data group and a primary classification, then click
Continue:
Figure 207. Create Element

5. Complete the fields at the top of the Create Element page, and then answer the questions:

Figure 208. Create Element: Basic Information
Note: The questions and default answers shown here are based on the predefined core element template for
earnings. Your answers drive the definition of the earnings element to be created.
6. Click Next, and complete the rest of the questionnaire:
Figure 209. Create Element: Additional Details

7. Verify the information and click Submit to create the new element:

Figure 210. Create Element: Review
8. On the Element Summary page, provide additional information as needed, such as input values,
processing rules, and eligibility:
Figure 211. Create Element: Review
Note: Use the Element Overview panel to navigate through the setup pages. Element eligibility must be defined so
the element can be linked to an element entry (and hence to gross compensation).
9. In the Element Overview panel, select Actions>Create Element Eligibility.
10. On the Element Eligibility page, enter a name in the Element Eligibility Name field and click Submit.

Figure 212. Create Element: Element Eligibility
Note: By entering only a name and no eligibility criteria, the element is eligible for all employees.
11. Click on Input Value in the left panel to provide additional information as needed:
Figure 213. Create Element: Input Values
12. Repeat this entire process to create a set of elements to support your business needs. For example, you
might create another element for a car allowance.
Element Entries
For earnings to be associated with a person, you must create an element entry for that person and that element. In
the sections that follow, you will see how an element entry is automatically generated by creating a Salary Basis or a
Compensation entry for the payee. Other processes (described in detail in the Oracle Fusion Payroll Guide) can also
be used to create element entries for a person.
Salary Basis and Compensation

Once you have created the elements that are meant to hold the payee basic salary and compensation information,
you can perform the setup required to attribute the gross compensation to the payee.
To set up the salary basis:

1. Sign in to the application with a role that has compensation administrator privileges, such as
CMP_ADMIN_ALL.
2. Navigate to Compensation work area.
Figure 214. Compensation Work Area Navigation

3. Select Manage Salary Basis, and then click Create.
Figure 215. Manage Salary Basis

4. On the Salary Basis page, select the element to use for the salary basis and provide the required
information.
Figure 216. Manage Salary Basis: Details
Individual Compensation
To create a compensation plan, such as for a car allowance:
1. In the Compensation work area, select Manage Plans and click Create:

Figure 217. Manage Plans
2. Select the payroll element for the compensation plan, such as a car allowance:
Figure 218. Create Individual Compensation Plan: Payroll Element

3. Select the Dates tab and set the payment start and end dates:
Figure 219. Create Individual Compensation Plan: Payment Start and End Dates
4. Select the Eligibility tab to define eligibility for the plan:
Figure 220. Create Individual Compensation Plan: Eligibility

5. Select the Plan Access tab and indicate whether to restrict access to this plan:

Figure 221. Create Individual Compensation Plan: Plan Access
6. Select the Instruction Text tab and add any user instructions you want to associate with the plan.
Figure 222. Create Individual Compensation Plan: Instruction Text
Assigning Salary Basis and Compensation to a Payee

Once you have completed setup for Salary Basis and Compensation, you can assign them to the payee.
Adding a Salary
To add a salary:
1. Select Manage Salary in the Person Management work area:
Figure 223. Manage Salary

2. Click Create, then complete the fields on the Add Salary window:
Figure 224. Add Salary

3. On the Manage Salary page, select the previously created Salary Basis and enter a Salary Amount,
such as 2000 EUR per month:

Figure 225. Manage Salary: Salary Details
When you save this record, an element entry with the specified start and end dates is automatically generated. You
can view the entry on the Manage Elements page:
Figure 226. Manage Salary: Element Entries
Note: An annualized value of the compensation is given to the Salary Basis. The salary element entry is
passed to the Gross Compensation calculation process, which prepares compensation data for the Payroll
Interface.
Adding Compensation
1. Select Manage Compensation in the Person Management work area
Figure 227. Manage Compensation

2. On the Manage Compensation page, click Award Compensation:

Figure 228. Manage Compensation: Award Compensation
3. On the Award Compensation window, select the previously created compensation plan and enter the
compensation amount, such as 500 EUR for Car allowance:
Figure 229. Manage Compensation: Award Compensation Details
When you save this record, an element entry with the specified start and end dates is automatically generated. You
can view the entry on the Manage Elements page:
Figure 230. Manage Compensation: Element Entries

Running Global Reports for Netherlands
A set of global reports is available with the Netherlands localization and can now be run for a Dutch legal entity:
Worker Data Validation Report

Payroll Balance Report
Element Result Report
Worker Data Validation Report

Global organizations with several thousand workers may have some employee data that is missing or invalid and
that needs corrective action. It would prove challenging to verify and correct data without a simple way to identify the
list of workers whose data require action before the processes or reports are run. The Worker Data Validation
Report for the Netherlands enables you to generate a list of employees with missing or noncompliant statutory HR
data.
Based on this report output, the user can take the necessary action to enter or correct the data before running the
dependent processes or reports.
Examples of where there could be missing or non-compliant data are:
At the time of data entry, required information for a statutory process is unavailable.
Some of the data being migrated from previous applications and required for running the statutory processes
might be unavailable during migration or might be statutorily non-compliant.
This data might not be needed by customers running legal processes or reports with third-party providers. Hence,
these validations are not enforced at a UI level. The report helps users by providing:
The list of employees who have either missing data or statutorily noncompliant data.
Details of the business rule and a validation message to enable the user to know which data to enter or correct.
Validations Delivered for the Netherlands

For Netherlands, a set of validations is delivered to identify missing data that might impact legal reporting.
Validations are provided at the following levels:
Organization
Person
Assignment
The validation at each level is described further here.
Organization
A reporting establishment must be in the legal employer organization.
Person
A value for the attribute Address is required
A house or building number is required if the address includes a house or building number addition.
The postal code must follow the format NNNNAA, where N is a number and A is either an uppercase or a
lowercase letter, for example, 2412DC.
A value for the attribute Name Initials is required.
A value for the attribute First Name is required.
A value for the attribute Marital Status is required.

A value for the attribute Date of Birth is required.
Assignment
A reporting establishment is required for the assignment.
A payroll is required for the assignment.
Additional validations can be set up at implementation level as described in MOS document: Oracle Fusion HRMS:
Data Validation Report (https://support.oracle.com/epmos/faces/DocumentDisplay?id=1964959.1)
Run Worker Data Validation Report

This section explains the steps to submit or run the Worker Data Validation Report.
1. Sign in to the Oracle Fusion application using a role that has a Payroll Manager profile and navigate to the
Checklist work area.
2. Select Run Worker Data Validation Report:
Figure 231. Run Worker Data Validation Report

3. Enter the parameters to be used in running the report:
Figure 232. Run Worker Data Validation Report: Parameters

Payroll Flow: Identifier for the process being run. You can enter a value each time the process is executed.
You can choose any format to describe the payroll flow.
Effective As-of Date: Data status will be evaluated as of the selected effective date.
Legal Employer: It is mandatory to select the Legal Employer for which the report must be run.
4. Submit the report.

Figure 233. Run Worker Data Validation Report: Review
5. Click OK and View Checklist.
6. When the process is completed successfully, click Go to Task.
Figure 234. Run Worker Data Validation Report: Task Details

7. In the Processes and Reports tab, click View Results.
Figure 235. Run Worker Data Validation Report: View Results
8. Select the file under File Name or URL to view the output.

Figure 236. Run Worker Data Validation Report: View Results
Figure 237. Run Worker Data Validation Report: Example
Payroll Balance Report

The Payroll Balance Report is a reconciliation report. This report extracts the run balance results for a specific
period, which can be used to check or verify the values of other reports. The report is driven by Payroll, PSU, TRU
and Employee Name in the specified order.
You must run this report after the Gross Compensation calculation process.
You can run this report for a single employee. Use this report when there is an issue with an employee and you
need to view the results for that single employee to help diagnose the problem. The report shows all the results for
an employee.
The report shows Run balance dimensions.
It displays balances connected to the following balance groups:

GLB_DEDUCTIONS_BALANCE_GROUP
GLB_EMPLOYER_CHARGES_BALANCE_GROUP
GLB_SOE_EARNINGS_BALANCE_GROUP
ORA_DAYS_BALANCE_GROUP
ORA_OTHER_UNITS_BALANCE_GROUP
Run Payroll Balance Report

1. Select the Submit a Process or Report task in the Payroll Checklist work area.

2. Select the LDG for which the process is to be run and the flow pattern Run Payroll Balance Report:
Figure 238. Run Payroll Balance Report
3. Enter parameters to run the report:
Figure 239. Run Payroll Balance Report: Parameters
Payroll: Payroll definition for which the payroll is run.
Process Start Date: Start date of the process for which the payroll is run.
Process End Date: End date of the process for which the payroll is run.

Consolidation Group: Select the name of the consolidation group.
Payroll Statutory Unit: Limits the output to a specific PSU.
Tax Reporting Unit: Limits the output to a specific TRU.
Balance Category: Limits the output to a specific Balance Category, for example Standard Earnings.
Location: Limits the output to a specific location.
Payroll Relationship Group: Limits the output to a predefined group of Payroll Relationships.
Person: Limits the output to a selected person.
Process Configuration Group: Select a Process Configuration Group if you want a log file generated for
the report.
4. Click Next twice then click Submit to submit the process.
Figure 240. Run Payroll Balance Report: Parameters

5. Verify that the process ran successfully then click Go to Task to check the results:
Figure 241. Run Payroll Balance Report: Task Details

6. View the report results:

Figure 242. Run Payroll Balance Report: View Results
Figure 243. Run Payroll Balance Report: Example
Element Result Report

The Element Result Report usually runs every pay period and it gives the earnings or deduction amounts for the
selected elements. The report must be run after the Gross Compensation calculation process.
You can sort this report by Employee Full Name, Payroll Relationship, and Process Date.
If two reports are run on the same date, the reports display data by Payroll Name in ascending order. The report is
based on the Run Results.
The report displays balances connected to the following balance groups:

GLB_DEDUCTIONS_BALANCE_GROUP
GLB_SOE_EARNINGS_BALANCE_GROUP
GLB_EMPLOYER_CHARGES_BALANCE_GROUP
Run Element Result Report

1. Select the Submit a Process or Report task in the Payroll Checklist work area.
2. Select the LDG for which the process is to be run and the flow pattern Run Element Result Report:
Figure 244. Run Element Results Register

3. Enter parameters to run the report:
Figure 245. Run Element Results Register: Parameters
Process Start Date: Start date of the process for which the payroll is run.
Process End Date: End date of the process for which the payroll is run.
Payroll: Payroll definition for which the payroll is run.

Payroll Statutory Unit: Limits the output to a specific PSU.
Tax Reporting Unit: Limits the output to a specific TRU.
Balance: Limits the output to a specific Balance.
Balance Category: Limits the output to a specific Balance Category, for example Standard Earnings.
Location: Limits the output to a specific location.
Person: Limits the output to a selected person.
Process Configuration Group: Select a Process Configuration Group if you want a log file generated for
the report.
4. Click Next twice then click Submit to submit the process.
Figure 246. Run Element Results Register: Submit

5. Verify that the process ran successfully then click Go to Task to check the results:
Figure 247. Run Element Results Register: Task Details
6. View the report results:

Figure 248. Run Element Results Register: View Results
Figure 249. Run Element Results Register: Example
Common Lookups Customization Level

The customization level of the following common lookups are modified from Extensible to User.
Caution: Do not update or delete the delivered lookup values.
CONTACT
MAR_STATUS
PER_HIGHEST_EDUCATION_LEVEL
PER_NATIONAL_IDENTIFIER_TYPE
PER_ETHNICITY
PER_VISA_PERMIT_TYPE

Conclusion
This document has provided a set of information useful for anyone implementing or using Oracle Fusion Human
Capital Management HR for the Netherlands.
In order to verify that all the tasks needed in an Oracle Fusion Human Capital Management implementation have
been performed, we recommend referring to the documents mentioned in the Other Information Sources section.

Glossary
BSN
BSN (Burgerservicenummer) is the Citizen Service Number or Tax and Social Insurance Number national identifier
for the Netherlands.
Business unit
Business Unit is a unit of an enterprise that performs one or many business functions that can be rolled up in a
management hierarchy. A business unit can process transactions on behalf of many legal entities.
Consolidation group
Consolidation group is a grouping of payroll runs within the same time period for which you can schedule reporting,
costing, and post-run processing.
Calculation card
A mechanism for capturing values required for calculating payroll deductions at the level of a payroll statutory unit,
tax reporting unit, or payroll relationship. At the payroll relationship level, this is called a personal calculation card. At
the tax reporting unit level, it is the employer deduction information card, also referred to as the TRU card.
Calculation component
An individual calculation captured on a calculation card. Typically relates to a calculation element for which the
calculation component creates an entry.
Department
Department is a division of a business enterprise dealing with a particular area of activity.
Division
Division is a business-oriented subdivision within an enterprise. Each division is organized to deliver products and
services or address different markets.
Enterprise
Enterprise is an organization with one or more legal entities under common control.
Flexfield
Grouping of extensible data fields called segments, where each segment is an attribute added to an entity for
capturing additional information.
Gatekeeper Law
Dutch legislation (Wet Verbetering Poortwachter) that describes the process, schedule, and documentation to which
an employer must conform to support the return to work of an employee who has been on an extended, or repeated
(and related) pattern of sickness absence.
Geography structure
A hierarchical grouping of geography types for a country. For example, the geography structure for United States is:
State, County, City, and then Postal Code.

Identifying jurisdiction
The first jurisdiction a legal entity or establishment must register with to be allowed to do business in a country.
Legal authority
A government or legal body that is charged with powers such as make laws, levy and collect fees and taxes, and
remit financial appropriations for a given jurisdiction.
Legal employer
Legal employer is a legal entity that employs people.
Legal entity
An entity is identified and given rights and responsibilities under commercial law, through the registration with the
country's appropriate authority.
Legal jurisdiction
Legal jurisdiction is a physical territory, such as a group of countries, single country, state, county, parish, or city,
which comes under the purview of a legal authority.
Legal reporting unit
Legal reporting unit is the lowest level component of a legal structure that requires registrations. Used to group
workers for the purpose of tax and social insurance reporting or represent a part of your enterprise with a specific
statutory or tax reporting obligation.
Legislative data group
Legislative data group is a means of partitioning payroll and related data. At least one legislative data group is
required for each country where an enterprise operates. Each legislative data group is associated with one or more
payroll statutory units.
Location
Location is the physical address of a workforce structure, such as a department or a job.
Payroll statutory unit
A legal entity registered to report payroll tax and social insurance. A legal employer can also be a payroll statutory
unit, but a payroll statutory unit can represent multiple legal employers.
Process configuration group
A group of action parameters that set options, mainly related to performance and logging, for payroll processes. A
few parameters control other features, such as element templates, dates, and report output location.
Registration
The record of a party's identity related details with the appropriate government or legal authorities for the purpose of
claiming and ensuring legal and or commercial rights and responsibilities.
Reporting establishment
An organization used in the production of human resources (HR) reports that are required by government agencies.

Tax reporting unit
Tax reporting unit is a legal entity that groups workers for the purpose of tax and social insurance reporting.
SEPA
The Single Euro Payments Area (SEPA) will be the area where citizens, companies and other economic actors will
be able to make and receive payments in euro, within Europe, whether between or within national boundaries under
the same basic conditions, rights and obligations, regardless of their location.

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 2017, 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. 0817
White Paper Title: Oracle Fusion HCM (Netherlands): HR Implementation and Functional Consideration
August 2017
Author: Pawan Kumar
Contributing Authors: Julia Margetson
1 | ORACLE FUSION HCM (NETHERLANDS): HR IMPLEMENTATION AND FUNCTIONAL CONSIDERATIONS

NL HR Setup PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

NL HR Setup PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

Oracle Fusion HCM (Netherlands):

HR Implementation and Functional Considerations

ORACLE WHITE PAPER |MAY 2017

ORACLE FUSION HCM (NETHERLANDS): HR IMPLEMENTATION AND FUNCTIONAL CONSIDERATIONS

Whats in this Document 6

Other Information Sources 6

Comments and Suggestions 2

Creating an Implementation Project 3

Defining Enterprise Structures 5

Legislative Data Groups 10

Legal Employers and Payroll Statutory Units (PSUs): Overview 11

Legal Reporting Units and Tax Reporting Units: Overview 11

Creating Legal Entities 11

Legal Reporting Units 15

Legal Reporting Unit Registrations 17

ORACLE FUSION HCM (NETHERLANDS): HR IMPLEMENTATION AND FUNCTIONAL CONSIDERATIONS

Organization Structure Models Supported by Dutch Localization 28

Personal Data Setup 34

Name Styles and Name Formats 35

Validations for BSN Examples 42

ORACLE FUSION HCM (NETHERLANDS): HR IMPLEMENTATION AND FUNCTIONAL CONSIDERATIONS

Maintaining Person and Employment Information 48

Payroll Processing After Termination 57

HR Reports for the Netherlands 58

First Day Notification Report 58

Run the First Day Notification Report 60

Viewing Report Output 61

Viewing Payroll Flows for a Report 61

Viewing the Report Output 63

Additional Information for Payroll Interface 66

Tax Reporting Unit (TRU) Calculation Card 66

Validations for TRU Calculation Card 70

Personal Calculation Card Automatic Creation 70

ORACLE FUSION HCM (NETHERLANDS): HR IMPLEMENTATION AND FUNCTIONAL CONSIDERATIONS

Review and Update an Automatic Statutory Deductions and Reporting Card: 70

Personal Calculation Card Manual Creation 76

Creating the Statutory Deductions and Reporting Card Manually 77

Creating Calculation Components 79

Entering Calculation Component Details for Tax component: 80

Entering Calculation Component Details for Special-Rate Tax component: 80

Creating Enterable Calculation Values for Special-Rate Tax component: 81

Validations for Personal Calculation Card 85

Assigning Legal Entities to Primary Ledger 89

Organization Payment Methods 89

Net Pay Balance 91

Consolidation Groups and Payroll Definitions 93

Person Payment Information 96

Assigning a Payroll to the Employee 96

ORACLE FUSION HCM (NETHERLANDS): HR IMPLEMENTATION AND FUNCTIONAL CONSIDERATIONS

Elements and Element Templates 98

Availability of Element Template Functionality Based on Customer License 98

Setting up the License Information (Before Release8) 98

Setting up the License Information (Release8 onwards) 100

Using Element Templates 101

Element Entries 105

Salary Basis and Compensation 105

Individual Compensation 106

Assigning Salary Basis and Compensation to a Payee 108

Adding a Salary 108

Adding Compensation 109

Running Global Reports for Netherlands 111

Worker Data Validation Report 111

Validations Delivered for the Netherlands 111