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; } } }

Wells Fargo Direct Connect error

Greg Brown

My direct connect bill pay bank had an error. I ran Validate & Repair and received the following: QEL:Removed 2 qel records for payments not in register. I have NO IDEA which records were removed...

I am still receiving the error on the Wells Fargo Direct Connect Account.

Screenshot 2025-07-13 072840.png

Find more posts tagged with

Comments

RalphC

I suspect that it's a temporary issue and that the servers are just down for maintenance. I, too, couldn't connect Sunday morning.

You apparently have/had some file corruption, but I don't believe it's related to your inabilty to connect Sunday morning. Typically, my IT shop would perform server maintenance Saturday-Sunday when there was little to no traffic and we would have a day to resolve any remaining issues after we brought the servers back up. Try again tomorrow (Monday) and I'll bet it's resolved.

[Deleted User]

@Greg Brown what error or error code did you get from the OSU? The QEL validate error may or may not be related.

That validate error message means Quicken found and removed two downloaded payment records (stored in the QEL file - the internal download log) that no longer matched anything in your account register. It’s essentially a cleanup notification and not usually a cause for concern.

Here’s what might trigger it:

You manually deleted or edited transactions in the register that had previously been matched to downloads.
The financial institution changed transaction data between downloads, causing mismatches.
You restored a backup or adjusted account settings, making older downloads no longer relevant.

Review your account register for any missing payments or duplicates just to be sure everything is reconciled.

Greg Brown

I understand the QEL errors weren't necessarily the cause of the connection error. My issue is when Quicken reports QEL errors why not report the detailed records right after the error message. It can be a laborious task to resolve, as noted below, from a previous issue. BTW the direct connect errors do NOT show in the OSU summary report, nor do any transactions from direct connect accounts appear there, as reported in previous othe posts. I assume that the QEL errors are probably a result of having to kill Quicken when OSU becomes unresponsive.

This was how I resolved a previous QEL error issue:

So… I opened a file from my 2nd computer from 2 days before I did the Validate and Repair. Updated that file, accepted downloaded transactions and all accounts balanced.

I then extraced csv files from both OOB accounts from both computers and compared them. The amount fields differences exactly matched the amount I was OOB on the original file. I matched the individual transactions and discovered that each account had at least one instance of duplicated transactions and missing transactions from the OOB file. Once I deleted the duplicated transactions and added the missing transactions, the accounts were in balance.

My conclusion is that the "QEL:Removed 3 qel records for payments not in register." was the cause of my OOB condition on both accounts.