nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Duplicate transactions

es114

I thought this problem was noted on the recent update as fixed. In my download this morning I had over 50 transactions duplicated which took hours to fix. Also continue to have unidentified security many times that I had to reconcile with Fidelity online.

Find more posts tagged with

Comments

NotACPA

Q keeps track of what has been previously downloaded via the FITID (Financial Institution Transaction ID).

When a transaction downloads with a previously viewed FITID, Q knows that it's a dupe and won't present it again.

HOWEVER, when the download method changes, in your case from Direct Connect (where Fido generates the FITID) to Express Web Connect+ (where Q/Intuit generate it) if's fairly common for the FITID to have been changed and thus Q to not recognize the dupe.

The only thing that you can do it to identify and delete the dupes. Downloading a dupe a 2nd time shouldn't happen. If it does, report that.