Small and medium business | Business Central, N...

NACHA File format

(4) Share

Report

Posted on by BBBCMAN

531

Hi All,

I am setting up export file format for CHASE Bank and the file format shown in the list on drop down has only 4 options and doesn't have NACHA format. How to add export file format NACHA in BC. The formats I can see as follows.

Categories:

Dynamics 365 Business Central

All responses (5)

Answers (0)

Sort by

Suggested answer

Assisted by AI

OussamaSabbouh 20,100 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hello BBBCMAN,
The list in your screenshot is Bank Export/Import Setup, and you cannot get NACHA simply by adding a new row there—the export format also needs the corresponding processing logic. In the North American/US version of Business Central, ACH/NACHA payments are handled through the EFT process: prepare the Payment Journal, set Bank Payment Type = Electronic Payment (or Electronic Payment-IAT for international ACH), export the payment, and then use Generate EFT File. Microsoft specifically documents ACH/EFT for North American versions. If your environment only shows SEPA formats like the screenshot, first verify that the environment/company is using the US localization; SEPA entries normally indicate that you are looking at the generic/European bank-export formats rather than the US EFT functionality. For Chase, also obtain their exact NACHA specification (usually CCD/CCD+, PPD, etc.), because banks can require variations from the standard NACHA layout. If the standard BC EFT output doesn't meet Chase's specification, the recommended options are AMC Banking 365 to convert the payment data to the bank-required format, or a custom Data Exchange Definition/AL extension for the Chase layout. I would not manually create a NACHA entry in Bank Export/Import Setup without the required processing codeunit.
Regards,
Oussama Sabbouh
BBBCMAN 531 on at

Like (0)

Report
Copy link

Link copied!

Thanks Oussama for your kind reply. I exported data exchange definition and imported them into this company and I added into export/import setup new format. How to test this since I am not able to find bank payment type = electronic payment as per your notes. I created a payment journal selected an employee and balance type as bank and press export and getting the following error.
If requesting support, please provide the following details to help troubleshooting:
Error message:
The file export has one or more errors.
For each line to be exported, resolve the errors displayed to the right and then try to export again.
Internal session ID:

Application Insights session ID:

Client activity id:

Time stamp on error:
2026-09-28T15:54:59.0709019Z
User telemetry id:
b14dfc84-0dfa-4f82-9f24-d98966af0f3b
AL call stack:
"Payment Journal"(Page 256)."ExportPaymentsToFile - OnAction"(Trigger) line 45 - Base Application by Microsoft version 28.5.54151.54677
Suggested answer

YUN ZHU 103,635 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, hope the following can give you some hints.
Setting Up NACHA file format for ACH Payments in Business Central using Data Exchange Definition
PS: Add more custom processing when importing Bank Statement (Bank Export/Import Setup) – Customization
https://yzhums.com/44582/

Thanks.
ZHU
Suggested answer

Grigorios Mavrogeorgis 3,638 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, NACHA in BC isn't a format you pick by that name, it comes from the EFT setup of the US localization. In a US company you normally see a line like US EFT DEFAULT in Bank Export/Import Setup (there are CA and MX ones too), and that goes in Payment Export Format on the bank account card. Your list has only SEPA plus Yodlee, so either the environment isn't the US version, or the company was created without the standard setup data.
I'd check Data Exchange Definitions in Tell Me first. If the US EFT definition is there, make a New line in Bank Export/Import Setup, direction Export, and point it to that definition. Copy the processing codeunit from a US Cronus company, I wouldn't trust my memory on the number. Also as far as I know the export stops if Transit No. and Last Remittance Advice No. are empty on the bank account.
Which localization is it, US or W1?
Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis
Suggested answer

D365BC_AmanKr 180 on at

Like (1)

Report
Copy link

Link copied!
Hello,
In Business Central, you cannot simply add “NACHA” as a new row in Bank Export/Import Setup and expect it to work—the export format requires the correct processing logic behind it. In the US localization of BC, ACH/NACHA files are generated through the EFT functionality rather than the SEPA formats you see in your screenshot. That’s why you don’t see “Bank Payment Type = Electronic Payment” in your Payment Journal: it only appears when the US localization and EFT setup are enabled.
To move forward, first confirm that your company is running the North American version of Business Central. If you only see SEPA formats, you are likely in a non‑US localization where EFT/NACHA is not included by default. For Chase Bank, you’ll also need their exact NACHA specification (CCD, CCD+, PPD, etc.), since banks often require variations. If the standard EFT output doesn’t match Chase’s requirements, you have two main options:
Use AMC Banking 365 or a similar ISV solution to convert BC payment data into the NACHA format required by Chase.
Build a custom Data Exchange Definition/AL extension that implements the Chase NACHA layout and processing codeunit.
The error you’re seeing (“The file export has one or more errors…”) indicates that the Data Exchange Definition you imported isn’t fully aligned with the Payment Journal setup or the processing codeunit. Each line in the journal must have the correct Bank Payment Type and mapping fields defined in the Data Exchange Definition. Without the EFT logic enabled, the export will fail even if you added a NACHA entry in the setup.

Hope it will help you.
Please Verify if you found the answer helpful so that it will help others.
Many Thanks
Aman