The structured importer limits Bank reference to 120 characters. A longer value may indicate that the wrong column was mapped or that several fields were joined together.
- Compare the mapped value with the original export’s transaction identifier, check number or reference field.
- Review the separator and quotes if the value contains a full description or several adjacent columns.
- Correct the mapping or obtain a supported export, then inspect the resulting reference alongside the transaction date and amount.
Do not truncate a long identifier arbitrarily when doing so could make two distinct references identical. Reference integrity can help later source review and duplicate investigation.
When the source identifier is genuinely long
Keep the complete original export and ask support how to preserve the identifier through the supported workflow. The optional field should not be replaced with an invented sequence merely to make the import pass.
If a reference is absent in the source, leave the optional mapping unset rather than filling it with unrelated values. After any correction, check the row count and compare repeated merchant charges carefully; a shared date and amount alone do not establish that they are duplicates.
Was this article helpful?
Tell us whether this answered the question you came with.