OFX importer and transaction matcher problems

[Benoit Grégoire]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Just out of curiosity, what's a typical case where the transaction
> amount manually entered and the one you're importing don't match
> exactly ? (Other than a typo when entering it)
> Personally I don't have any, which is why I asked the question
> above in the first place :)

The most typical case is transaction and associated fees merged by banks, 
typically for ATM withdrawals from an ATM belonging to another bank.

> > Humm, I was under the impression that those transactions wouldn't even
> > show once matched.  Unfortunately I don't have time to look into it right
> > now.
>
> When are transactions actually considered matched? When they show up as
> matched in the importer, or when you actually commit the import? If it's
> the latter, that would explain it.

They are considered matched when you actually commit the import.

> > > Thinking about it a bit more, I guess all I really want is an easy way
> > > to distinguish between the case where all transactions in a certain
> > > file have already been imported vs. no transactions found in the file
> > > (because of openSP problems for example)
> >
> > Now THAT is a good point...
>
> Perhaps a nice dialog box for both of these cases, which I think would
> be less confusing than the empty importer window you get now.

Indeed.

- -- 
Benoit Grégoire, http://step.polymtl.ca/~bock/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAX7qzmZ6zzPlLuwMRAqasAJ43fmnW9+ceumDCKtsGvDCnCtrmhwCgx3ku
ngOS3Kmtpq5Vdqseicmjkcc=
=tm/v
-----END PGP SIGNATURE-----