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

Check a payee that exceeds the import field length

Preserve the vendor identity without placing a whole narrative in Payee.

Updated 2026-11-11

Payee is longer than 200 characters means the mapped payee field exceeds the supported length. Check whether you selected a merchant-name column or a longer transaction narrative.

  1. Compare the Payee mapping with the original export’s headings and contents.
  2. If a full narrative was mapped as Payee, use the appropriate merchant field and keep the movement narrative in Description.
  3. If the genuine payee name is unusually long, prepare a faithful usable form while retaining the complete original source.

The optional Payee field adds context; it does not replace a valid date, description or amount. Avoid moving arbitrary text into another field simply to clear a length warning.

Keep similar names distinguishable

If a merchant label includes a location or account identifier that distinguishes repeated charges, preserve that context in the source evidence or appropriate description. A shortened label should not turn different counterparties into an apparent match.

After remapping, check representative rows and their amounts again. If many payees are unexpectedly long, inspect the separator and quoting because combined columns can create the same symptom. Keep the original file for later duplicate and category review.

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.