Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Does anyone know how to re-export an EFT/ACHA after you use the 'Generate EFT' files? It appears from what i gather that this is not possible from the Credit Transfer Register.
Sencondly, When a user tries to use the 'Generate EFT' to export the ACHA file, Nav is throwing the below error. Anyone have any guidance oin this?
I have not found a way to regenerate the EFT file. If the file is grossly incorrect, I post the transaction and immediately Financially Void it to reinstate the Payable and prepare another file. If it needs a small change I sometimes modify the TXT file myself. As for the message, on the Bank Account Card, their is the field called E-Pay Export File Path. Make sure this path is real, based on the entry you put there:
Hope this helps.
Thank you for such a quick reply.
On question 1 - i will work with the finance team to see if this process works.
On question 2 - When the 'Generate ETF' button is selected, it opens a file dialog window for you to select a local path. The user is selecting a local path on their machine. This gives me the impression that the pathing on the bank card is not used. From the docs the e-pay export path is supposed to map to a local drive on the server where Dynamics Service is running. Which we have done. Without getting off point, why the popup for a local path if the system is supposed to use the e-pay export path?
Your 2nd question update leads me to ask what Dynamics Service is running? If I was sending EFT files via a Bank Service then I am wondering are you using AMC Banking? This will send the EFT file via their service to the linked Bank. If I am doing this all manually, then the process is:
1. Payment Journal create list of EFT payments
2. Export EFT File, which generates remittance advices to vendor
3. Generate EFT File to then upload to your Bank. NOTE: In your version of NAV 2018, the Generate EFT File will open a Save As window which the user specifies the location to save the file too. NOTE: The User and NAV must be able to Save a file to that location. So if the NAV Server cannot save a file there, you will get the error. I would have IT map a drive to the location you are saving too.
Business Applications communities