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

Roll back an import while preserving protected work

Understand why some imported rows may remain after rollback.

Updated 2026-11-11

Roll back removes imported rows that nobody has worked on yet. Rows that were reviewed, split, matched, given documents or questions, or placed in a closed period can remain, with the log explaining why.

  1. Open the finished batch and confirm that it is the import you intend to undo.
  2. Choose Roll back and provide a clear reason for the audit trail.
  3. Read the result and inspect any Partly rolled back notice and retained row reasons.

Rollback is not a promise to erase every consequence of an import. Protected records may support accounting work that needs its own correction process.

Correct retained rows separately

Use Transactions to investigate records that remain. Check their current review, matching and period status before changing them. If a record is posted or supports another document, follow the relevant authorized correction workflow.

Before importing a corrected source file, compare it with retained rows so the same activity is not added twice. Keep the original batch log and the reason for replacement. A partial rollback should be treated as an explicit mixed outcome, not as a clean empty account ready for an unchecked reimport.

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.