Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.
Statements and transaction imports

Fix Date does not match the selected format

Check the mapped date column and date convention before editing source rows.

Updated 2026-11-11

Date does not match the selected format means the mapped value could not be interpreted as a valid date under the current settings. Start with the source column and Date format selection.

  1. Compare Date as read with the original export. Make sure the mapped field is a transaction date rather than a reference, heading or account balance.
  2. Choose the appropriate year-first, month-first or day-first convention.
  3. Inspect the row again and check the file’s overall first and last dates.

If only a few rows fail, they may contain impossible dates, text month names, spreadsheet serial numbers or a different format from the rest of the file. Confirm each affected value from the bank before preparing a consistent working copy.

Do not substitute download dates

The date you exported or uploaded the file does not replace the movement’s date. Use the source transaction evidence to repair a missing or unreadable value.

If the correct source date falls outside your intended import period, let the start-date or closed-period checks handle it. A format problem and a period restriction have different causes, and correcting one does not justify changing the other.

Was this article helpful?

Tell us whether this answered the question you came with.

Related articles

Still stuck?

Tell us what you were trying to do and where it went wrong. If you are already a client, you can also open a support case from Help and support in your workspace.

We confirm who you are before we change anything on an account.