web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / The EFT file could not...
Microsoft Dynamics GP (Archived)

The EFT file could not be generated in the path specified

(1) ShareShare
ReportReport
Posted on by Michael Buchsbaum 170

I've seen this similar issue before in the forums, but no reply other than to check the path in the EFT setup of the checkbook. I've done that and I've even generated prenote files from the setup screen which worked fine. When I get to the EFT Generation, using the same Checkbook ID, I'm getting that error message.

I must be missing something. I don't know how a prenote can be generated and written to a folder but the actual EFT file can't. Any ideas? Thanks!

*This post is locked for comments

I have the same question (0)
  • Michael Buchsbaum Profile Picture
    Michael Buchsbaum 170 on at

    Anyone? The full error is "The EFT file could not be generated in the path specified for PM Domestic Payments in Checkbook EFT Payables Options." Again the path in the output fields is valid with full permissions. Writing a prenote file works fine using that directory, but generating the actual EFT file poruces this error. I've tried local drives and network drives - doesn't matter.

  • Ian Grieve Profile Picture
    Ian Grieve 22,784 on at

    It might be worth checking your data and seeing if there is a dodgy character somewhere which is causing the problem.

  • Troy Bakken Profile Picture
    Troy Bakken 55 on at

    Although this is quite late, I ran into this issue today. After setting up the EFT Bank Default Output File paths and then trying to generate the payment file I received the same error. I restarted GP and was able to generate the file. I suspect the setting is stored in a variable and not updated when changed. Seems strange but none the less it worked.

  • Community Member Profile Picture
    Community Member on at

    I ran into this error message yesterday and the resolution was so counter-intuitive that I thought I'd share in case it helps anyone else.

    It turned out that within the export format, I had a mismatch between the field name and table name for a data field i.e. a table name was being referenced where the referenced field did not exist. (Don't know how that happened.)

    Anyway, fixing that issue fixed the error.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans