Sage 100

In 4.30.0.23 we have pay stubs going to random email addresses.one employee received the stub for a completely different employee. Both employees are setup correctly. It's their first payroll. They used the Paperless Office Stub Viewer to send out the stubs. Has anyone seen anything like this?

Are you using Sage's ACH direct deposit? Also have you rebuild the PR files lately?

It's a brand new setup. It is Sage's PR direct deposit.

OK - the reason I was asking is because I saw something similiar for someone using Kissinger's ACH. The direct deposit file actually had info from one of the other companies. Kissinger seemed to indicate that this happened because the PR files had been rebuilt.

Side note: When they're ready to email from the Viewer again, one way of checking to see if correct email is being sent is to temporarily setup a product like PostCast Server (google it). It's a quick and dirty SMTP Server you install on any wkstn. In Company Maint / Email point it to this SMTP (using the computer name or IP of the wkstn). Configure PostCast to not auto-forward emails to actual receipients. This way emails are in a holding bin and you can view them right there and see if they are going to correct recipients.

@AlnoorCassim Is this a workaround for customers who don't have access to a compatible SMTP?

If you mean use as a workaround for Gmail / Google Apps prior to 2013 version (b/c it uses newer version of ChilkatMail). then Yes. BUT for that purpose (as opposed to Robert's) use the paid version of PostCast Server or SMTP Relay Server by SoftHeap or some other equivalent.

It may have been due to a rebuild. I had a problem last night and did have to do a rebuild.

@JohnLeonard do you remember the solution to the issue after the files were rebuilt?

They had to manually enter the direct deposit information on the Bank's website. Kissinger said don't rebuild the PR_03 data file. The client has not had another payroll run since this happened, so I am hoping that it will not happen again. In our situation, we had just migrated from 4.3 to 4.5 and had rebuilt the files prior to the migration.

Ah! I didn't rebuild the PR_03.

And you have to love Sage KB Articles where the solution is: Do not email Direct Deposit stubs.

And to be fair it's an internal only document.

In other words, don't fix the problem, just don't use the feature causing problems. Who needs all these features anyway??

Our customers used to pay us to add features. Now they are paying us to remove them."" paraphrased from something Pascal said at Summit.

Oops! Focus...

I think that was the speech.

That's the new fucus.

Sooooo.... apparently some of the employees still had their vacation forwards turned on. All is good in Mudville.

There's always a reason....

Yeah. I still wonder about the other cases that Sage already knows about.