I'm hoping someone may have an idea or is maybe experiencing something similiar; I'm really confused by this issue.
Using GP2013 we run payroll weekly and the last 3 weeks (all of 2014) we've had instances of payroll checks being cut for more than the actual amount calculated. There is nothing on the transactional data to indicate where it is coming from other than the historical net is just wrong.The following is consistant with these checks/dd:
1) The check cannot be voided (says check does not exist)
2) The check posting batch is out of balance by the amount the employee was overpaid (account affected is the Cash account bc it’s paying them more than the liabilities and expenses)
3) Sometimes the Federal and/Or State Taxes are not calculated at all but other standard deductions are
4) The Recreate Check Stub feature will display correct amount but shows where the direct deposit was for the wrong amount.
5) All checks affected so far have garnishments (either court-order and/or notes/loans from our company). We use PIP for our garnishments not greenshades. It does not affect everyone with a garnishment.
6) Some of the affected employees would have netted zero & been in arrears, but not all.
Microsoft’s suggestion to our partner was to re-sequence the deductions to: TSA deductions, Standard, then Garnishments; which we tried and less people were affected but it still occurred. This is a causing major issues with net wages and taxes, not to mention paying people extra, non-traceable amounts. The amount they’re overpaid is not consistant either, I can’t narrow down how it gets the number but the overpay amount does vary by changing the deduction sequence when testing. Through testing, I think I’ve ruled out an issue with minimun net pay and maximum garnishment rules. MS believe it’s just a sequencing problem which it is however, why it’s consistantly happening every week since the YE update seems questionable. Has anyone heard of this before?
*This post is locked for comments