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

Use a payee-only export carefully

Review the description derived from a merchant or payee field.

Updated 2026-11-11

When an export has a payee or merchant field but no separate description, the importer can use that field as the description. Check that the resulting text identifies each movement clearly enough for later review.

  1. Inspect the source headers and the proposed Description mapping.
  2. Compare a few rows with the bank statement, especially generic processor or transfer labels.
  3. Preserve any available bank reference and additional source evidence that helps distinguish similar movements.

A recognizable merchant name can make the row readable, but it may not explain what was purchased. Category review can still require a receipt or other business context.

Avoid invented narratives

Do not replace a vague payee with an assumed expense purpose merely to make the import look more complete. Keep the source wording and add supported context through the appropriate review workflow.

If the mapped payee is blank on some rows, those rows still need a valid description from source evidence. Check for a memo or details column before discarding the row. Review the final preview and totals after changing the mapping so one fix does not shift other fields.

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.