Sage 100

Late this afternoon client emailed and said that Paperless Office mailed wrong Direct Deposit Stub to another employee's address. Client is running SAGE 100 STD v4.50 PU5. She said she checked the email address on both employee's maintenance and they were different and correct. Has anyone else had this problem? I assume the Direct Deposit Stub has the SSN as a password so employees cannot see each others stub.

I haven't seen this, but a password is required--either a random one, a SS# or one entered manually. I'm not sure where to check out the errant email address--DFDM is where I'd start.

I have had this reported at least once. I think client was on older release. Never able to pin point the issue. As Sage says, shxx happens. Your client should upgrade to v2016c ASAP!!

I had it happen in 4.50 also. Only happened once and never again (thank goodness).

Thank you for your responses. I will recommend to client that this could be a one-off issue, but we should move from 4.5x to v2015. Not ready to try v2016 yet.

We have a client that had this happen repeatedly. The employee who received the wrong stub could open it with their own ssn/pwd. Did your client receive any errors during PDF creation and then need to restart the process? If so, likely a record got hung up in the workfiles PR_31 and PR_32 and caused the delivery issue. You will want to make sure the workfiles have cleared properly after they update.

Also - the client Dawn referenced was on V2013.

I haven't had this happen with direct deposit stubs, but with SO invoices. Paperless Office was delivering them to the wrong email addresses. Not only was it sending to the wrong email address, but the email address was for a customer that doesn't even get SO invoices delivered via paperless office. I reinstalled the workstation and everything seems to be fine now.

I'm sure an upgrade to Sage Payroll Services would solve this problem. What's that the customer asks? Why doesn't Sage use the maintenance money to pursue and understand (and hopefully fix) these types of bugs? ....

I had this happened, and what I had to do based on Sage's advice was to go to File/Run Pl_advancedoptions_ui and uncheck the box for Lock Files. It hasn't happen since though unchecking the box may affect other pdf issues. I have only seen it once and Version 2015.

@WayneSchulz To paraphrase a statement by Erika Jelovsek at a past Insights - ""It is just too hard to do""......

Resurrecting this issue from 4 months ago (November 2015) Update: in January 2016, SAGE 100 STD was upgraded to v2015 PU# 3 (for ACA reporting). Direct Deposit Stubs have been going to the correct employees until yesterday. No error messages were generated. The controller's DD stub ended up in another employee's email in-box. That employee was able open the controller's DD stub with their SSN password. Now the controller wants DD stub emailing STOPPED until ""SAGE fixes it's programs!"" I have a case opened with SAGE. The payroll administrator processes payroll (data entry thru Check Register Update / Paperless Office email generation) via a remote session from her home office connected to HQ server via a terminal server. Could the remote session be the cause of the possible cross addressing of email accounts? Should I recommend the payroll administrator perform the last step - Check Register printing / Update / Paperless Office DD stub email generation - when she returns to HQ and performs this step from her local office workstation?

My client who had this issue repeatedly was also on a Terminal Server. Sage support told them to turn on non-graphical forms as a resolution. I did discuss this with Diane Coffman in San Diego and sent her all of the case notes I had on it, but I have not ever heard back from her about it. .

she's too busy porting that bug to the framework version...