manual OFX creation
Josh Sled
jsled at asynchronous.org
Mon Nov 20 10:13:22 EST 2006
On Sun, 2006-11-19 at 23:00 -0800, Adam Monsen wrote:
> Only problem is, there doesn't seem to be any of that extremely handy
> automatic transaction description-to-GnuCash account matching that occurs
> when I do an OFX import. Well, there's something, but it doesn't seem to be
> as smart as whatever happens for OFX. It is definitely a different user
> interface; it only seems to match the transaction to the correct account
> when the description is a verbatim match.
Right. The QIF importer and the OFX importer are just different pieces
of code. The QIF importer is a bit fuzzy, but relatively literal, while
the OFX importer utilizes bayesian matching.
It is a known issue that the QIF importer should use the bayesian
importing code.
> 1. Is there some way to use the OFX import matching goodness when importing
> a QIF file?
Not until the QIF importer is re-written as above.
> 2. Why is the QIF import UI different than the OFX import UI?
That's just the way it was developed.
--
...jsled
http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo ${a}@${b}`
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.gnucash.org/pipermail/gnucash-user/attachments/20061120/9648f8a3/attachment.bin
More information about the gnucash-user
mailing list