I am opening this issue because YNAB's native file importer completely rejects standard Discover Card CSV files, throwing the error: "We couldn't find any transactions in the file." Even though the raw Discover file is fully populated with transactions when opened in a text editor, YNAB fails to read it.
To bypass this, I tried using your community parser tool.
Steps to Reproduce:
- Drag and drop the original, unedited Discover Card CSV file into your parser tool.
- The tool's UI successfully reads the file, parses the data, and shows the correct transaction layout in the web preview screen.
- Click the "Save YNAB Data" button to export the converted file.
Actual Result:
The browser downloads the file, but the file is completely empty (221 bytes / contains absolutely no data). If I try to upload this converted file to YNAB, it naturally throws the exact same "Zero Transactions" error because the file is entirely blank, except for the headers (date, payee, memo, outflow, inflow)
The original file contains standard data.
I am opening this issue because YNAB's native file importer completely rejects standard Discover Card CSV files, throwing the error: "We couldn't find any transactions in the file." Even though the raw Discover file is fully populated with transactions when opened in a text editor, YNAB fails to read it.
To bypass this, I tried using your community parser tool.
Steps to Reproduce:
Actual Result:
The browser downloads the file, but the file is completely empty (221 bytes / contains absolutely no data). If I try to upload this converted file to YNAB, it naturally throws the exact same "Zero Transactions" error because the file is entirely blank, except for the headers (date, payee, memo, outflow, inflow)
The original file contains standard data.