Short Answer: Dates fail to parse when the chosen transaction date column or the '4. Date format' order doesn't match the actual date data; fix these settings and re-check the preview.
PreRequisites
-
'Data preview (20 rows)' visible
-
'3. Transaction date' selected
Steps
-
Confirm '3. Transaction date' points to the correct column (for example, 'Posting Date').
The correct column is selected as the transaction date. -
Inspect sample cells in 'Data preview (20 rows)' to see the raw date format used (e.g., '05-Jan-2025' or '01/07/2025').
You understand the day/month/year order in the file. -
Under '4. Date format' set 'First value', 'Second value', 'Third value' to match the previewed order (Day/Month/Year or Month/Day/Year).
Date format order matches the file. -
If some rows still parse incorrectly, check the source file for mixed date formats and normalize them in the source spreadsheet before re-mapping.
Dates are consistent and parse correctly after normalization.
Troubleshooting
-
Some rows parse correctly while others show wrong dates.
LikelyCause: The date column contains mixed formats (different rows use different formats).
Action: Open the source file, standardize the date format across rows, then re-open the dialog and reapply the selected '4. Date format'. -
No date values appear after selecting a transaction date column.
LikelyCause: Wrong '2. Header row' caused the wrong column to be identified as the transaction date.
Action: Set '2. Header row' to the row that contains your header names, then re-select the transaction date column.