“My Chase download will not import”
Chase offers several download formats under labels that do not match what the files actually are, and each one has its own way of failing. Knowing which you downloaded is usually enough to explain the error you got.
Symptoms
The QFX download is refused as an invalid Web Connect file The CSV imports with columns shifted or dates misread The download worked last month and fails now with no change on your side
What actually causes it
The wrong format for the target app
Chase labels downloads by product — Quicken, QuickBooks, Spreadsheet — and picking the Quicken variant for QuickBooks (or the reverse) produces a file the app refuses on identifier grounds even though the data is fine.
Commas inside merchant descriptions
Card descriptions frequently contain commas, and when the export does not quote those fields the row splits and every following column shifts on exactly the rows with such merchants.
Identifiers changed after a card reissue
A replacement card changes the account identifier inside the file. Software matching on that identifier treats it as a different account and either refuses or offers to create a new one.
How to fix it
- Drop the downloaded file into the fixer below — it identifies the real format regardless of the label Chase used and reports any structural defects.
- If the report shows shifted rows, they are the comma-in-description case; the exact line numbers are listed for a quick fix in a spreadsheet.
- For account mismatches, compare the identifier in the file against what your software stored, then reconnect the account rather than forcing the import.
- Where the format itself is wrong for your app, go back and choose the download variant named after the software you actually use.
Related import problems
Skip the manual edit — fix it automatically
The fixer reads the content rather than the file extension, so it tells you what Chase actually gave you. Free, no signup, no upload.
Open the fixer