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

Fix unexpected text after a closing CSV quote

Check delimiter and quoting when a field ends incorrectly.

Updated 2026-11-11

Unexpected text after a closing quote means the parser found characters where a separator or row ending was expected. Check both the file’s delimiter and the quoted field on the reported line.

  1. Confirm the Separator setting matches the export. A wrong separator can make otherwise valid fields appear malformed.
  2. Inspect the reported source line and compare it with the original export. Look for pasted notes or punctuation outside the quoted field.
  3. Correct the file structure through the source application, then read and preview the file again.

Spaces after a closing quote are different from extra text that changes the field structure. Avoid removing meaningful description text merely to clear the error.

Check the neighboring columns

Once the row parses, verify the date, description and amount against the bank record. A repair that shifts an amount into a reference column can leave readable but incorrect data.

Retain the original export and a record of any working-copy changes. If the bank-generated file itself remains malformed, request another supported format such as a clean CSV or OFX export rather than reconstructing transactions from uncertain fragments.

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.