dealing with invoices and QIF imports

Derek Atkins warlord at MIT.EDU
Wed May 28 12:46:29 EDT 2008


Quoting Charles Day <cedayiv at gmail.com>:

> Well no one is telling the importer that it's an income account. It must be
> defaulting, and it shouldn't do that if Assets:A/R already exists. An Asset
> account type should be considered compatible.

The QIF is.   You should know that.  QIF Accounts are Asset/Liabilities.
Everything else is Income/Expense.  So yes, there is a default account
type based on the actual QIF transaction information.  Whether or not
this is right or wrong I leave for another day, but the way the QIF
importer is currently structured makes it very hard to just remove
this....

> Does he really have an existing GnuCash account named Assets:A/R, or is the
> name perhaps slightly different, like Assets:Accounts Receivable? That could
> explain the behavior.

This question is irrelevant.  He's telling the importer to create an
account Foo:Bar.  If Foo:Bar doesn't exist then it will be created
with the correct type (in this case, Income).  If Foo exists and is
a compatible type then it will just create Bar.  However if Foo exists
and is NOT compatible then it will create Foo2 of the correct type.

I'm not exactly sure why it creates Bar2 as well, but it does in this
latter case.

In HIS case he asked for Assets:<Something>...  Assets already exists
but is incompatible with Income, so it creates Assets2.

Note that compatibility is two-fold..  There is account-type compatibility
AND currency/commodity compatibility.  I believe that either case will
cause a new tree to get created.

> -Charles

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available



More information about the gnucash-user mailing list