Tried a bunch of them. Wow. This thing is a beast. It creates a lot of unwanted stuff by default. The SQLite export is what I wanted most, but it fails. The XML and JSON exports show a lot of SQL commands. Frankly, the QIF export is the most sane of the available formats. If I were you, I'd convert from that. QIF is simple and well documented: https://en.wikipedia.org/wiki/Quicken_Interchange_Format
On Sun, Jun 5, 2016 at 11:48 PM, Martin Blais <[email protected]> wrote: > Looks like many other formats are available, I'd try a few to find the > less lossy one. Likely CSV is not great (not hierarchical): > > > > Usage: skroogeconvert [Qt-options] [KDE-options] [options] > > A conversion tool for financial files (KMyMoney, GnuCash, Skrooge, ...) > > Generic options: > --help Show help about options > --help-qt Show Qt specific options > --help-kde Show KDE specific options > --help-all Show all options > --author Show author information > -v, --version Show version information > --license Show license information > -- End of options > > Options: > --in <file> Input file > --out <file> Output file > --param <name> Name of a parameter > --value <value> Value of a parameter > > Input supported formats: > > *.afb120 *.cfo *.csv *.uncompressed *.gnucash *.gnc *.gsb *.xhb *.kmy > *.mt940 *.mny *.mmb *.ofx *.qfx *.qif *.skg *.sqlite|All supported formats > *.afb120 *.cfo|AFB120 file (cfomb) > *.csv|CSV file > *.uncompressed *.gnucash *.gnc|GnuCash document > *.gsb|Grisbi file > *.xhb|Homebank document > *.kmy|KMyMoney document > *.mt940|MT940 file > *.mny|Microsoft Money document > *.mmb|Money Manager Ex document > *.ofx *.qfx|OFX file > *.qif|QIF file > *.skg|Skrooge document > *.sqlite|Sqlite document > > Output supported formats: > > *.csv *.json *.kmy *.qif *.skg *.sqlite *.xml|All supported formats > *.csv|CSV file > *.json|JSON file > *.kmy|KMyMoney document > *.qif|QIF file > *.skg|Skrooge document > *.sqlite|Sqlite document > *.xml|XML file > > > On Sun, Jun 5, 2016 at 11:47 PM, Martin Blais <[email protected]> wrote: > >> On Sun, Jun 5, 2016 at 10:55 AM, Matthias Beyer <[email protected]> >> wrote: >> >>> On 04-06-2016 16:01:38, Martin Blais wrote: >>> > I just installed skrooge and tried an export. >>> > It looks like single-entry accounting in a CSV file. >>> > Should be straightforward to convert. >>> > Let me know what doesn't work and I'm sure I could help. >>> > >>> >>> Wow, thanks for the support and sorry I didn't answer in time, I'm >>> currently >>> suffering from a cold. >>> >>> So here's some sample data, including the CSV header (see attachement). >>> >>> Note: as said, I track my money really precisely, so, as you can see >>> from the >>> sample data, I track every drink I have and so on. >>> >>> The first four lines are the "open" lines. "Konto4" is my Cash in this >>> case >>> here. >>> >>> I tried to script the import several times, grouping by date and >>> account, but I >>> failed most of the time because of several points. >> >> >> Here are some observations on the data you attached: >> >> - It looks to me like the "id" field may be a unique key for each line >> (posting) and like the "idtransaction" field refers to those. If this is >> true, this is how you should group your postings: by unique value of >> "idtransaction". >> >> - If this is right, the field you provided is a subset of the entire >> thing. If not, then it's probably a single-entry system and you have to >> figure out how to group the postings some other way. >> >> Q. Does the "number" field ever have a non-zero value? >> Q. Do you have any idea what the "idgroup" field may be for? >> >> >> One I can think of right now is: When doing a transaction from one >>> account to >>> another, this is done with two transactions in skrooge (you can type the >>> things >>> one time, but it will create two transactions): You can see this in line >>> 5 and 6 >>> (with comments "Moved"). You can also easily see that lines 7-9 do not >>> balance >>> properly. I don't know why this is. >>> >> >> Hmm. It isn't clear indeed. >> The best way to debug this IMO would be to manually create a sample input >> file and see how the export translates those. >> >> Is there another export format? >> >> >> >> >> >> >>> Other problems were non-balancing transactions. >>> >>> I tried to convert like this: >>> >>> 1. Group the transactions from skrooge by >>> 1. Date >>> 2. Account >>> 2. For each transaction >>> 1. generate the account name ( {Income, Expenses}:<category, >>> transformed to colon-syntax of beancount>) >>> 2. Make accounts unique >>> 3. open the accounts >>> 4. generate the transaction from {Income, Expenses}:<category> to >>> <account> >>> >>> I ended up with the problems listed above. >>> >>> -- >>> Mit freundlichen Grüßen, >>> Kind regards, >>> Matthias Beyer >>> >>> Proudly sent with mutt. >>> Happily signed with gnupg. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Beancount" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beancount/20160605145512.GA12724%40lucy >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhO-nOBCtWJJ%3D1VUwHdRQX6Qsqgx-fcDMgrPmXo5Bzv3pA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
