The transaction importer reports descriptions longer than 500 characters. Before shortening one, check whether a parsing or mapping problem combined unrelated content into the Description field.
- Compare the mapped description with the original bank record. Check the separator and quotes if the field contains several columns or multiple transactions.
- If the source description is genuinely long, prepare a concise faithful description for the working import while retaining the full original evidence.
- Read the file again and confirm that date, amount, payee and bank reference still map to their intended fields.
Do not discard identifiers that distinguish two otherwise similar transactions without preserving them in the appropriate source or reference field. The goal is to fit the supported field while keeping the movement traceable.
Check the cause across the file
Many unusually long descriptions usually indicate a structural issue. Fixing the delimiter or broken quote may resolve them without any content reduction.
If you cannot shorten a genuine source description without losing necessary meaning, ask support about the appropriate record format. Keep the original export and note the affected line so the problem can be reviewed against complete evidence.
Was this article helpful?
Tell us whether this answered the question you came with.