Why are my EFT remittances failing to email and/or email notifications failing to send to approvers?
2. Verify you have a Remittance Message ID in the Message Setup window. The EFT file will be attached to this message format.
3. For each vendor you pay via EFT, ensure the respective email address is in the system. Go to the Vendor Address Maintenance window > Internet Information (globe icon) to verify.
II.
If you find no issue with Email setup in GP, does this issue occur for all users in all companies, and did the user receive an Exchange Login prompt and enter their email and password?
Is MFA configured and if so, please ensure you are running a version of Mekorma that supports MFA (introduced in Mekorma build x83 - April 29, 2021) and at the GP Company Email Setup window you have the Application (Client) ID field populated as assigned by Azure AD.
If the client's email system has been switched from MAPI to 64-bit Outlook using O365, confirm that GP email settings reflect this change and the Application (Client) ID in the Company Email Setup is populated.
III.
We have seen cases where the Reply-To fields at both Purchasing Email Setup and Message Setup must be cleared after having migrated from on-premise Exchange to Azure cloud services. The remnant domain data is known be associated with the failure of email remittance sending. After clearing these fields users were able to send EFT remittance successfully.
Before clearing any data we recommend you copy the data and save for later reference if needed.
Company Email settings>Email setup>Purchainsg Series>Purchasing Email Setup
Company >Email Message setup>Message Setup
Steps:
1. Open the GP>Company>Email settings window and choose the Purchasing Series.
2. Enlarge the Purchasing E-mail Setup window from top to bottom. This will enlarge the "Have Replies Sent to" window.
3. When the"Have Replies Sent to" window. is enlarged it will display any additional email addresses that have been entered. Take note and remove the email entries if present.
4. Open the Vendor Remittance in the Message Setup window.
5. Enlarge the Remittance Message ID window from top to bottom. This will display an elongated "Have Replies Sent to" field.
6. Check for any email entries in the "Have Replies Sent to" field.
7. Take note and remove any email addresses if present.
8. Test.
Resources:
Mekorma User Guide on EFT Remittance Emailing:
Mekorma Blog on Email Issues:
Mekorma Knowledgeable "How Can I use Mekorma With MFA?"
https://portal.mekorma.com/articles/details/Article/KA-01294/how-can-i-use-mekorma-with-mfa
Microsoft Troubleshooting guide:
https://learn.microsoft.com/en-us/dynamics-gp/installation/email-troubleshooting-guide
Microsoft Community: EFT Check Remittances are not e-mailing:
https://community.dynamics.com/gp/b/dynamicsgp/posts/eft-check-remittances-are-not-e-mailing-1316703384
Microsoft Community: Modern Authentication and upgrading to Microsoft Dynamics GP 18.5:
https://community.dynamics.com/gp/b/dynamicsgp/posts/modern-authentication-and-upgrading-to-microsoft-dynamics-gp-18-5
Microsoft Community Emailing Setup Guide:
https://community.dynamics.com/gp/b/dynamicsgp/posts/emailing-setup-guide
Azure AD Registration to support MFA:
https://learn.microsoft.com/en-us/dynamics-gp/whats-new/multi-factor-authentication
HYPOTHESIS:
If it the case for example the user logs into GP for example 4 hours and within that time the GP connection with Exchange times out and needs to be re-established this may create the problem.
Perform the following test to determine:
Test: WITHIN 5 MINUTES:
1. log in to GP
2. log in to Exchange
3. Test process
If you cannot recreate the problem with the test, this supports the notion of the hypothesis above.