Sage 100

How to test Payroll DD stub email delivery? I have a recent upgrade to 2014 where the DD stub email delivery is failing. Unfortunately the way the stubs are generated I don't believe you can re-generate and test the process again (though I am aware you can go to the DD Stub Viewer and select all stubs then email them by clicking the icon). Have I overlooked some way to test these DD email stubs? Or do I just have to tell the customer to wait until next week and we test again. There are about 100 employees. I guess I could test in a backup company on one employee then if that's successful go to the live company. Anything I missed?

Same issue at one of my clients.... no way to test.. you get one shot and if they don't go through you are screwed. I am currently checking to see if their isp's mail server spam filter is catching them and not performing the relay.

Actually my issue is with ACH remittance advises but same issue.

My situation: Customer on 4.3 EES --- > Sage 100 ERP 2014. Ran fine for the past few years on 4.3. I'm presuming that there may be a timeout issue (and I could swear someone mentioned that regarding paperless email but cannot find it). I have a problem with the IT people so as a last resort I probably will set them up with Gmail, print and prove it's not Sage then they can decide whether to pay me to babysit IT.

MIne is 2014 also. They don;t use email for paperless or anything else, and the email tests fine in company maintenance... so I believe the email gets sent successfully .

same here. I'd be curious whether you have a lengthy period of time before it tries to send emails. Mine seems to process for 3-5 minutes.

When I tested, it was with one vendor (me) so I could see if I received an email. I don't remember there being a long wait but that could be because there was only one vendor. Client just complains that none of the vendors are receiving the ach remittance. I will be on site tomorrow and will post whatever I discover.

I'm going on-site tomorrow too. In my case I have a problematic IT department so it may be tough to diagnose.

@DougHiggs Just back from my DD stub challenge. The only change we made on the Sage side was in company maintenance on the email tab to set ""SMTP Encryption"" to TTLS/STARTTLS"". Previously I think it was none. We also have had (and it remained) checked ""Use 128 big encryption for password protected documents"". The IT person was there and likely made several tweaks to Exchange settings. I don't know what changes he made or if those impacted our outcome -- however we were able to send email stubs today. I have to say I'm somewhat disappointed that these types of challenges keep arising during upgrades and I consider it a key reason as to why a customer gets that look of fear/terror/dread when we mention that it's time to upgrade. It's going to be harder and harder to convince customers to upgrade if these types of problems continue. I also think that one reason the problems may appear suddenly is that the customer puts off the upgrade so long (this one was coming from 4.3 EES). FYI

Thanks for the update @WayneSchulz . I was on site today and they have elected to upgrade to 2015 instead of trying to solve the issue on the current version, 4.5.. Waiting for 2015 plus 2-3 months to upgrade so that they can use TLS and office 365. They are on 4.5 and 4.5 doesn't support TLS which is what office 365 uses... They have another email pop3 account that they are using for the Sage setup to work around the TLS issue.... even though the work around doesn't work. They are convinced the emails are blocked by their vendor's spam filter as they are transmitted on port 25...Apparently some vendors are receiving the ACH remittance advice. Whatever the reason is I am not spending any more time or effort until the upgrade to 2015 and change over to office 365/TLS.