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

Data Import Exchange Definition Differences

(5) Share

Report

Posted on by Jacob

192

Hi,

I have a data import exchange set up like so:

The field definition mapping is as follows:

In this case related to this problem - the Transformation rule is irrelevant.

The data exchange definition is working for one file, but not the other and is erroring on the date field.

I have confirmed that both files date field is (as an example) - dd/MM/yyyy = 20/08/2025.

File 1 will import successfully, yet file 2 will error with this:

The value in line 1, column 7 has incorrect format or type.
Expected format: Date, according to the Data Format and Data Formatting Culture of the Data Exch. Column Def.
Actual value: "2025-07-08".

The value in the file is 100% 08/07/2025 as displayed here:

and more importantly:

I have confirmed:

- Both files encoding is the same - .csv

- I have tried both encoding csv as UTF-8 and .csv with no luck.

- Removed the definition from both bank accounts and readded.

- Added and removed the data transformation rule in the field mapping

What causes the definition to work on one, fail on the other?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

Mansi Soni 9,839 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hello,

The error happens because in the second file, even though Excel shows the date as 08/07/2025, the actual raw value inside the CSV is stored as 2025-07-08 (ISO format). Business Central checks the raw text against the Data Format (dd/MM/yyyy) you defined in the Data Exchange Definition, so when it sees 2025-07-08, it doesn’t match the expected format and fails. The first file works because its raw values really are in dd/MM/yyyy. Always ensure the exporting system always outputs the date in the required format.

https://community.dynamics.com/blogs/post/?postid=5bc2164b-25dc-ee11-a73d-0022484c32cd
https://learn.pocketsmith.com/article/103-transaction-dates-are-incorrect-after-importing-a-bank-file#prevent
https://learn.microsoft.com/en-us/dynamics365/business-central/across-how-to-set-up-data-exchange-definitions

Hope this answer will help you!

Regards,
Mansi Soni

Was this reply helpful? Yes No
Jacob 192 on at

Like (2)

Report
Copy link

Link copied!

Hey @Mansi Soni,

Unfortunately, that isn't the case. The Raw text output for the date is in dd/MM/yyyy format.

This is the raw text date:

From what I can tell it there is nothing in the output that is doing yyyy-mm-dd

Was this reply helpful? Yes No
Suggested answer

Dhiren Nagar 2,890 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi,

You need to change the format to d/MM/yyyy.

This is because your date if is in the single digit does not have 0 before it for e.g. 28 is showing as 28 but 07 is showing as 7 which is incorrect date format for your file. So use d/MM/yyyy and try again.

I hope this helps.

Regards,

Dhiren.

If this works mark the answer as verified.

Was this reply helpful? Yes No
Jacob 192 on at

Like (2)

Report
Copy link

Link copied!

Hey @Dhiren Nagar,

Unfortunately, didn't work either. I did check the other file and the date format did only have dd/MM/yyyy so that part makes sense.

Despite this - I have changed the date format to 'yyyy-MM-dd' and this appears to be working for both.

This honestly seems like D365 is doing something under the hood. The format in the file is 100% either dd/mm/yyyy or d/mm/yyyy. Doesn't really make sense why one would work and the other not other than magic but have to accept that there is some.

Thanks again for the help

Jake

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,177 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

adding more details

https://community.dynamics.com/blogs/post/?postid=5bc2164b-25dc-ee11-a73d-0022484c32cd

✅ Mark the checkbox below if this answer helped you.

Was this reply helpful? Yes No