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

Fix a preview that places each row in one column

Choose the correct delimiter before remapping the fields.

Updated 2026-11-11

When an entire source line appears as one column, the selected separator probably does not match the file. Check the delimiter before changing the date or amount mappings.

  1. Look at the source text and identify the character between fields: comma, semicolon, tab or pipe.
  2. Choose that Separator and inspect the preview again.
  3. Map Date, Description and the applicable amount fields once the columns split correctly.

If the source really contains one combined text field per transaction, obtain a structured export from the bank or prepare a reviewed table from the original evidence. The importer needs separately mapped values for reliable dates and amounts.

Check quoting too

A whole row enclosed as one quoted field can also appear as a single column. Preserve legitimate quoted descriptions, but correct an accidentally quoted entire table through the source export or spreadsheet application.

After fixing the structure, compare the row count and totals. A delimiter change can reveal additional fields or rows that were previously unreadable. Do not commit the import based only on the disappearance of the initial formatting error; confirm that the interpreted transactions match the source.

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.