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

Read the finished import Results log

Confirm which source rows were added and why others were excluded.

Updated 2026-11-11

The Results log records the outcome of a finished import. Use it to confirm what reached Transactions instead of assuming every row in the source was added.

  1. Open the finished batch from Import history.
  2. Read its totals for imported, not imported and blocked rows.
  3. Use Filter by result and the row Reason column to inspect exceptions. Compare the line number, date and amount with the original source.

Not imported can reflect a deliberate skip or an existing duplicate. Blocked rows need their specific outcome reason reviewed. A rejected source value and a closed-period restriction require different fixes.

Reconcile the source coverage

Compare the final results with the statement period and any earlier imports. The total source row count can include rows that were intentionally held back, so the imported count alone does not describe completeness.

Use Review in Transactions when available to continue category and accounting work for the imported records. If an outcome is unexpected, investigate the saved log before reuploading. A second batch can reproduce the same issue while making it harder to identify which copy created a particular transaction.

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.