I get an error converting my transfers CSV: decision tree

Published on · Updated on

I get an error converting my transfers CSV

Before emailing support, walk through this decision tree:

1. Did you flag the header row?

If your CSV has a header (first row with column names), tick “first row is header”. If you don’t, “Name,IBAN,Amount” gets parsed as a transfer and obviously bounces.

2. Is the separator one of the supported ones?

We detect comma, semicolon and tab. If you used another character (| for instance), replace it or re-export with a standard separator.

3. Is the encoding UTF-8?

Weird characters (é, ñ) signal that the CSV is ISO-8859-1 but we read it as UTF-8. Save again in UTF-8 from Excel or LibreOffice.

4. Is every IBAN valid?

Make sure each has the correct length and starts with the right country code (ES, DE, FR…). A single invalid row can reject the whole file.

5. Are amounts consistent?

Don’t mix comma- and dot-decimal in the same file. Review the amounts come out wrong guide.

6. Still failing?

Contact support with:

  • Screenshot of the error.
  • First row of the CSV (you can anonymise names and IBANs).
  • How you exported the file (Excel, ERP, by hand).

Conclusion

90% of errors are resolved by the 5 steps above.


Frequently Asked Questions

How do I know if my CSV is UTF-8?
Open it in an editor (VS Code, Sublime) and check the status bar. If it says 'UTF-8', good. 'ISO-8859-1' or 'Windows-1252' need conversion.
Is the error always on a specific row?
Yes, almost always. Our parser stops at the first invalid row and shows the line number. Start there.
Do I need to delete empty columns?
Recommended. If you leave them, make sure the header has the same number of columns as the data rows.

Validate your SEPA XML file before uploading

Try it now →
Was this article helpful?

Related articles