Some issues importing CSV statements

[sgp]

I am having trouble importing bank statements from Coop bank. There is only an option to save as text. I can amend to csv format but get the error:
There was an error processing your file
The CSV file appears to be corrupt.
Error: The CSV appears to be corrupt near record ‘25’ field '1 at position ‘0’. Current raw data : ‘’.

I did it several months ago and uploaded succesfully

thx
Rob

[sean]

I have the same issue with HSBC - I think there may be an issue on the Quickfile side as I have imported many statements before without a hitch!

There was an error processing your file
The CSV file appears to be corrupt.
Error: The CSV appears to be corrupt near record ‘11’ field '1 at position ‘0’. Current raw data : ‘’.

[Glenn]

We upgraded our CSV parser a couple of weeks ago as the older parser we were using will run into compatibility issues when we upgrade our servers in August.

If you can I would recommend always exporting as QIF (MS Money) or OFX (I know for sure HSBC allows for QIF downloads). The new parser is very strict on formatting and most of these problems are due to the way certain applications handle blank columns/rows in CSV files.

We will be looking at these cases now.

EDIT 1:

I can confirm that HSBC is a problem too. In the case of HSBC I opened the file in a notepad and there’s an extra carriage return at the end. Removing the trailing carriage return in Notepad fixed the problem. Obviously we’ll update our code to do this for you. COOP may be related to the same issue but haven’t had a chance to check as yet, @sgp maybe you have some blank rows at the end that’s causing this? I will take a look shortly.

EDIT 2:

We’ve now patched and tested HSBC, Lloyds, Nationwide and COOP. This should go live in the next 1-2 hours.

EDIT 3:

Live

[sean]

Thanks Glenn - greatly appreciated!

[sgp]

Hi Glenn
Thanks, I removed CR at end of CSV file & it worked
Rob

[ntlworld]

I have had the same problem with Barclays

[Glenn]

@ntlworld that shouldn’t be a problem any longer with Barclays, we made some updates last week and tested with a bunch of different Barclays statements. If that problem persists let me know!