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

Set an optional start date for a transaction import

Hold earlier activity back while preserving its row-level reason.

Updated 2026-11-11

Start date limits which source rows are eligible to be imported from a transaction export. Rows before that date are held back with a reason, while the saved batch keeps their check results.

  1. Choose the financial account and identify the first date of activity you intend to add.
  2. Enter Start date if you need to exclude earlier history from this batch.
  3. After Check rows against the books, inspect Before start date rows and confirm the boundary is correct.

An account’s opening-balance date also matters. The form explains that rows on or before that date are always held back. An optional start date does not override that protection.

Avoid overlapping opening history

Compare the selected boundary with the source opening balance and any earlier imports. A period should not include both an opening value and the same activity already represented by that value without an appropriate accounting plan.

If the boundary is wrong, correct it before committing. If the source dates themselves are correct, do not edit them to make rows eligible. Retain the source file and use the saved check reasons to explain which activity was intentionally excluded.

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.