Nationwide to remove support for Microsoft money

NerdyN

Marc_C wrote: »

rpb424,


BTW, if anyone would like a copy of MS Money 2005 build 1105 say so here and I will upload a copy to Dropbox.

Hi,

Could I please ask you to do this. I would be extremely grateful for my v2002 seems unable to cope!

Many thanks!

NN

Marc_C

My Pleasure!

Here are some notes I wrote some time ago...........

1. MS Money 2005 UK will convert any money files it finds to the 2005 format and any previous version of Money will be unable to work with converted files. My advice is to copy all current Money files and put them in a safe place!
2 Identify your current Money programme and put it in a safe place.
3. Download the file from Dropbox: http://db.tt/0mzSpbyU It is an ISO file and will need to be burnt onto a cd. Image Burn is a good free burner http://www.imgburn.com/
4. On installation, version 2005 will ask you if you want to keep the previous version of Money. It might be prudent to say “yes” just in case of any problems. At least you will be able to continue using the old files you put in that safe place if the worst comes to the worst!

NerdyN

Marc_C wrote: »

My Pleasure!

Here are some notes I wrote some time ago...........

Thank you very much, Marc,

I really appreciate it, plus your excellent guidance!

Cheers,

NN

AlanSinfield

I have just tried Nationwide OFX format on a Flex Account and an Investdirect account and it imported. The investdirect import seems to have a problem with the transaction description in that it is blank

I will do further tests and report back

coberley

Since Nationwide stopped supporting Microsoft Money (without any notification), I have been using Nationwide OLB in conjunction with " Ace Money" ( a superb program) and "Nationwide OFX Converter" from iCreateOFX for the last two years very successfully. Nationwide then changed the OLB interface and this caused several problems due to a change in the CSV and OFX formats without notifying their OLB customers.

Philip Katete from iCreateOFX was extremely helpful and responsive and made the relevant changes to the Nationwide OFX Converter Program within a few days. All works fine now. However, you do have to convert the CSV file to an OFX file as neither the Nationwide OFX or CSV files will import directly to Ace Money.

I should also mention that contacting Nationwide about the problem they were most unhelpful but after several e-mails did eventually put their hands up and confirmed that they had made changes to the format of the OFX and CSV file structure!

callum9999

The OFX file just imported into Money for me as well. I did it twice with overlapping dates and it seemed to duplicate a load of things but that could just have been a one-off error of my doing or Money's fault.

jonfarmer

AlanSinfield wrote: »

I have just tried Nationwide OFX format on a Flex Account and an Investdirect account and it imported. The investdirect import seems to have a problem with the transaction description in that it is blank

I will do further tests and report back

Following Alan's message I have also had another try at using the NW OFX format, and it imported directly and correctly into Money 2005. I'm not sure what has changed, since a quick look at the OFX file itself seems to show it is still using OFX version 203. But if you have had problems with the NW OFX import in the past and therefore switched to using the CSV file with a converter, it might be worth doing a further trial of the OFX file itself again now.

jonfarmer

callum9999 wrote: »

The OFX file just imported into Money for me as well. I did it twice with overlapping dates and it seemed to duplicate a load of things but that could just have been a one-off error of my doing or Money's fault.

Unfortunately, Callum9999 is right. The reason is set out below:
Nationwide has at last provided the OFX download service that customers have been requesting. BUT their incompetent programmers have not realised that within the OFX format they are required to provide a unique Financial Transaction ID which is STABLE.

If the FITID is NOT stable then when the customer completes a download of the recent transactions the next day, the same transaction is given a different FITID and as a result the financial management software then imports the same transaction AGAIN. So each day, the system creates a whole raft of DUPLICATE transactions. Aaagh!

As an illustration, here are two Nationwide OFX records relating to the SAME transaction, one downloaded on the 17th and one on the 18th December. These should both have had the SAME unique FITID, but one has an FITID of 6313122011120000 and the other 6013122011120000:

17th December:
<STMTTRN><TRNTYPE>POS</TRNTYPE><DTPOSTED>20111213120000.000[+0]</DTPOSTED><TRNAMT>-394.80</TRNAMT><FITID>6313122011120000</FITID><NAME>Bowsports WOLVERHAMPTON.</NAME></STMTTRN>

18th December:
<STMTTRN><TRNTYPE>POS</TRNTYPE><DTPOSTED>20111213120000.000[+0]</DTPOSTED><TRNAMT>-394.80</TRNAMT><FITID>6013122011120000</FITID><NAME>Bowsports WOLVERHAMPTON.</NAME></STMTTRN>

So this and all the other transactions get imported as duplicates each day. Nationwide needs to correct this basic programming error URGENTLY

techno79

jonfarmer wrote: »

Unfortunately, Callum9999 is right. The reason is set out below:
Nationwide has at last provided the OFX download service that customers have been requesting. BUT their incompetent programmers have not realised that within the OFX format they are required to provide a unique Financial Transaction ID which is STABLE.

If the FITID is NOT stable then when the customer completes a download of the recent transactions the next day, the same transaction is given a different FITID and as a result the financial management software then imports the same transaction AGAIN. So each day, the system creates a whole raft of DUPLICATE transactions. Aaagh!

As an illustration, here are two Nationwide OFX records relating to the SAME transaction, one downloaded on the 17th and one on the 18th December. These should both have had the SAME unique FITID, but one has an FITID of 6313122011120000 and the other 6013122011120000:

17th December:
<STMTTRN><TRNTYPE>POS</TRNTYPE><DTPOSTED>20111213120000.000[+0]</DTPOSTED><TRNAMT>-394.80</TRNAMT><FITID>6313122011120000</FITID><NAME>Bowsports WOLVERHAMPTON.</NAME></STMTTRN>

18th December:
<STMTTRN><TRNTYPE>POS</TRNTYPE><DTPOSTED>20111213120000.000[+0]</DTPOSTED><TRNAMT>-394.80</TRNAMT><FITID>6013122011120000</FITID><NAME>Bowsports WOLVERHAMPTON.</NAME></STMTTRN>

So this and all the other transactions get imported as duplicates each day. Nationwide needs to correct this basic programming error URGENTLY

You should send a message to Nationwide informing of this. May fob you off with some BS reply but hopefully, they'll also forward the message internally to the relevant team who may actually resolve the issue. In the mean time, maybe the best work around is to use a custom date range for showing only those transactions in Nationwide online banking that need to be downloaded? This is what I do by default.

AlanSinfield

I sent Nationwide a message and their response is as follows: At least the are aware of problems

Dear Alan,
Thank you for your message.
I would like to thank you for sharing this information with us. I have read through the information and notice that you mention you attempted to import your Invest Direct transactions and this came through blank. We are aware of a known issue regarding this and our Technology are working on a resolution. I apologise for any inconvenience caused regarding this.
Regards,