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

Retry a failed check while keeping the column mapping

Recover the staging step without rebuilding a verified source layout.

Updated 2026-11-11

If Check rows against the books fails, the page can keep your mapping and ask you to try again. Review the error and current source before retrying the check.

  1. Confirm that the company, account and file remain the intended ones.
  2. Check that the separator, date convention and amount mappings still match the preview.
  3. Use the offered retry and wait for a saved batch result before continuing.

A failed staging request is not a completed import. It also does not prove that the source file itself is unreadable, especially when the local preview was already correct.

Avoid changing valid source data

Do not edit dates or amounts to address a temporary request failure. Preserve the verified mapping and respond to the actual message, such as a source problem or current access issue.

If the result remains uncertain, check Import history for the same source and account before creating another batch. Report the exact message and which stage failed. Distinguishing Read rows, Check rows against the books and the final Import action helps support identify whether the issue occurred before or after a saved batch was created.

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.