Hendrik Boom <[EMAIL PROTECTED]> writes:
> Now I don't expect you to run and fix this (though it would be nice)
> immediately before a stable release, for fear of disturbing
> something else.
This period of time is for bug fixes, and you've found a bug, so it's
the perfect time to fix it.
The question is, what's the right way to fix the problem? In your
ideal solution, would Gnucash merge the two splits into one, following
the Cash account's representation of the event, or split the Cash
transaction, following the Checking account's representation?
> But if the mass import process were to produce a log of unmatched
> transfers, this would help me track them down.
This is on my list for 1.5 features in QIF import, along with a more
general mechanism for recognizing transactions that have already been
imported into gnucash.
Bill Gribble
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
