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

Use Skip all for a reviewed set of possible duplicates

Apply a broad exclusion only when every candidate represents existing activity.

Updated 2026-11-11

Skip all applies one decision to the possible duplicates in the saved import. Use it when you have established that all of those candidates repeat activity already recorded for the account.

  1. Review the file period, source account and earlier imports to understand the overlap.
  2. Inspect candidate descriptions and references, including repeated same-day purchases.
  3. Choose Skip all only after confirming the whole candidate set, then review the remaining ready rows and commit if appropriate.

A large overlap can make the broad action useful, but a shared date and amount alone is not enough to prove every candidate is a repeat. One genuine extra purchase could otherwise be omitted.

If the set is mixed

Use individual row decisions for a mixture of duplicates and separate real movements. Keep the source statement available so each decision has evidence.

After the import finishes, check the not-imported count and row reasons. Compare the final source coverage with the statement. If the result differs from what you intended, investigate the saved batch before uploading a new copy, because another upload can recreate the same unresolved overlap without explaining the earlier decision.

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.