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

Read one transaction export at a time

Keep each checked batch tied to one source account and file.

Updated 2026-11-11

The transaction-export upload accepts one bank export at a time. Each file should represent one account, so the import can check its rows against the selected financial account.

  1. Choose the company and account for the first file.
  2. Select or drop one supported bank export, then read and review its rows.
  3. Finish the batch or leave it saved with a clear status before starting the next file.

If you drop several files together, the source step asks you to choose one. Combining separate accounts into one larger file is not a reliable workaround, because account and currency identity need to remain clear.

Prepare a sequence of files

For a large historical import, use distinct account and period filenames. Check that adjacent periods do not unintentionally overlap and retain a record of each finished batch’s imported and excluded counts.

If a batch is interrupted, resume that saved batch before importing the next copy of the same period. A clean sequence makes it easier to compare the final activity with bank statements and identify any gap without relying on memory about which file was uploaded last.

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.