Matching transactions

[Doug Laidlaw]

What I miss, is being unable to edit a scheduled transaction before importing 
it.  Don's paycheck example is perhaps the most common.

Another issue is when a scheduled transaction doesn't happen on the exact day 
when it is supposed to.  The old clunky scheduler was better in this regard, 
but I wouldn't want to return to it!   Just being able to select some items 
rather than all or none, would improve things.  No doubt these issues are 
being worked on.  I am using 2.2.6 from the Mandriva 2009 repositories.

Comparing Gnucash and Quicken, amounts are matched better in Gnucash, but some 
other correspondences are worse.  For example, Gnucash will pick up a cheque 
number and amount and match it against the book entry, where Quicken can't, 
but in Quicken, after I right-click and elect to look for it myself, it gives 
me a selection screen with only 4 lines of the cashbook at a time in the 
window, a far more time-consuming process.  Quicken doesn't seem to use dates 
at all.  Instead of suggesting a transaction with the same date, it almost 
invariably suggests the earliest similar transaction.  Once again, a regular 
paycheck is the most common example.

Australia is still tied to QIFs.

Doug.

On Tuesday 16 December 2008 1:22:02 pm possum wrote:
> Thanks Derek.  Will try that and see how that works out over the next
> month.
>
> Derek Atkins wrote:
> > Hi,
> >
> > possum <don.harville at att.net> writes:
> >> I have set up some scheduled transaations to give me a look ahead 30
> >> days in
> >> the future.  I presumed that when I imported my bank transactions that
> >> if a
> >> scheduled transaction matched an imported transaction, then it would
> >> recognize it and not re-enter it.  On a similar note my paycheck varies
> >> a little bit each time so I can't schedule what it will exactly be each
> >> time.
> >> So I set up a scheduled transaction from my company with an estimated
> >> amount.
> >
> > No, the importers only deal with "Real" transactions that are
> > actually posted in the CoA.  You have to run the SXes first to
> > post them before the importer will see them.
> >
> >> In reality this is not working all the time.  The transactions from the
> >> bank
> >> have a long name with various information vs. the nickname that I used
> >> in the scheduled transaction, so GC doesn't recognize them as the same.
> >> Also
> >> the same thing for my paycheck since the amounts don't match up.
> >
> > The names don't need to match as much as the values do.
> >
> >> So can someone tell me how GC is supposed to work in matching imported
> >> transactions vs. scheduled transactions and what do I need to do to make
> >> it
> >> work as well as it can.  I do have Bayesian matching selected in my
> >> preferences.
> >> Thx
> >> --
> >>
> >> Please remember to CC this list on all your replies.
> >> You can do this by using Reply-To-List or Reply-All.
> >
> > -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
> > _______________________________________________
> > 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.