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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Date format for bank reconciliation bank statement import

(3) ShareShare
ReportReport
Posted on by 541
I have a CSV file here to upload for a bank account reconciliation for the bank statement entries. Most of the time the date has been in format MM-DD-YYYY, so i have been able to configure the data exchange definition and import with no issue. However, the current file I have the date is in format DD-MM-YYYY, so I receive an error when importing the CSV: the value in line 1, column 4 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 "01-12-2025".
I have tried both types of text and date, as well as using the transformation rule for US_date_format. Any suggestions, on the data exchange, transformation rule or elsewhere to be able to read the date correctly? I do not want to manually edit the date on the CSV as there are too many lines to do so
I have the same question (0)
  • Verified answer
    Valentin Castravet Profile Picture
    32,506 Super User 2026 Season 1 on at
    Have you tried using dd-MM-yy as the data format for the data field in the data exchange definition? You shouldn't have to use a transformation rule.
     
  • Suggested answer
    YUN ZHU Profile Picture
    99,974 Super User 2026 Season 1 on at
    Hi, hope the following can give you some hints.
    Dynamics 365 Business Central: Add more custom processing when importing Bank Statement (Bank Export/Import Setup) – Customization
     
    Thanks.
    ZHU
  • Suggested answer
    Rajvi Shah Profile Picture
    246 on at
    Hello,
     
    This issue occurs because Business Central reads the date based on the Data Formatting Culture defined in the Data Exchange Definition. Currently it is expecting MM-DD-YYYY (en-US), but your file contains DD-MM-YYYY, so the system misinterprets the value 01-12-2025.
  • Suggested answer
    OussamaSabbouh Profile Picture
    14,539 Super User 2026 Season 1 on at
    Hello,
    Your CSV import fails because the Data Exchange Definition expects MM-DD-YYYY, while the file now contains DD-MM-YYYY. The fix is simply to edit the Column Definitions for that field, keep Data Type = Date, and change Data Format to dd-MM-yyyy so it matches the CSV format; once the format matches the incoming data, Business Central will import it correctly without needing transformation rules or manual edits to the file.
     
    Regards,
    Oussama Sabbouh

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,024 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,145 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 705 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans