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

Read a pipe-delimited transaction file

Use Pipe when vertical bars separate the source fields.

Updated 2026-11-11

Choose Pipe in Separator when a vertical bar separates each field in your export. The importer supports pipe-delimited rows alongside comma, semicolon and tab formats.

  1. Confirm that vertical bars divide the date, description and amount fields in the source.
  2. Set Separator to Pipe and review the resulting column names or column positions.
  3. Map the required fields, then compare several preview rows with the original file.

A vertical bar inside a description needs appropriate quoting when it is also the separator. If the preview shows an unexpected extra column, inspect the source row rather than shifting the mapping to compensate for only that row.

Verify the full import

The preview displays the first rows, while the next step checks every row against the books. Use both stages. A correct first row does not prove that the rest of the export follows the same structure.

If you prepare the file yourself, keep one movement per row and a consistent number of fields. Retain the unmodified source as evidence. Avoid using pipes as decorative separators in an introductory note above the transaction table, since that material can be mistaken for data.

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.