User Defined Per Check Limit Incorrectly Limits Deductions/Employer Match Because It Includes Deductions Not Taken
Last updated on DECEMBER 13, 2017
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.1 and later
Information in this document applies to any platform.
Employee with Savings Plan, Plan Type 40 for before tax is not taken due to net and therefore the employer match is also not taken. The employee’s Plan Type 41 after tax deduction is taken; however, the employer match deduction is limited by the User Defined Per Check Limit which seems to be including the match that was not taken.
Plan Type 40, Before Tax Match, nontaxable btax benefit, Partial Deductions not allowed, Employer Match recalculated
Plan Type 41, After Tax Match, nontaxable benefit, Partial Deductions not allowed, Employer Match recalculated
User Defined Per Check Limit 7% for both Plan Types Employer Match Deductions
Plan type 40 = 75% before tax
Plan Type 41 = 2% after tax
Employee's paycheck adjusted to about $1,500
Increased Medical Deduction to $500
Plan Type 40 deductions not taken due to Net, Match is not taken due to Checklimit
Plan Type 41 deduction taken, Match is not taken due to checklimit
The Plan Type 40 employer match is limited due to the check limit and deduction code is set up to take it all or none at all. However, for the Plan Type 41 match, I believe the limit is incorrectly imposed as even though the employer match for plan type 40 was not taken, it seems to be taken into consideration.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms