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

Prepare dates that use written month names

Convert unsupported text dates to a consistent verified calendar format.

Updated 2026-11-11

The structured import date parser expects numeric date layouts. If a source uses written month names, prepare a working copy with confirmed dates in YYYY-MM-DD before reading the rows.

Use the original bank statement or export as the authority for the month, day and year. A conversion should change the representation while preserving the date itself.

Review the converted file

  1. Confirm the source language and month abbreviation, especially if more than one abbreviation could be misunderstood.
  2. Export the date column as full calendar dates rather than spreadsheet display text or serial numbers.
  3. Inspect the first and last dates, month boundaries and any rows with unusual source wording.

If the source omits a year, establish it from the statement period before completing the working file. Do not assign the current year to every row without evidence.

Keep a copy of the original text dates so a later reviewer can trace the conversion. After import preview, compare known transactions with their statement dates. A successful parse shows the format is readable; it does not independently confirm that an ambiguous source date was interpreted correctly.

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.