EPY: How to Verify that a U.S. Tax Calculation in PeopleSoft is Correct [ID 608210.1]-CSDN博客


		Modified 29-APR-2010 Type PROBLEM Status PUBLISHED

In this Document
  Symptoms
  Cause
  Solution

Applies to:

PeopleSoft Enterprise HRMS Payroll for North America - Version: 8 to 9.1 - Release: 8 to 9
Information in this document applies to any platform.
SPECIFIC TO:Enterprise, North American Payroll

This document was previously published as Customer Connection Solution 301517

Symptoms

If you are questioning the way PeopleSoft is calcing taxes at the Federal, State or Local levels at various stages of your payroll implementation process---at first setup, at parallel testing, and after the go live date.

Cause

Not Applicable

Solution

No matter what stage you are at, the following is an explanation of the procedures for you to follow when you feel a PeopleSoft tax calc is not correct.

Note: PeopleSoft uses the Annual Percentage tables for the taxing jurisdiction where available.   Users using any other frequency may have experience small differences to the annual calculation.

1. If you feel a tax calc is incorrect, you need to do several things.  First, test in both demo and production, if you have both, especially if you first notice the problem in production.  Rule out any problems at your end first.  If you don't, and we end up not being able to reproduce the problem, the ball ends up back in your court anyway, at a later date.  It is also assumed that this was tested on a supported release with the most current tax update(s) applied.

2. If you still feel the calc is incorrect in both demo and test/prod, then get the appropriate docs--preferably from the state or locality, secondly from BNA or CCH (they can be wrong sometimes), and do a manual calc.  DO NOT assume that PeopleSoft (or a legacy) is right or wrong at this point.  Always use the official docs as the guide.  Do not try to 'back into" the tax calc from figures you see in the Federal State Tax Table. This table is not designed to be used when doing a tax calc.  There is often code behind those numbers.  Be prepared to send both the doc itself and your manual calcs to PeopleSoft.  Remember that PeopleSoft uses the annualized method or "computerized method" or percent method (wording differs by taxing entity), rather than tables for specific payroll frequencies such as weekly, biweekly, monthly, etc.

3.  If your manual calc per the doc produces a different result than PeopleSoft, log a case with GSC, and be prepared to send panel shots of the EE tax setup, paycheck data, and your hand calc results.   GSC works from a "prove that it's wrong" standpoint, rather than "prove that it's right" before we receive what we need from the client.

4.  At this point, GSC would then test and try to reproduce the same results as the client is getting.  If we are able to reproduce the client's problem, it typically becomes an incident that is then delivered via Customer Connection and/or tax updates or application upgrade project.  If we cannot reproduce, the ball then goes back to your court (step 1) and the case is closed.

5.  Tax Priorities  (what order is taxes withheld from and employee's paycheck)

  1.  Employee share of OASDI on non-tip earnings
  2.  Employee share of Medicare on non-tip earnings
  3.  Federal income tax on non-tip earnings
  4.  State taxes on non-tip earnings  (Includes State Disability)
  5.  Local taxes on non-tip earnings
  6.  Employee share of OASDI on reported tips
  7.  Employee share of Medicare on reported tips
  8.  Federal income tax on reported tips
  9.  State taxes on reported tips  (Includes State Disability)
10.  Local taxes on reported tips
11.  Additional federal withholding requested by the employee
12.  Additional state withholding requested by the employee
13.  Additional local withholding requested by the employee

WORKAROUND:
N/A

KEYWORDS:
Taxes, Net Pay, Documentation

Show Related Information Related