[Kmymoney] OFX import not using default brokerage account for 'Dividend'

[Allan]

On 15/04/14 00:20, Jack wrote:
> On 2014.04.14 17:48, Allan wrote:
>> On 14/04/14 22:32, Jack wrote:
>>> On 2014.04.14 16:00, Bob Ewart wrote:
>>>> I have a similar problem to Timothy when importing dividends from
>>>> Merrill Lynch via ofx.
>>>>
>>>> I'm using Kmymoney 4.6.4 and have two accounts "Merrill-Lynch" and
>>>> "Merrill-Lynch (Brokerage)" among others.
>>>>
>>>> When I import the .ofx file, the cash (from other than dividends) goes
>>>> into Merrill-Lynch (Brokerage) as expected.  The dividends all show up
>>>> in Merrill-Lynch flagged with $0.00 value and no account showing below.
>>>>
>>>> Click on one to edit it and the account shows up as Merrill-Lynch
>>>> (Brokerage) with a value showing, but the  Enter button is grayed out.
>>>>
>>>> Click on the account and start retyping it.  Merrill-Lynch (Brokerage)
>>>> is selected.  Now the Enter button is active.
>>>>
>>>> Click on Enter and the amount then goes into the Merrill-Lynch
>>>> (Brokerage) account.
>>>>
>>>> Bob
>>>
>>> I've been fighting to do useful imports from Merrill Lynch for some
>>> time.  I seem to recall I also tripped up on this exact issue the last
>>> time I tried to to an OFX direct connect.  I have a very vague
>>> recollection that I did send something to the list about it - but I'll
>>> have to check my notes and the list archives.  I think I did find an
>>> easier way to enable the enter button (a few clicks, no typing) but I'll
>>> have to see if I can jog my memory, since I can't remember now what I
>>> actually ended up doing.
>>>
>>> Jack
>>
>> Was it this? -
>> "I'm continuing to try to update my Merrill Lynch investment accounts
>> with ofx direct connect, and I just noticed two more strange things.
>>
>> First, an imported buy shares transaction does not include a brokerage
>> account.  This is not a surprise, since it is probably not explicitly
>> included in the OFX transaction.  The imported transaction is thus
>> highlighted and shows the error triangle.  If I click "Accept" the
>> highlighting goes away, but nothing else happens.  However, if I
>> "Edit" the transaction (with or without accepting it first) the
>> brokerage account associated with the investment account is filled
>> in.  [As far as I can tell, this ONLY happens if the name of the
>> brokerage account is exactly the same name as the investment account,
>> but with " (Brokerage)" appended.  Is there any reason it doesn't use
>> the associated account no matter what the name?]  So far, so good.
>> However, "Enter" is still grayed out.  Only if I manually change the
>> status from not marked to cleared can I "Enter" the transaction.  So -
>> just by editing the transaction, it will fill in the default brokerage
>> account - but it does not do this as part of importing the
>> transaction.  Is this by design, or just an oversight, and should I
>> open an enhancement request to change the behavior?
>>
>> Second, while deleting some unused Payees, I noticed that all the buy,
>> sell, and dividend transactions that had been imported from OFX had
>> created payees such as "Purchase: AFLAC INC            COM PRICE SHOWN
>> IS AVERAGE PRICE."  For the ones starting with "Dividend: ..." no
>> transactions are shown in the transaction list on the payee view, but
>> trying to delete it throws an error that it is still referenced in a
>> transaction.  For the Purchase and Sale payees, they do list the
>> relevant transactions, but displaying any of those transactions in the
>> investment account ledger does not show a payee field.  I am assuming
>> that the payee is created as a side effect of the OFX import, even
>> though Payee is not a field normally used in investment transactions.
>> Again - should I open a bug for this, or is it expected behavior? "
>>
>> See two new OFX investment import oddities - 29 March.
>>
> Yes, that's the one.  No wonder I didn't see it immediately - I was
> looking in the other mailing list.  However, you do see that changing
> the status from not marked to cleared allowed the "Enter."  However, I'm
> not sure it helps any with figuring out what's going on.
>
> Jack

I won't see it Jack as I don't get this problem.

Have you tried Git HEAD since December?

Allan