Showing posts with label Oracle Cloud Payroll. Show all posts
Showing posts with label Oracle Cloud Payroll. Show all posts

Sunday, 22 February 2026

Oracle Cloud Payroll - US Retiree Payroll Configuration

US RETIREE PAYROLL IN ORACLE CLOUD HCM — MUST-DO CONFIGURATION

This article is designed to help Oracle Cloud HCM practitioners implement US retiree payroll in a clean, auditable way. It focuses on practical configuration choices, common setup gaps, and testable outcomes—so teams can enable learning, reduce rework, and deliver reliable payroll operations.

This checklist is based on hands-on implementation patterns and guidance from Oracle documentation/support material, including:
  • Oracle Support Document ID 2461709.1 — “Oracle Fusion Human Capital Management for RETIREES US: Implementation and Use (v1.9)”
  • Oracle Cloud Human Capital Management for the United States: How do I perform tax filing through a third-party? KB160976
  • Audience: Payroll implementers, HCM functional consultants, payroll admins supporting US retiree pay
  • Scope: US retirees paid via Oracle Cloud Payroll (commonly pension/annuity payments; often reported via 1099-R depending on your program design)

————————————————————————————————————

Retiree payroll has a few “small” setup decisions that create big downstream impact: tax card creation, TRU/PSU structure, registrations, reporting card associations, and address quality. If you get right early, year-end, reconciliation, and ongoing maintenance become predictable.

————————————————————————————————————

SECTION A — FOUNDATION (NON-NEGOTIABLE)

If you are already payroll customer running employee's payroll then this would be already configured.

A1) Set the United States Selected Extension correctly

  • Confirm your US “Selected Extension” setting aligns with how you plan to process retirees (HR-only vs payroll-enabled configuration).

A2) Address Validation + geographies maintenance (strongly recommended)

  • Enable Address Validation (if your governance permits).
  • Establish an operational cadence to refresh geographies (as applicable).

————————————————————————————————————

SECTION B — ORG STRUCTURE (BUILD RETIREE BOUNDARIES EARLY)

B1) Separate retiree PSUs from employee PSUs (recommended baseline)
  • Create retiree Payroll Statutory Units (PSUs) separately from employee PSUs where your business/legal reporting model supports it.
B2) Create retiree TRUs separately; lock down distribution code governance
  • Create retiree TRUs separately from employee TRUs.
  • If your program requires different 1099-R distribution codes, segment TRUs accordingly.
  • Governance rule: do not change TRU’s 1099-R distribution code after creation—create a new TRU if the code changes.
        Manage LRU HCM Information => Enter the distribution code






————————————————————————————————————

SECTION C — TAX REGISTRATIONS (REQUIRED FOR STABLE PAYROLL PROCESSES)

This configuration is same as your regular employee(Non-Retiree) payroll configuration.

C1) US Federal registration at LRU level (FEIN)

  • Create the US Federal Tax registration at the LRU level.
  • Enter the Employer FEIN.

C2) State registrations (as applicable)

  • Populate state registrations for jurisdictions where you withhold/report, based on your compliance model and filing responsibilities.

————————————————————————————————————

SECTION D — TRU CALCULATION RULES (PUT WITHHOLDING LOGIC IN THE RIGHT PLACE)

This configuration is same as your regular employee(Non-Retiree) payroll configuration.

D1) Create TRU calculation rules card

Create “Calculation Rules for Tax Reporting and Payroll Statutory Unit” at the TRU level.

D2) Flat-rate override governance (if your retiree program uses it)

Recommended override priority (high → low)
1. Retiree person tax card overrides
2. TRU-level overrides
3. Tax engine defaults

Note –

Retiree payments that are subject to 1099-R rules are not subject to SUI, SDI, FLI, Social Security, or Medicare taxes. Therefore, the payroll process does not calculate them.

————————————————————————————————————

SECTION E — CONSOLIDATION GROUP AND PAYROLL GROUP

E1) It would be better to create separate consolidation group and payroll definition for retiree payroll processing

————————————————————————————————————

SECTION F — RETIREE TAX CARDS (ENSURE THEY AUTO-CREATE AND STAY CORRECT)

F1) Confirm the retiree tax card model
  • Validate the retiree tax card behavior for your program (commonly “Tax Withholding for Pensions and Annuities”).
F2) Validate auto-creation is working (don’t assume)

F3) State-tax edge case validation

When you onboard or convert employee to retiree; you will see below calculation created and TRU association created auto




————————————————————————————————————

SECTION G — REPORTING INFORMATION CARD (OFTEN MISSED, HIGH IMPACT)

G1) Confirm TRU components are associated to the correct assignment

  • Validate that Reporting Information Card components created per TRU are correctly associated to the retiree assignment number—especially when multiple TRUs exist.


————————————————————————————————————

SECTION H — RETIREE ASSIGNMENT (MINIMUM REQUIRED FIELDS)

This data point is same as your regular employee(non-retiree) payroll data point.

H1) Retiree must have a payroll-eligible assignment

  • Payroll relationships are assigned
  • Ensure retiree assignment is Active and Payroll Eligible

————————————————————————————————————

SECTION I — HOME ADDRESS, LOCATION AND WFH FLAG FOR RETIREES (WHAT IT MEANS IN ORACLE)

Key point (clear definition)

Retirees aren’t “working,” but Oracle still requires a Work Location on the retiree assignment. For WFH/Remote retirees, treat Work Location as a required data field for consistency and reporting—not as a local tax driver.

I1) All Retirees must have valid US Home Address for payroll processing. Retirees can have overseas mailing address for communication.

I2) Create a dedicated retiree remote location and assign it to all retirees and check 'Work From Home' flag for them.




————————————————————————————————————

SECTION J — PAYMENTS (DIRECT DEPOSIT MUST BE OPERATIONALLY SUPPORTED)

This data point is same as your regular employee(Non-Retiree) payroll data point.

J1) Run prerequisite process for new retirees
  • Run “Maintain Party and Location Current Record” before entering personal payment methods (for newly onboarded retirees).
J2) Enter payment methods
  • Use “Manage Personal Payment Methods” to add direct deposit details.

————————————————————————————————————

SECTION K — KNOWN CONSTRAINTS (DESIGN AROUND THEM EARLY)
  • Local taxes for retirees may not be supported in retiree processing models; plan your retiree withholding accordingly.
  • Involuntary deductions may not be supported for retiree processing; define an alternative approach if required.
  • Confirm territory/jurisdiction scope early if you have retirees outside standard US states.

————————————————————————————————————

Finally Let's add earning elements and run QuickPay to see the results








————————————————————————————————————

Disclaimer: 

The checklist provided here focuses on foundational setup patterns and common “must-do” configurations for US retiree processing in Oracle Cloud HCM. Actual implementations can vary by retiree plan design, bargaining agreements, legal/tax requirements, and reporting needs. Most projects also require additional configuration, including elements and balance definitions, fast formulas, eligibility, costing rules, payroll calendars, retro and correction processes, and integrations with third-party or downstream systems (e.g., tax services, payment files, benefits providers, and financial/GL systems) to deliver end-to-end processing and statutory reporting.

Wednesday, 24 January 2018

Payroll Batch Loader Error Query



select ml.*
from pay_bl_message_lines_vl ml
,    pay_batch_lines bl
,    pay_batch_headers bh
where bh.batch_id = bl.batch_id
and   bl.batch_line_id = ml.source_id
and   bh.batch_name = 'BATCH NAME'
and   bl.batch_line_status = 'E';


Full Query for all PBL errors with batch name, task name, task action name, assignment number and error message


SELECT pbh.batch_name,
       pbh.legislative_data_group_id,pbt.display_task_name,pbta.display_task_action_name,
pivot_line_value_data.action_parameter_name1,pivot_line_value_data.action_parameter_value1,pivot_line_value_data.action_parameter_name2,pivot_line_value_data.action_parameter_value2,
       pbmlv.message_text
FROM
(SELECT batch_line_id,
     MAX(decode(rn,1,display_action_parameter_name))
action_parameter_name1,MAX(decode(rn,1,action_parameter_value))
action_parameter_value1,
     MAX(decode(rn,2,display_action_parameter_name))
action_parameter_name2,MAX(decode(rn,2,action_parameter_value))
action_parameter_value2,
     MAX(decode(rn,3,display_action_parameter_name))
action_parameter_name3,MAX(decode(rn,3,action_parameter_value))
action_parameter_value3,
    MAX(decode(rn,4,display_action_parameter_name))
action_parameter_name4,MAX(decode(rn,4,action_parameter_value))
action_parameter_value4
 FROM ( SELECT batch_line_id,
               action_parameter_name,
       action_parameter_value,
       display_action_parameter_name,
               row_number() over (partition by batch_line_id
                          order by batch_line_id,
  action_parameter_name ) rn
          FROM (SELECT pbavl.element_name action_parameter_name,
               pbavl.parameter_name display_action_parameter_name,
       pblv.action_parameter_value,
       pblv.batch_line_id
FROM pay_task_parameters_vl pbavl,  pay_batch_line_values pblv
WHERE pbavl.base_task_parameter_id = pblv.action_parameter_id
AND pbavl.display_flag <> 'N' ) 
          )
GROUP BY batch_line_id) pivot_line_value_data,
                        pay_batch_lines pbl ,
                  pay_batch_headers pbh,
                        pay_bl_message_lines_vl pbmlv,
PAY_BL_TASK_ACTIONS_VL pbta,PAY_BL_TASKS_VL pbt
WHERE pivot_line_value_data.batch_line_id = pbl.batch_line_id
AND pbl.batch_id = pbh.batch_id
AND pbl.batch_line_id = pbmlv.source_id
AND pbl.batch_line_status = 'E'
AND pbh.batch_name like '%Pay%%%'
AND pbt.task_id=pbta.task_id
and pbl.task_action_id=pbta.task_action_id

Saturday, 21 January 2017

Fusion HCM New Hire Process - USA


Important Points -

(1) Address

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.

(2) Marital Status, Ethnicity, and Veteran fields in the Legislative Information section

Note: The Ethnicity and Veteran fields are required for EEO and VETS reporting.

(3)  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.
.
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.

Field Name Description :
New Hire Status

- Identifies the employee’s employment status as pertains to the New Hire report:

Different Values

(1) Include in the New Hire report :Employee is to be included in the next run of the New Hire Report.
(2) 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.
(3) Excluded from the New Hire report : Employee is not included in the report.


= = = =

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.
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.

====

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.
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.
3. Search for and select the person record.
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.
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:

1. Navigate to the Payroll Calculations work area.
2. Select Manage Calculation Cards.
3. Search for and select the person record.
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.
10. Click Save and Close.
This end dates the record for the assignment associated with the previous TRU and creates a new record for the new TRU.


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.
    This displays the Employee Withholding Certificate page.

2. Click Edit. This is available for both the federal and state level.

When the federal employee withholding certificate is accessed, 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. For those states that do not follow federal, the specific state’s editable PDF form will be displayed. 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.

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:

1. Determines the resident and work tax addresses based on the following hierarchy:

Address Type                                                 ---- Priority

Location address                                            ----   4
Location override address                              ----   3
Assignment-level location override               ----   3
Work at home flag = Yes                               ----   1 (overrides assignment, location override, and                                                                                           location)

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.