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

Exclude subtotals and statement summaries from CSV movements

Keep the transaction table separate from totals used as evidence.

Updated 2026-11-11

A subtotal or closing balance is not an individual bank movement. Keep these source summaries as evidence, but exclude them from a working CSV intended to import one movement per row.

  1. Compare the source table with its section totals, opening balance and closing balance.
  2. Prepare a working transaction table containing only actual movement rows and a clear header.
  3. Check that the remaining row count and summed inflows and outflows agree with the source detail.

Informational rows often appear as missing-date or missing-description errors. Some totals also look like valid amounts, so you should identify their meaning rather than relying entirely on validation errors.

Retain the full original

Do not discard the bank statement’s summary pages. They are useful for checking coverage and reconciliation even though they should not become extra transaction rows.

If a row’s purpose is unclear, investigate before excluding it. A bank fee or interest entry near a subtotal can be a real movement. Use source descriptions and statement structure to distinguish it, then preserve its actual date and amount in the working import.

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.