Importing mis-match

[Keith]

Thanks for the advice of reporting it as a bug. It's been entered into
Bugzilla and confirmed.

http://bugzilla.gnome.org/show_bug.cgi?id=458684

Keith

From: Derek Atkins <warlord at MIT.EDU>
> To: Keith <pdragon at pdragon.net>
> Date: Thu, 19 Jul 2007 15:29:45 -0400
> Subject: Re: Importing mis-match
> The importer should definitely not match against transations that
> have already been matched to an import with a different transaction ID.
> If it's doing that, that's a bug.  Please file a report in Bugzilla.
> Note that you may need to provide an example datafile and a sample
> OFX that show the problem in order to debug.
>
> -derek
>
> Keith <pdragon at pdragon.net> writes:
>
> > I use Gnucash for just basic checking account and credit card balance
> > tracking. My bank lets me download .ofx data and I just import that into
> > Gnucash to make entries and, at the end of the month, reconcile. One odd
> > thing I've noticed, though, is when importing my paycheck transactions.
> I
> > get paid a fixed amount twice a month, so the amount is always the same.
> I
> > typically don't enter my paycheck information in manually, and just let
> the
> > OFX import put it in. The problem is Gnucash keeps trying to auto-match
> &
> > reconcile my paycheck to old, previously imported paycheck transactions.
> > Even when they've already been cleared and/or reconciled. If I don't
> > manually change this to a new entry on the import screen, it's never
> > actually imported. And if I try to re-import again, Gnucash has somehow
> > associated my new paycheck transaction with the old, previous entry. So
> far,
> > thankfully, I've been able to catch this every time it happens (I notice
> I
> > have A LOT less money than I should) and just close Gnucash without
> saving
> > and reimport, fixing the incorrect match. If I hadn't ever caught this,
> I
> > honestly don't know how I could fix it. I could just manually enter the
> > paycheck in, I guess, but then I'm not sure if reconciling would work in
> the
> > end because I don't know what Gnucash did with that previous
> transaction.
> > It's somehow associated with another transaction, but I don't know how.
> >
> > Why is Gnucash matching to previous transactions that were either
> already
> > cleared or even reconciled? Is this a bug or am I doing something wrong?
> >
> > I started using Gnucash with the 2.1.1 beta and just last night upgraded
> > 2.2.0 stable. It's done this consistently through every version and
> still
> > does it with the new stable.
> >
> > Thanks in advance!
> >
> > Keith
> > _______________________________________________
> > gnucash-user mailing list
> > gnucash-user at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > -----
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> >
> >
>
> --
>        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
>
>
>
>