Workaround for duplicate transactions (was: Am I missing something?)

Rob Prior rv7 at
Sat Feb 22 14:10:30 CST 2003

First the background:

Benoit Grégoire wrote:
> On February 12, 2003 10:40 pm, Rob Prior wrote:
>>Two (the real question):  When I import an .OFX file with a transaction
>>that withdraws from one account and deposits to another, say a transfer
>>of $500 from chequing to credit card, the OFX file has in it one entry
>>for the withdrawl from chequing, and one entry with the deposit to
>>credit card.  I have yet to see the OFX import wizard match these.  I
>>started using Gnucash at 1.7.7, but I just installed 1.8.1 last night
>>and it works the same.  This results in two entries in each account, one
>>of which has to be deleted from each account in order to balance things.
>>  Am I missing something?
> No, this is
> As you can see, the solution is not trivial.  I'll get to it eventually, but I 
> am very busy right now, and wanted to concentrate on data export capabilities 
> and libofx for the next few weeks.
> In the meantime, you can mark the second transaction as "SKIP" (no checkmarks) 
> in the matcher, which will save you from having to delete it in the register.
>>Frequently (but not always) a transfer to my credit card account shows
>>up as a withdrawl immediately in my account, but the credit to my credit
>>card account doesn't show up until the next business day, so the date on
>>the transaction is sometimes a day off.  Would that contribute?
> No, it would actually help.  If you download your file first between the two 
> transactions, and a second time after, the second transaction will be 
> recognised as a duplicate.

Now a possible workaround:

I found the other day that I can download my accounts individually, ie. not 
all at once in one file.  If I do this instead, then import each file 
separately (one for each of Chequing, Savings, and Credit Card), the 
transactions are all properly filed when the first file is opened, and then 
they can auto-match when the next file is opened with the duplicate transaction.

It's not the ideal solution, obviously, but until we figure out Quicken's 
algorithm for matching duplicates (I never had trouble with mismatched 
transfers between accounts in Quicken), it may be a good alternative.

Rob Prior
rv7 "at"
Stop dreaming... Start flying
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'

More information about the gnucash-devel mailing list