PeopleSoft NA Payroll or HCM Functional Training:

PeopleSoft NA Payroll or HCM Functional Training:

Please send email to nandu.peoplesoft@gmail.com for enrolling the course or call me @8897575066. Please see below HCM Functional training AGENDA.

Payroll for North America training AGENDA.

This is an online Functional Training. Training goes through webex and explain you with real time execution of processes with examples. Recordings and documentation will be given once the training is done.

Tuesday, June 28, 2011

Peoplesoft Certification and Interview Questions

How to disable auto-numering feature in Peoplesoft

the Installation table fill the the last assigned value with 9's.

Eg:- Last Employee ID Assigned field on the Last ID Assigned tab should be filled with only 9's.

Employees table - PER099 Process in Peoplesoft

PER099 - Employees Record

PER099 - This Application Engine program re-fresh the snapshot of the employee data stored in the in PS_EMPLOYEES table and PS_EMPLOYEES_LNG

Employee - EMPLOYEES is a table populated by PER099 AppEngine process.

It is a snapshot of emploees' personal/demographic data, employment data, and job/salary data as of the date indicated when the program is run.

This table is primarily for reporting. Only employees with EMPL_STATUS (A,P,L,S,W) are included with all their EMPL_RCDs and the most current JOB row as of the ASOFDATE.

EMPLOYEES_LNG is the language record related to EMPLOYEES.

A related language record enables text fields on a table to be translated into various languages for use in other countries.

Note :- It is not preferred to modify these record during implementation. If you need custom fields for the reporting purpose create the child record with the same set of keys and the custom fields in to these and create Job process including the PER099 and custom process which populates custom field in the child record. Simple join on the Employees record and custom child record will give you all the fields for reporting purpose.

EMPL_RCD is Benefit Record in Base Benefit Records

BENEFIT_NBR field is not implement in the peoplesoft base benefit records.
EMPL_RCD in the Base Benefit Tables doesn't store EMPL_RCD instead store the Benefit record Number and Benefit number (BENEFIT_NBR) field in these records are dummy ( not implemented )and they always store zero. It's seems to be some sort of the design flaw in the Peoplesoft.

All the Base Benefit (Benefit Program participation , Health Benefit ..etc )
record's schema shows that it is keyed by EMPL_RCD. This is not logically or functionally accurate. Throughout all of Base Benefits, when in the context of benefit enrollment, EMPL_RCD must be interpreted as an alias for BENEFIT_RCD_NBR. All benefit enrollment-related records are logically keyed by BENEFIT_RCD_NBR, so here EMPL_RCD actually contains the value of the appropriate BENEFIT_RCD_NBR. It is CRITICAL that all joins, comparisons, and updates to this record be against BENEFIT_RCD_NBR. Thus a typical driving join for benefit participation is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_BEN_PROG_PARTIC.EMPL_RCD, and a typical join for benefit enrollment is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_HEALTH_BENEFIT.EMPL_RCD. The security and search views used in Base Benefits perform this "mapping" internally.

Primary Jobs in Peoplesoft - HR & Base Benefits

Primary Jobs in Peoplesoft
There are 2 types of the Primary Jobs in the Peoplesoft HCM
1) HR - Primary Job Indicator in the Job data component.
2) Benefits - Primary Job Indicator.
One of the Employee job will be considered as the HR -Primary job for an employee and this is mainly for reporting purpose.

One of the Employee Job will be considered as the Benefits - Primary Job for Jobs under particulary Benefit Record number of an employee. If employees' Jobs are assigned to more than one Benefit record number and for each set of the Employees' Jobs under the particular Benefit record number one Benefits Primary Job should be selected.

Job - Data - Benefit Program Participation Page can be used to set the Benefit Record number.

Note : - Benefit Record Number is Zero by default. You manually change this field when appropraite. Because you are maintaning an effective-dated history of primary jobs benefits according to a set of strict rules , don't change the benefit record number of an existing job.
Doing so invalidates the primary job inicators that reside on the effective - dated primary jobs table and can result in erroneous processing within Benefits Adminstration and payroll for north america, resulting in abnormal termination of some processes.

Multiple Job Options can be set in the below Component.
Setup HRMS > Product Releated > Base Benefits > Multiple Job Options > Mutliple- Job optns

Following page can be used to view and update an employee's primary Job flag inculde deduction flag.
Benefits > Maintain Primary Jobs > Maintain Flags > Primary Jobs Flags

Primary Jobs table, Which is automatically created when ever a job is added using the Add concurrent Job pages updated whenever the job is terminated, based upon rules that you define in the multiple- Job optns (multiple Job options) page.

Primary Jobs table has following flags as well.

Include Eligibility : For Benefits Administration only. Select this check box if you want this job to be included by the system when determining the employee’s benefit eligibility.

Include Deductions: Select this check box if you want this job to be included when the system calculates the employee’s benefit deduction and coverage.

Why Benefits Primary Job is requried.
1) Determine to which Job the system applies the benefit deducation.
2) Identify the job that will provide the service date and the termination date.
3) Search record on all the Benefits search page shows only the jobs which has primary job flag is selected.

Automatically Building Primary Job Data for Multiple Employees
Run the Primary Job Utility process whenever you add a new employee population to the database through an external interface or database load (such as when implementing employee groups in phases or acquiring another company).

Benefits > Maintain Primary Jobs > Rebuild Primary Job Flags > Primary Job Maint
Process Name :- BN_BEN500_AE
When the utility runs, all existing data for the indicated employee population (if any) in the Primary Jobs Table is deleted. For each employee, a new effective-dated entry is made, assigning the primary job designation to the lowest active employee record within a benefit record number. Primary Job information is created for a time span bounded by the earliest and latest job effective dates for all jobs within a benefit record. If all jobs within a benefit record are terminated, the job with the lowest employee record is designated as the primary job.

Warning! All manual changes made through the Primary Jobs Flags page for the selected employee population are lost, because the complete Primary Job history is rebuilt for each employee.

Calculating Benefits Deductions for Multiple Jobs

Calculating Benefits Deductions for Multiple Jobs
Set Up HRMS > Product Related > Base Benefits > Rates and Rules >Calculation Rules Table > Calculation Rules

When calculating benefit deductions or coverage amounts based on the employee’s salary you need to determine which job salaries to use. You can calculate deduction and coverage amounts based on:
• Primary: The salary from the Primary Job
• Flagged BR: The sum of the salaries from a group of jobs within the same benefit record number selected for deduction processing
• All Flagged: The sum of salaries across all benefit record numbers selected for deduction processing.

Note. The Combined Salaries check box and Grouping Method on the Calculation Rules page along with the employee’s Include Deductions flag from the Primary Jobs Flags page determine the deduction or coverage amount for salary based plans.

Coverage end date in Benefit Enrollment

Coverage End date (COVERAGE_END_DT) in Benefit Enrollment tables.
The Coverage End Date is a legacy field from a very early release of PeopleSoft that is no longer used.  It is not populated by any online or batch process.

A new row inserted into the Health Benefit Enrollment with Coverage Elect of 'W' for Waive and 'T' for Terminated could indicated end of coverage and the Coverage Begin Date along with the Effective Date are used to identify the date coverage ended.
  When you insert a new Coverage Begin Date, the prior coverage is assumed to be ended the day before.

For example,

Single Coverage, Effective 1/1/2009
Family Coverage, Effective 3/1/2009 (assumed single coverage ended on 2/28/09)

How to use Verify Search to find applicants using the keywords

Find the resumes applicants based on the keywords.
Search the resumes in peoplesoft.

Recruiting > Administration > Build Applicant Index

An application engine program can be executed to run the Verify search Index to search the applicants.

under the applicants status select the group that needs to be indexed. select the index
C:\tmp for NT and /temp for UNIX scheduler.

execute the process HRS_SRCH_IDX to create the search index in the PS_HOME/data/search/HRS_ResumeText/

If the application servers and process schedulers are on separate boxes then additional steps need to be taken so that the application servers have access the files created under the PS_HOME\data\search\HRS_ResumeText\%DB NAME% directory

These files can be copied to app server as well.

To find the applicants

Recruiting > Find Applicants
In the Resume and Application Search section enter word that you are looking for in the resume in Enter Keywords field.

Peoplesoft Base Benefit Tables

Base Benefit Tables

PS_BEN_PROG_PARTIC - EE Benefit program participation.
PS_BENEFIT_PARTIC - Ben Plan type enrollment control
PS_BENEF_COMMENT - Benefit Comments

Dependent Details table

PS_DEPENDENT_BENEF - View Dependents/Beneficiaries
PS_DEP_BEN - EE Dependents/Beneficiaries
PS_DEP_BEN_EFF - EE Dependents Details EFFDT
PS_DEP_BENEF_VW - EE Dependent Only View
PS_DEP_BEN_ADDR - EE Dependent Address details
PS_BEN_NAME - EE Dependent Name
PS_DEP_BENEF_NID - Dependent / Benef National ID s
PS_DEPENDENT_PHONE - Dependent/Benef Phone Numbers

Health Plan Tables – Plan types – 1%

PS_HEALTH_PLAN_TBL - Health Plan Attributes Table
PS_HEALTH_PLAN_VW - Health Plans types View with its long descr plan type LIKE ‘1%’
PS_HEALTH_PLAN_LNG - Health Plans types view with its long descr lng plan type like ‘1%’

PS_HEALTH_BENEFIT - Health Benefits EE Elections
PS_HEALTH_DEPENDNT - Health Benefits EE Dependent Elections

PS_HEALTH_VW - EE Current Health Elections

Savings Plan Tables – Plan types - 4%


PS_SAVINGS_PLN_TBL -Savings Plan Attributes Table.
PS_SAVINGS_INV_TBL - Describing a specific investment option
Available within a Savings Plan type.
PS_ SAVINGS_PLN_VW -Savings Plan types view with its long description

PS_SAVINGS_PLAN -Savings Plan Enrollment Table.
PS_SAVINGS_BENEFIC -Savings Plan Beneficiaries.
PS_SAVINGS_INVEST -Savings Plan Enrollment Investment option.
PS_SAVINGS_PLAN_VW -Savings Plan Enrollment view

Life Plan Tables – Plan types - 2%

PS_LIFE_ADD_TBL -Life AD/D Ben Plan Parameters
PS_LIFE_PLAN_VW -Life AD/D Plan type views

PS_LIFE_ADD_BEN -EE Life AD/D Benefit Enrollment
PS_LIFE_ADD_BENEFC -EE Life AD/D Beneficiaries
PS_LIFE_VW -EE Current Life AD/D Benefits

FSA Plan Tables – Plan types - 6%

PS_FSA_BENEF_TBL -FSA Benefit Plan Parameters
PS_FSA_PLAN_VW -FSA Plan Type with its long description.

PS_ FSA_BENEFIT -EE FSA Benefit Enrollment View
PS_FSA_BENEFIT_VW -EE FSA Benefit Enrollment View

Retirement Plan Tables – Plan Types – 7%

PS_RTRMNT_PLAN_TBL -Retirement Plan Attributes Table
PS_RTRMNT_PLAN_VW -Retirement Plan types view

PS_RTRMNT_PLAN -EE Retirement Enrollment Table
PS_RTRMNT_VW -EE Current Retirement Benefits

Simple Plan Tables – Plan Types – A%

PS_SIMPLE_BENEFIT - EE Simple Benefits Plans Enrollments
PS_SIMPLE_PLAN_TBL - Plan attributes table.
PS_SIMPLE_PLAN_VW - Simple Plan Types view with long description.

Disability benefit plan table


PS_DISABILITY_BEN EE Disability Ben Enrollments
PS_DISABILITY_VW EE Current Disability Bens

Peoplesoft HCM Process - Scheduled process

HR_PERSDATA Application Engine - Updates the PERSONAL_DATA snapshot table with future dated entries as they become effective.

NAME_DISPLAY Application Engine - Refreshes the NAME_DISPLAY and NAME_FORMAL fields in all records with the NAME_GBL_SBR. Use when the criteria used to change these fields is changed.

PER099 Application Engine - Fill EMPLOYEES Table.

PTAF_NEM Application Engine - PTAF_NEM - Approval Framework Escalation App Engine.           AWE Workflow escalation process.

SCRTY_OPRCLS Application Engine - SCRTY_OPRCLS - Updates the SJT_OPR_CLS security Join Table.

SCRTY_SJTDLY Application Engine -  Nightly update for SJT Records -  Update of all effdt rows that have become current as of this data.

HRS_AM Application Engine - Applicant Search Auto-Match -Recruiter Applicant Search auto-match process.

HRS_DUPE_PRC Application Engine - Find Applicant Duplicates - Finds applicant duplicates given certain criteria.

HRS_JOB_AGNT Application Engine - Job Agent - Run the Job Posting Search Agent process.

HRS_JSCH_IDX Application Engine -Verity based Job Posting Index build process.

HRS035 SQR Report - Application Analysis (USA).

PER506 SQR Report - Department Tbl & Departmental - This report lists any departments that you have created in the Department Tree but have not yet added to the departmental security tree, It also lists any changes in departments since the effective date of the current security tree.

PER900 SQR Report - Core HR Data Integrity Audit. - Audit of the CORE HR Tables for Data Relationship Integrity.

PSPBARUN - Cobal Job - For the Benefit Administration - scheduled to run twice each night with some custom pre and post processes.

Important PeopleSoft HCM processes

1) Refresh the EMPLOYEES table.
2) Refresh the Personal Data Process.
3) Refresh the Personal Data table with future-dated data.
4) Refresh name display values.
5) Audit Human Resources data for integrity.
6) ID Change.
7) ID Delete.
8) ERN Delete process.
9) Refresh Compensation.



Set Up HMRS > System Administration > Database Processes

1) PERS_REFRESH – Refresh Personal Data Process. Based on the setup in the Personal data setup component. Personal data record will be refreshed. Process updates the current data asof the Current date / System date. What fields are populated is configurable in the personal data setup component.

Record: PS_PERSONAL_DATA
Setup Record:- PS_PERSON_DT_SETUP.













2) HR_PERSDATA - Refresh the Personal Data table with future-dated data. This process updates


Personal data table with all the PERS_DATA_EFFDT, NAMES, and ADDRESSES (optional) when that data becomes effective. This is should be scheduled as a nightly process in order to catch changes every day.


3) PER099 - Refresh EMPLOYEES Table. Refresh the PS_EMPLOYEES snapshot table as of the selected date or current date. This process also updates the PS_EMPLOYEES_LNG.


4) Refresh all records with the NAME_DISPLAY and NAME_FORMAL fields to reflect changes made to the People Code definition of those fields. You can choose to update records with all name format types or just with one name format type.


It has following options to choose from.


                                                                                                   
5) HRAUDIT - Audit Human Resources data for integrity.- Core HR Data Integrity. PER900. Initiate the Core Human Resources Data Integrity Audit.


Following things are audited.

• Persons were found in PERS_DATA_EFFDT that do not exist in PERSON
• Persons were found in PERSON that do not exist in PERS_DATA_EFFDT

• Persons were found in EMPLOYMENT that do not exist in PERS_DATA_EFFDT

• Persons were found in JOB that do not exist in EMPLOYMENT

• Persons were found in EMPLOYMENT that do not exist in JOB

• Persons were found in JOB that do not exist in PERS_DATA_EFFDT

• Persons were found in JOB that do not exist in JOB_JR.

• Persons were found in JOB_JR that do not exist in JOB.

• Persons were found in PERSON that do not have a Primary Name in NAMES.

• Persons were found in NAMES that do not have record in PERSON.

• Persons were found in ADDRESSES that do not have record in PERSON.

• Persons exist in DISABILITY that does not exist in PERSON.

• Persons were found in DIVERS_ETHNIC that do not exist in PERSON.

6) Change ID / Delete ID Process – HR_PER502 - This process is used for the correction of the employee ID it updates the all tables with new employee ID. This also used for the deleting ID as well. ID Delete control component contains the exclusion list of the records.
 
7) Delete ERN Process - HR_EERCD_DEL – This process is used to delete the Employee record Number or Empl RCD of an employee.
ERN Delete Field Names Component– EMPL_RCD different field names in the different records to look for. ERN Delete Exclusion List – List of the table to be excluded from the table.
ERN Delete Control – List of the message for the Exclusion list of table/ field names.

8) Refresh Compensation -
HR_CMP015 – Process to refresh the compensation. Refresh multiple worker compensation packages with current default values, and print a report that displays the new and previous compensation data of the impacted workers. It executes the process executes the same steps as the Default Pay Components button on the Compensation page.

Incorrect Termination Date in the Job data component

Termination date is auto-populated in the peoplesoft when an employee is terminated in the Job data component. Termination date is suppose to be the termination action EFFDT - 1.

Termination date is configured to be popluated as JOB.EFFDT - 1 in the Action table component.
Termination date will not populated correctly due to a delivered bug in HCM 9.0 as well as HCM 9.1.

When you insert new row in the job data component effective date is defaulted to current date or defaulted from the previous row if it is a future date. Select the action as Termination and look at the termination date it is populated correctly with JOB.EFFDT - 1. Now change the EFFDT field it will not refresh the effdt to JOB.EFFDT - 1 value. It lets you save the component with that information. Any logic based on the termination date will fail.

Delivered code fires on the field change of the Action field alone and not on the EFFDT field. This creates the problem of incorrect termination date.

screen shot from HCM 9.1 peopletools 8.50

Monday, June 27, 2011

Information on Payroll Taxes


Generally speaking, employers report payroll by calculating gross pay and various payroll deductions to arrive at net pay. While this seems simple enough to understand, calculating various payroll deductions requires that the payroll accountant be detail-oriented and work with extreme accuracy.
Basic Formula for Net Pay:
Employee's gross pay (pay rate times number of hours worked)
minus Statutory payroll tax deductions
minus Voluntary payroll deductions
equals Net Pay.
Statutory Payroll Tax Deductions
Payroll taxes must be withheld from an employee's paycheck. This is required by law. Employers must hand these withholdings over to various tax agencies. Payroll tax deductions include the following:
  • Federal income tax withholding (based on withholding tables in Publication 15)
  • Social Security tax withholding (6.2% up to the annual maximum)
  • Medicare tax withholding (1.45%)
  • State income tax withholding
  • Various local tax withholdings (such as city, county, or school district taxes, state disability or unemployment insurance).
Voluntary Payroll Deductions
Voluntary payroll deductions are withheld from an employee's paycheck only if the employee has agreed to the deduction. Voluntary deductions pay for various benefits which the employee has chosen to participate in. Voluntary payroll deductions include the following:
  • Health insurance premiums (medical, dental, and eyecare)
  • Life insurance premiums
  • Retirement plan contributions (such as a 401k plan)
  • Employee stock purchase plans (ESPP and ESOP plans)
  • Meals, uniforms, union dues and other job-related expenses
Voluntary deductions can be paid with pre-tax dollars or after-tax dollars, depending on the type of benefit being paid for. Professional grade payroll software will help you keep track of all the tax-related payroll calculations.
Employer Payroll Tax Responsibilities
The responsibility for payroll taxes continues even after paychecks have been issued to employees. The company is responsible for paying the employer's share of payroll taxes, for depositing tax dollars withheld from the employees' paychecks, preparing various reconciliation reports, accounting for the payroll expense through their financial reporting, and filing payroll tax returns.
Employer Payroll Taxes
Companies are responsible for paying their portion of payroll taxes. These payroll taxes are an added expense over and above the expense of an employee's gross pay. The employer-portion of payroll taxes include the following:
  • Social Security taxes (6.2% up to the annual maximum)
  • Medicare taxes (1.45% of wages)
  • Federal unemployment taxes (FUTA)
  • State unemployment taxes (SUTA)
FICA Taxes
FICA stands for the Federal Insurance Contributions Act. The FICA tax consists of both Social Security and Medicare taxes. Social Security and Medicare taxes are paid both by the employees and the employer. Both parties pay half of these taxes. Employees pay half, and employers pay the other half. Together both halves of the FICA taxes add up to 15.3%. The 15.3% FICA tax is broken down as follows:
  • Social Security (Employee pays 6.2%)
  • Social Security (Employer pays 6.2%)
  • Medicare (Employee pays 1.45%)
  • Medicare (Employer pays 1.45%)
For 2011 only, the employee portion of Social Security is reduced to 4.2% instead of 6.2%. This payroll tax holiday was legislated as part of the Tax Relief Act of 2010. Starting 2012, the employee-portion of Social Security will revert back to the full 6.2%.
Reporting Payroll Taxes
Employers are required to report their payroll tax obligations and to deposit payroll taxes in a timely manner. Reporting requirements include:
  • Making federal tax deposits
  • Annual federal unemployment tax return (Form 940 or 940EZ)
  • Employer's quarterly payroll tax return (Form 941)
  • Annual Return of Withheld Federal Income Tax (Form 945)
  • Wage and Tax Statements (Form W-2)
Employers also have requirements to file reports with various state and local agencies. Employers can find links to state tax agencies through the American Payroll Association website.


Social Security Taxes

The Social Security tax is a tax applied to income related to labor. All employees and self-employed entrepreneurs pay into Social Security through the Social Security tax, which is also known as Old-Age, Survivors, and Disability Insurance (OASDI).
The Social Security tax functions very much like a flat tax. A single rate of 12.4% is applied to wage and self-employment income earned by a worker up to a maximum dollar limit. Half of this tax is paid for by the employee in the form of payroll withholding. The other half of this tax is paid for by the employer. Self-employed persons pay both halves of the Social Security tax since they are both the employee and the employer.

Social Security tax rates

Employees pay 6.2% of their wage earnings, up to the maximum wage base.
Employers pay 6.2% of their employee's wage earnings, up to the maximum wage base.
Self-employed persons pay the combined rate of 12.4% of their net earnings from self-employment, up to the maximum wage base.

The Math behind the Social Security Tax

All wages and self-employment income up to the Social Security wage base in effect for a given year is subject to the Social Security tax. For the year 2011, the Social Security wage base is $106,800. Earnings up to this base amount have the Social Security tax applied. Earnings over this base amount do not have the Social Security tax applied.
The math works like this:
  • If wages are less than $106,800, then wages times 6.2% is the amount the employee pays and wages times 6.2% is the amount the employer pays.
  • If wages are more than $106,800, then 106,800 times 6.2% is the amount the employee pays and wages times 6.2% is the amount the employer pays.

Special Rate Reduction for 2011 Only

For the year 2011 only, the Social Security tax rate paid by employees is 4.2% instead of the normal 6.2% The maximum wage base remains unchanged. Employers still pay the full 6.2% rate. Thus for 2011, the combined Social Security tax rate is 10.4%. Self-employed persons will pay this 10.4% combined rate on their earnings. This special payroll tax holiday was enacted as part of the Tax Relief Act of 2010.
Thus for 2011, we substitute 4.2% for 6.2% in the above math formulas for the amount paid by the employee. At the maximum wage base of $106,800, this translates into a tax savings of $2,136, as follows:
  • Social security tax at the normal rate: 106,800 times 6.2% = $6,621.60
  • Social security tax at the reduced rate for 2011: 106,800 times 4.2% = $4,485.60
You can plug in your own salary level to determine your own personal savings from the payroll tax holiday. If your labor income is less than the 106,800 wage base, simply multiply your salary by 2% to find your savings. If your labor income is more than the wage base, you receive the maximum savings of $2,136.

Employers have until January 31 to Implement the new withholding rates

The Internal Revenue Service has instructed employers to implement the lower 4.2% Social Security tax rate by January 31, 2011. By that time, you should see a reduction in the amount withheld for Social Security. Some employers label this as "Soc Sec" or "OASDI" on your paystub. Other employers use the label "FICA" which combines both Social Security and Medicare tax withholding.
Employers are also supposed to refund to you any Social Security tax withheld at the higher rate. If employers withheld at 6.2%, they should be refund to you the 2 percentage point difference no later than March 31, 2011.

What Happens to the "Missing" Social Security Funds?

To prevent Social Security from losing tax revenue, Congress mandated that revenues be transferred from the general fund to the Social Security trust funds to make up for the tax reduction. This is provided for in section 601 of the Tax Relief Act, which reads in part, "There are hereby appropriated to the Federal Old-Age and Survivors Trust Fund and the Federal Disability Insurance Trust Fund established under section 201 of the Social Security Act (42 U.S.C. 401) amounts equal to the reduction in revenues to the Treasury by reason of the application of subsection (a). Amounts appropriated by the preceding sentence shall be transferred from the general fund at such times and in such manner as to replicate to the extent possible the transfers which would have occurred to such Trust Fund had such amendments not been enacted."

What is the Social Security Tax For?

The Social Security tax is that goes directly to the Social Security trust funds and is used to pay for Social Security retirement benefits, benefits for widows and widowers, and disability benefits. Unlike income taxes, which are paid in the general fund of the United States and can be used for any purposes, Social Security taxes are paid into special trust funds that can be used only to fund social insurance benefits.

Medicare Tax

Definition:
The medicare tax is a payroll tax that must be withheld from an employee's paycheck by an employer. The medicare tax is one part of the employer's obligation to withhold Federal Insurance Contributions Act (FICA) taxes which also includes social security taxes.
Employers pay a matching percentage of FICA taxes; employees pay 1.45% and employers pay an additional 1.45%. Self-employed individuals pay the whole amount of medicare and social security taxes.
Also Known As: FICA taxes

Dynamic role rules

What are dynamic role rules?
• The assignment of roles to User Profiles based on your business rules
• These business rules run against system(s) to assign PeopleSoft access
• Business rule data can reside in a number of places:
– PeopleSoft data
– 3rd party systems
– LDAP
• Allows your PeopleSoft security structure to change in an automated fashion
• The dynamic role rule process removes and grants access to User Profiles
Methods - Assigning dynamic role rules
• There are three technologies you can use to execute your business rules:
o PS/Query
o LDAP Plug-in
o PeopleCode
• One, two, or all three of the technologies listed above can be used
Building Role Rules - PS/Query
• PeopleSoft recommends using PS/Query to build role rules if the membership data resides in your PeopleSoft database
• Access is removed or granted based on the User Profile IDs retrieved by the query
• Can be built on Queries and/or Views
• Business rules can be built into the View and/or Query
Assigning Roles - PeopleCode
• Membership data not contained within the PS database
• Data might exist on other 3rd party systems
• Extremely flexible
o SQLExec functions
o Business Interlinks
o Component Interfaces
Static role assignments
• Roles are assigned to User Profiles manually
• Not scalable
• All security changes require manual intervention
• High administration costs
• High margin for human error

New Action Reason in Peoplesoft ver 9.2

New Action Reason

HIR / REB  - Rehire Prior Benefits
HIR / REN - Rehire with no Prior Benefits



Taxation in North America

To understand the taxation in North America such as different types of taxes involved in North American Payroll
please refer to the below link:
http://en.wikipedia.org/wiki/Taxation_in_the_United_States


Sunday, June 26, 2011

Points to Consider When Running the PAYSHEET Process


·         The PAYSHEET process can be run before or after a time interface.
It depends on whether the time interface is designed to load the majority of the paysheet data or simply other earnings.
·         Once paysheets are created, you don't normally rerun this process.
However, it might be necessary if any high-level information on the paysheet changed (for example, earnings code for regular or overtime pay). If you need to recreate paysheets, it is recommended that you run PAYUNSHT first to delete the current paysheets. Otherwise, the process doesn't recreate a paysheet for an employee who already has one.
·         If an error occurs during this process, it can be rerun and the process continues processing where it left off (after the last commit to the database).