Release 13 21.D UK HR Setup

Oracle HCM Cloud (UK)
HR Implementation and
Functional Considerations
Implementation and Functional Considerations Product Paper
Month 10, 2021 | Version 21D

Copyright © 2021, Oracle and/or its affiliates
Confidential: Public
PURPOSE STATEMENT
This document provides an overview of features and enhancements included in release 21D. It is intended solely to help you
assess the business benefits of upgrading to 21.07 and to plan your I.T. projects.
DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of
Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software
license and service agreement, which has been executed and with which you agree to comply. This document and
information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without
prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the implementation
and upgrade of the product features described. 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 in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document
without risking significant destabilization of the code.
Note: In the images or examples included in this document regarding: user details, company names, addresses,
emails, and/or telephone numbers represent a fictitious sample of data (based upon made up data used in a demo
environment). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
1 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

Copyright © 2021, Oracle and/or its affiliates | Confidential: Public
Contents
Purpose Statement ...................................................................................................... 1
Disclaimer ..................................................................................................................... 1
Introduction ................................................................................................................. 4
Further Information ....................................................................................................................................4
Other Information Sources .................................................................................................................................4
Organizational Structures and Additional Data Capture ......................................... 5

Enterprise ................................................................................................................................................................ 5
Create an Implementation Project .......................................................................................................... 5
Manage Payroll Product Usage ................................................................................................................ 5
Manage Geographies .................................................................................................................................6
Verify Geographies......................................................................................................................................6
Cleanse Address ..........................................................................................................................................6
Load Geography Data ................................................................................................................................6
Define Enterprise Structures............................................................................................................................... 7
Legal Jurisdictions................................................................................................................................................. 7
Legal Addresses .....................................................................................................................................................8
Legal Authorities....................................................................................................................................................8
Legislative Data Groups .......................................................................................................................................9
Legal Entities ..........................................................................................................................................................9
Legal Employers and Payroll Statutory Units .................................................................................................9
Legal Reporting Units and Tax Reporting Units .......................................................................................... 10
Organization Structure Models ........................................................................................................................ 10
Create Legal Entities ............................................................................................................................................ 11
Create Legal Entity Registrations ..................................................................................................................... 11
Legal Entity HCM Information for Legal Employers and Payroll Statutory Units................................ 12
Legal Entity Calculation Cards.......................................................................................................................... 12
Taxes ............................................................................................................................................................ 12
National Insurance .................................................................................................................................... 13
Create Legal Reporting Units............................................................................................................................ 13
Set Up Default Behaviour for TRU Calculation cards........................................................................ 14
Set Up Unique ID Lists for FPS Reporting............................................................................................ 14
Create Legal Reporting Unit HCM Information .................................................................................. 15
UK Tax Reporting Unit Information ...................................................................................................... 16
UK TRU RTI Information .......................................................................................................................... 16
Business Units ...................................................................................................................................................... 17
Workforce Structures................................................................................................. 18
Locations ............................................................................................................................................................... 18
Divisions................................................................................................................................................................. 18
Departments ......................................................................................................................................................... 18
Reporting Establishments ................................................................................................................................. 18
Action Reasons..................................................................................................................................................... 19
Personal Data setup .................................................................................................. 20

Addresses ............................................................................................................................................................. 20
Address Validation ............................................................................................................................................. 20
Address Mapping ............................................................................................................................................... 20
Names .................................................................................................................................................................... 21
Legislative Information ...................................................................................................................................... 21
National Identifiers .............................................................................................................................................. 22
Employment Indermediaries ............................................................................................................................ 22
Disability ................................................................................................................................................................ 22
Additional Information for payroll and payroll Interface ....................................... 22

Payroll Processing after Termination ............................................................................................................ 24

Statututory Deductions Calculation Card ..................................................................................................... 24
Banking Setup ........................................................................................................... 24

Banks ......................................................................................................................................................................25
Bank Branches .....................................................................................................................................................25
Bank Accounts .....................................................................................................................................................25
Organization Payment Methods .............................................................................. 26

Net Pay Balance .................................................................................................................................................. 26
Consolidation Groups ................................................................................................27

Payroll Definitions .................................................................................................... 28
Elements and Compensation ................................................................................... 29
Elements and Element Templates ................................................................................................................. 29
Element Entries ......................................................................................................... 30

INTRODUCTION
This paper identifies and describes HR setup tasks for Oracle Fusion Human Capital Management for the UK.
This document is intended to support the implementation team in understanding:
» The organizational structures that need to be defined to manage HR processes for the UK.
» The UK-specific data that needs to be provided.
» Where predefined UK-specific data can be integrated with customer-specific data.
» The data that needs to be defined to hire and maintain a UK worker.
» The UK-specific business rules that have been implemented.
» The HR processes that can be executed for the UK.
» Information required to support interfacing or transferring data to a third-party payroll system.
» The migration process from a legacy system, by identifying the UK-specific fields that need to be populated by such
migration.
This document may also be beneficial to end users who run application processes after the implementation.
Note: This document should not be considered a comprehensive guide for HR implementations. The focus of this document
is UK-specific processes and information. For information about generic tasks, the implementation team should refer to
documentation listed in the following section.
Further Information
You must use this product paper in conjunction with the other Oracle Fusion HRMS UK products papers:
Oracle Fusion HRMS (UK): Payroll Implementation and Functional Considerations (Doc ID 1921464.1)
Oracle Fusion HRMS (UK): Pensions Automatic Enrolment and Functional Considerations (Doc ID 2006584.1)
Other Information Sources

On the Oracle Help Center, see:
» Implementing Global Human Resources
» Implementing Global Payroll
» Implementing Global Payroll Interface
» Implementing Payroll for the United Kingdom
» Administering Payroll for the United Kingdom
» Using Global Payroll Flows
» Using Global Payroll Interface
» Using Global Human Resources
» Using Global Payroll
» Administering Global Payroll

ORGANIZATIONAL STRUCTURES AND ADDITIONAL DATA CAPTURE
Before a customer can hire a UK worker 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 UK 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, you can 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.
Since there is no concept of legislation at the enterprise level, no UK-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.
Create an Implementation Project

The setup tasks for organization structures should be defined in an implementation project. Follow these steps to create an
implementation project:
Sign in to the Oracle Fusion application using a role that has the profile of an implementation consultant and privileges to
create all organizational structures.
» To do this, go to Setup and Maintenance -> Manage Implementation Projects -> Create.
» Select Workforce Deployment as the offering, and optionally other components beneath it, such as Workforce Management,
Absences or Payroll.
» Click Save and Open Project.
Manage Payroll Product Usage

Before you use any localization, you must state how you will use that product. Each localization has one of 3 possible settings:
» None. This indicates that only the HR functionality of the localization will be used.
» Payroll Interface. This indicates that you will be using the HR functionality, and interfacing to a 3rd party payroll via the inbuilt payroll
interface
» Payroll. This indicates that you plan to use the full HR and payroll functionality for the chosen localization.
Follow these steps to set your product usage:
1. Navigate to Define Common Applications Configuration for Human Capital Management -> Define Feature by Country or
Territory -> Features by Country or Territory-> Go to Task.
2. Select the United Kingdom Legislation
3. Click Edit and set the correct usage in the Selected Extensions.

Manage Geographies
Geography information is used in Oracle Fusion applications for address entry and geography-based business processes,
such as territory management and shipping. Through Manage Geographies task you can define new, or manage existing,
geography structures (such as country, state, city), geography hierarchies, and geography validations for a country.
The load of geography data is typically done via a geo loader, and is outside of the scope of this document.
Verify Geographies
Before defining enterprise structures, the implementation team must load and verify predefined geographies and load any
additionally required local geographies.
Follow these steps to verify predefined geographies:
1. Go to Manage Geographies.
2. Select GB within Country code and click Search to view the predefined United Kingdom geography setup and content.
3. Click on the checkmark to open the associated setup data:
These are the items of geography that need to be validated.
Cleanse Address
Address cleansing validates and corrects the address information that you enter. Address cleansing validates both the
geography attributes and the address line attributes.
You can specify the real-time address cleansing level:

» None: Specifies no real time address cleansing.
» Optional: Provides option to cleanse addresses.
Once you have enabled address cleansing, a Verify Address icon appears at address entry points in the application. Click the
icon to perform address cleansing and receive a corrected, standardized address. If the application doesn't find a matching
address, then an alert message is displayed.
Load Geography Data

Refer to the document Implementing Global Human Resources, specifically the chapter Geographies for HCM.

Define 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.
Legal Jurisdictions
All legal entities must be registered against a jurisdiction that is governed by a legal authority. A legal jurisdiction is a
combination of the legislative category (such as labour law, transaction tax law, or income tax law) and the physical territory
(such as a group of countries, a country, a state, or a county) to which legal rules are defined. A tax jurisdiction is a geographic
area where a tax is levied by a specific tax authority. Jurisdictions must be set up before creating registrations, because a
jurisdiction is required in the registration process. A jurisdiction can also have a start date and end date to show when the
jurisdiction is effective and when you can register against it.
A predefined jurisdiction called United Kingdom HMRC is provided for your use when registering UK legal entities. To view
this jurisdiction:
1. Select Manage Legal Jurisdictions in the implementation project task list.
2. On the Manage Legal Jurisdictions page, select United Kingdom in the Territory field, and click Search.
3. Select United Kingdom HMRC in the Search Results to display the Edit Legal Jurisdictions page:
The predefined values for this jurisdiction are stored in the record XLE_JURISDICTIONS_B
NAME COLUMN VALUES COMMENTS
Name Name United Kingdom

HMRC
Territory TERRITORY United Kingdom
Legislative LEGISLATIVE_CAT_CODE HRX_GB_HMRC The value HMRC is

Category predefined in lookup type
LEGISLATIVE_CATEGORY
Identifying IDENTIFYING No Indicates that

registrations under this
jurisdiction are not
created automatically

Legal Entity REGISTRATION_CODE_RN RN Indicates that the legal
Registration entity registration
code number is used to
uniquely identify legal
entities to the legal
authority
Legal REGISTRATION_CODE_ETB HRX_GB_PAYE_REF Indicates that the TRU

Reporting registration number is the
Unit PAYE scheme number
Registration that is used to uniquely
code identify the TRU to this
legal authority. The value
PAYE Scheme is
predefined for the UK in
lookup type
XLE_REG_CODE_EST.
Note: An identifying jurisdiction is the one that is automatically associated with all legal entities created for the territory. It represents the
jurisdiction that a company has to register with when first created, such as the Chamber of Commerce or Companies House.
Registration information for the identifying jurisdiction is mandatory when creating a Legal Employer. Since the United Kingdom HMRC
jurisdiction is not predefined as an identifying jurisdiction, an identifying jurisdiction needs to be defined in the implementation phase.
You can create a new identifying jurisdiction or set the Identifying option to Yes for United Kingdom HMRC, which is recommended.
Do not change any other attributes of the predefined United Kingdom HMRC jurisdiction.
You can create additional jurisdictions as needed using the Manage Legal Jurisdictions task.
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 UK. You must create legal addresses for all organizational units of the
enterprise.
To define legal addresses:
1. Navigate to: Manage Legal Addresses in the implementation project task list.
2. On the Manage Legal Addresses page, click Create.
3. On the Location Create page, enter the address information and Save your work.
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 UK. 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 will register each legal entity you create unit with a legal authority.
To define legal authorities:
1. Select Manage Legal Authorities.
2. On the Manage Legal Authorities page, click Create.
3. On the Create Legal Authority page:
4. Select the Tax Authority Type based on the type of interaction. Typically, this is set to Collecting and Reporting.
5. Add one or more addresses.

6. Add one or more legislative categories, such as the predefined HMRC category. This establishes a link between the legal
authority and all jurisdictions associated with the selected legislative category.
7. 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 Legislative Data group has a context of a country.
Each Payroll Statutory Unit is attached to one Legislative Data Group and an LDG may be attached to multiple PSUs.
Payroll configuration setup can be done at the following levels:

» Country (setup is applicable for all the LDGs or PSUs of the country).
» Legislative data group (setup applicable for a set of PSUs that belongs to this LDG).
Note: a more complex setup is possible, for example, when multiple LDGs are required per legislation with one or more PSUs.
An LDG must be defined in an HR-only implementation if the customer plans to export 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 a user creates payroll data, the LDG can be derived from the payroll relationship for
the transaction via the PSU association.
To define an LDG:
» Select Manage Legislative Data Groups in the implementation project task list.
» On the Manage Legislative Data Groups page, click Create.
» On the Create Legislative Data Group page, provide the required information and save your work.
Legal Entities
A legal entity is an entity unequivocally identified and given rights and responsibilities under Commercial Law, through registration with
the territory’s 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

Oracle Fusion recognizes different types of legal entities:
A legal employer is a legal entity that employs workers. In the UK, the concept of legal employer corresponds to the concept of a
company.
A payroll statutory unit (PSU) is a legal entity that is responsible for paying workers, including the payment of PAYE and national
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.
When defining a legal entity, you must consider the context when it is used:
» If used in an HCM context, designate it as a legal employer. In an HCM implementation, it is mandatory to define legal employers.
» If used in a Payroll context, designate it as a PSU.
You can define a legal entity that is both a legal employer and a PSU.

If multiple legal employers must be grouped for tax reporting purposes, you can associate them all with a single PSU. If legal employers
do not report together, they must not share a PSU.
In general, in Italy, there is a 1.1 relationship between Legal Employer (Company) and PSU because normally legal reporting is not
done at a level higher than company.
No legal entities are predefined for the UK. You must create all legal entities that apply to the enterprise you are setting up.
Legal Reporting Units and Tax Reporting Units

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.
If LRUs are used in Oracle Fusion Payroll for tax reporting purposes, then they are considered tax reporting units (TRUs). In the Legal
Entity Configurator, when you create an LRU that belongs to a PSU, the application automatically creates a TRU in HCM and
associates it with the parent PSU. When you create an LRU that belongs to a legal employer (that is not also a PSU), you must select a
parent PSU. This way, TRUs are indirectly associated with a PSU through their association with a Legal Employer.
TRUs are especially relevant for the UK because the TRU represents the Tax reporting unit identified by the PAYE scheme.
Organization Structure Models

You can define a set of organizational units that comprise the organization structure required to manage your HR processes. Each
enterprise can combine these organizational units in a different way in order to set up the organizational model that best fits their
business needs. Before you begin creating organizational units, it is helpful to understand the organization structure models supported
by the UK localization.
These are examples of supported configurations:
» Enterprise 1: 1 PSU with 1 legal employer and 1 TRU

» Enterprise 2: 1 PSU with 1 legal employer and multiple TRUs
» Enterprise 3: 1 PSU with multiple legal employers and multiple TRUs where each legal employer is associated with a single TRU
» Enterprise 4: 1 PSU with multiple legal employers, where different employers are associated with different TRUs.
Note that an enterprise can have many PSUs of the same or different legislative data groups. Also, it is possible for a legal entity to be
both a PSU and a legal employer.

Create Legal Entities
To define legal entities:
1. Select Manage Legal Entity in the implementation project task list and click Select Scope, and Create New.
2. Select Add then click Create to display the Create Legal Entity page.
3. Provide the required information, noting the following:
If a legal entity is not designated as a payroll statutory unit, you can select an existing payroll statutory unit to which it belongs.
» The Legal Entity Identifier is just an internal code.
» An identifying jurisdiction must have been previously defined.
» You must have previously defined the legal address for the legal entity.
» Start date and end date are optional in the UI, but it is recommended to enter at least the start date.
» The type of registration information required is based on the Registration Code Assignment information you defined when
you created the selected jurisdiction.
A default LRU will be created for you with this PSU. It will have the same name and address as the Legal Entity. The
Registration Information field PAYE scheme will be used to register this default TRU with the United Kingdom HMRC
Jurisdiction. This is managed using the Manage Legal Reporting Unit Registrations task.
Create Legal Entity Registrations

Legal entities are connected to legal authorities through legal entity registrations. A registration is automatically created for the
identifying jurisdiction you select when you create a legal entity to define a legal entity registration.
1. Set the scope for this task as follows: Select Manage Legal Entity Registrations in the implementation project task list and
click Select.
2. Under Legal Entity, select Select and Add.
3. Search for and select the legal entity you just created, and then edit the already created registration.
Note: A registration was automatically created for the UK Income Tax jurisdiction when the legal entity was created, based on
the registration details provided.
If required, you can create additional registrations:
4. Click Create to add a registration.
5. Enter the required information, noting the following:

» When you select a jurisdiction, the Territory field is populated automatically.
» The Issuing Legal Authority field displays a list of legal authorities associated with the selected jurisdiction.
» The Registered Address field displays a list of predefined legal addresses.

Legal Entity HCM Information for Legal Employers and Payroll Statutory Units
Additional information about legal entities is required for Oracle HCM processes.
To provide HCM information:
1. Set the scope for this task by selecting the legal entity, as you did in Step 1 of the previous task.
2. Select Manage Legal Entity HCM Information in the implementation project task list.
If the entity is a legal employer, complete the fields on the Legal Employer tab.
Note: The Employment Model selection is critical. The UK localization supports all delivered employment models.
3. If the legal entity is also a PSU, click the Payroll Statutory Unit tab.
4. Complete the fields on this tab and click Submit.
5. If the Organization is implementing MyCSP or Teachers’ Pension, click the UK Public Sector Payroll Statutory Unit details.
6. Complete the fields on this tab and click Submit.
Note: The Fiscal Year Start for a UK customer should be April 6th of the year the enterprise is going live on Oracle Fusion HCM. It is
here at the PSU level that we associate the legislative data group.
Legal Entity Calculation Cards

You can configure default settings at the legal employer level that are used in subsequent processes. Even though you may create
default settings here, depending upon the functionality, you may also create default settings at the TRU-level, which would override the
default values at legal employer level.
To set the default values for legal entity calculation cards for Statutory Deductions, use the Manage Legal Entity Calculation Cards task
Taxes
» Create a default card of the type Organization Statutory Deductions and set the appropriate effective date
» Click on PAYE Default Values Calculation Component and add the Pay As You Earn Default component details.
» Expand the Pay as You Earn Default Component Details
Here are the defaults that are available:
• P45 Action: The Employee’s calculation card, when created, will be created with the P45 Action specified here.
• Do not issue: Do not issue a P45
• Issue when final pay in previous period: Issue P45 based on the latest payroll run before the termination date.
• Note: This final payroll run must be in the tax year
• Issue When final pay on or after termination: Issue P45 based on the payroll which runs on or after the termination date.
• Manual issue: P45 is produced and given to employee manually. In this case Fusion will not produce a P45
» Enable FPS to update tax code if payment after P45: If checked, the FPS process will update the employee’s calculation card with
the Tax Code and Tax Basis used in the PAYE calculation. This FPS run is reporting the payroll run calculation which was the first
payroll run for this HMRC Payroll ID after the P45 was issued. The calculation card is updated as at the effective date of the first
payroll run after the P45 has been issued.
» Enable automatic new starter creation: Although the Statutory Deduction calculation card may be automatically created on hire,
the new starter declaration will not be automatically created. Select this checkbox for the new starter declaration to be created
automatically.
Note: the new starter component must exist (either via automatic creation, or via manual adding, or via HDL), before the
Employee Self Service New starter declaration can be used. Therefore we advise you enable automatic creation of new
starter component.
» Irregular Employment Payment: The Employee’s Irregular Employment Payment indicator is on the employee’s PAYE card
component. The value here is defaulted to the PAYE component for new hires. Where no value is entered or the component doesn’t
exist, it will be left null on the employee’s component during New Hire.

» Enable automatic PAYE tax code updates: Check this to allow update of the PAYE component Tax Code when the employee
completes an employee Self Service New Starter declaration.
If no P45 has been provided, the Tax Code and Tax Basis will be automatically updated:
» Declaration A: default tax code and Cumulative Tax Basis

» Declaration B: default tax code and Non-cumulative Tax Basis
» Declaration C: BR Tax Code, and Cumulative Tax Basis
If a P45 has been provided, the Tax Code and Tax Basis as shown on the P45 should be manually entered on the PAYE component,
the PAYE component will not be updated in this case.
» Enable automatic student loan updates: Check this to allow creation of the Court Orders and Student Loan Card, and a Student
Loan component, when the employee completes the relevant section in an employee Self Service New Starter declaration.
» Enable automatic postgraduate loan updates: Check this to allow creation of the Court Orders and Student Loan Card, and a
Post Graduate Loan component, when the employee completes the relevant section in an employee Self Service New Starter
declaration.
» Statutory Report Person Identifier: By default, the P60, P45 and P11D reports identify the employee by showing the HMRC
Payroll ID. You can choose Person Number if you prefer. Note, for payslip, you will have to customize your payslip template to show the
Person number, as the default template shows HMRC Payroll ID.
National Insurance
Click on National Insurance and add the Calculation Component and component details as seen below. Expand the National Insurance
Component Details:
These defaults are available:

» Default NI Category: When a Statutory Deductions calculation card is created for a new hire, the NI category will be defaulted, as
specified here.
» Default Pension Basis: When a Statutory Deductions calculation card is created for a new hire, the Pension Basis will be defaulted,
as specified here.
» Default SCON: This is disused, and is present only for historic purposes.
» Disable automatic card creation. By default, a new hire will automatically create a Statutory Deductions card, with NI and PAYE
components. Check this check box to disable this functionality.
You can add you default and save the values.
For more information, see Oracle Fusion HCM (UK): Pensions Automatic Enrolment Functional and Implementation Considerations on
My Oracle Support (MOS). Document ID 2006584.1
For more information on the Involuntary Deductions card, see Oracle Fusion HCM (UK): Court Orders and Student Loans Functional
and Implementation Considerations on My Oracle Support (MOS). Document ID 2009287.1.
Create Legal Reporting Units

To create a LRU (or a TRU, as it is referred to in HCM):
1. To set the scope for this task, select Manage Legal Reporting Unit in the task list.
2. On the Scope Selection window, select Create New and click Apply and go to Task.
a. An LRU with the same name as the previously created legal entity has been created by default.
b. The LRU is designated as the main, or primary, legal reporting unit for the legal entity.
3. To create a second LRU for this legal entity, enter the required information on the Manage Legal Reporting Unit page:
c. Set Legal Entity to your Legal Entity
d. Set Legal Reporting unit to ‘Create New’
4. Click apply and Go to Task.

5. You must provide the PAYE Scheme. The PAYE Scheme must be in the specified format, for example, CCC/12345. You
must enter a forward slash character to separate the two components of the PAYE scheme.
Note: When performing a global transfer of an employee from another legislation to a UK legislation, ensure that the
Jurisdiction entered is a United Kingdom HMRC and is registered with ‘United Kingdom HMRC’, as above, if the employee is
to be successfully transferred into the TRU.
Additional HCM information is required for a UK TRU. To do this you must set the default behavior for the TRU calculation cards as
described in the subsequent sections.
Set Up Default Behaviour for TRU Calculation cards

You can create defaults for various calculation cards at the Legal Employer level. You can also specify default values at the TRU level.
The TRU level values will override the Legal Employer level defaults.
To set the default values for TRU calculation cards:
1. Navigate to Manage Legal Reporting Unit Calculation Cards
2. Follow the steps described in the section Legal Entity calculation cards to set the default values.
Set Up Unique ID Lists for FPS Reporting

Before you provide HCM information for a UK TRU, if you want to submit your FPS file in sub-sets for your TRU(s), you must first create
a lookup type containing a list of unique IDs that can be used when submitting FPS returns for that TRU. Each unique ID represents a
part or subdivision of that TRU’s FPS Submission. For example, a TRU might subdivide its FPS submissions into 4 parts or batches,
with one XML file for each part. When you associate a person’s statutory calculations card with a TRU, you can also select one of these
unique IDs to indicate which part of the EOY submission (that is, which part) will include this person’s FPS information. This also
ensures that all employments within a calculation card are reported in the same file.
No unique ID lookup types are predefined for the UK.
To create a lookup type for a unique ID list:
1. Select Manage Common Lookups from the implementation project task list.
2. Click Create.
3. On the Manage Common Lookups page, enter the Lookup Type, Meaning, Description, and Module.
Note: The Lookup Type name must include the string ‘UNIQUE_ID”. In the Module field, enter a value that describes
the how the lookup is used, such as ‘GB FPS Unique IDs’.

4. Save the lookup type, then create a lookup code, within this lookup type, for each unique ID that this TRU can submit.
5. Save your work.
Points to Consider:
» Each lookup code meaning identifies one part or subdivision of the FPS submission. Each part can be submitted in a separate
batch to HMRC, so these parts are also referred to as batches and each batch has a unique id.
» Display Sequence indicates the order in which lookup values will appear in the calculation card UI.
» Leave the Tag field blank.
Lookup codes in this lookup type will be hidden from the user, but the Meaning will be displayed in the calculation card UI and the FPS
archive and reports. The meaning will also be validated in FPS processing as per HMRC specification.
After you have defined a unique ID lookup type, you can assign it to a TRU, as described in the next section. A lookup type can be
shared across multiple TRUs. When a Payroll user creates a calculation card for an employee, they can select a unique ID from the
unique ID list defined for the TRU associated with the calculation card.
Note: Once the TRU with the Unique ID lookup type and lookup codes is in use, the name of the lookup type on the TRU must never be
edited or modified.
Create Legal Reporting Unit HCM Information

Additional information about legal reporting units (LRUs), referred to as tax reporting units in this context, is required for Oracle HCM
processes.
To create LRU HCM information:
1. To set the scope for this task, select the parent legal entity and then the legal reporting unit, as described in previous tasks.
2. Select Manage Legal Reporting Unit HCM Information in the implementation project task list.
3. On the Manage Legal Reporting Unit HCM Information page, select the UK Tax Reporting Unit Details.
4. Complete the following fields and click Submit:

UK Tax Reporting Unit Information
» ECON (Employer Contracted Out Number): Identifier given by the UK authorities to an employer that contracts out of the state
pension scheme. Note: From April 2016 this is only required for historic reporting and data integrity.
» EDI Sender ID: Unique identifier given to the employer by HMRC to identify the sender of any EDI files sent by the employer to
HMRC.
» HMRC Office Phone
» Unique ID List: Defines the lookup type containing the list of unique IDs for this tax reporting unit. When you associate a person’s
statutory deduction calculation card with a TRU, you can also optionally pick a unique ID from this list.
» Employer Accounts Office Reference Number: This is a Unique identifier issued to the employer by the HMRC Accounts Office
and will be present on all RTI message files relating to payments due or made.
» Service Company: This indicates a company that operates Intermediaries legislation, sometimes known as IR35.
» Corporation Tax Reference: This is a unique identifier issued by HMRC to the employer who pays income tax
» Self-Assessment Unique Identifier: This is a unique identifier issued by HMRC to anyone who needs to submit self-assessment for
taxation, for organizations that are sole proprietors or partnerships.
» Employment Allowance Indicator: Posted to the Employment Allowance Indicator in the EPS file.
» Account Holder Name: Posted to the Account Holder Name field in the EPS file.
» Branch sort code: Posted to the Branch sort code field in the EPS file.
» Account Number: Posted to the Account Number field in the EPS file.
» Building Society Reference: Posted to the Building Society Reference field in the EPS file.
» Late PAYE Reporting Reason: Posted to the Late PAYE Reporting Reason field in the FPS file.
» DEO Employer Reference: This is used in the court Order reports for CMS DEO and DEA.
» Exclude from apprenticeship Levy: If selected, the NI Earnings of any employee who reports to this TRU will be excluded from the
Apprenticeship Levy calculation.
» Apprenticeship Levy Apportioned Allowance: There is an allowance for apprenticeship levy. However, where there are multiple
TRUs, this field is used to apportion the allowance between the various TRUs.
» Apprenticeship Levy Employers Pay Bill YTD: If a customer migrates to Oracle Fusion HCM during the tax year, use this field to
hold the Year to Date value of the Employer’s Pay Bill to include it for reporting.
» Apprenticeship Levy Employers Pay Bill Date: Use this date to identify which tax year the Apprenticeship Levy Employees Pay
Bill YTD relates to. This is only expected to be used in the tax year that the migration to Fusion takes place.
» Agricultural sector: Used by the EPS process to classify the employer.
» Industrial sector: Used by the EPS process to classify the employer.
» Fisheries sector: Used by the EPS process to classify the employer.
» Road Transport sector: Used by the EPS process to classify the employer.
» State Aid rules do not apply: Used by the EPS process to classify the employer.
UK TRU RTI Information

» Sender ID: Used in HMRC data transfers.
» Hidden Authentication Value: Used in HMRC data web service calls (for example, transmission of the FPS and receiving the P6).
» P6 Highest Index Retrieved: The respective GOT number.
» P9 Highest Index Retrieved: The respective GOT number.
» SL1 Highest Index Retrieved: The respective GOT number.
» SL2 Highest Index Retrieved: The respective GOT number.
» RTI Highest Index Retrieved: The respective GOT number.
» PGL1 Highest Index Retrieved: The respective GOT number.
» PGL2 Highest Index Retrieved: The respective GOT 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 UK-specific data are required or captured at this level. However, it is mandatory to 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.
2. Click Create.
3. On the Create Business Unit page, provide the required information:
4. Note: You must have previously created the location and default set. (Default sets are created using the Manage Reference
Data Sets task.

WORKFORCE STRUCTURES
Workforce structure setup is performed once the 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 UK. 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.
To create or manage locations:
1. Select Manage Locations in the implementation project task list.
2. Click Create.
3. On the Create Location page, provide the required information and click Submit.
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 UK-specific attributes are stored here.
To create divisions:
1. Select Manage Divisions in the implementation project task list:
2. Click Create.
3. On the Create Division page, enter the required information.
4. 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.
No data is required or captured at this level for the UK, but implementation teams can create a department structure for an enterprise in
the organizational structure setup phase of the project.
To create departments:
1. Select Manage Departments in the implementation project task list:
2. Click Create.
3. On the Create Department page, provide the required information.
Note: If a location is associated to a department, when the department is associated to another entity such as a
worker, this location will also be connected to that entity by default.
4. Click Next to provide additional department details, and then review and submit.
Reporting Establishments
A reporting establishment represents an organizational unit used for statutory reporting, other than tax or social insurance reporting.
You can create a new reporting establishment, or you can select an existing TRU and define it as a reporting establishment.

To create reporting establishments:
1. Select Manage Reporting Establishments in the implementation project task list.
2. Click Create.
3. On the Create Reporting Establishment page, select Create New to create a new reporting establishment or choose ‘Select
an existing organization’ to define it as a Reporting Establishment if the reporting establishment is an existing TRU.
4. Select Tax Reporting Unit in the Classification field and click Search. Then click Select Organization for the TRU you want to
work with.
5. In the Reporting Establishment Description section, provide the required information:
6. Click Next to provide additional details, and then review and submit.
Action Reasons
Action reasons are useful primarily for analysis and reporting purposes. They provide information about when or why a specific action,
such as termination of a worker, can be taken. They can also be used to trigger a process based on the value of the action reason. For
example, a specific termination reason might trigger the payment of an indemnity. Action reasons are often used in report fields or
selection criteria.
Several action reasons are predefined in the system. Although action reasons are not workforce structures, the implementation team
may want to create additional ones to suit the business needs of the enterprise.
To view and manage action reasons:
1. Select Manage Actions in the implementation project task list.
2. On the Manage Actions page, you can search for existing actions and view associated action reasons. You can also create
new actions and action reasons.
3. To create a new action reason for an action, click Create in the Actions Reasons section and complete the required fields.
4. The new reason code will be available for selection when a user performs the specified action.

PERSONAL DATA SETUP
This section of the document describes the setup and validations that have been predefined for the UK 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 UK is predefined and should not be modified during
implementation. The predefined format is called ‘United Kingdom Postal Address Format’ and enables the following fields
» Country (Mandatory)
» Address 1 (Mandatory)
» Address 2
» Address 3
» City or Town (Mandatory)
» County
» Postal Code
Address Validation
The validation is performed on the Postcode, which conforms to the UK Postal code format and typical formats include:
1. AN NAA
2. ANN NAA
3. AAN NAA
4. AANN NAA
5. ANA NAA
6. AANA NAA
7. GIR 0AA (historic code)
In the postcode format, A is Alpha and N is Numeric.
In addition to the above validation, the following rules also apply:
1. The letters Q, V, and X cannot be used in the first position.
2. The letters I, J, and Z cannot be used in the second position.
3. The only letters allowed in the third position are A,B,C,D,E,F,G,H,J,K,S,T,U, and W.
4. The only letters allowed in the fourth position are A,B,E,H,M,N,P,R,V,W,X, and Y.
5. The second half of the postcode is always in the format: numeric, alpha, alpha. The letters
C, I, K, M, O, and V are not allowed.
Address Mapping
If you are uploading the data through HCM Data Loader (HDL) then map the address fields as follows:
UI Name Table Column name (PER_ADDRESSES_F)
Address Line 1 ADDRESS_LINE1

City or Town TOWN_OR_CITY
County REGION_1
Postcode POSTAL_CODE
Names
The format in which names must be entered for workers located in the UK is predefined and should not be modified during
implementation. The UK name format follows the standard format used in Oracle Fusion:
» Last Name
» Title
» First Name
» Middle Name
Legislative Information
UK-specific legislative information can be captured for each person. None of these fields is mandatory, and it is up to the enterprise to
decide which data needs to be entered.
The UK supports the following legislative information:
» Marital Status: Uses UK-specific values in the lookup

» Ethnicity: Uses UK-specific values in the lookup
» Highest Education Level
The UK-specific PER_PERSON_LEGISLATIVE_DATA_LEG_DDF includes these flexfield segments:
» NINO Verified: Used by the NVREP process flagging that the NINO is verified.
» Verified Date: Used by the NVREP process showing the date the NINO was verified.
» Response Status Returned: The status returned by the NVREP process.
» Verification Type: From the NVREP process.
» Correlation ID: From the NVREP process.
» Last Update Process Sequence: From the NVRP process.
» Partner First Forename: No longer used
» Partner Second Forenames: No longer used
» Partner Surname: No longer used
» Partner National Insurance Number: No longer used
» Sexual Orientation
» Gender Identity
» Unique Taxpayer Reference (UTR).
» Last Marital Status Change Date Prior to Hire
» Employee age verified
» Multiple Civil Service Assignments
» Civil Service Joining Date
» Teacher Reference Number
» Off-payroll worker subject to 2020 rules. Indicates if this person is a Deemed Employee as defined by HMRC.
Note: you cannot change the off-payroll worker flag if the person has been processed. You must terminate the existing person and
setup a new person to reflect the new status.

» National Identity: As required by the protected characteristics legislation.
» Candidate Age Band: As required by the protected characteristics legislation.
» Caring Responsibilities: As required by the protected characteristics legislation.
Note: Refer to the XLS document that accompanies this product paper for a complete list of predefined lookup and
flexfields for the UK.
National Identifiers
The following validation has been delivered for the UK National Insurance (NI) Number:
» If the NI number is not null then its length must be either 8 or 9 character AND
» The first 2 characters of the NI number must be alphabets (a-z or A-Z) AND
» The first 2 characters must be in the list of valid NI number prefixes as defined in the lookup HRX_GB_NI_VALID_PREFIX) AND
» Characters 3-8 must be numeric (0-9) AND
» If character 9 is present then it must be either A or B or C or D or Space.
This is as required by the protected characteristics legislation.
Employment Indermediaries
To support the reporting of employees who are employed through intermediaries, you can now capture additional data such as
employment agencies or other third parties.
This data capture consists of two new fields:
» Worker Engagement Details

» Worker Unique Taxpayer Reference
To create this:
1. Use the Manage Employment task to enter the Worker Engagement Details field in the Job Details section.
2. Select one of the following values for this field:

o Another party operated PAYE on the worker’s payments
o Limited company
o Limited liability partnership
o Non-UK engagement
o Partnership
o Self-employed contractor
3. Enter the value for the Worker Unique Taxpayer Reference field in the In the Manage Person page.
4. Click Edit for the United Kingdom Legislative Information -> More Details.
5. Enter a 10-digit value for the Unique Taxpayer Reference field that is issued to an individual by HMRC.
Disability
When employees access their disability record using their employee login, and the country is set to United Kingdom, they are presented
with a declaration form that helps them in completing the disability record.
Note: You can view this declaration only if you log in as an employee. .
ADDITIONAL INFORMATION FOR PAYROLL AND 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
will also be running Oracle Fusion HCM (UK) Payroll, additional information must be provided to support payroll processes. Setup tasks
for Oracle Fusion Payroll are outside the scope of this guide.

Note: To setup the United Kingdom territory information, see the section Managing Payroll Product Usage.
If the enterprise is not implementing Oracle Fusion Payroll but will be extracting data from the Oracle Fusion application, via the Payroll
Interface, to feed an external payroll system, additional payroll-related data must be provided to support the Payroll Interface.
For more information on payroll interface, see the books Administering Global Payroll Interface and Implementing Global Payroll
Interface on Oracle Help Center.
The sections that follow describe how to define payroll-related information to support both the Payroll Interface and full payroll
implementation for the UK localization extensions.
You can see the predefined configuration on the Configure Legislations for Human Resources:
Review all the sections to ensure the configuration meets your needs. The sections are summarised here:
» Tax year start date

» Default currency
» Payroll Relationship Rule
» Payroll Relationship Type Mapping
For each system person type it is possible to define the type of payroll relationship that is created. Note that if no payroll relationship
is created to a system person type it will not be possible to enter element entries for that system person type. The only exception is
the nonworker paid system person type for which by default element entries is enabled.

» Element Classifications
» Payment Types
» Component Groups
» Balance Dimensions
» Balance Types
» Balance Categories
» Defined Balances
» Balance Classifications
» References
» Calculation Cards
» Value Definition Groups
» Balance Groups
Payroll Processing after Termination

If Payroll is being used, or, if Payroll Interface will be used to feed an external payroll system, it is necessary to specify for which
assignment statuses payroll should be processed, for instance, when suspended or inactive. This is especially relevant after
termination.
To set up mapping between pay status and assignment status, perform the following steps:
1. Select the Manage Assignment Status task.
2. Define the mapping between Assignment Status and Pay status.
3. Shown here are some of the possible values.
Statututory Deductions Calculation Card

A Statutory Deductions calculation card captures values required for calculating and processing payroll deductions. To support the
Payroll Interface, you must create a Statutory Deductions calculation card for each person for whom payroll deductions will be
processed.
For more information, see the Oracle Fusion HRMS (United Kingdom): Payroll Implementation and Functional Considerations (Doc ID
1921464.1) on MOS.
BANKING SETUP
An HR customer may want to add payee banking information even if payroll is not processed by Oracle Fusion Payroll for UK. 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 UK. 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 role that has implementation privileges, such as APPL_IMP_CONSULTANT.
2. Select Manage Banks -> Create.
3. On the Create Bank page, provide the required information.
Bank Branches
To define branches for the banks you created:
1. Select Manage Bank Branches -> Create.
2. On the Create Bank Branch page, provide the required information.
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 UK.
To define bank accounts:
1. Select Manage Bank Accounts > Create.
2. On the Create Bank Branch page, provide the required information.
Note: To use this bank account for processing payments related to payroll, select the Payroll option in the Account Use field. If you
want to use a building society account, you must enter it when first saving the bank account record. If a bank account record is saved
without a Building Society Roll Number, the account is considered to be a normal bank account, and not a building society account.

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 UK. Implementation teams will need to create the ones applicable to the
enterprise.
To define organization payment methods:
1. Select Manage Organization Payment Methods -> Create.
2. Select the legislative data group associated with this payment method.
3. On the Create Organization Payment Method page, enter the required information.
Note: The UK supports the following Payment Types: BACS, Cheque, and Cash Payment.
If you select BACS, the page is refreshed to show fields related to electronic file transfer (EFT).
You can configure BACS for single-file, single-day format or multi-file, single-day format.
To set up single-file, single-day format
1. In the Electronic Funds Transfer File Information section, leave Bureau Name and Bureau Reference blank.
2. Enter the appropriate values for Transaction Limit and BACS File Limit.
3. In the Payment Sources section, click Create.
4. On the Create Payment Source page, enter a Name and select a Bank Account Name.
5. Enter the BACS User Number and Contra Narrative.
To set up multi-file single-day format
1. In the Electronic Funds Transfer File Information section, enter the Bureau Name, Bureau Reference Transaction Limit, and
BACS File Limit.
2. In the Payment Sources section, click Create.
3. On the Create Payment Source page, enter a Name and select a Bank Account Name.
4. Enter the BACS User Number and Contra Narrative.
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 Total Pay, is predefined for the UK, and no additional setup is required during the implement phase.
To view the Total Pay balance:
1. Select Manage Balance Definitions in the Payroll Calculations or Setup and Maintenance work areas.
2. Enter Total Pay in the Name field and select a UK LDG, then click Search:
3. Click the Total Pay balance in the Search Results to view the balance information.
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.
Note: The Core Relationship Payments has been associated with this balance.

CONSOLIDATION GROUPS
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 are used within the organization to enable grouping of different payrolls for reporting purposes. No consolidation
groups are predefined for the UK. If you will be creating payroll definitions for the implementation, you must define at least one
consolidation group first since it is mandatory information for payroll definitions.
To set up consolidation groups:
1. Sign in to the application with a role that has implementation privileges, such as APPL_IMP_CONSULTANT.
2. Select Manage Consolidation Groups -> Create.
3. Enter a name and select a legislative data group. Description is optional, but useful to provide.
4. Click Save.

PAYROLL DEFINITIONS
Payroll definitions contain calendar and offset information that determine when payments are calculated and costed. 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 UK.
To set up payroll definitions:
1. Select Manage Payroll Definitions -> Create.
2. On the Create Payroll page, enter the required information:
3. 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.
4. Click Next, and provide the required information on the Payroll Offsets page.
5. Save your work.

ELEMENTS AND COMPENSATION
Even if elements are normally 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.
A set of element templates is predefined for the UK. The following UK templates are used to create base pay and compensation
earnings:
» Regular Earnings
» Irregular Earnings
Here are the steps to create a regular earnings element for basic salary:
1. Select Manage Elements > Create.
2. On the Create Element window, select a legislative data group and a primary classification, then click Continue.
3. Complete the fields at the top of the Create Element page, and then answer the questions.
4. Click Next, and complete the rest of the questionnaire.
5. Verify the information and click Submit to create the new element.
6. On the Element Summary page, provide additional information as needed, such as input values, processing rules, and
eligibility.
7. Use the Element Overview panel to navigate through the setup pages.
Note: Element eligibility must be defined so the element can be linked to an element entry (and hence to gross
compensation).
8. In Element Overview, select Actions > Create Element Eligibility.
9. On the Element Eligibility page, enter a name in the Element Eligibility Name field and click Submit.
Note: By entering only a name and no eligibility criteria, the element is eligible for all employees.
10. Click an Input Value in the left panel to provide additional information as needed:
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 can also be used to create element entries for a person.

CONNECT WITH US
Call +1.800.ORACLE1 or visit oracle.com.
Outside North America, find your local office at oracle.com/contact.
blogs.oracle.com facebook.com/oracle twitter.com/oracle
Copyright © 2021, 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 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, electronic or mechanical, for any purpose, without
our prior written permission.
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. 0120
Product Paper Title: Oracle HCM (UK) HR Implementation and Functional Considerations
September, 2021
Author: Henry Winsor

Release 13 21.D UK HR Setup

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Release 13 21.D UK HR Setup

Uploaded by

Copyright:

Available Formats

Oracle HCM Cloud (UK)

Month 10, 2021 | Version 21D

1 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

Organizational Structures and Additional Data Capture ......................................... 5

Personal Data setup .................................................................................................. 20

Additional Information for payroll and payroll Interface ....................................... 22

2 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

Banking Setup ........................................................................................................... 24

Organization Payment Methods .............................................................................. 26

Consolidation Groups ................................................................................................27

Element Entries ......................................................................................................... 30

3 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

This document is intended to support the implementation team in understanding:

Other Information Sources

4 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

Create an Implementation Project

Manage Payroll Product Usage

2. Select the United Kingdom Legislation

5 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

Follow these steps to verify predefined geographies:

3. Click on the checkmark to open the associated setup data:

These are the items of geography that need to be validated.

You can specify the real-time address cleansing level:

Load Geography Data

6 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

1. Select Manage Legal Jurisdictions in the implementation project task list.

NAME COLUMN VALUES COMMENTS

Name Name United Kingdom

Territory TERRITORY United Kingdom

Legislative LEGISLATIVE_CAT_CODE HRX_GB_HMRC The value HMRC is

Identifying IDENTIFYING No Indicates that

7 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

Legal REGISTRATION_CODE_ETB HRX_GB_PAYE_REF Indicates that the TRU

To define legal addresses:

2. On the Manage Legal Addresses page, click Create.

To define legal authorities:

1. Select Manage Legal Authorities.

2. On the Manage Legal Authorities page, click Create.

3. On the Create Legal Authority page:

5. Add one or more addresses.

8 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

7. Click Save and Close.

Legislative Data Groups

Each Legislative Data group has a context of a country.

Payroll configuration setup can be done at the following levels:

Legal Employers and Payroll Statutory Units

9 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

Legal Reporting Units and Tax Reporting Units

Organization Structure Models

These are examples of supported configurations:

» Enterprise 1: 1 PSU with 1 legal employer and 1 TRU

10 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

3. Provide the required information, noting the following:

4. Click Save and Close.

Create Legal Entity Registrations

2. Under Legal Entity, select Select and Add.

If required, you can create additional registrations:

4. Click Create to add a registration.

5. Enter the required information, noting the following:

11 Product Paper| Oracle HCM (UK) HR Implementation and Functional Considerations |

To provide HCM information:

4. Complete the fields on this tab and click Submit.

6. Complete the fields on this tab and click Submit.