Home → Switching to Moneydance →

Problems with Memo's on split transactions when a QIF file is imported

• Edit

jason

11 Aug, 2016 03:55 PM

Hello,
I am looking at switching to Moneydance after using the Australian version of Quicken for about 16 years - so I have a significant amount of data to deal with.
I have imported the first few accounts following the correct instructions, however what I have found is that if there is a "memo" in Quicken on a split transaction, when this is imported into Moneydance, the memo ends up as a "Category" in the split in Moneydance.
I have imported a lot of information, so now have the problem to deal with, is there any way to bulk change this as I quite simply cannot go through 16 years of splits and move all of the memos to the correct location.

I have attached a snip of what it looks like. In this particular instance "BPay" was a memo against one of teh split lines.

Many Thanks

• Memo_as_Category.JPG 32.3 KB

1. 1 Posted by dwg on 11 Aug, 2016 09:08 PM

   

   What dd you use to export the data from Quicken and create your QIF file, was it Quicken/Reckon itself or did you use Michael Young's Excel sheet?

   • Edit

2. 2 Posted by jason on 12 Aug, 2016 12:08 AM

   

   Hi dwg

   Yes, I did use that spreadsheet - perhaps there was a problem there.

   I have actually found a work around to the problem, which was:

   1) Purchased and installed a US version of Quicken onto a different computer
   2) Imported all of my AUS Quicken data into it (no problems encountered with this at all))
   3) Exported QIF files from US Quicken.
   4) Deleted all of the transactions that I had imported using Michael Young's Excel spreadsheet
   5) Imported the QIF that were generated by US Quicken.

   Now I just need to claim my refund from US Quicken under there Money Back Guarantee Policy.

   Whilst I have fixed this - with a bit of work(!), I am unsure what went wrong in the first instance.

   Thanks

   Jason

   • Edit

3. 3 Posted by dwg on 12 Aug, 2016 12:29 AM

   

   Hi Jason

   The problem is likely to have been created by Reckon.

   The export from Reckon is inconsistent in that if you have not used some fields Reckon moves the data into a different column, i.e. it does not leave a blank column when it should. I suspect that this is what might have happened in your case.

   Some time ago I posted in these forums a revised version of Michael's Spreadsheet (with his permission) that works around this problem in many cases.

   Des

   • Edit

4. jason closed this discussion on 21 Aug, 2016 07:57 AM.