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

Check a file whose date range ends earlier than expected

Confirm export completeness before treating the imported period as covered.

Updated 2026-11-11

If Preview ends earlier than the period you expected, inspect the source export before importing. The displayed date range summarizes readable rows and can reveal a truncated download or an unintended bank filter.

  1. Compare the first and last transactions in the file with the bank’s selected export period.
  2. Check whether rows with later dates have parsing problems and are excluded from the preview summary.
  3. Obtain a complete or corrected export and review the date range again.

An export named for a full month can still contain only part of it. The filename does not establish coverage.

Avoid overlapping replacement work

If you already imported the partial file, use its Results log to identify the dates and rows that were added. A later complete export needs duplicate review against that existing activity.

When checking the missing interval, include days with no transactions as legitimate possibilities. A gap in activity is not automatically a missing file. Compare the statement and opening or closing evidence to determine whether the period is complete, then retain that evidence with your review.

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.