Since a recent update, i cannot import an .ofx file from my bank as i have a message HTTP 500 internal error…
I have tried with an older file (that have been already imported) but have the same problem…
I have made no change (only updated manager) since last successfull import…
I have tried to come back to an older version (17.11.22) that was working to import .ofx file, but it is not possible to install as the database was already updated with last version…
I don’t know if this is related, but another user had an issue with .ofx imports not matching number formats. A recent change to the program (v17.12.12) addressed this. Are the number formats in your export the same as your number format preference in Manager? As I understand things, the program now assumes that they are. If they are not, perhaps that causes problems.
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt)
at ManagerServer.HttpHandlers.Businesses.Business.BankTransactions.ImportBankStatementForm.ParseBankStatementLines(String fileName, Byte buffer)
at ManagerServer.HttpHandlers.Businesses.Business.BankTransactions.ImportBankStatementForm.Post()
at HttpFramework.HttpApplication.ProcessRequest(HttpRequest request, HttpResponse response)
at ManagerServer.HttpApplication.ProcessRequest(HttpRequest request, HttpResponse response)
I am not sure how Manager interprets different date formats, or whether .ofx format allows different date formats. But as of a recent fix, Manager assumes the .ofx numbers are in the same format as your preference. So you will need to either (a) temporarily choose a matching number format or (b) edit the statement file wit a text editor to substitute a period for the comma as your date separator. I confess I do not know how Manager treats the absence of spaces as thousands separators. Probably it ignores them.
None of the choices we have in preferences matches the one generated by the bank.
the best would be to have an option with comma or dot without any thousands separators.
Did you try importing with the format highlighted in this illustration?
Another option is to try importing the .ofx file into a spreadsheet, then define the column with amounts as a number format. You can select a number format available in Manager or define a custom format. Finally, convert back to a text file format and paste the result into your .ofx file.
It worked, but I don’t want to work in a foreign number format nor want to change umber format each time I need to import a bank statement. This is a feature that was working before.