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

Resume a transaction import that stopped partway through

Continue the saved batch while preserving rows already added.

Updated 2026-11-11

When an import stops, rows already added are kept. Open the same saved batch and use Resume import when offered to finish the remaining eligible work.

  1. Return to Import history for the original company and locate the batch by source file and account.
  2. Read its current status and any action error. Confirm that it is the batch you intended to resume.
  3. Choose Resume import and wait for the updated results rather than starting another upload of the same rows.

A progress display can show Import paused when a committing batch is not actively running in the current view. The saved batch state, not the earlier browser progress bar, determines what still needs work.

Check the outcome after resuming

Review imported, not-imported and blocked counts. Inspect row reasons for anything that did not complete. A resumed operation can encounter current access or period conditions that require attention.

If the workspace or signed-in user changed, reload the correct scope before continuing. Report the source filename, account and exact message if recovery fails. Do not remove already imported transactions simply because the browser stopped before showing a final confirmation.

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.