Magic money tree?

[Wealdman]

Continuing my testing I imported a .mny file containing inter alia a current account with a balance of £76,384.64 - it's large having some 10,500 entries. I compared all the open accounts and the Maxim balances agreed with Money apart from a 2p discrepancy arising from 2 portfolio accounts (see my Lost Penny post).

I did not make any entries - the only thing that I did was to click the option to Hide Closed files.

I next saved the file and closed it, quitting the program. I then reopened MM and reloaded the saved .mmy file. All of the balances look to be unchanged other than the Current account which is now showing a balance of £636,135.61!!

[Campbell]

The MNY import is still very new so may still have a few niggles. Are you able to identify where the balance goes out? Does editing an early transaction resolve it? (it would trigger a balance recalculation from that transaction onwards)

[Wealdman]

I’ve think that I have solved the mystery. It is all down to entries in Static Data, Scheduled Transactions.

Looking at the MS Money file which was imported into Maxim Money, it has no Bills and Deposits showing that are outstanding, i.e, all instances have been recorded.

However, turning to Scheduled transactions in Maxim Money, for some reason it shows 8 instances of historical entries (all monthly). The first of these is dated 27 June 2013.
Having deleted the 8 spurious entries in Scheduled Transactions, saving the MM file, quitting and reloading all is well – the current balance accords exactly with MS Money’s balance and that of the bank itself!

[Campbell]

Ok, that's great news. MS Money stores the history of scheduled transactions in the main transactions table, and it's quite a job trying to work out which transactions are real, and which are metadata. If you are able to send a sample of anything that doesn't map in correctly I will tweak the import.

[Wealdman]

Although containing personal and private data I guess I can send you (privately) a copy of the screengrab showing the 8 items erroneously appearing in my Scheduled Transactions, but surely these are entirely personal to my particular dataset. I wonder therefore how this would assist in the tweaking the import process generally.

If you have something else in mind please let me know.

Incidentally, I assume that one should use the 'Contact us' option to send items privately.

[Campbell]

I was more wondering if it was possible to recreate the issue in a standalone example, based on what you have in your main data file. I suspect not though, as the issue is most likely around changes to the data over time. Don't worry about it if your data now all looks ok, I will hopefully further refine the import over time.

But yes, you can either PM me through the forum, or use the main support email address.

[Wealdman]

Just wondering whether the tweak should be for the import process to reject the writing to the list of Scheduled Transactions any items which have a Due Date earlier than the date the import is occurring. This would have caught my 8 spurious items.