Match payees/memos to Gnucash accounts ignored during QIF import

[Johann Rohwer]

Charles Day wrote:
> On Tue, Mar 4, 2008 at 2:58 PM, Johann Rohwer <j.m.rohwer at gmail.com 
> <mailto:j.m.rohwer at gmail.com>> wrote:
>     I've been using Gnucash effectively for years to do my personal finance.
>     However, when I recently upgraded to version 2.2.1 it turned out that
>     when importing QIF files from my online banking, the actions in the
>     druid step "Match payees/memos to Gnucash accounts" are ignored and all
>     the imported transactions are linked to the "Unspecified" expense
>     account after import. Of course I can still edit them in place one by
>     one, but this is very inconvenient since the druid remembers the correct
>     matches for frequently occurring transactions. Is this a known
>     issue/bug?
> 
> 
> Could you provide a sample transaction from your QIF file for which the 
> payee/memo mappings are being ignored? 

Attached below. I should add that it happens for every transaction in 
the QIF file I get from my online banking. So it does not appear to be 
transaction specific.

> Two theories off the top of my head:
> 1. Does your QIF contains some lines that only contain an "L"?

It doesn't seem so.

> 2. Does this only happen to investment transactions?

No I don't think so. I only use gnucash to keep track of my personal 
finances and bank accounts (checking a/c, credit cards, loans); I don't 
have any stocks or investments registered.

I should add that I recently set up accounts in different currencies 
(since I have acquired checking accounts in different currencies) and 
then upgraded to the latest gnucash release because it allows you to 
specify the currency during the QIF import. I'm not sure whether these 
issues might be related though.

---------------- 8-< ------sample qif file -----------
!Type:Bank

D05/03/2008
T-900.00
N0
MACB DEBIT:EXTERNAL PPS
^
---------------- 8-< ------end sample qif file -----------

I match this to Expenses:Insurance during the import druid, but it 
nevertheless ends up in "Unspecified". Same for all other txns.

Thanks
Johann