“My Barclays download will not import”
Barclays offers CSV, QIF and OFX under labels that describe the software rather than the format, and each has a different failure. Most trouble comes from the date order rather than the data, which is why so many transactions look right and a handful do not.
Symptoms
Dates after the 12th of the month import wrong or are rejected The CSV loads as one column in US-built software A QIF download is refused outright by modern Quicken
What actually causes it
Day-first dates read as month-first
UK exports write 03/04/2026 meaning 3 April. American software reads it as 4 March. Days up to the 12th import silently wrong and days after are rejected, which is why the damage looks random until you notice the pattern.
Semicolon or tab delimiters
Some Barclays exports separate columns with something other than a comma. Importers expecting commas read each row as a single column and offer nothing to map.
A QIF chosen for an account type that no longer accepts it
Modern Quicken refuses QIF for bank and credit card accounts regardless of the file. A perfectly valid Barclays QIF is turned away on account-type grounds, not content.
How to fix it
- Drop the file into the fixer below: the delimiter, column alignment and date shapes are all reported, which identifies which of the three causes you have.
- Set the date format explicitly to day-first during import rather than accepting your computer's default.
- Let the fixer convert non-comma delimiters, then re-import the repaired file.
- If the file is a QIF headed for a bank account, download the CSV or OFX variant instead — that restriction is not something a file repair can lift.
Related import problems
Skip the manual edit — fix it automatically
The fixer reports what the date fields actually contain, which is how you tell day-first from month-first before the import rather than after. Free, no signup, no upload.
Open the fixer