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

Data Exchange Definition for Payment Export - tables for export HEADER and FOOTER

(4) Share

Report

Posted on by ploo

139

Hi experts

I set up a data exchange definition where the output file requires a HEADER, a BODY, and a FOOTER.

I was able to create the Line and Column Definitions for the BODY and mapped columns to the payment journal using table 1226. But I cannot find the table to map the column definitions for the HEADER and FOOTER lines (the payment journal doesn't have a header or footer).

Does anyone know the correct tables to use?

Thanks

Peter

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

Teagen Boll 3,214 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi Peter,

This could depend on the country/localization you have. Here are some common tables used.

USA

Header: 10300 - ACH US Header

Body: 10301 - ACH US Detail

Footer: 10302 - ACH US Footer

Canada

Header: 10303 - ACH RB Header

Body: 10304 - ACH RB Detail

Footer: 10305 - ACH RB Footer

Here is a screenshot example of the ACH US Header:

Hopefully that gives you a starting point.

Best,

Teagen Boll

Work: Catapult ERP

Social: LinkedIn

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 101,995 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Same question: Data Exchange Definition - code unit for Payment Export that uses Header, Body and Detail lines

Was this reply helpful? Yes No
ploo 139 on at

Like (1)

Report
Copy link

Link copied!

Hi @Teagen Boll and @YUN ZHU,

This post is slightly different from the other post.

My question in this post is regarding the tables used in mapping the Line Definition columns/fields for the Header and Footer.

My client is on this version

Version: W1 27.5 (Platform 27.0.50190.0 + Application 27.5.46862.50530)

To map the Detail Line Definition, I found table 1226 (Payment Export Table) but couldn't find a table for the Header and Footer. I even searched for "ACH" (according to Teagan's example) but couldn't find this.

The bank file export of the Detail line works.

W1 is the Asia region - are there tables for Header and Footer line definition mapping?

Thanks

Peter

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 17,676 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello Peter,

For payment export data exchange definitions, you normally map the actual payment lines to table 1226 – Payment Export Data, not to the journal directly; for HEADER and FOOTER, there usually isn’t a separate “payment journal header/footer table” to pick, because those records are file-structure lines, not real journal records. If the header/footer values are fixed text, use the Constant field in the column definitions; if they need calculated values like file date, total amount, line count, company bank info, etc., then standard setup alone may not be enough and you’ll need the related export/codeunit logic customized or use an existing payment export format as a template. Microsoft’s docs also hint at this: for payment exports, you create line definitions per payment/file line type, and columns can export constants, but the actual mapped payment data comes from the payment export data structure.
Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Gerardo Rentería Ga... 27,280 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

ACH file format for Business Central - Sharing The Righter Way - Cynthiapriebe.com

Definiciones de intercambio de datos (exportación de pagos) en Business Central

Best Regards
Gerardo

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 2,544 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Peter,

For HEADER and FOOTER lines in Data Exchange Definition, BC does not require you to map them to a specific table. You can use Constant value in the column mapping. Many bank file definitions work this way, especially SEPA exports.
In the Column Definition for HEADER and FOOTER, you can set Data Type to Text and use a Constant, or use fields from Gen.

Journal Batch (Table 232) or Gen. Journal Line (Table 81) if you need dynamic values like batch name, posting date, or total amount.
For totals in the FOOTER (like total amount or record count), use the Aggregation Type field on the Column Definition, set it to Sum or Count, and it aggregate from the BODY lines automatically.

Also worth check existing standard data exchange definitions like SEPA CT pain.001 for reference. Open one and see how Microsoft did the HEADER/FOOTER mapping, this is the easiest way to understand the pattern.
Hope this help, Best regards

✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.

Regards

Gregory Mavrogeorgis

Work: GMSOFT Limited
Blog: Inside Business Central
LinkedIn: www.linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No
ploo 139 on at

Like (0)

Report
Copy link

Link copied!

Hi @Grigorios Mavrogeorgis,

Thanks for the idea of aggregation in the FOOTER line definition.

The documentation for defining Data Exchange Format isn't extensive (always referring only to Date formatting example).

CoPilot suggested this formatting which I will test:

Furthermore, the Detail line definition is from mapping table 1226 - Payment Export Data where there is no implicit Header or Footer information.

To draw the field mapping from a similar table (81 or 232), is there a way to associate the payment batch with the correct row in these tables? Where do I set the filter (e.g. batch name) to associate?

Thanks

Peter

Was this reply helpful? Yes No