Nationwide to remove support for Microsoft money

Ron-ski

Logged on today to find I've been switched over to the new site as well, first impressions was 'oh what a mess!' Wife doesn't like it either.

Anyway I've had a quick look at Nationwides OFX file in notepad and its very different from the ones I download from Tesco's (which work). I've sent Nationwide a message, no doubt I'll get a useless answer.

mattgod69

techno79 wrote: »

Thank you, that's absolutely magic. I set all the numbers in Money to just the 8 digit account number and same in the script as well. All sorted now.

I really appreciate your efforts in updating the script and the help in getting it working. Finally I can get back into a routine for my finances.

Big boo to Nationwide for causing so much hassle to their customers!

I had to do the same as this otherwise i got errors. eg, for my flexaccount, i had 4 nos and a slash and then some more numbers, but just changing it to the 8 numbers caused it to import ok.

Many thanks to all on this forum...... especially rpb424.... what a star!

rpb424

joeatiyah wrote: »

Credit card still asks for account on import, but it always did for me (I think Colin gave advice as to how to avoid that, but I never bothered - its no big deal).

I think I've figured out why this is.

If you create a brand new account and assign the correct number to it then Money will not ask you which account to use when importing. However for some reason if you amend the number in an existing account (say when you get a replacement card with a new number) then Money always asks from that point on, even if the number exactly matches that in the OFX file. Seems like a bug in Money to me.

You can get round this by creating a new account with the correct number, exporting the old account as a QIF file, re-importing it into the new one and then deleting the old account. I tried this today and it works.

techno79

I sent Nationwide an email to explain their OFX file format is not conforming to the OFX standard and is causing import issues in other software (I didn't explicitly mention Microsoft Money). Does anyone know exactly what part of the OFX file is deviating from the OFX standard? I can then follow up with Nationwide with that exact information so hopefully this'll filter down to the necessary people who can correct it. TIA.

rpb424

There are various OFX versions, and the options in mt2ofx allow you to create many of them. If you compare a downloaded OFX from Nationwide that will not import with one converted by mt2ofx that will import then there are some marked differences.

The problem would appear to be that Money only seems to support version 102 OFX files, but the Nationwide ones are produced to version 203. If I edit the mt2ofx options to produce a version 203 from the csv file instead then the resultant OFX file it generates looks substantially similar to a Nationwide one as you would expect, but Money will not import it.

I only have Nationwide accounts, so I don't know what OFX versions other banks are producing. Also, I am using Money 2001, so I also don't know whether or not later versions might support other OFX versions.

Ron-ski

I've sent Nantiowide a couple emails concerning this problem, they confirmed today that they are having problems and are looking into it.

I apologise if the previous message was not clear. I confirm we are experiencing a temporary Internet Bank fault with OFX downloads and not PDF statements. This is something we are currently looking into.

I also have a Tesco's account and their OFX files import OK, but appear to V102

OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:NONE
<OFX>
<SIGNONMSGSRSV1>
<SONRS>
<STATUS>
<CODE>0
<SEVERITY>INFO
</STATUS>
<DTSERVER>20111118203110.609[0:GMT]
<LANGUAGE>ENG
<DTACCTUP>20111118203110.609[0:GMT]
</SONRS>
</SIGNONMSGSRSV1>
<CREDITCARDMSGSRSV1>
<CCSTMTTRNRS>
<TRNUID>0
<STATUS>
<CODE>0
<SEVERITY>INFO
</STATUS>
<CCSTMTRS>
<CURDEF>GBP
<CCACCTFROM>

rpb424

Good that you got an admission of a fault on their part.

I'd imagine that the vast majority of financial institutions use version 102. Given that Nationwide have taken this many years to implement OFX at all then I'd guess that, having no experience in this, they didn't specify OFX correctly to whoever was responsible for implementing it, and they have ended up wrongly with version 203 as a result.

techno79

rpb424 wrote: »

There are various OFX versions, and the options in mt2ofx allow you to create many of them. If you compare a downloaded OFX from Nationwide that will not import with one converted by mt2ofx that will import then there are some marked differences.

The problem would appear to be that Money only seems to support version 102 OFX files, but the Nationwide ones are produced to version 203. If I edit the mt2ofx options to produce a version 203 from the csv file instead then the resultant OFX file it generates looks substantially similar to a Nationwide one as you would expect, but Money will not import it.

I only have Nationwide accounts, so I don't know what OFX versions other banks are producing. Also, I am using Money 2001, so I also don't know whether or not later versions might support other OFX versions.

I see. Thanks for the reply and explanation as that makes perfect sense. Following Ron-Ski's post, hopefully Nationwide will change over to version 102 or something else that works with Money straight off. In the mean time, MT2OFX and your scripts are doing the job so thank you for your efforts.

P.S. I'm using Money 2005 (UK edition) and that doesn't work in the same way so I don't think it changes for later versions of Money.

callum9999

Does anyone know if changing to "version 102" is a tricky thing to do? I assume it accesses all the same information as the one nationwide has, just formats it differently. In my head that translates to a software engineer messing around with the system for 30 minutes and fixing it but I'm sure that's pretty wide of the mark!

rpb424

Perhaps they're just using mt2ofx like us to convert their csv files and have got the output format set wrong in the options.