Sage 100

I have a client still on 4.40 MAS 90 that has been intermittently getting out of balance DTRs from Payroll for the last three months. There are no errors showing on the PR Data Entry audit report entries or totals or on the check register. The amount has been around $16 on a 25k payroll. It appears to be failing to post all of the employer state unemployment expense and is pretty close to the amount for a single employee. The issue is random but has happened about 1/month on a weekly payroll. I have been though the tax table, divisions, earnings codes and deduction codes and could not see any issues there. The deduction codes are either all periods or manual. We have not been able to associate it with a significant event. Does anyone have ideas on what could cause this? Yes, we hope to upgrade them in September when things slow for them.

If you copy the data to a test company and run a payroll for just the one suspect employee is the DTR oob? I test it and then rebuild all keys and sorts in PR and test it again. Is this PR imported or input? If imported I'd think that may be the issue.

Is the client telling you the audit report ok or have you been able to review it yourself? Is the same deduction cycle used for every payroll?

Thank you both for your replies. @MoiraGoggin, so far, we have not pinned it to a suspect employee. We thought we had but it is intermittent and on a previous payroll that had the issue, the suspect was not the cause. I have not run in a test company because it doesn't happen all the time. When this first happened, I found that PR9 and PRA each had a record when the files should have been empty. I re-initialized PR 6-A and the next payroll worked. This time I found the same thing so I deleted PR6-A and re-initialized them manually. Then I rebuilt keys for all PR files and the sort files. Not sure if that is related or not. We will see. The payroll is not imported. @DebbieBeach, I went through all 36 pages myself . :) All deductions are either set to All periods or None. Because they don't use the periods, I would bet the period is just the default every time. I brought that up but because they regularly have employees off a week or so, they handle deductions that only occur a couple times a month manually.

Any negative deductions involved? I have a client that deducts state pension every week. On occasion, they have ""refund"" the money back to the employee because of termination as a negative. PR jokes with the employer portion of FICA/Medicare. Perhaps it is doing something similar in your case. Also, since it doesn't appear on the audit report, take a look at FUTA and SUI or perhaps and employer match type of deduction.

@ JeffSchwenk, there are no negative deductions. Thanks for making me think more about what doesn't appear on the audit report. We are virtually certain it has to do with State Unemployment Tax; however, the setup looks good and it works most of the time. They did a payroll Monday and it worked fine. I went back in to see if there was anything left over in the PR data entry and found PR9 was clean but PRA had three records in it. I understand this is a temporary sort file but this doesn't seem normal. Other systems I have checked have cleared this file after the payroll update.

@JohnBroadfoot this was in the Sage KB - it might help you.

@MoiraGoggin, thanks for the article. I looked through all three KBs and totally missed this one. Need to work in my search skills. This was supposed to be fixed on PU3 and the client is on PU8 and SS does tie out. Sage seems to regularly break their fixes and it is entirely possible the bug affected more than just SS. I have emailed the client to figure out if multiple departments were used on the OOB payrolls. The example was small enough to be some kind of rounding issue. The 15 to 20 dollar range the client is seeing suggests one side is missing from one or more employees.

OOB payrolls did not have people working in multiple departments.