session 1020 multiple jobs processing in hrms 8 - part i march 20, 2001 dave dresselhouse ...

Session 1020Multiple Jobs Processing

in HRMS 8 - Part I

March 20, 2001

Dave Dresselhouse

PeopleSoft

Agenda

This is a 2-part presentation...

Part I (2:30 - 3:30) Multiple Jobs Basics / Overview HRMS Payroll for North America Pension Administration

Break (3:30 - 3:45)

Part II (3:45 - 4:45) Benefits Enrollment and Deductions Benefits Administration / Eligibility

Multiple Job Basics / Overview

PeopleSoft HRMS Product Line

Company: UniversityPosition: Professor

Paid: WeeklyJob: #1

Company: UniversityPosition: DeanPaid: Monthly

Job: #3

Company: HospitalPosition: Physician

Paid: MonthlyJob: #4

Company: UniversityPosition: Researcher

Paid: WeeklyJob: #2

Employee

All jobs don’t have to be “concurrent”:

Professor

Researcher

DeanTime

Physician



EMPLOYMENTEmpl_Rcd: #0




PERSONAL_DATA

Representation of multiple jobs in the database:

JOBEffdt: 1/1/98Action: HIR

JOBEffdt: 2/1/99Action: XFR

JOBEffdt: 8/1/99Action: DTA



JOBEffdt: 12/31/98

Action: TER



Why Use Multiple Jobs?

Concurrent employment in multiple companies (or legal entities) within a corporation/organization Jobs for different FEINs need to be kept separate

Need to distribute expenses differently for each job held in a single companye.g. Salary and Benefits expenses

If Benefits eligibility can vary by job, or group of jobs

Pension Administration requires multiple jobs


PeopleSoft HRMS

PeopleSoft HRMS

PeopleSoft HRMS Enhancements

What’s new in HRMS?

“Primary/Secondary” Job Indicator

FTE tracking/visibility across multiple jobs

Job inquiry across multiple jobs

Benefit Record assignment

Reports respond to “Primary Job”

PeopleSoft HRMS

Primary/Secondary Job Indicator

PeopleSoft HRMS

Established on the Job record

Effective dated

Used mostly for reporting Real-World implementation requires that we allow

more than one primary job as an exception Due to security implementations On-Line warning Audit report

Cross-Job FTE Tracking

PeopleSoft HRMS

Visibility of totals across all jobs as of Effective Date

Standard Hours FTE

Note that totals are not stored

Inquiry Across Multiple Jobs

PeopleSoft HRMS

View of “non-sensitive” data for all jobs as of Effective Date

Benefit Record / Program Assignment

PeopleSoft HRMS

Benefit_Rcd# = Empl_Rcd# relationship broken

Benefit Record can be directly entered in normal page flow

Benefit Record for a job can be changed at any time

Benefit Program is not required if all jobs in Benefit Record are managed by “Other” pay systems

HRMS Reports

PeopleSoft HRMS

All reports that derive data from one job have been modified to respect the new “Job Indicator” field

In the case of “overlapping” primary jobs: Lowest Active Empl_Rcd is used If all jobs are terminated:

Lowest Empl_Rcd is used

PeopleSoft Pension Administration


Enhanced Multiple Job functionality affects four major areas of Pension Administration:

Alias resolution

Plan Eligibility

Consolidations

Service

PeopleSoft Pension Administration Enhancements


Multiple Concurrent Jobs processing requires new method for resolving Database Aliases

In earlier releases, Aliases were resolved on Job 0

For Multiple Concurrent Jobs enhancement it was necessary to establish the employee’s Primary Job in order to resolve Aliases

User-defined criteria for Active Job and Eligibility are used to identify Primary Job


Alias Resolution

Primary Job for Pension can be directly specified

Effective Dated


Alias Resolution

Primary Job is determined in the following order of precedence:

Override Job (user defined)

Lowest Eligible Active Job

Lowest Eligible Job

Lowest Active Job

Lowest Job


Alias Resolution

Plan Eligibility

First, an eligibility timeline is established for each job

Using individual job eligibility timelines, a blended timeline of eligible and non-eligible status periods, is created across multiple jobs

Based on the blended timeline, appropriate definitions are applied


Plan Eligibility

Multiple Jobs Eligibility Timeline

‘84 ‘86 ‘88 ‘90 ‘92 ‘94 ‘96 ‘98 ‘00

Job

0

1

2

3

4

5

Blended ELIGIBILITY TIMELINE = Eligible

= Ineligible

First, an Eligibility Timeline is created for each job.Then a blended timeline is created.

Job 3 is Salary Plan & Ineligible

Example

Mary Complex:

5 Multiple Jobs

Plan: USPEN3

Let’s look at the rest of Mary’s Job History

PeopleSoft Pension Administration2/24/84 - 8/4/87

and

12/14/87 - 7/15/92

Job

0

1

2

3

4

$

Multiple Jobs Consolidated Earnings

Annualized‘ 91 ‘92 ‘93 ‘94 ‘95 ‘96 ‘97 Earnings

Job 3 is Salary Plan: No Eligible Earnings

$

15,600

7,800

24,960

45,000

39,000

48,3

60

41,1

14

2,78

2

0

9,3

77

24,1

48

$15,600

7,800

24,960

$48,360

0


‘ 91 ‘92 ‘93 ‘94 ‘95 ‘96 ‘97

Multiple Jobs: Service

Job

0

1

2

3

4

5

Multiple Jobs: Service / Eligible Jobs Only

Job 5 Begins After 1997

Service 1 .083 0 0 .25 .6221

Job 3 is a

Salary Plan:

No Eligible

Service


PeopleSoft Payroll for North America


What’s new in Payroll for North America?

Improved “Single Check” processing

Additional balance keys

Improved General Deductions enrollment and processing

FICA status tracked at the Job level

PeopleSoft Payroll for North America PeopleSoft Payroll for North America

Enhancements

Combine as many jobs as possible onto a single check

Increases accuracy of Tax withholding - prevents under-withholding

Reduced processing costs associated with the production, distribution and reconciliation of “extra” checks

Less confusing to the employee


Improved “Single Check” Processing

Which jobs can be combined?

Same Company Same Pay Period End Date Either On or Off Cycle Same FLSA Period All paysheets created and ‘OK to Pay’ Same or Different Benefit Records Same or Different Paygroups, aligning Pay End

Dates






Paid: Semi-M (SM1)Empl_Rcd: #0

Benefit_Rcd: #0

Company: UniversityPosition: Dean

Paid: Monthly (MO1)Empl_Rcd: #2

Benefit_Rcd: #2



Benefit_Rcd: #3



Benefit_Rcd: #1

Employee

$ $ $ $

Release 7.X

Pay End: 3/31/2001





Benefit_Rcd: #0

Company: UniversityPosition: Dean


Benefit_Rcd: #2



Benefit_Rcd: #3



Benefit_Rcd: #1

Employee

$ $

Release 8.X

Pay End: 3/31/2001



3/15/2001Semi-Monthly

3/31/2001Monthly

Semi-Monthly

Empl_Rcd 0, BenefitRcd 0






$

$

$

$

$

$

$

$

$

Pay End Jobs Paid 7.X Checks8.X Checks

Release 8.X / 7.X Comparison



Controls single check processing when ‘Single Check for Multiple Jobs’ flag is checked

Identifies Paygroup where paysheets will be consolidated

Determines General Deduction processing

PaygroupA

PaygroupB*

PaygroupC

PaySheet

PaySheet

PaySheet

ConsolidatedPay Sheet *Primary

Pri

mar

y P

ay G

rou

p


How do you enable “Single Check” processing?

Company Table - “Single Check for Multiple Jobs”

Employees must be assigned to a Primary Paygroup Even if all jobs are in the same paygroup! Should be most frequently-paid pay group for the employee


Additional Balance Keys

Additional keys were added to the Balance tables

Finer level of detail to support multiple jobs Earnings - Now tracked byJob (Empl_Rcd) Deductions - Now tracked by enrollment (Benefit Record)

No change to General Deductions General Deductions are no longer job-specific


Improved General Deduction Enrollment


Disconnect General Deductions from Benefit Programs

General Deductions no longer defined in a Benefit Program Defined at the Company level

Enrollments no longer posted at the Job level Employee is enrolled at the Company level All jobs in the same Company share the same enrollment

No need to maintain enrollments as jobs come and go

Improved General Deduction Enrollment


University

Hospital





Parking

Parking

Company Jobs 7.X 8.X

Parking

Parking

Parking Parking

Enrollments

Release 8.X / 7.X Comparison

Improved General Deduction Processing

Union Dues and Multiple Jobs

General Deduction can be flagged as “Union Dues”

Union Dues are deducted only if a job enrolled in the Union is being paid on the check


Improved General Deduction Processing

Deduction Frequency

Can now specify whether deduction should be taken from every check, or just one particular check

If not taken on each check… Taken on Primary Paygroup check If no Primary Paygroup, taken on check with highest paygroup priority of all paygroups the employee participates in


FICA Status Tracking

FICA Status can be identified for each Job

Moved from Fed_Tax_Data to Job Employee can hold a mix of FICA Exempt/Non-

Exempt jobs


Issues

Known Issues in PeopleSoft8

HRMS - none Pension - none Payroll for North America

“Single Check” setting cannot be overridden at the employee level

Difficulty adding/changing multiple tax locations in the same state

Difficulty with General/Benefit deduction overrides


End of Part I - Multiple Jobs in HRMS

Part II - Detailed look at Base Benefits, Benefits Administration and Deduction Calculation for Multiple Jobs


Session 1020Multiple Jobs Processing

in HRMS 8 - Part I

March 20, 2001

Dave Dresselhouse

PeopleSoft

session 1020 multiple jobs processing in hrms 8 - part i march 20, 2001 dave dresselhouse ...

Documents

multiple jobs job inquiry

weekly job

monthly job

hir job effdt

job record effective

xfr job effdt

dta job effdt

ter job effdt