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

Set First line is column names correctly

Prevent a header from becoming a transaction or a real transaction from being skipped.

Updated 2026-11-11

First line is column names tells the importer whether to treat the first row as headings. Check this setting against the actual file, especially when a bank export has no header or contains introductory lines.

  1. Inspect the first row of the source. Labels such as Date, Description and Amount usually identify a header.
  2. Enable First line is column names when those are headings. Disable it when the first row is an actual transaction.
  3. Review the first transaction in Preview and compare the total row count with the source.

If a real transaction is missing only from the beginning of the preview, the header setting may have skipped it. If words such as Date appear as an invalid transaction, a header may have been read as data.

Remove introductory material carefully

A title, account summary or bank address above the table is not a transaction header. Prepare a working export that starts with the actual table, preserving the original statement separately.

After changing the header setting, recheck column mappings. Header-based suggestions can be useful, but you still need to confirm that the date, description and amounts refer to the intended columns.

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.