Taxes Changing on Salaried Employee's Paycheck

I am running QB 2006 Pro and one of my salaried employee's net pay is
not always the same. I looked at the detail and it appears that the
problem is that the Federal Witholding amounts differ...there are even
a couple of checks with $0.00 deduction for Fed W/H.
I do not do anything other than place a checkmark next to this
employee's name and click on "creat paycheck" when I pay this
employee. What could be
causing this problem?
I am using the current update (20810).
Thank you
Reply to
csonsini
Do you think it would help if we know how often you calculate payroll, the employees wages, status and exemptions? Based on the limited info all I can say at this point is that it is god's will.
Reply to
Haskel LaPort
They are on a bi-weekly payroll and the employee's filing status doesn't matter because there should always be federal w/h taken from the check. His gross pay is always the same - $1177.00 - and here's the rundown:
His paychecks from the beginning of the year until 3/19 had $33 deducted for federal w/h. From 4/2-5/28 the federal w/h was $80, on 6/11 the w/h was $0. The last 2 paychecks (6/25 and 7/9) were back to $80 w/h.
So, as you can see, it appears to be arbitrary.
Reply to
csonsini
Someone is changing the deduction amounts! Check the pay stubs (hard copy) to be sure that the same number of exemptions, and single or married is being claimed each period. If not, you have a much bigger problem, think stolen password or machine left logged in. If it is staying the same then it is time to call Quickbooks.
Reply to
Gary Charpentier
I work out of my home office and, unless my pets are getting into the Quickbooks, no one else has access. I guess I'll give Quickbooks a call...not that they've ever been of any assistance to me in the past!!
Reply to
csonsini
They are on a bi-weekly payroll and the employee's filing status doesn't matter because there should always be federal w/h taken from the check. His gross pay is always the same - $1177.00 - and here's the rundown:
His paychecks from the beginning of the year until 3/19 had $33 deducted for federal w/h. From 4/2-5/28 the federal w/h was $80, on 6/11 the w/h was $0. The last 2 paychecks (6/25 and 7/9) were back to $80 w/h.
So, as you can see, it appears to be arbitrary.
God works in mysterious ways. You also appear rather odd since here it is July and you are first questioning this miracle.
Reply to
Haskel LaPort
It was just brought to my attention. I would never expect the payroll program to arbitrarily change someone's deductions. I don't examine everyone's paychecks to make sure their deductions are correct.
Reply to
csonsini
They are on a bi-weekly payroll and the employee's filing status doesn't matter because there should always be federal w/h taken from the check.
I guess that also includes the status of do not withhold.
His gross pay is always the same - $1177.00 - and here's the rundown:
His paychecks from the beginning of the year until 3/19 had $33 deducted for federal w/h. From 4/2-5/28 the federal w/h was $80, on 6/11 the w/h was $0. The last 2 paychecks (6/25 and 7/9) were back to $80 w/h.
So, as you can see, it appears to be arbitrary.
Reply to
Haskel LaPort
It would seem most peculiar it's a program defect if it only occurs for one individual.
I'd look for an (inadvertent, perhaps) change in the deduction status for that particular employee.
Who does QB entry, you, a single employee, multiple employees...??? Same for who does payroll?
--
Reply to
dpb
Examine the hard copy stubs to see what the computer knew at that time what his deductions were. Until this is done, no specific help is possible. (Oh, if you keep backups you should check those as well)
Do you have more than one person on salary? If so, does this "bug" affect any other employee? Any problems with hourly employees?
Have you grabbed IRS Pub 15 and hand calculated what his deduction should be? Does any of the amounts match? You may want to hand calculate a payroll for everyone and check it.
Possible (not in any order) 1) Bad hardware You likely would be getting blue screens if this were true. 2) You changed them and didn't know or remember you did it - Did he update his W-4? Did you think you were updating another employee's w-4 info and get his by mistake? 3) You entered amounts on the payroll entry screen to override the calculated amounts (and maybe didn't know you did it) 4) Your computer has been compromised 5) Corruption in your data file 6) Corruption in the payroll update(s) 7) QB has a bug and you are the only person to whom it applies. Believe me if QB had this as a bug thousands of people would be screaming.
As for #6, check your update history and see if the dates of the payroll updates you got happen to match the changes in his check and your payroll dates.
Sorry for the homework, but the more we can eliminate the better the advice.
Reply to
Gary Charpentier
Examine the hard copy stubs to see what the computer knew at that time what his deductions were. Until this is done, no specific help is possible. (Oh, if you keep backups you should check those as well)
Do you have more than one person on salary? If so, does this "bug" affect any other employee? Any problems with hourly employees?
Have you grabbed IRS Pub 15 and hand calculated what his deduction should be? Does any of the amounts match?
Possible (not in any order) 1) Bad hardware 2) You changed them and didn't know or remember you did it - Did he update his W-4? Did you think you were updating another employee's w-4 info and get his by mistake? 3) You entered amounts on the payroll entry screen to override the calculated amounts (and maybe didn't know you did it) 4) Your computer has been compromised 5) Corruption in your data file 6) Corruption in the payroll update(s) 7) QB has a bug and you are the only person to whom it applies. Believe me if QB had this as a bug thousands of people would be screaming.
As for #6, check your update history and see if the dates of the payroll updates you got happen to match the changes in his check and your payroll dates.
Sorry for the homework, but the more we can eliminate the better the advice.
Reply to
Gary Charpentier

Site Timeline Threads

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.