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

Review rows marked Before start date

Check the intended boundary instead of changing genuine transaction dates.

Updated 2026-11-11

Before start date marks source activity held outside the import’s allowed starting boundary. Compare the batch Start date and the financial account’s opening-balance date with the row’s actual source date.

  1. Read the row date and reason in the checked batch.
  2. Confirm the import boundary against your intended coverage and opening evidence.
  3. If the batch was prepared with an incorrect boundary, correct the setup before committing a replacement or revised import.

The source form explains that rows on or before an account’s opening-balance date are always held back. This prevents a source opening value and the activity already represented by it from being mixed casually.

Preserve chronology

Do not move a real transaction to a later date merely to make it eligible. That would change the period in which the movement is recorded.

If earlier activity genuinely belongs in the company’s historical books, review the appropriate opening or historical coverage workflow. Keep the original statement and the saved import check results. Those records show which movements were excluded here and help determine whether they are already represented elsewhere or require separate supported work.

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.