On 19/07/14 01:49, geo...@wildturkeyranch.net wrote:
https://bugs.kde.org/show_bug.cgi?id=337251
--- Comment #17 from geo...@wildturkeyranch.net ---
(In reply to allan from comment #16)
On 17/07/14 19:21, Cristian Oneț wrote:
https://bugs.kde.org/show_bug.cgi?id=337251
--- Comment #15 from Cristian Oneț <onet.crist...@gmail.com> ---
Indeed if the 'Buy' is replaced with a 'BuyX' in the attached Qif file the
brokerage account is created as expected and the transaction does not need to
be touched. Does this mean that the application works as expected and this can
be closed?
I think it best to wait a bit for any comment from the poster.
I there a specification for investments in the QIF format somewhere?
Not specifically for investments, just as part of the overall
description. I think perhaps
http://en.wikipedia.org/wiki/Quicken_Interchange_Format is most useful
as it has a number of hints, links and references. One of these is useful -
http://web.archive.org/web/20100222214101/http://web.intuit.com/support/
quicken/docs/d_qif.html
.
Allan
This seems strange. BUY would be what Quicken puts out from a combined account
(i.e. security/brokerage in one account). I is my impression that the "X"
suffix ishttp://www.respmech.com/mym2qifw/qif_new.htm used if the security is
paid for from another (Quicken) account. In my full QIF dump of 7 or 8
security accounts I only see BUYX in the Prices data.
I have several Quicken files which contain BuyX lines, but generally I
used defined transfer accounts
Here is a reference to BUYX: http://www.respmech.com/mym2qifw/qif_new.htm
This does not exist.
That said, the issue I submitted this bug report for was what was happening
when I imported a Quicken QIF and found "missing cat" errors on all the
security transactions. And then when I tried to fix it, the edit routine
produced the Brokerage account as a default, which should have allowed me to
just push the "Enter" button, but it was greyed out.
Even this is a lot of work given that we are "traders" and have a LOT of
transactions to process.
Given all this, I have written a script to pre-process the QIF. Should I be
replacing all the BUYs with BUYX??
Given that QIF is (in my opinion) the best way to move to a new accounting
program and that KMM does not handle all actions I think it would be nice if
the KMM project posted the QIF spec it is implementing.
KMM's QIF processing started life some years before I came on the scene,
and I have no KMM spec, but where necessary I've tried to follow Quicken
documentation, augmented where that is too loose.
I think the point in question refers particularly to transfers. In
general, these are defined by 'L' lines defining the account to use. If
there is no 'L' line, or it is empty, then BuyX is taken as indicating a
transfer and an existing brokerage account is used, or one is created.
If there is neither an 'L' line nor an 'X' activity suffix, KMM does not
know which account to use so leaves the account field empty. The
imported transaction is flagged as missing a category assignment. Then,
all that is necessary is for the user to select the appropriate account.
Here, I don't see "...the edit routine
produced the Brokerage account as a default, which should have allowed me to
just push the "Enter" button, but it was greyed out." I'm using the
development branch. The enter button gets enabled as soon as an account is selected.
Allan
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
