![]() Registered Member ![]()
|
Hi,
I like the multiple processing options skrooge offers, but I also like a double-entry book-keeping system. So my idea was to use kmymoney, and if I need to do some mass customization, export to skrooge, do processing, and reexport back to kmymoney. However, my question is will skrooge not destroy the transaction information present in kmm? As kmm is double entry, it works using balanced transactions, and they are tied together in the database. If I import the kmm file to skrooge, will this information not be lost? How will skrooge then be able to export to a kmm file if the transaction info is missing? Thanks! |
![]() Moderator ![]()
|
Skrooge is able to import/export directly in KMyMoney format (.kmy) without loosing information.
If it doesn't work as expected, this is a bug. |
![]() Registered Member ![]()
|
Hi,
that sounds great! So I understand this better, could you explain how the transaction information is preserved? Also, is it possible to look at a skrooge file using a sqlite viewer? I tried, but there was an error... |
![]() Moderator ![]()
|
In KMyMoney, with the double-entry, all transactions are from one account to an other one. In Skrooge, we have accounts and categories, so in fact, KMyMoney accounts are mapped with Skrooge accounts and categories.
Yes, you just have to export your document in .sqlite format, then you can open the exported document with sqlite. |
![]() Registered Member ![]()
|
I tried exporting, but I get:
"[ERR-5]: Export of 'xxxx/kmm/test' failed [ERR-1]: This export mode is not yet implemented" (I'm under windows, skrooge version seems 1.2.0). Regarding double entry: so you, too, keep every transaction twice: once under the relevant account, and once under the category? so there are 2 records like there are in kmm (there they are called splits)? In that case, I don't see what Skrooge is missing to be a double-entry system? Thanks! |
![]() Moderator ![]()
|
Don't forget to export with a recognized format. (see the list in the combo box) In you case, the output file name must have the extension .sqlite.
In Skrooge a category is not MANDATORY for a transaction.
|
![]() Registered Member ![]()
|
Thank you, the correct file extension was what I missed.
I think I now better understand the data model, and how it maps to kmm (transfers between accounts in kmm will be represented as grouped transactions in skg, while transfers to categories will be represented by suboperations, depending on how many splits there are). One question: in kmm, the memo field for each side of a transfer between accounts can differ. In skrooge, this can happen as well on import, but if I change the comment field in one of the grouped operations, the the others will change as well. Is this intended? |
Registered users: Bing [Bot], claydoh, Evergrowing, Google [Bot], rblackwell