[gnucash-user-owner@lists.gnucash.org: gnucash-user post from brian.horton@attglobal.net requires approval]

[Linas Vepstas]

Hi,
please subscribe to the mailing list.

--linas

----- Forwarded message from gnucash-user-owner at lists.gnucash.org -----
As list administrator, your authorization is requested for the
following mailing list posting:

From: Brian Horton <brian.horton at attglobal.net>
To: gnucash-user at lists.gnucash.org
Subject: qif import: no duplicates matched

I imported at seperate times a qif from my bank for my checking account,
savings account, and credit cards. There are several transactions in
each that are transfers back and forth. Yet the imported didn't flag any
as duplicates, so I ended up with a good number of them.

What are my options? I guess my only option now is to go thru and delete
the dups by hand, right? What about in the future? Is there anyway that
I can make it recognize the dup's better? Should/can I edit the .qif's
somehow before importing them so that it recognizes them better? Or
would dups get detected better if I imported the .qif's at the same
time? or..? (I haven't tried it, but would gnucash like it better if the
bank qif's had "transfer" instead of "t'fer"?) Should I rename my
accounts so that they have the same name (ie, 1111S1) as in the .qif?

There are some settings in the preferences related to Match score, and 
auto-ADD and auto-CLEAR, but I can't tell from the help if these will 
affect this or not..

Using 1.8.4 on RH8.0. Here are some bits from the .qif's that are dups
that didn't get recognized as dups:

Checking.qif: (1111S5 account)
D02/26/2003
PT'FER FROM 1111S1
N
T52.00
L
^
D02/26/2003
PCITIBANK-AUTOPAY/PAYMENT/
N
T-1851.58
L
^

Savings.qif (1111S1 account)
D02/26/2003
PT'FER TO 1111S5
N
T-52.00
L
^

CitibankCreditCard.qif:
D02/26/2003
T1851.58
PAUTOPAY 000000000004571RAUTOPAY AUTO-PMT
M
^


thx!!!

.bri.



Subject: confirm 775d9cec289ce967ba7462b3befd24d2f90e8a83
From: gnucash-user-request at lists.gnucash.org

If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message.  Do this if the message is
spam.  If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list.  The Approved: header can also appear in the first line
of the body of the reply.


----- End forwarded message -----

-- 
pub  1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <linas at linas.org>
PGP Key fingerprint = 8305 2521 6000 0B5E 8984  3F54 64A9 9A82 0104 5933