Are you using the CVS version or a recent 1.5 release, or are you
using 1.4? The QIF importer in 1.4 had a lot of problems, but the
newer one in CVS/1.5 is MUCH better.
You may still need to massage your QIF file a bit, depending on the
bank it comes from. But as of a couple months ago Grib fix
Hi Bill,
FYI, This isn't very important but I thought I'd mention it:
I was staring at our gnucash URL's: e.g.
Income
and realized that there's an internet draft for this stuff (excerpt
below). If we follow the draft, a compliant format would be:
Income
--linas
=
Hi again,
When I posted my last question, I was under the impression that online
banks used qif files -- that was a poor assumption. My bank (as well as
many others) are using web connect. Web connect uses a new format based
of of xml (as of version 2.0). This new format (ofx, I think) is tal
Nathan "A." Smith writes:
> Hi again,
>
> When I posted my last question, I was under the impression that online
> banks used qif files -- that was a poor assumption. My bank (as well as
> many others) are using web connect. Web connect uses a new format based
> of of xml (as of version 2.0).
Title: RE: importing "web connect" files -- was importing bank qif file
Hi,
I would like to stress the fact that OFX is not "a" version of XML neither
it is XML compliant at this time.
The "problem" with OFX is that is does not enforce closing of every single
tag. Even some client parsers
"Bruin, Bolke de" writes:
>
> I would like to stress the fact that OFX is not "a" version of XML neither
> it is XML compliant at this time.
>
> The "problem" with OFX is that is does not enforce closing of every single
> tag. Even some client parsers (most notably Quicken) bark on finding these
