Duplicate and missing downloaded transactions using Express Web Connect

I have a long-standing problem with Quicken 2007 using automatic transaction update (Windows XP Professional). I am configured to use Express Web Connect with the bank. If I manually download a QFX file from the bank's web, it works perfectly. But, when doing it automatically using the Download Transaction wizard, some transactions occurring on the same day get mixed up.

I am wanting to know who else may have experienced this problem, to help motivate Quicken to do something about it. Or, does anyone have suggestion for getting better attention from Quicken? I have spent much time creating new files, re-installing Quicken, and all the other useless voodoo customer support asks you to do. I think it is very likely that this is a Quicken bug. So far, Quicken's interest in solving this problem has been underwhelming.

Here is a real example.The bank shows the following two transactions:

After pressing the "Update Transactions" button on the Downloaded Transactions tab in Quicken, the following two transactions show up:

New, 4/3/2009, TXFR, 5.00 New, 4/3/2009, TXFR, 5.00

The $674.02 transaction has been replaced by a duplicate of the $5.00 transaction. This happens often enough that it makes reconciliation a real pain. If I do the same transfer manually, the transactions are correct. But manual transfer is a pain because I have numerous accounts to reconcile.

This is not a renaming rule problem because the problem is occuring when Quicken downloads the bank data. For those interested in technical details, I have identified that Quicken is creating a corrupt temporary download file, which is created as part of the "Update Transactions" function. This is an XML-like file that describes the updated transactions received from the bank. It is possible that the bank is doing the corrupting, but that begs the question of why applying transactions manually works correctly, but the auto function does not. It seems more likely that Quicken is not properly parsing and processing the data stream from the bank.

Here is part of the actual temporary file that sets up the problem described in the example above:

- XFER 20090403170000.000 -5.00 20090403001 TRANSFER TO XXXXXXXXX-YYY WITHDRAWAL BY TRANSFER - 90044

XFER 20090403170000.000 -5.00 20090403000 TRANSFER TO XXXXXXXXX-YYY WITHDRAWAL BY TRANSFER - 90044

Doing the same download manual returns the following, correct file that shows the distinct transactions:

DIRECTDEBIT 20090403120000.000[-5:CDT] -674.02 20090403000 AUTO PAY Pre-Authorized DEBIT - 85708

XFER 20090403120000.000[-5:CDT] -5 20090403001 TRANSFER TO XXXXXXXXX-YYY WITHDRAWAL BY TRANSFER - 90044