Thanks for reporting, will investigate

This was investigated and nothing wrong was found.

Can you please attach the CSV and describe how you mapped the columns?

There's something very weird going on with csv downloads from this particular bank and the converter: I've uploaded two csv files: on is direct from the bank, the other has been edited in Excel to remove the oldest three transactions and saved again as a csv. I notice that the edited csv has had the quotes removed from around each field data, but that seems not to matter to your converter.

I deleted the old mapping I had for this bank and tried to set up a new mapping in the converter. The first weird thing is that I want to set the very first field/column (transaction date) to General -> Date DD/MM/YYYY, but it won't let me: the date formats are greyed-out (mappings2.png) and will only accept NUM format. And it doesn't matter whether I'm trying to convert the original downloaded csv or the edited one. Yet, when I try to convert csv files from other banks, I have no problem setting date formats for them (they are auto-recognised), regardless if their csvs have each field within double quotes or not.

Finally, I just discovered that, if I select an alternative bank's mapping for these two files, the converter immediately recognises the data format, and if I switch back to the correct saved mapping for these files, the correctly- recognised date column remains identified as Date DD/MM/YYYY. This now converts as expected. Very wierd.

The only downloaded csv files that are affected in this way come from Lloyds bank (credit card) in the UK. All other banks' downloaded csv are ok.

With these specific csv files, both the automapper and my predefined mapping for these csv files (which used to work fine until your new conversion webapp was launched). Both of these show column 1 as being numeric, rather than date, even after I apply the Lloyds bank mapping - which I re-created as a test to see if that would make any difference (see attached screenshots - if I can find a means of attaching them). If I now run the conversion, the qif file comes out as per my original post with the header line treated as a transaction, and all the transaction dates preceded by "N" instead of "D".

HOWEVER... I just discovered that, if I download, import; set the mapping to Lloyds, then change it to any other mapping I have, column 1 is then correctly recognised as a date field. I can then switch back to the Lloyds mapping and it remains correct - i.e. recognised as a date field.

I've tried importing the downloaded csv's into both MS Excel and Libre Office Calc, making a few changes (like deleting a few transactions), saving, then importing into the converter: column 1 is still incorrectly recognised as a numeric field. So it seems not to be a problem with the downloaded csv files?

I can see that you attached screenshots and sample csv files.

I tried both CSV's and both automatically mapped like this, which seems correct.

The fact that the date fields are grayed-out on the 'Transaction Date' is because the Date DD/MM/YYYY is already mapped on the 'Transaction cleared date'. And 'Num' is incorrectly mapped.
 

So here are the steps to fix this:

1 - Select 'Ignore' for the second column

2 - Select Date DD/MM/YYYY for first column

3 - Convert the file

4 - Save mapping

5 - Delete old mapping