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

Discard an import before its rows are added

Keep the checked history while stopping an uncommitted batch.

Updated 2026-11-11

Discard stops a saved import that has not yet added its rows. The confirmation explains that the checked rows remain in history, so you can still see what was prepared and why it was stopped.

  1. Open the staged batch and confirm its filename, account and company.
  2. Choose Discard and enter a short reason that explains the decision, such as selecting the wrong source account.
  3. Confirm the action and check that the batch reports it was discarded before import.

Use a specific reason rather than a generic note. It helps distinguish a deliberate replacement from a failed import when you revisit history later.

Start a corrected batch

If you need to try again, fix the account, file or mapping problem first. Compare the new preview with the source before checking against the books.

Discarding is different from rolling back rows already imported. If the batch has started committing, inspect its current result and available actions instead of assuming nothing was added. Existing transactions can remain, especially where later review or accounting work protects them. Always base recovery on the saved status.

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.