QuickBooks is unable to verify the financial institution

QuickBooks is unable to verify the Financial Institution information for this download.

It stops the import dead, it says nothing about which piece of information is wrong, and the file usually turns out to be fine. Here is what the message actually means and the fixes in the order that resolves it fastest.

What QuickBooks is checking

A Web Connect file carries identifiers naming where it came from. QuickBooks reads them before it reads any transactions, and compares them against the account you chose.

Identifier	What it is
BANKID	The bank’s routing number
INTU.BID	Intuit’s own id for that institution
ACCTID	The account number, or a fragment of it
ACCTTYPE	CHECKING, SAVINGS or CREDITLINE

The critical part is what happens on a first Web Connect import into an account: QuickBooks records those identifiers against it. From then on the account expects files from that institution, and a file naming a different one is refused.

That binding is invisible. There is no screen showing it and no button to clear it, which is why the error feels arbitrary: nothing you can see about the account has changed.

Fix 1: check you picked the right account

The most common cause, and the least interesting. Two checking accounts in the list, similar names, and the file belongs to the other one.

Retry the import and read the account name in the dropdown rather than accepting the default.

Fix 2: import into a brand new account

This is the fix that works when nothing else does, and it works because a new account has no binding to contradict.

Create a fresh account in the Chart of Accounts, import the file into that, then move the transactions if you need them somewhere else, or simply carry on in the new account and make the old one inactive.

It feels like a workaround and it is the supported behaviour: Intuit’s own guidance for unsupported institutions is to let QuickBooks bind the account on a first import.

Fix 3: confirm it is really a Web Connect file

Rename a copy to .txt and open it. A genuine Web Connect file begins with a block of key and value lines:

OFXHEADER:100
DATA:OFXSGML
VERSION:102

Then a blank line, then <OFX>. If your file starts with <?xml, it is OFX 2.x, which several QuickBooks versions refuse. If it starts with anything else, it is not a Web Connect file at all, and the most common impostor is a report exported from QuickBooks Online that happens to carry a .qbo name.

Fix 4: edit the identifiers

Last resort, and it works. The identifiers sit in plain text near the top of the file, and you can change them with any text editor.

Take them from a file your bank issued for the same account, if you have one, since those carry the ids Intuit has registered. Copy the BANKID, INTU.BID and ACCTID values across into the file that is failing.

Two cautions. Save as plain text, because a word processor will add formatting that breaks the file. And do not leave a wrong BANKID in a file you keep: the next import will inherit the confusion.

Fix 5: check the QuickBooks side

Occasionally the fault is not the file at all.

• The account is already connected to a bank feed. An account set up for direct connection sometimes refuses a manual Web Connect file. Deactivate the online services for that account, then import.
• The company file is on a mapped network drive. Web Connect imports are unreliable that way. Copy the .qbo to the same machine as the company file and import locally.
• The QuickBooks version is past its Web Connect sunset. Intuit disables online services on desktop editions after about three years. If yours is out of support, Web Connect is off entirely and the message can be its way of saying so.

Why converted files hit this more often

A converter has no way to know which institution Intuit has your account registered under. Your bank knows, because it pays Intuit for the branding and is issued an id; a file built from a CSV or a PDF cannot be.

So a converted file carries placeholder identifiers, and placeholders will never match an account already bound to a real bank. That is not a defect in the conversion, it is a fact about the format, and it is why fix 2 is the one that reliably works with a converted file.

Both converters here behave this way: CSV to QBO and a PDF statement to QBO write valid Web Connect files with placeholder institution ids, and the account you import into should be a new one the first time.

If none of it works

Import a CSV instead. QuickBooks Online takes CSV directly and never checks an institution id, because a CSV does not carry one. It is a step sideways rather than a fix, and it gets the transactions into your books today.

On Desktop, where CSV is not an option in most editions, the sequence that has never failed is: new account, import, move the transactions, make the old account inactive.