Any importer

“The download worked last month and fails now”

Short answer

Nothing changed on your side because the change was on theirs: rebuilt banking platforms alter delimiters, date formats and column names, and mergers change the bank and account identifiers. Running the old working file and the new failing one through StatementFix shows what moved. If the new file is merely different rather than defective, update your import mapping instead of the file.

When a routine that worked for years fails and nothing changed on your side, something changed on theirs. Website upgrades quietly alter export formats, and the resulting file is usually valid — just different.

Symptoms

  • The same monthly routine now produces a rejected file
  • Column order or names changed in a CSV export
  • An OFX download now arrives with a different extension or structure
  • Other customers of the same bank report it at the same time

What actually causes it

Cause 1

New export code with different conventions

Rebuilt banking platforms tend to change delimiters, date formats and column names. Each change is small; together they break every downstream tool.

Cause 2

A regression in the new exporter

Fresh export code reintroduces old bugs: unescaped ampersands, missing headers, duplicated transaction ids. These are genuine defects on the bank's side and worth reporting.

Cause 3

Identifiers changed after a merger

Bank and account identifiers change when institutions merge, so files that are otherwise identical are treated as belonging to a different account.

How to fix it

  1. Drop both the old working file and the new failing one into the fixer below and compare what it reports — the difference is usually immediately visible.
  2. If the new file has structural defects, repair it here and report the problem to the bank; regressions get fixed when customers describe them precisely.
  3. If the new file is merely different, update your import mapping rather than the file.
  4. Keep one known-good file from each bank. Having a baseline turns "something broke" into a five-minute comparison.

Skip the manual edit — fix it automatically

Running the old and new file through the same checks turns a vague "it stopped working" into a specific list of what changed. Free, no signup, no upload.

Open the fixer

Your file never leaves your browser.