dealing with invoices and QIF imports

[Charles Day]

On Thu, May 29, 2008 at 7:07 AM, Derek Atkins <warlord at mit.edu> wrote:

> "Charles Day" <cedayiv at gmail.com> writes:
>
> >         I just tried reproducing this, and in fact the QIF importer
> *does*
> >         allow a
> >         category to be mapped to an existing GnuCash account with an
> Asset
> >         account
> >         type. So that's not the problem.  -Charles
> >
> >     I believe it's a raw Payee/Memo mapping that is purely
> Income/Expense.
> >     So if the transaction has no L line, it's assumed to be
> Income/Expense.
> >
> > I can now reproduce this problem, but it's got nothing to do with the
> Asset
> > account type. You can map to that type of account, no sweat. I believe
> the
> > problem is that account types A/Receivable and A/Payable are completely
> > unknown to the QIF importer. I could just add specific support for these
> two
> > types, if you think that's good enough. Should be easy. But in general it
> > really seems to me that if a user picks or approves use of an existing
> GnuCash
> > account then the importer should use that account, regardless of account
> type,
> > as long as the commodity matches (since we are still restricted to
> > single-currency imports). That might be a bigger change though. Your
> thoughts?
>
> Oh, in that case, yes, just add the a/r and a/p account types to
> the lists of known assets and liabilities in the QIF importer.
>

Committed as r17180 with backport requested.

So, Leigh, I'm afraid that unless you have a test environment available and
can build GnuCash from trunk, you'll have to wait until 2.2.6 to try out the
fix. (It does work, according to my tests.)

-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
>