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

ach

(2) Share

Report

Posted on by peter fun

887

How can I change the order of Addenda and Entry Detail records in an EFT file in Business Central?

I have been troubleshooting an EFT file formatting issue in Business Central and believe the problem is related to the order in which the Addenda and Entry Detail records are being generated.

In the EFT file generated from Business Central, the Addenda record is currently appearing before the Entry Detail record. For example, in the latest EFT file:

3rd line = Addenda record (contains the External Document No.)
4th line = Entry Detail record

However, the required format is:

Entry Detail record
Addenda record

This order should be followed for every payment.

Could anyone please advise how this can be configured in Business Central's EFT/Data Exchange Definition so that the Entry Detail is generated first, followed immediately by its corresponding Addenda record?

Is this something that can be configured through the Data Exchange Definition, or would it require a developer customization?

Categories:

Microsoft Dynamics RMS

Dynamics 365 Business Central

Dynamics 365 Business Central migration

Microsoft Dynamics NAV

All responses (6)

Answers (0)

Sort by

Suggested answer

Teagen Boll 3,875 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Is the adenda record set as a Footer or Header?
Data exchange definitions print in order of the Code field in the following order: Headers > Details > Footers. In the case of my screenshot above it would be Header A > Header B > Detail > Footer A > Footer B.

You can change the code or the Line Type to change the order.

Best,
Teagen Boll, CPA
LinkedIn
Blog posts
peter fun 887 on at

Like (0)

Report
Copy link

Link copied!

Adenda is showing in first line
Suggested answer

Teagen Boll 3,875 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi Peter, if the adenda is a Header line type it will always show first. You need to check the setup in the data exchange definition and set it as a footer or change the code to make sure it prints in the correct order.

Best,

Teagen Boll, CPA
LinkedIn
Blog posts
Suggested answer

Mansi Soni 10,422 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hello @peter fun ,

In the Data Exchange Definition, check the Line Type and Parent Code for the Addenda line. If it is defined as a Header, it will be generated before the Entry Detail. Ideally, configure the Entry Detail as the parent and Addenda as its child/footer/detail line so the sequence becomes Entry Detail > Addenda. If the required sequence cannot be achieved through the standard Data Exchange Definition, then a developer customization may be needed.

Hope this answer helps you!

Regards,
Mansi Soni
peter fun 887 on at

Like (0)

Report
Copy link

Link copied!

it configured like belovv: guide me kindly
Suggested answer

Assisted by AI

OussamaSabbouh 19,425 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hello Peter,
This is partly configurable, but there is no simple “record sequence” field in the Data Exchange Definition. First check Line Definitions: the Entry Detail should be the parent/detail record and the Addenda should be configured as its child using Parent Code = Entry Detail line code, since Business Central supports parent/child relationships between exported records. Also, do not use the Priority field in Field Mapping for this—it only controls the processing order of field mappings, not the order of records in the output file. If the hierarchy is already correct but BC still writes the Addenda before the Entry Detail, then the sequence is being controlled by the Data Handling / Reading-Writing / mapping codeunit, and you would need a small customization or a custom payment export definition/codeunit to produce Entry Detail → Addenda for each payment. I would therefore verify the Parent Code and Line Type setup first before customizing.
Regards,
Oussama Sabbouh