Oracle Fusion Human Capital Management For US Implementation and Use White Paper PDF

Oracle Fusion Human Capital Management for the US: Implementation and Use
Guide (HR and Payroll)
ease
An Oracle White Paper

June 2017
Oracle Fusion Human Capital

Management for the US: Implementation
and Use Guide (HR and Payroll)
Release 11 and 12
Disclaimer
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
Table of Contents
An Oracle White Paper ...................................................................... 1
Release 11 and 12 ............................................................................ 1
Disclaimer ......................................................................................... 2
Table of Contents .............................................................................. 3
Overview ......................................................................................... 11
Reference Information ................................................................. 11
United States ........................................................................................ 11
Global Human Resources .................................................................... 11
Global Payroll Interface ........................................................................ 11
Global Payroll ....................................................................................... 12
General ................................................................................................. 12
Effective Dates ................................................................................ 14
Organization Structures ................................................................... 15
Enterprises .................................................................................. 15
Implementation Projects .............................................................. 15
Product Extension Parameter ...................................................... 18
Address Validation ................................................................................ 18
Address Style and Settings .................................................................. 18

Geographies ................................................................................ 19
Loading Geographies ........................................................................... 19
Verifying Geographies .......................................................................... 20
Configuring State Display Properties ................................................... 23
Running the Load Geography Information and Load Payroll Tax Information
Processes ............................................................................................. 23
Load Payroll Tax Information ....................................................... 23
Defining Address Style Format Mapping for United States .................. 24
Viewing Geocodes for a Geography .................................................... 25
Manually Adding a Geography ............................................................. 25
Changing the Address Field Display Sequence ................................... 27

Enterprise Structures ................................................................... 29
Legal Addresses .......................................................................... 29
Legislative Data Groups .............................................................. 30
Jurisdictions................................................................................. 30
Viewing Jurisdictions ............................................................................ 32
Creating Jurisdictions for Local Taxes ................................................. 34

Legal Entities ............................................................................... 35
Legal Employers and Payroll Statutory Units ....................................... 35
Legal Reporting Units and Tax Reporting Units ................................... 36
Organization Structure Models Supported by the US Localization ...... 36
Creating Legal Entities ......................................................................... 37
Identifying the LDG ............................................................................... 38
Additional Reporting Information for Legal Employers and PSUs ....... 39

Legal Entity Calculation Cards ..................................................... 44
Creating the Calculation Card .............................................................. 44
Creating Federal Tax Rules ................................................................. 45
Creating Regional Calculation Rules .................................................... 45

Legal Reporting Units .................................................................. 47
Contact Details ..................................................................................... 49
Registrations ......................................................................................... 52
HCM Information .................................................................................. 54
Reporting Establishments .................................................................... 57
Calculation Cards ................................................................................. 59
State Unemployment Insurance Rate .................................................. 59

Business Units ............................................................................. 62
Puerto Rico Configuration............................................................ 62
Legal Addresses ................................................................................... 62
Legal Reporting Units ........................................................................... 62
Tax Reporting Units .............................................................................. 63
Deduction Elements ............................................................................. 64

Workforce Structures ....................................................................... 65
Managing Workforce Structures .................................................. 65
Locations ..................................................................................... 65
Departments ................................................................................ 69
Grades ........................................................................................ 70
Jobs............................................................................................. 71
Banking Setup ................................................................................. 73
Configuring Employee Options for Bank Details .......................... 73
Defining Banks ............................................................................ 74
Defining Bank Branches .............................................................. 74
Defining Bank Accounts............................................................... 75
Defining Organization Payment Methods ..................................... 76
Configuring Prenotes ................................................................... 78
Payroll Configuration ....................................................................... 79
Consolidation Groups .................................................................. 79
Payroll Definitions ........................................................................ 80
Elements and Element Templates ................................................... 82
Costing ........................................................................................ 88
Element Eligibility ................................................................................. 88
Employee and Employer Tax Elements ............................................... 90

Secondary Element Classifications .............................................. 92
Domestic Partner Secondary Classifications ............................... 92
Retroactive Elements .................................................................. 92
Salary Basis ................................................................................ 92
Gross-up Earnings....................................................................... 94
Gross-up Imputed Earnings ......................................................... 98
Overtime Earnings ..................................................................... 102
Involuntary Deductions .............................................................. 102
Deferred Compensation............................................................. 102
Supported Deferred Compensation Plans.......................................... 102
Contribution Limits .............................................................................. 102
Balance and Feed .............................................................................. 102

Wage Basis Rules ......................................................................... 103
Viewing Wage Basis Rules ........................................................ 103
Creating Wage Basis Rules ....................................................... 103
Editing Wage Basis Rules ......................................................... 105
Document Delivery Preferences .................................................... 106
Person-Level Overrides ............................................................. 106
Document Delivery Preference Configuration ............................ 106
Process Configuration Group ........................................................ 107
Process Configuration Group for Forms W-2 and 1095-C.......... 107
Employee Management ................................................................. 109
Configuring Disabilities .............................................................. 109
Hiring a Worker ......................................................................... 109
Verifying Employee New Hire Status in Work Relationship Details111
Maintaining Person and Employment Information ...................... 111
Maintaining Person Information .......................................................... 111
Maintaining Employment Information ................................................. 112

Employee Security: Roles, Duties and Priveleges ..................... 114
Creating Custom Security Roles and Duties ...................................... 114
Employee Roles Within Portrait Access ............................................. 114
Smart Navigation ................................................................................ 114
Employee Management of Document Print Preferences in My Portrait115

Payroll Processing ......................................................................... 116
Taxation Within Fusion Payroll .................................................. 116
Managing the Employee Withholding Certificate ........................ 116
Setting Up Automatic Tax Card Creation ........................................... 116
Manual Tax Card Creation ................................................................. 116
Changing the TRU for an Assignment................................................ 117
Wage Accumulation............................................................................ 117
Manage Tax Withholding in My Portrait ............................................. 117
Manage Tax Withholding using Smart Navigation ............................. 119

Tax Calculation .......................................................................... 119
Payroll Processing .............................................................................. 119
Other Considerations.......................................................................... 120

Supplemental Taxation Overrides .............................................. 121
Prerequisites ....................................................................................... 121
Supplemental Earnings Elements ...................................................... 121

FUTA Credit Reduction Rate Overrides ..................................... 122
Calculation and Withholding of Pennsylvania Local Earned Income Tax 122
Configuring the Pennsylvania Local Earned Income Tax .................. 122
Setting Up Employee Earning Distribution Overrides ................. 124

Reciprocal Agreements and Setting the Employee Nonresident Status 127
SUI Limits and Changes to State ............................................... 127
Overriding the Employee’s California Wage Plan Code ............. 127
Terminating a Worker ................................................................ 128
Assigning Salary Information to an Employee ............................ 129
Adding Payment Information to an Employee ............................ 129
Assigning a Payroll to the Employee .................................................. 129
Transferring an Employee to a New Payroll ............................... 129
Assigning Payment Methods to the Employee ........................... 130
Payroll Processes .......................................................................... 131
QuickPay ................................................................................... 131
Settings that Affect Processing .......................................................... 131
How QuickPay Is Processed .............................................................. 131
Submit the QuickPay Flow ................................................................. 132
Calculate and Verify Run Results ....................................................... 133
Processing International ACH Transfers ............................................ 133

Employee Payslip ...................................................................... 133
Person Management Work Area ........................................................ 134
Manage Person .................................................................................. 134
Manage Document Records ............................................................... 135

Earnings Taxation Over Multiple Pay Periods ............................ 135
Pretax Deduction Refunds ......................................................... 137
Tax Troubleshooting ...................................................................... 138
New Hire Reporting ....................................................................... 140
Prerequisites ............................................................................. 140
Set Up Steps ............................................................................. 140
Baselining Employee Status After Implementation..................... 140

Generating the New Hire Report................................................ 140
Viewing the Output .................................................................... 141
VETS-4212 Employment Report.................................................... 143
Prerequisites ............................................................................. 143
Set Up Steps ............................................................................. 143
Running the Report ................................................................... 144
VETS-100 and 100A Employment Reports .................................... 148
EEO-1 Report ................................................................................ 149
Prerequisites ............................................................................. 149
Set Up Steps ............................................................................. 149
Multiple Worksite Reporting ........................................................... 152
Prerequisites ............................................................................. 152
Set Up Steps ............................................................................. 152
Troubleshooting ......................................................................... 155
Appendix A: Vertex ....................................................................... 157
Licenses .................................................................................... 157
Address Validation..................................................................... 157
Vertex Tax Calculation Reference Material ................................ 157
Troubleshooting ......................................................................... 157
Support and Reference.............................................................. 158
Appendix B: User Interface Customization ................................... 159
Customizing User Interfaces ...................................................... 159
Changing UI Color .............................................................................. 159
Customizing Fusion Application UIs Using Page Composer ...... 160
Appendix C: PA Residency Certificate in the Portrait Gallery ........ 161
Appendix D: Replacing the Preconfigured Payslip Template with a Custom

Template ....................................................................................... 162
Customizing the Template ......................................................... 162
Configuring the Delivery Options for the Online Payslip ............. 163
Configuring the Delivery Options for the Printed Payslip ............ 167
BI Server Information ................................................................. 169
Appendix E: Customizing the Check Template for the MICR Codes171
Appendix F: Adding a Signature File to the Check Template ........ 173
Appendix G: Setting up a Regular Earnings Element to Reduce Regular 174
Oracle Fusion Human Capital Management for the US: Implementation and Use Guide (HR and Payroll)
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
Reference Information
Utilize the following information to find other documents that may be useful for your implementation.
United States
United States Information Center (Doc ID 2063588.2). Contains all US specific information on HR, Benefits
(including ACA), and Payroll.
 Legislative Announcements
 Whitepapers
 Other useful US information
Global Human Resources

Location: Book List – Global Human Resources Cloud
Document Name
Release 11
Oracle Global Human Resources Navigate to the Oracle Help Center > Cloud > Applications
Cloud Using Global Human Tab (next to Get Started) > Global Human Resources >
Resources (Release 11) Release 11 > Books (on the left panel)
Oracle Global Human Resources This takes you to all of the documents listed in this chart.
Cloud Implementing Global
Human Resources (Release 11)
Global Payroll Interface

Document Name
Release 11
Oracle Global Human Navigate to the Oracle Help Center > Cloud > Applications
Resources Cloud Using Global Tab (next to Get Started) > Global Human Resources >
Payroll Interface (Release 11) Books (on the left panel)
Oracle Global Human This takes you to all of the documents listed in this chart.
Resources Cloud Implementing
Global Payroll Interface
(Release 11)
There are two options available to US customers wanting to outsource their payrolls to a third-party payroll
service provider:
 Using predefined extract definitions for ADP Connection for PayForce. The reference documents listed
contain detailed information about this interface and will not be covered in this guide.
11
 Using the inbound and outbound interface provided with the Global Payroll Interface. This enables the
application to interact with third-party payroll service providers. It also includes a predefined extract definition
you can tailor to meet your needs. The Global Payroll Interface extract definition works within the context of
the country or territory. When creating your copy of the extract definition, select a US legislative data group
(LDG). When selecting the LDG, some US specific parameters are included in the extract definition, such as
gender, marital status, ethnicity, and Fair Labor Standards Act (FLSA) status. In addtion, it includes
employee withholding certificate information for federal and regional levels. Refer to the documents listed for
further details on the Global Payroll Interface.
Global Payroll
Document Name
Release 11
Oracle Global Human Navigate to the Oracle Help Center > Cloud > Applications
Resources Cloud Implementing Tab (next to Get Started) > Global Human Resources >
Global Payroll (Release 11) Release 11 > Books (on the left panel)
Oracle Global Human This takes you to all of the documents listed in this chart.
Resources Cloud Using Global
Payroll (Release 11)
Fusion Payroll: How Earnings Navigate to My Oracle Support and in the search field enter
are Paid and Taxed in the Doc ID number.
Supplemental Run vs Regular
Payroll Run? (Doc ID
1997404.1)
General
Document Name Location
Oracle Fusion Applications Help https://Fusionhelp.oracle.com
(external access)
How to Use My Oracle Support Navigate to My Oracle Support and in the search field enter
Hot Topics Email to subscribe to the Doc ID
Fusion US Legislative Product
News (Doc ID 1677334.1)
Oracle Fusion Applications http://docs.oracle.com/cd/E38454_01/nav/hcm.htm
Documentation: Oracle Fusion
Human Capital Management
YouTube Video Playlist Related https://www.youtube.com/playlist?list=PL1ZiAfFIniZclvZFvJ
to Customizing the Fusion udjDYmkhmosK13A
Applications UIs Using Page
Composer
Oracle Fusion Human Capital Navigate to My Oracle Support and in the search field enter
Management HCM Extract for the Doc ID
Release 8 and Release 9 (Doc
ID 1960148.1)
12
Database Items for Extracts and Navigate to My Oracle Support and in the search field enter
Formulas in Oracle Fusion HCM the Doc ID
(Doc ID 1565118.1)
Oracle Fusion Payroll Batch Navigate to My Oracle Support and in the search field enter
Loader User Guide for Release the Doc ID
9 (Doc ID 2030268.1)
Fusion HCM For US Courtesy Navigate to My Oracle Support and in the search field enter
Tax Users Guide (Doc ID the Doc ID
2138998.1)
13
Effective Dates
In Fusion, many objects are date-effective objects, which is an object with a change history. Customers can
retrieve objects as of a current, past, or future date. When searching for a date-effective object, you enter an
effective as-of date. The search returns the record with the effective date range that includes the specified
effective as-of date. Special care must be taken when adding, updating, or deleting records that are date-
effective.
14
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
 Product Extension Parameter
 Geographies
 Enterprise Structures
 Legal Addresses
 Legislative Data Groups
 Jurisdictions
 Legal Entities
 Legal Employers and Payroll Statutory Units
 Legal Entity
 Legal Reporting Units
 Contact Details
 Registrations
 HCM Information
 Calculation Cards
 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.
15
2. Select Setup and Maintenance from the Navigator.
3. On the Implementation Projects tab, click Create.
16
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.
This parent project contains all the tasks needed to set up HCM organizational structures.
8. Click Save and Open Project.
17
Product Extension Parameter

Use the Manage Features by Country or Territory task to select the correct product for each of your legislations
and ensure that the appropriate features work correctly in your implementation. Refer to the “Selecting Country
Extensions: Critical Choices” application help topic in the Help Portal for information on how these settings
impact the functions of payroll related features.
Valid values for the selected extension parameter are:
 Human Resources or None (this is the default)
 Payroll
 Payroll Interface
Address Validation
For SaaS customers, address validation is included for all product extensions. For the Payroll and Payroll
Interface products, address validation is enforced automatically. You must run the Load Geographies process for
all product extensions using address validation. Run this process frequently, as geographies can be added at
any time.
For On-Premise and On-Demand customers, address validation is included with the Payroll product only. For
other products, customers must acquire a Vertex license separately in order to get the functionality.
If the product setting is set to one of the payroll values, an Employee Withholding Certificate tax card is
automatically created for an employee when their payroll relationship is created. An association to a tax reporting
unit (TRU) is also created automatically for the payroll product settings if the TRU was specified at time of hire.
After any upgrade, the Product Extension parameter is set to null, and the Implementation Team must reset it
before you can perform any transactional actions, such as running payroll, new hires, setting up elements, and so
on.
Oracle strongly recommends you enable address validation for the HR product extension. Doing so makes it
much easier to transition to the Payroll or Payroll Interface products.
Note:
If address validation has not been enabled then care must be taken when switching product extensions, as
any address that was previously defined may be missing required values, such as county and tax district.
There is also the possibility of invalid address combinations, such as mismatched city and ZIP Code
combinations.
An employee must have a valid address in order for them to receive their tax card and to ensure the accuracy of
their tax calculations. You must revalidate the address data prior to using any payroll features if you have:
 Switched the product setting from “Human Resources or None” to “Payroll”
 Not turned on and address validation was not turned on previously
Refer to the following document on Oracle Support for additional information:
Fusion Payroll: Types of License In Fusion Payroll (Doc ID 1611941.1)
Address Style and Settings

Refer to the “Changing Address Style and Address Validation Settings: Critical Choices” online help topic in the
Help Portal.
To check and set the product extension:
1. Search for and start the Manage Features by Country or Territory task.
18
2. Check the Selected Extension for the United States legislation to ensure the proper setting.
3. Make any changes, if needed, and click Save.
4. Click Done.
Geographies
Geocodes are used for:
 Address validation
 Regional taxation
 Geography-based business processes
The US geography information is provided by Vertex or another third-party source.
Loading Geographies
This process is necessary to maintain geography data changes from Vertex in the Fusion application. This task
is required for both HR-only (if using address validation) and Payroll implementations. Vertex publishes monthly
updated files that contain geography data changes (ORAMAST.txt file). For SaaS customers, Oracle Product
Services installs the files. Saas customers automatically receive a notification when the file is installed, and they
can click on the link in the notification to get the latest Vertex tax guide. 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.
Once the files are installed, all customers (including SaaS) must run the processes to update their geography
data. You must run this process as part of the initial setup for the implementation project as well as upon a
monthly basis.
To load US geographies:
19
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.
20
2. On the Manage Geographies page, select US and click Search. The predefined entry for United States
displays.
3. Click on the “Hierarchy Defined” checkmark on the United States line, or select Manage Geography
Hierarchy from the Actions menu. This displays the primary and alternate names for all US geographies.
See section “Configuring Geographies to Diplay a Two Character State” below if you want to only display the
two letter state abbreviation.
Select a state’s link to view its primary and alternate names and codes. When you load the state
geographies, they include both the 2-character state abbreviations and the full state names.
4. Click Done to return to your search results.
5. Select the green checkmark for each type of geography data you want to verify.
 Address Cleansing Defined
This feature is not used by HCM. Refer to “Defining Address Cleansing: Explained” in the Help Portal.
 Structure Defined
21
 Hierarchy Defined
 Validation Defined
6. If a locale is missing (such as a city or county), you can resolve this by:
 If no local taxes are associated with the missing locale, you can create a new entry in the geography
table.
22
 If there is a local tax associated for the missing locale, you must ensure that you have the correct
geocode from Vertex, otherwise you must wait for a Vertex update to populate the missing locale. See
“Manually Adding a Geography” steps below.
Configuring State Display Properties

Follow these steps to diplay a two character state name in place of the full state name.
1. Select Manage Geographies in the implementation project checklist.
2. On the Manage Geographies page, select US and click Search. The predefined entry for United States
displays.
3. Click on the “Hierarchy Defined” checkmark on the United States line, or select Manage Geography
Hierarchy from the Actions menu. This displays the primary and alternate names for all US geographies.
4. Select a state’s link to view its primary and alternate names and codes. Ensure the proper name is marked
as primary.
When you load the state geographies, they include both the 2-character state abbreviations and the full state
names.
5. If you do not want to see the full state name in the State list of values, and no existing address data has been
created using the full state name, delete the row with the full state name from the Primary and Alternate
Names table.
Running the Load Geography Information and Load Payroll Tax Information Processes
Once Oracle Products Services Team has installed the files, all customers (including SaaS) must run the
following processes to update their geography data and tax data:
 Load Geography Information
 Load Payroll Tax Information
Load Payroll Tax Information

The Load Payroll Tax Information for US process is necessary to maintain tax data changes from Vertex in the
Oracle Fusion application. Vertex publishes monthly updates that contain tax data changes (QFPT.dat file). For
SaaS customers, Oracle Product Services installs the files. 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.
Once the files are installed, all customers (including SaaS) must run the Load Payroll Tax Information for US
process to update their tax data. You must run this process as part of the initial setup for the implementation
project as well as upon a monthly basis.
You have two options for running this task:
23
 From FSM, select Define Payroll > Define Earning and Deduction Definitions
 From the Regulatory and Tax Reporting work area
When running this task, populate the parameters as follows:
Field Name Notes
Data Location Specify the location name for the file to be used only
if it is different from the default location, as defined in
the ESS configuration file. This configuration file
contains the location of the Vertex ISAM libraries.
Allow Upload of Older Specify whether to allow an older version of the data
Version file to be uploaded. Default setting is No.
Geographic Category Run for Federal and State each month. City, County
and School District may be run less frequently than
monthly and may take more time to run. If running it
monthly, schedule it to run after hours.
Defining 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
Note:
Do not use “No Style”.
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.
24
Note:
Do not change the Tax Validation and Geography Validation predefined settings. Oracle Fusion HCM
applications do not use this functionality.
3. Click Save and Close.
Viewing Geocodes for a Geography

A geocode is a 9-digit code used to identify the legal jurisdiction. The first two digits represent the state, the next
three digits represent the county, and the last four represent the city. Leading zeroes are not included. This data
is created as part of the Load Geographies process. To view the geocode for a particular geography, follow
these steps:
1. Start the Manage Geographies task in FSM.
2. Perform a search with United States as the country name.
3. Select United States in the search results.
4. Select Manage Geography Hierarchy from the Actions menu.
5. Double-click the appropriate geography name to see the tax geography code.
Manually Adding a Geography

In the rare cases where a geography is missing, you can manually add it. However, before doing so, run the
Load Geography for US process to ensure it hasn’t already been addressed by a Vertex update.
The following example shows how to add the city of Waelder in Bastrop county, Texas to your geography
information. You can use similar steps to add other geographies, such as a county or ZIP Code.
1. Start the Manage Geographies task in FSM.
3. Highlight the United States line in the search results.
4. Select Manage Geography Hierarchy from the Actions menu.
5. Expand the Texas state node to view the list of counties.
6. Expand the Bastrop county node to view the list of cities.
7. Verify that Waelder is not included in the list.
8. Select the Bastrop county row in the hierarchy, and click Create. The Create City page displays.
25
9. In the Primary and Alternative Names section, click Add, or enter the data on the blank line.
10. Specify values for the following fields:
Field Name Notes
Name Enter Waelder as the city name.
Data Provider Leave the default setting.
Language Leave the default setting.
11. Click Save.
12. In the Primary and Alternative Codes section, click Add or enter the data on the blank line.
Field Name Notes
Code Enter geocode 44-21-6195.
Note:
The geocode you provide must be unique within the
county and state.
Code Type Select “Tax geography code”.
14. In the Primary and Alternative Codes section, click Add.
Field Name Notes
Code Enter Waelder.
Code Type Select Primary City.
26

17. Select the Waelder city row in the hierarchy, and click Create. The Create Postal Code page displays.
18. In the Primary and Alternative Names section, click Add, or enter the data on the blank line.
19. Specify valuesfor the following fields:
Field Name Notes
Name 78959
20. Click Save.
21. In the Primary and Alternative Codes section, click Add or enter the data on the blank line.
Field Name Notes
Code 78959
Code Type Select “FIPS Code”.
23. If needed, continue adding more zip codes.
24. Save and close when complete.
Changing the Address Field Display Sequence

To simplify data entry for addresses, you may want to change the field sequence so that users enter the ZIP
Code before the city, state, and county. This enables the application to derive subordinate values, such as city
and state, based on the ZIP Code.
To change the display sequence:
1. Start the Manage Address Formats task in FSM.
3. Select United States in the search results.
4. Select the proper address format to modify in the search results, and click Edit.
5. Starting at the bottom with the country field, update the line number to be one greater than the current line
number.
27
For example: Assign Country to line 8, County to line 7, and so on.

6. Click Save after each line number update.
7. Update each line up to ZIP Code. Retain ZIP Code on line 4.
8. Change the position to 1, and click Save.
Note:
If you are a Payroll or Payroll Interface customer, or a HR-only customer using address validation, do not
disable the Tax District field. The Tax District field identifies townships and other special taxing districts.
When you enter the ZIP Code for an address, and Vertex populates the city, state, and county (or you
select them), you can select the appropriate Tax District from the list of values. For example:
Rosewood, OH, 43070 would belong to the Adams Township:
28
Enterprise Structures
You can now begin the process of defining enterprise structures. All setup tasks are located in the
implementation project task list under Workforce Deployment > Define Common Applications Configuration for
Human Capital Management > Define Enterprise Structures for Human Capital Management:
Legal 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.
29
3. Define your addresses as needed.

Legislative Data Groups

An 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
30
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.
The Create Legal Jurisdiction page contains the following regions:
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.
Registration Code Assignment: For a given jurisdiction, includes fields that allow the user to select a specific
registration code to display when creating legal entities and legal reporting units (LRUs).
Legal Functions: Includes fields that allow 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 Used for federal income tax, federal
Federal Tax States unemployment tax, Social Security, and
Medicare.
<Territory> Income Tax State Used for all states with an income tax. One
Income Tax legal jurisdiction for each state with an
income tax is created.
<Territory> Unemployment State Used for all states with an unemployment
Unemployment Insurance Tax insurance tax. One legal jurisdiction for
Insurance each state with an unemployment tax is
created.
<Territory> Disability Insurance State Used for all states with a disability insurance
Disability Tax tax. One legal jurisdiction for each state with
Insurance a disability tax is created.
31
Viewing Jurisdictions
To view these predefined jurisdictions:
1. Navigate to Setup and Maintenance.
2. Select Go to Task for the Manage Legal Jurisdictions task in the implementation project task list.
3. On the Manage Legal Jurisdictions page, select United States in the Territory field, and click Search.
4. Select the name of the jurisdiction in the Search Results to display the Edit Legal Jurisdictions page.
32
Note:
The US localization does not provide any predefined jurisdictions for local taxes. You must first create the local
jurisdiction and then create the local tax registration, using the local tax legislative category and local jurisdiction.
Local tax registrations are not currently used for any tax filing reports or processes. However,you can chose to
create them if desired.
When you create new local jurisdictions, there may be cases where the territory name appears multiple times in
the list of values. To help identify the correct entry, use the Advanced button and select Add Fields. Use the
first Name field to enter the country (United States), and use the second Name field to enter the state code (such
as CA, AL, or GA), and use the third Name field to enter the county name. Entries into these fields help narrow
the list of entries.
33
Creating Jurisdictions for Local Taxes

You may need to create a local tax jurisdiction if you are withholding for specific local taxes, such as cities and
counties. You must create this jurisdication before you can create a registration for that local. To create local tax
jurisdictions:
1. Navigate to Setup and Maintenance.
34
2. Select Go to Task for the Manage Legal Jurisdictions task in the implementation project task list.
3. Click Create. Refer to the screen shot under Viewing Jurisdictions for an example of how the fields appear.
4. On the Create Legal Jurisdiction page, enter a name.
5. Select a territory, such as United States.
6. Select the Local Tax legislative category.
7. Select No in Identifying.
8. Select Legal Entity Registration Number in the Legal Entity Registration Code field.
9. Select Legal Reporting Unit Registration Number in the Legal Reporting Unit Registration Code field.
Legal Entities
A legal entity is an entity unequivocally identified and given rights and responsibilities under commercial law,
through registration with the territory’s appropriate authority. Legal entities have the responsibility to account for
themselves (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 Human Capital Management recognizes different types of legal entities:
35
 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

An 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 an LRU is to be used for tax reporting purposes, then it must be configured as a 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 employer’s:
 US federal employer identification number (FEIN)
 State employer identification number (EIN)
 Registration details
This captures the FEIN, not the TRU itself.
 Statutory registered name
If there are multiple TRUs under one PSU, the amounts calculated towards maximum wage and tax limits are
recognized across all TRUs within that PSU.
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
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 HCM for the US:
36
 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

Before you define any legal entities, you must have already defined any associated legal addresses through the
Manage Legal Addresses task.
To define legal entities:
1. Select Manage Legal Entities in the implementation project task list.
37
2. Click Create to display the Create Legal Entity page.
3. If you are identifying this legal entity as a PSU:

 If you have not yet defined your US LDG, the application automatically creates the LDG for you and
associates it with the PSU.
 If you have already defined a US LDG, you must manually associate it with the PSU. Refer to Identifying the
LDG below for instructions.
4. If you do not designate this legal entity as a PSU, you can assign an existing PSU to it by selecting one from
the Payroll Statutory Unit field.
5. Provide any other required information.
Identifying the LDG

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

4. Select the PSU tab. By default, general information for the PSU is displayed, including the LDG. If it has not
automatically been associated, you can click on the drop-down to find the appropriate LDG to associate.
Additional Reporting Information for Legal Employers and PSUs

Additional information about legal employers and PSUs are required for:
 EEO
 VETS
 New Hire Reporting
 Payroll processing
39
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.
Click edit to correct or update the details.
40
6. Click the Federal link.
7. In the EEO Reporting Rules section, specify the following values:
41
Field Name Notes

Affiliated with Enterprise Select Yes to indicate whether your entire company
of 100 Employees or employs more than 100 or more employees.
More 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 Select Yes to indicate whether your company
employees in pay period employs 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.
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.
Note:
The TRU you specify here requires additional EEO and VETS reporting information. Use the Manage Legal
Reporting Unit HCM Information task to set these values for the TRU in the EEO and VETS Reporting Rules
region. Refer to the HCM Information section for instructions.
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.
Note:
This field is not used for EEO-1 reporting.
Establishment Employer Select Multiple if you are a multi-establishment
Type employer.
Select Single if you are a single establishment
employer.
42
11. In the United States Reporting Entity Data section, identify each legal employer as either a parent or child.
The EEO-1 and VETS-4212 report processes use these fields to group legal employers for reporting. You
can group legal employers if you want the child legal employer head count to be included in the parent legal
employer’s report.
Field Name Notes
Parent Legal Employer Select Yes if legal employer is a parent legal employer.
Select No if you want the headcount to be included in the
parent legal employer’s report.
Note:
Although the default value displays as Yes, the application
does not automatically uptake this value. To ensure proper
reporting results, you must reselect Yes (if applicable)
through the Edit > Correction mode.
Proxy Legal Employer Select a parent legal employer if you have selected No in
the Parent Legal Employer field.
12. In the EEO and VETS Assignment Category section, select the assignment categories you want excluded
from the EEO-1 report.
If you set this value for a parent legal employer, its child legal employers automatically inherit the value as
well.
13. If the legal entity is also a PSU, select the Payroll Statutory Unit tab.
14. Enter the Fiscal Year Start.

15. 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.
43
16. 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 Calculation Cards

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 was titled Manage Legal Entity Deduction Records prior to Release 8.
Creating the Calculation Card

To create the calculation card:
1. Select the Manage Legal Entity Calculation Cards task.
2. On the Payroll Statutory Unit page, click Create:
44
3. On the Create Calculation Card page, provide the effective date and select Calculation Rules for Tax
Reporting and Payroll Statutory Unit.
4. Click Continue.
Creating Federal Tax Rules

To enter federal income tax (FIT) calculation rules for the card:
1. When creating or editing the card, select the appropriate row under Calculation Components.
2. Enter the appropriate data in the Calculation Component Details section, including the employer self-
adjustment method, if applicable.
3. Repeat to add calculation rules for Social Security, Medicare, and federal unemployment tax (FUTA).
4. Click Save.
Creating Regional Calculation Rules

To create regional calculation rules for the card:
1. When creating or editing the card, click the Regional link in the Calculation Card Overview section.
2. Under the Actions menu, select Create.
45
3. Select the appropriate state, and click OK.
4. Select State Unemployment in the Calculation Components table.

5. In the Calculation Component Details tab of the State Income Tax: Details section, click Add Row.
6. Select State Unemployment Organization Information, and click OK.
7. Select the self-adjustment method.
46
8. To define state unemployment (SUI) employer experience rates for your PSU, select the Enterable
Calculation Values on Calculation Cards tab and click Create.
The rate you enter is applied to all TRUs. To define different rates for different TRUs, enter the experience
rate on the calculation card at the LRU-level. See the Calculation Cards section for detailed steps.
9. Repeat these steps to enter the self-adjustment method for state disability.
10. To define courtesy tax withholding rules refer to the “Oracle Fusion HRMS US: Courtesy Tax Implementation”
guide MOS Doc ID: 2138998.1. Note: This configuration can also be done at the LRU level.
Legal Reporting Units

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 entity’s name.
To create an LRU:
1. Select Define Legal Reporting Units for Human Capital Management in the task list.
47
2. Select Manage Legal Reporting Unit in the implementation project task list.
3. On the Scope Selection window, select Create New and click 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.
48
4. To create a second LRU for this legal entity, enter the required information on the Create Legal Reporting
Unit page.
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.
49
3. On the Select Scope page, select the Search Legal Reporting Units option and click Apply and Go to Task.
4. Highlight the LRU from the list, and click Contact.
5. On the Manage Contacts page, click Create Contact.
50
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.
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 person’s area code.
Phone Specify the contact person’s phone number.
Extension Specify the contact person’s 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:
51
Contact Point Type Select E-mail.

Purpose Select Work.
E-Mail Format Select the contact person’s email format.
E-Mail Specify the contact person’s 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.
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
States 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.
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.
52
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.
Note: To ensure your payroll reports, such as employee W-2s and Multiple Worksite report, are populated with
correct and complete information, you must perform configuration actions for your federal and state registrations
at the LRU level. Ensure the following fields are populated for each TRU:
Jurisdiction Field Name Description
United States Federal Tax EIN or TIN Employer’s federal EIN.
<State> Income Tax Legal Reporting Employer’s state EIN.
Unit Registration
Number
<State> Legal Reporting Employer’s state unemployment
53
Unemployment Insurance Unit Registration account number.

Number
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
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 and Reporting
Establishment check boxes based on the following:
License Tax Reporting Unit Reporting Establishment
Payroll Required Optional
Nonpayroll Required If you have multiple LRUs, selection is
required for each.
If you have a single LRU, selection is
optional, but you must associate the TRU to a
legal employer at the legal entity level. Use
the “TRU for the New Hire Report” field in the
Manage Legal Entity HCM Information task.
54
You must identify the LRU as a TRU in order to pay employees and as a TRU and reporting establishment
for nonpayroll customers in order for the EEO-1 statutory report process to pick employees for reporting.
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.
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.
Note:
The list of states appears on left the side. If there are no data capture fields needed for that state at the PSU
or TRU level, the state does not appear in the list. The majority of fields are captured at the TRU level. If
there are fields at TRU level and NOT at the PSU level, you will still see the state in the list for the PSU.
55
7. In the Third Party Interfaces section, enter the following value:

Field Name Notes
Client Identifier Used by the Third-Party Tax Filing Interface and
Third-Party Involuntary Payment 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.
Branch Identifier Used by the Third-Party Involuntary Payment
Interface. Refer to the Oracle Fusion HRMS (US):
Third-Party Involuntary Payments Interface (Doc ID
2043941.1) white paper on MOS for necessary
setups for the Involuntary Payment Interfaces.
8. For the TRU you identified as the default for New Hire reporting, specify the following in the EEO and VETS
Reporting Rules section:
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.
Note:
This field is not used for EEO reporting.
Establishment Employer Select Multiple if you are a multi-establishment
Type employer.
Select Single if you are a single establishment
employer.
Headquarters Select your headquarters location from the LOV.
56
Establishment
Note:
The application ignores values set for any other TRU.
9. In the EEO Reporting Information section, enter the following values:
Field Name Notes
Affiliated with Enterprise Select Yes to indicate that your entire company
of 100 Employees or employs 100 or more employees.
More 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
than 100 Employees more 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.
Reporting Establishments
A reporting establishment is an organization used for HR statutory reporting.
For nonpayroll implementations, if you have multiple LRUs, each must be a reporting establishment. If you have
a single LRU, selection is optional, but you must associate the TRU to a legal employer at the legal entity level.
Use the “TRU for the New Hire Report” field in the Manage Legal Entity HCM Information task.
For payroll implementations, selection is optional.
You can identify a TRU as a reporting establishment during LRU definition, as described in the previous section.
To identify an existing TRU as a reporting establishment:
1. Sign in to the Oracle Fusion application using an Application Implementation Consultant role that has
privileges to create and modify all organizational structures.
57
2. Select Setup and Maintenance from the Navigator.

3. Select Manage Reporting Establishments in the implementation project task list.
4. Click Create.
5. On the Create Reporting Establishment page, indicate if you want to select an existing TRU to define as a
reporting establishment or create a new one.
6. In the Reporting Establishment Description section, provide the required information.
7. Click Next to provide additional details, and then review and submit it.
58
Calculation Cards
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. Entering this
data for the LRU overrides any data entered at the PSU level.
Refer to the Legal Entity Calculation Cards section for steps to create the card and enter the federal tax rules.
State Unemployment Insurance Rate

In order to calculate the employer’s state unemployment liability, you must define the SUI rate.
Specifying the SUI Rate
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.
59
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.
60
10. Click on the tab at the bottom of the page labled ‘Enter Calculation Value on the Calculation Cards and then
click on the Add. Enter the SUI rate for this LRU in the Rate field.
When you enter a SUI rate for a selected state, the SDI and state income tax (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:
Specify the self-adjust method here.
14. Click Save.
15. Repeat steps 11 through 14 to set the self-adjust method for state unemployment.
Updating the SUI Rate
To update a state’s SUI rate once it already exists:

1. Search for and start the Manage Legal Reporting Unit Calculation Cards task.
2. Select the Calculation Rules for Tax Reporting and Payroll Statutory Unit Calculation Card.
3. Enter the Effective As-of Date for the new rate.
4. Select the state under the Regional Component Group.
5. Select the State Unemployment Calculation Component.
6. Select the Enterable Calculation Values on Calculation Cards tab in the State Unemployment: Details
section.
7. Select the State Unemployment Employer Experience Rate.
61
8. Click Actions>Edit>Update.
9. Enter the new rate.
10. Click OK.
Business Units
Oracle Fusion HCM for the 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.
Puerto Rico Configuration

The configuration to support the processing and paying of employees working and/or living in the territory of
Puerto Rico is largely the same as with state configurations, with differences in the following areas:
 Legal addresses
 Legal reporting units
 Tax reporting units
 Deduction Elements
Legal Addresses
Users must identify United States as the country when configuring the legal addresses through the Manage Legal
Address task. This ensures that Vertex loads the correct data for Puerto Rico.
Legal Reporting Units

Users must select United States as the territory when defining the legal reporting units in FSM. This is needed in
order to enter the FEIN using United States Federal Tax jurisdiction.
Note:
The jurisdictions required for the state-level registrations are available for Puerto Rico.
62
You must also create separate legal reporting units for Puerto Rican workers. Do not assign both US and Puerto
Rican workers to the same TRUs.
Tax Reporting Units

To identify that the TRU belongs to a territory, an EFF at the federal level must be populated to designate what
territory it is associated to. The field is located under the Federal rules for Organization Information EFF. Start
the Manage Legal Reporting Unit HCM Information task, and click Federal. The segment is Territory Rules and
the field is Territory Identifier.
Note:
Leave this field blank for TRUs not associated with US territories.
63
Deduction Elements
To identify that deduction elements belong to Puerto Rico territory, create a State input value and populate it in
the results element with a value of 72. For this configuration, select a Reference of “State” under the Default
Entry Values and Validation section for the results element. Define the State input value with a display sequence
of 1. You must modify your fast formula and status processing rules to ensure the correct value is passed to the
results element.
Note:
This is only necessary for deduction elements that are used to feed these specific Puerto Rico W2 balances:
 W2 Territory Charitable Contributions
 W2 Territory Government Retirement Fund
 W2 Territory Government Employee Savings Plan
 W2 Territory 401k
64
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.
Managing Workforce Structures

Maintenance of workforce structures can be performed through FSM.
When you select Workforce Structures in the Navigator, the following page is displayed:
Use this work area to manage:

 Positions
 Jobs
 Grades
 Departments
 Locations
Locations
Locations identify:
 Where business is conducted, including the physical location of a workforce structure
 Workers’ physical work locations
65
 Other areas of interest to the business

To create or manage locations:
1. Select Manage Locations in the implementation project task list.
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.
66
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,
Description such as 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 These fields are informational only.
1, 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
Reporting the 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
67
Reporting Name Enter the location reporting name.

Hiring Location Enter the hiring location number.
Number
Maximum Specify the greatest number of employees currently hired
Number of during the 12-month period covered by this report.
Employees
Minimum Specify the fewest number of employees currently hired
Number of during the 12-month reporting period.
Employees
Note:
The Run VETS-4212 Establishment Electronic Report process uses the values you specify in the Maximum
and Minimum Number of Employees fields for employee counts. If you leave these fields blank, the process
derives the employee counts based on the reporting period start and end dates.
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 3, 4, or 5-digit number, depending on the state.
Number Currently this is required for New Mexico, Massachusetts,
Minnesota, Iowa, and Michigan.
11. For locations in Pennsylvania, specify their Political Sub Division code (PSD). This value defaults in the
Work PSD Code field on the Residency Certificate of every employee assigned to that location.
12. Do not specify a value in the Non-Resident EIT Rate for Pennsylvania Work Location field.
68
13. 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, use the following
configuration:
Field Name Value
HR Reporting Location No
HR Reporting Proxy Select reporting location
14. Click Submit.
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.
69
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.
To create grades:
1. Select Manage Grades in the implementation project task list.
2. Click Create.
3. Define the information required for this grade.
70
4. Click Next to define the order of progression between grades.
5. Click Next to define grade rates.
Grade rates can be used to define pay values for grades in an LDG (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.
71
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.
72
Banking Setup
An HR-only customer may want to add payee banking information even if payroll is not being processed by
Oracle Fusion Global Payroll. 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.
Configuring Employee Options for Bank Details

Employees can enter their bank details using the Manage Personal Payment Methods task through their
employee self-service. Use the CE_USE_EXISTING_BANK_BRANCH profile option to define what settings are
available to them.
To define the fields the employees can use to configure their bank details:
1. Start the Manage Cash Management Profile Options task.
2. Search for the CE_USE_EXISTING_BANK_BRANCH profile option.
3. In the search results, select the profile option.

4. In the Profile Values region, select the Site profile level.
5. Set the profile value:
Profile Value Description
Yes Employees select their banks and branches from a predefined list.
You must have previously defined this list through either the Create Bank and
Create Bank Branch tasks or the mass upload process (see next sections).
73
No Employees can set their bank and branch details through free text fields.
Defining Banks
To define banks:
1. Sign in to the application with a role that has cash manager privileges, such as CASH_MANAGER.
2. Select Manage Banks in the implementation project task list.
3. Click Create.
4. On the Create Bank page, provide the necessary information.
Defining Bank Branches

To define branches for the banks you created:
1. Select Manage Bank Branches in the implementation project task list.
74
2. Click Create.
3. On the Create Bank Branch page, provide the necessary information.
Defining 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.
75
2. Click Create.
3. On the Create Bank Branch page, provide the required information.
4. If you want to use this bank account for processing payments related to payroll, select the Payroll option in
the Account Use field.
Defining 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.
76
4. On the Create Organization Payment Method page, enter the required information:
Name Enter the name of this OPM.
Payment Type Select the payment type for this OPM.
You must create a separate OPM for domestic and
international payments.
Use the Direct Deposit payment type for domestic direct
deposits and the International Transfer payment type for
international payments.
Two EFT templates are available:
 PPD for US Payments
 IAT for international payments
Note:
Prior to Release 12, the Direct Deposit payment type is
called NACHA.
Currency Select US Dollar.
Prenotification required Prenotification is the process of submitting a 0 USD
transaction in order to verify an electronic transfer’s 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 Direct Deposit or International Transfer 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 Determines whether the system
File 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
Reference Identification employer by an external authority,
such as their IRS tax ID or D-U-N-S
77
number.
Company Name Immediate Originator Identifies the company name of the
Name originator.
Payment sources associate bank accounts and other sources of funds with the OPMs. Each organization
payment method in use must have at least one valid payment source.
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 Direct Deposit employee direct
deposit.
8. Enter required information, and click Submit.
Configuring Prenotes
Prenotes are Automated Clearing House (ACH) prenotifications. They are 0 USD ACH entries that you send at
least 10 banking days prior to the first live payroll credit sent. Under NACHA operating rules (also known as ACH
rules), the prenote validates the routing number and account number of the receiving bank or credit union.
Specify the following prenotification rules on OPMs of the Direct Deposit payment type:

Prenotification Designates whether the prenotification process is
Required required for employees.
Prenotification Amount Default value for this field is 0.
Prenotification Days Number of days required for a prenotification wait
period. The employee is paid by check until the waiting
period is completed. For example, if the prenote wait
period is 10 days and running a weekly payroll,
depending on the timing employees might receive two
paychecks before direct deposit starts.
If a prenote is required for the OPM, the system sends a prenote entry with 0 USD in the direct deposit file (PPD)
for all new hires. For an employee’s checking account, the prenotification transaction contains the transaction
code of 23 in the entry detail record. For the employee’s saving account, the prenotification transaction contains
the transaction code of 33.
Note:
The prenotification process is currently only available for new hires. You cannot issue prenotes for changes
made to accounts for existing employees.
78
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 HCM for the 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 Add Row.
79
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 to 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.
2. Click Create.
3. Select the LDG for this payroll definition, and click Continue.
4. On the Create Payroll page, enter the required information.
5. Select a consolidation group.
6. Select the Premium Calculation rate for overtime calculation.
7. Select a time definition.
This is used to define the starting date and length of the overtime period used in the calculation of overtime.
8. Click Add Row in the Valid Payment Methods section, and add one or more OPMs that are valid for this
payroll.
80
You can select any OPM defined for the LDG that is linked to this payroll definition.
The default payment method is check.
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.
Note:
The US does not use the following fields in the Calculation Defaults section:
 Use Information Hours From
 Threshold Basis
81
Elements and Element Templates

You create elements through predefined element templates, which provide you with an intuitive user interface
and help you 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.
Note:
When creating an overtime earnings element, do not use the name “Overtime” for any element name or
reporting name. "Overtime” is a reserved term, and including it in user-defined elements interferes with
balance initializations.
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 an 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.
82
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.
The “Process and pay element separately or with other earnings elements” question impacts how the new
element is taxed based on the type of run (regular or supplemental):
 For regular runs, when you select “Process and pay with other earnings”, the element uses regular tax
rates.
 When you select one of the process separately options, the element uses supplemental tax rates. For
supplemental runs, earnings are always taxed at the supplemental rate.
For additional information on the difference between Regular and Supplemental payroll runs and how
supplemental earnings are taxed when processed in Regular vs. Supplemental payroll runs, please refer to
the MOS document, Fusion Payroll: How Earnings are Paid and Taxed in Supplemental Run vs Regular
Payroll Run? (Doc ID 1997404.1).
6. Click Next.
83
7. For Periodicity Conversion Rule, use the following chart:

Primary Element Generated from
Secondary Classification
Classification Template
Standard Rate Calculates the annual rate using the input To convert a weekly amount to a
Annualized periodicity, and converts the amount to an semimonthly periodicity, the
output periodicity and rate. formula:
Uses default values to calculate the 1. Multiplies the weekly amount
annual rate, such as 2080 hours or 260 by 52.
84
working days. 2. Divides the result by 24.

Standard Rate Calculates the daily rate using the input To convert an annual amount to
Daily periodicity, and converts the amount to an daily periodicity, the formula:
output periodicity and rate. 1. Divides the annual amount by
Uses a default value to calculate the daily 365.
rate, such as 260 working days a year. 2. Multiplies the result by the
number of days in the payroll
period.
Standard Uses the employee’s standard working Employee works 40 hours a week
Working Hours hours to convert the monetary value and with a monthly salary of 1000
Rate their working hours to an annual value USD:
Annualized before calculating the rate.
((1000*12)/(40.00*52) = 5.77 an
hour
Assignment Uses the employee’s working hours to Employee works 40 hours a
Working Hours convert the monetary value and their week, with a 37.5 standard
Rate working hours to an annual value before working hours a week, and a
Annualized calculating the rate. monthly salary of 1000 USD:
((1000*12)/(37.50*52) = 6.15 an
hour
Periodic Work Uses the employee’s work schedule for Employee has a monthly salary
Schedule Rate the payroll period for daily and hourly of 1000 USD and is assigned a
Annualized conversions. monthly payroll. The formula
checks the work schedule details
for the month.
For a daily conversion:
1000 a month/20 days in the
month = 50
Note:
For compensation calculations
where the employee is not
assigned a payroll, the rate is
calculated using the weekly rate
calculation. The amount is
converted to an annual figure
and divided by the number of
days or hours in that week
based on the work schedule.
8. Complete the rest of the questionnaire.
9. Click Next.
10. Verify the information, and click Submit to create the new element.
85
The Element Summary page provides additional information, such as input values, processing rules, and
eligibility.
86
11. Use the Element Overview panel to navigate through the summary page options.
12. 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).
13. Enter a name in the Element Eligibility Name field, and click Submit.
87
By entering only a name and no eligibility criteria, the element is eligible for all employees.
14. Select an input value in the left panel, and provide additional information such as default values, validation
formulas, and required flag.
15. Click Submit and Done.
16. Repeat this process to create a set of elements to support your business needs.
Costing
Costing is the financial accounting of your payroll costs. It breaks down the costs of a payroll into customer-
defined units (such as a location, division, or project). Costing of payments is a separate post-payments process.
For customers not using Oracle Fusion General Ledger, you can disable the Transfer to Subledger Accounting
task by copying the US Simplified Flow and creating your own flow and removing the task.
Reference the Global Human Resources Cloud Implementing Payroll Costing document and online help for
assistance with defining your costing structure. Refer to “Oracle Fusion Global Payroll: Setup of Information
Elements for Payroll Relationship Level Costing” (Doc ID 2172879.1) on the Oracle Support website for
assistance on creating cost allocation on element eligibility using attributes other than Payroll Statutory Unit and
Relationship Type.
Element Eligibility
You must define element eligibility for the following elements for costing.
Primary Secondary Element Input Value
Classification Classification Generated from
88
Template
Standard All secondary <User Earnings Calculated
Earnings classifications Element> Note:
Results If you also need to cost
hours, you must cost the
appropriate hours input
value in the Results
element.
Supplemental All secondary <User Earnings Calculated
Earnings classifications Element>
Results
Imputed All secondary <User Earnings Calculated
Earnings classifications Element>
Results
Nonpayroll All secondary <User Earnings Calculated
Payment classifications Element>
Results
Pretax Deferred <User Deduction Calculated
Deductions Compensation 401k Element>
Results
Pretax Deferred <User Catchup Deduction
Deductions Compensation 401k Element> Calculated
Catch Up Results
Pretax All other secondary <User Pay Value
Deductions classifications Element>
Results
Employee Tax All secondary <Seeded Tax Calculated
(See the
Employee and
Employer Tax
Elements
section below for
additional
details.)
Employer <User Employer Match
Liabilities Element> Calculated
(specific to Employer
Deferred Match Results
Compensation)
Employer All secondary <User Pay Value
Element>
89
Liabilities classifications Results

Involuntary All secondary <User DeductionsCalculated
Results
Involuntary All secondary <User FeeCalculated
Deductions classification – Element>
Fees Organization
Fee Results
<User
Element>
Person Fee
Results
<User
Element>
Processing Fee
Results
Voluntary All secondary <User Pay Value
Deduction classifications Element>
Results
You must define eligibility for these elements, as it is used to create the element entries.
Additionally, you must define eligibility for the predefined US Taxation element as an open link.
Employee and Employer Tax Elements

You must cost the following predefined employee and employer tax elements:
Tax Element Name Input Value
Family Leave Insurance Employee Tax FLI Tax Calculated
Note:
Family Leave Insurance (FLI) applies to New
Jersey only. This element is the preferred
method to cost FLI taxes, although you can cost
the State Disability Insurance Employee Tax
element instead (listed below). Do not cost both
elements.
Federal Income Tax Tax Calculated
Federal Income Tax Not Taken Tax Calculated
Federal Unemployment Tax Tax Calculated
Head Tax Not Taken Tax Calculated
Medicare Employee Tax Tax Calculated
Medicare Employee Tax Not Taken Tax Calculated
Medicare Employer Tax Tax Calculated
90
Residence City Income Tax Not Taken Tax Calculated

Residence City Tax Tax Calculated
Residence County Income Tax Not Taken Tax Calculated
Residence County Mental Health Tax Tax Calculated
Residence County Tax Tax Calculated
Residence School District Tax Tax Calculated
Residence School Tax Not Taken Tax Calculated
Residence State Income Tax Tax Calculated
Residence State Income Tax Not Taken Tax Calculated
Social Security Employee Tax Tax Calculated
Social Security Employee Tax Not Taken Tax Calculated
Social Security Employer Tax Tax Calculated
State Disability Insurance Employee Tax Tax Calculated, FLI Tax Calculated
Note:
FLI applies to New Jersey only. The Family
Leave Insurance Employee Tax element is the
preferred method to cost FLI taxes (listed
previously), although you can cost this element
instead. Do not cost both elements.
State Disability Insurance Employee Tax Not Tax Calculated
Taken
State Disability Insurance Employer Tax Tax Calculated
State Unemployment Insurance Employee Tax Tax Calculated
State Unemployment Insurance Employee Tax Tax Calculated
Not Taken
State Unemployment Insurance Employer Tax Tax Calculated
Work City Income Tax Not Taken Tax Calculated
Work City Tax Tax Calculated
Work County Income Tax Not Taken Tax Calculated
Work County Mental Health Tax Tax Calculated
Work County School District Tax Tax Calculated
Work County Tax Tax Calculated
Work Head Tax Tax Calculated
Work School Tax Not Taken Tax Calculated
91
Work State Income Tax Tax Calculated

Work State Income Tax Not Taken Tax Calculated
Secondary Element Classifications

Secondary classifications are subsets of the primary classifications. Use them to manage wage basis rules for
deductions and taxes. There could be cases where you need to create a new secondary classification to suit
your business needs.
To create a new secondary classification:
1. Start the Manage Element Classifications task in the Payroll Calculation work area.
2. Enter the appropriate LDG, and click Search.
3. Select the appropriate primary classification in the search results.
4. Select Actions > Edit.
5. In the Secondary Classifications section, select Actions > Create.
6. Enter the new name and start date.
7. Click OK.
8. Create any new wage basis rules as needed. See Creating Wage Basis Rules for details.
Domestic Partner Secondary Classifications

The Imputed Earnings primary classification includes two secondary classifications related to domestic partners:
 Domestic Partner Dependent: For nontaxable benefits
 Domestic Partner Nondependent: For taxable benefits
When defining elements of these types, you must select the secondary classification that best meets your
requirements.
Retroactive Elements
Retroactive elements are automatically created when you select Yes to the question: Is this element subject to
retroactive changes? The element template creates these elements nonrecurring with the same attribution of the
base element with a couple of exceptions. If you selected Process Separately or Pay Separately, the template
creates input values on the retroactive element; however, the input value default is set to N on the retroactive
element. You can override this value at the element level, element entry level, or element eligibility level if
desired.
Salary Basis
Best practice for Payroll Implementation projects is to setup salary basis and payrolls before hiring employees. A
salary basis allows employers to:
 Establish the period of time for which an employee’s 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.
92
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.
93
Gross-up Earnings
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 Bonus
Classification
Processing Type Nonrecurring
Employment Level Assignment level
Process the element Yes
only once in each
payroll period?
Use this element to Yes
calculate a gross
amount from a
specified net amount?
Process and pay Process Separately but pay with other earnings
element 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.
94
3. Click Submit and then Done.

4. To ensure the FIT deduction is calculated at 39.6% (the highest tax bracket), override the Supplemental Rate
percentage on the employee’s 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.
95
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.
96
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 employee’s FIT withheld is calculated at
39.6% of gross wages:
97
Gross-up Imputed Earnings

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 Bonus
Classification
only once in each
payroll period?
Use this element to Yes
calculate a gross
amount from a
specified net amount?
Process and pay Process Separately but pay with other earnings
element separately or
with other earnings
elements?
3. Click Done.
98
4. To ensure the FIT deduction is calculated at 39.6% (the highest tax bracket), override the Supplemental Rate
percentage on the employee’s Manage Payroll Calculation Information page for the federal employee
withholding certificate.
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.
You must now configure an additional voluntary deduction.
6. Navigate to the Manage Elements task, and define a gross-up deduction element:
99
Field Name Value

Primary Classification Voluntary Deduction
Secondary N/A
Classification
only once in each
payroll 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.
100
10. Click Submit and then Done.

11. To define the element entries for the deduction element:
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.
101
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 Earnings
Oracle Fusion HCM for the US determines the overtime rate according to the overtime 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).
Refer to the Oracle Support Document 1600746.1 - Oracle Fusion HRMS (US): US Overtime Setup white paper
for necessary steps for the overtime set up.
Note:
When creating an overtime earnings element you should not use the name “Overtime” for any element name or
reporting name. "Overtime” is a reserved term, and including it in user-defined elements will interfere with
balance initializations.
Involuntary Deductions
Refer to the Oracle Support Document 1597039.1 - Oracle Fusion HRMS (US): Payroll Involuntary Deductions
white paper for full details on involuntary deductions.
For Release 12, refer to the Oracle Support Document 2238172.1 - Oracle Fusion HRMS (US): Electronic
Income Withholding Orders Processing Guide for full details on e-IWO (Electronic Income Withholding Orders).
Deferred Compensation
Deferred compensation plans allow you to save for retirement on a pretax or after-tax basis. Employees elect to
participate in a plan whereby they can choose one or more deductions from wages on a pretax or after-tax basis.
In most cases, the pretax deferred wages are not subject to federal income tax or state income tax withholding at
the time of deferral. However, they are included as wages subject to Social Security, Medicare, and Federal
Unemployment taxes.
Supported Deferred Compensation Plans

Oracle currently supports the following deferred compensation plans:
 401 (k)
 401 (k) Catch-up
 Roth 401 (k)
 Roth 401 (k) Catch-up
Employer match is also available for these plans.
Contribution Limits
There are maximum contribution limits issued by the federal government. Oracle configures and maintains the
following values in Calculation Value Definitions:
 Deferred Compensation 401k Annual Limit
 Deferred Compensation 401k Catch Up Annual Limit
 Elective Deferral Limit
 Eligible Compensation Annual Limit
Balance and Feed

The percentage deduction deferred compensation calculations use the Deferred Compensation 401K Eligible
Earnings balance. You must feed this balance for your eligible earnings.
102
Wage Basis Rules

Oracle Fusion HCM for the US provides the wage basis rules at the federal and state levels for use in the
taxation of earnings. This includes rules for primary classifications of supplemental earnings, imputed earnings,
and pretax deductions along with the corresponding secondary classifications. It does not provide wage basis
rules for local taxes.
For information on wage basis rules as they relate 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 does not reduce
subject wages. If no check mark is present, then the deduction is not subject to taxation and does reduce
subject wages.
3. Navigate in the tree structure to Regional > Wage Basis Rules > State.
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 in Search region to
filter the data.
Creating Wage Basis Rules

There are no seeded wage basis rules at the local level (city, county, or school). While most local wage basis
rules follow their state wage basis rules, there are a few states where the local wage basis rules differ. 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. In the tree structure, select the Regional node.
To define wage basis rules at the federal level taxes, select the Federal node.
2. Select Related deductions > City Tax > Wage Basis Rules.
3. Select Actions > Create.
103
The Create Wage Basis Rule UI appears.

4. Enter the following information:
Field Name Requirement Mapping
Effective Start Date Required Use either the 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 This configuration most commonly
uses the following:
 Imputed Earnings
 Pretax Deductions
 Supplemental Earnings
Select all secondary Mandatory If you select Yes for Subject to Wage
classifications Basis Rule below, you must select No
here.
Secondary Mandatory If you select No for Subject to Wage
Classification Basis Rule below, you must select an
appropriate secondary classification.
Subject to Wage Basis Mandatory If you select Yes here, you must select
Rule No for Select all secondary
classifications.
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 HCM for the 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, or city that needs updating.
104
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.
10. Create a wage basis rule for Deferred Compensation 401k Catch Up.
You must complete this change for every state, county, city combination for the locales the employer is in for
Ohio.
11. If county taxes are impacted, you must apply the same entries for the state and county combinations for each
appropriate primary classification and 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.
Editing Wage Basis Rules

You may want to change the seeded wage basis rules. For example, the seeded rule for Group Term Life (GTL)
for the applicable federal and state components defaults to a “Not withholdable” rule. You may want to change
this to “Withholdable”.
To edit the predefined wage basis rules:
1. Start the Manage Component Group Rules task, and query your LDG.
2. Select the Federal or Regional component (depending on what you are trying to update).
3. Expand the Federal or Regional folder at the top, and then expand the Related Deductions folder.
4. Navigate to the Wage Basis Rules folder.
5. Select Create from the Actions menu.
6. Enter an effective date.
7. If you are updating the State component, select your appropriate state.
8. Select a primary classification and secondary classification.
9. Deselect the Subject to wage basis rule box, and click Submit. This cancels the seeded rule.
10. Navigate back to the Wage Basis Rules folder.
11. Select Create from the Actions menu.
12. Enter an effective date.
13. If you are updating the State component, select your appropriate state.
14. Select a primary classification and secondary classification.
15. Enable the Subject to wage basis rule option, and click Submit. This creates the new rule.
105
Document Delivery Preferences

You typically define delivery preferences for documents that are delivered periodically from employers to workers,
such as payslips or year-end tax statements. You can select default delivery methods for a document type
(online and paper), and specify other delivery related preferences. Set these preferences using the Manage
Document Types task in the Setup and Maintenance work area.
Person-Level Overrides
You can enable persons to override the delivery preferences for their documents through their Portrait Gallery.
The elections they choose override delivery preferences specified elsewhere for the document type.
Document Delivery Preference Configuration

To set the delivery preferences for any of the HCM documents (such as payslip, W_2, and W_2C):
1. Start the Manage Document Types task.
2. Select the Category Payroll, and click Search.
3. Click Payslip.
4. Under Document Delivery Defaults, select the Delivery Method(s).
5. Repeat these steps if you want to override the enterprise level for W_2 and W_2c.
Note:
The third-party quarterly tax filing process references the enterprise level only if an employee-level override
does not exist for W_2. It does not reference the work structure overrides.
106
Process Configuration Group

When running the Generate Payslips process to generate payslips, you must specify a process configuration
group in the Process Configuration Group field. The process configuration group you select must have the
following parameter set to Y: “XML Data Source For document of records delivery options performance
purposes, determines if XML is derived from the database. Default: Y." This ensures the process properly
publishes the payslip to the Document of Records.
Process Configuration Group for Forms W-2 and 1095-C

To post forms W-2 and 1095-C to the DOR, you must configure a different process configuration group that has
the XML Data Source parameter set to N. This process configuration group must be specified when running the
W-2 employee report in final mode or the 1095-C employee report.
To define the process configuration group:
1. Start the Manage Payroll Process Configuration task.
2. On the Manage Payroll Process Configuration page, click Create under Configuration Groups.
3. On the Create Configuration Group page, provide a name and click Save and Close.
4. Select the configuration group you just created.

5. Under Configuration Group Details, set the value to N for “XML Data Source For document of records
delivery options performance purposes, determines if XML is derived from the database. Default: Y."
107
108
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.
Note:
You can load employee data through file-based loaders instead of direct entry in the application. Refer to the
following documents for additional details:
 Document 1595283.1 (Oracle Fusion Human Capital Management File-Based Loader for Release 7 and
8 for more details on the File Based Loader)
 Document 2030268.1 (Oracle Fusion Payroll Batch Loader User Guide for Release 9)
Configuring Disabilities
Before you can assign disabilities to employees, you must define the specific disability types and statuses
required for your organization’s business needs.
Note:
When using the Manage Person task, you select these values through the Type and Requested
Accommodation Status fields in the Legislative Information region on the Disabilities tab.
Use the Manage Common Lookups task to set the valid entries for the following lookups:
Lookup Field
HRX_US_ADA_TYPE Type
HRX_US_ADA_STATUSES Requested Accommodation Status
Refer to the “Person Lookups: Explained” topic on the Help Portal for a list of other person disability lookups
available from Global Human Resources.
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
3. On the Identification page, provide the following information in the Basic Details section:
109
Hire Date Date of the employee’s 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
Name US.
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.
Also, if you enter the ZIP Code first, the city, state, and county fields are automatically populated.
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.
Note:
Use the Payroll Details section to associate a TRU and payroll with the employee. If you opt not to, this
employee would not automatically receive an Employee Withholding Certificate, and you would have to
create it manually. See Manual Tax Card Creation for more instructions.
11. For nonpayroll implementations, attach your employees to a reporting establishment.

If you do not, when you run the EEO-1 report process , it associates the employee to the TRU identified in
the “TRU for the New Hire Report” field. This field is located in the Manage Legal Entity HCM Information
task.
110
Assigning the employee to a reporting establishment is not required for payroll implementations.
12. 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. Additionally, the US taxation element is automatically added to the employee’s element entry
once the association to the TRU is done. 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 employee’s employment status as pertains to
the New Hire report:
Include in the New Hire Employee is to be included
report in the next run of the New
Hire 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 Employee is not included
Hire report in 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.
Maintaining Person Information

To maintain an employee’s 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.
3. Use the Manage Person tabs to view the complete set of person information.
111
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 employee’s data.
5. Click Submit when finished.
Maintaining Employment Information

To maintain an employee’s employment information:
1. Select Person Management under Workforce Management in the Navigator.
3. Select Manage Employment.
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 employee’s data.
5. Click Submit.
Adding a Second Assignment
To add an additional assignment to an employee’s employment information:

1. Follow steps 1 through 3 under Maintaining Employment Information above.
2. Select Edit > Update.
3. Enter an Effective Start Date (or accept the default).
4. Select Add Assignment.
112
5. Click OK.
6. Enter employment information.

7. Click Next.
8. Enter compensation details.
9. Click Next.
10. Add or delete roles as needed.
11. Click Next.
12. Review the information and click Submit.
13. Click Yes.
You can view and access the new assignment from the Employment Tree. The last assignment added is the one
first displayed in the Manage Employment UI when it is initially accessed. The other assignments may be
accessed using this tree hierarchy.
113
Employee Security: Roles, Duties and Priveleges

Employers can customize their own security and employment roles within Fusion.
Creating Custom Security Roles and Duties

Create custom security roles as needed for specific employees. One duty role to consider assigning is the
Payroll Person Level Administration Duty. This duty role manages individual and group level payroll
administration, including managing costing, payment methods, deductions, element entries, and batch data load.
Refer to the MOS document (Document 1556500.1 - Fusion HCM Security Role Mappings) for additional
information.
Employee Roles Within Portrait Access

Employers creating custom employee roles must ensure they add the View US End of Year Tax Form privilege.
This privilege is attached to the US Employee Portrait Gallery duty role, which grants employees access to the
View End-of-Year Tax Form task.
Smart Navigation
Beginning with Release 11, Smart Navigation is being introduced, which provides quick navigation to all person
related tasks based on the user’s security permissions. All access to “My Portrait” is being replaced with
“Person Spotlight” in Release 13.
114
Employee Management of Document Print Preferences in My Portrait

Employees can update their own document print preferences in Portrait using the Document Delivery action:
1. Select the Personal Information icon at the top of the page.
2. Scroll down to the Document Delivery Preferences section, and select the edit (pencil) icon for the item you
wish to update.
3. Edit choices as needed.
115
Payroll Processing
There are several factors that make up the payroll processing.
Taxation Within Fusion Payroll

Vertex provides all the statutory compliance for the Oracle Fusion Global Payroll engine, but it is important for
you to understand how the payroll process handles US taxation.
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.
Note:
For states that levy school district income taxes, you must manually populate the school district on the
employee withholding certificate. Depending on the state, you enter the school district under either the city or
county node. For resident addresses in a township, you must populate the tax district field on the address
before you can populate the proper school district on the tax card.
Setting Up Automatic Tax 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. This element is automatically
added to employee’s element entry when the association to the Tax Reporting Unit is completed.
Manual Tax Card Creation

There are cases where an employee would not have their tax card automatically created, such as if they were
loaded through the File Based Loader utility.
For these employees, to create an Employee Withholding Certificate:
1. Navigate to the Payroll Calculations work area.
2. Start the Manage Calculation Cards task.
4. Click Create.
5. Enter an appropriate Effective-As-of-Date, and select Employee Withholding Certificate for Name.
6. Enter employee information as appropriate at the Federal level.
7. Click Save.
8. Select the Regional link under the Component Groups tree.
9. Enter employee information as appropriate for the Regional level.
10. Click Save.
11. Select the Associations link under the Component Groups tree.
12. Under Associations, click Create.
13. Select the Tax Reporting Unit, and click OK.
116
14. Click Save. This creates the US Taxation Component and is displayed in the Calculation Component column
after saving.
15. Under Association Details, click Create.
16. Select the Employment Terms or Assignment Number and the Calculation Component created in prior steps,
and click OK.
17. Click Save.
18. Upon tax card association creation, the following fields are autopopulated with default values on the federal-
level employee withholding certificate and should be verified:
 State for Unemployment Calculation
 State for Disability Calculation
 Primary Work Address
Changing the TRU for an Assignment

To change the TRU for a preexisting assignment on the Employee Withholding Certificate:
2. Select Manage Calculation Cards.
4. Click Employee Withholding Certificate.
5. Click Associations under the Component Groups tree.
6. Select the Tax Reporting Unit under Associations for which the assignment currently exists.
If the association for the TRU for the new assignment does not already exist, create it now.
7. Select the assignment number to change under Association Details.
8. Click Edit>Update.
9. Select the Calculation Component for the new TRU.
This end dates the record for the assignment associated with the previous TRU and creates a new record for
the new TRU.
Wage Accumulation
On the Employee Withholding Certificate, each tax component group (Federal and Regional) has a Withholding
Exemption section. To exempt an employee from tax withholding or wage accumulation, mark the following as
Yes:
Field Name Result
Exempt from Does not withhold this tax but does accumulate wages for
(component) Income the component.
Tax
Exempt from Wage Does not withhold tax, and does not accumulate wages for
Accumulation the component.
If you mark both as exempt, the payroll process ignores the Exempt from Wage Accumulation setting.
Manage Tax Withholding in My Portrait

Employees can update their own withholding information in Portrait using the Manage Tax Withholding action:
1. Select Manage Tax Withholding action in the left panel under Actions.
117
This displays the Employee Withholding Certificate page.
2. Click Edit. This is available for both the federal and state level.
118
When you access the federal employee withholding certificate, the system displays the federal W-4 editable
PDF form. For those states that do follow federal, the state name is stamped on the editable federal PDF
form and the filing status defaults from the federal component. For those states that do not follow federal, the
specific state’s editable PDF form displays. The employee can perform their updates on these forms for both
federal and state withholding. When the form is submitted, the data is saved to the system. See Appendix C
for information on accessing the PA Residency Certificate in My Portrait.
Note: You must ensure your browser is set to use the Adobe Acrobat plugin as its default PDF file viewer. Refer
to the Mozilla Support or Microsoft Community websites for instructions on how to configure Firefox or Internet
Explorer. Do not use Google Chrome for this activity, as it is not compatible with the Adobe PDF file viewer.
Manage Tax Withholding using Smart Navigation

Starting from Release 12, the My Portrait page will not be available for employees to update their withholding
information. Employees can update their withholding information in Smart Navigation using the Manage Tax
Withholding action:
1. Click the About Me > Personal Information menu item.
2. Click More information icon under My Details.
3. Click Payroll
4. Click Manage Tax Withholding
This displays Employee Withholding Certificate page.
Refer to Manage Tax Withholding in My Portrait section for instructions to edit or add state withholding
information.
Tax Calculation
Oracle Fusion Global Payroll automatically calculates your taxes when you perform a payroll run. The following
describes the rules it uses when doing so.
Payroll Processing
When you perform a payroll run, the payroll process:
119
1. Determines the resident and work tax addresses based on the following hierarchy:
Address Type Priority
Location address 4
Location override 3
address
Assignment-level 3
location override
Work at home flag = 1 (overrides assignment, location override, and location)
Yes
Higher priorities override the lower ones.
The process derives the resident tax address from the home address, and the work tax address is derived
from the work location or, if the work-at-home flag is enabled, it uses the home address.
2. Determines the related withholding status and any additional information from the tax calculation card.
3. Passes this information to Vertex for calculation.
Other Considerations
Your tax calculations are also impacted by the following:
 Resident and work location tax addresses are derived by the following:
o Tagged earnings
Used when a unit of paid time is to be taxed in a different jurisdiction, such as when entering 8 hours of
time working in a different location than where the person normally works. When tagged as such, the
payroll process taxes the calculated pay for those units of time at the designated jurisdiction. If the
employee does not have any withholding elections for the tagged jurisdiction, then the process
automatically calculates the tax at the highest withholding status or allowance elections.
o Earnings distribution card
o Resident and work default tax address hierarchy
Taxation is derived based on where the person is located as of the last day of the pay period. For
example, if you make a mid-pay period change, the taxation would still be based on the location as of the
end of the pay period.
 Wage basis rules determine the taxable income
Refer to Wage Basis Rules for additional information.
 Payroll run type
Run Type Description
Supplemental All earnings are taxed at the supplemental rate.
Regular If the supplemental earnings element run type is set to
process separately or pay separately, these elements tax
at the supplemental rate, otherwise they tax at the W-4
rate.
 Organization calculation cards capture:
o SUI and SDI rates
o Self adjustment settings
o Overrides to standard rates
120
 Employee withholding certificate (tax card) captures an employee’s filing status and exemptions at the
federal, state, county, city, school district, and tax district levels
Also captures the SUI and SDI state and any employee-level overrides.
 When using the percentage method tax calculation, Vertex automatically rounds the withholding to the
nearest whole dollar for the following states:
 Colorado
 Idaho
 Maine
 Missouri
 Montana
 North Carolina
 Oklahoma
 West Virginia
Supplemental Taxation Overrides

California taxes the withholding rates on bonus and stock option payments at a different supplemental
withholding rate than other supplemental earnings. You can specify alternate tax methods for these kinds of
earnings, either for new Supplemental Earning elements or existing ones.
Prerequisites
Before you can create or modify Supplemental Earning elements, you must deploy the “Element Information
EFF” extensible flexfield:
1. Navigate to the Setup and Maintenance work area.
2. Select the All Tasks tab.
3. Search for the Manage Extensible Flexfields task.
5. Search for the ”pay%element%“ Flexfield Code.
6. Select the search result, and click Deploy Flexfield.
7. Click Done.
Note:
You can override the supplemental tax method only for supplemental earnings configured as “Process
separately, but pay with other earning”. California is the only state available for selection.
Supplemental Earnings Elements

To set the alternate rate on a Supplemental Earnings element:
1. Navigate to the Payroll Calculation work area.
2. Select the Manage Elements task.
3. Search for the supplemental earnings element (ensure your query returns the shadow elements as well).
121
4. Select the <element name> Calculator shadow element.
5. Select Edit>Correct.
6. Scroll down to the Element Information EFF: Element Information region.
7. Select California for State and Alternate flat rate for Supplemental Tax Method.
8. Click Submit.
FUTA Credit Reduction Rate Overrides

FUTA credit reductions rates are predefined for each of the states that require a credit reduction and are updated
annually. In certain circumstances, you may need to override these rates. To override the rate:
2. Select Manage Calculation Value Definitions.
3. Advance Search for Name that contains Credit Reduction in your LDG (make sure to search with the
effective date that you want to update the rate).
4. Click <state name> Federal Unemployment Tax Credit Reduction Rate.
5. Click Actions > Add Row.

6. Enter the From Value, To Value, and, Rate.
Calculation and Withholding of Pennsylvania Local Earned Income Tax

As part of the payroll calculation process, Vertex compares the Resident Income Tax Rate (city+school) and
Non-Resident Income Tax Rate (city) and uses the higher tax rate for calculating local taxes. The following
information outlines how to configure your application to support the PA Local Earned Income Tax.
Configuring the Pennsylvania Local Earned Income Tax

To configure Oracle Fusion HCM for the US to support the Pennsylvania local earned income tax calculation:
122
1. You must first ensure that you have run the Load Payroll Tax Information process. This process allows the
political subdivision (PSD) codes to become available for use. Refer to the Load Payroll Tax Information
section for instructions.
2. If you haven’t done so already, use the Manage Locations task to define the PSD code each Pennsylvannia
work location. Refer to Locations in the Workforce Structures section for instructions.
3. Update the PSD codes on individual employees’ Residency Certificates as needed.
For newly hired Pennsylvania employees, the employee tax card inherits both the work and resident PSD
codes from their home address and work location. However, there are some situations where you must
manually update the card:
 The employee's work location is outside of Pennsylvania, the employee resides in Pennsylvania, and the
employee has transitioned to work-at-home status. In this case, you must set the work PSD to the home
address’s code.
 The employee's work location has changed from a state other than Pennsylvania to Pennsylvania, and
the employee resides in Pennsylvania. In this case, you must set the work PSD code.
 The employee changes from one work Pennsylvania location to a different work Pennsylvania location.
In this case, you must correct the work PSD code.
Note:
Any time you make a location change to a Pennsylvania employee, whether it is their home address or
work location, you must confirm that the PA Residency Certificate has the proper resident and work PSD
codes.
To update the codes:
a. Start the Manage Calculation Cards task from the Payroll Calculations work area.
b. Search for and select the person record.
c. Click Employee Withholding Certificate.
d. Select PA under the Component Groups tree and Regional link.
e. Open the Action menu, and select Correct or Update.
f. Update the following values as needed:
 Resident PSD Code
 Work PSD Code
 Resident School District
 Work School District
g. Do not enter any values for the Resident Income Tax Rate and Non-Resident Income Tax Rate fields.
123
h. Click Save and Close.
Note:
The payroll process automatically determines the PSD code by:
1. Checking the employee’s residency certificate.
2. If not found there, it attempts to determine the code based on the employee’s home address, including the
tax district. This is for the Resident PSD Codes only.
3. If it is unable to derive the PSD code, or if you have specified an invalid code on the residency certificate, the
payroll calculation stops for that employee. The payroll process logs an error in the payroll results.
Setting Up Employee Earning Distribution Overrides

The Employee Earnings Distribution Overrides card is used to derive the percentage of earnings to be distributed
over different jurisdictions. The card is created using the Manage Calculation Card task. This card must be
created for each work relationship the employee is in.
To capture the percentage of earnings distribution that applies to the state, county, and city for the employee:
1. Select Manage Calculation Cards in the Payroll Calculation work area.
2. Search for and select the employee.
3. Under Search Results, click Create.
124
4. Select Employee Earnings Distribution Overrides, and click Continue.

5. To distribute employee earnings to a different state (for example, 50 % to Alabama):
a. In the Calculation Card Overview panel, click Regional.
b. Select Actions>Create.
c. Select the state.

d. Click Save.
e. In the Calculation Component Details section, select either Edit>Correct or Edit>Update to modify the
percentage.
f. Enter the percentage.
g. Click Save.
6. To distribute employee earnings to a different county (for example, 50% to Jefferson county):
a. In the Calculation Card Overview panel, select the state component under Regional.
125
c. Select the county.

d. Click Save.
7. To distribute employee earnings to a different city (for example, 50 % to the city of Birmingham):
a. In the Calculation Card Overview panel, select the county component under Regional.
c. Select the city.

d. Click Save.
126
Reciprocal Agreements and Setting the Employee Nonresident Status

Some states have reciprocal agreements where the employee may claim nonresident status. This allows the
employee to have their resident state tax withheld in lieu of their work state tax. In order to accomplish this, you
must set the Nonresident field on the tax card to Yes. Otherwise, Vertex can not correctly calculate the
reciprocity. For specific reciprocity tax calculations, refer to the Vertex tax guide.
To set the Nonresident field on the tax card:
3. Select the Employee Withholding Certificate Calculation Card, and click Search (this assumes there is
already an existing Employee Withholding Certificate).
4. Click the Regional Component Group.
If more than one state exists under the Regional group, select the appropriate state.
5. Under State Tax Information, select Yes for Nonresident.
SUI Limits and Changes to State

If an employee has a change in their work state within the same TRU, the system automatically handles the state
specific SUI limits. Once those limits are reached, the state unemployment employee/employer deductions are
stopped. The SUI limit is adjusted automatically for the new state for SUI wages paid in another state. This
means that SUI wage base overrides are not necessary in Fusion.
Note:
If the SUI rate changes mid year, you must turn off the self adjust to keep the integrity of the calculation prior
to the rate change. You configure self adjustment settings on the organization calculation card.
Overriding the Employee’s California Wage Plan Code

The California Wage Plan Code is captured at the PSU and TRU levels. To override the the state’s Wage Plan
Code for the employee:
127

3. Select the Reporting Information Calculation Card, and click Search.
4. Click CA under the Regional Component Group.
This assumes there is already an existing CA state Component Group. If not, select Regional and click
Create to create the California state Component Group.
5. Under Calculation Component Details, click Add Row to add the California Reporting Information Calculation
Component Details.
6. Click OK.
7. Select the appropriate Wage Plan Code.
Terminating a Worker
When a person’s 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.
4. Click Submit.
128
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.
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.
Adding Payment Information to an Employee

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.
4. In the Payroll Details section of the Manage Person Details page, add the payroll.
5. Click Save and then Done.
Transferring an Employee to a New Payroll

To assign an employee to a new payroll:
1. Start the Manage Payroll Relationships task in the Payroll Calculation work area.
129
3. Enter the appropriate Effective As-of Date.

4. Select the appropriate assignment under the Payroll Employment Tree.
5. Select Actions > Transfer Payroll under Payroll Details.
6. Enter the new payroll, and click Save.
7. Select the old payroll under Payroll Details, and review the element duration dates.
8. Edit the Final Close date to the last check date you will pay the employee out of the old payroll, and click
Save.
Refer to the Assigning and Transferring Payrolls topic in the Help Portal for a demonstration and the Transferring
a Person's Payroll from Weekly to Semimonthly topic for an example.
Assigning Payment Methods to the Employee

Before adding payment methods to an employee, you must configure the banks and branches in the system and
assign a payroll definition to the employee. By default, all employees inherit the payroll definition’s OPM. If you
want to override this for a specific employee, you need to create a PPM and select an alternate OPM.
Note:
Before you can define PPMs, you must use the CE_USE_EXISTING_BANK_BRANCH profile option to
determine how employees enter their bank details. See the Banking Setup section for information on setting
this profile option.
To assign PPMs:
1. Select the Manage Personal Payment Methods task in the Payroll Distribution work area.
3. On the Manage Person Details page, click Create.
4. On the Personal Payment Method page, select the Organization Payment Method for this employee.
5. If the payment type is Direct Deposit, you must add a bank account and provide banking details.
Note:
When you pick an existing branch name, the Oracle Fusion Financials for the Americas plug-in populates the
Routing Transit Number and it becomes read-only. If you are creating a new branch, the Routing Transit
Number is an editable field. You must enter a branch Routing Transit Number for a new branch.
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.
For IAT payments, use Batch Loader to add country-specific bank account details for an employee. Country
code is added in the Create External Bank Account Task Action in the Batch Loader.
130
Payroll Processes
The following items describe useful information for various payroll processes within Fusion.
QuickPay
Use QuickPay to perform a payroll run for a single person without waiting for the normal payroll cycle cut-offs.
This is typically done when certain person-specific events occur, such as new hire, termination, special
payments, or a localized problem with a payroll run that requires reprocessing. The QuickPay flow calculates
payroll run results and prepayments and then allows you to make an external payment to the individual.
Settings that Affect Processing

You specify parameters when you submit the QuickPay flow and then provide additional settings as tasks in the
QuickPay flow are executed:
 QuickPay flow parameters
 Process date of the QuickPay run
 Payroll relationship for the person whose payroll you are processing
 QuickPay calculation settings
 Payroll
 Date paid
 Payroll period for the QuickPay
 Date earned
This is the date the payroll run uses to determine which element entries to process. This is typically the
last day of the payroll period being processed. The default date earned is derived from the payroll
calendar period.
 Run type
Select the type of payroll run, such as regular or supplemental. The run type determines which payroll
calculations to perform, which elements to process, and how to pay the results.
 Element entries
You can exclude element entries that you do not want processed (for example, an employee may not
want to have voluntary deductions taken from a special bonus check). By default, QuickPay processes
all element entries for all terms and assignments associated with the specified payroll relationship, based
on the run type and other settings you provide.
How QuickPay Is Processed

The following figure shows the sequence of tasks in a QuickPay flow:
131
The QuickPay flow is summarized here:

1. The Calculate QuickPay task calculates payroll run results for the person, based on the settings provided.
2. You verify the run results on the View Person Process Results page and mark the verification task as
complete.
3. The Calculate QuickPay Prepayments task calculates payment distribution.
4. You verify the prepayment results in the Prepayment Results section of the View Person Process Results
page, and then mark the verification task as complete.
5. If payment is being made by an internal payment process, such as Make EFT Payments or Generate Check
Payments, you can skip to the end of the flow and then run the payment process now or after processing
multiple QuickPays for the same payment method. Select the Skip Flow action for the Make External
Payment task to skip the rest of the tasks in the flow and mark the flow as complete. When you are ready,
run the payment process, which will pick up unpaid payments from this QuickPay and any others that match
the parameters you provide when you submit the process. If the payment is being made externally, you
select the Make Payment action on the Make External Payments page and record information about the
external payment, such as the check number and reason for generating the payment manually. The
application marks the record as Paid so that it will not be included in the normal payment process.
6. You verify the payment results and mark the task as complete.
Submit the QuickPay Flow

To perform a QuickPay operation:
1. In the Payroll Calculation work area under Person, start the Calculate QuickPay task.
You can also select the Submit a Payroll Flow and then select the QuickPay flow pattern.
2. On the Flow Pattern page, select an LDG and click Next.
3. On the Enter Parameters page, complete the following fields and then click Next:
Field Name Notes
132
Payroll Flow Enter a flow name.

Process Date Specify the current date.
Payroll Search for the payroll relationship for the person.
Relationship
Reason Defaults to Corrective Action.
4. On the Enter Flow Interaction page, click Next.
5. Review the information and click Next.
6. Click OK and View Checklist.
Calculate and Verify Run Results

To calculate and verify the run results:
1. On the Payroll Flow checklist page, click Go to Task for the Calculate QuickPay task.
2. On the Calculate QuickPay page, select Regular in the Run Type field and verify the remaining information in
the Details section.
The Element Entries section refreshes to display all element entries that will be processed in the QuickPay
run, based on the settings defined in the Details section and rules defined for the element entries
themselves.
3. Exclude any element entries from being processed by deselecting them.
4. Click Submit Process.
5. Click Go to Task for the Verify Payroll Results task.
6. On the View Person Process Results page, click the person's name in the Search Results.
7. Verify the SOE.
8. Click Done to return to the checklist.
Processing International ACH Transfers

Use the Make EFT Payment process to generate the IAT electronic payment file.
To generate an IAT EFT payment to an employee:
1. Create International Organization Payment Method.
Refer to the Organization Payment Methods section for steps to create the OPM and to enter the EFT details.
2. Attach the OPM to a payroll.
Refer to the Payroll Definitions section for steps to add the OPM to a payroll.
3. Add primary mailing foreign address for employee.
4. Create IAT Personal Payment Method to the employee.
Use Batch Loader to add a personal payment method and country-specific bank account details for an
employee.
5. Run the ‘Make EFT Payments’ process for an organization payment method with a payment type of
International Transfer, ensure that you select the International EFT report category.
Employee Payslip
Occasionally it is necessary for the payroll administrator to view the employee’s payslip and not the SOE, which
is more for deep dive trouble shooting. There are three methods for viewing the payslip:
 View Payslip link in Person Management Work Area
133
 Documents tab in Manage Person UI

 Manage Document Records UI
Person Management Work Area

To view the employee payslip from the Person Management work area:
1. Click Navigator > Person Management.
3. Select View Payslip.
4. Enter any search criteria.

5. Click Search.
6. Click the URL under the View Payslip column for the desired payment date.
7. Click Open.
Manage Person
To access the payslip from the Documents tab in the Manage Person UI:
1. Click Navigator > Person Management.
3. Click the Documents tab.
134
4. Click the URL under the Attachments column for the desired payment date.
5. Click Open.
Manage Document Records

To access the payslip from the Manage Document Records UI:
1. Click Navigator > Document Records.
2. Select Payslip from the Type drop down list.
3. Search for and select the person name.
4. Click Search.
5. Click the URL under the Attachments column for the desired payment date.
6. Click Open.
Earnings Taxation Over Multiple Pay Periods

Instead of taxing an earnings payment in only the current pay period, you may choose to spread that taxation out
across a number of months. As a result, the tax would be at a lower rate.
For example, if you tax a bonus of 10,000 USD in only one period, the tax amount would be higher than if you
taxed that same bonus amount over 6 months.
135
In order to accomplish this, the element template provides the “Tax this earning across multiple pay periods”
question during element definition. If you answer Yes to this question, the template creates a Taxation Pay
Periods input value. This new input value allows you to define how many pay periods to tax the payment over on
the employee’s element entry for that earnings code.
Note:
In order to include this input value as part of the element, you must also answer the “Process and pay
element separately or with other earnings elements?” element template question with one of the following:
 Process separately, but pay with other earnings
 Process separately and pay separately
136
Pretax Deduction Refunds

Occassionally a pretax deduction may be taken from an employee’s pay that was in error. If the element was
created by a conversion row based on Fusion Benefits, you cannot remove the element entry.
There are two options based on whether payroll has been run or not:
 If payroll has not been processed, and you are still in the benefits enrollment window, you can back out or
open the conversion life event and deselect the plan that resulted in the incorrect deduction (for example,
FSA plan).
 If payroll has been processed, you should make the adjustment for reimbursment in next pay run.
For this situation, it is advised to perform the refund during the next payroll run. However, if that is not an
option, it is advised to pay the refund as 80-90% of the deduction amount as an nonpayroll payment, then
deduct that amount from the regular check in the next pay cycle. Do not give the full amount back, because
the actual refund takes additional taxes to offset the tax break that they previously receieved.
137
Tax Troubleshooting
Before contacting Oracle Support for any of these issues, please check the following:
Problem Solution
Errors Confirm that a TRU is properly associated to the employee’s withholding certificate.
during Refer to the Payroll Processing
payroll There are several factors that make up the payroll processing.
calculation
Taxation Within Fusion Payroll
Vertex provides all the statutory compliance for the Oracle Fusion Global Payroll engine,
but it is important for you to understand how the payroll process handles US taxation.
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.
Note:
For states that levy school district income taxes, you must manually populate the
school district on the employee withholding certificate. Depending on the state, you
enter the school district under either the city or county node. For resident addresses
in a township, you must populate the tax district field on the address before you can
populate the proper school district on the tax card.
Setting Up Automatic Tax Card Creation

To ensure that new workers get an Employee Withholding Certificate:
3. Set the PAYROLL_LICENSE process configuration parameter to either PAYROLL or
PAYROLL_INTERFACE, as appropriate to your implementation.
4. Confirm that element eligibility has been created for the US Taxation element. This
element is automatically added to employee’s element entry when the association to
the Tax Reporting Unit is completed.
Manual Tax Card Creation

There are cases where an employee would not have their tax card automatically
created, such as if they were loaded through the File Based Loader utility.
For these employees, to create an Employee Withholding Certificate:
20. Start the Manage Calculation Cards task.
22. Click Create.
138
23. Enter an appropriate Effective-As-of-Date, and select Employee Withholding

Certificate for Name.
24. Enter employee information as appropriate at the Federal level.
25. Click Save.
26. Select the Regional link under the Component Groups tree.
27. Enter employee information as appropriate for the Regional level.
28. Click Save.
29. Select the Associations link under the Component Groups tree.
30. Under Associations, click Create.
31. Select the Tax Reporting Unit, and click OK.
32. Click Save. This creates the US Taxation Component and is displayed in the
Calculation Component column after saving.
33. Under Association Details, click Create.
34. Select the Employment Terms or Assignment Number and the Calculation
Component created in prior steps, and click OK.
35. Click Save.
36. Upon tax card association creation, the following fields are autopopulated with
default values on the federal-level employee withholding certificate and should be
verified:
 State for Unemployment Calculation
 State for Disability Calculation
 Primary Work Address
Changing the TRU for an Assignment

To change the TRU for a preexisting assignment on the Employee Withholding
Certificate:
12. Select Manage Calculation Cards.
14. Click Employee Withholding Certificate.
15. Click Associations under the Component Groups tree.
16. Select the Tax Reporting Unit under Associations for which the assignment currently
exists.
If the association for the TRU for the new assignment does not already exist, create
it now.
17. Select the assignment number to change under Association Details.
18. Click Edit>Update.
19. Select the Calculation Component for the new TRU.
This end dates the record for the assignment associated with the previous TRU and
139
creates a new record for the new TRU.
Wage Accumulation
On the Employee Withholding Certificate, each tax component group (Federal and
Regional) has a Withholding Exemption section. To exempt an employee from tax
withholding or wage accumulation, mark the following as Yes:
Field Name Result
Exempt from Does not withhold this tax but does accumulate wages for
(component) Income the component.
Tax
Exempt from Wage Does not withhold tax, and does not accumulate wages for
Accumulation the component.
If you mark both as exempt, the payroll process ignores the Exempt from Wage
Accumulation setting.
Manage Tax Withholding in My Portrait

Employees can update their own withholding information in Portrait using the Manage
Tax Withholding action:
3. Select Manage Tax Withholding action in the left panel under Actions.
This displays the Employee Withholding Certificate page.
140
4. Click Edit. This is available for both the federal and state level.
When you access the federal employee withholding certificate, the system displays
the federal W-4 editable PDF form. For those states that do follow federal, the state
name is stamped on the editable federal PDF form and the filing status defaults from
the federal component. For those states that do not follow federal, the specific
state’s editable PDF form displays. The employee can perform their updates on
these forms for both federal and state withholding. When the form is submitted, the
data is saved to the system. See Appendix C for information on accessing the PA
Residency Certificate in My Portrait.
141
Note: You must ensure your browser is set to use the Adobe Acrobat plugin as its
default PDF file viewer. Refer to the Mozilla Support or Microsoft Community websites
for instructions on how to configure Firefox or Internet Explorer. Do not use Google
Chrome for this activity, as it is not compatible with the Adobe PDF file viewer.
Manage Tax Withholding using Smart Navigation

Starting from Release 12, the My Portrait page will not be available for employees to
update their withholding information. Employees can update their withholding
information in Smart Navigation using the Manage Tax Withholding action:
5. Click the About Me > Personal Information menu item.
6. Click More information icon under My Details.
7. Click Payroll
8. Click Manage Tax Withholding
This displays Employee Withholding Certificate page.
Refer to Manage Tax Withholding in My Portrait section for instructions to edit or add
state withholding information.
Tax Calculation
Oracle Fusion Global Payroll automatically calculates your taxes when you perform a
payroll run. The following describes the rules it uses when doing so.
Payroll Processing
When you perform a payroll run, the payroll process:
4. Determines the resident and work tax addresses based on the following hierarchy:
Address Type Priority
142
Location address 4
Location override 3
address
Assignment-level 3
location override
Work at home flag = 1 (overrides assignment, location override, and location)
Yes
Higher priorities override the lower ones.
The process derives the resident tax address from the home address, and the work
tax address is derived from the work location or, if the work-at-home flag is enabled,
it uses the home address.
5. Determines the related withholding status and any additional information from the tax
calculation card.
6. Passes this information to Vertex for calculation.
Other Considerations
Your tax calculations are also impacted by the following:
 Resident and work location tax addresses are derived by the following:
o Tagged earnings
Used when a unit of paid time is to be taxed in a different jurisdiction, such as
when entering 8 hours of time working in a different location than where the
person normally works. When tagged as such, the payroll process taxes the
calculated pay for those units of time at the designated jurisdiction. If the
employee does not have any withholding elections for the tagged jurisdiction,
then the process automatically calculates the tax at the highest withholding
status or allowance elections.
o Earnings distribution card
o Resident and work default tax address hierarchy
Taxation is derived based on where the person is located as of the last day of the
pay period. For example, if you make a mid-pay period change, the taxation
would still be based on the location as of the end of the pay period.
 Wage basis rules determine the taxable income
Refer to Wage Basis Rules for additional information.
 Payroll run type
Run Type Description
Supplemental All earnings are taxed at the supplemental rate.
Regular If the supplemental earnings element run type is set to
process separately or pay separately, these elements tax
at the supplemental rate, otherwise they tax at the W-4
rate.
143
 Organization calculation cards capture:

o SUI and SDI rates
o Self adjustment settings
o Overrides to standard rates
 Employee withholding certificate (tax card) captures an employee’s filing status and
exemptions at the federal, state, county, city, school district, and tax district levels
Also captures the SUI and SDI state and any employee-level overrides.
 When using the percentage method tax calculation, Vertex automatically rounds the
withholding to the nearest whole dollar for the following states:
 Colorado
 Idaho
 Maine
 Missouri
 Montana
 North Carolina
 Oklahoma
 West Virginia
Supplemental Taxation Overrides

California taxes the withholding rates on bonus and stock option payments at a different
supplemental withholding rate than other supplemental earnings. You can specify
alternate tax methods for these kinds of earnings, either for new Supplemental Earning
elements or existing ones.
Prerequisites
Before you can create or modify Supplemental Earning elements, you must deploy the
“Element Information EFF” extensible flexfield:
8. Navigate to the Setup and Maintenance work area.
9. Select the All Tasks tab.
10. Search for the Manage Extensible Flexfields task.
12. Search for the ”pay%element%“ Flexfield Code.
13. Select the search result, and click Deploy Flexfield.
14. Click Done.
Note:
You can override the supplemental tax method only for supplemental earnings
configured as “Process separately, but pay with other earning”. California is the only
144
state available for selection.
Supplemental Earnings Elements

To set the alternate rate on a Supplemental Earnings element:
9. Navigate to the Payroll Calculation work area.
10. Select the Manage Elements task.
11. Search for the supplemental earnings element (ensure your query returns the
shadow elements as well).
12. Select the <element name> Calculator shadow element.
13. Select Edit>Correct.
14. Scroll down to the Element Information EFF: Element Information region.
15. Select California for State and Alternate flat rate for Supplemental Tax Method.
16. Click Submit.
FUTA Credit Reduction Rate Overrides

FUTA credit reductions rates are predefined for each of the states that require a credit
reduction and are updated annually. In certain circumstances, you may need to override
these rates. To override the rate:
9. Select Manage Calculation Value Definitions.
10. Advance Search for Name that contains Credit Reduction in your LDG (make sure to
search with the effective date that you want to update the rate).
11. Click <state name> Federal Unemployment Tax Credit Reduction Rate.
12. Click Actions > Add Row.

13. Enter the From Value, To Value, and, Rate.
145

section for more information.
Error during Edit the federal tax card component on the Employee Withholding Certificate. Ensure
payroll the SUI state, SDI state, and primary work address are populated correctly. These fields
calculation are defaulted once the tax card association is created.
that a Note:
geography If the work location is missing for the employee’s assignment, these fields would not be
code is defaulted when the tax card association is created, and you would need to define them.
missing or
primary
work
address is
missing
Errors Use the Manage Legal Reporting Unit Calculation Cards task to confirm that the SDI and
during SIT component details have been created for the LRU. No overrides are necessary.
payroll Only the component detail needs to be created.
calculation
related to
the
US_TAX_S
DI formula
Periodic Check that the United States Federal Tax registration exists for the TRU.
Archiver
does not
archive any
US
balances
Payroll run Check the following:
produces  Verify that the employee’s resident and work addresses are in US address format,
inaccurate and confirm any overrides.
tax
For work addresses, the following hierarchy is used:
calculations
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:
146
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
employee’s 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.
2. Select Federal or State.
3. Compare your wage basis rules against the State Withholding Tax Summary in
the Vertex Calculation guide.
147
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 HCM for the US to run the New Hire report:
1. Ensure that a default TRU is associated to a legal employer.
2. Refer to the Additional Reporting 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 Contact Details section on how to capture contact details for a TRU.
5. Verify the FEIN is set up for United States federal tax.
6. Refer to the Registrations section for information on creating registrations.
8. Verify the employees’ New Hire Status.
Refer to the Configuring Disabilities

Before you can assign disabilities to employees, you must define the specific disability types and statuses
required for your organization’s business needs.
Note:
When using the Manage Person task, you select these values through the Type and Requested
Accommodation Status fields in the Legislative Information region on the Disabilities tab.
Use the Manage Common Lookups task to set the valid entries for the following lookups:
Lookup Field
HRX_US_ADA_TYPE Type
HRX_US_ADA_STATUSES Requested Accommodation Status
Refer to the “Person Lookups: Explained” topic on the Help Portal for a list of other person disability lookups
available from Global Human Resources.
Hiring a Worker section for information on New Hire Status.
To verify large numbers of employees, follow the instructions in the next section.
Baselining Employee Status After Implementation

If you ran the New Hire report immediately after migrating from a legacy system, the New Hire Status parameter
would be blank for all employees and all employees would be reported.
To set the New Hire Status parameter for all legacy employees:
1. Start the process as described in the next section.
148
2. When setting the process’s parameters, set the End Date field for the date when you last generated this
report with the legacy system. This sets the New Hire Status parameter for the employees reported to that
date.
3. Discard the output report.
4. Proceed with your standard new hire reporting schedule.
Generating the New Hire 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 Mandatory Select Yes if you are a multistate employer and want to
Employer 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 and 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 end of the
reporting date range.
If a start date is not entered, the report process
captures all new hires and rehires as of this date.
Reporting State Mandatory State to which you are submitting this report. The
report is formatted according to this state’s
requirements.
Reporting Mode Mandatory Choose one of the following:
 Draft: Verifies the data prior to submission.
 Final: Produces 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 Overrides the contact information in the report. The
149
LOV is 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.
150
VETS-4212 Employment Report

Oracle Fusion Human Capital Management for the United States supports the generation of the VETS-4212
Federal Contractor Veterans’ report.
Prerequisites
Some of the following steps require the use 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 Human Capital Management for the United States to run the VETS-4212 report:
1. Define VETS-specific information in the Location UI. A valid US Zip Code is required for proper reporting.
Refer to the Locations section for VETS-specific information to capture.
Note: The Run VETS-4212 Establishment Electronic Report process uses the values you specify in the
Maximum and Minimum Number of Employees fields in the Location UI for employee counts. If you leave
these fields blank, the process derives the employee counts based on the reporting period start and end
dates.
2. Associate each job with an EEO-1 category.
Refer to the Jobs section for instructions on assigning EEO-1 categories to a job.
3. Enter VETS reporting information for your legal employer.
Refer to the Additional Reporting Information for Legal Employers and PSUs section for additional
information.
4. Enter VETS reporting information for your TRU.
Refer to the HCM Information section for additional information.
5. Verify FEIN is set up for United States federal tax.
Refer to the Registrations section for information on creating registrations.
6. Assign the appropriate veterans data to employees.
When hiring a new employee, you record their veteran data on the Hire an Employee: Person Information
page, in the Legislative Information region.
Note:
It is no longer necessary to populate the VETS-100 and VETS-100A fields starting from reporting period
2015. These fields were removed in PB11.
151
Note:
Select from either the Veteran Self-Identification Status drop-down or the individual categories using the
checkboxes. If both the self-identification status and individual veteran categories are selected, then the
report process counts the employee twice in the protected veteran category. Assign the appropriate job to
employees.
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-4212 report:
2. Select a value from the Legislative Data Group LOV.
3. Select the Run VETS-4212 Establishment Electronic Report flow pattern in the Process or Report section.
4. Click Next.
152

Legal Employer Mandatory Select a parent legal employer to report all employees
attached to it and child legal employers, if any.
Establishment Mandatory Select Multiple if you have multiple establishments.
Employer Type 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 defined on the
Official TRU’s contact information.
Phone Number Optional Default is the HR representative phone number defined on
the TRU’s contact information.
E-Mail of Certifying Optional Default is the HR representative E-mail address defined on
Official the TRU’s contact information.
6. Click Next.
7. In the Enter Flow Interaction task, click Next.
8. In the Schedule task, select “As soon as possible”.
9. Click Next.
10. Click Submit.
11. In the confirmation window, click OK and View Checklist.
This process generates an electronic file, an audit report, and an exception report.
Viewing the Output

To view the output files:
153
US > VETS.
3. Click VETS-4212 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):
 VETS4212_eTextReport
 VETS4212_AuditReport
 VETS4212_ExceptionReport
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.
154
9. Select the output name link under the Output & Delivery section.
155
VETS-100 and 100A Employment Reports

The VETS-100 report will no longer be used beginning with the 2015 filing cycle. The VETS-100A report is
replaced by the VETS-4212 report. The new VETS-4212 report must be used instead of VETS-100A report
beginning with the 2015 filing cycle.
156
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
Some of the following steps require the use of a task or tasks. These tasks must be accessed through an
Set Up Steps
To configure Oracle Fusion Human Capital Management for the United States to run the EEO-1 report:
1. Define EEO-1 specific information in the location UI. A valid US Zip Code is required for proper reporting.
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 Additional Reporting Information for Legal Employers and PSUs section for additional
information.
4. Enter EEO-1 reporting information for your TRU.
Refer to the HCM Information section for additional information.
5. Verify FEIN is set up for United States federal tax.
6. Refer to the Registrations section for information on creating registrations.
7. 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.
8. 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.
For nonpayroll implementations, if you do not attach your employees to a reporting establishment, the EEO-1
report process associates the employee to the TRU identified in the “TRU for the New Hire Report” field.
This field is located in the Manage Legal Entity HCM Information task.
Assigning the employee to a reporting establishment is not required for payroll implementations.
9. Assign the appropriate Assignment Category to employees.
When hiring a new employee, you record their assignment category on the Hire an Employee: Employment
information task, in the Job Details region.
10. For Work-at-Home employees, the EEO-1 report uses the work location set at the assignment level. In order
for this type of employee to be picked up on the EEO-1 report, you must populate the location field with one
of the following on the employee’s assignment:
 Location where they were hired
 Headquarters location
 Manager’s location
157
Running the Report

To run the EEO-1 report:
2. Select value from the Legislative Data Group LOV.
3. Select the Run EEO1 Report flow pattern in the Process or Report section.
4. Click Next.
Legal Employer Mandatory Select a parent legal employer to report all employees
attached to it and any child legal employers.
Establishment Mandatory Select Multiple if you have multiple establishments.
Employer Type Otherwise, select Single.
Payroll Period Mandatory Select any payroll period start date occurring during
Start Date the third quarter of the current survey year (July,
August. or September).
Payroll Period Mandatory Select any payroll period end date occurring during the
End Date third quarter of the current survey year (July, August,
or September).
Title of Certifying Optional Use to override the contact information. The default is
Official the HR Representative title specified on the TRU
contact information.
Name of Optional Use to override the contact information. The default is
Certifying Official 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 Optional Use to override the contact information. The default is
Certifying Official 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.
158
Viewing the Output

To view the output files:
US > EEO.
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.
Note:
The output file (eText) generated is based on the EEO-1 data file specifications. You must modify the file
name as per the EEOC guidelines and then upload it to the EEO website.
159
Multiple Worksite Reporting

The Multiple Worksite Report (MWR) collects information on a business establishment's employment and wages,
distributed by industry, location, and state. You file this report with the Bureau of Labor Statistics (BLS)
Electronic Data Interchange (EDI) Collection Center. They use the report data to ensure an equitable distribution
of federal funds through grant programs that use county economic indicators as a basis for allocations.
An employer must submit this information to the EDI Center if they meet all of the following criteria:
 Reports their employees under one SUI account number
 Is engaged in multiple economic activities, is operating under more than one worksite, or both
 Has a total of 10 or more workers employed across all worksites
If an organization has an office at only one location within a state, it is not considered a multiple worksite, and this
report is not necessary.
Prerequisites
Some of the following steps require the use of a task or tasks. You access these tasks through an
All Quarter-to-Date Archive processes must be run and completed before starting this process.
Set Up Steps
To configure Oracle Fusion Human Capital Management for the United States to run the MWR report:
1. Use the Manage Legal Reporting Unit Registrations task to set the following fields for all TRUs:
Jurisdiction Field Name Description
United States Registration Employer's FEIN.
Federal Tax Number
<state> Registration Employer's SUI account number.
Unemployment Number
Insurance
Note:
You must run this report for the Puerto Rican TRUs separately from your US TRUs.
2. Use the United States Multiple Worksite Reporting region of the Manage Location task to set the following
fields for each location:
Trade Name Name of the client establishment at this
location.
Worksite Description Meaningful, unique description of the client
establishment, such as store number or
plant name.
Unit Number Five-digit number used in conjunction with
the SUI account number to uniquely identify
a location at its address. This field is
160
informational only.
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 Reporting Select Yes if this location is eligible for MWR
reporting. When the report is run, all
employees assigned to this location are
included in the report. Select No to exclude
this location from the report.
3. For employees designated as work-at-home:

a. Mark employees properly on their Reporting Information Card for inclusion on the MWR.
b. Use the Manage Calculation Cards task to select the location that represents the employees’ state as the
Eligible Reporting Location on their tax cardEmployee Withholding Certificate.
You must have at least one location per state available for assignment to work-at-home employees. If
you do not specify a location, the report process assigns the employees to location 999999 on the report.
The exception report output includes a warning message, indicating the reporting location state and
resident tax state mismatch.
Running the Report

To run the MWR report:
1. Select Payroll > Regulatory and Tax Reporting>Submit a Process or Report
2. Select the Legislative Data Group LOV.
3. Select the Run Multiple Worksite Electronic Report, and click Next.
Year Mandatory Enter a 4-digit reporting year.
Quarter Mandatory Select the reporting quarter: 1, 2, 3, 4.
Payroll Statutory Mandatory Select your PSU.
161
Unit
Tax Reporting Unit Optional Select the TRU associated with your FEIN. If no TRU is
selected, all TRUs are reported for the PSU.
If the employer is operating under multiple FEINs, leave this
field blank while specifying a value for the PSU.
You must run this report for Puerto Rican TRUs separately
from your US TRUs.
Type of Employer Mandatory Select the type of employer:
 Regular Employer
 Payroll Provider Firm
Client Contact Optional Overrides the contact person's phone number defined for
Phone Number the legal entity. Used only if the type of employer is
identified as a payroll provider firm.
Client Contact Optional Overrides the contact person's name set for the legal
Name employer. Used only if the type of employer is identified as
a payroll provider firm.
Process Optional Use to override the contact information. The default is the
Configuration HR representative’s rmail address as specified on the TRU
Group contact information.
5. Click Next.
7. Select “As soon as possible” in Schedule task.
8. Click Next.
9. Click Submit.
10. Click OK and View Checklist in Confirmation window.
The report process generates an electronic file, an audit report, and an exception report.
Report Description
Electronic output file This process supports the electronic EDI submission method developed by the
BLS. This file groups locations according to their SUI account numbers under
their FEIN, and their employment data is compiled into a single ASCII fixed field
text file.
You are responsible for properly naming, encrypting, and transmitting the output
file to the BLS data collection center in Chicago, where it is then routed to the
respective state agencies. This can be done by FTP, SFTP, or secure web
transfer. Refer to the BLS website for further information.
This file is sorted by:
State
SUI account number
Note:
The output file (eText) generated is based on the MWR data file specifications.
You must transmit the output file to the EDI Center
Audit file Provides totals by FEIN, SUI account number, and worksite description code. It
sorts the grand totals by FEIN and SUI account number. You can review this file
to verify that these totals match the totals returned by your diagnostic reports,
162
such as the Employee Active Balance Report, Gross0-to-Net Report, or your

Third-Party Quarterly Tax Extract.
Exception report Includes data mismatches, missing archived data, missing locations, and other
errors detected by the process.
Troubleshooting
There are multiple scenarios where data errors would require the reprocessing of the MWR. Many of these are
logged as events in the MWR exception report.
In the event of such data errors:
1. Roll back the Run Multiple Worksite Electronic Report process.
2. Roll back the Quarter-to-Date Archive process.
3. Resolve your data errors, as described.
4. Run the Quarter-to-Date Archive process, and ensure all processes have completed.
5. Resubmit the Run Multiple Worksite Electronic Report process.
6. Transmit the output file to the EDI Center.
The following are examples of data errors that would require the rerun of the MWR process:
Problem Solution
Location Was Incorrectly Excluded from One or more locations are marked as No for the Include
Report for Reporting field despite having active employees
assigned to them.
All active employees must be assigned to a location that
is included in the report. During the data error resolution
step, you must do one of the following:
 Reassign the active employees to an eligible
location.
 Change the locations' reporting status from excluded
to included:
1. Navigate to the Manage Locations task.
2. In the United States Multiple Worksite Reporting
region on the Manage Location page, change the
Include for Reporting field to Yes.
Included Location Was Marked as One or more inactive locations were included in the
Inactive report. When the MWR process was run, all employees
attached to these locations were listed in the exception
report.
During the data error resolution step, you must do one of
the following for each affected location:
 Reactivate the location.
 Move all employees to an active location, and
remove the inactive location from the report:
1. Navigate to the Manage Locations task.
163
2. In the United States Multiple Worksite Reporting

region on the Manage Location page, change the
Include for Reporting field to No.
Employee Wages Were Changed After This can occur as a result of a late payroll run, balance
the Report Was Run adjustment, and so on. In this case, no data errors exist;
however, the MWR and Quarter-to-Date processes must
be rolled back and rerun in order to update the
employee's payroll data.
Report Was Run Before All Quarter-to- The Run Multiple Worksite Electronic Report process
Date Archive Processes Were Complete was started before all Quarter-to-Date Archive
processes have completed. As a result, the archive
provided the report with incomplete data.
No data correction is required. Roll back the processes
and resubmit them, in the proper order, ensuring they
complete processing.
Work-at-Home Employees not Appearing One or more employees designated as work-at-home
in Report are reported in the MWR in location 999999 or they are
included in locations outside their state of residence.
The MWR organizes workers designated as work-at-
home in the same state as their residence tax state. This
ensures they are reported in the same state as their
state unemployment insurance state. To ensure work-at-
home employees are properly reported:
For each work-at-home employee, check the following:
 Employees are properly marked for inclusion in this
run of the MWR.
 Location representing each of the employees' states
exists, and you have selected those locations as the
Reporting Location for Work-at-Home Employees on
the employees' Reporting Information cards.
One location per state is used for all designated
work-at-home employees.
164
Appendix A: 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). The
Load Geographies for US process performs these updates. See the Geographies section for more details.
 Payroll Tax Calculation Rules/Tax Data: These updates come from Vertex in the monthly QFPT.dat (Tax
file). The Load Payroll Tax Information for US process performs these updates. See the Load Payroll Tax
Information for US section for more details.
 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.
Licenses
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.
Address Validation
For SaaS customers, address validation is included with the HR and Payroll licenses. However, for On-Premise
and On-Demand customers, address validation is included with a Payroll license. For HR licenses, customers
must acquire a Vertex license separately in order to get the functionality.
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 user’s 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 month’s update
and the new update on this page. There is one document for the US and one for Canada.
Note:
th
Although you may get a notification before the 18 of the month, the Vertex guides are not available until the
th
18 .
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
165
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.
Customer does not have a US Payroll Switch the license to HR-only, and run the
license and does not want address Load Geographies for US task again. If
validation 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 the Tax Troubleshooting section.
You may be asked to provide additional
details from the payroll run. Refer to “How
to Enable Logging for Oracle Fusion
Global Payroll” (Doc ID 1536245.1) on the
Oracle Support website.
Make note of logging parameter value “V,”
as this is used to log information related to
the Vertex tax calculations. This setting
also produces an XML file. Oracle
Support can assist with retrieval if the file
is requested by Oracle Development.
Error during Vertex file load (does not If the database contains corrupt
apply to SaaS customers) information, 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.
166
Appendix B: User Interface Customization

Customizing User Interfaces
Customers may rebrand Oracle-delivered user interfaces and customize them to fit their corporate needs.
In Release 8 and beyond of Oracle Sales Cloud and Oracle Human Capital Management Cloud (Oracle HCM
Cloud), a business system analyst who has been granted administrative privileges can select and apply one of
six user interface themes or customize these themes to include a unique company logo and watermark. The
business system analyst can also change the style and shape of buttons and menus by selecting from several
predefined options and can add unique company news and announcements to the announcement portion of the
home page.
Customizations like these can be made within the Settings functional area of the FUSE Simplified UI.
Changing UI Color
Changing the UI color may also be a good way for customers to distinguish between a production environment
and a test environment.
To change the color of the UI:
1. Click Settings.
2. In the Theme dropdown, select the desired color scheme.
167
3. Click Apply.
Customizing Fusion Application UIs Using Page Composer

Various customizations to the user interface are presented in this playlist hosted by Fusion Applications
Developer Relations. Please see the link below to access the short individual videos.
YouTube Video Playlist Related to Customizing Fusion Applications UIs Using Page Composer:
https://www.youtube.com/playlist?list=PL1ZiAfFIniZclvZFvJudjDYmkhmosK13A
168
Appendix C: PA Residency Certificate in the Portrait Gallery

The PA Residency Certificate form is available from the Portrait Gallery. This feature enables employees to view
and update their own information. The form will default the employee and employer information such as name,
address, SSN and employer FEIN.
To navigate to the form employees will:
1. Click on My Portrait.
2. Click on Manage Tax Withholding.
3. Select the PA line, and then Edit.
4. The PDF form will open up for the user to update the Resident and/or Work PSD codes.
5. Once, updated, scroll to the bottom of the form, and click the “I Agree” button.
6. Click Done.
169
Appendix D: Replacing the Preconfigured Payslip Template with a Custom

Template
Customers may wish to replace the preconfigured payslip template with a custom template. The same process
could be performed for modifying another preconfigured report template. For the payslip, Oracle is using one
customized template for both the online payslip and the printed payslip. To accomplish this, it is simply a
separate extract delivery option configured in the application. This entails setup with the applications side as well
as the BI side.
Customizing the Template

To customize the preconfigured payslip template:
1. Log into the BI Server and copy the preconfigured USOnline_Paylip template, located under the path:
/Shared Folders/Human Capital Management/Payroll/Payment Distribution/US
2. Open the preconfigured USOnlinePayslip template, and save it under a new name.
3. Make the required changes.
4. Open the Custom folder.
5. Select +Add New Layout.
6. Under Upload or Generate Layout, select Upload.
7. In the Upload Template File page, enter or select the following:

Field Name Value
Layout Name Free form field
Note:
The value you specify here will be required when
you set up and override the predefined payslip.
Template File Select the template you just modified
Type RTF Template
Locale English
170
8. Click Upload.
Configuring the Delivery Options for the Online Payslip

Once you have customized the template, you must replace the preconfigured payslip template.
1. Navigate to Workforce Management->Data Exchange.
2. Select Manage Extract Definitions.
3. Specify “Payslip” as the Name.
4. Select a US LDG.
5. Click Search.
6. Under Search Results, click Payslip.

7. In the Edit Extract Definition page, click the Extract Delivery Options folder.
If you don’t see the folder structure on the left, click Switch Layout.
171
8. Under Extract Delivery Options, click Add.

9. Add or select the following fields for the online payslip:
Field
Value
Name
Start Date 01-01-0001
Delivery Free form text
Option
Name
Output PDF
Type
Report This is the path of the report on the BI server. It must include the “xdo” extension.
For example: /Human Capital Management/Payroll/Payment
Distribution/US/USOnlinePayslip.xdo.
Note:
This value is the file path location and not the actual name. Because there is a
global payslip and a US payslip, you must ensure you are updating the US payslip.
Output Free form text
Name
172
Report Name of the template on the BI server

Layout or
Template
Name
Delivery Documents of Record
Type
Bursting /DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/REL_ACTION_I
Node D
Overridin US Online Payslip
g Delivery
Mode
10. In the Additional Details section, populate the following parameters with the corresponding values:
Field Name Value
Date From /DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/GLB_ARCH
_PR/GLB_PAY_ARCH_PR_PAYROLL/PAYROLL_PERIOD_START_DATE
Date To /DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/GLB_ARCH
_PR/GLB_PAY_ARCH_PR_PAYROLL/PAYROLL_PERIOD_END_DATE
Information /DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/GLB_ARCH
Text1 _PR/GLB_PAY_ARCH_EE_INFO/EMAIL_ADDRESS
Information US_PAYSLIP
Category
Date1 _PR/GLB_PAY_ARCH_PR_PAYROLL/PAYROLL_PAYSLIP_VIEW_DATE
Number1 _PR/GLB_PAY_ARCH_PR_PAYROLL/PAYROLL_ID
Number2 _PR/GLB_PAY_ARCH_PR_PAYROLL/PAYROLL_PERIOD_NUMBER
Information /DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/NET_PAY
Number3
Number5 _PR/GLB_PAY_ARCH_PR_INFO/GLB_ARCH_CBID/GLB_PAY_ARCH_CBID_I
173
NFORMATION/PREPAYMENT_RELATIONSHIP_ACTION_ID
Number6 _PR/GLB_PAY_ARCH_PR_INFO/GLB_ARCH_CBID/GLB_PAY_ARCH_CBID_I
NFORMATION/CALC_BREAKDOWN_ID
Document PAYSLIP
Name
Issued /DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/PAYMENT_
Date DETAILS/PAYMENT_DATE
Key Select this value from the picklist in the Attribute column, as it must reference the
correct object. To find this value, perform a search with the following criteria:
Field Value
Parent Data Group Global Archive Payroll Calc
Breakdown
Attribute Calculation Breakdown Identifier
Record Global CBID Information
Locale En_US
Person Id /DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/GLB_ARCH
_PR/GLB_PAY_ARCH_EE_INFO/PERSON_ID
Related /DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/REL_ACTIO
Objec Id N_ID
Related PAYROLL_REL_ACTION_ID
Object Id
Col
Related PAY_PAYROLL_REL_ACTIONS
Object
Name
System PAYSLIP
Document
174
Type
11. Click Save.
This completes the payslip delivery option configuration.
Configuring the Delivery Options for the Printed Payslip

Once you have configured the delivery option for the online payslip, you must do the same for the printed payslip.
1. In the Additional Details: Payslip section, select the name of the new Printed Payslip file created.
2. Under Extract Delivery Options, click Add.

3. Add or select the following fields for the printed payslip:
Field
Value
Name
Start Date 01-01-0001
Delivery Free form text
Option
Name
Output PDF
Type
Report This is the path of the report on the BI server. It must include the “xdo”
extension. Both the online payslip and printed share the same template file. For
example: /Human Capital Management/Payroll/Payment
Distribution/US/USOnlinePayslip.xdo.
Note:
This value is the file path location and not the actual name. Because there is
a global payslip and a US payslip, you must ensure you are updating the US
payslip.
Output Free form text
Name
Report Name of the template on the BI server
Layout
Delivery Printer
Type
175
Bursting /DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/REL_ACTIO
Node N_ID
Overriding US Printed Payslip
Delivery
Mode
4. In the Additional Details section, populate the following parameters with the corresponding values:
Field
Value
Name
Key Select this value from the picklist in the Attribute column, as it must reference the
correct object. To find this value, perform a search with the following criteria:
Field Value
Parent Data Group Global Archive Payroll Calc
Breakdown
Attribute Calculation Breakdown Identifier
Record Global CBID Information
176
Locale en_US
System PAYSLIP
Document
Type
5. Click Save.
6. In the Additional Details: Payslip section, select the name of the new Online Printed Payslip file created.

8. Click Submit.
When you run the Generate Payslip process, it substitutes the new custom template for the preconfigured Oracle
template.
BI Server Information
Refer to the screen capture below for the BI server location for the preconfigured online payslip.
177
Note:
There is more than one location for the Online Payslip. Ensure you are modifying the USOnlinePayslip.
When you modify the template, ensure you upload and select “English” as the language and not
“English(United States)”.
178
Appendix E: Customizing the Check Template for the MICR Codes

As each bank uses a different MICR code on their checks, you must configure the routing and bank account
numbers to ensure the Generate Check Payment process prints each of them correctly. The following table
illustrates the possible differences between Oracle Fusion’s default template and a bank’s:
Oracle Fusion Routing Number Account Number Check Number
XYZ Bank Check Number Routing Number Account Number
To configure how the MICR line appears on printed checks, you must modify the predefined check template.
The following is the preferred method for customizing the predefined check template. Alternatively you could
define a new delivery option to reference your own check template.
1. Log into the BI Server.
2. Copy the preconfigured US Check Writer Report template.
Find this template at:
/Shared Folders/Human Capital Management/Payroll/Payment Distribution/Cheque Report.xdo
3. Save the template into the Custom folder using the same directory structure as the seeded template:
/Custom/ Human Capital Management/Payroll/Payment Distribution
Keep the same .xdo and template name as the predefined version.
4. Open the copied template in Microsoft Word.
5. Use the Word tools to ensure the MICR line meets the requirements of your bank. Elements you may need
to change:
 Font size
 Order of the MICR line fields
 Adding any necessary leading zeros to the check number, routing number, and account number
6. Use Microsoft Word’s symbol library to insert or update any special characters. This symbol varies by bank.
The predefined template uses the following concatenation schema for the rounting number:
<?concat(' ',SOURCE_BANK/BRANCH_NUMBER,' ')?>
It uses the following for the account number:
<?concat(SOURCE_BANK/BANK_ACCOUNT_NUM,' ')?>.
This concatenation of the special characters enables it to show in the check writer report output.
7. If you need to insert or update the special characters in the MICR line:
a. Copy and paste the appropriate BI Publisher property for the appropriate field into a new blank Microsoft
Word document.
b. Place your cursor in the appropriate place.
c. Open the symbol library.
179
d. Select the MICR font. You may need to install this font.
e. Insert the symbol you need into the copied BIP property.
f. Copy and paste the BIP property from the new Word document into the modified check writer template.
Note:
These symbols may appear differently when you paste it into the BIP property.
g. Other things to consider:
 You may need to add or remove lines to control the positioning.
 You may need to adjust the left margin alignment.
8. Save your changes.
When you run the “Generate Check Payments” process the BI Publisher first looks for the template in the Custom
folder. If it does not find it there, it uses the predefined template location.
180
Appendix F: Adding a Signature File to the Check Template

There are two methods for including a signature GIF file on the check template. See Appendix E for
recommended steps for modifying the check template.
 Method 1:
1. Open the copied check template in the custom folder using Microsoft word.
2. Paste the signature.gif on the authorized signature line in the template.
3. Save your changes.
 Method 2:
This solution involves updating the signature.gif in a sub-template.
1. Create a new sub-template for thesignature.gif file.
2. Change the Check template to call the new sub-template.
3. Save the check template.
Note:
Refer to the Report Designer’s Guide for BI Publisher for further details on creating sub-templates.
181
Appendix G: Setting up a Regular Earnings Element to Reduce Regular

To create an element under Standard Earnings (primary) > Regular (secondary) that reduces regular:
1. Create your earnings using Standard Earnings primary classification and Regular secondary classification.
2. Change the processing priority of this element to 2100.
3. Complete the element definition, and submit.
4. In the Manage Balance Definitions task:
 For the Reduce Regular Earnings balance, create a new balance feed using your base element name.
Select the Pay Value input value with the Add option.
 For the Reduce Regular Hours balance, create a new balance feed using your base element name.
Select the Hours Worked input value with the Add option.
Ensure you have properly set the effective as-of date.
182
Oracle Fusion Human Capital Management for Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the
the United States: Implementation and Use contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
July 2016 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
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
183

Oracle Fusion Human Capital Management For US Implementation and Use White Paper PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Oracle Fusion Human Capital Management For US Implementation and Use White Paper PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Oracle Fusion Human Capital Management for the US: Implementation and Use

Guide (HR and Payroll)

An Oracle White Paper

Oracle Fusion Human Capital

Global Human Resources .................................................................... 11

Global Payroll Interface ........................................................................ 11

Global Payroll ....................................................................................... 12

Address Style and Settings .................................................................. 18

Verifying Geographies .......................................................................... 20

Configuring State Display Properties ................................................... 23

Defining Address Style Format Mapping for United States .................. 24

Viewing Geocodes for a Geography .................................................... 25

Manually Adding a Geography ............................................................. 25

Changing the Address Field Display Sequence ................................... 27

Creating Jurisdictions for Local Taxes ................................................. 34

Legal Reporting Units and Tax Reporting Units ................................... 36

Organization Structure Models Supported by the US Localization ...... 36

Creating Legal Entities ......................................................................... 37

Identifying the LDG ............................................................................... 38

Additional Reporting Information for Legal Employers and PSUs ....... 39

Creating Federal Tax Rules ................................................................. 45

Creating Regional Calculation Rules .................................................... 45

HCM Information .................................................................................. 54

Reporting Establishments .................................................................... 57

Calculation Cards ................................................................................. 59

State Unemployment Insurance Rate .................................................. 59

Legal Reporting Units ........................................................................... 62

Tax Reporting Units .............................................................................. 63

Deduction Elements ............................................................................. 64

Element Eligibility ................................................................................. 88

Employee and Employer Tax Elements ............................................... 90

Contribution Limits .............................................................................. 102

Balance and Feed .............................................................................. 102

Maintaining Person Information .......................................................... 111

Maintaining Employment Information ................................................. 112

Employee Roles Within Portrait Access ............................................. 114

Smart Navigation ................................................................................ 114

Employee Management of Document Print Preferences in My Portrait115

Manual Tax Card Creation ................................................................. 116

Changing the TRU for an Assignment................................................ 117

Wage Accumulation............................................................................ 117

Manage Tax Withholding in My Portrait ............................................. 117

Manage Tax Withholding using Smart Navigation ............................. 119

Other Considerations.......................................................................... 120

Supplemental Earnings Elements ...................................................... 121

Setting Up Employee Earning Distribution Overrides ................. 124

How QuickPay Is Processed .............................................................. 131

Submit the QuickPay Flow ................................................................. 132

Calculate and Verify Run Results ....................................................... 133

Processing International ACH Transfers ............................................ 133

Manage Person .................................................................................. 134

Manage Document Records ............................................................... 135

Baselining Employee Status After Implementation..................... 140

Appendix D: Replacing the Preconfigured Payslip Template with a Custom

Global Human Resources

Global Payroll Interface

2. Select Setup and Maintenance from the Navigator.

3. On the Implementation Projects tab, click Create.

8. Click Save and Open Project.

Product Extension Parameter

Address Style and Settings

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

2. Enter the necessary details in the Parameters section.