MMEX Discussion Forum

I have about 4 years of full records and another 3 years of sparse records from Gnucash, and I've been trying to import them properly into MMEX.

My data is all in English, and because Gnucash is double-entry, is all a set of transfers. That can be mapped fairly easily to categories in some cases, but for transfers between accounts rather than externally (for example, withdrawing cash from my savings account) it seems a bit of a hassle to import.

Also, my accounting methods mean I've used split transfers fairly liberally. For example, if I pay for a meal using a credit card and my colleagues pass me their portions in cash (or vice-versa), that's a split transaction, and there's more of those than I'd care to admit.

What's the most painless way to import?

So far what I've seen is that CSV (which I can export to from Gnucash losslessly, verified by my own sampled testing) does not support either split transfers or transfers between accounts.

Does QIF support both or either? Because I don't have a direct Gnucash QIF export, just a convertor someone wrote half a decade ago, and don't grok the format. I'll write my own simple convertor if I have to, but would need to know whether it supports both splits and transfers.

For reference, if it matters, I'm using 1.2.2 on Linux. I have no qualms going to a developmental version if needed.

QIF import is support transfers.

Nikolay wrote:QIF import is support transfers.

Thanks Nikolay. Does it also support splits? I found old threads which said prior to 1.1.1 it worked fine.

To be clear, I was referring to this report:-

 http://forum.moneymanagerex.org/viewtop ... f=5&t=5661



Also to this feature request:-


http://sourceforge.net/p/moneymanagerex ... uests/128/

Either of them would be fine for my purposes. As the QIF import currently which I do seems to preserve transfers but absolutely mess up splits, I may have to manually modify my source data. However as I'm using a third party convertor just to get to QIF, I'd rather use CSV, if it were not for the fact that it can only import to one account, not to multiple accounts.

Ideally the CSV importer would have:-
a) The ability to specify account as well (so we can have a gigantic CSV with all accounts listed inside)
b) A 'Type' category which will specify whether this particular entry is a transfer, as well as a 'target' or whatever category for the account name it needs to be connected to.

Sorry I can't see how it supports splits? I exported data from MS Money and each QIF is just one account. So it has no knowledge of the other accounts.

I asked Artificial Intelligence how to import from GnuCash into MMEX. Unfortunately the answer incorrectly says that you can export GnuCash files using the QIF format. That option does not exist, so I'm trying the CSV method. I'll update this post or add more posts to document how the process works for me.

I've used GnuCash for several years and become progressively more frustrated with it. For simple personal finance, it creates extra work (mainly because of double entry), and the user interface continues to be a pain in the ass. It is not only unattractive, it makes it difficult to see and enter data. The "Description" column is excessively wide and refuses to stay shorter; this makes other columns difficult to see. It is also unnecessarily difficult to use splits. And on top of those issues, now I'm having trouble switching to MMEX because QIF isn't supported.

You have added your comments to an ancient post from 2015; it would probably have been better to start a new thread.

Oh yes, AI usually searches through 10 pieces of information stored in its memory and presents the best result from an AI perspective. Depending on how well the AI engine is trained, the result is good, bad, or useless. Information on the internet is cobbled together to form information that makes neither head nor tail.
That's how I see things at the moment, but perhaps things will improve over time.