Oracle - Fusion - HRMS - For - US - Implementation - and - Use - White - Paper Note 1676530.1 PDF

Oracle Fusion HRMS (US): Implementation and Use
An Oracle White Paper

May 2014
Oracle Fusion HRMS (US):

Implementation and Use (HR and Payroll)
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.
Table of Contents
Overview ............................................................................................... 6
Other Information Sources ............................................................... 6
Document Updates ........................................................................... 6
Change Record ................................................................................. 6
Vertex .................................................................................................... 6
License .............................................................................................. 7
Installing the Monthly File Updates .................................................. 7
Running the Process ........................................................................ 7
Vertex Tax Calculation Reference Material ...................................... 7
Troubleshooting ................................................................................ 7
Support and Reference..................................................................... 8
Organization Structures ........................................................................ 8
Enterprises ........................................................................................ 9
Implementation Projects ................................................................... 9
Payroll Product License Parameter ................................................ 11
Geographies ................................................................................... 13
Enterprise Structures ...................................................................... 17
Legal Addresses ............................................................................. 18
Legislative Data Groups ................................................................. 19
Jurisdictions .................................................................................... 19
Legal Entities .................................................................................. 21
Legal Entity HCM Information for Legal Employers and PSUs ..... 24
Legal Entity Deduction Records ..................................................... 28
Legal Reporting Units ..................................................................... 29
Legal Reporting Unit Contact Details ............................................. 31
Legal Reporting Unit Registrations ................................................. 33
Legal Reporting Unit HCM Information .......................................... 34
Legal Reporting Unit Deduction Records ....................................... 37
Business Units ................................................................................ 40
Workforce Structures .......................................................................... 40

Locations ......................................................................................... 40
Departments ................................................................................... 44
Grades ............................................................................................ 44
Jobs ................................................................................................. 46
Actions Reasons ............................................................................. 47
Managing Workforce Structures ..................................................... 49
Banking Setup ..................................................................................... 51
Banks .............................................................................................. 51
Bank Branches................................................................................ 52
Bank Accounts ................................................................................ 53
Organization Payment Methods ..................................................... 54
Payroll Configuration .......................................................................... 57
Consolidation Groups ..................................................................... 57
Payroll Definitions ........................................................................... 58
Elements and Element Templates...................................................... 60
Element Eligibility and Costing ....................................................... 66
Salary Basis .................................................................................... 67
Creating a Gross-up Earnings Element ......................................... 69
Creating a Gross-up Imputed Element ........................................... 73
Overtime.......................................................................................... 76
Wage Basis Rules............................................................................... 77
Viewing Wage Basis Rules ............................................................. 77
Creating Wage Basis Rules ............................................................ 78
Employee Management ...................................................................... 82
Hiring a Worker ............................................................................... 83
Verifying Employee New Hire Status in Work Relationship Details85
Maintaining Person and Employment Information ......................... 86
Managing the Employee Withholding Certificate ........................... 89
Terminating a Worker ..................................................................... 90
Assigning Salary Information to an Employee ............................... 91

Person Payment Information .......................................................... 92
Assigning a Payroll to the Employee .............................................. 92
Assigning Payment Methods to the Employee .............................. 93
Tax Troubleshooting ........................................................................... 94
New Hire Reporting............................................................................. 96
Prerequisites ................................................................................... 96
Set Up Steps ................................................................................... 96
Running the Report ......................................................................... 96
Viewing the Output ......................................................................... 97
VETS-100 and 100A Employment Report ......................................... 98
Prerequisites ................................................................................... 98
Set Up Steps ................................................................................... 98
Running the Report ......................................................................... 98
Viewing the Output ....................................................................... 100
EEO-1 Report.................................................................................... 102
Prerequisites ................................................................................. 102
Set Up Steps ................................................................................. 102
Running the Report ....................................................................... 102
Viewing the Output ....................................................................... 103
Overview
This document is intended to document how to:
Define the organizational structures required for HR and Payroll country-specific processes
Define the data required for paying a US worker
Define the data required for hiring and maintaining a US worker
Define the data required for HR and Payroll country-specific reporting
Other Information Sources

Oracle Fusion Workforce Deployment Implementation Guide (Release 7):
http://docs.oracle.com/cd/E38454_01/fusionapps.1117/e20379.pdf
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 (Release 7):
http://docs.oracle.com/cd/E38454_01/doc.1117/e35673.pdf
Oracle Fusion Global Payroll Interface Guide (Release 7):
http://docs.oracle.com/cd/E38454_01/doc.1117/e35674.pdf
Document Updates
This document is based on the most current application release as of the documents publication date. Content
is updated as needed to reflect major changes to existing features or when significant new features are added to
the US 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.
Change Record
Date Description of Change
01-May-2014 Created document.
22-May-2014 Added reference to Vertex troubleshooting document on MOS.
Vertex
Vertex installation is a mandatory step for US Payroll and US Payroll Interface clients. Fusion payroll processing
will not work without Vertex data.
Vertex provides:
Address Validation: These updates come from Vertex in the monthly ORAMAST.txt (Geography file).
Payroll Tax Calculation Rules/Tax Data: These updates come from Vertex in the monthly QFPT.dat (Tax
file).
6
Update notifications: When the updates are released by Vertex, those registered with Vertex at the customer
site receive an email notification. For SaaS customers, the Oracle Product Services team receives the
notification and logs a bug to install the files.
License
Saas customers do not need to acquire a Vertex license. This is included as part of the Saas service offering.
On-Premise and On-Demand customers must acquire a Vertex license and pay the associated fees.
Installing the Monthly File Updates

Both files are available each month from Vertex. For SaaS customers, Oracle Product Services installs the files
for them. The On-Demand team installs the files for the customers when they are requested to do so by their
customers. On-Premise customers install the file themselves.
Running the Process

Once the files are installed, all customers (including SaaS) are required to run the processes to update their
geography data, tax data, or both.
Vertex Tax Calculation Reference Material

Non-SaaS customers have on-line access to the latest Vertex Tax documentation using My Vertex.
SaaS users can access their Cloud Notifications website and download the Vertex users guide from this site.
When you receive the notification that the Vertex updates are being applied to your environment, there is a
Here link at the bottom of the page. (You may want to bookmark this page.) To see the Vertex documents
available for download, click this link and go to the Documentation tab. Oracle keeps the current months update
and the new update on this page. There is one document for the US and one for Canada.
Note:
Although you may get a notification before the 18th of the month, the Vertex guides are not available until the
18th.
In order to access this download, your Oracle Cloud Administrator must have added you to the Cloud Notification
site with at least Document Viewer privileges. You may download documents if you have Account Administrator
or Document Viewer roles. If your access is Account Viewer, you will not have access to the files. If you are not
sure who the account administrator is for your company, please contact Oracle Support.
Note:
The Vertex user guides are proprietary to Vertex, and as such, Oracle can only distribute on a need-to-know
basis. Share these documents only with people in your company that have a need to know, such as the
Payroll Department.
Troubleshooting
Problem Solution
Invalid Address Data Is the combination you are trying to enter
valid? Confirm it on USPS.com. If valid,
contact Oracle Support.
In any case where entering an address is
required, it is good practice to enter the ZIP
Code first. In this way, the application is able
to automatically populate other fields based on
the Vertex data.
7
Customer does not have a US Payroll license Switch the license to HR-only, and run the
and does not want address validation Load Geographies for US task again. If they
have never run the process, they do not need
to run it. Setting the license to HR-only should
be sufficient.
Payroll Tax Calculation Refer to Tax Troubleshooting, below.
Error during Vertex file load (does not apply to If the database contains corrupt information,
SaaS customers) you will receive an error.
Do not copy over an existing database.
Note:
When installing a new data file, remove the
existing ISAM database and install the new
database in a empty directory.
Do not load an older version of the file.
Support and Reference

Contact Oracle Support with any issues not resolved using the troubleshooting tips.
For instructions on how to maintain your Vertex ISAM database after installation, refer to Updating the Vertex
Data File for US Tax Information: Worked Examples in the Help Portal.
For additional information, refer to Oracle Fusion HCM and Payroll (US/CA) Vertex Frequently Asked Questions
(FAQ) (Doc ID 1613196.1) on the Oracle Support website.
Organization Structures
Before an employer can hire a US worker or run any country-specific processes, 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 these structures and how to define them:
Enterprises
Implementation Projects
Payroll Product License
Geographies
Enterprise Structures
Legal Addresses
Legislative Data Groups
Jurisdictions
Legal Entities
Legal Entity HCM Information for Legal Employers and PSUs
Legal Entity Deduction Records
Legal Reporting Units
Legal Reporting Unit Contact Details
Legal Reporting Unit Registrations
Legal Reporting Unit HCM Information
8
Legal Reporting Unit Deduction Records

Business Units
These structures, which typically contain country-specific information, must be defined before you can create
application users.
Enterprises
The Enterprise classification represents the top structure in the organization that supports partitioning
requirements for Oracle Fusion applications. Each employee you define exists within the context of an
enterprise. If a person is associated with two enterprises, that person must have two person records.
Since there is no concept of legislation at the enterprise level, no US-specific attributes are stored at this level.
All US-specific attributes are stored in subordinate structures, such as the legal entity.
This document does not describe enterprise setup, as this structure is defined at a higher level than HR and is
used across Oracle Fusion product lines.
Implementation Projects
Setup tasks for organization structures must be defined in an implementation project. 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.
2. Select Setup and Maintenance from the Navigator.
9
3. On the Implementation Projects tab, click Create.
4. On the Create Implementation Project page, provide a name and start date for your project.
5. Click Next.
6. Select Workforce Deployment.
7. For Payroll implementations, further select Payroll and then US Payroll.
This parent project contains all the tasks needed to set up HCM organizational structures.
10
8. Click Save and Open Project.
Payroll Product License Parameter

Valid values for Payroll License parameter are:
HR_ONLY
This is the default.
PAYROLL
PAYROLL_INTERFACE
Use the new Manage Payroll Product Usage task to select the correct payroll product for each of your legislations
to ensure that payroll-related features work correctly in your implementation. This feature replaces the Payroll
License action parameter, which was maintained on the Manage Payroll Process Configuration page.
NOTE:
In Release 8 and onwards, the license is set by country. After any upgrade, the Payroll License parameter is
reset to null, and the Implementation Team must update it before any transactional actions can be
performed, such as running payroll, new hires, setting up elements, and so on.
If this parameter is set to one of the payroll values, it automatically creates an employees tax deduction card
when a payroll relationship is created.
Refer to the following document on Oracle Support for additional information:
Fusion Payroll: Types of License In Fusion Payroll (Doc ID 1611941.1)
To check and set the product license:
1. Search for and start the Manage Payroll Product Usage task.
11
12
2. Check the selected Payroll Product for the appropriate legislation to ensure the proper setting.
3. Make any changes, if needed, and click Save.
4. Click Done.
Geographies
The US geocodes are used for:
Address validation
Regional taxation
Geography-based business processes
This geography information is provided by Vertex or another third-party source.
Loading Geographies
The Implementation Team must load this data into the geographies table.
This task is required for both HR-only (if using address validation) and Payroll implementations.
To load US geographies:
13
1. Select Load Geographies for US in the implementation project checklist.
2. Enter the necessary details in the Parameters section.
3. Click Submit.
Verifying Geographies
To verify predefined geographies:
1. Select Manage Geographies in the implementation project checklist.
14
2. On the Manage Geographies page, select US and click Search to view the predefined US geography setup
and content.
3. Select the green checkmark for each type of geography data you want to verify.
Address Cleansing Defined
Structure Defined
15
Hierarchy Defined
Validation Defined
16
Define Address Style Format Mapping for United States

HR-only and Payroll implementations must update the Geography Mapping fields for the following formats:
United States Postal Address Format
United States Tax Address Format
No Style is not used for US implementations.
HR-only implementations with no address validation must select the United States Postal Address Format. All
other implementations must use the United States Tax Address Format.
To set your geography validation:
1. Select Workforce Deployment > Define Common Applications Configuration for Human Capital Management
> Define Geographies for Human Capital Management > Manage Geographies.
2. In the Geography Mapping and Validation section, select or deselect the Enable List of Values checkbox as
appropriate for each geography type.
Note:
Tax and geography validations are not used by Oracle Fusion HCM applications, so do not use the Tax
Validation and Geography Validation checkboxes. Likewise, you can ignore the fields in the Geography
Validation Control section.
3. Click Save and Close.
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:
17
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 US. 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.
2. On the Manage Legal Addresses page, click Create.
18
3. Define your addresses as needed.

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.
To define an LDG:
1. Select Manage Legislative Data Groups in the implementation project task list.
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.
Jurisdictions
All legal entities must be registered against a jurisdiction that is governed by a legal authority. A jurisdiction is a
combination of the legislative category (labor law, transaction tax law, income tax laws, and so on) and the
19
physical territory (such as group of countries, country, state, county, and parish) to which legal rules are
grounded. 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. The
identifying jurisdiction is usually the first jurisdiction that the legal entity must register with, in order to be
recognized in its territory. The registration to the identifying jurisdiction of the legal entity territory is called the
identifying registration. The jurisdiction can also capture the registration code or the name of the registration
number. The registration code can then be used as the prompt for the registration number given the context of
the jurisdiction. The jurisdiction has a start date and end date to show when the jurisdiction is effective and when
you can register against the jurisdiction.
There are three sub-regions on the Create Legal Jurisdiction page:
General Information: Displays the legislative category and allows the user to select the territory, enter the
name, the start and end date (if any end date), and to specify whether the jurisdiction is identifying or not. The
Additional Customer descriptive flexfield allows employers to define their own country or legislative category
context additional attributes.
Registration Code Assignment: For a given jurisdiction, allows the user to select a specific registration code to
display when creating legal entities and legal reporting units (LRUs).
Legal Functions: Allows the user to relate specific legal functions for a given jurisdiction, such as payment,
reporting, and so on. This is optional.
The US localization provides the following predefined legal jurisdictions, which are a combination of the territory
and legislative category:
Jurisdiction Legislative Category Territory Description
United States FEDERAL_TAX United States Used for federal income tax,
Federal Tax federal unemployment tax, Social
Security, and Medicare.
<Territory> Income Tax State Used for all states with an income
Income Tax tax. One legal jurisdiction for
each state with an income tax is
created.
<Territory> Unemployment State Used for all states with an
Unemployment Insurance Tax unemployment insurance tax.
Insurance One legal jurisdiction for each
state with an unemployment tax is
created.
<Territory> Disability Insurance State Used for all states with a disability
Disability Tax insurance tax. One legal
20
Insurance jurisdiction for each state with a

disability tax is created.
No local tax jurisdictions are predefined by the US localization. The user must first create the local jurisdiction
and then create the local tax registration, using the local tax legislative category and local jurisdiction.
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 (through balance sheets, income statements, specified reports, and so on) to company regulators,
taxation authorities, and owners according to rules specified in the relevant legislation.
Legal Employers and Payroll Statutory Units

Oracle Fusion HRMS recognizes different types of legal entities:
A legal employer is a legal entity that employs workers.
A payroll statutory unit (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.
When defining a legal entity, you must consider the context in which it is to be used:
If it is to be used in an HCM context, designate it as a legal employer. In an HCM implementation, it is
mandatory to define legal employers.
If it is to be 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 need to be grouped together for tax reporting purposes, you can associate them
all with a single PSU. If legal employers do not report together, they must be segregated by PSU.
No legal entities are predefined for the US. You must create all legal entities that apply to the enterprise you are
setting up.
Legal Reporting Units and Tax Reporting Units

A LRU is the lowest level component of a legal structure that requires registrations. It is used to group workers
for the purpose of tax reporting or to represent a part of your enterprise with a specific statutory or tax reporting
obligation.
If a LRU is to be used for tax reporting purposes, then it must be configured as a tax reporting unit (TRU). When
you create an LRU that belongs to a legal employer (that is not also a PSU), you must select a parent PSU. In
this way, TRUs are indirectly associated with a legal employer by association with a PSU.
TRUs are especially relevant for the US because the TRU captures the employers:
US federal employer identification number (FEIN)
State employer account number
Registration details
Statutory registered name
Organization Structure Models Supported by the US Localization

The sections that follow describe how to define a set of organizational units that comprise the organization
structure required to manage HR processes for the US. Each enterprise can combine these organizational units
21
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 US
localization.
The figure below illustrates the four configurations supported by Oracle Fusion HRMS (US):
Enterprise 1: One PSU with one legal employer and one TRU
Enterprise 2: One PSU with one legal employer and multiple TRUs
Enterprise 3: One PSU with multiple legal employers and multiple TRUs, where each legal employer is
associated with a single TRU
Enterprise 4: One PSU with multiple legal employers, where different employers are associated with different
TRUs
Note:
An enterprise can have multiple PSUs belonging to the same or different LDGs. It is possible for a legal entity to
be both a PSU and a legal employer.
Creating Legal Entities

To define legal entities:
1. Select Manage Legal Entities in the implementation project task list.
22
2. Click Create to display the Create Legal Entity page.
3. Provide the required information, noting the following:

Legal Entity to PSU: If no LDG exists, it automatically creates a LDG and associates it to the PSU. If a
LDG already exists for that country, you must manually associate it. This started in Release 5.
If a legal entity is not designated as a PSU, you can select an existing PSU to which it belongs.
You must have previously defined the legal address for the legal entity.
Viewing the LDG

To view the LDG for a PSU:
1. Select the implementation project.
2. Select Manage Legal Entity HCM Information.
23
3. Search for the PSU or legal entity.

4. Select the PSU tab. By default, general information for the PSU is displayed, including the legislative data
group.
Legal Entity HCM Information for Legal Employers and PSUs

Additional information about legal employers and PSUs are required for:
EEO
VETS
New Hire Reporting
Payroll processing
24
Note:
Electronic year-end and quarterly filings processes are not yet available in Oracle Fusion. These filings are
currently handled by the ADP third-party vendor using the ADP Tax Filing interface. See Oracle Fusion
HRMS (US): Payroll Third-Party Tax Filing Interface white paper on MOS for necessary setups for the Tax
Filing Interface.
To enter the additional HCM information:
1. Select Manage Legal Entity HCM Information in the implementation project task list.
2. In the Select Scope window, choose Select and Add in the Legal Entity LOV.
3. Click Apply and Go to Task.

4. Search for and select the legal entity you just created, and then click Save and Close.
5. If the entity is a legal employer, complete the fields on the Legal Employer tab.
25
6. Click the Federal link.
7. In the EEO Reporting Rules section, specify the following values:

Field Name Notes
Affiliated with Enterprise of Select Yes to indicate whether your entire company
100 Employees or More employs more than 100 or more employees.
Select No if your entire company employs fewer than 100
employees.
Company Number Enter the unique company identifier assigned by the
EEOC.
More than 100 employees Select Yes to indicate whether your company employs
in pay period more than 100 employees in a pay period.
Select No if your company employs fewer than 100
employees.
Government Contractor Select Yes or No to indicate whether or not the
employer is a government contractor.
26
8. In the New Hire Reporting Rules section, associate a default TRU to a legal employer by selecting one in the
TRU for the New Hire Report field.
The HR reports use the employer FEIN, registered name, contact details, and other registration details of the
TRU associated to the legal employer.
9. In the VETS Reporting Rules section, specify the following values:
Field Name Notes
Reporting Name Enter the hiring location name.
Parent Company Enter the parent company headquarters.
Type of Reporting Select Prime Contract, Subcontractor, or Both.
Organization
Company Number Enter the unique company identifier.
10. In the EEO and VETS Reporting Information section, specify the following values:
Field Name Notes
Employment Category Each of the employees to be included in report must have
an employment category. Select the employment
categories to be included in the report.
Establishment Employer Select Multiple if you are a multi-establishment employer.
Type Select Single if you are a single establishment employer.
11. If the legal entity is also a PSU, select the Payroll Statutory Unit tab.
12. Click the Federal link, and enter any additional information to support electronic year-end filings for the US.
Data entered here applies to all LRUs attached to the PSU.
27
13. Click the appropriate link to enter additional information to support electronic year-end and quarterly filings for
those regions.
Data entered here applies to all LRUs attached to the PSU.
Legal Entity Deduction Records

Additional information about federal and regional tax rules is required for Oracle HCM processes. Data entered
here applies to all LRUs attached to the PSU.
Note:
This task is named Manage Legal Entity Calculation Cards in Release 8 and beyond.
To create the calculation card and enter federal tax rules:
1. Select the Manage Legal Entity Deduction Records task.
2. On the Payroll Statutory Unit page, click Create:
3. On the Create Calculation Card page, enter the required information and click Continue.
28
4. To enter federal income tax (FIT) calculation rules, select the appropriate row under Calculation
Components.
5. Enter the appropriate data in the Calculation Component Details section.
6. Repeat to add calculation rules for Social Security and FUTA.
7. Click Save.
Legal Reporting Units

For the US, all LRUs must be designated as TRUs. Set the following at the LRU level:
Regional tax rules
State unemployment insurance (SUI) rates
State disability insurance (SDI) rates
The first time you create a legal entity as a PSU, the application automatically creates an associated LRU, which
you must then identify as a TRU. When you assign an existing PSU to a legal employer, the default LRU inherits
the legal entitys name.
To create a LRU:
1. Select Define Legal Reporting Units for Human Capital Management in the task list.
2. Select Manage Legal Reporting Unit in the implementation project task list.
29
3. On the Scope Selection window, select Create New and click on Apply and Go to Task.
Note:
An LRU with the same name as the previously created legal entity is created by default.
This LRU is automatically designated as the main LRU for the legal entity.
4. To create a second LRU for this legal entity, enter the required information on the Create Legal Reporting
Unit page.
30
Legal Reporting Unit Contact Details

HCM employer contact details are captured at the LRU level and are required for:
EEO
VETS
New Hire Reporting
The HR Reporting processes pick contact details for reporting from the TRU associated to a legal employer.
To capture LRU contact details:
1. From the implementation project, expand Workforce Deployment > Define Common Applications
Configuration for Human Capital Management > Define Enterprise Structures for Human Capital
Management > Define Legal Entities for Human Capital Management > Define Legal Reporting Units for
Human Capital Management > Manage Legal Reporting Unit.
2. Select the legal entity name under Selected Scope.
3. On the Select Scope page, select the Search Legal Reporting Units option and click Apply and Go to Task.
31
4. Highlight the LRU from the list, and click Contact.
5. On the Manage Contacts page, click Create Contact.
6. Enter the following information:

Field Name Description
Role Select the employee role.
First Name First name of the employer contact.
Last Name Last name of the employer contact.
Job Title Code Job title code of the employer contact.
From Date Date the employee became the contact.
7. Click OK.
32
8. Define the contact points:

a. In the Contact Information region, select the Contact Points tab.
b. Click Create.
c. Specify the following fields:
Contact Point Type Select Phone.
Area Code Specify the contact persons area code.
Phone Specify the contact persons phone number.
Extension Specify the contact persons phone extension.
From Date Specify the date from which this phone number is valid.
d. Click OK.
e. Click Create.
f. Specify the following fields:
Contact Point Type Select E-mail.
Purpose Select Work.
E-Mail Format Select the contact persons email format.
E-Mail Specify the contact persons email address.
From Date Specify the date from which this e-mail address is valid.
g. Click OK.
9. Define the contact roles:
a. Select the Contact Roles tab.
b. Click Add Row.
c. Click the Legal Role column and select a role.
Note:
HR report processes use the contact details for a person with HR representative role. Payroll report
processes use the Payroll Tax representative or Payroll representative roles.
Legal Reporting Unit Registrations

LRUs are connected to legal authorities through LRU registrations. When you create a legal entity, a registration
is automatically created for the selected identifying jurisdiction. You must create a registration for the United
Stated Federal Tax jurisdiction to enter the Employer FEIN. If the LRU interacts with other legal authorities, you
must create additional registrations as appropriate.
Note:
Employer FEIN, registered name, and state EIN details are captured using the Manage Legal Reporting Unit
Registrations task.
If the United States Federal Tax registration is not present, some payroll processes will not function properly
(such as Archive Periodic Payroll Results).
Used for: EEO, VETS, New hire, and Payroll reporting.
33
To define a legal entity registration:

1. Select the parent legal entity and then the LRU, as described in previous tasks.
2. Select Manage Legal Reporting Unit Registrations in the task list.
The Manage Legal Reporting Unit Registrations page displays a list of registrations for this legal entity.
3. Verify there is a record for United States Federal Tax.

4. If no United States Federal Tax record exists, click Create to add a registration.
5. Enter the required information.

When you select a jurisdiction, the Territory field is populated automatically.
The Issuing Legal Authority field displays a list of all legal authorities associated with the selected jurisdiction.
See previous section on Jurisdictions for further information. The Registered Address field displays a list of
all predefined legal addresses.
Legal Reporting Unit HCM Information

Additional information about LRUs is required for Oracle HCM processes. Fields are available to support
electronic year-end and quarterly filings. Entry in these fields for the LRU overrides any values you may have
entered for the PSU.
Note:
Electronic year end and quarterly filings are not currently supported in Oracle Fusion. These filings must be
34
performed through the US Third-Party Tax Filing interfaces. Refer to the Oracle Fusion HRMS (US): Payroll
Third-Party Tax Filing Interface white paper on MOS for necessary setups for the Tax Filing Interfaces.
Note: Used for: EEO, VETS, New hire, Payroll, and Payroll Third-Party Tax Filing Interface.
To specify the required HCM information for TRUs:
1. Select the parent legal entity and then the LRU, as described in previous tasks.
2. Start the Manage Legal Reporting Unit HCM Information task from the implementation project task list.
3. On the Manage Legal Reporting Unit HCM Information page, select the Tax Reporting Unit check box. This
identifies the LRU as TRU.
4. Click Next.
5. Select the Tax Reporting Unit tab.
Do not enter any data in the Tax Reporting Unit Type or Associated Legal Employer areas.
35
6. Click the Federal link.

Use this page to specify information required for year-end and quarterly filings, as well as various reports and
processes for the US.
Entry in these fields overrides any values entered for the PSU.
7. In the Third Party Interfaces section, enter the following value:

Field Name Notes
Client Identifier Used by the Third-Party Tax filing interface. Refer to the
Oracle Fusion HRMS (US): Payroll Third-Party Tax Filing
Interface white paper on MOS for necessary setups for the
Tax Filing Interfaces.
8. In the EEO and VETS Reporting Rules section, enter the following values:
36
Field Name Notes

Employment Category Each of the employees to be included in report must have
an employment category. Select the employment
categories to be included in the report.
Establishment Employer Select Multiple if you are a multi-establishment employer.
Type Select Single if you are a single establishment employer.
Headquarters Select your headquarters location from the LOV.
Establishment
9. In the EEO Reporting Information section, enter the following values:
Field Name Notes
Affiliated with Enterprise of Select Yes to indicate that your entire company employs
100 Employees or More 100 or more employees.
Select No if your entire company employs fewer than 100
employees.
Company Number Enter the unique company identifier assigned by the
EEOC.
Company Employs More Select Yes to indicate that your company employs more
than 100 Employees than 100 employees.
Select No if your company employs fewer than 100
employees.
Government Contractor Select Yes or No to indicate whether or not you are a
government contractor.
10. In the VETS Reporting Rules section, enter the following values:
Field Name Notes
Parent Company Specify your parent company headquarters.
Type of Reporting Select Prime Contract, Subcontractor, or Both.
Organization
Company Number Enter your unique company identifier.
11. Click Submit.
12. Click the appropriate regional link to enter additional information to support year-end and quarterly filings for
the US.
Entry in these fields override any values entered for the PSU.
Note:
The Federal W-2 Reporting Rules Overrides and State Quarterly Wage Listing Rules Overrides are for future
use.
Legal Reporting Unit Deduction Records

To properly calculate tax withholding, the Oracle Fusion HCM payroll processes require additional information
about federal and regional tax rules, such as self adjustment methods and SUI Employer rates. This data is
entered for the LRU and overrides any data entered at the PSU level.
Refer to the Legal Entity Deduction Records section for steps to create the card and enter the federal tax rules.
37
To enter a SUI rate:

1. Search for and start the Manage Legal Reporting Unit Calculation Cards task.
2. Enter the Effective As-of Date.
3. Select Regional.
4. Under the Actions menu, select Create.
5. Select the appropriate state, and click OK.
38
6. Select State Unemployment in the Calculation Components table.

7. Select the Enterable Calculation Values on Calculation Cards tab.
8. Click Add.
9. Select State Unemployment Employer Experience Rate from the Name menu.
10. Enter the SUI rate for this LRU in the Rate field.
39
When a SUI rate is entered for a selected state, the SDI and SIT component details for that state must also
be provided.
11. In the Calculation Components table, select State Disability.
12. In the Calculation Component Details section, click Add.
13. Select State Disability Organization Information from the LOV, and click OK.
Note:
The Self Adjust method can be specified here.
14. Click Save.
15. Repeat steps 11 through 14 for State Income tax.
Business Units
Oracle Fusion HRMS (US) uses the business unit classification to group sets of data. When you associate a
business unit with a default set, the default set is inherited by every entity connected to the business unit.
No US-specific data is required or captured at this level. However, a worker must be assigned a business unit
during the hire process, so you must create business units for the enterprise.
Workforce Structures
Workforce structure setup should be performed once you have completed organization structure setup.
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 US. The Implementation Team is responsible for defining all the
workforce structures that apply to the enterprise for which the setup is being done. Some workforce structures
may not apply to every enterprise.
Locations
Locations identify:
Where business is conducted, including the physical location of a workforce structure
Workers physical work locations
Other areas of interest to the business
To create or manage locations:
1. Select Manage Locations in the implementation project task list.
40
2. Click Create.
3. Under Basic Details, define the effective start date.
When editing the location record, use the Correct option to make the changes effective to the start of the
existing record. Otherwise use the update option.
4. Define the other required fields in the Basic Details and Location Information sections.
5. Define the required fields in the Main Address section.
41
6. In the United States Multiple Worksite Reporting Information section, define the following information:
Field Name Notes
Trade Name Name of the client establishment at this location. If this location is to
be included in MWR reporting, this field is required.
Worksite Meaningful, unique description of the client establishment, such as
Description store number or plant name. If this location is to be included in MWR
reporting, this field is required.
Unit Number Five-digit number used in conjunction with the SUI account number
to uniquely identify a location at its address. This field is
informational only.
Comment Code 1, These fields are informational only.
2, 3
Comment Additional information on any recent changes in your company that
may have impacted employment, wages, and locations, such as
changes in business activities, acquisitions, mergers, and sales.
Refer to the BLS website for more information.
Include for Select Yes if this location is eligible for MWR reporting; when the
Reporting process is run, all employees assigned to this location are included
in the report. Select No to exclude this location from the report.
7. In the United States Reporting Information section, define the following EEO and VETS information:
Field Name Notes
D-U-N-S Number Enter the 9-digit business identifier assigned by Dun and Bradstreet.
NAICS Number Enter the 6-digit North American Industry Classification System
(NAICS) code. This number is used by federal statistical agencies
in classifying business establishment.
8. In the United States Veteran Reporting Information section, define the following VETS information:
Field Name Notes
Reporting Name Enter the location reporting name.
Hiring Location Enter the hiring location number.
Number
Maximum Number Specify the greatest number of employees currently hired during the
of Employees 12-month period covered by this report.
Minimum Number Specify the fewest number of employees currently hired during the
of Employees 12-month reporting period.
42
9. In the United States EEO-1 Reporting Information section, define the following EEO-1 information:
Field Name Notes
Reporting Name Enter the location reporting name.
Unit Number Enter the unit number applicable to the establishment or location.
Reported Last Select Yes or No.
Year
10. In the United States Unemployment Reporting Information section, define the following information:
Field Name Notes
Employer Unit Enter a three, four, or five digit number, depending on the state.
Number Currently this is required for New Mexico, Massachusetts,
Minnesota, Iowa, and Michigan.
11. For locations in Pennsylvania, enter additional information to support PA Act 32.
12. In the United States EEO and Veteran Reporting Information section, identify the HR Reporting locations.
A location is identified as a reporting location when the HR Reporting Location field is set to Yes.
For Example:
An employer may have multiple physical locations that are in close proximity to each other and are therefore
reported under a single HR Reporting Location. To represent this, No for a locations HR Reporting
Location and attach it to a location identified as a HR Reporting location. This can be accomplished through
the following configuration:
Field Name Value
HR Reporting Location No
HR Reporting Proxy Select reporting location
13. Click Submit.
43
Departments
A department is a division of a business enterprise dealing with a particular area or activity to which you can
assign workers.
No data is required or captured at this level for the US, 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. Define the information required for this department.
4. Click Next to provide additional department details.

5. Click Next.
6. Review your data, and click Submit.
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.
44
To create grades:
1. Select Manage Grades in the implementation project task list.
2. Click Create.
3. Define the information required for this grade.
4. Click Next to define the order of progression between grades.
5. Click Next to define grade rates.
45
Grade rates can be used to define pay values for grades in a legislative data group (country).
6. Add a rate that was previously defined or create a new rate.
7. Click Next.
8. Review your data, and click Submit.
Jobs
To create jobs:
1. Select Manage Job in the implementation project task list.
2. Click Create.
3. Define the information required for this job.
46
4. Click Next to enter job details.
This information is used in HR reporting and payroll processing.

5. Specify the following information in the United States Job Information section:
Field Name Notes
FLSA Status Select a code to indicate whether this job is exempt or nonexempt
according to the Fair Labor Standards Act Status.
EEO-1 Category To report valid job codes for EEO-1 and VETS reporting, select an
EEO-1 category to which this job belongs.
Job Group Used to store jobs of a similar type together in one group. To further
classify the job categories, select the job group to which this job
belongs.
6. Click Submit.
Actions Reasons
Action reasons are useful primarily for analysis and reporting purposes. They provide information about when or
why a specific action can be taken, such as termination of a worker. They can also be used to trigger a process
based on the value of the action reason.
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.
47
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.
The following screen below shows the action reasons for the termination action:
48
3. To create a new action reason for an action, click Create in the Actions Reasons section and complete the
required fields:
The new reason code is available for selection when a user performs the specified action.
4. Click OK.
Managing Workforce Structures

As described in the previous sections, implementers use the setup tasks in FSM to create organization and
workforce structures. Maintenance of such structures can also be performed through FSM. For some of these
structures, maintenance tasks are also available in the Workforce Structures work area:
49
When you select Workforce Structures in the Navigator, the following page is displayed:
Use this work area to manage:

Positions
Jobs
Grades
Departments
50
Locations
Banking Setup
An HR-only customer may want to add payee banking information even if payroll is not being processed by
Oracle Fusion HRMS for US. 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 set up of banks and branches must be done before entering bank accounts
and payment methods for the payee. Additionally some payroll set up, described later in this document, would be
needed.
No banks or branches are predefined for the US. Banks and branches must be defined during implementation.
You can do this 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 in the implementation project task list.
3. Click Create.
4. On the Create Bank page, provide the necessary information.
51
Bank Branches
To define branches for the banks you created:
1. Select Manage Bank Branches in the implementation project task list.
2. Click Create.
3. On the Create Bank Branch page, provide the necessary information.
52
Bank Accounts
Once banks and branches are set up, you must 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 US.
To define bank accounts:
1. Select Manage Bank Accounts in the implementation project task list.
2. Click Create.
3. On the Create Bank Branch page, provide the required information.
53
4. If you want to use this bank account for processing payments related to payroll, select the Payroll option in
the Account Use field.
Organization Payment Methods

After setting up the banks, bank branches, and bank accounts, you must define the payment methods used
within the organization. Organization payment methods (OPMs) link the personal payment methods (PPMs) with
the payment sources without a need to store as many details about the payment method on the person record.
When you create a payroll, you must define the valid OPMs for that payroll. All employees included in the payroll
run will use the selected OPMs, unless specifically overridden.
To define OPMs:
1. Select Manage Organization Payment Methods in Payment Method work area.
2. Click Create.
3. Select the LDG associated with this payment method.
4. On the Create Organization Payment Method page, enter the required information.
54
Name Enter the name of this OPM.

Payment Type Select the payment type for this OPM.
Currency Select US Dollar.
Prenotification required Prenotification is the process of submitting a zero-dollar
transaction in order to verify an electronic transfers routing
numbers and account number information. Use this field to
indicate whether a prenotification process is required for
direct deposit payment types.
5. If you have selected NACHA as the payment type, in the Electronic Funds Transfer File Information section,
enter the appropriate values.
Field Label EFT Name Comments
Balancing Entries Balanced Electronic File Determines whether the system
generates a balanced or unbalanced
electronic payments file. An
unbalanced electronic payments file
does not have an offsetting debit record
and therefore allows cases where the
total debits of the file are not equal to
the total credits. Some banks require
unbalanced files.
Bank Reference Immediate Destination Identifies the immediate destination
Identification bank routing and transit number.
Bank Name Immediate Destination Name of the Financial Institution.
Name
Company Immediate Origin Optional.
Reference Type Identification Type
Company Immediate Origin Numeric code assigned to the employer
Reference Identification by an external authority, such as their
IRS tax ID or D-U-N-S number.
Company Name Immediate Originator Identifies the company name of the
Name originator.
Payment sources associate bank accounts and other sources of funds with OPMs. Each organization
payment method that is in use must have at least one valid payment source.
55
6. In the Payment Sources Section, click Create.

7. On the Create Payment Source page, enter a Name and select a Bank Account Name.
The system uses the payment information set at the payment source level for NACHA employee direct
deposit.
8. Enter required information, and click Submit.
56
Payroll Configuration
Consolidation groups and payroll definitions are normally concepts related to payroll, but if an HR-only customer
needs to assign banking details for their employees, then these objects must be set up.
Consolidation Groups
Oracle Fusion HRMS (US) uses consolidation groups within the organization to enable grouping of different
payrolls for reporting purposes. No consolidation groups are predefined for the US. If you are creating payroll
definitions for the implementation, you must define at least one consolidation group. Payroll definitions must be
assigned to a consolidation group.
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 in the implementation project task list.
3. On the Manage Consolidation Groups page, click the Add Row icon.
57
4. Enter a name, and select a US LDG.

The Description is optional but useful to provide.
5. 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, bi-weekly, or semi-monthly, determine
the interval at which you pay employees.
A payroll definition is associated with only one payroll period type, and implementers must set up at least one
payroll definition for each payroll period type the employer wants use to pay employees.
When you create a payroll definition, the complete payroll schedule is automatically generated, based on:
Selected payroll period type
Any offsets and calendar adjustments
Number of years
Once you have created a payroll definition, use the Manage Payroll Relationships page to assign employees to it.
Note:
Before creating a payroll definition, you must have defined the LDG and at least one consolidation group.
No payroll definitions are predefined for the US.
To set up payroll definitions:
1. Select Manage Payroll Definitions in the implementation project task list.
58
2. Click Create.
3. Select the LDG for this payroll definition, and click Continue.
4. On the Create Payroll page, enter the required information.
59
5. Select a consolidation group.

6. Click the Add Row icon in the Valid Payment Methods section, and add one or more OPMs that are valid for
this payroll.
You can select any OPM defined for the LDG that is linked to this payroll definition.
The default payment method is check.
7. Select Premium Calculation rate for FLSA calculation.
8. Select a time definition.
This is used to define the starting date and length of the overtime period used in the calculation of FLSA.
9. Click Next.
10. Provide the required information on the Payroll Offsets page.
11. Review the information on the Payroll Calendar page.
12. Provide the suspense and default accounts on the Costing of Payroll page.
13. Review summary information on the Payroll Review page.
14. Click Submit.
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 element
definition process gets a set of rules from the template and processes the predefined template structure to create
appropriate data.
60
A set of element templates is predefined for the US. They are accessed through the Manage Elements task.
To create a regular earnings element for basic salary:
1. Select Manage Elements in the Setup and Maintenance or Payroll Calculations work area.
2. On the Manage Elements page, click Create.
3. On the Create Element window, select a LDG, a primary element classification, and if necessary, a
secondary classification.
Note:
Primary classifications have a priority range. When you define an element, you can override the default
processing priority with another number from the range. This is useful if you need to establish the order in
which the element processes with respect to other elements in the primary classification range.
Select the appropriate secondary classification. This secondary classification is used when updating or
creating wage basis rules or wage attachment rules.
4. Click Continue.
5. Complete the fields on the Basic Information page.
61
The questions and default answers are based on settings for the predefined classifications for the US. Your
answers drive the definition of the element you are creating.
6. Click Next.
7. Complete the rest of the questionnaire.
62
8. Click Next.
9. Verify the information, and click Submit to create the new element.
63
The Element Summary page provides additional information, such as input values, processing rules, and
eligibility.
64
10. Use the Element Overview panel to navigate through the summary page options.
11. To set element eligibility, in the Element Overview panel, select Actions > Create Element Eligibility.
This displays the Element Eligibility page. Element eligibility must be defined so the element can be linked to
an element entry (and hence to gross compensation).
12. Enter a name in the Element Eligibility Name field, and click Submit.
65
By entering only a name and no eligibility criteria, the element is eligible for all employees.
13. Select an input value in the left panel, and provide additional information such as default values, validation
formulas, and required flag.
14. Click Submit and Done.
15. Repeat this process to create a set of elements to support your business needs.
Element Eligibility and Costing

You must define element eligibility for the following elements for costing.
Element
Primary Secondary
Generated from Input Value
Classification Classification
Template
Standard Earnings All Secondary <User Element> Earning Calculated
classifications Results
Supplemental All Secondary <User Element> Earning Calculated
Earnings classifications Results
Imputed Earnings All Secondary <User Element> Earning Calculated
Nonpayroll Payment All Secondary <User Element> Earning Calculated
66
Pretax Deductions 401K <User Element> Deduction Amount

Result
Pretax Deductions All other secondary <User Element> Pay Value
Employee Tax All Secondary <User Element> Pay Value
Deductions classifications
Employee Tax All Secondary <User Element> Pay Value
Credits classifications
Involuntary All Secondary <User Element> Amount Taken
Deductions classifications Results
Involuntary All Secondary <User Element> Fee Calculated
Deductions classification Fees Organization Fee
Results
<User Element>
Person Fee Results
<User Element>
Processing Fee
Results
Voluntary Deduction All Secondary <User Element> Pay Value
You must define eligibility for these elements, as it is used to create the element entries.
You must define eligibility for the predefined US Taxation element as an open link.
Salary Basis
A salary basis allows employers to:
Establish the period of time for which an employees salary is quoted
Link a payroll element to a salary basis
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 the Compensation work area.
67
3. Select Manage Salary Basis.
4. Click Create.
5. On the Create Salary Basis page, select the element to use for the salary basis and provide the required
information.
68
Creating a Gross-up Earnings Element

To configure the system to process a bonus gross-up element:
1. Define the gross-up earning element using the following information:
Field Name Value
Primary Classification Supplemental Earning
Secondary Classification Bonus
Processing Type Nonrecurring
Employment Level Assignment level
Process the element only Yes
once in each payroll
period?
Use this element to Yes
calculate a gross amount
from a specified net
amount?
Process and pay element Process Separately but pay with other earnings
separately or with other
earnings elements?
2. To create element eligibility links, click Element Eligibility in the Element Overview section and then select
Create Element Eligibility from the Actions menu.
69
3. Click Done.
4. To ensure the FIT deduction is calculated at 39.6% (the highest tax bracket), override the Supplemental Rate
percentage on the employees Manage Payroll Calculation Information page for the federal employee
withholding certificate.
5. To define the element entries for the gross-up element:

a. Navigate to the Manage Element Entries task.
b. Search for the person.
c. Click Create.
70
d. Enter the appropriate effective date, and select the gross-up earnings element name.
e. Enter the net value to be used for the grossup calculation in the Net field.
f. Enter 1.00 in the To Within field.

g. Click Submit and Done.
6. Calculate quick pay, using the Regular run type and deselecting all elements on element entry except:
Gross-up element
US Taxation
Refer to QuickPay: How It Is Processed in the Help Portal for instructions on how to run a quick pay
operation.
7. Click Next, and enter parameter details.
8. Click Next and then Submit.

9. Click Go to Task.
71
10. In Calculate QuickPay page, select Regular Run Type and click Submit Process.
11. Navigate to the View Person Process Results task to see the gross-to-net calculation results.
For example, the following is a sample statement of earnings for a test employee who has not yet reached
their Social Security tax maximum:
Based upon calculations performed in the test environment, the employees FIT withheld is calculated at
39.6% of gross wages:
72
Creating a Gross-up Imputed Element

To configure the system to process a bonus gross-up imputed element:
1. Define the gross-up imputed earning element using the following information:
Field Name Value
Primary Classification Supplemental Earning
Secondary Classification Bonus
period?
Use this element to Yes
calculate a gross amount
from a specified net
amount?
Process and pay element Process Separately but pay with other earnings
separately or with other
earnings elements?
3. Click Done.
4. To ensure the FIT deduction is calculated at 39.6% (the highest tax bracket), override the Supplemental Rate
percentage on the employees Manage Payroll Calculation Information page for the federal employee
withholding certificate.
73
5. To define the element entries for the gross-up element:

c. Click Create.
d. Enter the appropriate effective date, and select the gross-up imputed earnings element name.
e. Enter the net value to be used for the grossup calculation in the Net field.
f. Enter 1.00 in the To Within field.

g. Click Submit and Done.
An additional voluntary deduction must now be configured.
6. Navigate to the Manage Elements task, and define a gross-up deduction element:
Field Name Value
Primary Classification Voluntary Deduction
74
Secondary Classification N/A

period?
8. In the Element Overview section, select Run Type Usages.

9. In the Element Run Type Usages table, select Exclude for both the Regular and Regular Normal run types.
10. Click Submit and then Done.

11. To define the element entries for the deduction element:
75

c. Click Create.
d. Enter the appropriate effective date and select the gross-up deduction element name.
e. In the Amount field, enter how much the deduction should reduce the net pay.
f. Click Submit and Done.

12. Calculate quick pay, using the Regular run type and deselecting all elements on element entry except:
Gross-up element
Deduction element
US Taxation
Refer to QuickPay: How It Is Processed in the Help Portal for instructions on how to run a quick pay
operation.
13. Click Next, and enter parameter details.
14. Click Next and then Submit.
15. Click Go to Task.
16. In Calculate QuickPay page, select Regular Run Type and click Submit Process.
17. Navigate to the View Person Process Results task to see the gross-to-net calculation results.
Overtime
Oracle Fusion HRMS (US) determines the overtime rate according to the Fair Labor Standards Act (FLSA)
eligibility based on the job assigned to the employee. Employers define a job as nonexempt in the FLSA Status
field found in the United States Job Information region (refer to the job work structures previously defined in this
document). Oracle Fusion HRMS (US) applies the FLSA Overtime calculation rules only when the job for the
assignment is nonexempt. If a job exists for the employee, but the FLSA Status is null or if no job is assigned to
an employee, the default status is exempt.
The FLSA Status impacts the premium overtime calculation if the job is defined as nonexempt. If an employer
elects to pay exempt employees overtime, FLSA does not control the rate, and the employer can pay the
overtime at whatever rate they want. In this case, the premium calculation of overtime is not performed since it is
defined by the employer.
See Oracle Fusion HRMS (US): Payroll Fair Labor Standards Act Setup white paper on MOS for necessary
setups for the FLSA set up.
76
Wage Basis Rules

US legislation has provided the wage basis rules at the federal and regional (state) levels for use in the taxation
of earnings. Rules for primary classifications of supplemental earnings, imputed earnings, and pretax deductions
along with the corresponding secondary classifications are provided. For information on wage basis rules as it
relates to involuntary deductions, refer to the Oracle Support Document 1597039.1 (Oracle Fusion HRMS (US):
Payroll Involuntary Deductions). https://support.oracle.com/epmos/faces/DocumentDisplay?id=1597039.1
Viewing Wage Basis Rules

Use the Manage Component Group Rules task from the Payroll Calculation work area to view the wage basis
rules.
1. Navigate in the tree structure to Federal > Wage Basis Rules > No References.
2. View the wage basis rules for Imputed Earnings, Pretax Deductions, and Supplemental Earnings as they
relate to each federal-level tax.
For Earnings, a check mark indicates the earning is subject to that tax.
Note:
The Not Withholdable Federal Tax column indicates the earning is subject to federal tax but no tax is
withheld.
For Pretax Deductions, a check mark indicates that the deduction is subject to taxation and will not reduce
subject wages. If no check mark is present, then the deduction is not subject to taxation and will reduce
subject wages.
3. Navigate in the tree structure to Regional > Wage Basis Rules > State.
77
4. View the wage basis rules for Imputed Earnings, Pretax Deductions, and Supplemental Earnings as they
relate to each state-level tax.
5. Due to the large volume of data, filter the data to view a particular state. Use the field above the State
column to enter the value. If no field is available above the State column, select the filter icon.
Creating Wage Basis Rules

US legislation is not providing any wage basis rules at the local level (city, county, or school). The local wage
basis rules follow the state wage basis rules. There are a few states where the local wage basis rules differ from
the state wage basis rules. You must create the local wage basis rules in these cases.
For example, at the Ohio local level, Deferred Compensation 401k and Deferred Compensation 401k Catch Up
are subject to tax. At the Kentucky local level, all Pretax Section 125 secondary classifications are taxable
(Dental Care 125, Dependent Care 125, Flexible Spending Account, Health Care 125, Health Savings Account,
Health Savings Account Catch Up, and Vision Care 125).
Use the Manage Component Group Rules task from the Payroll Calculation work area to create a local wage
basis rule.
For example, to create a new city tax rule for Ohio:
1. Navigate in the tree structure to Regional > Related Deductions > City Tax > Wage Basis Rules.
78
2. Select Actions > Create.
The Create Wage Basis Rule UI appears.
3. Enter the following information:
79
Field Name Requirement Mapping

Effective Start Date Required Recommended to use either
implementation date or the earliest date a
pay period exists.
State Optional 2-character state abbreviation.
County Mandatory Appropriate county from the LOV.
Note:
Although the UI does not denote this field
as required, this information is necessary
for creating local tax rules.
City Mandatory Appropriate city from the LOV.
Note:
Although the UI does not denote this field
as required, this information is necessary
for creating local tax rules.
Primary Classification Mandatory Selected from LOV. The following are
used primarily for this configuration:
Imputed Earnings
Pretax Deductions
Supplemental Earnings
4. Mark the Select all secondary classifications checkbox if all secondary classifications under the primary
classification would be defined the same way.
Note:
For the purpose of this example, do not select the checkbox.
5. Click Submit.
You may need to query by state to see the data you just created. If so, enter a value in field directly above
State for the state entered in previous step. This filters the data in the UI for that state. If a blank field is not
available for entry above State, select the filter icon.
These rules are stamped with the LDG and are not overwritten by Oracle Fusion HRMS (US).
6. Select the row to update.
You must repeat the following steps for each combination of primary classification and secondary
classification for each state / county / city that needs updating.
80
7. In the Actions drop down list, choose Edit > Correct.
The Correct Wage Basis Rule for Secondary Classification window appears.
8. Select the Subject to wage basis rule box.

For Ohio, 401 (k) does not reduce subject wages at the local level and is considered taxable.
9. Click Submit.
The Wage Basis Rules UI returns the row corrected with a check in the Use in Wage Basis column.
81
10. Create a wage basis rule for Deferred Compensation 401k Catch Up.
This change must be completed for every state / county / city combination for the locales the employer is in
for Ohio.
11. If county taxes are impacted, the same entries must be applied for the state / county combination for each
appropriate primary classification/secondary classification.
12. Complete a review of all secondary classifications impacted to determine which entries require corrections.
For Example:
When working with pretax deductions, determine what Section 125 secondary classifications are impacted for
a particular state / county / city or state / county combination. There could be a difference between the
treatment of HSAs, FSAs, Dental, Vision, Healthcare, and Dependent Care. One or more may need
corrections where others may not.
Employee Management
Once the organizational and workforce structures have been defined by the Implementation Team, the user is
ready to manage their 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 a Human
Resource Specialist, rather than to a member of the Implementation Team:
82
Hiring a Worker
The new hire process is the first task in the workforce lifecycle.
Note:
Before you can hire an employee, you must have already defined all available business units, jobs, grades,
departments, locations, overtime periods, and other payroll values must have been previously defined. The
business unit you select determines which job, grades, and department you can select.
To hire an employee:
1. Select New Person under Workforce Management in the Navigator.
2. In the task list on the left, select Hire an Employee.
The supported person types for the US are:

Employee
Contingent Worker
Nonworker
Pending Worker
83
3. On the Identification page, provide the following information in the Basic Details section:
Hire Date Date of the employees hire.
Hire Action Select Hire.
Hire Reason Valid action reasons defined for the hire action.
Legal Employer Displays a list of all legal employers for the US.
4. Provide the following information in the Personal Details section:

Last Name / First Name format is determined by the formats predefined for the US.
Name
Date of Birth Not mandatory for HR implementations, but it is mandatory for US
payroll implementations.
5. Use the National Identifiers table to enter the Social Security number.
6. Click Next.
7. On the Person Information page, in the Home Address section, provide an address that conforms to the
predefined US address format.
All employees attached to a payroll must have a home address throughout their period of employment.
84
Note:
Customers can use the 2-digit state abbreviation in release 7 and onwards. This change was included in
release 7 bundle 3 where the geography process was modified to default the state to the 2-digit state
abbreviation. Also, changes were made to ensure that there is no impact on employers that were using full
state names. Payroll setup and calculation works if employers use the full state name or the state
abbreviation.
8. Specify any of the following optional information:
Phone and E-Mail
Marital Status, Ethnicity, and Veteran fields in the Legislative Information section
Note:
The Ethnicity and Veteran fields are required for EEO and VETS reporting.
Citizenship and Visa Information
Emergency Contacts
9. Click Next.
10. On the Employment Information page, provide the necessary work relationship, payroll relationship,
assignment, job, manager, payroll, and salary details.
11. Click Submit.
Once a TRU is attached to an employee, the W-4 Federal Tax Card is generated. The association to the TRU is
also generated. This tax card is not created for HR-only customers.
Verifying Employee New Hire Status in Work Relationship Details

When hiring or rehiring employees, the New Hire Status field indicates whether they are to be included or
excluded from new hire reporting. Find this field in the Work Relationship Details of the Employment Information
page.
New Hire Status Identifies the employees employment status as pertains to the
New Hire report:
Include in the New Hire report Employee is to be included in
the next run of the New Hire
85
Report.
Already reported Employee has already been
included in a previous run of
the New Hire Report. The
New Hire Report process
automatically sets all included
employees to this status upon
completion in final mode.
Excluded from the New Hire Employee is not included in
report the report.
Maintaining Person and Employment Information

Once the new hire process is complete, the person is recorded in the system. Users can modify the person and
employment information as needed.
To maintain an employees person information:
1. Select Person Management under Workforce Management in the Navigator.
2. Search for and select the person record.

This starts the Manage Person task.
86
3. Use the Manage Person tabs to view the complete set of person information.
Note:
Use the Extra Information tab to capture country-specific person information. There are no US-specific fields
on this tab.
87
4. Select either Edit > Correct or Edit > Update to modify the information in any section.
Use Correct to reflect that the change is being made to resolve an error.
Use Update to reflect that the change is being made as a result of a change in the employees data.
5. Click Submit when finished.
You are returned to the Person Management work area. This work area provides additional tasks for
maintaining employment information.
6. Use the Manage Employment task to modify an existing instance of employment or add a new instance if, for
example, an employee has a job change.
88
Managing the Employee Withholding Certificate

The Employee Withholding Certificate is the default tax card. For most employees, it is created automatically
during the New Hire process. The Employee Withholding Certificate provides information used in taxation. Items
such as filing status, number of allowances, and exemptions from taxes are specified on the card. If no values
are entered, during tax calculations, a default value of Single for filing status and zero allowances will be used.
Setting Up Automatic Card Creation

To ensure that new workers get an Employee Withholding Certificate:
1. Set the PAYROLL_LICENSE process configuration parameter to either PAYROLL or
PAYROLL_INTERFACE, as appropriate to your implementation.
2. Confirm that element eligibility has been created for the US Taxation element.
Manual Card Creation

For employees that dont already have an Employee Withholding Certificate:
1. Start the Manage Calculation Cards task.
2. Search for and select the person record.
3. Click Create.
4. Enter an appropriate Effective-As-of-Date, and select Employee Withholding Certificate for Name.
5. Enter employee information as appropriate at the Federal level.
6. Click Save.
7. Select the Regional link under the Component Groups tree.
8. Enter employee information as appropriate for the Regional level.
9. Click Save.
10. Select the Associations link under the Component Groups tree.
89
11. Under Associations, click Create.

12. Select the Tax Reporting Unit, and click OK.
13. Click Save.
14. Under Association Details, click Create.
15. Select the Employment Terms Number and the Calculation Component, and click OK.
16. Click Save.
My Portrait Configuration
Employees can update their own withholding information in Portrait using the Manage Tax Withholding action.
The Edit icon is available for federal and supported states. Currently only states that follow federal are
supported. A federal editable PDF form is shown for the employee to make their updates.
Terminating a Worker
When a persons employment period ends, the work relationship must be terminated.
To terminate a work relationship:
1. Select Manage Work Relationship in the Person Management work area.
2. On the Manage Work Relationship page, select Terminate from the Actions menu.
3. On the Terminate Work Relationship page, enter the details of the termination, including the termination
reason.
90
4. Click Submit.
Assigning Salary Information to an Employee

Once you have completed the setup for salary basis, you can assign salary information to an employee:
1. Sign in to the application with a role that has compensation manager privileges, such as CMP_ADMIN_ALL.
2. Navigate to the Compensation work area.
3. Select Manage Salary, and then search for and select the employee.
4. On the Manage Salary page, enter a salary basis and salary amount in the Salary Details section.
91
5. Click Continue.
6. Review your changes, and click Submit.
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.
Person Payment Information

To add payment information for an employee, you must assign a payroll definition to the employee.
Assigning a Payroll to the Employee

After the hire process, if a payroll needs to be assigned or changed, follow these steps:
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.
3. Search for and select the employee.
4. In the Payroll Details section of the Manage Person Details page, add the payroll.
92
5. Click Save and then Done.
Assigning Payment Methods to the Employee

Before adding payment methods to an employee, ensure that banks and branches have been configured in the
system and a payroll definition has been assigned to the employee. By default, all employees inherit the payroll
definitions OPM. If you want to override this for a specific employee, you need to create a PPM and select an
alternate OPM.
To assign PPMs:
1. Select the Manage Personal Payment Methods task in the Payroll Distribution work area.
2. Search for and select the employee.
3. On the Manage Person Details page, click Create.
4. On the Personal Payment Method page, select the Organization Payment Method for this employee.
93
5. If the payment type is NACHA, you must add a bank account and provide banking details.
6. Add multiple payment methods as needed.

7. Use the Payment Amount Type and Percentage fields to manage distribution across different payment
methods.
8. Click Save and then Done.
Tax Troubleshooting
Before contacting Oracle Support for any of these issues, please check the following:
Problem Solution
Errors during payroll calculation Confirm that a TRU is properly associated to
the employees withholding certificate. Refer to
the Managing the Employee Withholding
Certificate section for more information.
Errors during payroll calculation related to the Use the Manage Legal Reporting Unit
94
US_TAX_SDI formula Calculation Cards task to confirm that the SDI

and SIT component details have been created
for the LRU. No overrides are necessary.
Only the component detail needs to be
created.
Periodic Archiver does not archive any US Check that the United States Federal Tax
balances registration exists for the TRU.
Payroll run produces inaccurate tax Check the following:
calculations Verify that the employees resident and
work addresses are in US address format,
and confirm any overrides.
For work addresses, the following
hierarchy is used:
1. Home worker: Manage Employment >
Job Details > Working at Home. If
Yes, follow the Resident address
hierarchy (below).
2. Assignment location override: Work
Tax Address set in the Manage
Employment task.
3. Location override address set in the
Manage Locations task.
4. Location Address set in the Manage
Locations task.
For Resident address, the following
hierarchy is used.
1. Address Type of US Resident Tax
Address.
2. Address with Type of Home.
Verify the following for the affected
employee:
They have an Employee Withholding
Certificate.
It is associated with a TRU.
Their filing status and number of
exceptions are correct.
Confirm that the appropriate state or local
taxes have been applied, based on the
employees resident and work address.
Confirm the calculation against the rates
and rules provided in the Vertex
Calculation Guide.
Verify your federal and state wage basis
rules:
1. Navigate to Manage Deduction Group
Rules > Wage Basis Rules.
95
2. Select Federal or State.

3. Compare your wage basis rules
against the State Withholding Tax
Summary in the Vertex Calculation
guide.
New Hire Reporting

New hire reporting is the process of reporting newly hired and rehired employees to a state agency.
Prerequisites
Some of the following steps require the use of a task or tasks. These tasks must be accessed through an
implementation project in order to set the scope. Use an existing implementation project with the Workforce
Deployment task list included or create a new one.
Set Up Steps
To configure Oracle Fusion HRMS (US) to run the New Hire report:
1. Ensure that a default TRU is associated to a legal employer.
2. Refer to the Legal Entity HCM Information for Legal Employers and PSUs section for the new hire reporting
rules.
3. Enter employer contact details for a TRU.
4. Refer to the Legal Reporting Unit Contact Details section on how to capture contact details for a TRU.
5. Verify Federal Employer Identification Number (FEIN) is set up for United States federal tax.
6. Refer to the Click OK.
b. Click Create.
d. Click OK.
e. Click Create.
96

g. Click OK.
b. Click Add Row.
Note:
10. Legal Reporting Unit Registrations section for information on creating registrations.
12. Verify the employees New Hire Status.
Refer to the Hiring a Worker section for information on New Hire Status.
Running the Report

Run the New Hire State Electronic Report to produce information on all your newly-hired and rehired employees.
To run the New Hire State Report:
1. Select Navigator > Data Exchange > HCM Extracts > Submit Extracts.
Note:
Use the following navigation in Release 7: Navigator > Data Exchange > Processes > Submit an HCM
Process.
2. Select a value from the Legislative Data Group LOV.
3. Select the Run New Hire State Report flow pattern in the Process or Report section.
4. Click Next.
5. Enter the following parameters:
Parameter Requirement Notes
Payroll Flow Mandatory Enter a unique name.
Multistate Employer Mandatory Select Yes if you are a multistate employer
and want to report all employees to a single
state agency.
Legal Employer Optional Select a legal employer to report all
employees attached to it.
Start Date Optional Enter a start date if you want to establish a
date range for reporting your new
hires/rehires. Otherwise, all unreported hiring
changes are reported as of the mandatory
end date.
End Date Mandatory If a start date is entered, this represents the
97
end of the reporting date range.

If a start date is not entered, the report
process captures all new hire/rehires as of
this date.
Reporting State Mandatory State to which you are submitting this report.
The report is formatted according to this
states requirements.
Reporting Mode Mandatory Choose one of the following:
Draft: Use to verify the data prior to
submission.
Final: Use to produce the final output file
for submission. When you use this
mode, the New Hire Status of all reported
employees is updated to Already
reported.
New Hire Contact Optional This field is used to override contact
information in the report. LOV will get
populated with list of contact persons with
HR Representative role.
6. Click Next.
7. Click Next in the Enter Flow Interaction task.
8. Select As soon as possible in the Schedule task.
9. Click Next.
10. Click Submit.
11. Click OK and View Checklist in the Confirmation window.
Viewing the Output

You can find the output files in the navigation path given below:
1. Click Navigator > Tools > Reports and Analytics.
2. Expand Shared Folders > Human Capital Management > Workforce Management > Person Management >
US > New Hire.
3. Click New Hire Electronic Report.
4. Click History.
5. Remove value in Owner field in Filters Section
6. Click Search.
The report process generates two files with different Report Job Names (Number):
NewHireStateETextReport: Electronic submission file
NewHireStateAuditReport: New Hire State Audit report
The date and time represents when you ran the process.
7. Select the link under Report Job Name for the values appropriate for the date and time you ran the process.
8. Open the audit report file in a spreadsheet, and verify your newly-hired and rehired employees information.
9. Double-click the output name link under the Output & Delivery section.
10. Open or Save the file.
98
VETS-100 and 100A Employment Report

Oracle Fusion HRMS (US) supports the generation of VETS-100 and VETS 100A Federal Contractor Veterans
reports.
Prerequisites
Set Up Steps
To configure Oracle Fusion HRMS (US) to run the VETS reports:
1. Define VETS specific information in the Location UI.
2. Refer to the Locations section for descriptions of the VETS-specific information that must be captured.
3. Each of your jobs must be associated with an EEO-1 category.
4. Refer to the Jobs section for instructions on how to assign an EEO-1 category to a job.
5. Enter VETS reporting information for your legal employer.
6. Refer to the Legal Entity HCM Information for Legal Employers and PSUs section for additional information.
7. Enter VETS reporting information for your TRU.
8. Refer to the Legal Reporting Unit HCM Information section for additional information.
9. Verify FEIN is set up for United States federal tax.
b. Click Create.
d. Click OK.
e. Click Create.
99

g. Click OK.
b. Click Add Row.
Note:
14. Assign the appropriate veterans data to employees.
15. When hiring a new employee, you record their Vets-100 and Vets-100A data on the Hire an Employee:
Person Information page, in the Legislative Information region.
16. Assign the appropriate job to employees.
17. When hiring a new employee, you record their job on the Hire an Employee: Employment Information page,
in the Job region.
Running the Report

To run the VETS reports:
2. Select a value from the Legislative Data Group LOV.
3. Select the Run VETS 100A Report flow pattern in the Process or Report section.
4. Click Next.
100
Establishment Mandatory Select Multiple if you have multiple

Employer Type establishments. Otherwise, select Single.
Start Date Mandatory Specify the starting point of the reporting date
range.
The default is 12 months prior to the end
date. This is also the minimum.
End Date Mandatory Represents the end of the reporting date
range. Can be any date between 01 July and
30 September of the current year.
Name of Certifying Optional Default is the HR Representative name
Official defined on the TRUs contact information.
Phone Number Optional Default is the HR Representative phone
number defined on the TRUs contact
information.
E-Mail of Certifying Optional Default is the HR Representative E-Mail
Official address defined on the TRUs contact
information.
6. Click Next.
8. Select As soon as possible in Schedule task.
9. Click Next.
10. Click Submit.
11. Click OK and View Checklist in Confirmation window.
Report process generates an electronic file, an audit report, and an exception report.
Viewing the Output

To view the output files:
101
US > VETS.
3. Click either VETS-100A Electronic Report or VETS-100 Electronic Report.
4. Click History.
5. Clear the value in the Owner field in the Filters section.

6. Click Search.
The report process generates three output files with different Report Job Names (Number):
VETS100A_ETextReport
VETS100A_AuditReport
VETS100A_ExceptionReport
Generally, the lowest report job name would be the electronic file, the next job name would be the audit
report, and the highest job name would be the exception report.
102
7. Select the Report Job Name link.

8. Review the exception report.
If there are any issues reported on this report, the electronic file may be blank.
9. Select the output name link under the Output & Delivery section.
EEO-1 Report
The Employer Information Report EEO-1, otherwise known as the EEO-1 Report, is required to be filed with the
U.S. Equal Employment Opportunity Commission's EEO-1 Joint Reporting Committee.
Prerequisites
Set Up Steps
To configure Oracle Fusion HRMS (US) to run the EEO-1 report:
1. Define EEO-1 specific information in the location UI.
Refer to the Locations section for descriptions of the EEO-1 specific information that must be captured.
2. Each of your jobs must be associated with an EEO-1 category.
Refer to the Jobs section for instructions on how to assign an EEO-1 category to a job.
3. Enter EEO-1 reporting information for your legal employer.
Refer to the Legal Entity HCM Information for Legal Employers and PSUs section for additional information.
4. Enter EEO-1 reporting information for your TRU.
Refer to the Legal Reporting Unit HCM Information section for additional information.
5. Verify FEIN is set up for United States federal tax.
103

b. Click Create.
d. Click OK.
e. Click Create.
g. Click OK.
b. Click Add Row.
Note:
11. Assign the appropriate ethnicity data to employees.
When hiring a new employee, you record their ethnicity data on the Hire an Employee: Person Information
task, in the Legislative Information region.
12. Assign the appropriate job to employees.
When hiring a new employee, you record their job on the Hire an Employee: Employment Information task,
in the Job region.
Running the Report

To run the EEO-1 report:
2. Select value from the Legislative Data Group LOV.
104
3. Select the Run EEO1 Report flow pattern in the Process or Report section.
4. Click Next.
Establishment Mandatory Select Multiple if you have multiple
Employer Type establishments. Otherwise, select Single.
Payroll Period Start Mandatory Select any payroll period start date occurring
Date during the third quarter of the current survey
year(July, August or September).
Payroll Period End Mandatory Select any payroll period end date occurring
Date during the third quarter of the current survey
year(July, August or September).
Title of Certifying Optional Use to override the contact information. The
Official default is the HR Representative title
specified on the TRU contact information.
Name of Certifying Optional Use to override the contact information. The
Official default is the HR Representative name as
specified on the TRU contact information.
Phone Number Optional Use to override the contact information. The
default is the HR Representative phone
number as specified on the TRU contact
information.
E-mail of Certifying Optional Use to override the contact information. The
Official default is the HR Representative E-Mail
address as specified on the TRU contact
information.
6. Click Next.
8. Select As soon as possible in Schedule task.
9. Click Next.
10. Click Submit.
11. Click OK and View Checklist in Confirmation window.
The report process generates an electronic file, an audit report, and an exception report.
Viewing the Output

To view the output files:
US > EEO.
105
3. Select EEO-1 Electronic Report.

4. Click History.
5. Clear the value in the Owner field in the Filters section.
6. Click Search.
The report process generates three output files with different Report Job Names (Number).
EEO1ETextReport
EEO1AuditReport
EEO1ExceptionReport
7. Select the link under Report Job Name for the values appropriate for the date and time you ran the process.
8. Select the output name link under the Output & Delivery section.
9. Open or Save the file.
Oracle Fusion HRMS (US):Implementation and Copyright 2012, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the
Use contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
May 2014 warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
Author: Oracle fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are
Contributing Authors: [OPTIONAL] 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 Corporation
World Headquarters
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
500 Oracle Parkway
Redwood Shores, CA 94065
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
U.S.A.
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
Worldwide Inquiries: trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open
Phone: +1.650.506.7000 Company, Ltd. 0112
Fax: +1.650.506.7200
oracle.com
106

Oracle - Fusion - HRMS - For - US - Implementation - and - Use - White - Paper Note 1676530.1 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle - Fusion - HRMS - For - US - Implementation - and - Use - White - Paper Note 1676530.1 PDF

Uploaded by

Copyright:

Available Formats

Oracle Fusion HRMS (US): Implementation and Use

An Oracle White Paper

Oracle Fusion HRMS (US):

Workforce Structures .......................................................................... 40

Assigning Salary Information to an Employee ............................... 91

Other Information Sources

Date Description of Change

01-May-2014 Created document.

22-May-2014 Added reference to Vertex troubleshooting document on MOS.

Installing the Monthly File Updates

Running the Process

Vertex Tax Calculation Reference Material

Support and Reference

Legal Reporting Unit Deduction Records

2. Select Setup and Maintenance from the Navigator.

3. On the Implementation Projects tab, click Create.

8. Click Save and Open Project.

Payroll Product License Parameter

1. Select Load Geographies for US in the implementation project checklist.

2. Enter the necessary details in the Parameters section.

Define Address Style Format Mapping for United States

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

3. Define your addresses as needed.

Legislative Data Groups

2. On the Manage Legislative Data Groups page, click Create.

Insurance jurisdiction for each state with a

Legal Employers and Payroll Statutory Units

Legal Reporting Units and Tax Reporting Units

Organization Structure Models Supported by the US Localization

Creating Legal Entities

2. Click Create to display the Create Legal Entity page.

3. Provide the required information, noting the following:

Viewing the LDG

3. Search for the PSU or legal entity.

Legal Entity HCM Information for Legal Employers and PSUs

3. Click Apply and Go to Task.

6. Click the Federal link.

7. In the EEO Reporting Rules section, specify the following values:

Legal Entity Deduction Records

2. On the Payroll Statutory Unit page, click Create:

Legal Reporting Units

5. Click Save and Close.

Legal Reporting Unit Contact Details

4. Highlight the LRU from the list, and click Contact.

5. On the Manage Contacts page, click Create Contact.

6. Enter the following information:

8. Define the contact points:

Legal Reporting Unit Registrations

To define a legal entity registration:

3. Verify there is a record for United States Federal Tax.

5. Enter the required information.

Legal Reporting Unit HCM Information

6. Click the Federal link.

7. In the Third Party Interfaces section, enter the following value:

Field Name Notes

Legal Reporting Unit Deduction Records

To enter a SUI rate:

5. Select the appropriate state, and click OK.

6. Select State Unemployment in the Calculation Components table.

5. Define the required fields in the Main Address section.

4. Click Next to provide additional department details.

4. Click Next to define the order of progression between grades.

5. Click Next to define grade rates.