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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / 2016 ACH - Payment Jou...
Microsoft Dynamics NAV (Archived)

2016 ACH - Payment Journal 'Export' Function Issue

(0) ShareShare
ReportReport
Posted on by Community Member

Good Morning.

The client is on NAV 2016

9.0, GIG6.00.01

9.0.42815.0

Upon attempting to create a test ACH payment file to submit to my client's bank, we are finding the 'Export' function is not working. When we click the button, nothing happens.

Note: I have run through this process in Cronus several times, so the we are more than familiar with the functionality.

All of the necessary setups have been checked several times:

  • Company Info -> Federal Tax ID No. field populated
  • Bank Card fields populated (Export and Sent files have read/write/delete permissions; paths end in " \ ". The "Remit" and "Export" files are defined. All bank routing and account information is populated).
  • All Vendor Bank Card fields populated ('Use for Electronic Payments' Boolean = Yes)

When we ran 'Suggest Vendor Payments', the journal populated. The 'Bank Payment Type' is "Electronic Payment".

In addition, the Payment Journal Batch of "ACH" has the 'Allow Payment Export' Boolean' checked. (Note: We have tried exporting with this both on and off).

We have tried to export the payment multiple times but nothing happens when we click the button. We don't get an error. Nothing happens.

The Export Payments Codeunit (# 10090) has not been modified.

Any suggestions would be greatly appreciated.

Thank you.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    *Update*

    While the Bank Card -> 'Export Format' is set to "US", we were able to find (through the assistance of a developer) that the export file is not creating because the Bank Card -> 'Payment Export Format' field is blank. This appears to be a bug of some sort as we should not need to populate this field.

    I populated the field and that created a whole slew of messages prompting us to add an IBAN, etc. This is not a foreign bank account. This is a US customer attempting to pay US vendors using a US bank.

    The database contains NA objects. I'm curious as to if there are any ideas out there as to what might be triggering these issues? As stated earlier, we were able to set this up in Cronus and execute the functionality with no issues.

  • Suggested answer
    Suresh Kulla Profile Picture
    Suresh Kulla 50,243 Super User 2025 Season 2 on at

    Do you have set the Payment Export Format on the Bank Account Card ? And can you xoom on the line and check if the Exported to Payment File is Set to true or false

  • Suggested answer
    Suresh Kulla Profile Picture
    Suresh Kulla 50,243 Super User 2025 Season 2 on at

    Bank ->  Payment Export Format defines you Bank Export/Import Setup and the Codeunit to run the process for exporting the file. You need to make sure you set that format appropiately.

  • Community Member Profile Picture
    Community Member on at

    Hello Suresh ~

    The 'Export Format' is set to "US" and the 'Payment Export Format' is blank. According to MSDN, the 'Payment Export Format' field should only need to be populated if the desired format is not country-specific, so it doesn't make sense that this would be a mandatory field.

    As I mentioned, testing this in Cronus worked fine; we're only having the issue in the customer's test database.

    The 'Exported to Payment File' is "No".

  • Community Member Profile Picture
    Community Member on at

    That field is blank in our Cronus database yet the file exports without a problem. What is the default option for US "NACHA" format? Thanks!

  • Suggested answer
    Suresh Kulla Profile Picture
    Suresh Kulla 50,243 Super User 2025 Season 2 on at

    The best way to find is run through the debugger and check if there any setups or conditions it is failing to export the file. Compare it with Cronus.

  • Community Member Profile Picture
    Community Member on at

    Note: I went back into Cronus and updated Bank Account: No.= ACH, the Bank Card -> Payment Export Format to "SEPACT". Next, I ran 'Suggest Vendor Payments' and pulled in an invoice. Now when I click the Export button, I receive the following error:

    "Payment Export Format must have a value in Bank Account: No.=WWB-OPERATING. It cannot be zero or empty."

    When I clear the field and run it again, the export function works.

  • Suggested answer
    Suresh Kulla Profile Picture
    Suresh Kulla 50,243 Super User 2025 Season 2 on at

    check this video

    www.youtube.com/watch

  • Community Member Profile Picture
    Community Member on at

    Thanks. According to her video, the 'Payment Export Format' field is blank, which is how we have this set up in Cronus. And when that field is blank (in Cronus), I am able to export the file.

    In my customer's Test database, the export is not working when the field is blank. When I populate the field, I get an array of different errors.

    So what I'm trying to figure out (since Debugger only points us to the 'Payment Export Format' field, is why is the export file not creating, due to that field being blank, when it does not have to be populated in the first place? I'm looking specifically for object versions to compare.

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    **RESOLVED**

    This is a known issue that was resolved in CU14:

    Cumulative Update 14 - December 2016

    381364

    When you try to export the North America EFT, no error message is displayed and nothing happens if no vendor remittance is selected in report selections in the North American version.

    mbs.microsoft.com/.../NAV2016AppHotfixOverview

    To fix, go into the ‘Report Selection –> Purchase’ and set the Vendor Remittance to Report ID 10083 – Export Electronic Payments.

    I tested this and it worked. The file now exports in my client's TEST database.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans