[Kmymoney-devel] [Bug 283279] Quicken 2000 QIF investment file imports only one of many security transactions.

[John Blomfield]

https://bugs.kde.org/show_bug.cgi?id=283279





--- Comment #6 from John Blomfield <jabfield shaw ca>  2011-11-01 23:30:42 ---
On 01/11/11 14:57, allan wrote:
> https://bugs.kde.org/show_bug.cgi?id=283279
>
>
>
>
>
> --- Comment #5 from allan<agander93 gmail com>   2011-11-01 21:57:46 ---
> (In reply to comment #4)
>> Thank you for your help Allan.
>> I believe I have now SOLVED the problem with the Quicken 2000 QIF file!
>>
>> a) Quicken 2000 allows users to have Securities without a Ticker Symbol
>> which results in a short !Type:Security item and probably confuses the
>> KMyMoney file parser. The result is that all other !Type:Security are
>> replaced by the one with the short item in the Investment Account
>> Ledger, even though the securities are imported into the
>> Investment->Securities view list. This should be fixed in KMyMoney.
>>
>> b) Quicken 2000 has an investment category ReinvInt for reinvesting
>> interest in addition to a ReinvDiv for reinvesting Dividends. This makes
>> a difference in some tax regimes.   KMyMoney only has Reinvesting
>> Dividends so Reinvesting Interest needs to be added to KMyMoney.
>> KMyMoney currently skips all transactions containing ReinvInt categories.
>>
>> c) I fixed the above problems by adding a Ticker Symbols to offending
>> Securities and replacing ReinvInt with ReinvDiv in my QIF file.  This is
>> a tedious editing job and therefore the KMyMoney parser needs updating.
>>
>> John Blomfield
>>
> Part of the KMyMoney functionality is the possibility of updating prices
> online, for which a ticker symbol is essential.  For varying reasons, a user
> might use different descriptions for the same security, and being able to link
> them via a symbol helps considerably,  Also, different institutions sometimes
> use different names to describe the same security, even within the same file.
>
> For these reasons, and probably others, the current use of them in KMM is
> fundamental to its working, and is unlikely to change any time soon.  If online
> updating is not required, dummy symbols could be used, as long as they are
> unique.
>
> The QIF format is very broken, and attempting to import multiple
> investments in a file with no !Account lines and just one !Type:Invst
> is just not going to work.  Heavy editing is bound to be required.  It is not
> unusual for qif files to require some editing when setting up new accounts,
> because of the many variations in qif formats.
>
> So far as ReinvInt is concerned, that is probably more of a real issue
> and perhaps could be added at some stage.  Presumably, the requirement would be
> for them to be treated like ReinvDiv, but with a different
> description/category.
>
Thanks again for the info.  In fact I did not have any problems 
importing with just one !Type:Invst line.

I have posted a bunch of tips and some Python code for parsing QIF files 
on http://forum.kde.org/viewtopic.php?f=69&t=97494 that may be of 
interest.  As you can see once the files are edited using the Python 
scripts I supplied all the imports worked fine.

John

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.