You’re offline. This is a read only version of the page.
13
Bouncing off a thread from the old GPUG forum from January 2023 with the same subject (Emailing eft remittances).
Two of my coworkers (Madeline & Brittany) worked with our IT consultants to try to determine why we have been receiving an error message in recent months when processing our payables batch (thankfully only one vendor right now, although we hope to expand that) for monthly debt service payments. And we believe we might have found a fix. We tested it in our demo company database in GP and the eft email remittance appears to be working again for us in that environment.
Currently, our bond trustee is the only AP vendor we have setup to pay via EFT and configured to send an EFT Remittance email when payment is posted in GP. That worked smoothly for several months until about October 2022. Then, for the last several months, we've received an error message when processing this payment in GP indicating that the email remittance did not send.
Here is a link (see below) that my coworkers and our IT consultants referenced to try to fix our issue of running into that error message. We believe the issue had something to do with Azure and "modern authorization". I'm certainly no IT expert, but I've been told by my coworkers that this reference document was helpful in apparently solving our issue - paying particular attention to step #18 at the end of the document.
Multi-Factor Authentication - Dynamics GP | Microsoft Learn
Hopefully this helps someone out there trying to fix the same issue in their environment.
Share
Report
All responses (
Answers (
