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

Read the reason for a rejected import row

Resolve the specific source problem before attempting the row again.

Updated 2026-11-11

Rejected means a checked row has a source or parsing problem that prevents import. Read its Reason and compare the line with the original export before making a correction.

  1. Filter the checked batch to rejected rows and identify the source line number.
  2. Check the raw date, description, amount and currency against the original file.
  3. Correct a mapping error or prepare a supported working value only when source evidence establishes it.

Different reasons need different fixes. A missing description, an impossible date, a currency conflict and an invalid number should not all be handled by a blanket reupload.

Preserve the unresolved set

If you continue with valid rows, keep a record of the rejected rows that still need resolution. A completed batch with excluded rows may leave a gap in the statement period.

When importing a corrected file later, compare it with the rows already added from the first batch. Use the saved logs and duplicate decisions to avoid repeating successful activity. Do not change genuine transaction details simply to make the corrected file appear different from the original.

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.